Ethernet interface not configured at boot time

[Robert Clark]

I recently did an upgrade from Ubuntu 6.10 to Ubuntu 7.04, and after booting or rebooting, my network
is not configured. With 6.10, I had no issues with Wired or Wireless interfaces.

For this bug report, only the wired interface is installed in my DELL Inspiron 5000e.

After booting, the "Active Connection Information" popup has zeroes for all of the address and mask fields.

If I double click on the network icon in the top panel then the network is configured.

Output from: 'uname -a'
Linux rac-laptop 2.6.20-12-generic #2 SMP Sun Mar 18 03:07:14 UTC 2007 i686 GNU/Linux

Output from: 'cat /etc/lsb-release'
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=7.04
DISTRIB_CODENAME=feisty
DISTRIB_DESCRIPTION="Ubuntu feisty (development branch)"

###########################################
# Here is the output of ifconfig after booting:
###########################################
eth0 Link encap:Ethernet HWaddr 00:01:02:79:11:47
          inet6 addr: fe80::201:2ff:fe79:1147/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:96 errors:0 dropped:0 overruns:0 frame:0
          TX packets:56 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:6940 (6.7 KiB) TX bytes:8837 (8.6 KiB)
          Interrupt:11 Base address:0xa000

eth0:avah Link encap:Ethernet HWaddr 00:01:02:79:11:47
          inet addr:169.254.3.24 Bcast:169.254.255.255 Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          Interrupt:11 Base address:0xa000

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:2 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:100 (100.0 b) TX bytes:100 (100.0 b)

###########################################
# After double clicking the network icon in the top panel:
###########################################
eth0 Link encap:Ethernet HWaddr 00:01:02:79:11:47
          inet addr:10.19.67.13 Bcast:10.19.67.255 Mask:255.255.254.0
          inet6 addr: fe80::201:2ff:fe79:1147/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:336 errors:0 dropped:0 overruns:0 frame:0
          TX packets:172 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:27372 (26.7 KiB) TX bytes:23429 (22.8 KiB)
          Interrupt:11 Base address:0xa000

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:2 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:100 (100.0 b) TX bytes:100 (100.0 b)

