Mark Blakeney

@massimosala the `mpremote` code is hosted here in this repo (where I raised the issue). Sorry, but those changes would never be accepted. I don't actually use `mpremote` directly, but...

I should add that this problem only started from kernel 6.7+. Works fine (i.e. bogus devices are not listed) on Linux kernel 6.6 and earlier.

I'm on a stock Arch x86_64 system with stock kernel etc. I have used `mpremote` forever and have never seen this problem until recently so I went looking today and...

So when a device is connected to that port how is it reported then?

On kernel 6.6 that prints out nothing. On kernel 6.8: ``` $ python tmp.py /dev/ttyS0 serial-base None 0000:0000 None None /dev/ttyS1 serial-base None 0000:0000 None None /dev/ttyS2 serial-base None 0000:0000...

The output from that second script on 6.8 is exactly the same as the previous output I pasted here. On 6.6, it is also the same except `platform` is shown...

@Gadgetoid what kernel version are you running on your RPi? And what output do you get from `mpremote devs` with a MP device connected on a UART port, and without...

@projectgus I think you and Gadgetoid are misunderstanding this PR. It **does not** prohibit `mpremote` from connecting to UART ports. You can specify any port you like and `mpremote` will...

@dpgeorge it is only a problem on Arch because Arch uses bleeding edge Linux kernel versions and it only happened on the update of the kernel to 6.7 (6.6 and...

I have a WD19TB (not TBS) and got this error which I repeated many times. Then came here and discovered this issue. Saw @dupondje comment so unplugged my dock cable...