Just installed the above USB webcam but it is not recognized by dmesg | grep usb, nor does Zoom recognize it. I was under the understanding it should not require a driver, or?
I am running CentOS 7.
Thanks.
On Tue, Sep 29, 2020 at 10:30 AM H agents@meddatainc.com wrote:
Just installed the above USB webcam but it is not recognized by dmesg | grep usb, nor does Zoom recognize it. I was under the understanding it should not require a driver, or?
I am running CentOS 7.
absolutely nothing at the end of dmesg when you plug it in ?
On Tue, 29 Sep 2020 at 13:31, H agents@meddatainc.com wrote:
Just installed the above USB webcam but it is not recognized by dmesg | grep usb, nor does Zoom recognize it. I was under the understanding it should not require a driver, or?
I am running CentOS 7.
Does anything show up when the device is plugged in. There should be info in dmesg when a device is added or removed, even if the kernel does not recognize it. If you do not have that, then the USB port or device is not working. The lines will say something like "New USB device found, idVendor=<>, idProduct=<>, bcdDevice=<>. That data is independent of your drivers.
Also the command lsusb and /proc/bus/input/devices can give data.
Thanks.
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
On 09/29/2020 01:38 PM, Stephen John Smoogen wrote:
On Tue, 29 Sep 2020 at 13:31, H agents@meddatainc.com wrote:
Just installed the above USB webcam but it is not recognized by dmesg | grep usb, nor does Zoom recognize it. I was under the understanding it should not require a driver, or?
I am running CentOS 7.
Does anything show up when the device is plugged in. There should be info in dmesg when a device is added or removed, even if the kernel does not recognize it. If you do not have that, then the USB port or device is not working. The lines will say something like "New USB device found, idVendor=<>, idProduct=<>, bcdDevice=<>. That data is independent of your drivers.
Also the command lsusb and /proc/bus/input/devices can give data.
Thanks.
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
It does not show up.
On Tue, 29 Sep 2020 13:30:30 -0400 H wrote:
Just installed the above USB webcam but it is not recognized by dmesg | grep usb, nor does Zoom recognize it.
tail -f /var/log/messages
plug in the camera
What do you see?
On 09/29/2020 01:39 PM, Frank Cox wrote:
On Tue, 29 Sep 2020 13:30:30 -0400 H wrote:
Just installed the above USB webcam but it is not recognized by dmesg | grep usb, nor does Zoom recognize it.
tail -f /var/log/messages
plug in the camera
What do you see?
kernel: usb 1-14: new high-speed USB device number 13 using xhci_hcd kernel: usb 1-14: unable to read config index 0 descriptor/all kernel: usb 1-14: can't read configurations, error -32 kernel: usb 1-14: new high-speed USB device number 14 using xhci_hcd kernel: usb 1-14: unable to read config index 0 descriptor/all kernel: usb 1-14: can't read configurations, error -32 kernel: usb usb1-port14: attempt power cycle kernel: usb 1-14: new high-speed USB device number 15 using xhci_hcd kernel: usb 1-14: unable to read config index 0 descriptor/all kernel: usb 1-14: can't read configurations, error -75 kernel: usb 1-14: new high-speed USB device number 16 using xhci_hcd kernel: usb 1-14: unable to read config index 0 descriptor/all kernel: usb 1-14: can't read configurations, error -32 kernel: usb usb1-port14: unable to enumerate USB device
Try
lsusb -v
and
sudo dmesg
... Be aware, systemd deals with udev and it may be malfunctioning
On 9/29/2020 10:30 AM, H wrote:
Just installed the above USB webcam but it is not recognized by dmesg | grep usb, nor does Zoom recognize it. I was under the understanding it should not require a driver, or?
I am running CentOS 7.
Thanks.
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
On 09/29/2020 02:11 PM, Bruce Ferrell wrote:
Try
lsusb -v
and
sudo dmesg
... Be aware, systemd deals with udev and it may be malfunctioning
On 9/29/2020 10:30 AM, H wrote:
Just installed the above USB webcam but it is not recognized by dmesg | grep usb, nor does Zoom recognize it. I was under the understanding it should not require a driver, or?
I am running CentOS 7.
Thanks.
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
I'll bite, systemd and its interaction with udev is beyond my paygrade. How do I investigate this?
do other USB 3 (XHCI) devices work on this system ?
On Tue, Sep 29, 2020 at 5:27 PM H agents@meddatainc.com wrote:
On 09/29/2020 02:11 PM, Bruce Ferrell wrote:
Try
lsusb -v
and
sudo dmesg
... Be aware, systemd deals with udev and it may be malfunctioning
On 9/29/2020 10:30 AM, H wrote:
Just installed the above USB webcam but it is not recognized by dmesg |
grep usb, nor does Zoom recognize it. I was under the understanding it should not require a driver, or?
I am running CentOS 7.
Thanks.
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
I'll bite, systemd and its interaction with udev is beyond my paygrade. How do I investigate this?
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
On 09/29/2020 09:09 PM, John Pierce wrote:
do other USB 3 (XHCI) devices work on this system ?
On Tue, Sep 29, 2020 at 5:27 PM H agents@meddatainc.com wrote:
On 09/29/2020 02:11 PM, Bruce Ferrell wrote:
Try
lsusb -v
and
sudo dmesg
... Be aware, systemd deals with udev and it may be malfunctioning
On 9/29/2020 10:30 AM, H wrote:
Just installed the above USB webcam but it is not recognized by dmesg |
grep usb, nor does Zoom recognize it. I was under the understanding it should not require a driver, or?
I am running CentOS 7.
Thanks.
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
I'll bite, systemd and its interaction with udev is beyond my paygrade. How do I investigate this?
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Not sure I have any. I tried two different USB 3.0 connectors with the same result.
Is there any way I can test this?
On 9/29/20 6:50 PM, H wrote:
On 09/29/2020 09:09 PM, John Pierce wrote:
do other USB 3 (XHCI) devices work on this system ?
On Tue, Sep 29, 2020 at 5:27 PM H agents@meddatainc.com wrote:
On 09/29/2020 02:11 PM, Bruce Ferrell wrote:
Try
lsusb -v
and
sudo dmesg
... Be aware, systemd deals with udev and it may be malfunctioning
On 9/29/2020 10:30 AM, H wrote:
Just installed the above USB webcam but it is not recognized by dmesg |
grep usb, nor does Zoom recognize it. I was under the understanding it should not require a driver, or?
I am running CentOS 7.
Thanks.
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
I'll bite, systemd and its interaction with udev is beyond my paygrade. How do I investigate this?
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Not sure I have any. I tried two different USB 3.0 connectors with the same result.
Is there any way I can test this?
I just checked my C922 it's plugged into a USB2 port and works fine
Try ANY usb device in your ports and see if it shows up in lsusb
You may have a bad port
On 09/29/2020 10:01 PM, Bruce Ferrell wrote:
On 9/29/20 6:50 PM, H wrote:
On 09/29/2020 09:09 PM, John Pierce wrote:
do other USB 3 (XHCI) devices work on this system ?
On Tue, Sep 29, 2020 at 5:27 PM H agents@meddatainc.com wrote:
On 09/29/2020 02:11 PM, Bruce Ferrell wrote:
Try
lsusb -v
and
sudo dmesg
... Be aware, systemd deals with udev and it may be malfunctioning
On 9/29/2020 10:30 AM, H wrote:
Just installed the above USB webcam but it is not recognized by dmesg |
grep usb, nor does Zoom recognize it. I was under the understanding it should not require a driver, or?
I am running CentOS 7.
Thanks.
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
I'll bite, systemd and its interaction with udev is beyond my paygrade. How do I investigate this?
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Not sure I have any. I tried two different USB 3.0 connectors with the same result.
Is there any way I can test this?
I just checked my C922 it's plugged into a USB2 port and works fine
Try ANY usb device in your ports and see if it shows up in lsusb
You may have a bad port
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
I have tried three different ports, two USB-3 and one USB-2 port...
do you have another computer, perhaps a Windows system, you can plug this camera into to see if it works at all?
On Tue, Sep 29, 2020 at 7:22 PM H agents@meddatainc.com wrote:
On 09/29/2020 10:01 PM, Bruce Ferrell wrote:
On 9/29/20 6:50 PM, H wrote:
On 09/29/2020 09:09 PM, John Pierce wrote:
do other USB 3 (XHCI) devices work on this system ?
On Tue, Sep 29, 2020 at 5:27 PM H agents@meddatainc.com wrote:
On 09/29/2020 02:11 PM, Bruce Ferrell wrote:
Try
lsusb -v
and
sudo dmesg
... Be aware, systemd deals with udev and it may be malfunctioning
On 9/29/2020 10:30 AM, H wrote: > Just installed the above USB webcam but it is not recognized by
dmesg |
grep usb, nor does Zoom recognize it. I was under the understanding it should not require a driver, or?
> I am running CentOS 7. > > Thanks. > > _______________________________________________ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
I'll bite, systemd and its interaction with udev is beyond my
paygrade.
How do I investigate this?
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Not sure I have any. I tried two different USB 3.0 connectors with the
same result.
Is there any way I can test this?
I just checked my C922 it's plugged into a USB2 port and works fine
Try ANY usb device in your ports and see if it shows up in lsusb
You may have a bad port
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
I have tried three different ports, two USB-3 and one USB-2 port...
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
On 09/29/2020 10:32 PM, John Pierce wrote:
do you have another computer, perhaps a Windows system, you can plug this camera into to see if it works at all?
On Tue, Sep 29, 2020 at 7:22 PM H agents@meddatainc.com wrote:
On 09/29/2020 10:01 PM, Bruce Ferrell wrote:
On 9/29/20 6:50 PM, H wrote:
On 09/29/2020 09:09 PM, John Pierce wrote:
do other USB 3 (XHCI) devices work on this system ?
On Tue, Sep 29, 2020 at 5:27 PM H agents@meddatainc.com wrote:
On 09/29/2020 02:11 PM, Bruce Ferrell wrote: > Try > > lsusb -v > > and > > sudo dmesg > > ... Be aware, systemd deals with udev and it may be malfunctioning > > > On 9/29/2020 10:30 AM, H wrote: >> Just installed the above USB webcam but it is not recognized by
dmesg |
grep usb, nor does Zoom recognize it. I was under the understanding it should not require a driver, or? >> I am running CentOS 7. >> >> Thanks. >> >> _______________________________________________ >> CentOS mailing list >> CentOS@centos.org >> https://lists.centos.org/mailman/listinfo/centos > _______________________________________________ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos I'll bite, systemd and its interaction with udev is beyond my
paygrade.
How do I investigate this?
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Not sure I have any. I tried two different USB 3.0 connectors with the
same result.
Is there any way I can test this?
I just checked my C922 it's plugged into a USB2 port and works fine
Try ANY usb device in your ports and see if it shows up in lsusb
You may have a bad port
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
I have tried three different ports, two USB-3 and one USB-2 port...
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
I just did - before seeing your post... I tried it on a Dell laptop also running CentOS 7 and it worked fine. Besides the difference in hardware, the OS on the laptop has not been updated for a number of months, possibly not since late last year, while the OS on the desktop is completely updated.
try the camera in a USB 2 port, it should work just fine at usb 2 speeds. most systems, the USB 3 ports hve a 'blue' tongue, while the 2 ports are black or another color.
On Tue, Sep 29, 2020 at 6:50 PM H agents@meddatainc.com wrote:
On 09/29/2020 09:09 PM, John Pierce wrote:
do other USB 3 (XHCI) devices work on this system ?
On Tue, Sep 29, 2020 at 5:27 PM H agents@meddatainc.com wrote:
On 09/29/2020 02:11 PM, Bruce Ferrell wrote:
Try
lsusb -v
and
sudo dmesg
... Be aware, systemd deals with udev and it may be malfunctioning
On 9/29/2020 10:30 AM, H wrote:
Just installed the above USB webcam but it is not recognized by dmesg
|
grep usb, nor does Zoom recognize it. I was under the understanding it should not require a driver, or?
I am running CentOS 7.
Thanks.
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
I'll bite, systemd and its interaction with udev is beyond my paygrade. How do I investigate this?
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Not sure I have any. I tried two different USB 3.0 connectors with the same result.
Is there any way I can test this?
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
On 09/29/2020 10:07 PM, John Pierce wrote:
try the camera in a USB 2 port, it should work just fine at usb 2 speeds. most systems, the USB 3 ports hve a 'blue' tongue, while the 2 ports are black or another color.
On Tue, Sep 29, 2020 at 6:50 PM H agents@meddatainc.com wrote:
On 09/29/2020 09:09 PM, John Pierce wrote:
do other USB 3 (XHCI) devices work on this system ?
On Tue, Sep 29, 2020 at 5:27 PM H agents@meddatainc.com wrote:
On 09/29/2020 02:11 PM, Bruce Ferrell wrote:
Try
lsusb -v
and
sudo dmesg
... Be aware, systemd deals with udev and it may be malfunctioning
On 9/29/2020 10:30 AM, H wrote:
Just installed the above USB webcam but it is not recognized by dmesg
|
grep usb, nor does Zoom recognize it. I was under the understanding it should not require a driver, or?
I am running CentOS 7.
Thanks.
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
I'll bite, systemd and its interaction with udev is beyond my paygrade. How do I investigate this?
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Not sure I have any. I tried two different USB 3.0 connectors with the same result.
Is there any way I can test this?
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Just tried a USB 2 port with a similar outcome:
kernel: usb 1-9: can't read configurations, error -32 kernel: usb usb1-port9: attempt power cycle kernel: usb 1-9: new high-speed USB device number 23 using xhci_hcd kernel: usb 1-9: unable to read config index 0 descriptor/all kernel: usb 1-9: can't read configurations, error -32 kernel: usb 1-9: new high-speed USB device number 24 using xhci_hcd kernel: usb 1-9: unable to read config index 0 descriptor/all kernel: usb 1-9: can't read configurations, error -32 kernel: usb usb1-port9: unable to enumerate USB device
I also have Logitech Bluetooth mouse, an external harddisk, a Belkin USB-serial adapter for my UPS, and a Canon scanner attached to other USB ports, all working fine.
On 9/29/20 7:21 PM, H wrote:
kernel: usb 1-9: unable to read config index 0 descriptor/all
Those error messages mean that the device isn't responding to the Get-Descriptor request.
I think a step back and checking the usb subsystem, in general, might be a good idea:
Let's start with the full output of
lspci
and follow up with the full output of
lsusb
and lsmod
All commands should be run as root
On 09/29/2020 11:11 PM, Bruce Ferrell wrote:
On 9/29/20 7:21 PM, H wrote:
kernel: usb 1-9: unable to read config index 0 descriptor/all
Those error messages mean that the device isn't responding to the Get-Descriptor request.
I think a step back and checking the usb subsystem, in general, might be a good idea:
Let's start with the full output of
lspci
and follow up with the full output of
lsusb
and lsmod
All commands should be run as root
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
This is lsusb:
Bus 002 Device 002: ID 0bc2:231a Seagate RSS LLC Expansion Portable Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
and lspci:
00:00.0 Host bridge: Intel Corporation Sky Lake-E DMI3 Registers (rev 04) 00:04.0 System peripheral: Intel Corporation Sky Lake-E CBDMA Registers (rev 04) 00:04.1 System peripheral: Intel Corporation Sky Lake-E CBDMA Registers (rev 04) 00:04.2 System peripheral: Intel Corporation Sky Lake-E CBDMA Registers (rev 04) 00:04.3 System peripheral: Intel Corporation Sky Lake-E CBDMA Registers (rev 04) 00:04.4 System peripheral: Intel Corporation Sky Lake-E CBDMA Registers (rev 04) 00:04.5 System peripheral: Intel Corporation Sky Lake-E CBDMA Registers (rev 04) 00:04.6 System peripheral: Intel Corporation Sky Lake-E CBDMA Registers (rev 04) 00:04.7 System peripheral: Intel Corporation Sky Lake-E CBDMA Registers (rev 04) 00:05.0 System peripheral: Intel Corporation Sky Lake-E MM/Vt-d Configuration Registers (rev 04) 00:05.2 System peripheral: Intel Corporation Sky Lake-E RAS (rev 04) 00:05.4 PIC: Intel Corporation Sky Lake-E IOAPIC (rev 04) 00:08.0 System peripheral: Intel Corporation Sky Lake-E Ubox Registers (rev 04) 00:08.1 Performance counters: Intel Corporation Sky Lake-E Ubox Registers (rev 04) 00:08.2 System peripheral: Intel Corporation Sky Lake-E Ubox Registers (rev 04) 00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller 00:14.2 Signal processing controller: Intel Corporation 200 Series PCH Thermal Subsystem 00:16.0 Communication controller: Intel Corporation 200 Series PCH CSME HECI #1 00:16.3 Serial controller: Intel Corporation Device a2bd 00:17.0 RAID bus controller: Intel Corporation C600/X79 series chipset SATA RAID Controller 00:1e.0 Signal processing controller: Intel Corporation 200 Series/Z370 Chipset Family Serial IO UART Controller #0 00:1f.0 ISA bridge: Intel Corporation C422 Chipset LPC/eSPI Controller 00:1f.2 Memory controller: Intel Corporation 200 Series/Z370 Chipset Family Power Management Controller 00:1f.3 Audio device: Intel Corporation 200 Series PCH HD Audio 00:1f.4 SMBus: Intel Corporation 200 Series/Z370 Chipset Family SMBus Controller 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-LM 16:05.0 System peripheral: Intel Corporation Sky Lake-E VT-d (rev 04) 16:05.2 System peripheral: Intel Corporation Sky Lake-E RAS Configuration Registers (rev 04) 16:05.4 PIC: Intel Corporation Sky Lake-E IOxAPIC Configuration Registers (rev 04) 16:08.0 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) 16:08.1 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) 16:08.2 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) 16:08.3 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) 16:08.4 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) 16:08.5 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) 16:08.6 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) 16:08.7 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) 16:09.0 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) 16:09.1 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) 16:0e.0 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) 16:0e.1 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) 16:0e.2 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) 16:0e.3 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) 16:0e.4 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) 16:0e.5 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) 16:0e.6 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) 16:0e.7 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) 16:0f.0 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) 16:0f.1 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) 16:1d.0 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) 16:1d.1 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) 16:1d.2 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) 16:1d.3 System peripheral: Intel Corporation Sky Lake-E CHA Registers (rev 04) 16:1e.0 System peripheral: Intel Corporation Sky Lake-E PCU Registers (rev 04) 16:1e.1 System peripheral: Intel Corporation Sky Lake-E PCU Registers (rev 04) 16:1e.2 System peripheral: Intel Corporation Sky Lake-E PCU Registers (rev 04) 16:1e.3 System peripheral: Intel Corporation Sky Lake-E PCU Registers (rev 04) 16:1e.4 System peripheral: Intel Corporation Sky Lake-E PCU Registers (rev 04) 16:1e.5 System peripheral: Intel Corporation Sky Lake-E PCU Registers (rev 04) 16:1e.6 System peripheral: Intel Corporation Sky Lake-E PCU Registers (rev 04) 64:00.0 PCI bridge: Intel Corporation Sky Lake-E PCI Express Root Port A (rev 04) 64:05.0 System peripheral: Intel Corporation Sky Lake-E VT-d (rev 04) 64:05.2 System peripheral: Intel Corporation Sky Lake-E RAS Configuration Registers (rev 04) 64:05.4 PIC: Intel Corporation Sky Lake-E IOxAPIC Configuration Registers (rev 04) 64:08.0 System peripheral: Intel Corporation Sky Lake-E Integrated Memory Controller (rev 04) 64:09.0 System peripheral: Intel Corporation Sky Lake-E Integrated Memory Controller (rev 04) 64:0a.0 System peripheral: Intel Corporation Sky Lake-E Integrated Memory Controller (rev 04) 64:0a.1 System peripheral: Intel Corporation Sky Lake-E Integrated Memory Controller (rev 04) 64:0a.2 System peripheral: Intel Corporation Sky Lake-E Integrated Memory Controller (rev 04) 64:0a.3 System peripheral: Intel Corporation Sky Lake-E Integrated Memory Controller (rev 04) 64:0a.4 System peripheral: Intel Corporation Sky Lake-E Integrated Memory Controller (rev 04) 64:0a.5 System peripheral: Intel Corporation Sky Lake-E LM Channel 1 (rev 04) 64:0a.6 System peripheral: Intel Corporation Sky Lake-E LMS Channel 1 (rev 04) 64:0a.7 System peripheral: Intel Corporation Sky Lake-E LMDP Channel 1 (rev 04) 64:0b.0 System peripheral: Intel Corporation Sky Lake-E DECS Channel 2 (rev 04) 64:0b.1 System peripheral: Intel Corporation Sky Lake-E LM Channel 2 (rev 04) 64:0b.2 System peripheral: Intel Corporation Sky Lake-E LMS Channel 2 (rev 04) 64:0b.3 System peripheral: Intel Corporation Sky Lake-E LMDP Channel 2 (rev 04) 64:0c.0 System peripheral: Intel Corporation Sky Lake-E Integrated Memory Controller (rev 04) 64:0c.1 System peripheral: Intel Corporation Sky Lake-E Integrated Memory Controller (rev 04) 64:0c.2 System peripheral: Intel Corporation Sky Lake-E Integrated Memory Controller (rev 04) 64:0c.3 System peripheral: Intel Corporation Sky Lake-E Integrated Memory Controller (rev 04) 64:0c.4 System peripheral: Intel Corporation Sky Lake-E Integrated Memory Controller (rev 04) 64:0c.5 System peripheral: Intel Corporation Sky Lake-E LM Channel 1 (rev 04) 64:0c.6 System peripheral: Intel Corporation Sky Lake-E LMS Channel 1 (rev 04) 64:0c.7 System peripheral: Intel Corporation Sky Lake-E LMDP Channel 1 (rev 04) 64:0d.0 System peripheral: Intel Corporation Sky Lake-E DECS Channel 2 (rev 04) 64:0d.1 System peripheral: Intel Corporation Sky Lake-E LM Channel 2 (rev 04) 64:0d.2 System peripheral: Intel Corporation Sky Lake-E LMS Channel 2 (rev 04) 64:0d.3 System peripheral: Intel Corporation Sky Lake-E LMDP Channel 2 (rev 04) 65:00.0 VGA compatible controller: NVIDIA Corporation GP107GL [Quadro P620] (rev a1) 65:00.1 Audio device: NVIDIA Corporation GP107GL High Definition Audio Controller (rev a1) b2:05.0 System peripheral: Intel Corporation Sky Lake-E VT-d (rev 04) b2:05.2 System peripheral: Intel Corporation Sky Lake-E RAS Configuration Registers (rev 04) b2:05.4 PIC: Intel Corporation Sky Lake-E IOxAPIC Configuration Registers (rev 04) b2:12.0 Performance counters: Intel Corporation Sky Lake-E M3KTI Registers (rev 04) b2:12.1 Performance counters: Intel Corporation Sky Lake-E M3KTI Registers (rev 04) b2:12.2 System peripheral: Intel Corporation Sky Lake-E M3KTI Registers (rev 04) b2:15.0 System peripheral: Intel Corporation Sky Lake-E M2PCI Registers (rev 04) b2:16.0 System peripheral: Intel Corporation Sky Lake-E M2PCI Registers (rev 04) b2:16.4 System peripheral: Intel Corporation Sky Lake-E M2PCI Registers (rev 04)
Finally lsmod:
Module Size Used by binfmt_misc 17468 1 ext4 584094 1 mbcache 14958 1 ext4 jbd2 107478 1 ext4 uas 22445 1 usb_storage 66718 1 uas zfs 3986613 2 zunicode 331170 1 zfs zlua 147429 1 zfs zcommon 89551 1 zfs znvpair 94388 2 zfs,zcommon zavl 15167 1 zfs icp 301854 1 zfs spl 104299 5 icp,zfs,zavl,zcommon,znvpair btrfs 1074009 0 raid6_pq 102527 1 btrfs xor 21411 1 btrfs fuse 100350 3 ipt_MASQUERADE 12678 1 nf_nat_masquerade_ipv4 13463 1 ipt_MASQUERADE nf_conntrack_netlink 36396 0 xt_addrtype 12676 2 br_netfilter 22256 0 overlay 91659 0 ip6t_rpfilter 12595 1 ip6t_REJECT 12625 2 nf_reject_ipv6 13717 1 ip6t_REJECT ipt_REJECT 12541 2 nf_reject_ipv4 13373 1 ipt_REJECT xt_conntrack 12760 12 ebtable_nat 12807 1 ebtable_broute 12731 1 bridge 151336 2 br_netfilter,ebtable_broute stp 12976 1 bridge llc 14552 2 stp,bridge ip6table_nat 12864 1 nf_conntrack_ipv6 18935 7 nf_defrag_ipv6 35104 1 nf_conntrack_ipv6 nf_nat_ipv6 14131 1 ip6table_nat ip6table_mangle 12700 1 ip6table_security 12710 1 ip6table_raw 12683 1 iptable_nat 12875 1 nf_conntrack_ipv4 15053 7 nf_defrag_ipv4 12729 1 nf_conntrack_ipv4 nf_nat_ipv4 14115 1 iptable_nat nf_nat 26583 3 nf_nat_ipv4,nf_nat_ipv6,nf_nat_masquerade_ipv4 iptable_mangle 12695 1 iptable_security 12705 1 iptable_raw 12678 1 nf_conntrack 139264 8 nf_nat,nf_nat_ipv4,nf_nat_ipv6,xt_conntrack,nf_nat_masquerade_ipv4,nf_conntrack_netlink,nf_conntrack_ipv4,nf_conntrack_ipv6 ip_set 45799 0 nfnetlink 14519 3 ip_set,nf_conntrack_netlink ebtable_filter 12827 1 ebtables 35009 3 ebtable_broute,ebtable_nat,ebtable_filter ip6table_filter 12815 1 ip6_tables 26912 5 ip6table_filter,ip6table_mangle,ip6table_security,ip6table_nat,ip6table_raw iptable_filter 12810 1 vfat 17461 1 fat 65950 1 vfat snd_hda_codec_hdmi 52340 1 mei_wdt 13426 0 skx_edac 13578 0 nfit 55639 1 skx_edac libnvdimm 159680 1 nfit intel_powerclamp 14451 0 coretemp 13444 0 snd_hda_codec_realtek 112353 1 intel_rapl 19451 0 iosf_mbi 15582 1 intel_rapl kvm_intel 188688 0 snd_hda_codec_generic 74631 1 snd_hda_codec_realtek kvm 636965 1 kvm_intel snd_hda_intel 40390 8 snd_hda_codec 136355 4 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel snd_hda_core 91007 5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel snd_hwdep 13608 1 snd_hda_codec irqbypass 13503 1 kvm snd_seq 62774 0 snd_seq_device 14356 1 snd_seq intel_wmi_thunderbolt 12826 0 snd_pcm 101339 4 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_core pcspkr 12718 0 wdat_wdt 13590 0 snd_timer 34110 2 snd_pcm,snd_seq snd 83987 26 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel,snd_seq_device i2c_i801 22736 0 soundcore 15047 1 snd idma64 17483 0 virt_dma 13326 1 idma64 pl2303 19203 1 joydev 17389 0 mei_me 32848 0 sg 40719 0 mei 91150 3 mei_wdt,mei_me tpm_crb 13639 0 ip_tables 27126 5 iptable_security,iptable_filter,iptable_mangle,iptable_nat,iptable_raw xfs 997681 3 libcrc32c 12644 3 xfs,nf_nat,nf_conntrack dm_crypt 27346 2 drbg 30186 1 ansi_cprng 12989 0 raid1 40017 1 sd_mod 46281 5 crc_t10dif 12912 1 sd_mod crct10dif_generic 12647 0 nouveau 1898794 2 video 24538 1 nouveau mxm_wmi 13021 1 nouveau i2c_algo_bit 13413 1 nouveau drm_kms_helper 186531 1 nouveau syscopyarea 12529 1 drm_kms_helper sysfillrect 12701 1 drm_kms_helper sysimgblt 12640 1 drm_kms_helper fb_sys_fops 12703 1 drm_kms_helper ttm 96673 1 nouveau drm 456166 5 ttm,drm_kms_helper,nouveau crct10dif_pclmul 14307 1 crct10dif_common 12595 3 crct10dif_pclmul,crct10dif_generic,crc_t10dif crc32_pclmul 13133 0 e1000e 248599 0 crc32c_intel 22094 2 ghash_clmulni_intel 13273 0 ahci 34056 7 aesni_intel 189456 4 libahci 31992 1 ahci glue_helper 13990 1 aesni_intel lrw 13286 1 aesni_intel gf128mul 15139 1 lrw ablk_helper 13597 1 aesni_intel cryptd 21190 5 ghash_clmulni_intel,aesni_intel,ablk_helper libata 243094 2 ahci,libahci serio_raw 13434 0 ptp 23551 1 e1000e drm_panel_orientation_quirks 17180 1 drm pps_core 19057 1 ptp wmi 21636 3 mxm_wmi,nouveau,intel_wmi_thunderbolt dm_mirror 22289 0 dm_region_hash 20813 1 dm_mirror dm_log 18411 2 dm_region_hash,dm_mirror dm_mod 124501 16 dm_log,dm_mirror,dm_crypt
My computer skills are not enough to interpret the above...
Thank you.
On 9/30/20 8:52 AM, H wrote:
00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller
My system has these:
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05)
lspci -s 00:14.0 -v 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) (prog-if 30 [XHCI]) Subsystem: ASUSTeK Computer Inc. Device 201f Flags: bus master, medium devsel, latency 0, IRQ 25 Memory at dd600000 (64-bit, non-prefetchable) [size=64K] Capabilities: [70] Power Management version 2 Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ Kernel driver in use: xhci_hcd Kernel modules: xhci_pci
lspci -s 00:1a.0 -v 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) (prog-if 20 [EHCI]) Subsystem: ASUSTeK Computer Inc. Device 201f Flags: bus master, medium devsel, latency 0, IRQ 16 Memory at dd618000 (32-bit, non-prefetchable) [size=1K] Capabilities: [50] Power Management version 2 Capabilities: [58] Debug port: BAR=1 offset=00a0 Capabilities: [98] PCI Advanced Features Kernel driver in use: ehci-pci Kernel modules: ehci_pci
lspci -s 00:1d.0 -v 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05) (prog-if 20 [EHCI]) Subsystem: ASUSTeK Computer Inc. Device 201f Flags: bus master, medium devsel, latency 0, IRQ 23 Memory at dd617000 (32-bit, non-prefetchable) [size=1K] Capabilities: [50] Power Management version 2 Capabilities: [58] Debug port: BAR=1 offset=00a0 Capabilities: [98] PCI Advanced Features Kernel driver in use: ehci-pci Kernel modules: ehci_pci
These are my kernel modules:
lsmod | grep usb btusb 53248 0 btrtl 16384 1 btusb btbcm 16384 1 btusb btintel 20480 1 btusb bluetooth 589824 41 btrtl,btintel,bnep,btbcm,rfcomm,btusb snd_usb_audio 278528 1 snd_usbmidi_lib 36864 1 snd_usb_audio snd_hwdep 16384 2 snd_hda_codec,snd_usb_audio snd_rawmidi 40960 1 snd_usbmidi_lib snd_pcm 143360 5 snd_hda_intel,snd_hda_codec,snd_usb_audio,snd_hda_core,snd_hda_codec_hdmi snd 98304 23 snd_hda_intel,snd_hwdep,snd_seq,snd_hda_codec,snd_usb_audio,snd_timer,snd_rawmidi,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_usbmidi_lib,snd_seq_device,snd_hda_codec_realtek,snd_pcm usbhid 57344 0 usbcore 290816 9 uvcvideo,usbhid,snd_usb_audio,ehci_hcd,xhci_pci,snd_usbmidi_lib,btusb,xhci_hcd,ehci_pci
This line is important:
usbcore 290816 9 uvcvideo,usbhid,snd_usb_audio,ehci_hcd,xhci_pci,snd_usbmidi_lib,btusb,xhci_hcd,ehci_pci
Notice the last two entries: xhci_hcd and ehci_pci
Those correspond to:
for my two usb 2 controllers:
Kernel driver in use: xhci_hcd Kernel modules: xhci_pci
for my single usb 3 controller:
Kernel driver in use: xhci_hcd Kernel modules: xhci_pci
from your lspci:
00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller
This is the sole USB controller in your system and it's a USB 3 controller
so... in your case let's do:
sudo lspci -s 00:14.0 -v
then try:
sudo modprobe usbcore
and repeat:
sudo lspci -s 00:14.0 -v
see if the Kernel driver/module lines change. If they do, plug the camera in and check for it to be recognized in lsusb
On October 1, 2020 11:58:11 AM EDT, Bruce Ferrell bferrell@baywinds.org wrote:
On 9/30/20 8:52 AM, H wrote:
00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset
Family USB 3.0 xHCI Controller My system has these:
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05)
lspci -s 00:14.0 -v 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) (prog-if 30 [XHCI]) Subsystem: ASUSTeK Computer Inc. Device 201f Flags: bus master, medium devsel, latency 0, IRQ 25 Memory at dd600000 (64-bit, non-prefetchable) [size=64K] Capabilities: [70] Power Management version 2 Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ Kernel driver in use: xhci_hcd Kernel modules: xhci_pci
lspci -s 00:1a.0 -v 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) (prog-if 20 [EHCI]) Subsystem: ASUSTeK Computer Inc. Device 201f Flags: bus master, medium devsel, latency 0, IRQ 16 Memory at dd618000 (32-bit, non-prefetchable) [size=1K] Capabilities: [50] Power Management version 2 Capabilities: [58] Debug port: BAR=1 offset=00a0 Capabilities: [98] PCI Advanced Features Kernel driver in use: ehci-pci Kernel modules: ehci_pci
lspci -s 00:1d.0 -v 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05) (prog-if 20 [EHCI]) Subsystem: ASUSTeK Computer Inc. Device 201f Flags: bus master, medium devsel, latency 0, IRQ 23 Memory at dd617000 (32-bit, non-prefetchable) [size=1K] Capabilities: [50] Power Management version 2 Capabilities: [58] Debug port: BAR=1 offset=00a0 Capabilities: [98] PCI Advanced Features Kernel driver in use: ehci-pci Kernel modules: ehci_pci
These are my kernel modules:
lsmod | grep usb btusb 53248 0 btrtl 16384 1 btusb btbcm 16384 1 btusb btintel 20480 1 btusb bluetooth 589824 41 btrtl,btintel,bnep,btbcm,rfcomm,btusb snd_usb_audio 278528 1 snd_usbmidi_lib 36864 1 snd_usb_audio snd_hwdep 16384 2 snd_hda_codec,snd_usb_audio snd_rawmidi 40960 1 snd_usbmidi_lib snd_pcm 143360 5 snd_hda_intel,snd_hda_codec,snd_usb_audio,snd_hda_core,snd_hda_codec_hdmi snd 98304 23 snd_hda_intel,snd_hwdep,snd_seq,snd_hda_codec,snd_usb_audio,snd_timer,snd_rawmidi,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_usbmidi_lib,snd_seq_device,snd_hda_codec_realtek,snd_pcm usbhid 57344 0 usbcore 290816 9 uvcvideo,usbhid,snd_usb_audio,ehci_hcd,xhci_pci,snd_usbmidi_lib,btusb,xhci_hcd,ehci_pci
This line is important:
usbcore 290816 9 uvcvideo,usbhid,snd_usb_audio,ehci_hcd,xhci_pci,snd_usbmidi_lib,btusb,xhci_hcd,ehci_pci
Notice the last two entries: xhci_hcd and ehci_pci
Those correspond to:
for my two usb 2 controllers:
Kernel driver in use: xhci_hcd Kernel modules: xhci_pci
for my single usb 3 controller:
Kernel driver in use: xhci_hcd Kernel modules: xhci_pci
from your lspci:
00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller
This is the sole USB controller in your system and it's a USB 3 controller
so... in your case let's do:
sudo lspci -s 00:14.0 -v
then try:
sudo modprobe usbcore
and repeat:
sudo lspci -s 00:14.0 -v
see if the Kernel driver/module lines change. If they do, plug the camera in and check for it to be recognized in lsusb
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Thank you. Unfortunately I will not have access to this computer for some time, will let you know when I can try what you suggest.
On 10/02/2020 07:38 AM, H wrote:
On October 1, 2020 11:58:11 AM EDT, Bruce Ferrell bferrell@baywinds.org wrote:
On 9/30/20 8:52 AM, H wrote:
00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset
Family USB 3.0 xHCI Controller My system has these:
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05)
lspci -s 00:14.0 -v 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) (prog-if 30 [XHCI]) Subsystem: ASUSTeK Computer Inc. Device 201f Flags: bus master, medium devsel, latency 0, IRQ 25 Memory at dd600000 (64-bit, non-prefetchable) [size=64K] Capabilities: [70] Power Management version 2 Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ Kernel driver in use: xhci_hcd Kernel modules: xhci_pci
lspci -s 00:1a.0 -v 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) (prog-if 20 [EHCI]) Subsystem: ASUSTeK Computer Inc. Device 201f Flags: bus master, medium devsel, latency 0, IRQ 16 Memory at dd618000 (32-bit, non-prefetchable) [size=1K] Capabilities: [50] Power Management version 2 Capabilities: [58] Debug port: BAR=1 offset=00a0 Capabilities: [98] PCI Advanced Features Kernel driver in use: ehci-pci Kernel modules: ehci_pci
lspci -s 00:1d.0 -v 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05) (prog-if 20 [EHCI]) Subsystem: ASUSTeK Computer Inc. Device 201f Flags: bus master, medium devsel, latency 0, IRQ 23 Memory at dd617000 (32-bit, non-prefetchable) [size=1K] Capabilities: [50] Power Management version 2 Capabilities: [58] Debug port: BAR=1 offset=00a0 Capabilities: [98] PCI Advanced Features Kernel driver in use: ehci-pci Kernel modules: ehci_pci
These are my kernel modules:
lsmod | grep usb btusb 53248 0 btrtl 16384 1 btusb btbcm 16384 1 btusb btintel 20480 1 btusb bluetooth 589824 41 btrtl,btintel,bnep,btbcm,rfcomm,btusb snd_usb_audio 278528 1 snd_usbmidi_lib 36864 1 snd_usb_audio snd_hwdep 16384 2 snd_hda_codec,snd_usb_audio snd_rawmidi 40960 1 snd_usbmidi_lib snd_pcm 143360 5 snd_hda_intel,snd_hda_codec,snd_usb_audio,snd_hda_core,snd_hda_codec_hdmi snd 98304 23 snd_hda_intel,snd_hwdep,snd_seq,snd_hda_codec,snd_usb_audio,snd_timer,snd_rawmidi,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_usbmidi_lib,snd_seq_device,snd_hda_codec_realtek,snd_pcm usbhid 57344 0 usbcore 290816 9 uvcvideo,usbhid,snd_usb_audio,ehci_hcd,xhci_pci,snd_usbmidi_lib,btusb,xhci_hcd,ehci_pci
This line is important:
usbcore 290816 9 uvcvideo,usbhid,snd_usb_audio,ehci_hcd,xhci_pci,snd_usbmidi_lib,btusb,xhci_hcd,ehci_pci
Notice the last two entries: xhci_hcd and ehci_pci
Those correspond to:
for my two usb 2 controllers:
Kernel driver in use: xhci_hcd Kernel modules: xhci_pci
for my single usb 3 controller:
Kernel driver in use: xhci_hcd Kernel modules: xhci_pci
from your lspci: 00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller
This is the sole USB controller in your system and it's a USB 3 controller
so... in your case let's do:
sudo lspci -s 00:14.0 -v
then try:
sudo modprobe usbcore
and repeat:
sudo lspci -s 00:14.0 -v
see if the Kernel driver/module lines change. If they do, plug the camera in and check for it to be recognized in lsusb
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Thank you. Unfortunately I will not have access to this computer for some time, will let you know when I can try what you suggest. _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Hmm, did not have an opportunity to try your suggestion at the end of message until today - after I did a BIOS update. The BIOS update, by the way, resulted in the complete loss of recognition of the Logitech camera, regardless of which USB ports I am trying...
Anyway, your suggestion above follows: #lspci -s 00:14.0 -v 00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller (prog-if 30 [XHCI]) Subsystem: Lenovo Device 103c Flags: bus master, medium devsel, latency 0, IRQ 28, NUMA node 0 Memory at 43ffff10000 (64-bit, non-prefetchable) [size=64K] Capabilities: [70] Power Management version 2 Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ Kernel driver in use: xhci_hcd
# modprobe usbcore # lspci -s 00:14.0 -v 00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller (prog-if 30 [XHCI]) Subsystem: Lenovo Device 103c Flags: bus master, medium devsel, latency 0, IRQ 28, NUMA node 0 Memory at 43ffff10000 (64-bit, non-prefetchable) [size=64K] Capabilities: [70] Power Management version 2 Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ Kernel driver in use: xhci_hcd
On 11/13/2020 12:40 PM, H wrote:
On 10/02/2020 07:38 AM, H wrote:
On October 1, 2020 11:58:11 AM EDT, Bruce Ferrell bferrell@baywinds.org wrote:
On 9/30/20 8:52 AM, H wrote:
00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset
Family USB 3.0 xHCI Controller My system has these:
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05)
lspci -s 00:14.0 -v 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) (prog-if 30 [XHCI]) Subsystem: ASUSTeK Computer Inc. Device 201f Flags: bus master, medium devsel, latency 0, IRQ 25 Memory at dd600000 (64-bit, non-prefetchable) [size=64K] Capabilities: [70] Power Management version 2 Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ Kernel driver in use: xhci_hcd Kernel modules: xhci_pci
lspci -s 00:1a.0 -v 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) (prog-if 20 [EHCI]) Subsystem: ASUSTeK Computer Inc. Device 201f Flags: bus master, medium devsel, latency 0, IRQ 16 Memory at dd618000 (32-bit, non-prefetchable) [size=1K] Capabilities: [50] Power Management version 2 Capabilities: [58] Debug port: BAR=1 offset=00a0 Capabilities: [98] PCI Advanced Features Kernel driver in use: ehci-pci Kernel modules: ehci_pci
lspci -s 00:1d.0 -v 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05) (prog-if 20 [EHCI]) Subsystem: ASUSTeK Computer Inc. Device 201f Flags: bus master, medium devsel, latency 0, IRQ 23 Memory at dd617000 (32-bit, non-prefetchable) [size=1K] Capabilities: [50] Power Management version 2 Capabilities: [58] Debug port: BAR=1 offset=00a0 Capabilities: [98] PCI Advanced Features Kernel driver in use: ehci-pci Kernel modules: ehci_pci
These are my kernel modules:
lsmod | grep usb btusb 53248 0 btrtl 16384 1 btusb btbcm 16384 1 btusb btintel 20480 1 btusb bluetooth 589824 41 btrtl,btintel,bnep,btbcm,rfcomm,btusb snd_usb_audio 278528 1 snd_usbmidi_lib 36864 1 snd_usb_audio snd_hwdep 16384 2 snd_hda_codec,snd_usb_audio snd_rawmidi 40960 1 snd_usbmidi_lib snd_pcm 143360 5 snd_hda_intel,snd_hda_codec,snd_usb_audio,snd_hda_core,snd_hda_codec_hdmi snd 98304 23 snd_hda_intel,snd_hwdep,snd_seq,snd_hda_codec,snd_usb_audio,snd_timer,snd_rawmidi,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_usbmidi_lib,snd_seq_device,snd_hda_codec_realtek,snd_pcm usbhid 57344 0 usbcore 290816 9 uvcvideo,usbhid,snd_usb_audio,ehci_hcd,xhci_pci,snd_usbmidi_lib,btusb,xhci_hcd,ehci_pci
This line is important:
usbcore 290816 9 uvcvideo,usbhid,snd_usb_audio,ehci_hcd,xhci_pci,snd_usbmidi_lib,btusb,xhci_hcd,ehci_pci
Notice the last two entries: xhci_hcd and ehci_pci
Those correspond to:
for my two usb 2 controllers:
Kernel driver in use: xhci_hcd Kernel modules: xhci_pci
for my single usb 3 controller:
Kernel driver in use: xhci_hcd Kernel modules: xhci_pci
from your lspci: 00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller
This is the sole USB controller in your system and it's a USB 3 controller
so... in your case let's do:
sudo lspci -s 00:14.0 -v
then try:
sudo modprobe usbcore
and repeat:
sudo lspci -s 00:14.0 -v
see if the Kernel driver/module lines change. If they do, plug the camera in and check for it to be recognized in lsusb
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Thank you. Unfortunately I will not have access to this computer for some time, will let you know when I can try what you suggest. _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Hmm, did not have an opportunity to try your suggestion at the end of message until today - after I did a BIOS update. The BIOS update, by the way, resulted in the complete loss of recognition of the Logitech camera, regardless of which USB ports I am trying...
Anyway, your suggestion above follows: #lspci -s 00:14.0 -v 00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller (prog-if 30 [XHCI]) Subsystem: Lenovo Device 103c Flags: bus master, medium devsel, latency 0, IRQ 28, NUMA node 0 Memory at 43ffff10000 (64-bit, non-prefetchable) [size=64K] Capabilities: [70] Power Management version 2 Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ Kernel driver in use: xhci_hcd
# modprobe usbcore # lspci -s 00:14.0 -v 00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller (prog-if 30 [XHCI]) Subsystem: Lenovo Device 103c Flags: bus master, medium devsel, latency 0, IRQ 28, NUMA node 0 Memory at 43ffff10000 (64-bit, non-prefetchable) [size=64K] Capabilities: [70] Power Management version 2 Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ Kernel driver in use: xhci_hcd
Here is the output from tail -f /var/log/messages:
Nov 13 12:41:35 t kernel: usb 1-7: new high-speed USB device number 26 using xhci_hcd Nov 13 12:41:35 t kernel: usb 1-7: unable to read config index 0 descriptor/all Nov 13 12:41:35 t kernel: usb 1-7: can't read configurations, error -32 Nov 13 12:41:35 t kernel: usb 1-7: new high-speed USB device number 27 using xhci_hcd Nov 13 12:41:35 t kernel: usb 1-7: unable to read config index 0 descriptor/all Nov 13 12:41:35 t kernel: usb 1-7: can't read configurations, error -32 Nov 13 12:41:35 t kernel: usb usb1-port7: attempt power cycle Nov 13 12:41:36 t kernel: usb 1-7: new high-speed USB device number 28 using xhci_hcd Nov 13 12:41:36 t kernel: usb 1-7: unable to read config index 0 descriptor/all Nov 13 12:41:36 t kernel: usb 1-7: can't read configurations, error -32 Nov 13 12:41:36 t kernel: usb 1-7: new high-speed USB device number 29 using xhci_hcd Nov 13 12:41:36 t kernel: usb 1-7: unable to read config index 0 descriptor/all Nov 13 12:41:36 t kernel: usb 1-7: can't read configurations, error -32 Nov 13 12:41:36 t kernel: usb usb1-port7: unable to enumerate USB device
With the above said, there is another issue that has been vexing me, I have an external USB harddisk and when it is attached the computer fails to boot the OS (CentOS 7.8.2003). After the Lenovo logo all I see is a blinking underscore on the screen. Disconnecting the harddisk at this time has no effect. I have to have the harddisk disconnected when I boot and then connect it, after which it works fine. The only noteworthy thing I am aware of is that is encrypted using LUKS so I have to enter a passphrase once it is connected.
On 11/13/2020 12:46 PM, H wrote:
On 11/13/2020 12:40 PM, H wrote:
On 10/02/2020 07:38 AM, H wrote:
On October 1, 2020 11:58:11 AM EDT, Bruce Ferrell bferrell@baywinds.org wrote:
On 9/30/20 8:52 AM, H wrote:
00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset
Family USB 3.0 xHCI Controller My system has these:
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05)
lspci -s 00:14.0 -v 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) (prog-if 30 [XHCI]) Subsystem: ASUSTeK Computer Inc. Device 201f Flags: bus master, medium devsel, latency 0, IRQ 25 Memory at dd600000 (64-bit, non-prefetchable) [size=64K] Capabilities: [70] Power Management version 2 Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ Kernel driver in use: xhci_hcd Kernel modules: xhci_pci
lspci -s 00:1a.0 -v 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) (prog-if 20 [EHCI]) Subsystem: ASUSTeK Computer Inc. Device 201f Flags: bus master, medium devsel, latency 0, IRQ 16 Memory at dd618000 (32-bit, non-prefetchable) [size=1K] Capabilities: [50] Power Management version 2 Capabilities: [58] Debug port: BAR=1 offset=00a0 Capabilities: [98] PCI Advanced Features Kernel driver in use: ehci-pci Kernel modules: ehci_pci
lspci -s 00:1d.0 -v 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05) (prog-if 20 [EHCI]) Subsystem: ASUSTeK Computer Inc. Device 201f Flags: bus master, medium devsel, latency 0, IRQ 23 Memory at dd617000 (32-bit, non-prefetchable) [size=1K] Capabilities: [50] Power Management version 2 Capabilities: [58] Debug port: BAR=1 offset=00a0 Capabilities: [98] PCI Advanced Features Kernel driver in use: ehci-pci Kernel modules: ehci_pci
These are my kernel modules:
lsmod | grep usb btusb 53248 0 btrtl 16384 1 btusb btbcm 16384 1 btusb btintel 20480 1 btusb bluetooth 589824 41 btrtl,btintel,bnep,btbcm,rfcomm,btusb snd_usb_audio 278528 1 snd_usbmidi_lib 36864 1 snd_usb_audio snd_hwdep 16384 2 snd_hda_codec,snd_usb_audio snd_rawmidi 40960 1 snd_usbmidi_lib snd_pcm 143360 5 snd_hda_intel,snd_hda_codec,snd_usb_audio,snd_hda_core,snd_hda_codec_hdmi snd 98304 23 snd_hda_intel,snd_hwdep,snd_seq,snd_hda_codec,snd_usb_audio,snd_timer,snd_rawmidi,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_usbmidi_lib,snd_seq_device,snd_hda_codec_realtek,snd_pcm usbhid 57344 0 usbcore 290816 9 uvcvideo,usbhid,snd_usb_audio,ehci_hcd,xhci_pci,snd_usbmidi_lib,btusb,xhci_hcd,ehci_pci
This line is important:
usbcore 290816 9 uvcvideo,usbhid,snd_usb_audio,ehci_hcd,xhci_pci,snd_usbmidi_lib,btusb,xhci_hcd,ehci_pci
Notice the last two entries: xhci_hcd and ehci_pci
Those correspond to:
for my two usb 2 controllers:
Kernel driver in use: xhci_hcd Kernel modules: xhci_pci
for my single usb 3 controller:
Kernel driver in use: xhci_hcd Kernel modules: xhci_pci
from your lspci: 00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller
This is the sole USB controller in your system and it's a USB 3 controller
so... in your case let's do:
sudo lspci -s 00:14.0 -v
then try:
sudo modprobe usbcore
and repeat:
sudo lspci -s 00:14.0 -v
see if the Kernel driver/module lines change. If they do, plug the camera in and check for it to be recognized in lsusb
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Thank you. Unfortunately I will not have access to this computer for some time, will let you know when I can try what you suggest. _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Hmm, did not have an opportunity to try your suggestion at the end of message until today - after I did a BIOS update. The BIOS update, by the way, resulted in the complete loss of recognition of the Logitech camera, regardless of which USB ports I am trying...
Anyway, your suggestion above follows: #lspci -s 00:14.0 -v 00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller (prog-if 30 [XHCI]) Subsystem: Lenovo Device 103c Flags: bus master, medium devsel, latency 0, IRQ 28, NUMA node 0 Memory at 43ffff10000 (64-bit, non-prefetchable) [size=64K] Capabilities: [70] Power Management version 2 Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ Kernel driver in use: xhci_hcd
# modprobe usbcore # lspci -s 00:14.0 -v 00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller (prog-if 30 [XHCI]) Subsystem: Lenovo Device 103c Flags: bus master, medium devsel, latency 0, IRQ 28, NUMA node 0 Memory at 43ffff10000 (64-bit, non-prefetchable) [size=64K] Capabilities: [70] Power Management version 2 Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ Kernel driver in use: xhci_hcd
Here is the output from tail -f /var/log/messages:
Nov 13 12:41:35 t kernel: usb 1-7: new high-speed USB device number 26 using xhci_hcd Nov 13 12:41:35 t kernel: usb 1-7: unable to read config index 0 descriptor/all Nov 13 12:41:35 t kernel: usb 1-7: can't read configurations, error -32 Nov 13 12:41:35 t kernel: usb 1-7: new high-speed USB device number 27 using xhci_hcd Nov 13 12:41:35 t kernel: usb 1-7: unable to read config index 0 descriptor/all Nov 13 12:41:35 t kernel: usb 1-7: can't read configurations, error -32 Nov 13 12:41:35 t kernel: usb usb1-port7: attempt power cycle Nov 13 12:41:36 t kernel: usb 1-7: new high-speed USB device number 28 using xhci_hcd Nov 13 12:41:36 t kernel: usb 1-7: unable to read config index 0 descriptor/all Nov 13 12:41:36 t kernel: usb 1-7: can't read configurations, error -32 Nov 13 12:41:36 t kernel: usb 1-7: new high-speed USB device number 29 using xhci_hcd Nov 13 12:41:36 t kernel: usb 1-7: unable to read config index 0 descriptor/all Nov 13 12:41:36 t kernel: usb 1-7: can't read configurations, error -32 Nov 13 12:41:36 t kernel: usb usb1-port7: unable to enumerate USB device
With the above said, there is another issue that has been vexing me, I have an external USB harddisk and when it is attached the computer fails to boot the OS (CentOS 7.8.2003). After the Lenovo logo all I see is a blinking underscore on the screen. Disconnecting the harddisk at this time has no effect. I have to have the harddisk disconnected when I boot and then connect it, after which it works fine. The only noteworthy thing I am aware of is that is encrypted using LUKS so I have to enter a passphrase once it is connected.
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
On the recommendation by Lenovo, the motherboard has been replaced but the Logitech C922 is still not recognized by the USB subsystem when connected. However, I have now tried Ubuntu 20.10 Live running off the DVD and it does recognize the webcam.
As stated earlier, I have two laptops running CentOS 7 and both recognize the same webcam, thus no high-level deficiency in CentOS 7 itself.
Thus, the problem is not with the hardware, the webcam or the computer, but maybe there is some low-level code for the USB subsystem missing in CentOS 7 required for the Logitech C922 to work on this Lenovo ThinkStation?
What is the opinion of someone more knowledgeable than myself?