[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#700466: marked as done (firmware-ralink 0.36 breaks rt2800pci WPA2 ap association)

Your message dated Tue, 20 Oct 2015 22:26:44 +0100
with message-id <1445376404.10397.10.camel@decadent.org.uk>
and subject line Re: Update: seems to be kernel 3.2.0-0.bpo.4-686-pae
has caused the Debian Bug report #700466,
regarding firmware-ralink 0.36 breaks rt2800pci WPA2 ap association
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
700466: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700466
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: firmware-ralink
Version: 0.35~bpo60+1
Severity: important

After installing firmware-ralink_0.36+wheezy.1~bpo60+1_all.deb I was unable to
associate with my WPA2 AP.
Reinstalling 0.35 repaired this instantly.

lspci -nn:
02:00.0 Network controller [0280]: RaLink RT2860 [1814:0781]

Before loading the new firmware, I got:
root@akoya:~# dmesg|grep rt2
[   26.643154] rt2800pci 0000:02:00.0: setting latency timer to 64
[   26.671878] Registered led device: rt2800pci-phy0::radio
[   26.671997] Registered led device: rt2800pci-phy0::assoc
[   26.672188] Registered led device: rt2800pci-phy0::quality
[   31.637447] rt2800pci 0000:02:00.0: firmware: agent loaded rt2860.bin into memory
[   31.672771] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
[  447.032356] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
[  458.520359] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
[ 1958.056703] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
[ 2101.112893] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
[ 3561.048288] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware

-- System Information:
Debian Release: 6.0.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-0.bpo.4-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

firmware-ralink depends on no packages.

firmware-ralink recommends no packages.

Versions of packages firmware-ralink suggests:
ii  initramfs-tools         0.99~bpo60+1     tools for generating an initramfs
ii  linux-image-3.2.0-0.bpo 3.2.23-1~bpo60+2 Linux 3.2 for modern PCs
ii  linux-image-3.2.0-0.bpo 3.2.35-2~bpo60+1 Linux 3.2 for modern PCs

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Sun, 17 Feb 2013 21:08:33 +0100 Michael Kesper <mkesper@schokokeks.o
rg> wrote:
> Hi,
> 
> After furtherv testing with the old firmware version, I wasn't able to
> connect with kernel 3.2.0-0.bpo.4-686-pae at all.

There weren't any changes to the Ralink firmware between versions 0.35
and 0.36, so it's not surprising that the firmware package version
makes no difference.

> 3.2.0-0.bpo.3-686-pae works (at least with the old firmware version).
>
> How can I test further what's wrong here?

Sorry we didn't respond to this earlier.  I don't see any changes in
the rt2800usb driver between the 'working' and 'broken' versions that
would explain this, so I'm not sure this was really a bug here.

If you still have problems with the rt2800usb driver, please report a bug against 'kernel' - not against 'firmware-ralink'.

Ben.

-- 
Ben Hutchings
The first rule of tautology club is the first rule of tautology club.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: