[Kernel-packages] [Bug 1022465] Re: rt73usb driver still buggy

2013-10-12 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1022465

Title:
  rt73usb driver still buggy

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  I can confirm, that the two different sticks I have with the same
  chipset, both fail in different machines, running 11.10 and now 12.04
  with 3.2.0-26 kernel. It loads the rt2x00usb, and does not yet use the
  hwcrypt option.

  WORKAROUND: Power Management: on

  The power option alone makes a difference:

  $ iwconfig wlan0 | grep Power
    Bit Rate=54 Mb/s   Tx-Power=20 dBm
    Power Management:off
  $ ping 192.168.116.200
  PING 192.168.116.200 (192.168.116.200) 56(84) bytes of data.
  64 bytes from 192.168.116.200: icmp_req=1 ttl=64 time=2.40 ms
  64 bytes from 192.168.116.200: icmp_req=2 ttl=64 time=2.40 ms
  64 bytes from 192.168.116.200: icmp_req=5 ttl=64 time=1.52 ms
  64 bytes from 192.168.116.200: icmp_req=6 ttl=64 time=1.90 ms
  64 bytes from 192.168.116.200: icmp_req=7 ttl=64 time=1.41 ms
  64 bytes from 192.168.116.200: icmp_req=8 ttl=64 time=1.51 ms
  64 bytes from 192.168.116.200: icmp_req=9 ttl=64 time=1.44 ms
  64 bytes from 192.168.116.200: icmp_req=10 ttl=64 time=1.14 ms
  64 bytes from 192.168.116.200: icmp_req=11 ttl=64 time=1.81 ms
  64 bytes from 192.168.116.200: icmp_req=12 ttl=64 time=1.53 ms
  $ sudo iwconfig wlan0 power on
  $ iwconfig wlan0 | grep Power
    Bit Rate=54 Mb/s   Tx-Power=20 dBm
    Power Management:on
  $ ping 192.168.116.200
  PING 192.168.116.200 (192.168.116.200) 56(84) bytes of data.
  64 bytes from 192.168.116.200: icmp_req=1 ttl=64 time=11.9 ms
  64 bytes from 192.168.116.200: icmp_req=2 ttl=64 time=1.75 ms
  64 bytes from 192.168.116.200: icmp_req=3 ttl=64 time=13.1 ms
  64 bytes from 192.168.116.200: icmp_req=4 ttl=64 time=122 ms
  64 bytes from 192.168.116.200: icmp_req=5 ttl=64 time=156 ms
  64 bytes from 192.168.116.200: icmp_req=6 ttl=64 time=54.6 ms
  64 bytes from 192.168.116.200: icmp_req=7 ttl=64 time=93.9 ms
  64 bytes from 192.168.116.200: icmp_req=8 ttl=64 time=1.62 ms
  64 bytes from 192.168.116.200: icmp_req=9 ttl=64 time=4.16 ms
  64 bytes from 192.168.116.200: icmp_req=10 ttl=64 time=13.5 ms
  64 bytes from 192.168.116.200: icmp_req=11 ttl=64 time=15.3 ms
  64 bytes from 192.168.116.200: icmp_req=12 ttl=64 time=11.8 ms
  $ sudo iwconfig wlan0 power off
  $ iwconfig wlan0 | grep Power
    Bit Rate=54 Mb/s   Tx-Power=20 dBm
    Power Management:off
  $ ping 192.168.116.200
  PING 192.168.116.200 (192.168.116.200) 56(84) bytes of data.
  64 bytes from 192.168.116.200: icmp_req=1 ttl=64 time=1.40 ms
  64 bytes from 192.168.116.200: icmp_req=2 ttl=64 time=1.26 ms
  64 bytes from 192.168.116.200: icmp_req=3 ttl=64 time=2.17 ms
  64 bytes from 192.168.116.200: icmp_req=4 ttl=64 time=1.93 ms
  64 bytes from 192.168.116.200: icmp_req=7 ttl=64 time=0.989 ms
  64 bytes from 192.168.116.200: icmp_req=9 ttl=64 time=3.52 ms
  64 bytes from 192.168.116.200: icmp_req=10 ttl=64 time=1.90 ms
  64 bytes from 192.168.116.200: icmp_req=13 ttl=64 time=1.69 ms

  The signal strength is relatively weak,
  Link Quality=32/70  Signal level=-78 dBm
  though the 100-s of milliseconds at times to the access point are 
