[SOLVED] Wireless authentication failed. ISL3890 [Prism GT/Prism Duette]

English Network/Internet
1

Hello

I’m putting my experiences here for when someone has the same problems. I spent way to much time for a problem with such easy solutions.

I’m using this laptop: Medion MD41300.

prism54 module freezes system with 2.6.22-10:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/134593
I think I might have these lockups too in Ubuntu 10.04 (or something else is the reason. I don’t know, nothing to see in dmesg). I didn’t know why and I assumed it had to do something with this bug:
Kernel instabilty on Medion MD41300 with Hyperthreading enabled / Mobile Pentium 4 HT 3.06Ghz
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.17/+bug/67110
But with disabled HT, there were still freezes.

Then I installed openSUSE 11.2 and the wireless worked fine.

In Hardy, it worked out of the box.
In Lucid, I had to install the linux-firmware-nonfree (kernel-firmware) package, but it had freezes.
In openSUSE 11.2, adding that package didn’t help. I manually put isl3886pci and isl3890 in /lib/firmware and it worked with no problems.
In openSUSE 11.3, I have had many problems with the wireless. I had it working with wicd, but after a minute or so it disconnected again. If I reconnected, it often said bad password, but then later it works again. Somewhat later, it didn’t work at all to connect to my private WPA protected network. However, when trying to do it manually, it connected to a wireless network from a neighbor. The strange thing is that NetworkManager/WiCD never shows a non protected network in my neighborhood.

Any tips for how I can easily connect again? :smiley:

I saved the different errors I had so Googlers can find this. I don’t know the exact configuration from when I took them.

The initial error I had. (I think)

9.723283] p54pci 0000:03:06.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
9.723345] p54pci 0000:03:06.0: firmware: requesting isl3886pci
9.758223] phy0: p54 detected a LM86 firmware
9.758228] p54: rx_mtu reduced from 3240 to 2376
9.758231] phy0: FW rev 2.13.12.0 - Softmac protocol 5.9
9.758234] phy0: cryptographic accelerator WEP:YES, TKIP:YES, CCMP:YES

10.893045] phy0: Cannot boot firmware!
10.893138] p54pci 0000:03:06.0: PCI INT A disabled
10.893150] p54pci: probe of 0000:03:06.0 failed with error -110

my wireless card:

03:06.0 Network controller: Intersil Corporation ISL3890 [Prism GT/Prism Duette]/ISL3886 [Prism Javelin/Prism Xbow] (rev 01)
Subsystem: Z-Com, Inc. XG-600 and clones Wireless Adapter
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx+
Latency: 80 (2500ns min, 7000ns max), Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 18
Region 0: Memory at d2004000 (32-bit, non-prefetchable) [size=8]
Capabilities: [dc] Power Management version 1
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: prism54

lspci -n

03:06.0 0280: 1260:3890 (rev 01)

Firmware files in place.
Wireless network card - openSUSE
so I blacklisted prism54 in /etc/modprobe.d/50-blacklis.conf

9.737066] p54pci 0000:03:06.0: PCI INT A -&gt; GSI 18 (level, low) -&gt; IRQ 18
9.737151] p54pci 0000:03:06.0: firmware: requesting isl3886pci
9.787201] phy0: p54 detected a LM86 firmware
9.787207] p54: rx_mtu reduced from 3240 to 2376
9.787209] phy0: FW rev 2.13.12.0 - Softmac protocol 5.9
9.787212] phy0: cryptographic accelerator WEP:YES, TKIP:YES, CCMP:YES

10.718139] phy0: hwaddr 00:60:b3:9e:4c:f3, MAC:isl3890 RF:Frisbee
10.824460] phy0: Selected rate control algorithm ‘minstrel’
10.825092] Registered led device: p54-phy0::assoc
10.825111] Registered led device: p54-phy0::tx
10.825128] Registered led device: p54-phy0::rx
10.825146] Registered led device: p54-phy0::radio
10.825154] p54pci 0000:03:06.0: is registered as ‘phy0’

p54pci blocked

