wireless card not workng hardy

Bug #205397 reported by Cody
4
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I just upgraded from Ubuntu Gutsy 7.10 to Ubuntu Hardy 8.04 and had a few problems in the process. I will not make a new bug for the sound card problem (the GStreamer plugin one) but the problem i have is with my wireless card. In Gutsy it worked fine and now it is not even being detected (so i think). Here is the steps ive done to try and get it working...

I turn on my Laptop (Asus F3S) and the lights turn on and stuff.... the 3 lights on the bottom (power,wireless,bluetooth) all flash and make a prety pattern... when i get to the ubuntu loading splash screen and press "Fn+F2" it will cycle through the pairs of wireless and bluetooth (I/O) meaning that it is in a way detecting it (i think). So i get to the login screen, (the wireless is out and the bluetooth is on) and put in my username and password. I get to the desktop and the wireless light is still out, and the bluetooth is on (the switch on the bottom to turn them on and off, is set to on). So i looked under every network GUI you can think of to try and find the wireless card, and some way to turn it on, but i couldn't and now im stuck with only ethernet connection.

Thanks a ton guys
~Cody Woolaver

Revision history for this message
BrandonTomlinson (druke) wrote :

did you check envy? (restricted driver manager) sounds like a driver issue.

Revision history for this message
Cody (cody-woolaver) wrote :

Yes i did, and the only restriced driver that i have is for my graphcs card

Revision history for this message
Wim (wimvandender) wrote :

Some people were having a similar problem after a libhal update. Please check Bug 205071. Maybe it is helpful

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

What wireless card are you using? Please check with the command lshw -class network

Revision history for this message
Cody (cody-woolaver) wrote :

When i run the "lshw -class network" command it prints:

cody@Charmander:~$ sudo lshw -class network
[sudo] password for cody:
PCI (sysfs)

and then holds there until i hit "ctrl+c" to cancel the opperation. I do not know if adding this information will help but here is some more information about my wireless card. The site happened to be in german, but you should still be able to get some unseful information from it.
[ http://www.hardware.info/nl-NL/productdb/bGRkZpiUmJHK/viewproduct/ASUS_F3S_F3SC/ ]

WLAN - Chip Intel PRO/Wireless 3945ABG
WLAN - Standaard 802.11 a/b/g
WLAN - Snelheid 54 Mbit/s

Thanks again guys
~Cody Woolaver

Revision history for this message
Cody (cody-woolaver) wrote :

Alright, after many days of trying to tackle this alone ive still goten really nowhere... but i did make an error eariler... that is not my wireless card...

03:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection (rev 61)

Also, here is an error message i come across

root@Charmander:~# dmesg | grep wl
[ 44.319471] iwlwifi_mac80211: disagrees about version of symbol struct_module
[ 44.326352] iwl4965: disagrees about version of symbol struct_module
[ 331.986254] iwlwifi_mac80211: disagrees about version of symbol struct_module
[ 331.986797] iwl4965: disagrees about version of symbol struct_module

Thanks

Revision history for this message
SFN (sfnative33) wrote :

I'm experiencing an issue that, while not identical, appears to be close enough to be the same issue.

My wireless card was working Gutsy but doesn't in Hardy. The lights never come on on mine though. Same for Bluetooth but I'm concerned about that. I've got an Acer TravelMate 8210-6245.

Like Cody's situation, the restricted driver manager also only shows my graphics driver.

"lshw -class network" provides the following info (MAC address obfuscated by me):

 *-network DISABLED
       description: Wireless interface
       product: PRO/Wireless 3945ABG Network Connection
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:05:00.0
       logical name: wmaster0
       version: 02
       serial: xx:xx:xx:xx:xx:xx
       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

"dmesg | grep wl" provided this:

[ 42.119025] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.0
[ 42.119029] iwl3945: Copyright(c) 2003-2007 Intel Corporation
[ 42.119213] iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection
[ 44.059914] iwl3945: Tunable channels: 11 802.11bg, 13 802.11a channels
[ 44.060908] wmaster0: Selected rate control algorithm 'iwl-3945-rs'
[ 5152.365601] iwl3945: Radio Frequency Kill Switch is On:
[ 5173.943446] iwl3945: Radio Frequency Kill Switch is On:
[ 5671.846359] iwl3945: Radio Frequency Kill Switch is On:
[ 5860.910542] iwl3945: Radio Frequency Kill Switch is On:
[ 6068.645457] iwl3945: Radio Frequency Kill Switch is On:
[ 6092.930875] iwl3945: Error sending REPLY_TX_PWR_TABLE_CMD: time out after 500ms.

Revision history for this message
Kyle Martin (martikj2-deactivatedaccount) wrote :

I'm having the same problem on my Dell 1420N, Intel Pro Wireless 3945, I can connect but my wireless light is dead.

Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this symptom still reproducible in 9.04 with linux-image-2.6.28-2-ub-generic?

Changed in linux-meta:
status: New → Incomplete
Revision history for this message
Javier Jardón (jjardon) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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