Latest zypper dup turned off all rear usb ports:
I just zypper dup this morning on openSUSE Tumbleweed. Then I powercycled, logged into KDE - no mouse connectivity. Moved usb mouse to front usb port on the desktop now mouse is picked up and works. What happened here and how can this be fixed?
Thinkcentre-M57p:~> lsusb Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 006: ID 03f0:140c HP, Inc HP Wireless Keyboard Kit Bus 001 Device 008: ID 17ef:608d Lenovo Optical Mouse Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub On 1/18/24 07:10, -pj wrote:
I just zypper dup this morning on openSUSE Tumbleweed. Then I powercycled, logged into KDE - no mouse connectivity. Moved usb mouse to front usb port on the desktop now mouse is picked up and works. What happened here and how can this be fixed?
I have attached another drive to the machine. In the process I was receiving an annoying POST message of 'system configuration changed' press any key to resume then a beep. I decided to go into BIOS and add the additional drive to the second boot device list.I saved then exited - then no rear usb. Anyways I figured to look at the usb ports setting in BIOS and sure enough they were set to disabled. I have absolutely *no* idea why this occurred but I set the rear usb ports back to an enabled state. The rear usb ports appear to be functional once again. I wrote back on this issue as soon as possible to prevent anyone from wasting their time in the case to render assistance. -Best Regards🤐 On 1/18/24 07:21, -pj wrote:
Thinkcentre-M57p:~> lsusb Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 006: ID 03f0:140c HP, Inc HP Wireless Keyboard Kit Bus 001 Device 008: ID 17ef:608d Lenovo Optical Mouse Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
On 1/18/24 07:10, -pj wrote:
I just zypper dup this morning on openSUSE Tumbleweed. Then I powercycled, logged into KDE - no mouse connectivity. Moved usb mouse to front usb port on the desktop now mouse is picked up and works. What happened here and how can this be fixed?
In data giovedì 18 gennaio 2024 15:06:19 CET, -pj ha scritto:
I have attached another drive to the machine. In the process I was receiving an annoying POST message of 'system configuration changed' press any key to resume then a beep. I decided to go into BIOS and add the additional drive to the second boot device list.I saved then exited - then no rear usb. Anyways I figured to look at the usb ports setting in BIOS and sure enough they were set to disabled. I have absolutely *no* idea why this occurred but I set the rear usb ports back to an enabled state. The rear usb ports appear to be functional once again. I wrote back on this issue as soon as possible to prevent anyone from wasting their time in the case to render assistance.
-Best Regards🤐
On 1/18/24 07:21, -pj wrote:
Thinkcentre-M57p:~> lsusb Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 006: ID 03f0:140c HP, Inc HP Wireless Keyboard Kit Bus 001 Device 008: ID 17ef:608d Lenovo Optical Mouse Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
On 1/18/24 07:10, -pj wrote:
I just zypper dup this morning on openSUSE Tumbleweed. Then I powercycled, logged into KDE - no mouse connectivity. Moved usb mouse to front usb port on the desktop now mouse is picked up and works. What happened here and how can this be fixed?
You actually see that only three devices are recognized with correct ID currently. By hearing your description I have the doubt that the kernel firmware package was updated and had not reached the mirror (you should have received a warning if you do consistency checks on your installs, but maybe zypper doesn't by default) or was not correctly installed. My first take would be do a zypper clean, then ref then dup to see if something comes up and then control if your kernel firmware file is installed as expected. Note: on my machine the mouse is never recognized during startup if not attached to the foreseen rear usb outlet. That is, if attached to the hub, you have to detach and reattach at running system to get it working. Finally once updated and controlled all packages you may try to run # dracut -f as such you force to restore initramfs (formerly that was the now deprecated mkinitrd). this is all what come to my mind, hope that may come to some usefulness. Regards.
Thanks for your message, it was useful information. For some reason the rear usb ports were shut of in BIOS settings. I was not understanding that mkinitrd was for certain deprecated either. dracut -f Knowing now can be used to force restore initramsfs, that they are not two separate things that different commands need to be issued to do. -Thanks On 01-21-2024 03:20AM, Stakanov wrote:
In data giovedì 18 gennaio 2024 15:06:19 CET, -pj ha scritto:
I have attached another drive to the machine. In the process I was receiving an annoying POST message of 'system configuration changed' press any key to resume then a beep. I decided to go into BIOS and add the additional drive to the second boot device list.I saved then exited - then no rear usb. Anyways I figured to look at the usb ports setting in BIOS and sure enough they were set to disabled. I have absolutely *no* idea why this occurred but I set the rear usb ports back to an enabled state. The rear usb ports appear to be functional once again. I wrote back on this issue as soon as possible to prevent anyone from wasting their time in the case to render assistance.
-Best Regards🤐
On 1/18/24 07:21, -pj wrote:
Thinkcentre-M57p:~> lsusb Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 006: ID 03f0:140c HP, Inc HP Wireless Keyboard Kit Bus 001 Device 008: ID 17ef:608d Lenovo Optical Mouse Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
On 1/18/24 07:10, -pj wrote:
I just zypper dup this morning on openSUSE Tumbleweed. Then I powercycled, logged into KDE - no mouse connectivity. Moved usb mouse to front usb port on the desktop now mouse is picked up and works. What happened here and how can this be fixed? You actually see that only three devices are recognized with correct ID currently. By hearing your description I have the doubt that the kernel firmware package was updated and had not reached the mirror (you should have received a warning if you do consistency checks on your installs, but maybe zypper doesn't by default) or was not correctly installed. My first take would be do a zypper clean, then ref then dup to see if something comes up and then control if your kernel firmware file is installed as expected.
Note: on my machine the mouse is never recognized during startup if not attached to the foreseen rear usb outlet. That is, if attached to the hub, you have to detach and reattach at running system to get it working. Finally once updated and controlled all packages you may try to run
# dracut -f
as such you force to restore initramfs (formerly that was the now deprecated mkinitrd).
this is all what come to my mind, hope that may come to some usefulness.
Regards.
participants (2)
-
-pj -
Stakanov