Ubuntu

Wireless networking broken in Network Manager

Bug #205215 reported by Jono Bacon
4
Affects Status Importance Assigned to Milestone
Ubuntu
New
Undecided
Unassigned

Bug Description

I recently upgraded to the new Hardy beta, and the upgrade went smoothly. However, when I rebooted, my wirless networking seems to be broken. When I look inside the manual configuration in nm-applet I see the following items:

  Wired connection (eth1)
  Wired connection (eth0)
  Wired connection (wlan0_rename)
  Point to point connection

All of the Wired connection tick boxed are ticked. I don't see any wireless networks when I click on the applet icon, and if I right-click there is no Enable Wireless option, just the Enable Networking option. If I left click the icon I just see a Manual Configuration... option.

iwconfig says that eth0 and eth1 don't have wireless extensions, and wlan0_rename does seem to have wireless there, but is not associated with an access point and has no essid.

The only other thing that might have affected this is that I had vmware installed and the kernel modules did not load due to the new kernel (the modules were built for the gutsy kernel), but I have uninstalled vmware.

Also, I know there was a HAL update shortly after the beta was released - I am running 0.5.11~rc2-1ubuntu2

The machine is a Dell M1330 with the Intel graphics and wireless. Interestingly, in Gutsy I needed a restricted driver for the wireless, but restricted manager says I don't need any restricted drivers.

Revision history for this message
Jono Bacon (jonobacon) wrote :

As requested, the output of ifconfig -a:

eth0 Link encap:Ethernet HWaddr 00:15:c5:80:ff:45
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
          Interrupt:17

eth1 Link encap:UNSPEC HWaddr 00-1C-BF-9D-42-85-00-00-00-00-00-00-00-00-00-00
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

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:1980 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1980 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:99000 (96.6 KB) TX bytes:99000 (96.6 KB)

wlan0_rename Link encap:Ethernet HWaddr 00:1c:bf:9d:42:85
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

And the output if iwconfig:

lo no wireless extensions.

eth0 no wireless extensions.

eth1 no wireless extensions.

wlan0_rename IEEE 802.11g ESSID:"" Nickname:""
          Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
          Tx-Power=27 dBm
          Retry min limit:7 RTS thr:off Fragment thr=2346 B
          Power Management:off
          Link Quality:0 Signal level:0 Noise level:0
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Revision history for this message
Daniel Robitaille (robitaille) wrote :

Possibly not related, but some of us experienced a broken network-manager for a few hours yesterday (i.e due to an Hal update released after Hardy Beta), but the latest hal (0.5.11~rc2-1ubuntu2) solved the problem (Bug #204778).

Revision history for this message
Lars Ljung (larslj) wrote :

What wireless card are you using? If you don't know the exact model you can use the command "lshw -class network" to find out.

Revision history for this message
Jono Bacon (jonobacon) wrote :

Also requested, the contents of the udev 70-persistent-net.rules file:

# This file maintains persistent names for network interfaces.
# See udev(7) for syntax.
#
# Entries are automatically added by the 75-persistent-net-generator.rules
# file; however you are also free to add your own entries.

# PCI device 0x14e4:0x1713 (tg3)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:15:c5:80:ff:45", NAME="eth0"

# PCI device 0x8086:0x4222 (ipw3945)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1c:bf:9d:42:85", NAME="eth1"

Revision history for this message
Jono Bacon (jonobacon) wrote :

Lars, output of lshw -class network:

  *-network
       description: Wireless interface
       product: PRO/Wireless 3945ABG Network Connection
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:0c:00.0
       logical name: eth1
       version: 02
       serial: 00:1c:bf:9d:42:85
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list logical ethernet physical wireless
       configuration: broadcast=yes driver=iwl3945 latency=0 module=iwl3945 multicast=yes wireless=IEEE 802.11g
  *-network
       description: Ethernet interface
       product: NetLink BCM5906M Fast Ethernet PCI Express
       vendor: Broadcom Corporation
       physical id: 0
       bus info: pci@0000:09:00.0
       logical name: eth0
       version: 02
       serial: 00:15:c5:80:ff:45
       capacity: 100MB/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm vpd msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=tg3 driverversion=3.86 latency=0 link=no module=tg3 multicast=yes port=twisted pair

Revision history for this message
Flávio Martins (flavioxmartins) wrote :

Jono you might want to try replacing the second part of the contents of the udev 70-persistent-net.rules file with:

# PCI device 0x8086:0x4222 (iwl3945)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTRS{address}=="00:1c:bf:9d:42:85", ATTR{type}=="1", NAME="wlan0"

Revision history for this message
Paul Sladen (sladen) wrote :

More of this at bug #204709.

Flávio: are 'ATTRS' and 'ATTR' supposed to be differerent on the second line?

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

Other bug subscribers

Remote bug watches

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