Wired mouse and keyboard stop working after boot

Post here if you are a new Porteus member and you're looking for some help.
PuranaPaapi
White ninja
White ninja
Posts: 7
Joined: 24 Nov 2023, 12:12
Distribution: 5.01 KDE

Wired mouse and keyboard stop working after boot

Post#1 by PuranaPaapi » 24 Nov 2023, 12:36

I am running Porteus 5.01, installed to FAT32 USB via Windows.
My regular gaming mouse and keyboard (both wired) are attached to the PC via a 2 way USB switching hub which is connected to 2 PCs out of which 1 PC is being used to run Porteus.
I am able to boot to the Porteus desktop and the lights on my regular keyboard and mouse are glowing.
As soon as I move the wired mouse, the keyboard and mouse work for about 2-3 seconds (mouse pointer moves on screen) after which the RGB lighting on them turns off and they stop working.
After that I have to use a logitech wireless keyboard and mouse combo via receiver plugged into another vacant USB port.
Please help me to run the regular gaming mouse and keyboard on Porteus

User avatar
Rava
Contributor
Contributor
Posts: 5416
Joined: 11 Jan 2011, 02:46
Distribution: XFCE 5.01 x86_64 + 4.0 i586
Location: Forests of Germany

Wired mouse and keyboard stop working after boot

Post#2 by Rava » 26 Nov 2023, 06:42

Can you please post the relevant parts of your /var/log/messages (NOT the whole file, just the recent part when a possible disconnect of an USB device is mentioned)
You have to be root to be able to look into /var/log/messages

You can see as which USB device your mouse and your keyboard are connected by looking for details like so:

I just plugged out my USB IBM optical cable mouse and plug it in again to give you an idea what I am talking about (disregard that the mouse itself is branded as IBM but is named differently by the system)

Code: Select all

Nov 26 07:39:43 porteus kernel: usb 2-1.2.3: USB disconnect, device number 14
Nov 26 07:39:46 porteus kernel: usb 2-1.2.3: new low-speed USB device number 16 using ehci-pci
Nov 26 07:39:46 porteus kernel: usb 2-1.2.3: New USB device found, idVendor=0461, idProduct=4d03, bcdDevice= 0.10
Nov 26 07:39:46 porteus kernel: usb 2-1.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Nov 26 07:39:46 porteus kernel: usb 2-1.2.3: Product: USB 3D Mouse
Nov 26 07:39:46 porteus kernel: usb 2-1.2.3: Manufacturer: ARROW STRONG
Nov 26 07:39:46 porteus kernel: input: ARROW STRONG USB 3D Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2.3/2-1.2.3:1.0/0003:0461:4D03.000A/input/input26
Nov 26 07:39:46 porteus kernel: hid-generic 0003:0461:4D03.000A: input,hidraw2: USB HID v1.00 Mouse [ARROW STRONG USB 3D Mouse] on usb-0000:00:1d.0-1.2.3/input0
Nov 26 07:39:46 porteus mtp-probe: checking bus 2, device 16: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2.3" 
Nov 26 07:39:46 porteus mtp-probe: bus: 2, device: 16 was not an MTP device 
usb 2-1.2.3 and /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2.3 is how my system addresses that mouse, meaning when you use as root less to look into /var/log/messages you could search for "2-1.2.3" to see more entries about that device. Repeat similar task for the keyboard.

In case you are unfamiliar how to search for patterns and how to browse files via less, ask

Code: Select all

man less
. :)

Also, do you have more modules loaded or only the ones from base/ ?

HTH.
Cheers!
Yours Rava

PuranaPaapi
White ninja
White ninja
Posts: 7
Joined: 24 Nov 2023, 12:12
Distribution: 5.01 KDE

Wired mouse and keyboard stop working after boot

Post#3 by PuranaPaapi » 27 Nov 2023, 05:35

Thank you for the time and effort for helping me. Below are the contents of /var/log/messages. (all actions done as root user)

1. After fresh boot, when USB HUB is connected to PC