73.739754] eth1: resetting device…
73.739772] eth1: uploading firmware…
74.175041] prism54 0000:03:06.0: firmware: requesting isl3890
74.444041] eth1: firmware version: 1.0.4.3
74.444090] eth1: firmware upload complete
74.684199] eth1: interface reset complete
74.684362] ADDRCONF(NETDEV_UP): eth1: link is not ready
74.903103] NET: Registered protocol family 17
76.211027] eth1: timeout waiting for mgmt response 1000, triggering device
83.874028] eth0: no IPv6 routers present
84.217845] eth1: timeout waiting for mgmt response 1000, triggering device
84.557758] IPv6 over IPv4 tunneling driver
84.559266] sit0: Disabled Privacy Extensions
84.673415] tun: Universal TUN/TAP device driver, 1.6
84.673419] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
85.186654] sixxs: Disabled Privacy Extensions
85.572150] RPC: Registered udp transport module.
85.572155] RPC: Registered tcp transport module.
85.572157] RPC: Registered tcp NFSv4.1 backchannel transport module.
85.633965] Slow work thread pool: Starting up
85.642121] Slow work thread pool: Ready
85.642184] FS-Cache: Loaded
85.718661] FS-Cache: Netfs ‘nfs’ registered for caching
88.286941] bootsplash: status on console 0 changed to on
94.262016] sixxs: no IPv6 routers present
111.778752] eth1: WPA IE Attachment was set
121.847666] eth1: WPA IE Attachment was set
161.948445] eth1: WPA IE Attachment was set
162.319760] eth1: timeout waiting for mgmt response 1000, triggering device
172.005499] eth1: WPA IE Attachment was set
182.058165] eth1: mgt_commit_list: failure. oid=19000004 err=1
182.063219] eth1: mgt_commit: failure
182.065323] eth1: WPA IE Attachment was set
192.117394] eth1: WPA IE Attachment was set
202.161436] eth1: mgt_commit_list: failure. oid=19000004 err=1
202.167336] eth1: mgt_commit: failure
202.169390] eth1: WPA IE Attachment was set
215.412940] eth1: mgt_commit_list: failure. oid=19000004 err=1
215.417919] eth1: mgt_commit: failure
215.420048] eth1: WPA IE Attachment was set
215.837030] eth1: timeout waiting for mgmt response 1000, triggering device
215.937032] eth1: timeout waiting for mgmt response 900, triggering device
216.037035] eth1: timeout waiting for mgmt response 800, triggering device
216.137031] eth1: timeout waiting for mgmt response 700, triggering device
216.237032] eth1: timeout waiting for mgmt response 600, triggering device
216.337031] eth1: timeout waiting for mgmt response 500, triggering device
216.437032] eth1: timeout waiting for mgmt response 400, triggering device
216.537032] eth1: timeout waiting for mgmt response 300, triggering device
216.637030] eth1: timeout waiting for mgmt response 200, triggering device
216.737030] eth1: timeout waiting for mgmt response 100, triggering device
216.737037] eth1: timeout waiting for mgmt response
216.847037] eth1: timeout waiting for mgmt response 1000, triggering device
216.947037] eth1: timeout waiting for mgmt response 900, triggering device
<snip>
219.764634] eth1: mgmt tx queue is still full
220.261156] eth1: mgmt tx queue is still full

Making Netgear WG511 work [Archive] - Ubuntu Forums
But I already did that and didn’t work.

Last thing I tried was installing ndiswrapper
SourceForge.net: Intersil ISL3890 - ndiswrapper
Only used some steps from this post: Forum Ubuntu-fr.org / [Tuto] Netgear PCMCIA WG511 V1

ndiswrapper -l

WARNING: All config files need .conf: /etc/modprobe.d/ndiswrapper, it will be ignored in a future release.
prisma00 : driver installed
device (1260:3890) present (alternate driver: prism54)

  • blacklisted other drivers
    blacklist prism54
    blacklist p54pci
  • add ndiswrapper to load at kernel boot
    Start /etc/sysconfig-editor
    System -> Kernel -> MODULES_LOADED_ON_BOOT
    And put there ndiswrapper

(just saw I was still using ndiswrapper: I removed it here and removed the two blacklisted ones)

And then I finally had an error which led me to the solution.

