No go on the restart order. I haven’t been able to re-establish a connection either after experimenting with some different startup orders and usb ports. ls returns properly:
I suspect you’re correct about udev rules. I did find this post which has a similar problem and a resolution: No connection to Lightburn after upgrading to Ubuntu 22.04
Using their process as a guide:
Running lsusb returns:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 011: ID 1a86:7523 QinHeng Electronics CH340 serial converter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Running dmesg, this popped out to me:
[ 4.362301] virtiofs virtio12: virtio_fs_setup_dax: No cache capability
[ 4.573319] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 4.582680] serial8250: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
[ 4.611591] serial8250: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
[ 4.677071] serial8250: ttyS2 at I/O 0x3e8 (irq = 4, base_baud = 115200) is a 16550A
[ 4.725882] serial8250: ttyS3 at I/O 0x2e8 (irq = 3, base_baud = 115200) is a 16550A
[ 4.802470] printk: console [hvc0] enabled
[ 4.811924] printk: bootconsole [uart8250] disabled
[ 8.494697] maitred: failed to enable LRO for eth0: Operation not supported
[ 8.504882] maitred: Failed to enable LRO: failed to enable LRO for eth0: Operation not supported
[ 8.519565] maitred: Set default IPv4 gateway for interface eth0 to 100.115.92.25
[ 8.538976] maitred: Received request to update VM resolv.conf
[ 8.555627] maitred: Received mount request
[ 8.681150] EXT4-fs (vda): mounted filesystem without journal. Opts:
[ 8.687314] maitred: Mounted “/dev/vda” on “/opt/google/cros-containers”
[ 8.715828] maitred: Received request to mount 9P file system
[ 8.734062] maitred: Mounted 9P file system on /mnt/shared
[ 8.755971] maitred: Received request to get kernel version information.
[ 8.763217] maitred: Received StartTermina request
[ 9.013810] BTRFS: device fsid 8d5067a3-b304-4924-9932-2619870e44ce devid 1 transid 608 /dev/vdb scanned by grpcpp_sync_ser (105)
[ 9.032966] BTRFS info (device vdb): flagging fs with big metadata feature
[ 9.038468] BTRFS info (device vdb): turning on sync discard
[ 9.044823] BTRFS info (device vdb): disk space caching is enabled
[ 9.062032] BTRFS info (device vdb): has skinny extents
[ 9.137195] maitred: This system has transitioned to LXD 4.0.x
[ 10.335664] usb 1-1: new full-speed USB device number 2 using xhci_hcd
[ 11.071886] ch341 1-1:1.0: ch341-uart converter detected
[ 11.148601] usb 1-1: ch341-uart converter now attached to ttyUSB0
[ 20.324161] lxdbr0: port 1(veth00244447) entered blocking state
[ 20.336096] lxdbr0: port 1(veth00244447) entered disabled state
[ 20.349395] device veth00244447 entered promiscuous mode
[ 21.681336] cgroup: cgroup: disabling cgroup2 socket matching due to net_prio or net_cls activation
[ 21.728227] physaUDOml: renamed from vethdce4a649
[ 21.740893] eth0: renamed from physaUDOml
[ 21.758706] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 21.776307] lxdbr0: port 1(veth00244447) entered blocking state
[ 21.777632] lxdbr0: port 1(veth00244447) entered forwarding state
[ 21.782183] IPv6: ADDRCONF(NETDEV_CHANGE): lxdbr0: link becomes ready
[ 22.660033] new mount options do not match the existing superblock, will be ignored
[ 23.353332] cgroup: systemd (250) created nested cgroup for controller “memory” which has incomplete hierarchy support. Nested cgroups may change behavior in the future.
[ 23.375348] cgroup: “memory” requires setting use_hierarchy to 1 on the root
Did not see anything hijacking my port, but wasn’t entirely sure what to be looking for.
I was also unable to get grep -riIn “1a86:7523” /usr/lib/udev/rules.d/* to return anything. I’m unsure how to go about editing rules from here.