F35 no USB after today's updates

[Sergio Pascual]

Hi, I upgraded my workstation to F35 last Friday, and today I 'dnf updated'
and rebooted. After the reboot, all my USBs are disabled. No mouse, no
keyword.
I know my hardware works because the keyboard works in grub, and the light
of my optical mouse in on until some errors appear in the kernel during
boot.

I have tried:
kernel-5.14.15-200.fc34.x86_64
kernel-5.14.15-300.fc35.x86_64
kernel-5.14.16-301.fc35.x86_64

without success.
I'm getting messages like these:

[   23.722355] usb 3-10: new high-speed USB device number 7 using xhci_hcd
[   23.857746] usb 3-10: New USB device found, idVendor=0bda,
idProduct=0184, bcdDevice=84.13
[   23.857755] usb 3-10: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[   23.857759] usb 3-10: Product: USB2.0-CRW
[   23.857762] usb 3-10: Manufacturer: Generic
[   23.857764] usb 3-10: SerialNumber: 20100818841300000
[   24.016363] usb 3-7.1: new high-speed USB device number 8 using xhci_hcd
[   29.648377] usb 3-7.1: device descriptor read/64, error -110
[   45.520400] usb 3-7.1: device descriptor read/64, error -110
[   45.624451] usb 3-7-port1: attempt power cycle
[   45.738358] usb 3-13: new high-speed USB device number 9 using xhci_hcd
[   45.865929] usb 3-13: New USB device found, idVendor=05e3,
idProduct=0608, bcdDevice=32.98
[   45.865939] usb 3-13: New USB device strings: Mfr=0, Product=1,
SerialNumber=0
[   45.865942] usb 3-13: Product: USB2.0 Hub
[   45.866653] hub 3-13:1.0: USB hub found
[   45.866992] hub 3-13:1.0: 4 ports detected
[   46.304365] usb 3-7.1: new high-speed USB device number 10 using xhci_hcd
[   56.160384] xhci_hcd 0000:00:14.0: Abort failed to stop command ring:
-110
[   56.160384] xhci_hcd 0000:00:14.0: xHCI host controller not responding,
assume dead
[   56.160384] xhci_hcd 0000:00:14.0: HC died; cleaning up
[   56.488455] xhci_hcd 0000:00:14.0: Timeout while waiting for setup
device command
[   56.488480] usb 4-2: USB disconnect, device number 2
[   56.904366] usb 3-7.1: device not accepting address 10, error -108
[   56.904412] usb 3-7-port1: couldn't allocate usb_device
[   56.904464] usb usb3-port2: couldn't allocate usb_device
[   56.904502] usb 3-13-port1: couldn't allocate usb_device
[   56.904603] usb 3-3: USB disconnect, device number 2
[   56.927819] usb 3-6: USB disconnect, device number 3

[Peter Robinson]

>  Hi, I upgraded my workstation to F35 last Friday, and today I
> 'dnf updated' and rebooted. After the reboot, all my USBs are disabled. No mouse,
> no keyword.
>  I know my hardware works because the keyboard works in grub, and the light of my optical
> mouse in on until some errors appear in the kernel during boot. 
Please provide details of the actual HW.