###########################################
# /var/log/syslog:
###########################################
Mar 20 06:19:40 rac-laptop kernel: [ 30.084000] 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
Mar 20 06:19:40 rac-laptop kernel: [ 30.084000] 0000:02:00.0: 3Com PCI 3CCFE575CT Tornado CardBus at d8a0c000.
Mar 20 06:19:40 rac-laptop kernel: [ 30.084000] PCI: Setting latency timer of device 0000:02:00.0 to 64
Mar 20 06:19:40 rac-laptop kernel: [ 30.596000] ACPI: PCI Interrupt 0000:00:08.0[A] -> Link [LNKD] -> GSI 5 (level, low) -> IRQ 5
Mar 20 06:19:40 rac-laptop kernel: [ 30.960000] eth0: setting half-duplex.
Mar 20 06:19:40 rac-laptop kernel: [ 31.204000] es1968: clocking to 48000
Mar 20 06:19:40 rac-laptop kernel: [ 31.340000] Linux video capture interface: v2.00
Mar 20 06:19:40 rac-laptop kernel: [ 31.592000] lp0: using parport0 (interrupt-driven).
Mar 20 06:19:40 rac-laptop kernel: [ 31.664000] Adding 746980k swap on /dev/disk/by-uuid/b82e1171-1d16-486b-b605-22207aef8915. Prio
rity:-1 extents:1 across:746980k
Mar 20 06:19:40 rac-laptop kernel: [ 31.800000] EXT3 FS on sda1, internal journal
Mar 20 06:19:40 rac-laptop kernel: [ 32.388000] NET: Registered protocol family 17
Mar 20 06:19:40 rac-laptop kernel: [ 33.960000] eth0: setting full-duplex.
Mar 20 06:19:41 rac-laptop dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
Mar 20 06:19:46 rac-laptop dhcdbd: Started up.
Mar 20 06:19:46 rac-laptop NetworkManager: <information>^Istarting...
Mar 20 06:19:46 rac-laptop NetworkManager: <information>^Ieth0: Device is fully-supported using driver '3c59x'.
Mar 20 06:19:46 rac-laptop NetworkManager: <information>^Inm_device_init(): waiting for device's worker thread to start
Mar 20 06:19:46 rac-laptop NetworkManager: <information>^Inm_device_init(): device's worker thread started, continuing.
Mar 20 06:19:46 rac-laptop NetworkManager: <information>^INow managing wired Ethernet (802.3) device 'eth0'.
Mar 20 06:19:46 rac-laptop NetworkManager: <information>^IDeactivating device eth0.
Mar 20 06:19:46 rac-laptop avahi-daemon[4468]: Found user 'avahi' (UID 104) and group 'avahi' (GID 108).
Mar 20 06:19:46 rac-laptop avahi-daemon[4468]: Successfully dropped root privileges.
Mar 20 06:19:46 rac-laptop avahi-daemon[4468]: avahi-daemon 0.6.17 starting up.
Mar 20 06:19:46 rac-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.r
eason
Mar 20 06:19:46 rac-laptop NetworkManager: <information>^IWill activate wired connection 'eth0' because it now has a link.
Mar 20 06:19:46 rac-laptop NetworkManager: <information>^ISWITCH: no current connection, found better connection 'eth0'.
Mar 20 06:19:46 rac-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.r
eason
Mar 20 06:19:46 rac-laptop NetworkManager: <information>^IWill activate connection 'eth0'.
Mar 20 06:19:46 rac-laptop NetworkManager: <information>^IDevice eth0 activation scheduled...
Mar 20 06:19:46 rac-laptop NetworkManager: <information>^IActivation (eth0) started...
Mar 20 06:19:46 rac-laptop NetworkManager: <information>^IActivation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Mar 20 06:19:46 rac-laptop NetworkManager: <information>^IActivation (eth0) Stage 1 of 5 (Device Prepare) started...
Mar 20 06:19:46 rac-laptop NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Mar 20 06:19:46 rac-laptop NetworkManager: <information>^IActivation (eth0) Stage 1 of 5 (Device Prepare) complete.
Mar 20 06:19:46 rac-laptop NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) starting...
Mar 20 06:19:46 rac-laptop NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) successful.
Mar 20 06:19:46 rac-laptop NetworkManager: <information>^IActivation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Mar 20 06:19:46 rac-laptop NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) complete.
Mar 20 06:19:46 rac-laptop NetworkManager: <information>^IActivation (eth0) Stage 3 of 5 (IP Configure Start) started...
Mar 20 06:19:46 rac-laptop avahi-daemon[4468]: Successfully called chroot().
Mar 20 06:19:46 rac-laptop avahi-daemon[4468]: Successfully dropped remaining capabilities.
Mar 20 06:19:46 rac-laptop avahi-daemon[4468]: No service found in /etc/avahi/services.
Mar 20 06:19:46 rac-laptop avahi-daemon[4468]: Network interface enumeration completed.
Mar 20 06:19:46 rac-laptop avahi-daemon[4468]: Registering HINFO record with values 'I686'/'LINUX'.
Mar 20 06:19:46 rac-laptop avahi-daemon[4468]: Server startup complete. Host name is rac-laptop.local. Local service cookie is 1443889
62.
Mar 20 06:19:47 rac-laptop NetworkManager: <information>^IActivation (eth0) Beginning DHCP transaction.
Mar 20 06:19:47 rac-laptop dhclient: There is already a pid file /var/run/dhclient.eth0.pid with pid 134993440
Mar 20 06:19:47 rac-laptop NetworkManager: <information>^IActivation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Mar 20 06:19:47 rac-laptop NetworkManager: <information>^IDHCP daemon state is now 12 (successfully started) for interface eth0
Mar 20 06:19:47 rac-laptop kernel: [ 49.632000] NET: Registered protocol family 10
Mar 20 06:19:47 rac-laptop kernel: [ 49.632000] lo: Disabled Privacy Extensions
Mar 20 06:19:47 rac-laptop kernel: [ 49.724000] ppdev: user-space parallel port driver
Mar 20 06:19:49 rac-laptop avahi-daemon[4468]: Registering new address record for fe80::201:2ff:fe79:1147 on eth0.*.
Mar 20 06:19:49 rac-laptop NetworkManager: <information>^IDHCP daemon state is now 1 (starting) for interface eth0
Mar 20 06:19:49 rac-laptop kernel: [ 51.396000] [drm] Initialized drm 1.1.0 20060810
Mar 20 06:19:49 rac-laptop kernel: [ 51.448000] ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
Mar 20 06:19:49 rac-laptop kernel: [ 51.452000] [drm] Initialized r128 2.5.0 20030725 on minor 0
Mar 20 06:19:49 rac-laptop kernel: [ 51.452000] agpgart: Found an AGP 1.0 compliant device at 0000:00:00.0.
Mar 20 06:19:49 rac-laptop kernel: [ 51.452000] agpgart: BIOS bug. AGP bridge claims to only support x2 rateFixing up support for x1
Mar 20 06:19:49 rac-laptop kernel: [ 51.452000] agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode
Mar 20 06:19:49 rac-laptop kernel: [ 51.452000] agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode
Mar 20 06:19:50 rac-laptop dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
Mar 20 06:19:50 rac-laptop hpiod: 1.7.1 accepting connections at 2208...
Mar 20 06:19:53 rac-laptop dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
Mar 20 06:19:56 rac-laptop hcid[4790]: Bluetooth HCI daemon
Mar 20 06:19:57 rac-laptop kernel: [ 58.448000] Bluetooth: Core ver 2.11
Mar 20 06:19:57 rac-laptop kernel: [ 58.448000] NET: Registered protocol family 31
Mar 20 06:19:57 rac-laptop kernel: [ 58.448000] Bluetooth: HCI device and connection manager initialized
Mar 20 06:19:57 rac-laptop kernel: [ 58.448000] Bluetooth: HCI socket layer initialized
Mar 20 06:19:57 rac-laptop dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
Mar 20 06:19:57 rac-laptop xinetd[4789]: Reading included configuration file: /etc/xinetd.d/Xvnc [file=/etc/xinetd.conf] [line=14]
Mar 20 06:19:57 rac-laptop NetworkManager: <debug info>^I[1174396797.204687] nm_hal_device_added (): New device added (hal udi is '/or
g/freedesktop/Hal/devices/platform_bluetooth').
Mar 20 06:19:57 rac-laptop kernel: [ 59.012000] Bluetooth: L2CAP ver 2.8
Mar 20 06:19:57 rac-laptop kernel: [ 59.012000] Bluetooth: L2CAP socket layer initialized
Mar 20 06:19:57 rac-laptop kernel: [ 59.024000] Bluetooth: RFCOMM socket layer initialized
Mar 20 06:19:57 rac-laptop kernel: [ 59.024000] Bluetooth: RFCOMM TTY layer initialized
Mar 20 06:19:57 rac-laptop kernel: [ 59.024000] Bluetooth: RFCOMM ver 1.8
Mar 20 06:19:57 rac-laptop hcid[4790]: Starting SDP server
Mar 20 06:19:58 rac-laptop xinetd[4789]: Reading included configuration file: /etc/xinetd.d/chargen [file=/etc/xinetd.d/chargen] [line
=14]
Mar 20 06:19:58 rac-laptop xinetd[4789]: Reading included configuration file: /etc/xinetd.d/daytime [file=/etc/xinetd.d/daytime] [line
=28]
Mar 20 06:19:58 rac-laptop xinetd[4789]: Reading included configuration file: /etc/xinetd.d/discard [file=/etc/xinetd.d/discard] [line
=26]
Mar 20 06:19:58 rac-laptop xinetd[4789]: Reading included configuration file: /etc/xinetd.d/echo [file=/etc/xinetd.d/echo] [line=25]
Mar 20 06:19:58 rac-laptop xinetd[4789]: Reading included configuration file: /etc/xinetd.d/time [file=/etc/xinetd.d/time] [line=26]
Mar 20 06:19:58 rac-laptop xinetd[4789]: removing chargen
Mar 20 06:19:58 rac-laptop xinetd[4789]: removing chargen
Mar 20 06:19:58 rac-laptop xinetd[4789]: removing daytime
Mar 20 06:19:58 rac-laptop xinetd[4789]: removing daytime
Mar 20 06:19:58 rac-laptop xinetd[4789]: removing discard
Mar 20 06:19:58 rac-laptop xinetd[4789]: removing discard
Mar 20 06:19:58 rac-laptop xinetd[4789]: removing echo
Mar 20 06:19:58 rac-laptop xinetd[4789]: removing echo
Mar 20 06:19:58 rac-laptop xinetd[4789]: removing time
Mar 20 06:19:58 rac-laptop xinetd[4789]: removing time
Mar 20 06:19:58 rac-laptop xinetd[4789]: xinetd Version 2.3.14 started with libwrap loadavg options compiled in.
Mar 20 06:19:58 rac-laptop kernel: [ 60.224000] eth0: no IPv6 routers present
Mar 20 06:19:58 rac-laptop xinetd[4789]: Started working: 1 available service
Mar 20 06:19:58 rac-laptop anacron[4828]: Anacron 2.3 started on 2007-03-20
Mar 20 06:19:59 rac-laptop anacron[4828]: Normal exit (0 jobs run)
Mar 20 06:19:59 rac-laptop /usr/sbin/cron[4855]: (CRON) INFO (pidfile fd = 3)
Mar 20 06:19:59 rac-laptop /usr/sbin/cron[4856]: (CRON) STARTUP (fork ok)
Mar 20 06:19:59 rac-laptop /usr/sbin/cron[4856]: (CRON) INFO (Running @reboot jobs)
Mar 20 06:20:04 rac-laptop dhclient: No DHCPOFFERS received.
Mar 20 06:20:04 rac-laptop dhclient: No working leases in persistent database - sleeping.
Mar 20 06:20:04 rac-laptop dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Mar 20 06:20:04 rac-laptop avahi-autoipd(eth0)[4962]: Found user 'avahi-autoipd' (UID 110) and group 'avahi-autoipd' (GID 115).
Mar 20 06:20:04 rac-laptop avahi-autoipd(eth0)[4962]: Successfully called chroot().
Mar 20 06:20:04 rac-laptop avahi-autoipd(eth0)[4962]: Successfully dropped root privileges.
Mar 20 06:20:04 rac-laptop avahi-autoipd(eth0)[4962]: fopen() failed: Permission denied
Mar 20 06:20:04 rac-laptop avahi-autoipd(eth0)[4962]: Starting with address 169.254.3.24
Mar 20 06:20:08 rac-laptop gconfd (rac-5015): starting (version 2.18.0.1), pid 5015 user 'rac'
Mar 20 06:20:08 rac-laptop gconfd (rac-5015): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configurat
ion source at position 0
Mar 20 06:20:08 rac-laptop gconfd (rac-5015): Resolved address "xml:readwrite:/home/rac/.gconf" to a writable configuration source at
position 1
Mar 20 06:20:08 rac-laptop gconfd (rac-5015): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configurati
on source at position 2
Mar 20 06:20:08 rac-laptop gconfd (rac-5015): Resolved address "xml:readonly:/var/lib/gconf/debian.defaults" to a read-only configurat
ion source at position 3
Mar 20 06:20:08 rac-laptop gconfd (rac-5015): Resolved address "xml:readonly:/var/lib/gconf/defaults" to a read-only configuration sou
rce at position 4
Mar 20 06:20:09 rac-laptop avahi-autoipd(eth0)[4962]: Callout BIND, address 169.254.3.24 on interface eth0
Mar 20 06:20:10 rac-laptop avahi-daemon[4468]: Joining mDNS multicast group on interface eth0.IPv4 with address 169.254.3.24.
Mar 20 06:20:10 rac-laptop avahi-daemon[4468]: New relevant interface eth0.IPv4 for mDNS.
Mar 20 06:20:10 rac-laptop avahi-daemon[4468]: Registering new address record for 169.254.3.24 on eth0.IPv4.
Mar 20 06:20:12 rac-laptop dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
Mar 20 06:20:13 rac-laptop avahi-autoipd(eth0)[4962]: Successfully claimed IP address 169.254.3.24
Mar 20 06:20:13 rac-laptop avahi-autoipd(eth0)[4962]: fopen() failed: Permission denied
Mar 20 06:20:20 rac-laptop gconfd (rac-5015): Resolved address "xml:readwrite:/home/rac/.gconf" to a writable configuration source at
position 0
Mar 20 06:20:21 rac-laptop dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Mar 20 06:20:21 rac-laptop NetworkManager: <information>^IUpdating allowed wireless network lists.
Mar 20 06:20:21 rac-laptop NetworkManager: <WARNING>^I nm_dbus_get_networks_cb (): error received: org.freedesktop.NetworkManagerInfo.
NoNetworks - There are no wireless networks stored..
Mar 20 06:20:24 rac-laptop dhclient: No DHCPOFFERS received.
Mar 20 06:20:24 rac-laptop NetworkManager: <information>^IDHCP daemon state is now 9 (fail) for interface eth0
Mar 20 06:20:24 rac-laptop NetworkManager: <information>^IActivation (eth0) Stage 4 of 5 (IP Configure Timeout) scheduled...
Mar 20 06:20:24 rac-laptop NetworkManager: <information>^IActivation (eth0) Stage 4 of 5 (IP Configure Timeout) started...
Mar 20 06:20:24 rac-laptop NetworkManager: <information>^INo DHCP reply received. Automatically obtaining IP via Zeroconf.
Mar 20 06:20:24 rac-laptop NetworkManager: <information>^Iavahi-autoipd running on eth0, assuming IPv4LL address
Mar 20 06:20:24 rac-laptop NetworkManager: <information>^IActivation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
Mar 20 06:20:24 rac-laptop NetworkManager: <information>^IActivation (eth0) Stage 4 of 5 (IP Configure Timeout) complete.
Mar 20 06:20:24 rac-laptop NetworkManager: <information>^IActivation (eth0) Stage 5 of 5 (IP Configure Commit) started...
Mar 20 06:20:24 rac-laptop NetworkManager: <information>^Inot touching eth0 configuration, was configured externally
Mar 20 06:20:24 rac-laptop NetworkManager: <information>^IActivation (eth0) Finish handler scheduled.
Mar 20 06:20:24 rac-laptop NetworkManager: <information>^IActivation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
Mar 20 06:20:24 rac-laptop NetworkManager: <information>^IActivation (eth0) successful, device activated.
Mar 20 06:20:24 rac-laptop dhcdbd: Unrequested down ?:3
Mar 20 06:20:24 rac-laptop NetworkManager: <information>^IDHCP daemon state is now 14 (normal exit) for interface eth0
Mar 20 06:20:51 rac-laptop NetworkManager: <information>^IUser Switch: /org/freedesktop/NetworkManager/Devices/eth0
Mar 20 06:20:51 rac-laptop NetworkManager: <information>^IDeactivating device eth0.
Mar 20 06:20:51 rac-laptop avahi-daemon[4468]: Withdrawing address record for 169.254.3.24 on eth0.
Mar 20 06:20:51 rac-laptop avahi-daemon[4468]: Leaving mDNS multicast group on interface eth0.IPv4 with address 169.254.3.24.
Mar 20 06:20:51 rac-laptop avahi-daemon[4468]: Interface eth0.IPv4 no longer relevant for mDNS.
Mar 20 06:20:51 rac-laptop avahi-daemon[4468]: Withdrawing address record for fe80::201:2ff:fe79:1147 on eth0.
Mar 20 06:20:51 rac-laptop NetworkManager: <information>^IDevice eth0 activation scheduled...
Mar 20 06:20:51 rac-laptop NetworkManager: <information>^IActivation (eth0) started...
Mar 20 06:20:51 rac-laptop NetworkManager: <information>^IActivation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Mar 20 06:20:51 rac-laptop NetworkManager: <information>^IActivation (eth0) Stage 1 of 5 (Device Prepare) started...
Mar 20 06:20:51 rac-laptop NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Mar 20 06:20:51 rac-laptop NetworkManager: <information>^IActivation (eth0) Stage 1 of 5 (Device Prepare) complete.
Mar 20 06:20:51 rac-laptop NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) starting...
Mar 20 06:20:51 rac-laptop NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) successful.
Mar 20 06:20:51 rac-laptop NetworkManager: <information>^IActivation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Mar 20 06:20:51 rac-laptop NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) complete.
Mar 20 06:20:51 rac-laptop NetworkManager: <information>^IActivation (eth0) Stage 3 of 5 (IP Configure Start) started...
Mar 20 06:20:51 rac-laptop ntpdate[5158]: can't find host ntp.ubuntu.com
Mar 20 06:20:51 rac-laptop ntpdate[5158]: no servers can be used, exiting
Mar 20 06:20:51 rac-laptop ntpdate[5134]: can't find host ntp.ubuntu.com
Mar 20 06:20:51 rac-laptop ntpdate[5134]: no servers can be used, exiting
Mar 20 06:20:53 rac-laptop NetworkManager: <information>^IActivation (eth0) Beginning DHCP transaction.
Mar 20 06:20:53 rac-laptop NetworkManager: <information>^IActivation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Mar 20 06:20:53 rac-laptop NetworkManager: <information>^IDHCP daemon state is now 12 (successfully started) for interface eth0
Mar 20 06:20:53 rac-laptop avahi-autoipd(eth0)[4962]: Got SIGTERM, quitting.
Mar 20 06:20:53 rac-laptop avahi-autoipd(eth0)[4962]: Callout STOP, address 169.254.3.24 on interface eth0
Mar 20 06:20:53 rac-laptop avahi-autoipd(eth0)[4963]: client: RTNETLINK answers: No such device
Mar 20 06:20:53 rac-laptop avahi-autoipd(eth0)[4963]: Script execution failed with return value 2
Mar 20 06:20:54 rac-laptop NetworkManager: <information>^IDHCP daemon state is now 1 (starting) for interface eth0
Mar 20 06:20:55 rac-laptop dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
Mar 20 06:20:55 rac-laptop dhclient: DHCPOFFER from 10.19.66.3
Mar 20 06:20:55 rac-laptop dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Mar 20 06:20:55 rac-laptop dhclient: DHCPACK from 10.19.66.3
Mar 20 06:20:55 rac-laptop avahi-daemon[4468]: Joining mDNS multicast group on interface eth0.IPv4 with address 10.19.67.13.
Mar 20 06:20:55 rac-laptop avahi-daemon[4468]: New relevant interface eth0.IPv4 for mDNS.
Mar 20 06:20:55 rac-laptop avahi-daemon[4468]: Registering new address record for 10.19.67.13 on eth0.IPv4.
Mar 20 06:20:55 rac-laptop avahi-daemon[4468]: Withdrawing address record for 10.19.67.13 on eth0.
Mar 20 06:20:55 rac-laptop avahi-daemon[4468]: Leaving mDNS multicast group on interface eth0.IPv4 with address 10.19.67.13.
Mar 20 06:20:55 rac-laptop avahi-daemon[4468]: Interface eth0.IPv4 no longer relevant for mDNS.
Mar 20 06:20:55 rac-laptop avahi-daemon[4468]: Joining mDNS multicast group on interface eth0.IPv4 with address 10.19.67.13.
Mar 20 06:20:55 rac-laptop avahi-daemon[4468]: New relevant interface eth0.IPv4 for mDNS.
Mar 20 06:20:55 rac-laptop avahi-daemon[4468]: Registering new address record for 10.19.67.13 on eth0.IPv4.
Mar 20 06:20:55 rac-laptop NetworkManager: <information>^IDHCP daemon state is now 2 (bound) for interface eth0
Mar 20 06:20:55 rac-laptop NetworkManager: <information>^IActivation (eth0) Stage 4 of 5 (IP Configure Get) scheduled...
Mar 20 06:20:55 rac-laptop NetworkManager: <information>^IActivation (eth0) Stage 4 of 5 (IP Configure Get) started...
Mar 20 06:20:55 rac-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.h
ost_name
Mar 20 06:20:55 rac-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.n
is_domain
Mar 20 06:20:55 rac-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.n
is_servers
Mar 20 06:20:55 rac-laptop NetworkManager: <information>^IRetrieved the following IP4 configuration from the DHCP daemon:
Mar 20 06:20:55 rac-laptop NetworkManager: <information>^I address 10.19.67.13
Mar 20 06:20:55 rac-laptop NetworkManager: <information>^I netmask 255.255.254.0
Mar 20 06:20:55 rac-laptop NetworkManager: <information>^I broadcast 10.19.67.255
Mar 20 06:20:55 rac-laptop NetworkManager: <information>^I gateway 10.19.66.1
Mar 20 06:20:55 rac-laptop NetworkManager: <information>^I nameserver 10.19.66.12
Mar 20 06:20:55 rac-laptop NetworkManager: <information>^I nameserver 10.19.66.13
Mar 20 06:20:55 rac-laptop NetworkManager: <information>^I domain name 'somecompany.com'
Mar 20 06:20:55 rac-laptop NetworkManager: <information>^IActivation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
Mar 20 06:20:55 rac-laptop NetworkManager: <information>^IActivation (eth0) Stage 4 of 5 (IP Configure Get) complete.
Mar 20 06:20:55 rac-laptop NetworkManager: <information>^IActivation (eth0) Stage 5 of 5 (IP Configure Commit) started...
Mar 20 06:20:55 rac-laptop avahi-daemon[4468]: Withdrawing address record for 10.19.67.13 on eth0.
Mar 20 06:20:55 rac-laptop avahi-daemon[4468]: Leaving mDNS multicast group on interface eth0.IPv4 with address 10.19.67.13.
Mar 20 06:20:55 rac-laptop avahi-daemon[4468]: Interface eth0.IPv4 no longer relevant for mDNS.
Mar 20 06:20:55 rac-laptop avahi-daemon[4468]: Joining mDNS multicast group on interface eth0.IPv4 with address 10.19.67.13.
Mar 20 06:20:55 rac-laptop avahi-daemon[4468]: New relevant interface eth0.IPv4 for mDNS.
Mar 20 06:20:55 rac-laptop avahi-daemon[4468]: Registering new address record for 10.19.67.13 on eth0.IPv4.
Mar 20 06:20:55 rac-laptop dhclient: bound to 10.19.67.13 -- renewal in 114585 seconds.
Mar 20 06:20:56 rac-laptop NetworkManager: <information>^IClearing nscd hosts cache.
Mar 20 06:20:56 rac-laptop NetworkManager: <WARNING>^I nm_spawn_process (): nm_spawn_process('/usr/sbin/nscd -i hosts'): could not spa
wn process. (Failed to execute child process "/usr/sbin/nscd" (No such file or directory))
Mar 20 06:20:56 rac-laptop NetworkManager: <information>^IActivation (eth0) successful, device activated.
Mar 20 06:20:56 rac-laptop NetworkManager: <information>^IActivation (eth0) Finish handler scheduled.
Mar 20 06:20:56 rac-laptop NetworkManager: <information>^IActivation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
Mar 20 06:20:57 rac-laptop ntpdate[5271]: adjust time server 82.211.81.145 offset -0.460589 sec
Mar 20 06:20:57 rac-laptop avahi-daemon[4468]: Registering new address record for fe80::201:2ff:fe79:1147 on eth0.*.
Mar 20 06:21:06 rac-laptop kernel: [ 128.060000] eth0: no IPv6 routers present

ProblemType: Bug
Architecture: i386
Date: Tue Mar 20 06:21:25 2007
DistroRelease: Ubuntu 7.04
Uname: Linux rac-laptop 2.6.20-12-generic #2 SMP Sun Mar 18 03:07:14 UTC 2007 i686 GNU/Linux

[Robert Clark (robert-a-clark)]

I do not see this problem if fsck runs at boot time. This leads me to believe that this is a timing problem at boot time. I'm aware that changes were made to improve boot times in feisty. Since I never saw this problem in edgy, suspect the boot optimization(s) in feisty is causing the problem.

I think the automatic fsck after 30 boots, gives the ethernet setup enough time to complete before other network steps are done.

Others feisty users may not see this, because they are running on newer/faster hardware.

Portion of /proc/cpuinfo
cpu MHz : 746.793
cache size : 256 KB
bogomips : 1494.79

[corpus (rafaor-gmail)]

I have a similar issue that might confirm this bug:

After upgrading from dapper to feisty beta, my network interfaces with static IP assigned will come up but no IP will be configured.

Currently, I have 3 ethernet interfaces, 2 static IP and 1 DHCP.

Starting in recovery (single) mode, all interfaces come up fine.

Starting normally, only the dhcp interface will have an IP assigned until I manually restart networking with "/etc/init.d/networking restart", then all interfaces come up as they should.

Booting without splash shows no obvious errors, nor do the dmesg logs.

I don't see anything wrong in the init scripts:

root@xxx:/etc# find /etc/ -lname "*networking*"
/etc/rcS.d/S40networking

/etc/network/interfaces hasn't changed:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address 192.168.32.1
netmask 255.255.255.0

auto eth1
iface eth1 inet static
address 192.168.45.254
netmask 255.255.255.0

auto eth2
iface eth2 inet dhcp

I tried disabling (and even removing completely) the firewall (shorewall) and disabling avahi with no success.

My test hardware is also pretty old (Dell Optiplex GX150)

[folkoy (pluron)]

Using Feisty Beta I have same problem.
The PC has a single Ethernet card "eth0" using DHCP.

When Feisty boots, the eth0 interface is not enabled. The first time I log on after each reboot, I have to click on the small networking applet and click on "wired connection". Then the eth0 is braught up and work fine. The problem is that it should have been enabled by default during the boot of Ubuntu Feisty instead of requiring human intervention after each reboot.

I checked in the networking configuration tool under GNOME and KDE don't see any misconfiguration for the networking and interfaces.

This was not a problem under dapper.

This will confuse new Ubuntu users if their interface is not ON by default.

any suggestions?

thanks

[Mark Anton (mgastkn)]

