| View previous topic :: View next topic |
| Author |
Message |
Gentook
n00b
Joined: 13 Sep 2003
Posts: 46
Location: Shaker Heights, OH
|
 Posted: Fri Nov 12, 2004 1:53 pm Post subject: dhcp eth0 not working with multiple emerge and router upgrad |
 |
|
Hey all - I'm faced with a bit of a problem here. I emerged a bunch of things yesterday (nothing that I would have thought would do this - largely the end of kde331 and gnome28).
I also had a suspicion that something might have been weird with logins to my computer so upgraded my linksys wrt54g from the 1.43 firmware to the 3.01 firmware. Nothing changed otherwise with that.
There were a load of etc-update changes but the only ones that have changed in the last 24 hours (with a find -atime) are the pam.d kde and kde-np files. net.eth0 and conf.d/net have NOT changed. Also - I've tried this with 2 different kernels I had that worked fine before - the NIC driver is compiled into both of them.
Now I get some pam errors in messages (may have been there before granted) as well as
| Code: | | dhcpcd dhcpStart ioctl SIOCGIFHWADDR No Such Device |
errors. I can use everything sucessfully in windows but don't get anywhere otherwise.
Can anyone out there lend me a minute or two to troubleshoot? One of the problems is that I upgraded too many things at once. But there was nothing that I did where I thought I'd disrupt anything like this.
G |
|
| Back to top |
|
 |
Gentook
n00b
Joined: 13 Sep 2003
Posts: 46
Location: Shaker Heights, OH
|
| Posted: Fri Nov 12, 2004 2:29 pm Post subject: Ok, that was odd. |
|
|
Alright - that was odd. Seems that the via-rhine module (my apologies - I was wrong - the NIC drivers were modules) was not getting loaded into the kernel.
Is this a problem with hotplug? What could have changed it and is there a way to get it working automatically again so I don't have to boot into single first and insmod the thing myself?
Best wishes,
G |
|
| Back to top |
|
|
MdaG
l33t
Joined: 09 Nov 2004
Posts: 945
Location: Stockholm, Sverige
|
| Posted: Fri Nov 12, 2004 5:46 pm Post subject: |
|
|
| I have the same problem. I ended up in this situation mergin config files with "dispatch-conf" |
|
| Back to top |
|
|
mleck
n00b
Joined: 11 Jan 2005
Posts: 35
Location: UT
|
| Posted: Tue Jan 11, 2005 7:57 am Post subject: |
|
|
I also encountered this same problem. I fixed it by moving hotplug and coldplug to my boot run level:
| Code: |
rc-update add hotplug boot
rc-update add coldplug boot
rc-update del hotplug default
rc-update del coldplug default
|
Anyhow, as others have said on similar topics to this, the error is a result of the system not recognizing the hardware first. By moving these services to the boot runlevel, they detect your hardware before you try to actually use it - at least, that is what happened for me. I hope this helps.
Good Luck. |
|
| Back to top |
|
|
|
Networking & Security
