Wifi Not working

[Jānis Kangarooo]

Wifi Not working
None networks showing up
This didnt happened in 1.march Beta-1 so its regresion since March 1

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-19-generic-pae 3.2.0-19.30
ProcVersionSignature: Ubuntu 3.2.0-19.30-generic-pae 3.2.11
Uname: Linux 3.2.0-19-generic-pae i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 4153 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf7df8000 irq 43'
   Mixer name : 'Realtek ALC269VB'
   Components : 'HDA:10ec0269,104384d3,00100100'
   Controls : 12
   Simple ctrls : 7
CasperVersion: 1.311
Date: Mon Mar 19 12:21:15 2012
LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120319)
MachineType: ASUSTeK Computer INC. X101
ProcEnviron:
 TERM=xterm
 LANG=lv_LV.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- debian-installer/language=lv keyboard-configuration/layoutcode?=lv
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-19-generic-pae N/A
 linux-backports-modules-3.2.0-19-generic-pae N/A
 linux-firmware 1.71
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/17/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0502
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: X101
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0502:bd10/17/2011:svnASUSTeKComputerINC.:pnX101:pvrx.x:rvnASUSTeKComputerINC.:rnX101:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
dmi.product.name: X101
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

[Joseph Salisbury (jsalisbury)]

@Kangarooo

Can you boot back into the prior Ubuntu kernel(3.2.0-18) and see if the issue goes away?

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[vonibenz (vonibenz)]

The problem was ALREADY PRESENT on previous version (Ubuntu 10.10, Ubuntu 11.04, Ubuntu 11.10) and, from my point of view, the bug is into the NetworkManager in the filesystem. In my case the WiFi card is a Ralink rt3090, perfectly working in Windows (and one time in the old Ubuntu 10.04). The driver is installed and mainteined (!) by Canonical, but now Ubuntu is unable to find, relieve, any wifi signal.

[Thijs Triemstra (collab)]

Upgrading to the lastest kernel doesn't make a difference as suggested in comment 3. Works fine under windows7, broken in 12.04 but was working pretty well in 11.10.

[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.4kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). 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.

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.

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc4-precise/

[Jānis Kangarooo (kangarooo)]

All is fixed in 12.04 all works.