I'm having a similar problem. I have to manually click on the "wired network" option on the networking applet (double-monitor icon) to get my AT&T DSL internet to get recognized. This was not a problem with the previous release of Ubuntu, only Feisty. I hope this gets fixed soon! My wired connection is set for dhcp.

[Robert Clark (robert-a-clark)]

This issue was apparently fixed through one of the feisty updates. I have not had any Ethernet configuration at startup up issues for over a week now.

I consider this bug Fixed. Thanks Ubuntu Team!

[folkoy (pluron)]

Hi Robert,
 My Feisty just got update few minutes ago (april 10). I rebooted and
the ethernet connection was not setup after reboot. I had to click again
on the small network applet in toolbar and select "Wired Connection".

I tried to change the config of the network interface in "Network
Settings" to enable Roaming mode. I rebooted and still the network
interface is not enabled after I logged in. So I disabled the "Roaming
mode", rebooted and did the following commands;

Immediately after reboot here is the state of my eth0;
$ sudo ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:50:2C:08:B9:02
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:46 errors:0 dropped:0 overruns:0 frame:0
          TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:13852 (13.5 KiB) TX bytes:1216 (1.1 KiB)
          Interrupt:19 Base address:0x9800

Then I tried to bringup and got the following message;
$ sudo ifup eth0
ifup: interface eth0 already configured

