[2.6.39][Oneiric][RT2860] Not able to connect to a secured wireless router with PEAP with TKIP/MSCHAPv2

Bug #777215 reported by Matthieu Baerts on 2011-05-04
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Undecided
Unassigned

Bug Description

Hello,

I'm using a Ralink RT2860 wireless card. It works well except if I try to connect to a secured wireless router with PEAP with TKIP/MSCHAPv2. I was able to connect to this network before but not now.
I already had this kind of bug on Lucid (bug #496093), on Maverick (bug #594866) and on Natty (bug #673440 => bug #659143).

Note that I was able to connect to this network only after having launched these commands (to blacklist some modules):
    $ sudo rmmod rt2800pci rt2860sta rt2x00pci
    $ sudo rmmod rt2800lib rt2x00lib
    $ sudo modprobe rt2860sta

This is my wpa_supplicant.conf used by Wicd:
    ctrl_interface=/var/run/wpa_supplicant
    network={
            ssid="student.UCLouvain"
            scan_ssid=0
            proto=WPA
            key_mgmt=WPA-EAP
            pairwise=TKIP
            group=TKIP
            eap=PEAP
            <email address hidden>"
            password="PASSWORD"
            ca_cert="/PATH/TO/chain-radius.pem"
            phase1="peaplabel=0"
            phase2="auth=MSCHAPV2"
}

We can also connect to this network by using PEAP-TTLS encryption but it didn't work too...
More information there: http://uclouvain.be/168492.html

Don't hesitate to tell me something to do if it's needed ;)
I'll join some useful files (dmesg, lspci, etc.)

    $ cat /proc/version_signature
       Ubuntu 2.6.39-0.5-generic 2.6.39-rc

Matthieu Baerts (matttbe) wrote :

There are some errors:
    [ 39.100490] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
    [ 39.170917] ADDRCONF(NETDEV_UP): wlan0: link is not ready

Matthieu Baerts (matttbe) wrote :

`lspci -vnvn` before the blacklisting

Matthieu Baerts (matttbe) wrote :

`lspci -vnvn` after the blacklisting

Matthieu Baerts (matttbe) wrote :

This what we have from the `lspci -vnvn` command for my Network controller

0a:00.0 Network controller [0280]: Ralink corp. RT2860 [1814:0781]
 Subsystem: Ralink corp. Device [1814:2790]
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0, Cache Line Size: 64 bytes
 Interrupt: pin A routed to IRQ 19
 Region 0: Memory at c2000000 (32-bit, non-prefetchable) [size=64K]
 Capabilities: [40] Power Management version 2
  Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold-)
  Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME+
 Capabilities: [50] MSI: Enable- Count=1/32 Maskable- 64bit+
  Address: 0000000000000000 Data: 0000
 Capabilities: [70] Express (v1) Endpoint, MSI 00
  DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <128ns, L1 <2us
   ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
  DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
   RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
   MaxPayload 128 bytes, MaxReadReq 512 bytes
  DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend-
  LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <512ns, L1 <64us
   ClockPM- Surprise- LLActRep- BwNot-
  LnkCtl: ASPM Disabled; RCB 128 bytes Disabled- Retrain- CommClk+
   ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
  LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
 Capabilities: [100 v1] Advanced Error Reporting
  UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq+ ACSViol-
  UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
  UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
  CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
  CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
  AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
 Kernel driver in use: rt2800pci
 Kernel modules: rt2860sta, rt2800pci

And this is the difference after having blacklisted a few module (comment #0):
    - Kernel driver in use: rt2800pci
    + Kernel driver in use: rt2860

Matthieu Baerts (matttbe) wrote :

I can reproduce it each time on this network (this is the network of my university and this kind of encryption is used almost everywhere in Europe (~eduroam)).

This is another file created with dmesg

Matthieu Baerts (matttbe) wrote :

But the conclusion is easy: my kernel loads a wrong driver for my RT2860 wireless card (rt2800pci instead of rt2860).

PS: I had this bug on Natty too last week (sorry, no time to report it :-/) so with the older kernel (2.6.38).

Brad Figg (brad-figg) on 2011-05-04
Changed in linux (Ubuntu):
status: New → Confirmed

Hi Matthieu,

rt2800pci is the right driver. It just seems it has this bug that you describe here. If you think it is the drivers fault I would like to encourage you to take the issue upstream:
http://rt2x00.serialmonkey.com/pipermail/users_rt2x00.serialmonkey.com
so this gets resolved as quickly as possible.

The staging driver rt2860sta is just a workaround. There is a reason it is in staging.

btw:
sudo modprobe -rv rt2800pci
unloads the driver in one go and lets you see what modules where unloaded.

Matthieu Baerts (matttbe) wrote :

It seems it works after having unloaded all rt* drivers and load this rt2800pci module with "nohwcrypt=1"
=> http://rt2x00.serialmonkey.com/pipermail/users_rt2x00.serialmonkey.com/2011-May/003756.html

Hi Matthieu,

what is the status of this bug now? I just read what seems to be the last of your messages on serialmonkey.com:
http://rt2x00.serialmonkey.com/pipermail/users_rt2x00.serialmonkey.com/2011-May/003782.html
and it seems to indicate that it did not work after all?

Thanks,
Wolfgang

Matthieu Baerts (matttbe) wrote :

Hello Wolfgang,

I'm sorry but I can't confirm it right now because my computer is under repair...
But I know that last week I was able to connect to my home wireless network and I still had an error like this one at startup:
   phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware

Matthieu Baerts, thank you for reporting this and helping make Ubuntu better. 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? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

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

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

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Matthieu Baerts (matttbe) wrote :

I'm sorry but I no longer have my laptop with this Ralink card.

@Wolfgang Kufner. Maybe can you confirm this bug report?

@Matthieu
I don't have access to a network with such an encryption, so I can't test this either.

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  Edit
Everyone can see this information.

Other bug subscribers