RT2561/RT61 - no wireless after update to 2.6.24-20

[RedRaider]

Hi,

New to Ubuntu and Linux and bug reporting, so please bear with me. I'm running Ubuntu 8.04 on a Dell Inspiron 8200 laptop. It has a Edimax EW-7108PCg wireless card (Ralink chipset). Anyway, wifi was working ok until I did a system update. I did that about 4 days ago, and all the updates installed fine, as far as I can tell. The next morning when I started up the computer, it showed no wifi connection, and in fact, I couldn't select a wireless network; I was unable to enable wireless networking. Also, neither of the activity lights on the card light up, like they used to.

To test if the card was working, I booted a 8.04 CD and did a live session. Wireless worked fine in the live session. The card works. Seems like something happened during the update.

As for the "source package I found the bug in", I have no idea. If I can figure it out, I'm attaching files necessary when reporting kernel bugs, although I'm not even sure this is a kernel bug issue. If you need more information, please tell me how to get that information for you, in addition to what information you need, as I am really new to Ubuntu.

Thank you,

RedRaider

P.S. I'm not quite sure how to attach multiple files to this report. The facility provided for including an attachment appears to only allow a single file to be attached. Let me know if you need more files and how to get them to you.

Update (7/28/08): looks like if I boot the 2.6.24-20-generic kernel, I don't have wireless networking. If I boot 2.6.24-19-generic, I have wireless.

[RedRaider (redraider1863)]

Looks like not all of the files got attached. Can the files only be attached one at a time?

[RedRaider (redraider1863)]

ugh, this is getting tedious

[RedRaider (redraider1863)]

There, finally...

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in linux.

[Brian Murray (brian-murray)]

Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance!

[RedRaider (redraider1863)]

Hi Brian, I took a look at the "finding the right package" page and it looks like it falls under "kernel related bugs" as it does not fall under any of the other packages. (This makes sense since when I run one kernel wireless does not work, but when I run a previous kernel it does work.) I don't know how to find the binary package because I don't know the process name. I also don't know how to find the source package. I also don't know how I am supposed to "associate" a package to this report. If you can provide a little more guidance, I'd appreciate it.

Regarding the 'uname -a', 'dmesg.log' and 'lspci-vvnn.log', I had previously attached these files, in separate attachments (see above). I couldn't figure out how to attach all of them together at the same time (if it is possible to attach multiple files together, please let me know how to do that, for future reference).

Thanks!

[yvon vignaud (yvonalaplage)]

Hi,

I have a similar problem with my wireless card on a sony laptop, after last kernel upgrade. As for RedRaider, wifi works perfectly well with kernel 2.6.24-19. I attach my logs.

Thanks,
Yvon

[RedRaider (redraider1863)]

Looks like the issue has been resolved for me. I just performed a system update and then booted into the 2.6.24-20-generic kernel. Wireless worked. I did notice that with 2.6.24-19-generic the activity light on my wifi card was always on, but with this kernel the wifi light only goes on when there's activity. Otherwise, things seem to be working so far.

[yvon vignaud (yvonalaplage)]

The problem is not solved in my case. The card is not detected by 2.6.24-20-generic kernel, and works perfectly with 2.6.24-19-generic.

[yvon vignaud (yvonalaplage)]

After system update (kernel upgraded to 2.6.24-21-generic) my wireless card with atheros chipset now works as well as with 2.6.24-19-generic. Kernel 2.6.24-20 still fail to detect it for some reason.

[Leann Ogasawara (leannogasawara)]

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.

[Ralph Janke (txwikinger)]

The Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . It contains the 2.6.27 Ubuntu kernel. It would be great if you could test and verify if this is still an issue. The status is being set to Incomplete until we receive further feedback. Thanks.

[yvon vignaud (yvonalaplage)]

Hi,

Dist-upgrade to Intrepid went smooth, and my wireless pcmcia card works fine under the new kernel 2.6.27-7-generic. In my case the problem was already solved with kernel 2.6.24-21.

[Leann Ogasawara (leannogasawara)]

Thanks for the update. Marking this "Fix Released" based on the last comment.

[Davies G (mo-3000)]

HI,

  I have had problems with this chipset since Gutsy, But I'm sorry to say that 8.10 still doesn't work correctly with this card...... at least with me anyway!

  It keeps asking me the enter the WEP key but never establishes a connection, after entering the the correct key it thinks about it, tries to establish an IP address, fails, then asks me again for the key. Exactly like Gutsy used too!

  Hardy was about the most stable, in so far that at least it would connect, and allow me to use firefox for about 5-7mins before the whole system would hang forcing me to reset.

I'll be happy to attach logs, please advise which ones you require.

[Leann Ogasawara (leannogasawara)]

Hi Davies,

Per the kernel team's bug policy, can you please attach the following information when running Intrepid. Please be sure to attach each file as a separate attachment.

* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log

It would also be good to wait to capture the dmesg output until after you've reproduced the issue just in case some useful error messages get logged. Additionally, I assume you are using NetworkManager? If so, it might also be interesting to take a look at your /var/log/syslog file after you reproduce the issue as well:

tail -n1000 /var/log/syslog > syslog.txt

If you can attach that too it would be great. For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help and feedback.

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.