> I have tried:
> kernel-5.14.15-200.fc34.x86_64
> kernel-5.14.15-300.fc35.x86_64
> kernel-5.14.16-301.fc35.x86_64
>
> without success.
> I'm getting messages like these:
>
> [   23.722355] usb 3-10: new high-speed USB device number 7 using xhci_hcd
> [   23.857746] usb 3-10: New USB device found, idVendor=0bda, idProduct=0184,
bcdDevice=84.13
> [   23.857755] usb 3-10: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> [   23.857759] usb 3-10: Product: USB2.0-CRW
> [   23.857762] usb 3-10: Manufacturer: Generic
> [   23.857764] usb 3-10: SerialNumber: 20100818841300000
> [   24.016363] usb 3-7.1: new high-speed USB device number 8 using xhci_hcd
> [   29.648377] usb 3-7.1: device descriptor read/64, error -110
> [   45.520400] usb 3-7.1: device descriptor read/64, error -110
> [   45.624451] usb 3-7-port1: attempt power cycle
> [   45.738358] usb 3-13: new high-speed USB device number 9 using xhci_hcd
> [   45.865929] usb 3-13: New USB device found, idVendor=05e3, idProduct=0608,
bcdDevice=32.98
> [   45.865939] usb 3-13: New USB device strings: Mfr=0, Product=1, SerialNumber=0
> [   45.865942] usb 3-13: Product: USB2.0 Hub
> [   45.866653] hub 3-13:1.0: USB hub found
> [   45.866992] hub 3-13:1.0: 4 ports detected
> [   46.304365] usb 3-7.1: new high-speed USB device number 10 using xhci_hcd
> [   56.160384] xhci_hcd 0000:00:14.0: Abort failed to stop command ring: -110
> [   56.160384] xhci_hcd 0000:00:14.0: xHCI host controller not responding, assume
dead
> [   56.160384] xhci_hcd 0000:00:14.0: HC died; cleaning up
> [   56.488455] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
> [   56.488480] usb 4-2: USB disconnect, device number 2
> [   56.904366] usb 3-7.1: device not accepting address 10, error -108
> [   56.904412] usb 3-7-port1: couldn't allocate usb_device
> [   56.904464] usb usb3-port2: couldn't allocate usb_device
> [   56.904502] usb 3-13-port1: couldn't allocate usb_device
> [   56.904603] usb 3-3: USB disconnect, device number 2
> [   56.927819] usb 3-6: USB disconnect, device number 3
>
>
>
> _______________________________________________
> devel mailing list -- devel(a)lists.fedoraproject.org
> To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/[e-mail]
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

[Stephen John Smoogen]

On Mon, 8 Nov 2021 at 06:53, Sergio Pascual <sergio.pasra(a)gmail.com&gt; wrote:
>  Hi, I upgraded my workstation to F35 last Friday, and today I 'dnf updated' and
> rebooted. After the reboot, all my USBs are disabled. No mouse, no keyword.
>  I know my hardware works because the keyboard works in grub, and the light of my optical
> mouse in on until some errors appear in the kernel during boot.
>
>  I have tried:
>  kernel-5.14.15-200.fc34.x86_64
>  kernel-5.14.15-300.fc35.x86_64
>  kernel-5.14.16-301.fc35.x86_64
>  
The developers will need to know what the exact motherboard/laptop
version and manufacturer you have in order to diagnose this issue. My
initial guess is that since the f34 kernel also fails, that the
problem is with a firmware module and whatever the motherboard is
expecting to use. [The fact that it is only finding USB2 says that
either the system is really old or that it is trying to fail to its
lowest working value.]


>  without success.
>  I'm getting messages like these:
>
>  [   23.722355] usb 3-10: new high-speed USB device number 7 using xhci_hcd
>  [   23.857746] usb 3-10: New USB device found, idVendor=0bda, idProduct=0184,
> bcdDevice=84.13
>  [   23.857755] usb 3-10: New USB device strings: Mfr=1, Product=2, SerialNumber=3
>  [   23.857759] usb 3-10: Product: USB2.0-CRW
>  [   23.857762] usb 3-10: Manufacturer: Generic
>  [   23.857764] usb 3-10: SerialNumber: 20100818841300000
>  [   24.016363] usb 3-7.1: new high-speed USB device number 8 using xhci_hcd
>  [   29.648377] usb 3-7.1: device descriptor read/64, error -110
>  [   45.520400] usb 3-7.1: device descriptor read/64, error -110
>  [   45.624451] usb 3-7-port1: attempt power cycle
>  [   45.738358] usb 3-13: new high-speed USB device number 9 using xhci_hcd
>  [   45.865929] usb 3-13: New USB device found, idVendor=05e3, idProduct=0608,
> bcdDevice=32.98
>  [   45.865939] usb 3-13: New USB device strings: Mfr=0, Product=1, SerialNumber=0
>  [   45.865942] usb 3-13: Product: USB2.0 Hub
>  [   45.866653] hub 3-13:1.0: USB hub found
>  [   45.866992] hub 3-13:1.0: 4 ports detected
>  [   46.304365] usb 3-7.1: new high-speed USB device number 10 using xhci_hcd
>  [   56.160384] xhci_hcd 0000:00:14.0: Abort failed to stop command ring: -110
>  [   56.160384] xhci_hcd 0000:00:14.0: xHCI host controller not responding, assume dead
>  [   56.160384] xhci_hcd 0000:00:14.0: HC died; cleaning up
>  [   56.488455] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
>  [   56.488480] usb 4-2: USB disconnect, device number 2
>  [   56.904366] usb 3-7.1: device not accepting address 10, error -108
>  [   56.904412] usb 3-7-port1: couldn't allocate usb_device
>  [   56.904464] usb usb3-port2: couldn't allocate usb_device
>  [   56.904502] usb 3-13-port1: couldn't allocate usb_device
>  [   56.904603] usb 3-3: USB disconnect, device number 2
>  [   56.927819] usb 3-6: USB disconnect, device number 3
>
>
>
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure


