I just did an update to my F33 Workstation install and now I can log in. I can't move the mouse pointer on the login screen. The keyboard doesn't appear to work either. Both are USB devices.
My login manager is GDM. I'm running Plasma as my desktop manager.
I don't think I have ssh enabled on that computer. How do I resolve this ?
On Thu, 4 Feb 2021 13:44:00 -0700 linux guy wrote:
How do I resolve this ?
First thing to try is unplugging and plugging back in the USB devices (or dongles if they are wireless).
If that doesn't work, try plugging them into a different USB port.
If that doesn't work, I guess power cycling is the only thing to try if you can't cleanly reboot.
On Thu, Feb 4, 2021 at 1:51 PM Tom Horsley horsley1953@gmail.com wrote:
On Thu, 4 Feb 2021 13:44:00 -0700 linux guy wrote:
How do I resolve this ?
First thing to try is unplugging and plugging back in the USB devices (or dongles if they are wireless).
If that doesn't work, try plugging them into a different USB port.
If that doesn't work, I guess power cycling is the only thing to try if you can't cleanly reboot. ________________________________________
I've done all those things. I also tried booting with every kernel that is installed on my computer.
Is anyone else having this problem ?
On Thu, Feb 04, 2021 at 01:53:59PM -0700, linux guy wrote:
I've done all those things. I also tried booting with every kernel that is installed on my computer.
So the GRUB screen responds to key-presses, just not the fully booted OS? Can you tell it to boot into text mode (adding systemd.unit=multi-user.target to the kernel line)? Does the keyboard work then?
I was able to edit the kernel boot line in the grub editor. My system booted to a system login prompt. My keyboard does not work. I cannot type a user name to log in.
On Thu, Feb 4, 2021 at 2:01 PM linux guy linuxguy123@gmail.com wrote:
So the GRUB screen responds to key-presses, just not the fully booted
That is correct.
OS? Can you tell it to boot into text mode (adding
systemd.unit=multi-user.target to the kernel line)?
I can.
Does the keyboard
work then?
Standby wile I test that.
I updated and rebooted my system in the first place because a USB hard drive I was using wasn't responding.
My motherboard (Asus TUF Wifi X570) has a PS/2 connector on it. But I do not have a PS/2 keyboard ! I used to... but I think it is long gone. I'll check.
On Thu, Feb 04, 2021 at 02:13:15PM -0700, linux guy wrote:
I updated and rebooted my system in the first place because a USB hard drive I was using wasn't responding.
That sounds like your USB bus might be having problems.
Have you tried the keyboard in every USB port on your system?
That sounds like your USB bus might be having problems.
I agree, that is what it looks like. The physical USB bus seems to be fine as the keyboard works in the grub editor. This appears to be a USB bus software issue.
Have you tried the keyboard in every USB port on your system?
I just tried a wired USB keyboard in several ports. No joy. I have also tried my wireless USB keyboard in several ports. No joy.
Am I the only one experiencing this ? If this is a global problem a lot of people are going to be affected !
I got the wired USB keyboard working by plugging it straight into a USB2 port. Standby for more testing.
On Thu, 4 Feb 2021 14:13:15 -0700 linux guy wrote:
I updated and rebooted my system in the first place because a USB hard drive I was using wasn't responding.
Maybe the USB hardware is dead. I have an old computer where none of the USB ports work (and the onboard video also doesn't work, I think perhaps they are on the same dead chipset).
Maybe the USB hardware is dead. I have an old computer where none of the USB ports work (and the onboard video also doesn't work, I think perhaps they are on the same dead chipset).
The keyboard works fine during early boot. I can edit in the grub editor just fine.
My *guess* is that there is an issue in the USB3 software stack somewhere. FYI, I updated from /stable.
On Thu, Feb 04, 2021 at 02:06:59PM -0700, linux guy wrote:
I was able to edit the kernel boot line in the grub editor. My system booted to a system login prompt. My keyboard does not work. I cannot type a user name to log in.
So, since it seems to be OK during GRUB but not once the kernel boots, I wonder if you somehow either blacklisted the USB keyboard driver. The USB keyboard driver is in-kernel, (CONFIG_USB_HID=y) so it can't be a broken modules file.
At this point, I would try booting off a USB livecd image to see if it doesn't work for other kernels too. It seems unlikely to be the kernel though, since it used to work with older kernels. It points to a local configuration change to me.
On Thu, 4 Feb 2021 16:15:39 -0500 Jonathan Billings wrote:
It points to a local configuration change to me.
I do remember seeing USB related BIOS settings on systems, maybe one of them got changed somehow.
It points to a local configuration change to me.
I do remember seeing USB related BIOS settings on systems, maybe one of them got changed somehow.
No changes, hardware or BIOS, have been made to the computer. Uptime was days to a week, can't remember the last time I rebooted. All software updates have been from F33/stable.
I'm logged into the console session. I am going to reboot to plasma, to see what happens.
I am now logged into my plasma session using a wired keyboard and a wired mouse, using USB ports that were not previously used.
I am available to troubleshoot anything the community wants. Fire away with your questions.
On 2/4/21 1:30 PM, linux guy wrote:
I am now logged into my plasma session using a wired keyboard and a wired mouse, using USB ports that were not previously used.
sounds more of a usb port or bus issue.
The keyboard and USB port worked fine during boot up. I was able to edit the kernel command line in grub without any issue.
This is not a hardware issue. Something changes in the software during the boot process.
The USB hard drive that is on the other USB bus does not connect to my computer. Nor does anything else connected to that bus. But a keyboard connected to that bus works during boot up.
$ lsusb Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 003: ID 04f2:0402 Chicony Electronics Co., Ltd Genius LuxeMate i200 Keyboard Bus 005 Device 002: ID 192f:0916 Avago Technologies, Pte. ADNS-2710 Optical Mouse Controller Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 003: ID 0b05:18f3 ASUSTek Computer, Inc. AURA LED Controller Bus 003 Device 002: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I think there is an issue with the USB3 driver.
On 2/4/21 1:41 PM, linux guy wrote:
This is not a hardware issue. Something changes in the software during the boot process.
my initial thought was probably slow keys were enabled.
my initial thought was probably slow keys were enabled. https://forum.kde.org/viewtopic.php?f=66&t=36625
Slowkeys is not enabled. This is NOT keyboard specific. It is affecting a USB hub, flash drive and USB IDE hard drive.
This issue seems to affect all devices connected to my USB3 ports. USB2 ports appear to work OK. Might be a coincidence though.
One other symptom: the power lights on my USB wired keyboard did not light up when I was plugging it into the USB3 ports. They now light up when plugged into the USB2 port.
On 2/4/21 2:00 PM, linux guy wrote:
One other symptom: the power lights on my USB wired keyboard did not light up when I was plugging it into the USB3 ports. They now light up when plugged into the USB2 port.
lsusb -t shows physical usb device hierarchy as a tree. this may help to narrow down the issue.
https://www.blackmoreops.com/2014/08/25/identify-pci-usb-wired-wireless-driv...
Ask and you shall receive.
$ lsusb -t /: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 2: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M |__ Port 5: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 5: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M |__ Port 6: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M |__ Port 6: Dev 3, If 2, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
The only working USB devices on this computer are the wired USB keyboard and the wired USB mouse. Not sure which they are in the tree above, I don't want to unplug anything at the moment as I'm getting work done.
did you check to ensure that any extension USB cable being used is rated for USB3?
On Thu, Feb 4, 2021 at 2:18 PM linux guy linuxguy123@gmail.com wrote:
The only working USB devices on this computer are the wired USB keyboard and the wired USB mouse. Not sure which they are in the tree above, I don't want to unplug anything at the moment as I'm getting work done.
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@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/users@lists.fedoraproject.org
I can ping the computer and it responds.
I can't ssh into it. Connection refused. Looks like I closed port 22, which is what I normally do.
Ideas ?
Do you happen to have usbguard activated?
If that is the case, you may need to grant the access all the keyboards and mices you may need to plugin.
On Fri, Feb 5, 2021 at 8:33 AM Samuel Sieb samuel@sieb.net wrote:
On 2/4/21 12:58 PM, linux guy wrote:
I can ping the computer and it responds.
I can't ssh into it. Connection refused. Looks like I closed port 22, which is what I normally do.
Workstation defaults to having ssh disabled. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@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/users@lists.fedoraproject.org
I have a USB2 hub attached to my computer. It was connected to a USB3 port. I moved it to a USB2 port and how all my USB devices work. None of them are connected to a USB3 port.
$ lsusb Bus 006 Device 004: ID 0951:1666 Kingston Technology DataTraveler 100 G3/G4/SE9 G2/50 Bus 006 Device 003: ID 152d:0551 JMicron Technology Corp. / JMicron USA Technology Corp. JMS551 SuperSpeed two ports SATA 3Gb/s br idge Bus 006 Device 002: ID 2109:0810 VIA Labs, Inc. VL81x Hub Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 003: ID 04f2:0402 Chicony Electronics Co., Ltd Genius LuxeMate i200 Keyboard Bus 005 Device 005: ID 192f:0916 Avago Technologies, Pte. ADNS-2710 Optical Mouse Controller Bus 005 Device 004: ID 2109:3431 VIA Labs, Inc. Hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 003: ID 0b05:18f3 ASUSTek Computer, Inc. AURA LED Controller Bus 003 Device 002: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
$ lsusb -t /: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 5000M |__ Port 1: Dev 3, If 0, Class=Mass Storage, Driver=usb-storage, 5000M |__ Port 4: Dev 4, If 0, Class=Mass Storage, Driver=usb-storage, 5000M /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 1: Dev 4, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 2: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 2: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M |__ Port 5: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 5: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M |__ Port 6: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M |__ Port 6: Dev 3, If 2, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M
On Thu, 4 Feb 2021 18:56:27 -0700 linux guy wrote:
I have a USB2 hub attached to my computer. It was connected to a USB3 port. I moved it to a USB2 port and how all my USB devices work. None of them are connected to a USB3 port.
That sounds a lot like the same hardware failure I have on my old P8H67-V (AUSTek) system. I just tested it again, and the USB3 ports will work with a single simple device plugged in (like a USB keyboard, which is what I tried), but a hub, or a device which actually wants to talk USB3 (like a disk drive) doesn't work. I'm assuming the southbridge chip (or whatever it is called) is dead or at least half dead. The USB2 ports do work.
The other hardware failure on this is the onboard Intel video which I guess must use the same half dead chip.
It can still limp along as long as I don't try to use the stuff that doesn't work, so it is an emergency backup system with a mirror of my main system so I can use it if my main system dies.
On Thu, Feb 4, 2021 at 7:28 PM Tom Horsley horsley1953@gmail.com wrote:
That sounds a lot like the same hardware failure I have on my old P8H67-V (AUSTek) system. I just tested it again, and the USB3 ports will work with a single simple device plugged in (like a USB keyboard, which is what I tried), but a hub, or a device which actually wants to talk USB3 (like a disk drive) doesn't work.
It worked fine up until I rebooted with a new kernel this afternoon. So if it is a hardware failure, it has worked perfectly since I got the board a year ago and failed after I updated and rebooted this afternoon. Can't say that didn't happen, but it seems really co-incidental.
I'm assuming the southbridge chip (or whatever it is called)
is dead or at least half dead.
X570 is an AMD AM4 motherboard. I'm running a Ryzen 3600X processor. System has been rock solid since I fixed a power supply issue a few months ago.
The USB2 ports do work.
The other hardware failure on this is the onboard Intel video which I guess must use the same half dead chip.
I have an NVIDIA GTX 1080 Ti video card.
On Thu, 4 Feb 2021 19:34:01 -0700 linux guy wrote:
It worked fine up until I rebooted with a new kernel this afternoon.
Hardware is well known to wait for a software upgrade to break in order to maximize confusion :-).
Do you have the external hub plugged into its own power? Or is it just drawing power from usb?
You might try booting into the previous kernel and doing a quick test, if it works there, then it is may be a new feature enforcing something that might have happened or work, or it may simply be a a kernel bug.
The standards on usb say how things are supposed to work, but often until ignoring the standards translates to a bug, no one enforces it in software. It could be doing a power calculation and determined there is not enough power based on what the devices say they need and how they are wired, and disabling anything over the power limit. Likely whatever gets seen first gets the power(or other resource) and anyone later won't get turned on. I know that the usb bus does this on the bandwidth a device claims to need, because of that you cannot run 2 webcams on the same usb bus that each want 80% of the bandwidth to run. The 2nd one will not be allowed to work. And most motherboards only really have 2-3 real usb ports with all of the ports really coming from internal hubs.
On Thu, Feb 4, 2021 at 8:34 PM linux guy linuxguy123@gmail.com wrote:
On Thu, Feb 4, 2021 at 7:28 PM Tom Horsley horsley1953@gmail.com wrote:
That sounds a lot like the same hardware failure I have on my old P8H67-V (AUSTek) system. I just tested it again, and the USB3 ports will work with a single simple device plugged in (like a USB keyboard, which is what I tried), but a hub, or a device which actually wants to talk USB3 (like a disk drive) doesn't work.
It worked fine up until I rebooted with a new kernel this afternoon. So if it is a hardware failure, it has worked perfectly since I got the board a year ago and failed after I updated and rebooted this afternoon. Can't say that didn't happen, but it seems really co-incidental.
I'm assuming the southbridge chip (or whatever it is called) is dead or at least half dead.
X570 is an AMD AM4 motherboard. I'm running a Ryzen 3600X processor. System has been rock solid since I fixed a power supply issue a few months ago.
The USB2 ports do work.
The other hardware failure on this is the onboard Intel video which I guess must use the same half dead chip.
I have an NVIDIA GTX 1080 Ti video card.
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@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/users@lists.fedoraproject.org
On 2/4/21 12:44 PM, linux guy wrote:
I just did an update to my F33 Workstation install and now I can log in. I can't move the mouse pointer on the login screen. The keyboard doesn't appear to work either. Both are USB devices.
My login manager is GDM. I'm running Plasma as my desktop manager.
At login hold shift key for about 10 seconds to see if that response?
On 2/4/21 5:28 PM, linux guy wrote:
Have you tried booting an earlier kernel?
Yes. The behavior was consistent across the 3 kernels I had installed. uname -a Linux bigboy 5.10.11-200.fc33.x86_64 #1 SMP Wed Jan 27 20:21:22 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
If it's not working now on a kernel version that did work before, that suggests that it's more likely to be a hardware issue than a kernel issue.
Does anything show up in the journal when you plug something into the ports that aren't working?
Since it appears to be USB3 ports that aren't working, try adding "blacklist=xhci_hcd" to the kernel command line before booting and see if that makes any difference. I don't know if that will do anything since Fedora has that kernel driver compiled in, it's not a module. So if it doesn't work, try "initcall_blacklist=xhci_init_driver" instead.
On Thu, Feb 4, 2021 at 7:16 PM Samuel Sieb samuel@sieb.net wrote:
On 2/4/21 5:28 PM, linux guy wrote:
Have you tried booting an earlier kernel?
Yes. The behavior was consistent across the 3 kernels I had installed. uname -a Linux bigboy 5.10.11-200.fc33.x86_64 #1 SMP Wed Jan 27 20:21:22 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
If it's not working now on a kernel version that did work before, that suggests that it's more likely to be a hardware issue than a kernel issue.
Does anything show up in the journal when you plug something into the ports that aren't working?
Since it appears to be USB3 ports that aren't working, try adding "blacklist=xhci_hcd" to the kernel command line before booting and see if that makes any difference. I don't know if that will do anything since Fedora has that kernel driver compiled in, it's not a module. So if it doesn't work, try "initcall_blacklist=xhci_init_driver" instead. _______________________________________________
I'll test this tomorrow.