COM ports seem inaccessible on Linux Debian Bullseye

Host server is on a Raspberry Zero W, it is connected to a device that uses a Rasberry Pico. This device is supossed to be interface via USB cable connection with a software. This setup is working flawlessly on a windows laptop client, however i need it to work on my linux workstation.

On launching vhuit64 , console shows:

"Error 2 modprobing vhci, No such file or directory"

 

Gui shows a connection to the Raspberry Pico board i'm connected to but i cant acces it from the software that should run it with a cabled connection.

The client gui displays the hub and device name, confirms that it is in use, but does not display a port number. Pico

While using virtualhere client on a windows laptop does display the port number as well. (COM5)Pico

 

Any advice to get this working please?

 

 

 

#2

So, as a last ditch resort, i found this discussion about arduino not seeing the ports and lo and behold the solution worked for my app as well.

Problem is related to snap apps:

uninstalled the snap ap and reinstalled with --devmode argument

"However, to get around the serial ports being blocked, you will need to install it with the --devmode flag. This, unfortunately, disables all security confinement for the snap, but until the new feature that @zyga-snapd mentioned becomes available it’s the easiest way to let the Arduino IDE talk to devices."

https://forum.snapcraft.io/t/serial-port-permissions-for-a-snap-arduino…

 

PS: (COM5)Pico still not visible in linux client, this did throw me off that it might be related to the problem but it was not... suggesting there should be consistency between os UX

PPS: "Error 2 modprobing vhci, No such file or directory"  seems that this got resolved by doing sudo apt-get install usbip on the raspberry pi zero USB host server side

usbip version

usbip (usbip-utils 2.0)  

was present only on the client side before manual install


 

 

#3

Actually you can ignore that modprobe error, i need to remove that as its not relevant.

Regarding com port names, ive only hooked it up in windows and not in linux (or macos yet)