(RESOLVED)Octoprint cannot see printer connected to Nintendo Switch running Ubuntu

RESOLVED
Turns out Linux builds for nintendo switch (I tried Bionic and Jammy builds) is not suitable for Octoprint in their current state. Do not have CH34X drivers and without the Headers you cannot make them. I used an old windows laptop and all 3 of my cables work fine and connect. Here's to the future in which we can hopefully remote manage our 3d printers with a Nintendo switch.

What is the problem?

I am running Octoprint on a nintendo switch running Ubuntu, I have everything in connection set to auto. Octoprint cannot see my Neptune 3 Pro connected via USB type A to B.

What did you already try to solve it?

I have added myself to the dialout group and tty group
Tried another data capable usb cable, only 1 I tried I know is shielded because it's transparent.
Updated Neptune 3 Pro firmware.
Uninstalled brltty
Removed SD card

Have you tried running in safe mode?

It looks like safe mode just disabled plugins, I have no plugins installed. I can still try if requested.

Did running in safe mode solve the problem?

N/A

Systeminfo Bundle

octoprint-systeminfo-20240109194255.zip (37.6 KB)

Additional information about your setup

OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible
Octoprint version: 1.7.3
Printer: Neptune 3 Pro
Firmware: Latest
OS: Ubuntu Linux

EDIT: I ran tail -f /var/log/syslog and reseated the USB cable. The following shows the cable is data atleast.

Jan 10 10:30:01 print-laptop kernel: [  960.321866] usb 1-1.3: USB disconnect, device number 4
Jan 10 10:30:04 print-laptop kernel: [  963.322654] usb 1-1.3: new full-speed USB device number 8 using tegra-xusb
Jan 10 10:30:04 print-laptop kernel: [  963.412237] usb 1-1.3: New USB device found, idVendor=1a86, idProduct=7523
Jan 10 10:30:04 print-laptop kernel: [  963.412245] usb 1-1.3: New USB device strings: Mfr=0, Product=2, SerialNumber=0
Jan 10 10:30:04 print-laptop kernel: [  963.412249] usb 1-1.3: Product: USB Serial
Jan 10 10:29:29 print-laptop bamfdaemon[1415]: bamf_matcher_set_starting_desktop_file: assertion 'desktop_file != NULL' failed
Jan 10 10:30:04 print-laptop mtp-probe: checking bus 1, device 8: "/sys/devices/70090000.xusb/usb1/1-1/1-1.3"

EDIT: I ran sudo chmod 666 /dev/tty* to set every permission, and then went to config and added '/dev/tty*' to the additional ports list. Let it scan the whole list, every one was a timeout except for tty0 and tty1 (which was getting a timeout previously)

Trying port /dev/tty1, baudrate 250000
Connecting to port /dev/tty1, baudrate 250000
Unexpected error while connecting to serial port /dev/tty1, baudrate 250000 from hook default: error: '(22, 'Invalid argument')' @ comm.py:_open_serial:3779
Could not open port /dev/tty1, baudrate 250000, skipping
Trying port /dev/tty0, baudrate 115200
Connecting to port /dev/tty0, baudrate 115200
Unexpected error while connecting to serial port /dev/tty0, baudrate 115200 from hook default: error: '(22, 'Invalid argument')' @ comm.py:_open_serial:3779
Could not open port /dev/tty0, baudrate 115200, skipping
Trying port /dev/tty0, baudrate 250000

Hello @Seth_Ward !

Does Ubuntu see the printer?

Are you running a slicer on the Ubuntu system? What is it? Is it still open?

I downloaded Cura slicer and it is not being picked up, at this point it does seem my issue is out of scope of the forum :frowning:

Any tips for better figuring out if its detected? The Arm64 build of cura seems to be very finnicky. Any help is appreciated.