Ubuntu hangs when configuring Gigabyte wireless card GN-WP01GS

Bug #54117 reported by Marcin Gałązka
2
Affects Status Importance Assigned to Milestone
linux-source-2.6.15 (Ubuntu)
Invalid
Medium
Ben Collins
linux-source-2.6.20 (Ubuntu)
Invalid
Medium
Ben Collins

Bug Description

Configuring network card via network-admin results in system hang on Ubuntu Dapper.

Step to reproduce:

1. Run network-admin
2. Choose GN-WP01GS wireless card
3. Click Properties
4. Enter settings (essid, wep-key, dhpc etc.)
5. Click Ok

System hangs after clicking Ok.

After booting iwconfig process takes ~100% CPU - killing or renicing process for some reason wasn't possible. To fix it wireless card must be removed from PC, then related entries deleted from /etc/network/interfaces after booting.

Workaround and more info is present here http://ubuntuforums.org/showthread.php?t=132980&highlight=ralink (I think this is solution for any RT2561 based card). Basically (for Dapper) it involves downloading firmware, config file, fetching config file with proper data (essid, wep-key...) and than enabling network interface using ifconfig or dhclient. Sometimes additional steps must be performed like adding default gateway using route.

Mentioned above workaround isn't 100% stable either. System still will hang if:
- config data isn't valid (e.g incorrect wep-key)
- access point settings are changed

There is also a (random) chance that system will hang when running ifconfig/dhclient (with proper data) or few second after that.

Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

Thank you for your bug report. Do you still have this issue with the latest release of Ubuntu ?

Changed in linux-source-2.6.15:
importance: Undecided → High
status: Unconfirmed → Needs Info
Revision history for this message
Marcin Gałązka (hipnoizz) wrote :

Partially - first attempt to configure this card on Feisty results in a hard lockup. After that everything looks ok, although it involves CLI - both network-admin and Network Manager were unable to do their work.

I suppose that Feisty uses a driver from http://rt2x00.serialmonkey.com instead an old Ralink driver so most bugs should be ironed. Not all nevertheless - https://bugs.launchpad.net/ubuntu/+bug/122774 ;-)

Changed in linux-source-2.6.15:
status: Incomplete → New
Revision history for this message
Ben Collins (ben-collins) wrote :

Please provide dmesg output (attach to bug report via web interface, do not paste into comment).

Changed in linux-source-2.6.20:
assignee: nobody → ben-collins
importance: High → Medium
status: New → Incomplete
Revision history for this message
Ben Collins (ben-collins) wrote :

Same for dapper, please.

Changed in linux-source-2.6.15:
assignee: nobody → ben-collins
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Brian Murray (brian-murray) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and feel free to submit bug reports in the future.

Changed in linux-source-2.6.15:
status: Incomplete → Invalid
Changed in linux-source-2.6.20:
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.