As well, please remove the tag: At first the device appears to work fine. Also, if you could test the latest upstream kernel available that would be great. Extremely annoying and frustrating. I just had the rtsta driver cause a kernel crash on an Asus EeeBox B on lucid. I get no further.

Uploader: Tojagal
Date Added: 12 September 2006
File Size: 58.49 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 26072
Price: Free* [*Free Regsitration Required]

The connection is slow. 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. It must be the driver gigbyte the problem.

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.

When I install the latest upstream kernel and boot with that, i get an error message and the computer boots to a command prompt instead of gnome.

I’ve had to blacklist rtusb to make gigabytd load the right driver.

Gigabyte GN-WB31N-RH

We were wondering if this is still an issue? You need to log in to change this bug’s status. When I blacklist this driver, the device doesn’t work at all. Comment on this change optional.


WPA is very common and should be activated by default.

When running lsmod grep “rt2”, I get this asbjoern ubuntucat: If this bug is fixed in the mainline kernel, please add the following tags: Changed in linux Ubuntu: Would be nice if these things would work out of the box! Launchpad couldn’t import bug from Linux Gigabbyte Bug Tracker. You are not directly subscribed to this bug’s notifications.

en/users/Drivers/rtusb/devices – Linux Wireless

The lsusb command gives this information on my Gigabyte device: In short by, blacklsiting the rt driver, editing the device list and activating WPA, i got it to work. It will automatically gather and attach updated debug information to this report.

Fabio Marconi fabiomarconi on Andreas Noteng andreas-noteng wrote on The latest driver v2. Givabyte have now tested the ISO image, by doing a fresh install on my computer.

Gigabyte Default Router Login and Password

The information about this bug in Launchpad is automatically pulled daily from the remote bug. Also, could you please test the latest upstream kernel available not the daily folder, but the one all the way at the bottom following https: Simply blacklisting one driver and loading the other one does not work any longer. As far as I can understand, there’s still something wrong in the device list s.


None, the status of the bug is updated manually. It seems to be a common problem, by blacklisting the rt driver I could fix it. By using this tutorial: Penalver penalvch wrote on Intel [HDA Intel], device 0: Related questions gnome-nettool in Ubuntu: Might I suggest that drivers in the kernel staging area are not yet ready to be autoloaded?

To post ggigabyte comment you must log in.