Brian Potkin wrote: > This is with today's daily build #1 for i386, using the installer build > from sid. > > I have tried to obtain an address with DHCP on a couple of machines > which are connected to a router by cable, but each time there is a > failure to do so. Static configuration of the interface does work. > > The syslog up to the end of this stage of the install is attached. Nov 29 14:21:59 kernel: [ 28.066457] 8139too: 8139too Fast Ethernet driver 0.9.28 Nov 29 14:21:59 kernel: [ 28.066528] 8139too 0000:00:0a.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 Nov 29 14:21:59 kernel: [ 28.067314] 8139too 0000:00:0a.0: eth0: RealTek RTL8139 at 0xe000, 00:a0:d2:a5:ad:25, IRQ 17 Nov 29 14:21:59 kernel: [ 28.067865] 8139cp: 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004) ... Nov 29 14:22:01 check-missing-firmware: no missing firmware in /dev/.udev/firmware-missing /run/udev/firmware-missing Nov 29 14:22:01 kernel: [ 29.842892] 8139too 0000:00:0a.0: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 ... Nov 29 14:22:35 main-menu[292]: (process:4523): Sending discover... Nov 29 14:22:35 main-menu[292]: (process:4523): udhcpc: sendto: Network is down Nov 29 14:22:35 main-menu[292]: (process:4523): Read error: Network is down, reopening socket Nov 29 14:22:35 main-menu[292]: (process:4523): Read error: Network is down, reopening socket ... Nov 29 14:24:13 netcfg[4524]: DEBUG: dhcp_client_sigchld() called Nov 29 14:24:13 kernel: [ 161.621068] 8139too 0000:00:0a.0: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 ... Nov 29 14:24:13 netcfg[4524]: INFO: executing: ip addr add 192.168.7.90/24 broadcast 192.168.7.255 dev eth0 ... Nov 29 14:24:32 main-menu[292]: (process:4523): udhcpc: sendto: Network is down Nov 29 14:24:32 main-menu[292]: (process:4523): Read error: Network is down, reopening socket This looks like it starts with the ethernet link up, and goes down before udhcpc is started, then after several minutes it goes up again, and even then udhcpc fails -- perhaps the link has gone down a second time? This could be anything from a faulty driver to a hardware problem to a cable problem. -- see shy jo
Attachment:
signature.asc
Description: Digital signature