When starting up my laptop (Asus G75), my Logitech mouse w/ unifying receiver is not always detected, and I have to unplug it multiple times before it's found. This happend on my Dell XPS 15z as well, and it does pertain to USB3. My MacBook Pro never had that issue -- it only had USB2 ports.
WORKAROUND: Run https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1039143/comments/55 as root and it will unload and reload the module until the mouse works.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-11-generic 3.5.0-11.11
ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2
Uname: Linux 3.5.0-11-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.4-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: rrohde 2109 F.... pulseaudio
/dev/snd/controlC0: rrohde 2109 F.... pulseaudio
Date: Mon Aug 20 12:47:21 2012
EcryptfsInUse: Yes
MachineType: ASUSTeK COMPUTER INC. G75VW
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-11-generic root=UUID=f3ba964c-10c0-441b-9917-2b07cbc460ea ro elevator=noop quiet acpi=irq splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.5.0-11-generic N/A
linux-backports-modules-3.5.0-11-generic N/A
linux-firmware 1.89
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/15/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G75VW.210
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G75VW
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG75VW.210:bd06/15/2012:svnASUSTeKCOMPUTERINC.:pnG75VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG75VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: G75VW
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
Do you happen to know if this issue happened in prior releases?
Would it be possible for you to test the latest upstream kernel? Refer to https:/ /wiki.ubuntu. com/KernelMainl ineBuilds . Please test the latest v3.6 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.
Once you've tested the upstream kernel, please remove the 'needs- upstream- testing' tag. Please only remove that one tag and 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.
[0] http:// kernel. ubuntu. com/~kernel- ppa/mainline/ v3.6-rc2- quantal/