Network link is not ready at boot

Bug #69246 reported by Joce
4
Affects Status Importance Assigned to Milestone
Ubuntu
Fix Released
Undecided
Unassigned

Bug Description

The wireless link doesn't go up at boot, but once booted without it, "sudo /etc/init.d/networking restart" sets the link up without any problem.

$ lspci -vv
[...]
02:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
        Subsystem: Intel Corporation Unknown device 1001
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0, Cache Line Size: 32 bytes
        Interrupt: pin A routed to IRQ 169
        Region 0: Memory at fe0ff000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: <access denied>
[...]

$ cat /var/log/messages | grep -3 eth1
Oct 30 10:24:55 otto kernel: [17179623.696000] ipw3945: Detected geography ABG (13 802.11bg channels, 23 802.11a channels)
Oct 30 10:24:56 otto kernel: [17179624.488000] NET: Registered protocol family 10
Oct 30 10:24:56 otto kernel: [17179624.488000] lo: Disabled Privacy Extensions
Oct 30 10:24:56 otto kernel: [17179624.488000] ADDRCONF(NETDEV_UP): eth1: link is not ready
Oct 30 10:24:56 otto kernel: [17179624.488000] IPv6 over IPv4 tunneling driver
[...]

Revision history for this message
Pifpaf (pifpafe) wrote :

I have the same problem on my computer.
Wireless connection is well configured, because is working manually with "sudo /etc/init.d/networking restart"

Automatic connection at boot time is working with WEP and wihtout encryption, but not with WPA. I think there is something wrong with WPA (wpa_supplicant?)

Informations:
Im running Edgy Eft with last updates

$uname -a
Linux tuxmobile1 2.6.17-10-generic #2 SMP Fri Oct 13 18:45:35 UTC 2006 i686 GNU/Linux

$sudo lspci -vv
...
06:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
        Subsystem: Toshiba America Info Systems Unknown device ff00
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (8000ns min, 16000ns max)
        Interrupt: pin A routed to IRQ 58
        Region 0: I/O ports at 6000 [size=256]
        Region 1: Memory at c4006000 (32-bit, non-prefetchable) [size=256]
        Capabilities: [50] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0-,D1+,D2+,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

06:02.0 Network controller: Intel Corporation PRO/Wireless 2200BG Network Connection (rev 05)
        Subsystem: Intel Corporation Unknown device 2741
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (750ns min, 6000ns max), Cache Line Size: 32 bytes
        Interrupt: pin A routed to IRQ 66
        Region 0: Memory at c4007000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: [dc] Power Management version 2
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=1 PME-

$cat /etc/network/interfaces
auto lo
iface lo inet loopback
auto eth1
iface eth1 inet dhcp
        wpa-ssid MYSSID
        wpa-key-mgmt WPA-PSK
        wpa-psk xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

This happen on my computer : my laptop Toshiba m70-204 and on my PC AMD Athlon 1300 with netgear WG602v3 (ndiswrapper Window XP drivers)

Revision history for this message
Pifpaf (pifpafe) wrote :

I forget the dmesg log

Revision history for this message
trollord (trollenlord) wrote :

Feisty+networkmanager fixed these.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.