Originally posted by eXsoR on Discord, 28 August 2025.
Yeah in my case I was using the RPM package
Originally posted by Walter Rogers (WX) on Discord, 28 August 2025.
Problem appears RESOLVED (enough) for me. Just have to remember to reset serial port from menu. Added one more mini-PC which now includes 3 devices tested and working with mini-kvm
Originally posted by eXsoR on Discord, 28 August 2025.
Yeah same here, it’s been working flawlessly after doing the Serial Port Reset.
Originally posted by Kevin Peng on Discord, 29 August 2025.
the logic of serial port reset close and open the serial port to simulate the disconnect and connect the usb serial port. The internal chip CH9329 need such a operation after factory reset
Originally posted by Kevin Peng on Discord, 29 August 2025.
But factory reset function has built auto reset the serial port, maybe the delay between factory reset and serial port reset is not long enough
Originally posted by eXsoR on Discord, 30 August 2025.
I see, yeah it probably be it.
Originally posted by Walter Rogers (WX) on Discord, 4 September 2025.
I found an example where the serial port reset did not allow me to receive and send keyboard/mouse entries on another Raspberry pi 3 (the one I drove 100miles roundtrip to work on… good thing I brought a keyboard and HDMI monitor). I hope this niggling detail can get fixed so I can reliably use my laptop with the mini-kvm openterface.
Originally posted by eXsoR on Discord, 4 September 2025.
That’s odd I e been using it for a few days now with no issues. Though I don’t use them on Raspberry Pi’s. I’ll give it a try tomorrow
Originally posted by Billiooo on Discord, 4 September 2025.
Sure, keep us updated on this 
Originally posted by Walter Rogers (WX) on Discord, 5 September 2025.
Mentioned above Rasp pi 3 is now remote and not accessible. But, another Rasp pi 3 on my desk has an nonoperative keyboard mouse through openterface. No time to further test this now…
Originally posted by eXsoR on Discord, 5 September 2025.
Tested a Rasperry Pi 4 B running Ubuntu Server ARM, with a 5V 3.5 A power supply and doesn’t seem to work at all. Not sure if its a limitation since I have to use a HDMI cable that comes with the RPI4.
Originally posted by eXsoR on Discord, 5 September 2025.
I just switch it to a ThinClient PC thats x86 I have (HP T640), and works with out any issues.
Originally posted by eXsoR on Discord, 5 September 2025.
my guess is its doesn’t like the Mico HDMI to HDMI cable since the RPi 4 only has MicroHDMI.
Originally posted by Kevin Peng on Discord, 5 September 2025.
The low raspberry pi usb port may likely the root cause I think. Usually when your raspberry pi power supply is not sufficient, and you have a high demand usb device, the usb port on it may likely lower than 5V. And the Openterface rely on the target as the main power supplier as the shorter cable in target side. As a result, it cause the serial not stable or even “kill” your usb port(you can recover after reboot).
Originally posted by Kevin Peng on Discord, 5 September 2025.
We noticed this as well in Uconsole Extensions board development. Our solution is lower the serial baudrate to 9600, which makes the serial port communication to be stable. So we change the default serial baudrate from 115200 to 9600 from QT version 0.4.#.
The latest version in the GitHub is still under testing, but mainly about the CI process, you can have a try @Walter Rogers (WX)
Originally posted by Walter Rogers (WX) on Discord, 6 September 2025.
Thanks, Peng… I just successfully tested the same Rasp pi 3 and keyboard/mouse worked. Believe I’ve occasionally seen low voltage warnings, so that seems like a good guess for the intermittency. Setting Rasp pi to 9600 baud default seems good to me. Does the UI allow me to manually set that? I probably just missed it if it does.
Originally posted by Kevin Peng on Discord, 6 September 2025.
If you are using the latest app, say 0.4.3, you can change default settings manually, if you are using 0.3.*. It will auto fallback to 115200 as default.
Originally posted by Walter Rogers (WX) on Discord, 12 September 2025.
Reference Raspberry pi and other device no keyboard/mouse on Fedora 42 kde. Got it working again. I upgraded to kernel 6.16.4-200 on Aug 27th. Needed to recompile serial driver… ch341. Now everything seems to work. RESOLVED (for now)
Originally posted by Kevin Peng on Discord, 12 September 2025.
Good to hear it works, this is the driver issue then