-- 
Stephen J Smoogen.
Let us be kind to one another, for most of us are fighting a hard
battle. -- Ian MacClaren

[Sergio Pascual]

El lun, 8 nov 2021 a las 13:39, Stephen John Smoogen (<smooge(a)gmail.com>)
escribió:

>  On Mon, 8 Nov 2021 at 06:53, Sergio Pascual
> <sergio.pasra(a)gmail.com&gt;
>  wrote:
>  >
>  > Hi, I upgraded my workstation to F35 last Friday, and today I 'dnf
>  updated' and rebooted. After the reboot, all my USBs are disabled. No
>  mouse, no keyword.
>  > I know my hardware works because the keyboard works in grub, and the
>  light of my optical mouse in on until some errors appear in the kernel
>  during boot.
>  >
>  > I have tried:
>  > kernel-5.14.15-200.fc34.x86_64
>  > kernel-5.14.15-300.fc35.x86_64
>  > kernel-5.14.16-301.fc35.x86_64
>  >
>
>  The developers will need to know what the exact motherboard/laptop
>  version and manufacturer you have in order to diagnose this issue. My
>  initial guess is that since the f34 kernel also fails, that the
>  problem is with a firmware module and whatever the motherboard is
>  expecting to use. [The fact that it is only finding USB2 says that
>  either the system is really old or that it is trying to fail to its
>  lowest working value.]
>
>
>  
My workstation is a Dell Precision Tower 7910.

lscpi says I have the following serial bus controllers

00:14.0 USB controller: Intel Corporation C610/X99 series chipset USB xHCI
Host Controller (rev 05)
00:1a.0 USB controller: Intel Corporation C610/X99 series chipset USB
Enhanced Host Controller #2 (rev 05)
00:1d.0 USB controller: Intel Corporation C610/X99 series chipset USB
Enhanced Host Controller #1 (rev 05)

Regards




