ISO CD images are available from http: Latitude D NonfreeKernelMo dules: Linux Kernel Bug Tracker There is several reports concerning this chip set here on launchpad, but it’s still an issue, an issue that should be an easy fix for maverick. Other bug subscribers Subscribe someone else. Between lucid and maverick rt2x00 drivers have become the new default for many devices.
|Date Added:||11 October 2013|
|File Size:||22.85 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Also, could you please test the latest gnwb31n-rh kernel available not the daily folder, but the one all the way at the bottom following https: This bug affects 9 people.
Anonymous Meerkat lkjoel on Email me about changes to this bug report. However, there is a problem with speed.
GIGABYTE GN-WB31N-RH AirCruiser N300 USB Adapter Drivers, Utility
Might Gigabytf suggest that drivers in the kernel staging area are not yet ready to be autoloaded? There is several reports concerning this chip set here on launchpad, but it’s still an issue, an issue that should be an easy fix for maverick. It will automatically gather and attach updated debug information to this report. Instead the rt2x00 driver family is supposed to take over.
GN-WP30N-RH (rev. ) | Wireless Product – GIGABYTE Global
Latitude D NonfreeKernelMo gn-wb31n-dh Simply blacklisting one driver and loading the other one does not work any longer. This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. Gogabyte on this change optional. Please be sure to confirm this issue exists with the latest development release of Ubuntu. Fabio Marconi fabiomarconi on As far as I can understand, there’s still something wrong in the device list s.
A quick search here at launchpad indicates that there is other devices missing in the device list as well. In my gn-wb31h-rh the problem can not be solved without blacklisting the rt driver. Once you’ve tested the upstream kernel, please comment on which kernel version specifically you tested. If so, could you please test for this with the latest development release of Ubuntu? The output shows that the device use the rtusb driver, instead of the rtsta.
The latest driver v2. I wasn’t connected to a wireless network; I just ran powertop, which in turn ran iwpriv and triggered the crash. For the same reason it will also never make it from staging to the kernel proper.
Extremely annoying and frustrating. Since installing Natty fresh installation, not updateonly the rt pci driver is loaded, only when my netbook was in a good mood I could connect gn-wb31n-eh Wifi and it was not too often in that mood Wolfgang Kufner wolfgangkufner wrote on Apologies if it has reached you inappropriately; please just reply to this message indicating so.
I just had the rtsta driver cause a kernel crash on an Asus EeeBox B on lucid.
The connection is slow. Please let us know your results.
Now I use Once you’ve tested the upstream kernel, please remove the ‘needs- upstream- testing’ tag. Bug report concerns the same Gigabyte usb device on the same kernel, but does not mention the blacklisting rt issue. When I install the latest upstream kernel and boot with gn-wb31m-rh, i get an error message and the computer boots to a command prompt instead of gnome.