No ethernet internet (dhcp) on fresh image

[tummychow]

When I dd the current raspi image onto an SD card and boot it with an ethernet cable plugged into my router, I get no internet connection. I can see from the router administration panel that there is no active DHCP client for the raspi, so the pi isn't even getting an IP address. (I'm accessing the pi over its serial port so I don't need a network or monitor to control it)

In fact, if I ifconfig, the only device listed is lo. ip link ls eth0 responds with "Device eth0 does not exist".

Not sure where to go from there because I was at least expecting the ethernet interface to... well, show up. Here's some more poking around, just in case it's useful:

$this->bbcode_second_pass_code('', '[root@alarmpi ~]# dmesg | grep eth0 | less
[ 3.295286] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:2d:07:28
[ 3.546659] smsc95xx 1-1.1:1.0 eth0: unregister 'smsc95xx' usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet
[ 3.816036] systemd[1]: Expecting device sys-subsystem-net-devices-eth0.device...
[ 4.682093] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:2d:07:28
[ 5.296647] smsc95xx 1-1.1:1.0 eth0: unregister 'smsc95xx' usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet
[ 6.366765] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:2d:07:28
[ 7.046691] smsc95xx 1-1.1:1.0 eth0: unregister 'smsc95xx' usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet
[ 8.573818] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:2d:07:28
[ 8.733966] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[ 10.228342] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1
[ 10.546877] smsc95xx 1-1.1:1.0 eth0: unregister 'smsc95xx' usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet
[ 10.547078] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[ 11.917452] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:2d:07:28
[ 14.296683] smsc95xx 1-1.1:1.0 eth0: unregister 'smsc95xx' usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet
')
It basically keeps going like that, alternating between unregister and register for several more lines. The last message is register.

$this->bbcode_second_pass_code('', '[root@alarmpi ~]# lsmod
Module Size Used by
snd_soc_pcm512x 8988 0
snd_soc_wm8804 7896 0
snd_soc_bcm2708_i2s 5653 0
regmap_mmio 2826 1 snd_soc_bcm2708_i2s
leds_gpio 2146 0
snd_soc_core 160700 3 snd_soc_pcm512x,snd_soc_wm8804,snd_soc_bcm2708_i2s
led_class 3731 1 leds_gpio
snd_compress 8167 1 snd_soc_core
spi_bcm2708 4764 0
i2c_bcm2708 4173 0
bcm2708_dmaengine 5108 0
regmap_spi 1925 3 snd_soc_pcm512x,snd_soc_wm8804,snd_soc_core
virt_dma 2281 1 bcm2708_dmaengine
regmap_i2c 1673 3 snd_soc_pcm512x,snd_soc_wm8804,snd_soc_core
snd_bcm2835 16293 0
snd_pcm 81885 2 snd_bcm2835,snd_soc_core
snd_page_alloc 5180 1 snd_pcm
snd_timer 20150 1 snd_pcm
snd 61384 5 snd_bcm2835,snd_soc_core,snd_timer,snd_pcm,snd_compress
bcm2708_rng 1032 0
rng_core 4147 1 bcm2708_rng
ipv6 303172 0')

[sdjf]

Have you studied the contents of /etc/netctl? You want a profile there that matches your setup. I am not well versed on what is on the current image, my ethernet is working well with a setup from last summer, but I think that is what needs to be set straight.

You can always bring up ethernet by hand...with an ifconfig command. I have a script running that makes sure my ethernet is running and available no matter what, as I found connections did not stay active for one reason or another.

Try this and see if it brings up your ethernet, for this you do not need the profile, pepedog knows this stuff real well, but I am answering as he has not popped in to do so.

ifconfig eth0 192.168.xxx.xxx netmask 255.255.255.0 up

Put the pi's ethernet address in the above in place of my 192.168.xxx.xxx, I have never used a router, but I think the above is worth a shot.

I do have a page about troubleshooting ethernet connectivity, although it is not up to date, but there may be some ideas that that might help you, if the above does not work.

http://sdjf.esmartdesign.com/raspberrypi/ethernet.html

And make sure you have adequate power on your pi, are you using model B? If A, you are using a powered hub for an ethernet adapter?

[tummychow]

I've reviewed the netctl profiles, the default profile for eth0 is suitable for this configuration. It uses DHCP over eth0 as expected.

ifconfig is deprecated, but I've tried ip link set eth0 up. I rebooted and re-imaged several times while exploring this issue; during the first few boots, this was enough to make the interface show up (and at that point I had various other issues). But if I invoke the command now, it consistently tells me that eth0 is not an interface (still not enumerating).

As for other solutions mentioned in your link, like systemd units or boot configuration, all of those things are set up properly by default (or at least they're supposed to be). Like I said, this is a fresh, completely untouched installation of an up-to-date image, where the ethernet interface should connect to a DHCP server once the pi is done booting up.

Personally I'm starting to suspect it's a problem with the LAN IC, but my soldering equipment is in another city right now and I can't inspect it myself. This is a model B revision 2, so the issues with the 1.8V line in the LAN IC were supposed to have been fixed... I've read some things about bad connections on its oscillator. At this point I'd be willing to believe that was the cause.