[REGRESSION] wusb54gc wireless card no longer supports monitor mode, packet injection, and now using rt73usb instead of rt73, cannot compile rt73 either (Ubuntu 7.10)

Bug #157419 reported by Joey Espinosa
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned
linux-source-2.6.22 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: linux-image-2.6.22-14-generic

This card worked in Ubuntu 7.04, and supported monitor mode and packet injection with the rt73 driver. Now, in Gutsy, it appears to be using the rt73usb driver, which does not support monitor mode or packet injection. I attempted to compile the rt73 driver, but it continuously errors out. Commenting out the block of code allows the card to be placed into monitor mode, but does not allow any sort of packet injection. Why isn't this working anymore!?!?

Revision history for this message
Joey Espinosa (therealjoelinux) wrote :

This is the error I get when trying to compile rt73:

make[1]: Entering directory `/usr/src/linux-headers-2.6.22-14-generic'
  CC [M] /home/joe/Download/temp/rt73-k2wrlz-1.0.0/Module/rtusb_data.o
/home/joe/Download/temp/rt73-k2wrlz-1.0.0/Module/rtusb_data.c: In function ‘RTUSBRxPacket’:
/home/joe/Download/temp/rt73-k2wrlz-1.0.0/Module/rtusb_data.c:1971: error: ‘struct sk_buff’ has no member named ‘mac’
make[2]: *** [/home/joe/Download/temp/rt73-k2wrlz-1.0.0/Module/rtusb_data.o] Error 1
make[1]: *** [_module_/home/joe/Download/temp/rt73-k2wrlz-1.0.0/Module] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-2.6.22-14-generic'
!!! WARNING: Module file much too big (>1MB)
!!! Check your kernel settings or use 'strip'
*** Module rt73.ko built successfully

It says that it built successfully, but no, it doesn't. It produces an error that I assume has something to do with the fact that the module no longer supports monitor mode or packet injection, and I purchased this wireless card for ONLY this purpose.

Revision history for this message
Joey Espinosa (therealjoelinux) wrote :

Ok, let me stick the plug in my own mouth!

I downloaded the latest CVS snapshot from http://rt2x00.serialmonkey.com, and I successfully compiled/installed it, without any tweaking of any sort (at all).

Now, my card works, with monitor mode and packet injection and all!

However, I'm still puzzled as to why Gutsy would use the rt73usb driver for this card if it's less functional than the rt73 driver. It's supposed to be an upgrade, not a downgrade...

But, at least we know now. Hopefully this will help whoever else stumbles across this problem.

--JoeLinux

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

I'm retargeting this bug towards the upcoming Hardy kernel. I've tagged this as "hardy-kernel-candidate" so that we make sure to retarget this report once the new release is out. However against the linux-source-2.6.22 package this is being marked as "Won't Fix" as it does not meet the criteria for a stable release update. To learn more about the stable release update process please refer to https://wiki.ubuntu.com/StableReleaseUpdates . Thanks!

Changed in linux-source-2.6.22:
status: New → Won't Fix
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hardy Heron Alpha2 was recently released. It contains an updated version of the kernel. You can download and try the new Hardy Heron Alpha2 release from http://cdimage.ubuntu.com/releases/hardy/alpha-2/ . You should be able to then test the new kernel via the LiveCD. If you can, please verify if this bug still exists or not and report back your results. General information regarding the release can also be found here: http://www.ubuntu.com/testing/hardy/alpha2 . Thanks!

Changed in linux:
status: New → Incomplete
Revision history for this message
wolfger (wolfger) wrote :

Over 4 months with no response. 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.