I updated windows on my laptop(Toshiba now owned by DynaBook) and it included some driver updates.
Now when I start Leap, there’s is a few lines in the boot up process that indicate some USB port or ports are not recognized.
my question is, will driver updated on the Windows 10 partition, affect Leap?
No, openSUSE should not depend on anything in your Windows partition, unless you are mounting that partition.
However, it is possible that the Windows update also updated your BIOS. And that could have noticeable effects when booting openSUSE.
Also Windows may leave hardware in an incorrect state that Linux can’t handle on a warm boot. Do a cold boot tl openSUSE and see if that works.
I have had Windows “corrupt” the /boot/efi partition by CHKDSK and moving files to CHKxxx or whatever CHKDSK renames them to. It also added a System Volume and Recycler folders to the partition.
I had to boot a “Live” USB and restore the /boot/efi partition as it points to the Windows boot partition and the laptop was useless as it could not boot.
Since the /boot/efi partition is fat32 - Windows seems to want to CHKDSK it on a boot.
I suspect that a request to reboot after a zypper up had modified files in /boot/efi and had not sync the drive before I rebooted the laptop. The Grub2 menu default is to boot Windows 10 and I bet that Windows saw it was dirty and fixed it. When I went back to OpenSUSE - no more boot as all the files were gone.
This is the USB error stuff I see when booting.
from boot.msg in /var/log
4.303157] usb 2-8: device descriptor read/64, error -71
<6> 4.303490] EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: (null)
<3> 4.543162] usb 2-8: device descriptor read/64, error -71
<6> 4.651230] usb usb2-port8: attempt power cycle
<7> 4.833505] systemd-journald[188]: Received SIGTERM from PID 1 (systemd).
<4> 5.082338] printk: systemd: 15 output lines suppressed due to ratelimiting
<6> 5.303150] usb 2-8: new full-speed USB device number 6 using xhci_hcd
<4> 5.303272] usb 2-8: Device not responding to setup address.
<4> 5.511394] usb 2-8: Device not responding to setup address.
<3> 5.719193] usb 2-8: device not accepting address 6, error -71
<6> 5.847190] usb 2-8: new full-speed USB device number 7 using xhci_hcd
<4> 5.847398] usb 2-8: Device not responding to setup address.
<4> 6.055291] usb 2-8: Device not responding to setup address.
<3> 6.263162] usb 2-8: device not accepting address 7, error -71
<3> 6.263858] usb usb2-port8: unable to enumerate USB device
EDITED TO ADD THIS Should I put the install USB in and try to fix it that way?
It is after a complete cold boot.
4.303157] usb 2-8: device descriptor read/64, error -71
This is because an update of the kernel, I am also affected.
First, the port was working, now not.
But I do not see deeper because I have enove USB-ports…
journalctl -b | grep -i 'device descriptor'
Nov 12 15:04:40 linux64 kernel: usb 1-7: device descriptor read/64, error -71
Nov 12 15:04:40 linux64 kernel: usb 1-7: device descriptor read/64, error -71
Nov 12 15:04:41 linux64 kernel: usb 1-7: device descriptor read/64, error -71
Nov 12 15:04:41 linux64 kernel: usb 1-7: device descriptor read/64, error -71
Apparantly I can’t see deeper either because I get the same as yours except mine is ‘usb 2.8’
So, no way to find what usb device 2.8 is ?
EDIT
‘lsusb -t shows it as the
Port 8: Dev12 ‘class=video, Driver=uvcvideo, 480M
Hardware dependant also perhaps…
Updated a Leap 15.2 system earlier today which included kernel-default 5.3.18-lp152.50.1 and all USB ports, both USB2 and 3 are working without problem, no errors reported in the log.
Hardware dependant also perhaps...
Kernel depending…
Sometime it is there, sometimes not…, depends
I am running kernel:stable
Pertains to your webcam?
yes, it likely is. The following outputs indicated it to be the ‘problem’.
This listing web cam no worky,. No port 8 shown!
lsusb -t
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
|__ Port 2: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 7: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
|__ Port 7: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
This listing the web cam does work & Shows port 8 (all I did was tilt the lid a bit.)
lsusb -t
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
|__ Port 2: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 7: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
|__ Port 7: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 8: Dev 33, If 0, Class=Video, Driver=uvcvideo, 480M
|__ Port 8: Dev 33, If 1, Class=Video, Driver=uvcvideo, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
So, until I know better, I am going to ignore it.
Yes, I wonder if Windows has inhibited it somehow.
I doubt it deano_ferrari, that camera has worked on and off for a long time. I have to have the lid just right to get it to work.
I guess I am just waking up to the message during boot. Another old age thing??
(there is a thread here somewhere of me asking about the web cam).
I will however open Win10, and see if it works consistently there. I don’t wanna, but I will.
PS; I can always rip it out and wire it to a USB cable, but it’d be easier to just buy one if I really need it.
So it works in the Linux environment? My thoughts were that Windows might disable it at shutdown and enable it at boot, effectively locking its access out from openSUSE.
I will however open Win10, and see if it works consistently there. I don’t wanna, but I will.
Well you started the thread asking about USB errors with respect to the device, so worth checking. We only have what you report to go on. 
PS; I can always rip it out and wire it to a USB cable, but it’d be easier to just buy one if I really need it.
Yep.
Same Same Windows 10. Sporadic web cam depending if I get the lid tilted just right.
But I tried.
Also, I rarely start Win10 on any of my machines. Every 3 or 4 months to get updates and/orbonly to add songs to my iPod.
So I don’t think Win10 is having any affect on web cam on/off at start up/shut down.
Now that, points very much to a hardware issue, intermittent connection breaking/making with lid movement. 
Yes, a likely cause here.