Nov 27 10:01:52 porteus kernel: usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
Nov 27 10:01:52 porteus kernel: usb 2-1: New USB device found, idVendor=05e3, idProduct=0626, bcdDevice= 6.56
Nov 27 10:01:52 porteus kernel: usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Nov 27 10:01:52 porteus kernel: usb 2-1: Product: USB3.1 Hub
Nov 27 10:01:52 porteus kernel: usb 2-1: Manufacturer: GenesysLogic
Nov 27 10:01:52 porteus kernel: hub 2-1:1.0: USB hub found
Nov 27 10:01:52 porteus kernel: hub 2-1:1.0: 4 ports detected
Nov 27 10:01:52 porteus kernel: usb 1-1.1: new high-speed USB device number 5 using xhci_hcd
Nov 27 10:01:52 porteus kernel: usb 1-1.1: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice= 6.56
Nov 27 10:01:52 porteus kernel: usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Nov 27 10:01:52 porteus kernel: usb 1-1.1: Product: USB2.1 Hub
Nov 27 10:01:52 porteus kernel: usb 1-1.1: Manufacturer: GenesysLogic
Nov 27 10:01:52 porteus kernel: hub 1-1.1:1.0: USB hub found
Nov 27 10:01:52 porteus kernel: hub 1-1.1:1.0: 4 ports detected


2. Then GAMING MOUSE is connected to HUB

Nov 27 10:03:46 porteus kernel: usb 1-1.1.3: new low-speed USB device number 6 using xhci_hcd
Nov 27 10:03:46 porteus kernel: usb 1-1.1.3: New USB device found, idVendor=1bcf, idProduct=08a0, bcdDevice= 1.04
Nov 27 10:03:46 porteus kernel: usb 1-1.1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov 27 10:03:46 porteus mtp-probe: checking bus 1, device 6: "/sys/devices/pci0000:00/0000:00:02.3/0000:05:00.0/usb1/1-1/1-1.1/1-1.1.3"
Nov 27 10:03:46 porteus mtp-probe: bus: 1, device: 6 was not an MTP device
Nov 27 10:03:46 porteus kernel: input: HID 1bcf:08a0 Mouse as /devices/pci0000:00/0000:00:02.3/0000:05:00.0/usb1/1-1/1-1.1/1-1.1.3/1-1.1.3:1.0/0003:1BCF:08A0.0006/input/input23
Nov 27 10:03:46 porteus kernel: input: HID 1bcf:08a0 Keyboard as /devices/pci0000:00/0000:00:02.3/0000:05:00.0/usb1/1-1/1-1.1/1-1.1.3/1-1.1.3:1.0/0003:1BCF:08A0.0006/input/input24
Nov 27 10:03:46 porteus kernel: input: HID 1bcf:08a0 as /devices/pci0000:00/0000:00:02.3/0000:05:00.0/usb1/1-1/1-1.1/1-1.1.3/1-1.1.3:1.0/0003:1BCF:08A0.0006/input/input25
Nov 27 10:03:46 porteus kernel: hid-generic 0003:1BCF:08A0.0006: input,hiddev97,hidraw5: USB HID v1.10 Mouse [HID 1bcf:08a0] on usb-0000:05:00.0-1.1.3/input0
Nov 27 10:03:46 porteus elogind-daemon[1051]: Watching system buttons on /dev/input/event12 (HID 1bcf:08a0 Keyboard)

3. As soon as I move the mouse, the mouse works for about 2-3 seconds (mouse pointer moves on screen) after which the RGB lighting on it turns off and it stops working.
4. Now gaming keyboard is connected to hub, there is no activity in /var/log/messages
5. With the mouse and keyboard connected to HUB, I reconnect the HUB to the PC - no activity again.
6. Unplug hub from PC. Reboot system.

7. GAMING KEYBOARD DIRECTLY CONNECTED TO PC

