On Fri, Nov 11, 2022 at 04:38:21PM +0100, Claudia Neumann wrote: > Hi Tomas, > > > Am Freitag, 11. November 2022, 06:54:36 CET schrieb to...@tuxteam.de: > > On Thu, Nov 10, 2022 at 11:21:21PM +0100, Claudia Neumann wrote:
[...] Thanks. The only difference I can see is: [Debian 11] [...] > After: [...] > Bus 001 Device 008: ID 1f61:0001 Flexocard GmbH VML-GK2 (USB) [...] > iManufacturer 1 Flexocard GmbH > iProduct 2 VML-GK2 (USB) > iSerial 3 2009002 [Debian 10]; [...] > After: [...] > Bus 001 Device 014: ID 1f61:0001 [...] > iManufacturer 1 > iProduct 2 > iSerial 3 This would kind of make sense: the newer kernel has a more complete USB device database and "knows" the Flexocard device. Now I see a couple of possibilities. Either the newer drivers are buggy, or some other program (perhaps courtesy of udev) "thinks" it has to take care of this USB gadget. To get a clearer idea about the second, you might try to run "udevadm monitor" while you insert your device. Another thing to check is whether any application has /dev/ttyACM0 (that was its name, wasn't it?) open is to query it with `lsof`. Ah, you might also want to see what parameters this pseudo-serial interface it has, e.g. `stty -a < /dev/ttyACM0'. Sorry: if it seems like I'm poking in the dark, then that' perhaps because I am :-) Cheers -- tomás
signature.asc
Description: PGP signature