Then I tried to bring down and bring back up and it worked;
$ sudo ifdown eth0
There is already a pid file /var/run/dhclient.eth0.pid with pid 4078
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
...

$ sudo ifup eth0
There is already a pid file /var/run/dhclient.eth0.pid with pid
134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:50:2c:08:b9:02
Sending on LPF/eth0/00:50:2c:08:b9:02
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 20
DHCPOFFER from 192.168.0.175
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 192.168.0.175
bound to 192.168.0.100 -- renewal in 65270 seconds.

At that point the inerface is fine and up although the applet still
beleive the network interface is still off (this was expected).

Here is my interface file;
~$ sudo cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface

iface eth0 inet dhcp

auto eth0

This bug is still not fixed.

Are you ok to re-open the bug?

Is there any test I can do on my machine or any files I need to check?

What should I do to re-open the bug, can we transition the bug from
fixed to non fixed. I guess the priority is at least medium if not high.

thanks
Steve

On Tue, 2007-10-04 at 15:28 +0000, Robert Clark wrote:
> This issue was apparently fixed through one of the feisty updates. I
> have not had any Ethernet configuration at startup up issues for over a
> week now.
>
> I consider this bug Fixed. Thanks Ubuntu Team!
>

[Mark Anton (mgastkn)]

Hi Ubuntu Team,
I have the April 10 updates. Unfortunately, I still need to manually click
on the double-monitor icon and select "wired network" every time I boot up
my Ubuntu 7.04. Older versions didn't do this. Is it going to be fixed in an
update?

Mark Anton

