Arch Linux

zenlord

Member

From: Belgium

Registered: 2006-05-24

Posts: 1,221

Website

wlan-card (prism54) errors

Hi,

I tried to read up on wireless network(card)s in linux, but I did not find the solution to my problem. I cannot scan for wireless networks, and get two different errors:

- if I enable the radio-button on my laptop and let netcfg2 search automatically for wireless networks, I get an error with "SIOCSIFFLAGS" (googling this I got several links but nothing relevant). If I connect manually, it gives me the same error and it won't work;
- if I don't enable the radio-button on my laptop, I get a kernel panic upon booting, right at the time netcfg2 is trying to connect. The error message is related to the prism54-driver (line 232 IIRC) and says it is a "KERNEL BUG", whatever that may mean.

Using an Ubuntu livecd makes my wlan card work (or so it seems - I have no wireless networks in this neighbourhood, but it performs the scan alright).

What I did:
- follow the wiki on wireless networks
- install the prism54-driver and make sure it is loaded as a module (in the output of the kernel panic I described above, the prism54-module is confirmed to be loaded)
- copy the firmware (2.7.0.0) in /lib/firmware and rename it accordingly
- use netcfg2 as I have done on several computers, including another laptop with a wireless network (but uses an Intel-card).
- search google and some big linux-related forums (Ubuntu, LQ, this one, Gentoo) for problems with prism54-cards.

I don't need it right away, but it might be useful some day, and I would like to see this fixed. Does anyone have any idea what I could be overlooking?

THX!

Zl.
/EDIT: some output:

root /home/vincent #  dmesg | grep prism
Loaded prism54 driver, version 1.2
prism54: Your card/socket may be faulty, or IRQ line too busy :(
prism54: Your card/socket may be faulty, or IRQ line too busy :(

root /home/vincent #  dmesg | grep eth1
eth1: resetting device...
eth1: uploading firmware...
eth1: firmware version: 2.7.0.0
eth1: firmware upload complete
...
eth1: mgt_commit_list: failure. oid=17000007 err=-110
eth1: mgmt tx queue is still full
eth1: mgt_commit_list: failure. oid=19000001 err=-12
eth1: mgmt tx queue is still full
...

which results in:

root /home/vincent #  iwconfig eth1
eth1      NOT READY!  ESSID:"<private>"  
          Mode:Managed  Channel:0  Access Point: Not-Associated   
          Tx-Power=31 dBm   Sensitivity=0/200  
          Retry short limit:0   RTS thr=0 B   Fragment thr=0 B   
          Encryption key:0102-0304-05   Security mode:restricted
          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

root /home/vincent #  netcfg2 <private>
:: <private> up                                                       [BUSY]
SIOCSIFFLAGS: Operation not permitted
                    - Wireless association failed.                       [FAIL]

Hardware:

1260:3886 Network controller: Intersil Corporation module: prism54 
          ISL3886 [Prism Javelin/Prism Xbow]

root /home/vincent #  lsmod | grep prism
prism54                51976  0

Last edited by zenlord (2008-03-19 08:33:32)