Nov 27 10:28:23 porteus kernel: usb 1-1.3: new full-speed USB device number 5 using xhci_hcd
Nov 27 10:28:23 porteus kernel: usb 1-1.3: New USB device found, idVendor=04d9, idProduct=a1cd, bcdDevice= 1.02
Nov 27 10:28:23 porteus kernel: usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Nov 27 10:28:23 porteus kernel: usb 1-1.3: Product: Gaming keyboard
Nov 27 10:28:23 porteus kernel: usb 1-1.3: Manufacturer: HTLTEK
Nov 27 10:28:23 porteus kernel: input: HTLTEK Gaming keyboard as /devices/pci0000:00/0000:00:02.3/0000:05:00.0/usb1/1-1/1-1.3/1-1.3:1.0/0003:04D9:A1CD.0008/input/input28
Nov 27 10:28:23 porteus kernel: hid-generic 0003:04D9:A1CD.0008: input,hidraw5: USB HID v1.10 Keyboard [HTLTEK Gaming keyboard] on usb-0000:05:00.0-1.3/input0
Nov 27 10:28:23 porteus kernel: input: HTLTEK Gaming keyboard as /devices/pci0000:00/0000:00:02.3/0000:05:00.0/usb1/1-1/1-1.3/1-1.3:1.1/0003:04D9:A1CD.0009/input/input29
Nov 27 10:28:23 porteus kernel: input: HTLTEK Gaming keyboard Consumer Control as /devices/pci0000:00/0000:00:02.3/0000:05:00.0/usb1/1-1/1-1.3/1-1.3:1.1/0003:04D9:A1CD.0009/input/input30
Nov 27 10:28:23 porteus kernel: hid-generic 0003:04D9:A1CD.0009: input,hiddev97,hidraw6: USB HID v1.10 Device [HTLTEK Gaming keyboard] on usb-0000:05:00.0-1.3/input1
Nov 27 10:28:23 porteus kernel: hid-generic 0003:04D9:A1CD.000A: hiddev98,hidraw7: USB HID v1.10 Device [HTLTEK Gaming keyboard] on usb-0000:05:00.0-1.3/input2
Nov 27 10:28:23 porteus kernel: input: HTLTEK Gaming keyboard as /devices/pci0000:00/0000:00:02.3/0000:05:00.0/usb1/1-1/1-1.3/1-1.3:1.3/0003:04D9:A1CD.000B/input/input31
Nov 27 10:28:23 porteus kernel: hid-generic 0003:04D9:A1CD.000B: input,hidraw8: USB HID v1.10 Mouse [HTLTEK Gaming keyboard] on usb-0000:05:00.0-1.3/input3
Nov 27 10:28:23 porteus mtp-probe: checking bus 1, device 5: "/sys/devices/pci0000:00/0000:00:02.3/0000:05:00.0/usb1/1-1/1-1.3"
Nov 27 10:28:23 porteus mtp-probe: bus: 1, device: 5 was not an MTP device
Nov 27 10:28:23 porteus elogind-daemon[1111]: Watching system buttons on /dev/input/event5 (HTLTEK Gaming keyboard)
Nov 27 10:28:23 porteus elogind-daemon[1111]: Watching system buttons on /dev/input/event12 (HTLTEK Gaming keyboard Consumer Control)
Nov 27 10:28:59 porteus NetworkManager[1257]: <info> [1701080939.0716] device (wlan0): set-hw-addr: set MAC address to AA:9A:86:AC:54:63 (scanning)
Nov 27 10:28:59 porteus NetworkManager[1257]: <info> [1701080939.1380] device (wlan0): supplicant interface state: disconnected -> interface_disabled
Nov 27 10:28:59 porteus NetworkManager[1257]: <info> [1701080939.1381] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> interface_disabled
Nov 27 10:28:59 porteus NetworkManager[1257]: <info> [1701080939.1445] device (wlan0): supplicant interface state: interface_disabled -> inactive
Nov 27 10:28:59 porteus NetworkManager[1257]: <info> [1701080939.1445] device (p2p-dev-wlan0): supplicant management interface state: interface_disabled -> inactive

8. GAMING MOUSE directly connected to PC.(activity same as point no. 2 above)

9. The keyboard and mouse work fine when connected directly. They don't work when connected via the HUB.

List of modules:
A. Base modules
1. kernel.xzm
2. core.xzm
3. xorg.xzm
4. xtra.xzm
5. kde5.xzm
B. Modules
1. google chrome (downloaded using browser selection and update tool)
2. changes (created using Porteus setting centre)
3. psc-settings (created using Porteus setting centre)

User avatar
Ed_P
Contributor
Contributor
Posts: 8374
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Wired mouse and keyboard stop working after boot

Post#4 by Ed_P » 27 Nov 2023, 05:45

I suspect the hub isn't supplying enough voltage.
Ed

User avatar
Rava
Contributor
Contributor
Posts: 5416
Joined: 11 Jan 2011, 02:46
Distribution: XFCE 5.01 x86_64 + 4.0 i586
Location: Forests of Germany

Wired mouse and keyboard stop working after boot

Post#5 by Rava » 27 Nov 2023, 21:00

Ed_P wrote:
27 Nov 2023, 05:45
I suspect the hub isn't supplying enough voltage.
That could be the issue.