10.428785] ndiswrapper version 1.55 loaded (smp=yes, preempt=yes)
10.604261] ndiswrapper: driver prisma00 (GlobespanVirata,12/05/2003, 2.1.14.2) loaded
10.604674] ndiswrapper 0000:03:06.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
10.605608] ndiswrapper: using IRQ 18
11.994621] wlan0: ethernet device 00:60:b3:9e:4c:f3 using NDIS driver: prisma00, version: 0x2010e, NDIS version: 0x501, vendor: ‘PRISM 802.11g Wireless Adapter’, 1260:3890.5.conf
11.994657] wlan0: encryption modes supported: WEP; TKIP with WPA; AES/CCMP with WPA

894.778795] ndiswrapper (iw_set_auth:1602): invalid cmd 12
1192.982176] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
1193.002303] ADDRCONF(NETDEV_UP): wlan0: link is not ready
1198.556551] ndiswrapper (iw_set_auth:1602): invalid cmd 12
1199.857618] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
1203.763025] eth0: no IPv6 routers present
1209.917062] wlan0: no IPv6 routers present

chargement du module wifi
I cleaned my /tmp folder and rebooted. And then it all worked again.

I had this error in the beginning, but I didn’t find any useful help searching this. It also didn’t seem very relevant to me because I could still connect but after a minute the connection was lost.
Jul 24 12:12:34 laptopj gnomesu-pam-backend: The gnome keyring socket is not owned with the same credentials as the user login: /tmp/keyring-HzRTTR/control
Jul 24 12:12:34 laptopj gnomesu-pam-backend: gkr-pam: couldn’t unlock the login keyring.

I hope my post in here will be useful to someone.[/size]

2

Your post may help someone, but they will need stamina to wade through all the
detail.

To simplify things for readers:

(1) prism54 is obsolete and unmaintained. It is not surprising that it causes
all kinds of problems. It will disappear fairly soon (I think in 2.6.36) and
should not be used.

(2) You should only use ndiswrapper when there is no native Linux driver as it
allows a piece of code that has not been reviewed (the Windows driver) to have
unlimited access to the kernel. Think “kernel panics” - the equivalent of
Windows “Blue Screens of Death”.

(3) Using p54pci is a preferred solution. I do not have that device, but I do
have a unit that uses p54usb, which shares everything but the lowest level
hardware access routines. It is very stable in both the 2.4 and 5 GHz bands.

3

Well, I’m back to ndiswrapper because I can’t get p54pci nor prism54 to work. However, in openSUSE 11.2 I only needed to put the drivers in /lib/firmware and it worked!

Kernel driver in use: p54pci:

9.458604] p54pci 0000:03:06.0: PCI INT A -&gt; GSI 18 (level, low) -&gt; IRQ 18
9.458674] p54pci 0000:03:06.0: firmware: requesting isl3886pci
9.649450] phy0: p54 detected a LM86 firmware
9.649456] p54: rx_mtu reduced from 3240 to 2376
9.649458] phy0: FW rev 2.13.12.0 - Softmac protocol 5.9
9.649461] phy0: cryptographic accelerator WEP:YES, TKIP:YES, CCMP:YES
9.935152] ieee1394: Host added: ID:BUS[0-00:1023]  GUID[000ae4040510307e]

10.501989] phy0: hwaddr 00:60:b3:9e:4c:f3, MAC:isl3890 RF:Frisbee
10.557195] phy0: Selected rate control algorithm ‘minstrel’
10.557809] Registered led device: p54-phy0::assoc
10.557828] Registered led device: p54-phy0::tx
10.557846] Registered led device: p54-phy0::rx
10.557865] Registered led device: p54-phy0::radio
10.557873] p54pci 0000:03:06.0: is registered as ‘phy0’

97.725260] wlan0: direct probe to 00:21:29:83:8c:9e (try 1)
97.925038] wlan0: direct probe to 00:21:29:83:8c:9e (try 2)
98.125036] wlan0: direct probe to 00:21:29:83:8c:9e (try 3)
98.325056] wlan0: direct probe to 00:21:29:83:8c:9e timed out
108.102332] wlan0: direct probe to 00:21:29:83:8c:9e (try 1)
108.302084] wlan0: direct probe to 00:21:29:83:8c:9e (try 2)
108.502137] wlan0: direct probe to 00:21:29:83:8c:9e (try 3)

Kernel driver in use: prism54:

