Debian USB issues, no keyboard mouse
I've been unable to get keyboard and mouse working when connecting to a Debian PC. The dmesg output from the PC is below and seems to indicate an issue with addressing.
Any help would be appreciated
- ATim @anidea
For anyone who is having similiar issues I tried the solution here
https://urukrama.wordpress.com/2009/01/27/usb-drive-not-recognised-error-71/
and the behavior is the same.- Diego @diego
Hello Tim! Thank you for reporting this issue. This is the first time we see something like this. It does look to me like a problem on the target machine (the Debian computer).
- What kernel are you running, if I may ask?
- I know yours is Debian GNU/Linux. But I found this other solution on the SuSE Linux website. TL;DR: disconnect the USB cable going to the TinyPilot, run
echo -1 > /sys/module/usbcore/parameters/autosuspend
and then reconnect the USB cable. - Are you completely sure the USB port is healthy?
- ATim @anidea
Thanks for the quick response Diego
The kernel version is 4.19.0-10-amd64
I ran the command and get similar messages (below is from tailing /var/log/messages versus dmesg)
The USB port appears okay and recognizes physical mice & keyboard w/o issue.
- AIn reply toanidea⬆:Tim @anidea
After adding
old_scheme_first=y
use_both_schemes=y
and enabling xHCI in biosHere is the tinypilot log
https://logs.tinypilotkvm.com/Nq21dxAV- Diego @diego
-
Have you tried hooking the TinyPilot to a different target computer? i.e. not the Debian machine.
-
Is this a brand new TinyPilot Voyager 2 that you are trying to setup?
- ATim @anidea
Hey Diego,
Yes I have tried another machine and things work there but unfortunately the one that doesn't work is the one that is critical for remote access.
It is a brand new Voyager 2
- ATim @anidea
@diego One caused of these errors seems to be over-current protection on USB ports. Is there any diagnostics within tiny-pilot to troubleshoot from that angle?
- Diego @diego
Hi @anidea - The TinyPilot is a Raspberry Pi inside. You are welcome to SSH in and play around. We don't have any specific diagnostics tool for the USB ports. However, you may find
raspinfo
helpful.- In your Debian PC, are there any other BIOS settings related to USB that you may see? I am not sure changing from EHCI to XHCI is a good idea.
- May I know brand and model of the motherboard in this Debian PC, please?
Speaking of USB over current, I found this blog post. Please go through the following procedure, if you haven't tried it already:
- Unplug all USB devices from the PC, including the TinyPilot.
- Turn the PC power off (disconnect power cable).
- Wait for a couple of minutes.
- Reconnect power cable.
- Plug everything back. When you do this, please ensure you are connecting the TinyPilot DATA cable to a USB port on your PC and the TinyPilot POWER cable/adapter to an AC power socket.
- Power the PC on.
- Boot into Debian.
Let me know if this solves your problem.
- ATim @anidea
The computer is a COMe SBC from Kontron
No other USB related settings that I see.
I had seen that blog post but no such luck.
I have also tried shutting down and restarting in that order but still get the same response. Ditto for trying to set initial_descriptor_timeout to longer.
looking at dmesg on the tinypilot I see these messages everytime I plug into the usb to the other PC but nothing else.
[ 655.360033] dwc2 fe980000.usb: new device is high-speed [ 655.869985] dwc2 fe980000.usb: new device is high-speed [ 656.691607] dwc2 fe980000.usb: new device is high-speed [ 656.711997] dwc2 fe980000.usb: new device is high-speed [ 656.992701] dwc2 fe980000.usb: new device is high-speed [ 657.202347] dwc2 fe980000.usb: new device is high-speed [ 657.391826] dwc2 fe980000.usb: new device is high-speed [ 657.486623] dwc2 fe980000.usb: new device is high-speed [ 657.691233] dwc2 fe980000.usb: new device is high-speed
and these messages during boot where the USB client/OTG port seems to be set up
[ 3.271389] dwc2 fe980000.usb: supply vusb_d not found, using dummy regulator [ 3.271717] dwc2 fe980000.usb: supply vusb_a not found, using dummy regulator [ 3.494712] dwc2 fe980000.usb: EPs: 8, dedicated fifos, 4080 entries in SPRAM [ 3.495347] dwc2 fe980000.usb: DWC OTG Controller [ 3.495402] dwc2 fe980000.usb: new USB bus registered, assigned bus number 3 [ 3.495472] dwc2 fe980000.usb: irq 38, io mem 0xfe980000
Does that all look as expected?
Is there a way to make the tinypilot just look like a keyboard versus hub with keyboard, mouse and mass storage as a baby step?
- Diego @diego
- In reply toanidea⬆:Diego @diego
Does that all look as expected?
It's all normal. See below exactly the same messages on my TinyPilot, which is working wonderfully.
[ 3.322075] dwc2 fe980000.usb: supply vusb_d not found, using dummy regulator [ 3.322457] dwc2 fe980000.usb: supply vusb_a not found, using dummy regulator [ 3.534932] dwc2 fe980000.usb: EPs: 8, dedicated fifos, 4080 entries in SPRAM [ 3.535639] dwc2 fe980000.usb: DWC OTG Controller [ 3.535698] dwc2 fe980000.usb: new USB bus registered, assigned bus number 3 [ 3.535813] dwc2 fe980000.usb: irq 38, io mem 0xfe980000
Is there a way to make the tinypilot just look like a keyboard versus hub with keyboard, mouse and mass storage as a baby step?
I gave it a try. See commands/snippet below. I am not sure how this will work for you, since the TinyPilot is still being presented as a hub (with only a keyboard attached); I commented out the mouse parts. Mass storage is not presented to the target computer until you mount an ISO, see the following FAQ for more details: How do I disable virtual media on my TinyPilot?.
PROCEDURE
cd /opt/tinypilot-privileged && \ sudo cp -p init-usb-gadget init-usb-gadget.original && \ sudo sed --in-place '103,149 {s/^/#/}' init-usb-gadget && \ sudo sed --in-place '159 {s/^/#/}' init-usb-gadget && \ cd /opt/tinypilot-privileged/lib && \ sudo cp -p usb-gadget.sh usb-gadget.sh.original && \ sudo sed --in-place '24 {s/^/#/}' usb-gadget.sh && \ sudo reboot
FALLBACK
cd /opt/tinypilot-privileged && \ sudo cp -p init-usb-gadget.original init-usb-gadget && \ cd /opt/tinypilot-privileged/lib && \ sudo cp -p usb-gadget.sh.original usb-gadget.sh && \ sudo reboot
- ATim @anidea
Thanks again diego. Same response and I tried several other boxes that use the same internal motherboard with the same results.
I've got no further ideas but welcome any you or anyone else has.- Diego @diego
@anidea - I'm afraid I ran out of ideas myself as well. It would seem to me as if the motherboard in that target system refuses to accept a hub in the USB port, it is expecting a single USB device. If this issue breaks the scenario you had in mind for the TinyPilot, please contact support@tinypilotkvm.com so we can work out a resolution for you. Please reference this forum post.
-