Some hubs can have the ability to plug in external 5V power, but I guess your hub, PuranaPaapi, doesn't have that?
Cheers!
Yours Rava

User avatar
Ed_P
Contributor
Contributor
Posts: 8374
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Wired mouse and keyboard stop working after boot

Post#6 by Ed_P » 27 Nov 2023, 23:16

Or maybe too many hubs.
PuranaPaapi wrote:
27 Nov 2023, 05:35
Nov 27 10:01:52 porteus kernel: usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
Nov 27 10:01:52 porteus kernel: usb 2-1: New USB device found, idVendor=05e3, idProduct=0626, bcdDevice= 6.56
Nov 27 10:01:52 porteus kernel: usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Nov 27 10:01:52 porteus kernel: usb 2-1: Product: USB3.1 Hub
Nov 27 10:01:52 porteus kernel: usb 2-1: Manufacturer: GenesysLogic
Nov 27 10:01:52 porteus kernel: hub 2-1:1.0: USB hub found
Nov 27 10:01:52 porteus kernel: hub 2-1:1.0: 4 ports detected
Nov 27 10:01:52 porteus kernel: usb 1-1.1: new high-speed USB device number 5 using xhci_hcd
Nov 27 10:01:52 porteus kernel: usb 1-1.1: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice= 6.56
Nov 27 10:01:52 porteus kernel: usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Nov 27 10:01:52 porteus kernel: usb 1-1.1: Product: USB2.1 Hub
Nov 27 10:01:52 porteus kernel: usb 1-1.1: Manufacturer: GenesysLogic
Nov 27 10:01:52 porteus kernel: hub 1-1.1:1.0: USB hub found
Nov 27 10:01:52 porteus kernel: hub 1-1.1:1.0: 4 ports detected
And maybe a system that doesn't support USB 3.1 and USB 2.1 devices.
Ed

User avatar
Rava
Contributor
Contributor
Posts: 5416
Joined: 11 Jan 2011, 02:46
Distribution: XFCE 5.01 x86_64 + 4.0 i586
Location: Forests of Germany

Wired mouse and keyboard stop working after boot

Post#7 by Rava » 28 Nov 2023, 01:29

Ed_P wrote:
27 Nov 2023, 23:16
Or maybe too many hubs.

Code: Select all

Nov 27 10:01:52 porteus kernel: usb 2-1: Product: USB3.1 Hub
Nov 27 10:01:52 porteus kernel: hub 2-1:1.0: USB hub found

Nov 27 10:01:52 porteus kernel: usb 1-1.1: Product: USB2.1 Hub
Nov 27 10:01:52 porteus kernel: hub 1-1.1:1.0: USB hub found
Good find, both 2-1:1.0: USB hub and 1-1.1:1.0: USB hub sound like they are hubs plugged unto hubs.
PuranaPaapi can you run your Porteus without any hubs plugged into hubs to see if the error persists?

And also check if there could be truth to Ed_P's other idea:
Ed_P wrote:
27 Nov 2023, 23:16
And maybe a system that doesn't support USB 3.1 and USB 2.1 devices.

PuranaPaapi
White ninja
White ninja
Posts: 7
Joined: 24 Nov 2023, 12:12
Distribution: 5.01 KDE

Wired mouse and keyboard stop working after boot

Post#8 by PuranaPaapi » 28 Nov 2023, 05:48

I am using a MIni PC to run Porteus. Model - Minisforum Elitemini HM80. I have attached the URL of image showing available ports on the PC.
Image
https://store.minisforum.com/cdn/shop/p ... 1638260554

The only HUB connected is the one which I am using for the keyboard and mouse. It has a USB type C power input for 5V supply. I have tried with a cable plugged into that as well but same result.
There are no other HUBs connected to my PC. Maybe the frontside 3.5mm audio output and MIC input are shown as USB hubs.

The keyboard and mouse work fine when connected to the HUB (without external 5V power) in Windows OS running on the same PC.

Status of Frontside ports
2 front USB ports - 1st port is vacant, and in 2nd port Porteus USB device is connected.
1 front USB Type C port is vacant.
3.5mm Audio out and MIC in connected to headphone.

Status of Backside ports
Both LAN ports - vacant
1nd USB port - hub cable (to which keyboard and mouse are connected)
2nd USB port - wireless gamepad receiver
3rd USB port - vacant
4th USB port - vacant
Display Port - vacant
HDMI port - connected to monitor.
USB C port - PC power supply is connected.