>  > without success.
>  > I'm getting messages like these:
>  >
>  > [   23.722355] usb 3-10: new high-speed USB device number 7 using
>  xhci_hcd
>  > [   23.857746] usb 3-10: New USB device found, idVendor=0bda,
>  idProduct=0184, bcdDevice=84.13
>  > [   23.857755] usb 3-10: New USB device strings: Mfr=1, Product=2,
>  SerialNumber=3
>  > [   23.857759] usb 3-10: Product: USB2.0-CRW
>  > [   23.857762] usb 3-10: Manufacturer: Generic
>  > [   23.857764] usb 3-10: SerialNumber: 20100818841300000
>  > [   24.016363] usb 3-7.1: new high-speed USB device number 8 using
>  xhci_hcd
>  > [   29.648377] usb 3-7.1: device descriptor read/64, error -110
>  > [   45.520400] usb 3-7.1: device descriptor read/64, error -110
>  > [   45.624451] usb 3-7-port1: attempt power cycle
>  > [   45.738358] usb 3-13: new high-speed USB device number 9 using
>  xhci_hcd
>  > [   45.865929] usb 3-13: New USB device found, idVendor=05e3,
>  idProduct=0608, bcdDevice=32.98
>  > [   45.865939] usb 3-13: New USB device strings: Mfr=0, Product=1,
>  SerialNumber=0
>  > [   45.865942] usb 3-13: Product: USB2.0 Hub
>  > [   45.866653] hub 3-13:1.0: USB hub found
>  > [   45.866992] hub 3-13:1.0: 4 ports detected
>  > [   46.304365] usb 3-7.1: new high-speed USB device number 10 using
>  xhci_hcd
>  > [   56.160384] xhci_hcd 0000:00:14.0: Abort failed to stop command ring:
>  -110
>  > [   56.160384] xhci_hcd 0000:00:14.0: xHCI host controller not
>  responding, assume dead
>  > [   56.160384] xhci_hcd 0000:00:14.0: HC died; cleaning up
>  > [   56.488455] xhci_hcd 0000:00:14.0: Timeout while waiting for setup
>  device command
>  > [   56.488480] usb 4-2: USB disconnect, device number 2
>  > [   56.904366] usb 3-7.1: device not accepting address 10, error -108
>  > [   56.904412] usb 3-7-port1: couldn't allocate usb_device
>  > [   56.904464] usb usb3-port2: couldn't allocate usb_device
>  > [   56.904502] usb 3-13-port1: couldn't allocate usb_device
>  > [   56.904603] usb 3-3: USB disconnect, device number 2
>  > [   56.927819] usb 3-6: USB disconnect, device number 3
>  >
>  >
>  >
>  > _______________________________________________
>  > devel mailing list -- devel(a)lists.fedoraproject.org
>  > To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  > Fedora Code of Conduct:
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  > List Archives:
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>  > Do not reply to spam on the list, report it:
>  https://pagure.io/fedora-infrastructure
>
>
>
>  --
>  Stephen J Smoogen.
>  Let us be kind to one another, for most of us are fighting a hard
>  battle. -- Ian MacClaren
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct:
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it:
>  https://pagure.io/fedora-infrastructure
>

[Jason Montleon]

I have a similar system. lspci out looks near identical. The system was 
just booted this morning.

I normally run it headless with just power and network connected, but 
plugging in a USB mouse, thumb drive, and USB optical drive, they show 
up fine in dmesg and lsusb output using random USB ports on the front 
and back, as does the card reader on the front of the system. I mounted 
the thumb drive fine.

# dmidecode | grep -i Precision && uname -srvpi && lspci | grep USB
	Product Name: Precision Tower 7810
Linux 5.14.16-301.fc35.x86_64 #1 SMP Wed Nov 3 13:55:42 UTC 2021 x86_64 
x86_64
00:14.0 USB controller: Intel Corporation C610/X99 series chipset USB 
xHCI Host Controller (rev 05)
00:1a.0 USB controller: Intel Corporation C610/X99 series chipset USB 
Enhanced Host Controller #2 (rev 05)
00:1d.0 USB controller: Intel Corporation C610/X99 series chipset USB 
Enhanced Host Controller #1 (rev 05)


