[Gigabyte P35-S3G] Saitek Pedals not recognized at boot, work after unplugging and plugging back in

Bug #888838 reported by Pat Callahan
24
This bug affects 4 people
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:0763.0005: input,hidraw3: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Rudder Pedals] on usb-0000:00:1a.2-2/input0
[ 7183.832022] usbcore: deregistering interface driver usbhid
[ 7184.052097] input: Belkin Components USB-PS2 Adapter as /devices/pci0000:00/0000:00:1a.1/usb4/4-2/4-2:1.0/input/input22
[ 7184.053186] generic-usb 0003:050D:0119.0001: input,hidraw0: USB HID v1.00 Keyboard [Belkin Components USB-PS2 Adapter ] on usb-0000:00:1a.1-2/input0
[ 7184.066403] input: Belkin Components USB-PS2 Adapter as /devices/pci0000:00/0000:00:1a.1/usb4/4-2/4-2:1.1/input/input23
[ 7184.066527] generic-usb 0003:050D:0119.0002: input,hidraw1: USB HID v1.00 Mouse [Belkin Components USB-PS2 Adapter ] on usb-0000:00:1a.1-2/input1
[ 7184.069467] input: Saitek Saitek Pro Flight Yoke as /devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.4/1-5.4:1.0/input/input24
[ 7184.069602] generic-usb 0003:06A3:0BAC.0003: input,hidraw2: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Yoke] on usb-0000:00:1a.7-5.4/input0
[ 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-3.0.0-12-generic 3.0.0-12.20
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu4
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: pac1 2284 F.... pulseaudio
 /dev/snd/controlC0: pac1 2284 F.... pulseaudio
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,1458a002,00100101'
   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,10de0101,00100100'
   Controls : 16
   Simple ctrls : 4
Date: Thu Nov 10 19:33:05 2011
HibernationDevice: RESUME=UUID=d90f94b7-890b-47d9-a648-acd3ecb92eb0
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=/vmlinuz-3.0.0-12-generic root=UUID=830cb168-a478-466e-b945-b20151ef6adc ro quiet splash irqpoll vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-12-generic N/A
 linux-backports-modules-3.0.0-12-generic N/A
 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:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/30/2007:svnGigabyteTechnologyCo.,Ltd.:pnP35-S3G:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-S3G:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: P35-S3G
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
Pat Callahan (pat-callahan1) wrote :
Brad Figg (brad-figg)
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
Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Re: 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/KernelMainlineBuilds . 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.

tags: added: needs-upstream-testing
Revision history for this message
Pat Callahan (pat-callahan1) wrote :

I tested this with kernel 3.2.0-030200rc2-generic #201111151435 SMP
from folder v3.2-rc2-oneiric/ 15-Nov-2011 19:51 in http://kernel.ubuntu.com/~kernel-ppa/mainline/

The bug is not fixed in the mainline kernel

tags: added: kernel-bug-exists-upstream
removed: needs-upstream-testing
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report at bugzilla.kernel.org [1]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

The bugzilla.kernel.org site may still be unavailable due to the recent break-in. If that is the case, please add the tag: kernel-needs-upstream-bug-report

[1] https://wiki.ubuntu.com/Bugs/Upstream/kernel

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Triaged
Revision history for this message
penalvch (penalvch) wrote :

Pat Callahan, 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 for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc1

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

tags: added: bios-outdated-f5 needs-upstream-testing
removed: descriptor-unity device saitek usb
Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Olivier Caro (oliviercaro) wrote : apport information

AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: olivier 2677 F.... pulseaudio
 /dev/snd/controlC0: olivier 2677 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xfeb00000 irq 16'
   Mixer name : 'Realtek ALC887-VD'
   Components : 'HDA:10ec0887,10438445,00100302'
   Controls : 43
   Simple ctrls : 22
Card1.Amixer.info:
 Card hw:1 'Generic'/'HD-Audio Generic at 0xfea40000 irq 78'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100200'
   Controls : 6
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
DistroRelease: Ubuntu 12.04
EcryptfsInUse: Yes
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: To be filled by O.E.M. To be filled by O.E.M.
MarkForUpload: True
NonfreeKernelModules: fglrx
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-57-generic root=/dev/mapper/vg0-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-57.87-generic 3.2.52
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-57-generic N/A
 linux-backports-modules-3.2.0-57-generic N/A
 linux-firmware 1.79.9
RfKill:

StagingDrivers: zram
Tags: precise running-unity staging
Uname: Linux 3.2.0-57-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom davfs2 debian-tor dialout dip lpadmin plugdev sambashare sudo
dmi.bios.date: 07/17/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0601
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A97 LE R2.0
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0601:bd07/17/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.

tags: added: apport-collected precise running-unity
Revision history for this message
Olivier Caro (oliviercaro) wrote : AcpiTables.txt

apport information

Revision history for this message
Olivier Caro (oliviercaro) wrote : AlsaDevices.txt

apport information

Revision history for this message
Olivier Caro (oliviercaro) wrote : AplayDevices.txt

apport information

Revision history for this message
Olivier Caro (oliviercaro) wrote : ArecordDevices.txt

apport information

Revision history for this message
Olivier Caro (oliviercaro) wrote : BootDmesg.txt

apport information

Revision history for this message
Olivier Caro (oliviercaro) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
Olivier Caro (oliviercaro) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
Olivier Caro (oliviercaro) wrote : Card1.Codecs.codec.0.txt

apport information

Revision history for this message
Olivier Caro (oliviercaro) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Olivier Caro (oliviercaro) wrote : Lspci.txt

apport information

Revision history for this message
Olivier Caro (oliviercaro) wrote : Lsusb.txt

apport information

Revision history for this message
Olivier Caro (oliviercaro) wrote : PciMultimedia.txt

apport information

Revision history for this message
Olivier Caro (oliviercaro) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Olivier Caro (oliviercaro) wrote : ProcEnviron.txt

apport information

Revision history for this message
Olivier Caro (oliviercaro) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Olivier Caro (oliviercaro) wrote : ProcModules.txt

apport information

Revision history for this message
Olivier Caro (oliviercaro) wrote : PulseList.txt

apport information

Revision history for this message
Olivier Caro (oliviercaro) wrote : UdevDb.txt

apport information

Revision history for this message
Olivier Caro (oliviercaro) wrote : UdevLog.txt

apport information

Revision history for this message
Olivier Caro (oliviercaro) wrote : UserAsoundrc.txt

apport information

Revision history for this message
Olivier Caro (oliviercaro) wrote : WifiSyslog.txt

apport information

Revision history for this message
penalvch (penalvch) wrote : Re: Saitek Pedals not recognized at boot, work after unplugging and plugging back in

Olivier Caro, please do not apport-collect to another person's report. If you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions or comments, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

tags: removed: apport-collected precise running running-unity
summary: - Saitek Pedals not recognized at boot, work after unplugging and plugging
- back in
+ [Gigabyte P35-S3G] Saitek Pedals not recognized at boot, work after
+ unplugging and plugging back in
Revision history for this message
Pat Callahan (pat-callahan1) wrote :

Retesting on 13.10

Revision history for this message
Pat Callahan (pat-callahan1) wrote :

Retested on 13.10 32 bit updated as of 20-Dec-2013.

This is now working correctly.

After boot or after resume, you can start flightgear and the pedals work.

This bug can now be closed.

Changed in linux (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
hamza alloush (hamzaalloush) wrote :

Believe it or not bug still persists on Ubuntu 14.04, have "device descriptor read/8, error -32" errors all over and it does work as described here, if i plug the device again.

Revision history for this message
penalvch (penalvch) wrote :

hamza alloush, this bug report is closed, and has nothing to do with 14.04.

Despite this, it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

To post a comment you must log in.