Louis C. Candell said: > Brian Doob <[EMAIL PROTECTED]> writes: > >> These are two of my boot messages: >> * Failed to load 8139too [!!] >> * Failed to bring eth0 up [!!] > >> [kernel] eth0: Setting 100mbps full-duplex based auto negotiated >> partner ability 45e1 >> [kernel] NETDEV WATCHDOG: eth0 transmit timed out >> [dhcpd] timed out waiting for a valid DHCP server response >> [rc-scripts] Failed to bring eth0 up >> > > Your machine is trying to get your IP through a DHCP connection. You are > connecting your computer into a router, so does your ROUTER > assign IP's with DHCP?
I fear your posting is a herring of the scarlet varity, Louis. The dhcpd is in fact failing because of the previous lines: * Failed to load 8139too [!!] * Failed to bring eth0 up [!!] Of course the dhcpd can't get an address if the network card isn't detected. I believe Brian has correctly surmised this. Brian can you please confirm that: $ ls /lib/modules/*/kernel/drivers/net/ | grep 8139 8139cp.o 8139too.o This is where the module <makes sign of Holy Chipset> is stored. I'm not actually sure if the 8139cp module is necessary; if fact I see that that is produced by the first option below (RTL-8139 C+ PCI Fast Ethernet Adapter support). `make menuconfig` on my system shows: <M> RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERI <M> RealTek RTL-8139 PCI Fast Ethernet Adapter support [ ] Use PIO instead of MMIO [ ] Support for uncommon RTL-8139 rev. K (automatic channel equ [*] Support for older RTL-8129/8130 boards [ ] Use older RX-reset method So I guess the only way the network hardware part of my config differs from Brian's is that he has "Support for uncommon RTL-8139 rev. K" enabled. Maybe it would be worth a go recompiling without that..? Stroller. -- [EMAIL PROTECTED] mailing list