On 4/10/07, folkoy <email address hidden> wrote:
>
> Hi Robert,
> My Feisty just got update few minutes ago (april 10). I rebooted
> and
> the ethernet connection was not setup after reboot. I had to click again
> on the small network applet in toolbar and select "Wired Connection".
>
> I tried to change the config of the network interface in "Network
> Settings" to enable Roaming mode. I rebooted and still the network
> interface is not enabled after I logged in. So I disabled the "Roaming
> mode", rebooted and did the following commands;
>
> Immediately after reboot here is the state of my eth0;
> $ sudo ifconfig eth0
> eth0 Link encap:Ethernet HWaddr 00:50:2C:08:B9:02
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:46 errors:0 dropped:0 overruns:0 frame:0
> TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:13852 (13.5 KiB) TX bytes:1216 (1.1 KiB)
> Interrupt:19 Base address:0x9800
>
> Then I tried to bringup and got the following message;
> $ sudo ifup eth0
> ifup: interface eth0 already configured
>
> Then I tried to bring down and bring back up and it worked;
> $ sudo ifdown eth0
> There is already a pid file /var/run/dhclient.eth0.pid with pid 4078
> killed old client process, removed PID file
> Internet Systems Consortium DHCP Client V3.0.4
> ...
>
> $ sudo ifup eth0
> There is already a pid file /var/run/dhclient.eth0.pid with pid
> 134993416
> Internet Systems Consortium DHCP Client V3.0.4
> Copyright 2004-2006 Internet Systems Consortium.
> All rights reserved.
> For info, please visit http://www.isc.org/sw/dhcp/
>
> Listening on LPF/eth0/00:50:2c:08:b9:02
> Sending on LPF/eth0/00:50:2c:08:b9:02
> Sending on Socket/fallback
> DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
> DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 20
> DHCPOFFER from 192.168.0.175
> DHCPREQUEST on eth0 to 255.255.255.255 port 67
> DHCPACK from 192.168.0.175
> bound to 192.168.0.100 -- renewal in 65270 seconds.
>
> At that point the inerface is fine and up although the applet still
> beleive the network interface is still off (this was expected).
>
> Here is my interface file;
> ~$ sudo cat /etc/network/interfaces
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
>
> # The loopback network interface
> auto lo
> iface lo inet loopback
>
> # The primary network interface
>
>
> iface eth0 inet dhcp
>
> auto eth0
>
>
> This bug is still not fixed.
>
> Are you ok to re-open the bug?
>
> Is there any test I can do on my machine or any files I need to check?
>
> What should I do to re-open the bug, can we transition the bug from
> fixed to non fixed. I guess the priority is at least medium if not high.
>
> thanks
> Steve
>
>
> On Tue, 2007-10-04 at 15:28 +...

[corpus (rafaor-gmail)]

Today's update seems to have fixed this for me. However, altho now "ifconfig" show all the interfaces as UP, the network icon says it's disabled. And if I "enable" it, network goes down.

[Robert Clark (robert-a-clark)]

My previous comments stating that this bug was fixed, were premature. Apparently a recent update has caused the issue to return.

I have the latest updates, and the original problem has re-appeared.

Additional information, which may require separate bug reports:

1) my Gigabit PCMCIA card, a Trendnet TEG-PCBUSR, now comes up in 10MB mode. This previously worked reliably in feisty at 100MB and 1000MB. It always woked at 100MB and 1000MB in Edgy.
2) my 802.11g Netgear PCMCIA wireless card no longer comes up properly at boot time. Rebooting sometimes allows the card/network to come up. This also worked reliably in Edgy.

I will provide more details on issues 1 and 2 above, when I can do more testing.

    Robert

[Mark Anton (mgastkn)]

Thanks for the information. My internet problem has never gone away. I still
have to manually click on the "wired network" at the double-monitor icon.
This problem still needs to be addressed, and we can only hope they do so.
Other aspects of Feisty Fawn are very good.

Mark Anton
Stockton, Ca

On 4/11/07, Robert Clark <email address hidden> wrote:
>
> My previous comments stating that this bug was fixed, were premature.
> Apparently a recent update has caused the issue to return.
>
> I have the latest updates, and the original problem has re-appeared.
>
> Additional information, which may require separate bug reports:
>
> 1) my Gigabit PCMCIA card, a Trendnet TEG-PCBUSR, now comes up in 10MB
> mode. This previously worked reliably in feisty at 100MB and 1000MB. It
> always woked at 100MB and 1000MB in Edgy.
> 2) my 802.11g Netgear PCMCIA wireless card no longer comes up properly at
> boot time. Rebooting sometimes allows the card/network to come up. This also
> worked reliably in Edgy.
>
> I will provide more details on issues 1 and 2 above, when I can do more
> testing.
>
> Robert
>
> --
> Ethernet interface not configured at boot time
> https://bugs.launchpad.net/bugs/94095
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Mark Anton (mgastkn)]

Hi Ubuntu Team!

I received today's (4/12) updates and my internet still won't come on
automatically, like it did for the previous version of Ubuntu. Feisty seems
to have a bug here. I've got my system, as it did before, set for "direct
connection" to access my AT&T DSL, and the network is set for DCHP. I still
have to manually click on the double-monitor icon near the clock and select
"wired network" before the internet will work.

Mark Anton
Stockton

[Mark Anton (mgastkn)]

Hi Ubuntu Team!

I received today's (4/14) updates and my internet still won't come on
automatically, like it did for the previous version of Ubuntu. Feisty seems
to have a bug here. I've got my system, as it did before, set for "direct
connection" to access my AT&T DSL, and the network is set for DCHP. I still
have to manually click on the double-monitor icon near the clock and select
"wired network" before the internet will work. The overall package seems to
be working pretty great, but this internet issue. I think, is pretty major
too. I read that Feisty Fawn won't be a Beta after April 19th, but I truly
believe that this issue needs to be cleaned up before you can say it's done.
Why isn't it detecting the internet as it's booting up? If you have an
questions you need to ask me, please feel free to do so.

Mark Anton
Stockton, California

[Martin Pitt (pitti)]

Mark, can you please attach your /etc/network/interfaces and /var/log/daemon.log (after a fresh boot) here?

[Mark Anton (mgastkn)]

I will be happy to, but I won't be able to until tonight when I get home to
that computer. To get that info for you, I guess I need to type those
commands in the terminal, right?

On 4/16/07, Martin Pitt <email address hidden> wrote:
>
> Mark, can you please attach your /etc/network/interfaces and
> /var/log/daemon.log (after a fresh boot) here?
>
> --
> Ethernet interface not configured at boot time
> https://bugs.launchpad.net/bugs/94095
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Robert Clark (robert-a-clark)]

No commands needed. Just attach the 2 files that Martin requested.

    =Robert