characteristic. The ping times are in average 10 times slower with power 
on.Needless to say that the sticks work perfectly okay in Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-26-generic 3.2.0-26.41
  ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
  Uname: Linux 3.2.0-26-generic x86_64
  NonfreeKernelModules: fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  udippel2124 F pulseaudio
   /dev/snd/controlC0:  udippel2124 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Generic'/'HD-Audio Generic at 0xfef44000 irq 51'
     Mixer name : 'ATI R6xx HDMI'
     Components : 'HDA:1002aa01,00aa0100,00100200'
     Controls  : 6
     Simple ctrls  : 1
  Card0.Amixer.values:
   Simple mixer control 'IEC958',0
     Capabilities: pswitch pswitch-joined penum
     Playback channels: Mono
     Mono: Playback [on]
  Card1.Amixer.info:
   Card hw:1 'Generic_1'/'HD-Audio Generic at 0xfef4 irq 16'
     Mixer name : 'Realtek ALC887-VD'
     Components : 'HDA:10ec0887,1462d696,00100302'
     Controls  : 44
     Simple ctrls  : 21
  Date: Mon Jul  9 08:31:37 2012
  HibernationDevice: RESUME=UUID=edf6d61e-4333-4393-a3d4-2065aa129bda
  InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427)
  MachineType: MSI MS-7696
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   LANG=en

Re: [Kernel-packages] [Bug 1022465] Re: rt73usb driver still buggy

2013-08-13 Thread udippel
I am very sorry, I updated maybe a hundred BIOS before, always without any
problem (meaning, I know how to!). But when I had to update the BIOS of
this mainboard last time, I ended up with a brick. And then it was a costly
€ 30 expenditure to return to factory, and some 10 days without. I reckon
it was an MSI problem (since I joined the ranks of many more people bitten
likewise); and promised to myself never to try upgrading *this* mainboard
again.

So sorry,

Uwe


On Tue, Aug 13, 2013 at 3:17 AM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:

