regression rt2860sta - WPA2 TTLS in Eeepc 901 stopped working in Jaunty

Bug #356348 reported by gallir
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: network-manager

WPA + TTLS Wifi connections does not work in Jaunty on a EeePC installed from the Netbook USB installer. It worked in 08.10. It never login in, I don't know if it's a network-manager or a rt2860sta module problem.

Tags: jaunty
gallir (gallir-gmail)
tags: added: jaunty
Revision history for this message
Alexander Sack (asac) wrote :

lets start to triage this regression on the driver side (NM really doesn't do much different in jaunty). Have you tried to install linux-backport-modules-jaunty package? there might be "more modern" drivers available for your chipset.

Also after reboot/reproducing, please attach the complete syslog.

summary: - WPA2 TTLS in Eeepc 901 stopped working in Jaunty
+ regression rt2860sta - WPA2 TTLS in Eeepc 901 stopped working in Jaunty
affects: network-manager (Ubuntu) → linux (Ubuntu)
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Would also be good if you could attach your full dmesg output as well as lspci -vnvn:

dmesg > dmesg.log
sudo lspci -vnvn > lspci-vnvn.log

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
gallir (gallir-gmail) wrote :

@akexander and @lean OK, I'll do it tomorrow (ergh, today) morning at the university (where the connection has failed).

description: updated
Revision history for this message
gallir (gallir-gmail) wrote :

Find attached the dmesg and lspci logs of the tests.

I tried first with the standard linux-modules, later with the jaunty-backports. It failed in both cases.

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

Hi gallir,

I noticed the following in your dmesg output:

[47926.947715] <-- RTMPAllocTxRxRingMemory, Status=0
[47926.952501] --> Error 2 opening /etc/Wireless/RT2860STA/RT2860STA.dat
[47926.952511] 1. Phy Mode = 0
[47926.952515] 2. Phy Mode = 0
[47926.979407] 3. Phy Mode = 0
[47927.003288] MCS Set = 00 00 00 00 00
[47927.004979] <==== RTMPInitialize, Status=0
[47927.005055] 0x1300 = 00073200
[47932.065157] ===>rt_ioctl_giwscan. 5(5) BSS returned, data->length = 546
[47937.444077] ra0: no IPv6 routers present
[47942.069111] ===>rt_ioctl_giwscan. 5(5) BSS returned, data->length = 546
[47942.069924] ==>rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=11)
[47957.090177] ===>rt_ioctl_giwscan. 5(5) BSS returned, data->length = 546
[47957.090626] ==>rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=11)
[47972.106857] ===>rt_ioctl_giwscan. 5(5) BSS returned, data->length = 546
[47972.107671] ==>rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=11)
[47987.127029] ===>rt_ioctl_giwscan. 5(5) BSS returned, data->length = 546

These actually look to be the same sort of messages seen in bug 344022. So for now I'm going to mark this as a duplicate of bug 344022, please continue to track this issue at that report and add any additional information. Thanks.

Revision history for this message
gallir (gallir-gmail) wrote :

Confirmed, it's duplicated. Sorry for not detecting it before.

Revision history for this message
penalvch (penalvch) wrote :

gallir, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily kernel folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12-rc3

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. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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