On 11/8/21 08:15, Sergio Pascual wrote:
>  
>  El lun, 8 nov 2021 a las 13:39, Stephen John Smoogen (<smooge(a)gmail.com 
>  <mailto:[e-mail]>>) escribió:
>  
>      On Mon, 8 Nov 2021 at 06:53, Sergio Pascual <sergio.pasra(a)gmail.com
>      <mailto:[e-mail]>> wrote:
>       >
>       > Hi, I upgraded my workstation to F35 last Friday, and today I
>      'dnf updated' and rebooted. After the reboot, all my USBs are
>      disabled. No mouse, no keyword.
>       > I know my hardware works because the keyboard works in grub, and
>      the light of my optical mouse in on until some errors appear in the
>      kernel during boot.
>       >
>       > I have tried:
>       > kernel-5.14.15-200.fc34.x86_64
>       > kernel-5.14.15-300.fc35.x86_64
>       > kernel-5.14.16-301.fc35.x86_64
>       >
>  
>      The developers will need to know what the exact motherboard/laptop
>      version and manufacturer you have in order to diagnose this issue. My
>      initial guess is that since the f34 kernel also fails, that the
>      problem is with a firmware module and whatever the motherboard is
>      expecting to use. [The fact that it is only finding USB2 says that
>      either the system is really old or that it is trying to fail to its
>      lowest working value.]
>  
>  
>  
>  
>  My workstation is a Dell Precision Tower 7910.
>  
>  lscpi says I have the following serial bus controllers
>  
>  00:14.0 USB controller: Intel Corporation C610/X99 series chipset USB 
>  xHCI Host Controller (rev 05)
>  00:1a.0 USB controller: Intel Corporation C610/X99 series chipset USB 
>  Enhanced Host Controller #2 (rev 05)
>  00:1d.0 USB controller: Intel Corporation C610/X99 series chipset USB 
>  Enhanced Host Controller #1 (rev 05)
>  
>  Regards
>  
>  
>       > without success.
>       > I'm getting messages like these:
>       >
>       > [   23.722355] usb 3-10: new high-speed USB device number 7 using
>      xhci_hcd
>       > [   23.857746] usb 3-10: New USB device found, idVendor=0bda,
>      idProduct=0184, bcdDevice=84.13
>       > [   23.857755] usb 3-10: New USB device strings: Mfr=1,
>      Product=2, SerialNumber=3
>       > [   23.857759] usb 3-10: Product: USB2.0-CRW
>       > [   23.857762] usb 3-10: Manufacturer: Generic
>       > [   23.857764] usb 3-10: SerialNumber: 20100818841300000
>       > [   24.016363] usb 3-7.1: new high-speed USB device number 8
>      using xhci_hcd
>       > [   29.648377] usb 3-7.1: device descriptor read/64, error -110
>       > [   45.520400] usb 3-7.1: device descriptor read/64, error -110
>       > [   45.624451] usb 3-7-port1: attempt power cycle
>       > [   45.738358] usb 3-13: new high-speed USB device number 9 using
>      xhci_hcd
>       > [   45.865929] usb 3-13: New USB device found, idVendor=05e3,
>      idProduct=0608, bcdDevice=32.98
>       > [   45.865939] usb 3-13: New USB device strings: Mfr=0,
>      Product=1, SerialNumber=0
>       > [   45.865942] usb 3-13: Product: USB2.0 Hub
>       > [   45.866653] hub 3-13:1.0: USB hub found
>       > [   45.866992] hub 3-13:1.0: 4 ports detected
>       > [   46.304365] usb 3-7.1: new high-speed USB device number 10
>      using xhci_hcd
>       > [   56.160384] xhci_hcd 0000:00:14.0: Abort failed to stop
>      command ring: -110
>       > [   56.160384] xhci_hcd 0000:00:14.0: xHCI host controller not
>      responding, assume dead
>       > [   56.160384] xhci_hcd 0000:00:14.0: HC died; cleaning up
>       > [   56.488455] xhci_hcd 0000:00:14.0: Timeout while waiting for
>      setup device command
>       > [   56.488480] usb 4-2: USB disconnect, device number 2
>       > [   56.904366] usb 3-7.1: device not accepting address 10, error -108
>       > [   56.904412] usb 3-7-port1: couldn't allocate usb_device
>       > [   56.904464] usb usb3-port2: couldn't allocate usb_device
>       > [   56.904502] usb 3-13-port1: couldn't allocate usb_device
>       > [   56.904603] usb 3-3: USB disconnect, device number 2
>       > [   56.927819] usb 3-6: USB disconnect, device number 3
>       >
>       >
>       >
>       > _______________________________________________
>       > devel mailing list -- devel(a)lists.fedoraproject.org
>      <mailto:[e-mail]>
>       > To unsubscribe send an email to
>      devel-leave(a)lists.fedoraproject.org
>      <mailto:[e-mail]>
>       > Fedora Code of Conduct:
>      https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>      <https://docs.fedoraproject.org/en-US/project/code-of-conduct/>
>       > List Guidelines:
>      https://fedoraproject.org/wiki/Mailing_list_guidelines
>      <https://fedoraproject.org/wiki/Mailing_list_guidelines>
>       > List Archives:
>      https://lists.fedoraproject.org/archives/list/[e-mail]
>      <https://lists.fedoraproject.org/archives/list/[e-mail].o...
>       > Do not reply to spam on the list, report it:
>      https://pagure.io/fedora-infrastructure
>      <https://pagure.io/fedora-infrastructure>
>  
>  
>  
>      -- 
>      Stephen J Smoogen.
>      Let us be kind to one another, for most of us are fighting a hard
>      battle. -- Ian MacClaren
>      _______________________________________________
>      devel mailing list -- devel(a)lists.fedoraproject.org
>      <mailto:[e-mail]>
>      To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>      <mailto:[e-mail]>
>      Fedora Code of Conduct:
>      https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>      <https://docs.fedoraproject.org/en-US/project/code-of-conduct/>
>      List Guidelines:
>      https://fedoraproject.org/wiki/Mailing_list_guidelines
>      <https://fedoraproject.org/wiki/Mailing_list_guidelines>
>      List Archives:
>      https://lists.fedoraproject.org/archives/list/[e-mail]
>      <https://lists.fedoraproject.org/archives/list/[e-mail].o...
>      Do not reply to spam on the list, report it:
>      https://pagure.io/fedora-infrastructure
>      <https://pagure.io/fedora-infrastructure>
>  
>  
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
>