8.755705] p54pci 0000:03:06.0: PCI INT A -&gt; GSI 18 (level, low) -&gt; IRQ 18
8.755748] p54pci 0000:03:06.0: firmware: requesting isl3886pci
8.776039] tifm_core: MMC/SD card detected in socket 0:0
8.861204] phy0: p54 detected a LM86 firmware
8.861210] p54: rx_mtu reduced from 3240 to 2376
8.861212] phy0: FW rev 2.13.12.0 - Softmac protocol 5.9
8.861215] phy0: cryptographic accelerator WEP:YES, TKIP:YES, CCMP:YES
9.361023] intel8x0_measure_ac97_clock: measured 50401 usecs (2429 samples)
9.361028] intel8x0: clocking to 48000

10.008019] phy0: Cannot boot firmware!
10.008097] p54pci 0000:03:06.0: PCI INT A disabled
10.008108] p54pci: probe of 0000:03:06.0 failed with error -110

96.694004] Loaded prism54 driver, version 1.2
96.694806] prism54 0000:03:06.0: PCI INT A → GSI 18 (level, low) → IRQ 18
97.041243] eth1: resetting device…
97.041284] eth1: uploading firmware…
97.084157] prism54 0000:03:06.0: firmware: requesting isl3890
97.189378] eth1: firmware version: 1.0.4.3
97.189506] eth1: firmware upload complete
97.428955] eth1: interface reset complete
97.430028] ADDRCONF(NETDEV_UP): eth1: link is not ready
97.552879] NET: Registered protocol family 17
108.135627] eth1: WPA IE Attachment was set
118.184568] eth1: WPA IE Attachment was set
128.243075] eth1: WPA IE Attachment was set
138.307832] eth1: WPA IE Attachment was set
148.353690] eth1: mgt_commit_list: failure. oid=19000004 err=1
148.359359] eth1: mgt_commit: failure
148.361407] eth1: WPA IE Attachment was set
158.568401] eth1: mgt_commit_list: failure. oid=19000004 err=1
158.575469] eth1: mgt_commit: failure
158.576687] eth1: WPA IE Attachment was set
ect…

4

Hello,
I read the thread with interest as I am trying to get a Netgear WG511 wireless card to work with openSUSE 11.3 on a Dell Inspiron laptop. It is not clear to me what the solution was here.

I will post my own recent experience in another thread, but it sounds REALLY similar.

Dave

5

In 11.2/Ubuntu: adding the firmware in /lib/firmware and it worked.
In 11.3: cleaning /tmp folder because of authorization issues after a crash. And ultimately using ndiswrapper because I couldn’t get it to work like 11.2 or Ubuntu with the kernel drivers: then I have the errors seen in my previous post.

6

Thanks, I will look at the /tmp folder later. I am still interested in getting the native driver to work with 11.3 on this laptop.

I played around with this some last night. I am still trying to get the native driver working. I did notice in Yast that the driver for the Prism wireless card defaulted to “prism54”. After changing that to p54pci and saving the yellow led on the card lit up. But I still could not see my network or get it to connect to my router. However, I do see a neighbors network.

This is on a laptop that I previously had not been able to run opensuse on due to limited memory (320 MB). I was able to install 11.3 when running the installer on the livecd in text mode. The cd I am using is the one with LXDE as the desktop. Of course I AM able to install and run other versions of linux like Xubuntu, Lubuntu and Linux Mint. The wireless is really easy to set up in these. One thing I did notice is that the version of the kernel for these other versions of linux is older than in 11.3.

Of course, I could just give up and use one of those other versions of linux on this laptop. But that would be the easy way out …

7

It’s on my primary laptop, so it has to work for me until I have enough time to figure it out properly. I hope you succeed.

However, when trying to do it manually, it connected to a wireless network from a neighbor. The strange thing is that NetworkManager/WiCD never shows a non protected network in my neighborhood.

I still find that strange. I guess it could connect because it wasn’t protected. I even browsed their router config, but I never saw/see the network. I used the default password for the router to log in, but nowhere in the configuration screens I found the ssid or anything like that.
And it means p54pci or prism54 did work.
And I even got it to work with wicd and without ndiswrapper, all be it for a little while. So it must be possible.

8

I finally got a solution: install compat-wireless
https://build.opensuse.org/package/show?package=compat-wireless&project=driver%3Awireless
Just add the repository, refresh and install the automatically selected packages.

Same problem in another thread:
wlan not working ISL3886 (opensuse11.3)