On 03/30/18 10:29, Tom Hodder wrote: > > Hi All, > > I've been having a bunch of trouble with the USB ports on my desktop, in particular > the webcam doesn't work and there are lots of errors in the output > <https://paste.fedoraproject.org/paste/qYxQ2rH-tlsE8pJqWz442w> of *"lsusb -v"* when > I try to debug. (I get the "can't get device qualifier: Resource temporarily > unavailable" errors, whether the webcam is plugged in or not, which seems to > eliminate the webcam itself as the source of the problem) > > On the positive side, a usb keyboard, mouse and USB sticks seem to work ok. The > hardware is a Supermicro SuperWorkstation 7037A-i > <https://www.supermicro.com/products/system/tower/7037/sys-7037a-i.cfm>, with an > X9dai motherboard > <https://www.supermicro.com/products/motherboard/xeon/c600/x9dai.cfm>. > > I assumed the problem was hardware related and raised a ticket with supermicro. > They asked me to test the machine using a supported OS, and the nearest to > fedora-27 was CentOS 6.2 (compatibility matrix > <https://www.supermicro.com/support/resources/OS/C602_listing2.cfm>). So today I > booted into Centos-6.2. To my surprise there were no errors in the "lsusb -v" > output <https://paste.fedoraproject.org/paste/yVFlRYGi9m4ZCt9PZPF3Gg>, no errors in > dmesg or syslog, and the webcam worked fine. > > This seems to suggest it's not a hardware problem, but some difference in the > drivers. I am pretty sure the usb/webcam used to work, but that's going back a few > versions of fedora, and probably 3/4 years. > > Any ideas on what might be causing this? > > > > > Plugging in the webcam produces this; > Mar 30 02:19:24 pc03.config kernel: usb 2-1.7: new high-speed USB device number 8 > using ehci-pci > Mar 30 02:19:25 pc03.config kernel: usb 2-1.7: New USB device found, idVendor=045e, > idProduct=0294 > Mar 30 02:19:25 pc03.config kernel: usb 2-1.7: New USB device strings: Mfr=1, > Product=2, SerialNumber=3 > Mar 30 02:19:25 pc03.config kernel: usb 2-1.7: Product: Video Camera > Mar 30 02:19:25 pc03.config kernel: usb 2-1.7: Manufacturer: Microsoft > Mar 30 02:19:25 pc03.config kernel: usb 2-1.7: SerialNumber: 000F330333475838 > Mar 30 02:19:25 pc03.config kernel: uvcvideo: Found UVC 1.00 device Video Camera > (045e:0294) > Mar 30 02:19:26 pc03.config kernel: uvcvideo 2-1.7:1.0: Entity type for entity > Extension 3 was not initialized! > Mar 30 02:19:26 pc03.config kernel: uvcvideo 2-1.7:1.0: Entity type for entity > Processing 2 was not initialized! > Mar 30 02:19:26 pc03.config kernel: uvcvideo 2-1.7:1.0: Entity type for entity > Camera 1 was not initialized! > > ... > Mar 30 02:19:19 pc03.config kernel: uvcvideo: Failed to set UVC probe control : -71 > (exp. 26). > Mar 30 02:19:19 pc03.config kernel: uvcvideo: Failed to set UVC probe control : -71 > (exp. 26). > Mar 30 02:19:19 pc03.config kernel: uvcvideo: Failed to set UVC probe control : -71 > (exp. 26). > Mar 30 02:19:19 pc03.config kernel: uvcvideo: Failed to set UVC probe control : -71 > (exp. 26). > The error above is being reported by the uvcvideo module which is part of the kernel. For informational and debugging information the first thing I would do is determine what kernel version is in used for Centos 6.2 v.s. F27. I'm pretty sure they are quite different. Then, I would also check the actual make/model of the webcam and see if there have been any firmware updates to the camera. Doing some web searches show that some user's webcams have shown the errors above and have been *fixed* by kernel upgrades. I've not seen where a camera ceased to work after an upgrade but that doesn't mean it won't happen if it is actually a firmware issue in the camera itself. As I mentioned above you should find the kernel version of CentOS 6.2 and potentially boot a live Fedora with a similar kernel. -- Conjecture is just a conclusion based on incomplete information. It isn't a fact.
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