[Stephen John Smoogen]

On Mon, 8 Nov 2021 at 08:16, Sergio Pascual <sergio.pasra(a)gmail.com&gt; wrote:
>  El lun, 8 nov 2021 a las 13:39, Stephen John Smoogen (<smooge(a)gmail.com>)
> escribió:
> >
> > On Mon, 8 Nov 2021 at 06:53, Sergio Pascual <sergio.pasra(a)gmail.com&gt; wrote:
> > >
> > > Hi, I upgraded my workstation to F35 last Friday, and today I 'dnf
> updated' and rebooted. After the reboot, all my USBs are disabled. No mouse, no
> keyword.
> > > I know my hardware works because the keyboard works in grub, and the light of my
> optical mouse in on until some errors appear in the kernel during boot.
> > >
> > > I have tried:
> > > kernel-5.14.15-200.fc34.x86_64
> > > kernel-5.14.15-300.fc35.x86_64
> > > kernel-5.14.16-301.fc35.x86_64
> > >
> >
> > The developers will need to know what the exact motherboard/laptop
> > version and manufacturer you have in order to diagnose this issue. My
> > initial guess is that since the f34 kernel also fails, that the
> > problem is with a firmware module and whatever the motherboard is
> > expecting to use. [The fact that it is only finding USB2 says that
> > either the system is really old or that it is trying to fail to its
> > lowest working value.]
> >
> >
>
>
>  My workstation is a Dell Precision Tower 7910.
>
>  lscpi says I have the following serial bus controllers
>
>  00:14.0 USB controller: Intel Corporation C610/X99 series chipset USB xHCI Host
> Controller (rev 05)
>  00:1a.0 USB controller: Intel Corporation C610/X99 series chipset USB Enhanced Host
> Controller #2 (rev 05)
>  00:1d.0 USB controller: Intel Corporation C610/X99 series chipset USB Enhanced Host
> Controller #1 (rev 05)
>  
Can you try downgrading to the F34 linux-firmware and see if the f34
kernel sees the chipset again?



-- 
Stephen J Smoogen.
Let us be kind to one another, for most of us are fighting a hard
battle. -- Ian MacClaren

[Sergio Pascual]

El lun, 8 nov 2021 a las 14:36, Stephen John Smoogen (<smooge(a)gmail.com>)
escribió:

