Ubuntu
linux-source-2.6.20 package

[regression] cannot connect to WEP-protected access point in Feisty

Bug #108528 reported by Wiktor Wandachowicz
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: rt2500

Media used: Ubuntu 7.04 desktop i386 LiveCD

My computer has ASUS A8V Deluxe motherboard, with ASUS WiFi-g WL-130g
wireless PCI card (RaLink-based chipset, operated by rt2500 module).

Symptoms:

Network Manager doesn't work. It correctly displays access point's ESSID,
asks for WEP 128-bit Passphrase, but is unable to connect.

Manual configuration which worked flawlessly in Ubuntu 6.06 and 6.10
doesn't help either.

I tried to comment out all "auto IFACE" lines in /etc/networking/interfaces
and add the following section:

iface ra0 inet dhcp
wireless-essid przestrzen
wireless-key REAL-26-CHARS-LONG-HEX-KEY
auto ra0

Then I did the following:

# ifdown ra0
# modprobe -r rt2500

# modprobe rt2500
# /etc/init.d/networking restart

This procedure works in current Ubuntu 6.10 installation. However, in
Ubuntu 7.04 it fails. This is bad, because it leaves the machine without
any internet connection.

Additional information:

# uname -a
Linux ubuntu 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux

# dpkg -l | grep linux-image
ii linux-image-2.6.20-15-generic 2.6.20-15.27 Linux kernel image for version 2.6.20 on x86
ii linux-image-generic 2.6.20.15.14 Generic Linux kernel image

Revision history for this message
Wiktor Wandachowicz (siryes) wrote :
Revision history for this message
Wiktor Wandachowicz (siryes) wrote :
Revision history for this message
Wiktor Wandachowicz (siryes) wrote :
Revision history for this message
sam tygier (samtygier) wrote :

might be related to
bug 37120
though with that one can still connect using CLI tools or network-admin

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

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

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.

Revision history for this message
Michele Mangili (mangilimic) wrote :

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.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.