[hardy] 2WIRE Wireless USB Dongle (prism based) does not work in Ubuntu

[Kyle M Weller]

Ok This card works perfectly with ndiswrapper, but this is a prism based chipset, I have done some windows driver hacking and dug all around the web to find a linux driver for this 2WIRE USB Adapter. Here is what I have found that may help the developers implement this card so the thousands of Linux users that have 2WIRE Products can use these cards. I have provided a lsusb -vvv and the original windows drivers and strings that are in the drivers that prove that the card is indeed Prism based.

USB ID 1630:0005

[Kyle M Weller (kylew)]

PRISMIOC.txt indicates that it is an Intersil branded chipset, formerly www.globespanvirata.com it also says:
PRISM Wireless LAN
ProductVersion
1.00.06.0097
Which indicates it is a prism based card
Arent older prism based cards implemented in the kernel? If so please let someone upstream know about this
I have provided a ndiswrapper howto for the public with issues with this card:
http://www.ubuntu-unleashed.com/2008/02/howto-setup-2wire-80211g-wireless-usb.html
But since prism is supported people shouldnt need to use ndiswrapper!

[Kyle M Weller (kylew)]

Here is the full driver cd (11mb) that came with the 2wire USB dongle, maybe something on there can help the developers
http://ubuntu-debs.googlecode.com/files/2wire_usb_install_cd.tar.gz

[Tormod Volden (tormodvolden)]

(Closing linux-wlan-ng task since this is not a prism2 device.)

[Kyle M Weller (kylew)]

Your wrong, it is actually a Z-Com prism2 device, I can go in winblows and load any prism2 driver after changing "just the usb device id" in the drivers and any of the prism devices load, imagine that. So id like to experiment by finding the source of the driver for ubuntu hardy and change the device id in the source, if it works I'll let you know, im pretty sure it will, this device is prism2, and works with aircrack-ng for winblows in monitor mode after I just change the id

[Kyle M Weller (kylew)]

Its a re-branded unknown usb device that all they did was change the device id, these drivers work for the card, all I do is change the device id to match so it loads:

USB Adapters Tested and Working :

NETGEAR WG121 (1st. Generation Fullmac) USB ID: VID 0846 PID 4210
DLINK DWL-G120(1st. Generation Fullmac) USB ID: VID 2001 PID 3701
NETGEAR WG111 version 1 R1(1st. Generation Fullmac) USB ID: VID 0846 PID 4220

NETGEAR WG111 version 1 R2(1st. Generation Softmac) USB ID: VID 0846 PID 4240

Bus 001 Device 002: ID 0cde:0006 Z-Com Medion 40900 802.11b Adapter
The above are prism based cards, all I do is change the device id in the windows drivers and it loads as prism just fine ie:
I changed USB\Vid_0cde&Pid_0006 to USB\Vid_1630&Pid_0005 which is my device id and the prism driver loads and works fine

[Fabien Tassin (fta)]

Re-marking Prism as invalid. This prism is Mozilla Prism, it has nothing to do with chipsets, See https://launchpad.net/prism/

[Kyle M Weller (kylew)]

It has prism nitro mode with the standard driver

[Tormod Volden (tormodvolden)]

> Your wrong, it is actually a Z-Com prism2 device

Quite possibly. I just "verified" by looking at the ID list in the driver source. The easiest way to get the source is to install the linux-wlan-ng-source package and use module-assistant to build it. It will be unpacked to /usr/src/modules where you can modify the source and rebuild the prism2_usb.ko and p80211.ko kernel modules. The ID list is in src/prism2/driver/prism2_usb.c.

[Tormod Volden (tormodvolden)]

FWIW, the other cards you mention "USB Adapters Tested and Working" above are prism54 cards and not prism2.

[Leann Ogasawara (leannogasawara)]

Just adding a note that this report will remain open against the actively developed kernel bug against 2.6.22 this will be closed as it does not qualify for a stable release update - https://wiki.ubuntu.com/StableReleaseUpdates . Thanks.

[Tormod Volden (tormodvolden)]

Closing linux-wlan-ng task, since this is not a prism2 device AFAICS.

[Leann Ogasawara (leannogasawara)]

Hi Kyle,

Unfortunately it appears the kernel devs did around to addressing this bug for Hardy. I'd like to try to keep this report up-to-date at least for the upcoming Intrepid Ibex 8.10 release. Care to confirm this is still an issue with the latest Alpha for the upcoming Intrepid Ibex 8.10. You should be able to test via a LiveCD - http://www.ubuntu.com/testing. Please let us know your results.

Additionally, beginning with the Intrepid Ibex 8.10 development cycle the linux-ubuntu-modules package was actually merged with the linux kernel package. Going forward, bugs that would have been reported against linux-ubuntu-modules should not just be reported against linux. The linux task is already properly opened for this report. Against 2.6.24 however this will be closed as this does not qualify for a Stable Release Update - http://wiki.ubuntu.com/StableReleaseUpdates . Thanks.

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[Bryan Wu (cooloney)]

Unfortunately it seems this bug is still an issue. Can you confirm this issue exists with the most recent Jaunty Jackalope 9.04 release - http://www.ubuntu.com/news/ubuntu-9.04-desktop . Please let us know your results. Thanks.

[bstempi (brian-stempin)]

I'm currently running Ubuntu Jaunty, and I still have this problem wit the D-Link DWL-G120.

[Jeremy Foshee (jeremyfoshee)]

Can someone test this against the current alpha of Lucid? I'd like to get this bug on my radar if it still exists on the kernel currently under development. Please also provide apport output to this bug and test against the mainline kernel build to verify whether this is upstream.

Thanks in advance.

-JFo

[Po-Hsu Lin (cypressyew)]

Closing this bug with Won't fix as Hardy is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!