[Gigabyte P35-S3G] Saitek Pedals not recognized at boot, work after unplugging and plugging back in
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
This report applies to Ubuntu 11.10.
The bug exists under previous versions of linux.
After a boot, Saitek pedals are not recognized.
dmesg contains multiple attempts to read the device:
usb 5-2: device descriptor read/64, error -32
etc.
If you unplug and re-plug the device, it works immediately.
It can be reproduced at will by unloading and reloading the usb or usbhid driver.
The current workaround is to unplug the Saitek pedals and plug them back in.
For some reason the sequence of events when connecting is different from what happens when the driver loads. In that case, the device is recognized without problem.
After Plugging in the device, it was working fine. [ 6918.310857]
I then reset the hid driver by removing and inserting the driver. [ 7183.832022]
Then the pedals device was no longer recognized, only the Yoke device, which is completely separate.
So what is different between what the driver does on load, and what the driver does when a device is plugged in?
dmesg:
[ 6918.310857] generic-usb 0003:06A3:
[ 7183.832022] usbcore: deregistering interface driver usbhid
[ 7184.052097] input: Belkin Components USB-PS2 Adapter as /devices/
[ 7184.053186] generic-usb 0003:050D:
[ 7184.066403] input: Belkin Components USB-PS2 Adapter as /devices/
[ 7184.066527] generic-usb 0003:050D:
[ 7184.069467] input: Saitek Saitek Pro Flight Yoke as /devices/
[ 7184.069602] generic-usb 0003:06A3:
[ 7199.069897] generic-usb: probe of 0003:06A3:0763.0004 failed with error -110
[ 7199.070267] usbcore: registered new interface driver usbhid
[ 7199.070269] usbhid: USB HID core driver
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-
ProcVersionSign
Uname: Linux 3.0.0-12-generic i686
NonfreeKernelMo
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu4
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf0200000 irq 45'
Mixer name : 'Realtek ALC662 rev1'
Components : 'HDA:10ec0662,
Controls : 34
Simple ctrls : 18
Card1.Amixer.info:
Card hw:1 'NVidia'/'HDA NVidia at 0xef000000 irq 17'
Mixer name : 'Nvidia GPU 14 HDMI/DP'
Components : 'HDA:10de0014,
Controls : 16
Simple ctrls : 4
Date: Thu Nov 10 19:33:05 2011
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. P35-S3G
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
linux-
linux-
linux-firmware 1.60
RfKill:
SourcePackage: linux
StagingDrivers: altera_stapl
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/30/2007
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F2
dmi.board.name: P35-S3G
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSof
dmi.product.name: P35-S3G
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
summary: |
- Saitek Pedals not recognized at boot + Saitek Pedals not recognized at boot, work after unplugging and plugging + back in |
Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https:/ /wiki.ubuntu. com/KernelMainl ineBuilds . If possible, please test the latest v3.2-rcN kernel (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 others). 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 by the mainline kernel, please add the following tag 'kernel- fixed-upstream- KERNEL- VERSION' . For example, if kernel version 3.2-rc1 fixed and issue, the tag would be: 'kernel- fixed-upstream- v3.2-rc1' .
If the mainline kernel does not fix this bug, please add the tag: 'kernel- bug-exists- upstream' .
Thanks in advance.