148f:2573 Wifi cannot connect (regression), Ubuntu Raring

[Benjamin Geese]

I recently installed ubuntu 13.04 from the daily builds. My WiFi USB Stick is no longer working. My Wifi gets detected, i can enter my password however i do not get a connection. I borrowed another USB stick with another chipset and this works fine.
However, the Stick based on the RT73usb chipset worked flawless with ubuntu 12.04 and 12.10.

Steps to reproduce:
1) Disable all other wifi sticks/hardware
2) connect a wifi stick with rt73usb chipset
3) select your preffered wifi network with network-manager
4) enter your (wpa2) password
5) the system tries to connect but does not succed

I attached a syslog containing the events from trying to connect until it gives up.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-19-generic 3.8.0-19.29 [modified: boot/vmlinuz-3.8.0-19-generic]
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ben 1832 F.... pulseaudio
CRDA:
 country DE:
  (2400 - 2483 @ 40), (N/A, 20)
  (5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR
  (5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS
  (5470 - 5725 @ 40), (N/A, 26), DFS
Date: Wed Apr 24 18:52:24 2013
HibernationDevice: RESUME=UUID=43128468-05ec-49b2-a1e1-09b15c3af6ff
InstallationDate: Installed on 2013-04-24 (0 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1)
MachineType: System manufacturer P5Q-PRO
MarkForUpload: True
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=78db2cd0-107e-43d7-a168-4909c5b734cf ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-19-generic N/A
 linux-backports-modules-3.8.0-19-generic N/A
 linux-firmware 1.106
RfKill:
 1: phy1: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/23/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2102
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5Q-PRO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2102:bd02/23/2009:svnSystemmanufacturer:pnP5Q-PRO:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5Q-PRO
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.9 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-rc8-raring/

[Benjamin Geese (ben-8409)]

I am currently testing the mainline kernel. However it seems to me the error is related somehow to dhcp services or more complicated then i thought. Booting into Ubuntu today i suddenly had wifi access.

This is more detailed waht happened before i got the error:
1) Booted into 12.04, downloaded raring live amd64,. created a startup disk
2) Reboot directly from 12.04 to the startup disk and install 13.04 replacing 13.04
- Note: There is no wifi access in the installer. While the network is detected, no connection is possible in several tries.
3) Boot into the freshly installed Ubuntu, the error persists
- Note: See the logs attached above
4) Removing and reconnecting the stick does not help

This is what i have done before booting today, the WIFI suddenly works with the buggy USB Stick, which might be related to the mysterious fix:
a) Using another USB WIFI Adapter to post this bug.
b) Removing the other USB connector and reconnecting the old
c) Powering the computer off
d) Booting Windows and using the buggy adaptor for Wifi access (works fine)
e) Rebooting Ubuntu Raring.

This i

[frizzle21 (frederik-nnaji)]

i'm marking this as confirmed, since i can observe the same issue on a 32Bit 12.10 and also on 13.04 .
When i upgraded to 12.10 from 12.04, somehow the wireless adapter still happened to work.
Then i upgraded to 13.04 from 12.10, and it stopped working.
Subsequent attempts to do a fresh install of 13.04 or 12.10 on the same machine with the same configuration failed: the wifi device didn't even come up as in show me avaialble networks or anything in 13.04 .

I downgraded back to 12.10 and am now using an old android phone for wifi tethering via usb cable.
This is a definite regression.

[penalvch (penalvch)]

Benjamin Geese, 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 kernel in the mainline kernels archive directory daily 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.11-rc2

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

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

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.

[Launchpad Janitor (janitor)]

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