> udippel, as per http://us.msi.com/product/mb/A75MA-G55.html#/?div=BIOS
> an update is available for your BIOS (2.0). If you update to this, does
> it change anything?
>
> If not, could you please both specify what happened, and provide the
> output of the following terminal command:
> sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
>
> Please note your current BIOS is already in the Bug Description, so
> posting this on the old BIOS would not be helpful.
>
> Thank you for your understanding.
>
> ** Description changed:
>
> - This has been going on for years, reported a number of times, eg.
> - 773599, 812981 and quite some more. As far as I can see, mostly closed
> - for lack of activity.  (Though the lack of activity was not so much on
> - the side of the reporters.)
> -
> - I can confirm, that two sticks that I have, two different sticks, with
> - that same chipset, both fail in different machines, running 11.10 and
> - now 12.04 with 3.2.0-26 kernel.
> -
> - I don't say that this is all. It still load the rt2x00usb , which was
> - also considered a culprit in some reports and workarounds, and does not
> - yet use the hwcrypt option, but the power option alone makes a
> - difference:
> + I can confirm, that the two different sticks I have with the same
> + chipset, both fail in different machines, running 11.10 and now 12.04
> + with 3.2.0-26 kernel. It loads the rt2x00usb, and does not yet use the
> + hwcrypt option, but the power option alone makes a difference:
>
>   $ iwconfig wlan0 | grep Power
> Bit Rate=54 Mb/s   Tx-Power=20 dBm
> Power Management:off
>   $ ping 192.168.116.200
>   PING 192.168.116.200 (192.168.116.200) 56(84) bytes of data.
>   64 bytes from 192.168.116.200: icmp_req=1 ttl=64 time=2.40 ms
>   64 bytes from 192.168.116.200: icmp_req=2 ttl=64 time=2.40 ms
>   64 bytes from 192.168.116.200: icmp_req=5 ttl=64 time=1.52 ms
>   64 bytes from 192.168.116.200: icmp_req=6 ttl=64 time=1.90 ms
>   64 bytes from 192.168.116.200: icmp_req=7 ttl=64 time=1.41 ms
>   64 bytes from 192.168.116.200: icmp_req=8 ttl=64 time=1.51 ms
>   64 bytes from 192.168.116.200: icmp_req=9 ttl=64 time=1.44 ms
>   64 bytes from 192.168.116.200: icmp_req=10 ttl=64 time=1.14 ms
>   64 bytes from 192.168.116.200: icmp_req=11 ttl=64 time=1.81 ms
>   64 bytes from 192.168.116.200: icmp_req=12 ttl=64 time=1.53 ms
>   $ sudo iwconfig wlan0 power on
>   $ iwconfig wlan0 | grep Power
> Bit Rate=54 Mb/s   Tx-Power=20 dBm
> Power Management:on
>   $ ping 192.168.116.200
>   PING 192.168.116.200 (192.168.116.200) 56(84) bytes of data.
>   64 bytes from 192.168.116.200: icmp_req=1 ttl=64 time=11.9 ms
>   64 bytes from 192.168.116.200: icmp_req=2 ttl=64 time=1.75 ms
>   64 bytes from 192.168.116.200: icmp_req=3 ttl=64 time=13.1 ms
>   64 bytes from 192.168.116.200: icmp_req=4 ttl=64 time=122 ms
>   64 bytes from 192.168.116.200: icmp_req=5 ttl=64 time=156 ms
>   64 bytes from 192.168.116.200: icmp_req=6 ttl=64 time=54.6 ms
>   64 bytes from 192.168.116.200: icmp_req=7 ttl=64 time=93.9 ms
>   64 bytes from 192.168.116.200: icmp_req=8 ttl=64 time=1.62 ms
>   64 bytes from 192.168.116.200: icmp_req=9 ttl=64 time=4.16 ms
>   64 bytes from 192.168.116.200: icmp_req=10 ttl=64 time=13.5 ms
>   64 bytes from 192.168.116.200: icmp_req=11 ttl=64 time=15.3 ms
>   64 bytes from 192.168.116.200: icmp_req=12 ttl=64 time=11.8 ms
>   $ sudo iwconfig wlan0 power off
>   $ iwconfig wlan0 | grep Power
> Bit Rate=54 Mb/s   Tx-Power=20 dBm
> Power Management:off
>   $ ping 192.168.116.200
>   PING 192.168.116.200 (192.168.116.200) 56(84) bytes of data.
>   64 bytes from 192.168.116.200: icmp_req=1 ttl=64 time=1.40 ms
>   64 bytes from 192.168.116.200: icmp_req=2 ttl=64 time=1.26 ms
>   64 bytes from 192.168.116.200: icmp_req=3 ttl=64 time=2.17 ms
>   64 bytes from 192.168.116.200: icmp_req=4 ttl=64 time=1.93 ms
>   64 bytes from 192.168.116.200: icmp_req=7 ttl=64 time=0.989 ms
>   64 bytes from 192.168.116.200: icmp_req=9 ttl=64 time=3.52 ms
>   64 bytes from 192.168.116.200: icmp_req=10 ttl=64 time=1.90 ms
>   64 bytes from 192.168.116.200: icmp_req=13 ttl=64 time=1.69 ms
>
>   The signal strength is relatively weak,
>   Link Quality=32/70  Signal level=-78 dBm
> - though the 100-s of milliseconds at times to the access point are
> characteristic. The ping times are in average 10 times slowe

[Kernel-packages] [Bug 1022465] Re: rt73usb driver still buggy

2013-08-12 Thread Christopher M. Penalver
udippel, as per http://us.msi.com/product/mb/A75MA-G55.html#/?div=BIOS
an update is available for your BIOS (2.0). If you update to this, does
it change anything?

If not, could you please both specify what happened, and provide the output of 
the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Please note your current BIOS is already in the Bug Description, so
posting this on the old BIOS would not be helpful.

Thank you for your understanding.

** Description changed:

