| 1 |
> On Sat, 2005-07-09 at 17:22 -0400, dnebinger@××××.com wrote: |
| 2 |
> > Hey, all. Suffered power outtage yesterday. Not much of a big deal as |
| 3 |
> the |
| 4 |
> > ups brought the system down on battery... |
| 5 |
> > |
| 6 |
> > That's the good news. The bad news is that, upon system boot, my dhcp- |
| 7 |
> based |
| 8 |
> > eth0 interface no longer comes up and I don't know why... |
| 9 |
> > |
| 10 |
> > When the init script is run it reports that it is bringing the card up |
| 11 |
> in |
| 12 |
> > DHCP and that it is calling dhclient. At that point, however, the |
| 13 |
> startup |
| 14 |
> > shows the [!!] indicating a failure occurred but I have no real details |
| 15 |
> why. |
| 16 |
> > |
| 17 |
> > The only thing in the system log is a message from dhclient: |
| 18 |
> > receive_packet failed on eth0: Network is down. |
| 19 |
> |
| 20 |
> I suspect dhclient's pid was still around and you need to manually |
| 21 |
> kill/zap it before it will restart itself. |
| 22 |
> |
| 23 |
> I believe also that if you were to restart your PC/server now, all will |
| 24 |
> be oK |
| 25 |
|
| 26 |
Cycled the system many times with pretty much the same result. Initially |
| 27 |
dmesg was showing that ifconfig was failing due to some SMP issue so I |
| 28 |
updated the kernel to 2.6.12.2 and installed and this failure went away. |
| 29 |
|
| 30 |
But now any boot results in the dhcp starting for eth0 but then failing |
| 31 |
completely. |
| 32 |
|
| 33 |
When the system comes up I can log in as root and manually start eth0 by |
| 34 |
running the dhcp command as /etc/init.d/net.eth0 start should be trying to |
| 35 |
do (although I can't tell that it is doing as I suspect). |
| 36 |
|
| 37 |
|
| 38 |
-- |
| 39 |
gentoo-user@g.o mailing list |
Archives