On 4/16/07, Mark Anton <email address hidden> wrote:
>
> I will be happy to, but I won't be able to until tonight when I get home
> to
> that computer. To get that info for you, I guess I need to type those
> commands in the terminal, right?
>
> On 4/16/07, Martin Pitt <email address hidden> wrote:
> >
> > Mark, can you please attach your /etc/network/interfaces and
> > /var/log/daemon.log (after a fresh boot) here?
> >
> > --
> > Ethernet interface not configured at boot time
> > https://bugs.launchpad.net/bugs/94095
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
>
> --
> Ethernet interface not configured at boot time
> https://bugs.launchpad.net/bugs/94095
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[folkoy (pluron)]

In attachement are 4 files.
deamon.log (/var/log/daemon.log) and messages (/var/log/messages) take after a clean bootup. I recapture the same file after clicking on the networking applet and on the "wired connection" so that Feisty connect to the network. If you do a diff of the two logs files you'll see intersting things that occured.

There was some dhcdbd error messages in the /var/log/messages that appears after clicking the network applet. Before booting the PC, the content of both /var/log/messages and daemon.log was erased to eliminate previous boot noise...

$ diff daemon.log daemon_after.log

Two lines were a bit scary;

1) eth0: Driver 'dmfe' does not support carrier detection. ^IYou must switch to it manually
2) Deactivating device eth0.

Then doing ;
$ diff messages messages_after

What's that redhat in the path?

1) Apr 16 18:20:58 ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason

The 4 files are in attachement. The interface file is already attached in a previous comment above.

[Mark Anton (mgastkn)]

Lo and behold, I have rebooted twice-- and it is now accessing the internet
by itself. Amazing. If you need any more information from me, please ask. I
want to help. I really appreciate what you guys are doing there.

Mark Anton
Stockton, Ca

On 4/16/07, Mark Anton <email address hidden> wrote:
>
> Here are the attatched files. Hope this helps. Thanks,
>
> Mark Anton
> Stockton
>
> On 4/16/07, Martin Pitt < <email address hidden>> wrote:
> >
> > Mark, can you please attach your /etc/network/interfaces and
> > /var/log/daemon.log (after a fresh boot) here?
> >
> > --
> > Ethernet interface not configured at boot time
> > https://bugs.launchpad.net/bugs/94095
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
>
>
>

[folkoy (pluron)]

forgot to mention in my reply above that the system got many package updated today and the networking problem is still there.

What other information might be usefull to you for debugging?

thanks

[Mark Anton (mgastkn)]

Hi,

Today, my computer logged on to the internet by itself. It happened after I
changed the setting manually. I noticed suddenly that it was now giving me
the option to do that when I move the mouse cursor over the double-monitor
icon. I kept it on the dchp setting. I rebooted a couple of times, and there
internet was there on its own.

Mark Anton

On 4/16/07, folkoy <email address hidden> wrote:
>
> forgot to mention in my reply above that the system got many package
> updated today and the networking problem is still there.
>
> What other information might be usefull to you for debugging?
>
> thanks
>
> --
> Ethernet interface not configured at boot time
> https://bugs.launchpad.net/bugs/94095
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Martin Pitt (pitti)]

Nice, thanks for checking this again. So this seems to be fixed in the latest version.

[folkoy (pluron)]

sorry, this bug is NOT fixed. Please re open the bug

[folkoy (pluron)]

Is there someone with enough privilege to re-open the bug status to "confirmed"? The problem is NOT fixed.
Do I need to re-open a new bug with same description?

[folkoy (pluron)]

bug is NOT fixed. Changing the bug status to "unconfirmed".

[Martin Pitt (pitti)]

Folkoy, maybe your network card does not support link beat detection. Can you please attach the output of

  dmesg | grep link

?

[folkoy (pluron)]

Hi Martin,
   That network card has been working without problem with Ubuntu 6.06 without a glitch and with many different Linux distro. It's only in Feisty that this problem occurs.

   Here is the output;
$ dmesg | grep link
[ 23.772183] audit: initializing netlink socket (disabled)

   Did you compare the last 4 files sent in my replies above aemon.log, daemon_after.log messages messages_after ?

   These logs are capture immediately after bootup and then re-capture after pressing on the networking applet then "wired Network".

  What else would be usefull for you?
thanks

[Ketil Malde (ketil-ii)]

It seems to me that my Dell D620 has similar problems. I typically use it wireless at home, suspend, dock it at work, and resumes. The network icon will then show up as if the wired network is working, but eth0 will not have an IP address. Clicking the 'wired network' item in the menu (twice?) fixes the problem.

I wonder if it is just the DHCP server that is slow to respond, and/or that the icon displays as connected to avahi being up and running? (I.e. eth0:avah is up).

-k

[Martin Pitt (pitti)]

folkoy, thanks for the dmesg output. So the problem is the missing carrier detect (link beat), duplicating to bug 83143.

[folkoy (pluron)]

Thanks,
BTW after a fresh install of latest Debian Etch 4.0, it also show the exact same problem. I assume the fix will also be pushed to Debian.

[Launchpad Janitor (janitor)]

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]

[jerrylamos (jerrylamos)]

Gutsy Tribe 5 (6) configures my network interfaces properly. Feisty and earlier Gutsy Tribes did not.
Jerry

[folkoy (pluron)]

Gutsy Tribe 5 is also working fine for me. My wired ethernet interface is up when I'm logged in the GUI.

[jerrylamos (jerrylamos)]

Oops, I spoke too soon, after yesterdays MASSIVE Ubuntu Tribe 5 (6?) upgrade, Network Mangler does not configure the network on one of my computers. I have to manually click on the Network Mangler icon.

If Network Mangler can connect fine when I click on the icon, why can't the programmers get it to connect during boot?? I can (have in times past) supplied /var/log/syslog, dmesg, anything anyone working on this bug wants to see.
Jerry

[Brian Murray (brian-murray)]

Jerry, you are commenting on a duplicate bug report of a bug which is marked as Invalid. Please submit a new bug report about network-manager and include the output of 'dmesg' and '/var/log/daemon.log' after booting your system.