prism2 not working anymore

Bug #84435 reported by KraetziChriZ
8
Affects Status Importance Assigned to Milestone
linux-source-2.6.17 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: linux-source-2.6.17

After Upgrading the Kernel to 2.6.17-11 my prism2 wlan card is not working anymore.

Unloading and loading the prism2_pci modul again brings the message that a prism device was found, but there is no device... (e.g. eth1)

:(

Revision history for this message
mariano.iannuzzi (mariano-iannuzzi) wrote :

Similar problem here, but I do not know which modulus is the problem.

I have an ACER Aspire with an integrated Intel a/b/g wireless card. The card worked great out of the box since dapper, it is just the latest edgy kernel update (17-11) that broke the card.

Thanks!

Revision history for this message
KraetziChriZ (christian.b) wrote :

other users habe same problem...:

http://ubuntuforums.org/showthread.php?t=358004&highlight=prism

I just get my card working again with the workaround here:
https://launchpad.net/ubuntu/+source/linux-source-2.6.17/+bug/63989

just added this 2 lines to the /etc/modprobe.d/blacklist:

blacklist hostap_pci
blacklist prism2_pci

and added "orinoco_pci" to the /etc/modules

Now my card is working. after reboot...

Revision history for this message
lojic (info-lojic) wrote :

I also have this problem.

IBM Thinkpad A31 with Actiontec Prism 2.5 Wavelan chipset

Worked fine with Ubuntu 6.10 2.6.17-10 and stopped working as soon as I applied the linux-image-generic 2.6.17-11 update.

KraetziChriZ - would you be able to elaborate on your solution? What is it about the -11 update that would require this "blacklist" method? i.e. why was it not necessary with -10 but is with -11? Is this a recommended solution, or a temporary workaround? Any extra info would be great.

Thanks!

Revision history for this message
lojic (info-lojic) wrote :

Sorry. I should have followed the link you provided before asking you to elaborate. That clarified things tremendously.

Revision history for this message
TrixSlice (syphonrealms) wrote : DELL 1450 with ndiswrapper and NetworkManager

I'm new to linux, so -10 was my first kernel. Instantly with the update to -11 my wireless Internet was dead. NetworkManager did NOT show wlan0 anymore.

I'm not sure how Linux operates, and how programs deal with kernels so I thought I might have to update all my programs. I proceeded to remove ndiswrapper, NetworkManager and wpa_supplicant. I cleanly reinstalled everything and still the same problem, but I got my wireless network to be displayed, I just can't connect.

I learned on the Ubuntu forum that I can Esc on boot and change to the -10 kernel. I plan on trying that after I post this.

Hope this gets fixed, Windows looks good right now.

Revision history for this message
justsee (justin-experimeme) wrote :

I booted after upgrading and my LInksys WMP54G wireless didn't work anymore either. I'm using the ra-tech linux drivers (http://gentoo.osuosl.org/distfiles/RT61_Linux_STA_Drv1.1.0.0.tar.gz), which I got working by following this: http://www.ubuntuforums.org/showthread.php?t=296822 . I don't have time to sort out wireless AGAIN on Ubuntu so booting and selecting 2.17.10 which is fine for now.

Revision history for this message
KraetziChriZ (christian.b) wrote :

Well, the problem is that the wireless networking card stops working if the kernel modules "hostap_pci", "prism2_pci" and "orinoco_pci" are loaded. I don't know why it works fine before upgrading the kernel, but the solution is a blacklisting of "hostap_pci" and "prism2_pci" and force loading "orinoco_pci". How to do this see my previous posting.

It's a 100% working workaround for Prism2/Orinoco Users. I don't build the new kernel, so I can't tell you what's going wrong there :-)

Other Users (intel ipw2200 and so on) must check which kernel modules are conflicting (and loaded both) and blacklist one of them. Yes, it's a geekish-workaround, but it's working for me...

Revision history for this message
KraetziChriZ (christian.b) wrote :

Looks like it's fixed with the newest Kernelupdate in Feisty.

Revision history for this message
Andrew Starr-Bochicchio (andrewsomething) wrote :

I'm closing this bug as the original reporter has indicated that their issue has been resolved.

Changed in linux-source-2.6.17:
status: New → 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.