>  Can you try downgrading to the F34 linux-firmware and see if the f34
>  kernel sees the chipset again?
>
>
>  
I have downgraded everything to the released F35 and now it works, with
kernel 5.14.16-301 and linux-firmware-20210919-125




>  --
>  Stephen J Smoogen.
>  Let us be kind to one another, for most of us are fighting a hard
>  battle. -- Ian MacClaren
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct:
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it:
>  https://pagure.io/fedora-infrastructure
>

[Pablo Sebastián Greco]

On 8/11/21 11:02, Sergio Pascual wrote:
>  El lun, 8 nov 2021 a las 14:36, Stephen John Smoogen 
>  (<smooge(a)gmail.com>) escribió:
>
>
>      Can you try downgrading to the F34 linux-firmware and see if the f34
>      kernel sees the chipset again?
>
>
>
>  I have downgraded everything to the released F35 and now it works, 
>  with kernel 5.14.16-301 and linux-firmware-20210919-125
>  
The fix for this problem is the difference between -300 and -301 (revert 
of 2 commits), which are already included in 5.14.17 too
>      -- 
>      Stephen J Smoogen.
>      Let us be kind to one another, for most of us are fighting a hard
>      battle. -- Ian MacClaren
>      _______________________________________________
>      devel mailing list -- devel(a)lists.fedoraproject.org
>      To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>      Fedora Code of Conduct:
>      https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>      List Guidelines:
>      https://fedoraproject.org/wiki/Mailing_list_guidelines
>      List Archives:
>      https://lists.fedoraproject.org/archives/list/[e-mail]
>      Do not reply to spam on the list, report it:
>      https://pagure.io/fedora-infrastructure
>  
Pablo.

[Sergio Pascual]

El lun, 8 nov 2021 a las 15:02, Sergio Pascual (<sergio.pasra(a)gmail.com>)
escribió:

>  El lun, 8 nov 2021 a las 14:36, Stephen John Smoogen (<smooge(a)gmail.com>)
>  escribió:
>
> >
> > Can you try downgrading to the F34 linux-firmware and see if the f34
> > kernel sees the chipset again?
> >  
> >
>  I have downgraded everything to the released F35 and now it works, with
>  kernel 5.14.16-301 and linux-firmware-20210919-125
>
>
>  
I have updated the system from F35 without updates to fully updated and the
problem has disappeared. I have updated in small groups of packages and
rebooted afterwards to check USB. Whatever happened, it is fixed now. My
current kernel is 5.14.16-301  but 5.15.15-300 works also

>

[Sergio Pascual]

El lun, 8 nov 2021 a las 19:01, Sergio Pascual (<sergio.pasra(a)gmail.com>)
escribió:

>  El lun, 8 nov 2021 a las 15:02, Sergio Pascual (<sergio.pasra(a)gmail.com>)
>  escribió:
>
> >
> >
> > El lun, 8 nov 2021 a las 14:36, Stephen John Smoogen (<smooge(a)gmail.com>)
> > escribió:
> >
> >>
> >> Can you try downgrading to the F34 linux-firmware and see if the f34
> >> kernel sees the chipset again?
> >>
> >>
> >>
> > I have downgraded everything to the released F35 and now it works, with
> > kernel 5.14.16-301 and linux-firmware-20210919-125
> >
> >
> >
>  I have updated the system from F35 without updates to fully updated and
>  the problem has disappeared. I have updated in small groups of packages and
>  rebooted afterwards to check USB. Whatever happened, it is fixed now. My
>  current kernel is 5.14.16-301  but 5.15.15-300 works also
>
> >
> >
>  
The problem with the missing usb reappeared again this morning. This time I
have installed kernel 5.14.13-300.fc35.x86_64, which fixes the problem.
Probably I'm suffering
https://bugzilla.redhat.com/show_bug.cgi?id=2019788  so at least I can
workaround the problem.

Thanks everyone!

[Peter Robinson]

