168c:001c Wireless won't stay connected

[Richard]

The wireless network asks me to login every 5-10 seconds. I am between two bridged routers and it could be hunting between them. Th connects was fine with the build of 15 days ago. I am running 12.04 beta.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: richard 1540 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf0340000 irq 43'
   Mixer name : 'Realtek ALC272'
   Components : 'HDA:10ec0272,144dca00,00100001'
   Controls : 20
   Simple ctrls : 11
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=3f9b9920-445b-4de4-8f20-168a3c9c2e16
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413)
IwConfig: Error: [Errno 2] No such file or directory
MachineType: SAMSUNG ELECTRONICS CO., LTD. NC10
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic root=UUID=7151a165-3dd6-483e-96f4-a2106df0b470 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-firmware 1.79
RfKill: Error: [Errno 2] No such file or directory
SourcePackage: linux
Tags: precise precise
UdevDb: Error: [Errno 2] No such file or directory
Uname: Linux 3.2.0-24-generic i686
UpgradeStatus: Upgraded to precise on 2012-02-27 (66 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 11/25/2008
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 03CA.MP00.20081125.KTW
dmi.board.name: NC10
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: None
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: No Asset Tag
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr03CA.MP00.20081125.KTW:bd11/25/2008:svnSAMSUNGELECTRONICSCO.,LTD.:pnNC10:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNC10:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrNoAssetTag:
dmi.product.name: NC10
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/978340/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 978340

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Richard (w0h0i-2ic6a7y-p7k1q)]

apport information

[Richard (w0h0i-2ic6a7y-p7k1q)]

apport information

[Richard (w0h0i-2ic6a7y-p7k1q)]

apport information

[Richard (w0h0i-2ic6a7y-p7k1q)]

apport information

[Richard (w0h0i-2ic6a7y-p7k1q)]

apport information

[Richard (w0h0i-2ic6a7y-p7k1q)]

apport information

[Richard (w0h0i-2ic6a7y-p7k1q)]

apport information

[Richard (w0h0i-2ic6a7y-p7k1q)]

apport information

[Richard (w0h0i-2ic6a7y-p7k1q)]

apport information

[Richard (w0h0i-2ic6a7y-p7k1q)]

apport information

[Richard (w0h0i-2ic6a7y-p7k1q)]

apport information

[Richard (w0h0i-2ic6a7y-p7k1q)]

apport information

[Richard (w0h0i-2ic6a7y-p7k1q)]

apport information

[Richard (w0h0i-2ic6a7y-p7k1q)]

apport information

[Richard (w0h0i-2ic6a7y-p7k1q)]

apport information

[penalvch (penalvch)]

Richard, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, 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 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 and remove the 'needs-upstream-testing' tag. 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-VERSION-NUMBER', where VERSION-NUMBER is the version number of the kernel you tested.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream-VERSION-NUMBER', where VERSION-NUMBER is the version number of the kernel you tested.

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thank you for your understanding.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

[Richard (w0h0i-2ic6a7y-p7k1q)]

On 02/08/2012 02:06, Christopher M. Penalver wrote:
> Richard, this bug was reported a while ago and there hasn't been any
> activity in it recently. We were wondering if this is still an issue? If
> so, 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 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 and remove the 'needs-upstream-testing' tag.
> 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-VERSION-NUMBER', where VERSION-NUMBER is the
> version number of the kernel you tested.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream-VERSION-NUMBER', where VERSION-NUMBER is the
> version number of the kernel you tested.
>
> If you are unable to test the mainline kernel, please comment as to why
> specifically you were unable to test it and add the tag: 'kernel-unable-
> to-test-upstream'.
I managed to avoid the problem. It was a while ago so I think I fixed it
by either:

Re-creating the access point; or
upgrading to Quantal (which I did around the same time).

Afraid I can't remember which one I did.

R

[penalvch (penalvch)]

Richard, great! Did you need a backport to a release prior to Quantal, or may we mark this Status Invalid?

[Launchpad Janitor (janitor)]

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