On 5/16/07, Daniel Rozeboom <[EMAIL PROTECTED]> wrote: > > Thanks so much for the quick response - I loaded up a 2.6.16.51 kernel > tree and (after fixing errors in the source code file for the driver) > managed to get the module installed and running. However, I'm still not > getting connectivity yet (I know this is probably beyond the domain of BLFS, > but perhaps you can lend some insight). The module loads up fine and > recognizes my card as eth0, but it always seems to say "Link Status: Not > Linked" and DHCP will fail due to a timeout error. Is this link status > equivalent to the driver detecting connectivity with a hub or the like? I > never see any received packets show up with ifconfig, but I do see two > transmitted packets for each DHCP attempt. I saw your post on the net about > checking for cable connectivity > (http://linuxfromscratch.org/pipermail/blfs-dev/2006-October/015767.html), > but on my system, /sys/class/net/eth0/carrier has no contents (neither a 1 > nor a 0) - do you know why that might be? Thanks for any advice you can > offer.
If I remember when I was experimenting with the carrier status, the entry would be null until "ip link set eth0 up" was done. For instance, I get a second ethernet device for firewire at eth1, and this has no contents in the carrier file. After I setup the device, it lists 1. So, it sounds like the device exists, but it hasn't been setup yet. Are you using the normal LFS networking scripts? They'll run /etc/sysconfig/network-devices/ifup eth0 so long as you have an ifconfig.eth0 directory. This in turn runs "ip link set eth0 up" and then any additional services you've setup in ifconfig.eth0. Could you show the output of "ifconfig eth0"? Does it change if you run "ip link set eth0 up"? -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