On Mon, Nov 8, 2021 at 1:36 PM Stephen John Smoogen <smooge(a)gmail.com&gt; wrote:
>  On Mon, 8 Nov 2021 at 08:16, Sergio Pascual <sergio.pasra(a)gmail.com&gt; wrote:
>  >
>  >
>  > El lun, 8 nov 2021 a las 13:39, Stephen John Smoogen (<smooge(a)gmail.com>)
> escribió:
>  >>
>  >> On Mon, 8 Nov 2021 at 06:53, Sergio Pascual <sergio.pasra(a)gmail.com&gt;
> wrote:
>  >> >
>  >> > Hi, I upgraded my workstation to F35 last Friday, and today I 'dnf
> updated' and rebooted. After the reboot, all my USBs are disabled. No mouse, no
> keyword.
>  >> > I know my hardware works because the keyboard works in grub, and the light
> of my optical mouse in on until some errors appear in the kernel during boot.
>  >> >
>  >> > I have tried:
>  >> > kernel-5.14.15-200.fc34.x86_64
>  >> > kernel-5.14.15-300.fc35.x86_64
>  >> > kernel-5.14.16-301.fc35.x86_64
>  >> >
>  >>
>  >> The developers will need to know what the exact motherboard/laptop
>  >> version and manufacturer you have in order to diagnose this issue. My
>  >> initial guess is that since the f34 kernel also fails, that the
>  >> problem is with a firmware module and whatever the motherboard is
>  >> expecting to use. [The fact that it is only finding USB2 says that
>  >> either the system is really old or that it is trying to fail to its
>  >> lowest working value.]
>  >>
>  >>
>  >
>  >
>  > My workstation is a Dell Precision Tower 7910.
>  >
>  > lscpi says I have the following serial bus controllers
>  >
>  > 00:14.0 USB controller: Intel Corporation C610/X99 series chipset USB xHCI Host
> Controller (rev 05)
>  > 00:1a.0 USB controller: Intel Corporation C610/X99 series chipset USB Enhanced Host
> Controller #2 (rev 05)
>  > 00:1d.0 USB controller: Intel Corporation C610/X99 series chipset USB Enhanced Host
> Controller #1 (rev 05)
>  >
>
>  Can you try downgrading to the F34 linux-firmware and see if the f34
>  kernel sees the chipset again? 
Not sure what downgrading linux-firmware will do here a the Intel USB
controllers don't require firmware.

[Miroslav Suchý]

Dne 08. 11. 21 v 12:53 Sergio Pascual napsal(a):
>  Hi, I upgraded my workstation to F35 last Friday, and today I
> 'dnf updated' and rebooted. After the reboot, all my 
>  USBs are disabled. No mouse, no keyword.
>  I know my hardware works because the keyboard works in grub, and the light of my optical
> mouse in on until some errors 
>  appear in the kernel during boot.
>
>  I have tried:
>  kernel-5.14.15-200.fc34.x86_64
>  kernel-5.14.15-300.fc35.x86_64
>  kernel-5.14.16-301.fc35.x86_64
>
>  without success.
>  I'm getting messages like these: 
I had the same issue this morning (F35). Beside the `dnf upgrade` I upgraded the firmware
using LVFS. But after 3rd 
reboot and a pause for a breakfast the USB have started working.

I had no time to investigate it further. The symptoms were the same. USB keyboard worked
in the grub, but did not worked 
later (not even in luks decrypt). I will try to spend later some times on logs.

Miroslav

[Michael Cronenworth]

On 11/8/21 5:53 AM, Sergio Pascual wrote:
>  Hi, I upgraded my workstation to F35 last Friday, and today I
> 'dnf updated' and 
>  rebooted. After the reboot, all my USBs are disabled. No mouse, no keyword.
>  I know my hardware works because the keyboard works in grub, and the light of my 
>  optical mouse in on until some errors appear in the kernel during boot.
>
>  I have tried:
>  kernel-5.14.15-200.fc34.x86_64
>  kernel-5.14.15-300.fc35.x86_64
>  kernel-5.14.16-301.fc35.x86_64
>  
Maybe you're affected by this[1] guy?

[1] https://bugzilla.redhat.com/show_bug.cgi?id=2019788