- This has been going on for years, reported a number of times, eg.
- 773599, 812981 and quite some more. As far as I can see, mostly closed
- for lack of activity.  (Though the lack of activity was not so much on
- the side of the reporters.)
- 
- I can confirm, that two sticks that I have, two different sticks, with
- that same chipset, both fail in different machines, running 11.10 and
- now 12.04 with 3.2.0-26 kernel.
- 
- I don't say that this is all. It still load the rt2x00usb , which was
- also considered a culprit in some reports and workarounds, and does not
- yet use the hwcrypt option, but the power option alone makes a
- difference:
+ I can confirm, that the two different sticks I have with the same
+ chipset, both fail in different machines, running 11.10 and now 12.04
+ with 3.2.0-26 kernel. It loads the rt2x00usb, and does not yet use the
+ hwcrypt option, but the power option alone makes a difference:
  
  $ iwconfig wlan0 | grep Power
    Bit Rate=54 Mb/s   Tx-Power=20 dBm
    Power Management:off
  $ ping 192.168.116.200
  PING 192.168.116.200 (192.168.116.200) 56(84) bytes of data.
  64 bytes from 192.168.116.200: icmp_req=1 ttl=64 time=2.40 ms
  64 bytes from 192.168.116.200: icmp_req=2 ttl=64 time=2.40 ms
  64 bytes from 192.168.116.200: icmp_req=5 ttl=64 time=1.52 ms
  64 bytes from 192.168.116.200: icmp_req=6 ttl=64 time=1.90 ms
  64 bytes from 192.168.116.200: icmp_req=7 ttl=64 time=1.41 ms
  64 bytes from 192.168.116.200: icmp_req=8 ttl=64 time=1.51 ms
  64 bytes from 192.168.116.200: icmp_req=9 ttl=64 time=1.44 ms
  64 bytes from 192.168.116.200: icmp_req=10 ttl=64 time=1.14 ms
  64 bytes from 192.168.116.200: icmp_req=11 ttl=64 time=1.81 ms
  64 bytes from 192.168.116.200: icmp_req=12 ttl=64 time=1.53 ms
  $ sudo iwconfig wlan0 power on
  $ iwconfig wlan0 | grep Power
    Bit Rate=54 Mb/s   Tx-Power=20 dBm
    Power Management:on
  $ ping 192.168.116.200
  PING 192.168.116.200 (192.168.116.200) 56(84) bytes of data.
  64 bytes from 192.168.116.200: icmp_req=1 ttl=64 time=11.9 ms
  64 bytes from 192.168.116.200: icmp_req=2 ttl=64 time=1.75 ms
  64 bytes from 192.168.116.200: icmp_req=3 ttl=64 time=13.1 ms
  64 bytes from 192.168.116.200: icmp_req=4 ttl=64 time=122 ms
  64 bytes from 192.168.116.200: icmp_req=5 ttl=64 time=156 ms
  64 bytes from 192.168.116.200: icmp_req=6 ttl=64 time=54.6 ms
  64 bytes from 192.168.116.200: icmp_req=7 ttl=64 time=93.9 ms
  64 bytes from 192.168.116.200: icmp_req=8 ttl=64 time=1.62 ms
  64 bytes from 192.168.116.200: icmp_req=9 ttl=64 time=4.16 ms
  64 bytes from 192.168.116.200: icmp_req=10 ttl=64 time=13.5 ms
  64 bytes from 192.168.116.200: icmp_req=11 ttl=64 time=15.3 ms
  64 bytes from 192.168.116.200: icmp_req=12 ttl=64 time=11.8 ms
  $ sudo iwconfig wlan0 power off
  $ iwconfig wlan0 | grep Power
    Bit Rate=54 Mb/s   Tx-Power=20 dBm
    Power Management:off
  $ ping 192.168.116.200
  PING 192.168.116.200 (192.168.116.200) 56(84) bytes of data.
  64 bytes from 192.168.116.200: icmp_req=1 ttl=64 time=1.40 ms
  64 bytes from 192.168.116.200: icmp_req=2 ttl=64 time=1.26 ms
  64 bytes from 192.168.116.200: icmp_req=3 ttl=64 time=2.17 ms
  64 bytes from 192.168.116.200: icmp_req=4 ttl=64 time=1.93 ms
  64 bytes from 192.168.116.200: icmp_req=7 ttl=64 time=0.989 ms
  64 bytes from 192.168.116.200: icmp_req=9 ttl=64 time=3.52 ms
  64 bytes from 192.168.116.200: icmp_req=10 ttl=64 time=1.90 ms
  64 bytes from 192.168.116.200: icmp_req=13 ttl=64 time=1.69 ms
  
  The signal strength is relatively weak,
  Link Quality=32/70  Signal level=-78 dBm
- though the 100-s of milliseconds at times to the access point are 
characteristic. The ping times are in average 10 times slower with power on.
- Still, I don't say that this is *the* workaround. I gathered it from some 
other, unfortunately abandoned, bug reports with other work-arounds. Needless 
to say that the sticks work perfectly okay in Windows.
+ though the 100-s of milliseconds at times to the access point are 
characteristic. The ping times are in average 10 times slower with power 
on.Needless to say that the sticks work perfectly okay in Windows.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-26-generic 3.2.0-26.41
  ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
  Uname: Linux 3.2.0-26-generic x86_64
  NonfreeKernelModules: fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Ve