Bug#598144: rt2500pci: very low transfers and link quality
Package: linux-2.6
Version: 2.6.32-20
Severity: important
File: rt2500pci
Hi all,
I have been using rt2500pci since rt2500 legacy drivers source package
dissapeared from the repository, and I have had this problems from the first
time until now. The legacy drivers worked fine, but with the new ones I have
very low transfers and poor link quality. I thought this problem was solved,
but for me still exists.
Greetings, David.
-- Package-specific info:
** Version:
Linux version 2.6.32-5-686 (Debian 2.6.32-20) (ben@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-2) ) #1 SMP Thu Aug 12 13:38:27 UTC 2010
** Tainted: P (1)
* Proprietary module has been loaded.
** Kernel log:
[10537.181030] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10537.512052] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10539.660055] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10539.969081] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10542.072051] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10542.336048] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10542.632048] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10543.173052] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10543.556108] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10544.928059] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10545.396062] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10546.217049] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10546.480060] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10548.188052] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10548.468071] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10549.280053] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10554.316065] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10555.412052] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10558.956067] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10559.220132] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10560.432084] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10561.532059] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10564.240074] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10564.420051] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10565.564065] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10568.672064] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10570.688060] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10570.996051] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10572.329044] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10578.072048] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10583.201038] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10586.356047] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10586.764053] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10589.324059] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10590.336075] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10594.416052] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10594.752072] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10595.044045] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10595.356057] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10596.948039] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10597.448031] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10600.080070] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10600.896048] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10601.512050] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10601.921060] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10603.040061] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10603.576045] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10605.588048] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10610.053048] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10610.688052] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10612.056057] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10612.365051] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10612.720056] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10613.169062] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10617.841046] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10618.204052] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10619.121054] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10619.534112] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10625.104058] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10630.000093] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10630.696073] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10631.106868] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10632.092040] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10636.534037] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10637.133049] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10638.172042] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10639.232046] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10641.244043] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10646.356044] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10648.381437] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10653.508054] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10659.644044] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10660.800041] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10664.664041] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10666.768043] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10668.140039] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10670.064048] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10671.800045] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10673.904041] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10675.924045] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10678.092042] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10678.312041] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10678.960046] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10679.236045] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10681.028043] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10683.056044] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10686.096055] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10688.168029] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10690.500045] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10690.636037] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10691.012041] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10698.048040] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10699.304043] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10700.401021] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10705.424049] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10711.528054] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10715.560053] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10717.124059] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10717.668068] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
[10724.772043] phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
** Network interface configuration:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
*** Protocol statistics:
Ip:
477362 total packets received
0 forwarded
0 incoming packets discarded
477271 incoming packets delivered
300309 requests sent out
80 outgoing packets dropped
Icmp:
80 ICMP messages received
0 input ICMP message failed.
ICMP input histogram:
destination unreachable: 80
84 ICMP messages sent
0 ICMP messages failed
ICMP output histogram:
destination unreachable: 84
IcmpMsg:
InType3: 80
OutType3: 84
Tcp:
1156 active connections openings
0 passive connection openings
12 failed connection attempts
41 connection resets received
5 connections established
442282 segments received
263694 segments send out
742 segments retransmited
0 bad segments received.
214 resets sent
Udp:
34904 packets received
84 packets to unknown port received.
0 packet receive errors
35789 packets sent
UdpLite:
TcpExt:
14 packets pruned from receive queue because of socket buffer overrun
379 TCP sockets finished time wait in fast timer
2 time wait sockets recycled by time stamp
2762 delayed acks sent
3 delayed acks further delayed because of locked socket
Quick ack mode was activated 497 times
325313 packets directly queued to recvmsg prequeue.
1448 bytes directly in process context from backlog
356196126 bytes directly received in process context from prequeue
130062 packet headers predicted
236377 packets header predicted and directly queued to user
3275 acknowledgments not containing data payload received
644 predicted acknowledgments
125 congestion windows recovered without slow start after partial ack
1 timeouts after reno fast retransmit
37 timeouts after SACK recovery
11 timeouts in loss state
18 retransmits in slow start
470 other TCP timeouts
734 packets collapsed in receive queue due to low socket buffer
481 DSACKs sent for old packets
34 DSACKs received
47 connections reset due to unexpected data
9 connections reset due to early user close
13 connections aborted due to timeout
TCPDSACKIgnoredOld: 9
TCPDSACKIgnoredNoUndo: 11
TCPSackShiftFallback: 24
IpExt:
InMcastPkts: 9
OutMcastPkts: 11
InBcastPkts: 78
OutBcastPkts: 77
InOctets: 641165138
OutOctets: 21779450
InMcastOctets: 2573
OutMcastOctets: 2653
InBcastOctets: 14152
OutBcastOctets: 13820
** USB devices:
Bus 002 Device 003: ID 08ff:2580 AuthenTec, Inc. AES2501 Fingerprint Sensor
Bus 002 Device 002: ID 046d:c019 Logitech, Inc. Optical Tilt Wheel Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-image-2.6.32-5-686 depends on:
ii debconf [debconf-2.0] 1.5.35 Debian configuration management sy
ii initramfs-tools [linux-initra 0.98.3 tools for generating an initramfs
ii linux-base 2.6.32-23 Linux image base package
ii module-init-tools 3.12-1 tools for managing Linux kernel mo
Versions of packages linux-image-2.6.32-5-686 recommends:
ii firmware-linux-free 2.6.32-23 Binary firmware for various driver
ii libc6-i686 2.11.2-6 Embedded GNU C Library: Shared lib
Versions of packages linux-image-2.6.32-5-686 suggests:
ii grub 0.97-56 GRand Unified Bootloader (dummy pa
ii grub-legacy [grub] 0.97-63 GRand Unified Bootloader (Legacy v
pn linux-doc-2.6.32 <none> (no description available)
Versions of packages linux-image-2.6.32-5-686 is related to:
pn firmware-bnx2 <none> (no description available)
pn firmware-bnx2x <none> (no description available)
pn firmware-ipw2x00 <none> (no description available)
pn firmware-ivtv <none> (no description available)
pn firmware-iwlwifi <none> (no description available)
ii firmware-linux 0.26 Binary firmware for various driver
ii firmware-linux-nonfree 0.26 Binary firmware for various driver
pn firmware-qlogic <none> (no description available)
ii firmware-ralink 0.26 Binary firmware for Ralink wireles
pn xen-hypervisor <none> (no description available)
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100926203325.8583.75263.reportbug@krusty-deb2.mundo-R.com">http://lists.debian.org/20100926203325.8583.75263.reportbug@krusty-deb2.mundo-R.com
09-26-2010, 08:50 PM
Ben Hutchings
Bug#598144: rt2500pci: very low transfers and link quality
On Sun, 2010-09-26 at 22:33 +0200, David Sánchez Herrero wrote:
> Package: linux-2.6
> Version: 2.6.32-20
> Severity: important
> File: rt2500pci
>
> Hi all,
>
> I have been using rt2500pci since rt2500 legacy drivers source package
> dissapeared from the repository, and I have had this problems from the first
> time until now. The legacy drivers worked fine, but with the new ones I have
> very low transfers and poor link quality. I thought this problem was solved,
> but for me still exists.
Please test Linux 2.6.35 as packaged in experimental. If this isn't any
better, please send a bug report to linux-wireless@vger.kernel.org and
cc the bug address 598144@bugs.debian.org .
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
09-27-2010, 05:03 PM
David Sanchez Herrero
Bug#598144: rt2500pci: very low transfers and link quality
Hi again,
I need to compile the graphics card drivers (Nvidia) and I can't find headers for 2.6.35 kernel in the repository (deb http://ftp.debian.org/debian experimental main).
Instead, I install linux-image-2.6.36-rc5-686, that has header packages available, but I can't install header packages because a dependency error:
Se instalarán los siguiente paquetes NUEVOS:****
* linux-headers-2.6.36-rc5-686{b} linux-headers-2.6.36-rc5-common{a}
0 paquetes actualizados, 2 nuevos instalados, 0 para eliminar y 230 sin actualizar.
Necesito descargar 4691kB de ficheros. Después de desempaquetar se usarán 29,9MB.
No se satisfacen las dependencias de los siguientes paquetes:
* linux-headers-2.6.36-rc5-686: Depende: linux-kbuild-2.6.36 que es un paquete virtual.
Las acciones siguientes resolverán estas dependencias
**** Mantener los paquetes siguientes en la versión actual:
El 26 de septiembre de 2010 22:50, Ben Hutchings <ben@decadent.org.uk> escribió:
On Sun, 2010-09-26 at 22:33 +0200, David Sánchez Herrero wrote:
> Package: linux-2.6
> Version: 2.6.32-20
> Severity: important
> File: rt2500pci
>
> Hi all,
>
> I have been using rt2500pci since rt2500 legacy drivers source package
> dissapeared from the repository, and I have had this problems from the first
> time until now. The legacy drivers worked fine, but with the new ones I have
> very low transfers and poor link quality. I thought this problem was solved,
> but for me still exists.
Please test Linux 2.6.35 as packaged in experimental. *If this isn't any
better, please send a bug report to linux-wireless@vger.kernel.org and
cc the bug address 598144@bugs.debian.org .
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
09-28-2010, 01:14 AM
Ben Hutchings
Bug#598144: rt2500pci: very low transfers and link quality
On Mon, 2010-09-27 at 19:03 +0200, David Sanchez Herrero wrote:
> Hi again,
>
> I need to compile the graphics card drivers (Nvidia) and I can't find
> headers for 2.6.35 kernel in the repository (deb
> http://ftp.debian.org/debian experimental main).
>
> Instead, I install linux-image-2.6.36-rc5-686, that has header
> packages available,
Right, that was just accepted into experimental.
> but I can't install header packages because a dependency error:
[...]
> what can I do??
You can live without the nvidia driver briefly, can't you?
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
09-28-2010, 07:50 AM
David Sanchez Herrero
Bug#598144: rt2500pci: very low transfers and link quality
Hi,
My idea was to test with NetworkManager and try to download some files, etc., but I think I can do some tests without graphic enviroment. Between this afternoon and tomorrow night I'm going to try it, and I'll tell you.
Greetings.
2010/9/28 Ben Hutchings <ben@decadent.org.uk>
On Mon, 2010-09-27 at 19:03 +0200, David Sanchez Herrero wrote:
> Hi again,
>
> I need to compile the graphics card drivers (Nvidia) and I can't find
> headers for 2.6.35 kernel in the repository (deb
> Instead, I install linux-image-2.6.36-rc5-686, that has header
> packages available,
Right, that was just accepted into experimental.
> but I can't install header packages because a dependency error:
[...]
> what can I do??
You can live without the nvidia driver briefly, can't you?
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
09-29-2010, 04:52 PM
David Sanchez Herrero
Bug#598144: rt2500pci: very low transfers and link quality
Hi again,
After some troubles that I could solve, I connected the interface, but it's impossible to make anything because in all terminals appears one message continously:
cfg80211: Calling CRDA to update world regulatory domain.
I can see that I lose the connection, probably because this message. This happens with 2.6.36-rc5-686 kernel. Any idea about solving this problem?
This problem doesn't exists with 2.6.32-5-686 kernel, but with it, I have again the error message that appears in my first report:
phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
In this case I don't lose the connection to the AP, but the link quality and transfers speed are still low.
2010/9/28 David Sanchez Herrero <david.krusty@gmail.com>
Hi,
My idea was to test with NetworkManager and try to download some files, etc., but I think I can do some tests without graphic enviroment. Between this afternoon and tomorrow night I'm going to try it, and I'll tell you.
Greetings.
2010/9/28 Ben Hutchings <ben@decadent.org.uk>
On Mon, 2010-09-27 at 19:03 +0200, David Sanchez Herrero wrote:
> Hi again,
>
> I need to compile the graphics card drivers (Nvidia) and I can't find
> headers for 2.6.35 kernel in the repository (deb
> Instead, I install linux-image-2.6.36-rc5-686, that has header
> packages available,
Right, that was just accepted into experimental.
> but I can't install header packages because a dependency error:
[...]
> what can I do??
You can live without the nvidia driver briefly, can't you?
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
10-01-2010, 02:52 AM
Ben Hutchings
Bug#598144: rt2500pci: very low transfers and link quality
On Wed, 2010-09-29 at 18:52 +0200, David Sanchez Herrero wrote:
> Hi again,
>
> After some troubles that I could solve, I connected the interface, but
> it's impossible to make anything because in all terminals appears one
> message continously:
>
> cfg80211: Calling CRDA to update world regulatory domain.
>
> I can see that I lose the connection, probably because this message.
> This happens with 2.6.36-rc5-686 kernel. Any idea about solving this
> problem?
No, but the developers on linux-wireless may be able to help.
Ben.
> This problem doesn't exists with 2.6.32-5-686 kernel, but with it, I
> have again the error message that appears in my first report:
>
> phy0 -> rt2500pci_set_device_state: Error - Device failed to enter
> state 1 (-16).
>
> In this case I don't lose the connection to the AP, but the link
> quality and transfers speed are still low.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
12-03-2011, 06:19 AM
Jonathan Nieder
Bug#598144: rt2500pci: very low transfers and link quality
# forwarded last year:
# http://thread.gmane.org/gmane.linux.kernel.wireless.general/56714
# no response, so let's try again.
notforwarded 598144
quit
Heya,
Regarding version 2.6.32-20, David Sánchez Herrero wrote:
> I have been using rt2500pci since rt2500 legacy drivers source package
> dissapeared from the repository, and I have had this problems from the first
> time until now. The legacy drivers worked fine, but with the new ones I have
> very low transfers and poor link quality.
That's no good. So let's see.
[...]
> it's
> impossible to make anything because in all terminals appears one message
> continously:
>
> cfg80211: Calling CRDA to update world regulatory domain.
>
> I can see that I lose the connection, probably because this message. This
> happens with 2.6.36-rc5-686 kernel. Any idea about solving this problem?
Very odd. Does it still happen?
[...]
> This problem doesn't exists with 2.6.32-5-686 kernel, but with it, I
> have again the error message that appears in my first report:
>
> phy0 -> rt2500pci_set_device_state: Error - Device failed to enter state 1 (-16).
Which kernel version is that? You can get the currently running
kernel version by running "cat /proc/version" and looking for the
string in parentheses.
I don't see any relevant fixes upstream (amazingly, since the driver
has had a lot of work done). If you can get a chance to test a 3.1.y
or later kernel from sid, that would be very helpful. (Then we can
get help from upstream.) For graphics, while testing you can use the
vesa driver or nouveau.
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20111203071919.GA18684@elie.hsd1.il.comcast.net">h ttp://lists.debian.org/20111203071919.GA18684@elie.hsd1.il.comcast.net
12-05-2011, 08:28 AM
David Sanchez Herrero
Bug#598144: rt2500pci: very low transfers and link quality
Hi Jonathan,
Thanks for reply about this problem, but the laptop with rt2500 wireless card died 6 or 7 months ago (a graphic card crash), so I can't try the 3.1 kernel version. I think that after a lot of tests (compiling a new module version using compat-wireless project, compiling the drivers from Ralink, updating the kernel version, disabling Network-Manager to manually configure the card, ...), I finally got the wireless card working fine, but now I can't remember which was the final solution to the problem.
I'm sure that there was something bad with the rt2500pci module because I found a lot of information about the problem, associated to different distros, and I could verify with a Live CD that the problem was in Ubuntu too.
I'm thinking about analyze the laptop hard disk this Christmas to recover some files to my new computer, so if I find some information about the solutión that I applied, I promise to write again to tell you.
Meanwhile, I think that you can mark this bug as solved if you want.
Greetings, David.
El 3 de diciembre de 2011 08:19, Jonathan Nieder <jrnieder@gmail.com> escribió:
Bug#598144: rt2500pci: very low transfers and link quality
Hi again,
Finally, after analyzing my laptop's hard disk, I have remembered the final solution, that was using Ndiswrapper with rt2500 Windows drivers. It was the only way...
Greetings, David.
2011/12/5 David Sanchez Herrero <david.krusty@gmail.com>
Hi Jonathan,
Thanks for reply about this problem, but the laptop with rt2500 wireless card died 6 or 7 months ago (a graphic card crash), so I can't try the 3.1 kernel version. I think that after a lot of tests (compiling a new module version using compat-wireless project, compiling the drivers from Ralink, updating the kernel version, disabling Network-Manager to manually configure the card, ...), I finally got the wireless card working fine, but now I can't remember which was the final solution to the problem.
I'm sure that there was something bad with the rt2500pci module because I found a lot of information about the problem, associated to different distros, and I could verify with a Live CD that the problem was in Ubuntu too.
I'm thinking about analyze the laptop hard disk this Christmas to recover some files to my new computer, so if I find some information about the solutión that I applied, I promise to write again to tell you.
Meanwhile, I think that you can mark this bug as solved if you want.
Greetings, David.
El 3 de diciembre de 2011 08:19, Jonathan Nieder <jrnieder@gmail.com> escribió: