[Bug 996523] Re: After resuming from suspend, NEW wireless networks cannot connect
** Tags removed: needs-upstream-testing ** Tags added: kernel-unable-to-test-upstream ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed ** Summary changed: - After resuming from suspend, NEW wireless networks cannot connect + 14e4:4727 After resuming from suspend, NEW wireless networks cannot connect -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996523 Title: 14e4:4727 After resuming from suspend, NEW wireless networks cannot connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/996523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996523] Re: After resuming from suspend, NEW wireless networks cannot connect
I tried installing that particular image .deb, and after reboot, my system seemed to have loaded into recovery mode, as though the kernel would not boot. Could I have possibly done something wrong? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996523 Title: After resuming from suspend, NEW wireless networks cannot connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/996523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996523] Re: After resuming from suspend, NEW wireless networks cannot connect
I am still experiencing this problem. I would like to test the latest upstream kernel, as jsalisbury suggested, but no one has responded to my question requesting clarification about how to do this. ** Changed in: linux (Ubuntu) Status: Expired = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996523 Title: After resuming from suspend, NEW wireless networks cannot connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/996523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996523] Re: After resuming from suspend, NEW wireless networks cannot connect
** Changed in: linux (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996523 Title: After resuming from suspend, NEW wireless networks cannot connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/996523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996523] Re: After resuming from suspend, NEW wireless networks cannot connect
Daygan, you are correct in that not enough files exist in that kernel directory for you to make a test. Instead, could you please try http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-rc7-quantal/ ? ** Description changed: After I resume my session from a suspended mode, when attempting to connect to a wireless network that was not the network that I was connected to most recently before suspending, the system is unable to connect, despite the fact that the presence of the network is recognized. This may be the same bug as this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/665837 , but I have specifically noticed that in my case, I can connect to the network that I was previously connected to, but not other networks. I will have to check again to see if, in fact, I am able to connect to ALL networks that I had previously connected to before suspend, or only the one that I had most recently connected to. - --- + --- 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 + List of PLAYBACK Hardware Devices + card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog] + Subdevices: 1/1 + Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 ArecordDevices: - List of CAPTURE Hardware Devices - card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog] -Subdevices: 1/1 -Subdevice #0: subdevice #0 + List of CAPTURE Hardware Devices + card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog] + Subdevices: 1/1 + Subdevice #0: subdevice #0 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: daygan 1935 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: daygan 1935 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: - Card hw:0 'Intel'/'HDA Intel at 0xf7cf8000 irq 44' -Mixer name : 'Realtek ALC269VB' -Components : 'HDA:10ec0269,1043841c,00100100' -Controls : 16 -Simple ctrls : 9 + Card hw:0 'Intel'/'HDA Intel at 0xf7cf8000 irq 44' + Mixer name : 'Realtek ALC269VB' + Components : 'HDA:10ec0269,1043841c,00100100' + Controls : 16 + Simple ctrls : 9 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=a3bbe0a8-e040-4edc-8040-75b1f45914ae InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) MachineType: ASUSTeK Computer INC. 1015PW NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic root=UUID=e4bc0974-4a1b-4b8a-b447-0b452afca786 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 RelatedPackageVersions: - linux-restricted-modules-3.2.0-24-generic N/A - linux-backports-modules-3.2.0-24-generic N/A - linux-firmware1.79 + linux-restricted-modules-3.2.0-24-generic N/A + linux-backports-modules-3.2.0-24-generic N/A + linux-firmware1.79 SourcePackage: linux Tags: precise precise Uname: Linux 3.2.0-24-generic x86_64 UpgradeStatus: Upgraded to precise on 2012-04-28 (9 days ago) UserGroups: adm admin cdrom dialout lpadmin nopasswdlogin plugdev sambashare dmi.bios.date: 05/06/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1015PE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd05/06/2011:svnASUSTeKComputerINC.:pn1015PW:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1015PW dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. - --- - 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: 2.0.1-0ubuntu7 - Architecture: amd64 - 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: - USERPID ACCESS COMMAND - /dev/snd/controlC0: daygan 1935 F pulseaudio - CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. - Card0.Amixer.info: - Card hw:0 'Intel'/'HDA Intel at 0xf7cf8000 irq 44' -Mixer
[Bug 996523] Re: After resuming from suspend, NEW wireless networks cannot connect
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996523 Title: After resuming from suspend, NEW wireless networks cannot connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/996523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996523] Re: After resuming from suspend, NEW wireless networks cannot connect
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-rc7-precise/ ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** Tags added: needs-upstream-testing ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996523 Title: After resuming from suspend, NEW wireless networks cannot connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/996523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996523] Re: After resuming from suspend, NEW wireless networks cannot connect
I'm confused. I don't see any specific file in the link that you provided that says anything about a kernel. Yes, the directory is under ~kernel-ppa, but the file doesn't seem to be a kernel file. I only see what looks to me like a headers file. The https://wiki.ubuntu.com/KernelMainlineBuilds page explains that to install mainline kernels, one installs the *image*.deb file, but I am only finding *image*.deb files in the daily directory, which you're suggesting I not use. Can I get some clarification? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996523 Title: After resuming from suspend, NEW wireless networks cannot connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/996523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996523] Re: After resuming from suspend, NEW wireless networks cannot connect
** Attachment added: dmesg output from a recent instance in which wireless networks would not connect https://bugs.launchpad.net/ubuntu/+source/linux/+bug/996523/+attachment/3143721/+files/dmesg_wireless_notconnecting -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996523 Title: After resuming from suspend, NEW wireless networks cannot connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/996523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996523] Re: After resuming from suspend, NEW wireless networks cannot connect
** Attachment added: dmesg output from a recent instance in which wired network would not connect (in fact it was not even recognized, despite the fact the the broadband wire was physically connected to the computer) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/996523/+attachment/3143724/+files/wire-connection-malfunction -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996523 Title: After resuming from suspend, NEW wireless networks cannot connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/996523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996523] Re: After resuming from suspend, NEW wireless networks cannot connect
I have discovered that the same problem occurs with wired connection after resuming from suspend. If I had previously been using a wireless connection before suspending, after resuming from suspend, connected wired connections are not recognized. ** Changed in: linux (Ubuntu) Status: Incomplete = Opinion ** Changed in: linux (Ubuntu) Status: Opinion = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996523 Title: After resuming from suspend, NEW wireless networks cannot connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/996523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996523] Re: After resuming from suspend, NEW wireless networks cannot connect
Also, the ability/inability to connect to wireless networks that were not connected before suspending seems inconsistent. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996523 Title: After resuming from suspend, NEW wireless networks cannot connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/996523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996523] Re: After resuming from suspend, NEW wireless networks cannot connect
** Attachment added: dmesg1 https://bugs.launchpad.net/bugs/996523/+attachment/3136773/+files/dmesg1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996523 Title: After resuming from suspend, NEW wireless networks cannot connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/996523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996523] Re: After resuming from suspend, NEW wireless networks cannot connect
apport information ** Tags added: apport-collected ** Description changed: - After I resume my session from a suspended mode, when attempting to - connect to a wireless network that was not the network that I was - connected to most recently before suspending, the system is unable to - connect, despite the fact that the presence of the network is - recognized. This may be the same bug as this: - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/665837 , but I have - specifically noticed that in my case, I can connect to the network that - I was previously connected to, but not other networks. I will have to - check again to see if, in fact, I am able to connect to ALL networks - that I had previously connected to before suspend, or only the one that - I had most recently connected to. + After I resume my session from a suspended mode, when attempting to connect to a wireless network that was not the network that I was connected to most recently before suspending, the system is unable to connect, despite the fact that the presence of the network is recognized. This may be the same bug as this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/665837 , but I have specifically noticed that in my case, I can connect to the network that I was previously connected to, but not other networks. I will have to check again to see if, in fact, I am able to connect to ALL networks that I had previously connected to before suspend, or only the one that I had most recently connected to. + --- + 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: 2.0.1-0ubuntu7 + Architecture: amd64 + 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: + USERPID ACCESS COMMAND + /dev/snd/controlC0: daygan 1935 F pulseaudio + CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. + Card0.Amixer.info: + Card hw:0 'Intel'/'HDA Intel at 0xf7cf8000 irq 44' +Mixer name : 'Realtek ALC269VB' +Components : 'HDA:10ec0269,1043841c,00100100' +Controls : 16 +Simple ctrls : 9 + DistroRelease: Ubuntu 12.04 + HibernationDevice: RESUME=UUID=a3bbe0a8-e040-4edc-8040-75b1f45914ae + InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) + MachineType: ASUSTeK Computer INC. 1015PW + NonfreeKernelModules: wl + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic root=UUID=e4bc0974-4a1b-4b8a-b447-0b452afca786 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 + RelatedPackageVersions: + linux-restricted-modules-3.2.0-24-generic N/A + linux-backports-modules-3.2.0-24-generic N/A + linux-firmware1.79 + SourcePackage: linux + Tags: precise precise + Uname: Linux 3.2.0-24-generic x86_64 + UpgradeStatus: Upgraded to precise on 2012-04-28 (9 days ago) + UserGroups: adm admin cdrom dialout lpadmin nopasswdlogin plugdev sambashare + dmi.bios.date: 05/06/2011 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 1301 + dmi.board.asset.tag: To Be Filled By O.E.M. + dmi.board.name: 1015PE + dmi.board.vendor: ASUSTeK Computer INC. + dmi.board.version: x.xx + dmi.chassis.asset.tag: 0x + dmi.chassis.type: 10 + dmi.chassis.vendor: ASUSTeK Computer INC. + dmi.chassis.version: x.x + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd05/06/2011:svnASUSTeKComputerINC.:pn1015PW:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: + dmi.product.name: 1015PW + dmi.product.version: x.x + dmi.sys.vendor: ASUSTeK Computer INC. ** Attachment added: AcpiTables.txt https://bugs.launchpad.net/bugs/996523/+attachment/3136960/+files/AcpiTables.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996523 Title: After resuming from suspend, NEW wireless networks cannot connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/996523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996523] Re: After resuming from suspend, NEW wireless networks cannot connect
I apologize for multiple reports. On my end, it looked at if apport had not finished and was stuck in a refresh-page mode before posting results and allowing me to send, so I canceled and re-issued the command a couple times. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996523 Title: After resuming from suspend, NEW wireless networks cannot connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/996523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