User avatar
babam
Warlord
Warlord
Posts: 528
Joined: 16 Nov 2016, 10:30
Distribution: Porteus 5.0rc3 Xfce K6.1.1
Location: Rainy city

Wired mouse and keyboard stop working after boot

Post#9 by babam » 28 Nov 2023, 10:34

Add usbcore.autosuspend=-1 cheatcode/kernel parameter.
Sorry, my English is bad.

User avatar
Rava
Contributor
Contributor
Posts: 5416
Joined: 11 Jan 2011, 02:46
Distribution: XFCE 5.01 x86_64 + 4.0 i586
Location: Forests of Germany

Wired mouse and keyboard stop working after boot

Post#10 by Rava » 28 Nov 2023, 16:14

When the tip by babam above doesn't help…
PuranaPaapi wrote:
28 Nov 2023, 05:48
I have tried with a cable plugged into that as well but same result.
have you plugged that into a wall socked USB power loader thingy (the ones used for smartphones and such) or into an USB port of your Minisforum Elitemini HM80?
If it was the later, try using an external USB power supply, best one with 2A 5V, or at least 1500 mA 5V.

And when one of the solutions here solved your issue or you found a solution elsewhere, please post what did help you so that others can learn about that, too.

But when your PC has 6 USB ports, why do you need a hub anyway?
Cheers!
Yours Rava

PuranaPaapi
White ninja
White ninja
Posts: 7
Joined: 24 Nov 2023, 12:12
Distribution: 5.01 KDE

Wired mouse and keyboard stop working after boot

Post#11 by PuranaPaapi » 28 Nov 2023, 18:08

I have added the cheatcode as advised by babam to
mnt/sdb1/porteus/porteus-v5.0-x86_64.cfg and the file looks like this at the end

changes=/mnt/sdb1/porteus/save.dat
usbcore.autosuspend=-1

I’m not sure whether I’ve done it correctly as this is the first time I’ve tried to enter a cheatcode in Porteus so can you please guide me exactly where to add the line suggested by babam.

I’ve tried powering up the hub via external power adapter as well. The issue is still unresolved.

Reason for using a HUB.
On my study desk I have 2 PCs connected to 1 display. The Mini PC is mounted on the Vesa mount on the back of the monitor and my work PC is a SFF PC on the floor beneath the desk.
Since I don’t have enough space for a set of separate mouse and keyboard for each PC I am using a USB hub that can switch output to PCs using a small button on the hub so that I can use the same keyboard and mouse for both PCs (any 1 PC at a time) and the keyboard and mouse are common input for the Hub.

User avatar
Ed_P
Contributor
Contributor
Posts: 8374
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Wired mouse and keyboard stop working after boot

Post#12 by Ed_P » 28 Nov 2023, 18:16

All one line. Thus:

Code: Select all

APPEND changes=/mnt/sdb1/porteus/save.dat usbcore.autosuspend=-1
Ed

User avatar
babam
Warlord
Warlord
Posts: 528
Joined: 16 Nov 2016, 10:30
Distribution: Porteus 5.0rc3 Xfce K6.1.1
Location: Rainy city

Wired mouse and keyboard stop working after boot

Post#13 by babam » 28 Nov 2023, 18:53

@PuranaPaapi, Add the cheatcode usbcore.autosuspend=-1 to the APPEND line of your boot entry in /mnt/sdb1/boot/syslinux/porteus.cfg
Sorry, my English is bad.

PuranaPaapi
White ninja
White ninja
Posts: 7
Joined: 24 Nov 2023, 12:12
Distribution: 5.01 KDE

Wired mouse and keyboard stop working after boot

Post#14 by PuranaPaapi » 28 Nov 2023, 19:53

Thank you babam and Ed_P.
I did that, now the cheatcode line appears when i press tab in porteus boot menu. But the hub problem is still unresolved. The keyboard and mouse still won’t work via the hub

beny
Full of knowledge
Full of knowledge
Posts: 2098
Joined: 02 Jan 2011, 11:33
Location: italy

Wired mouse and keyboard stop working after boot

Post#15 by beny » 28 Nov 2023, 20:05

hi PuranaPapi,take a look if the module CONFIG_TYPEC=m is loaded by the system the usb type c isn't the same of the usb well i think but i can go wrong..
lsmod on terminal

Post Reply