Re: usb QR reader
> On 16 Jan 2020, at 12:26, Hans Petter Selasky wrote: > > On 2020-01-16 11:23, Daniel Braniss wrote: >> 63549 a.outCALL openat(AT_FDCWD,0x1045b,0x2) >> 63549 a.outNAMI "/dev/ttyU0" >> 63549 a.outRET openat -1 errno 6 Device not configured >> 63549 a.outCALL nanosleep(0xbfbfec20,0xbfbfec10) >> 63549 a.outRET nanosleep 0 >> 63549 a.outCALL writev(0x2,0xbfbfe408,0x4) >> 63549 a.outGIO fd 2 wrote 28 bytes >> "open: Device not configured >> and the console: >> Jan 16 12:17:14 neo-black-1 kernel: umodem_cfg_set_dtr: onoff=1 >> Jan 16 12:17:14 neo-black-1 kernel: umodem_cfg_set_rts: onoff=1 >> Jan 16 12:17:15 neo-black-1 kernel: umodem0: at uhub5, port 1, addr 2 >> (disconnected) >> Jan 16 12:17:15 neo-black-1 kernel: umodem_detach: sc=0xd494c400 >> Jan 16 12:17:16 neo-black-1 kernel: umodem_cfg_set_break: onoff=0 >> Jan 16 12:17:16 neo-black-1 kernel: umodem0: detached >> Jan 16 12:17:23 neo-black-1 kernel: umodem_probe: >> Jan 16 12:17:23 neo-black-1 syslogd: last message repeated 1 times >> Jan 16 12:17:23 neo-black-1 kernel: umodem0 on uhub5 >> Jan 16 12:17:23 neo-black-1 kernel: umodem0: > class 2/0, rev 1.10/1.00, addr 2> on usbus5 >> Jan 16 12:17:23 neo-black-1 kernel: umodem0: data interface 1, has no CM >> over data, has no break > > Also do: > > ls /dev/cuaU* looks fine > > To make sure there are not multiple devices there! > > Can you try to open up /dev/cuaU0 instead? > > Same result? > the open succeeds, but read returns 0, and the device is detached again. i will now try the whole termcap stuff (speed, raw mode, etc) danny ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: usb QR reader
> On 16 Jan 2020, at 12:26, Hans Petter Selasky wrote: > > On 2020-01-16 11:23, Daniel Braniss wrote: >> 63549 a.outCALL openat(AT_FDCWD,0x1045b,0x2) >> 63549 a.outNAMI "/dev/ttyU0" >> 63549 a.outRET openat -1 errno 6 Device not configured >> 63549 a.outCALL nanosleep(0xbfbfec20,0xbfbfec10) >> 63549 a.outRET nanosleep 0 >> 63549 a.outCALL writev(0x2,0xbfbfe408,0x4) >> 63549 a.outGIO fd 2 wrote 28 bytes >> "open: Device not configured >> and the console: >> Jan 16 12:17:14 neo-black-1 kernel: umodem_cfg_set_dtr: onoff=1 >> Jan 16 12:17:14 neo-black-1 kernel: umodem_cfg_set_rts: onoff=1 >> Jan 16 12:17:15 neo-black-1 kernel: umodem0: at uhub5, port 1, addr 2 >> (disconnected) >> Jan 16 12:17:15 neo-black-1 kernel: umodem_detach: sc=0xd494c400 >> Jan 16 12:17:16 neo-black-1 kernel: umodem_cfg_set_break: onoff=0 >> Jan 16 12:17:16 neo-black-1 kernel: umodem0: detached >> Jan 16 12:17:23 neo-black-1 kernel: umodem_probe: >> Jan 16 12:17:23 neo-black-1 syslogd: last message repeated 1 times >> Jan 16 12:17:23 neo-black-1 kernel: umodem0 on uhub5 >> Jan 16 12:17:23 neo-black-1 kernel: umodem0: > class 2/0, rev 1.10/1.00, addr 2> on usbus5 >> Jan 16 12:17:23 neo-black-1 kernel: umodem0: data interface 1, has no CM >> over data, has no break > > Also do: > > ls /dev/cuaU* > > To make sure there are not multiple devices there! > > Can you try to open up /dev/cuaU0 instead? > > Same result? > > --HPS ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: usb QR reader
> On 16 Jan 2020, at 12:12, Hans Petter Selasky wrote: > > On 2020-01-16 11:07, Daniel Braniss wrote: >>> On 16 Jan 2020, at 11:16, Hans Petter Selasky wrote: >>> >>> ktracing >> wrote a small c program, that just opens and tries to read, the open fails >> with >> ‘’open: Device not configured” >> and the console shows: >> Jan 16 11:59:09 neo-black-1 kernel: umodem0: detached >> Jan 16 11:59:14 neo-black-1 kernel: ugen5.2: at >> usbus5 >> Jan 16 11:59:14 neo-black-1 kernel: umodem_probe: >> Jan 16 11:59:14 neo-black-1 syslogd: last message repeated 1 times >> Jan 16 11:59:14 neo-black-1 kernel: umodem0 on uhub5 >> Jan 16 11:59:14 neo-black-1 kernel: umodem0: > class 2/0, rev 1.10/1.00, addr 2> on usbus5 >> Jan 16 11:59:14 neo-black-1 kernel: umodem0: >> Jan 16 11:59:14 neo-black-1 kernel: data interface 1, has no CM over data, >> has no break >> Jan 16 12:01:52 neo-black-1 kernel: umodem_cfg_set_dtr: onoff=1 >> Jan 16 12:01:52 neo-black-1 kernel: umodem_cfg_set_rts: onoff=1 >> Jan 16 12:01:53 neo-black-1 kernel: umodem0: at uhub5, port 1, addr 2 >> (disconnected) >> Jan 16 12:01:53 neo-black-1 kernel: umodem_detach: sc=0xd494c400 >> Jan 16 12:01:54 neo-black-1 kernel: umodem_cfg_set_break: onoff=0 >> Jan 16 12:01:54 neo-black-1 kernel: umodem0: detached >> Jan 16 12:02:01 neo-black-1 kernel: umodem_probe: >> Jan 16 12:02:01 neo-black-1 syslogd: last message repeated 1 times >> Jan 16 12:02:01 neo-black-1 kernel: umodem0 on uhub5 >> Jan 16 12:02:01 neo-black-1 kernel: umodem0: > class 2/0, rev 1.10/1.00, addr 2> on usbus5 >> Jan 16 12:02:01 neo-black-1 kernel: umodem0: data interface 1, has no CM >> over data, has no break > > Can you put a sleep call in your c-program, like 1 second? > > --HPS 63549 a.outCALL openat(AT_FDCWD,0x1045b,0x2) 63549 a.outNAMI "/dev/ttyU0" 63549 a.outRET openat -1 errno 6 Device not configured 63549 a.outCALL nanosleep(0xbfbfec20,0xbfbfec10) 63549 a.outRET nanosleep 0 63549 a.outCALL writev(0x2,0xbfbfe408,0x4) 63549 a.outGIO fd 2 wrote 28 bytes "open: Device not configured and the console: Jan 16 12:17:14 neo-black-1 kernel: umodem_cfg_set_dtr: onoff=1 Jan 16 12:17:14 neo-black-1 kernel: umodem_cfg_set_rts: onoff=1 Jan 16 12:17:15 neo-black-1 kernel: umodem0: at uhub5, port 1, addr 2 (disconnected) Jan 16 12:17:15 neo-black-1 kernel: umodem_detach: sc=0xd494c400 Jan 16 12:17:16 neo-black-1 kernel: umodem_cfg_set_break: onoff=0 Jan 16 12:17:16 neo-black-1 kernel: umodem0: detached Jan 16 12:17:23 neo-black-1 kernel: umodem_probe: Jan 16 12:17:23 neo-black-1 syslogd: last message repeated 1 times Jan 16 12:17:23 neo-black-1 kernel: umodem0 on uhub5 Jan 16 12:17:23 neo-black-1 kernel: umodem0: on usbus5 Jan 16 12:17:23 neo-black-1 kernel: umodem0: data interface 1, has no CM over data, has no break ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: usb QR reader
> On 16 Jan 2020, at 11:16, Hans Petter Selasky wrote: > > ktracing wrote a small c program, that just opens and tries to read, the open fails with ‘’open: Device not configured” and the console shows: Jan 16 11:59:09 neo-black-1 kernel: umodem0: detached Jan 16 11:59:14 neo-black-1 kernel: ugen5.2: at usbus5 Jan 16 11:59:14 neo-black-1 kernel: umodem_probe: Jan 16 11:59:14 neo-black-1 syslogd: last message repeated 1 times Jan 16 11:59:14 neo-black-1 kernel: umodem0 on uhub5 Jan 16 11:59:14 neo-black-1 kernel: umodem0: on usbus5 Jan 16 11:59:14 neo-black-1 kernel: umodem0: Jan 16 11:59:14 neo-black-1 kernel: data interface 1, has no CM over data, has no break Jan 16 12:01:52 neo-black-1 kernel: umodem_cfg_set_dtr: onoff=1 Jan 16 12:01:52 neo-black-1 kernel: umodem_cfg_set_rts: onoff=1 Jan 16 12:01:53 neo-black-1 kernel: umodem0: at uhub5, port 1, addr 2 (disconnected) Jan 16 12:01:53 neo-black-1 kernel: umodem_detach: sc=0xd494c400 Jan 16 12:01:54 neo-black-1 kernel: umodem_cfg_set_break: onoff=0 Jan 16 12:01:54 neo-black-1 kernel: umodem0: detached Jan 16 12:02:01 neo-black-1 kernel: umodem_probe: Jan 16 12:02:01 neo-black-1 syslogd: last message repeated 1 times Jan 16 12:02:01 neo-black-1 kernel: umodem0 on uhub5 Jan 16 12:02:01 neo-black-1 kernel: umodem0: on usbus5 Jan 16 12:02:01 neo-black-1 kernel: umodem0: data interface 1, has no CM over data, has no break ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: usb QR reader
> On 6 Jan 2020, at 00:32, Hans Petter Selasky wrote: > > On 2020-01-05 18:03, Daniel Braniss wrote: >>> On 5 Jan 2020, at 17:08, Hans Petter Selasky wrote: >>> >>> On 2020-01-05 15:32, Daniel Braniss wrote: status 0x6a1a3 16:25:17.790304 usbus5.2 SUBM-CTRL-EP=,SPD=FULL,NFR=1,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 21 22 03 00 00 00 00 00 -- -- -- -- -- -- -- -- |!"..| flags 0x10 status 0x4a1a3 16:25:17.790346 usbus5.2 DONE-CTRL-EP=,SPD=FULL,NFR=0,SLEN=0,IVAL=50,ERR=TIMEOUT flags 0 <0> status 0x8a1a5 16:25:18.797312 usbus5.2 DONE-CTRL-EP=,SPD=FULL,NFR=0,SLEN=0,IVAL=0,ERR=TIMEOUT flags 0x10 >>> >>> Hi, >>> >>> There are some USB requests your USB device doesn't respond to. ERR=TIMEOUT >>> >>> You might find the corresponding driver and enable .debug=16 under : >>> >>> sysctl hw.usb | grep debug >>> >>> To get more information what exactly goes wrong. >>> > > Did you compile the kernel with options USB_DEBUG ? > > Now hw.usb.debug, but hw.usb.umodem.debug, for example. > > --HPS real events took over, so now: connecting the device: Jan 16 11:05:28 neo-black-1 kernel: ugen5.2: at usbus5 (disconnected) Jan 16 11:05:28 neo-black-1 kernel: umodem0: at uhub5, port 1, addr 2 (disconnected) Jan 16 11:05:28 neo-black-1 kernel: umodem_detach: sc=0xd494c400 Jan 16 11:05:28 neo-black-1 kernel: umodem0: detached Jan 16 11:05:36 neo-black-1 kernel: ugen5.2: at usbus5 Jan 16 11:05:36 neo-black-1 kernel: umodem_probe: Jan 16 11:05:36 neo-black-1 syslogd: last message repeated 1 times Jan 16 11:05:36 neo-black-1 kernel: umodem0 on uhub5 Jan 16 11:05:36 neo-black-1 kernel: umodem0: on usbus5 Jan 16 11:05:36 neo-black-1 kernel: umodem0: Jan 16 11:05:36 neo-black-1 kernel: data interface 1, has no CM over data, has no break trying to open it: Jan 16 11:06:34 neo-black-1 kernel: umodem_cfg_set_dtr: onoff=1 Jan 16 11:06:34 neo-black-1 kernel: umodem_ioctl: cmd=0x402c7413 Jan 16 11:06:34 neo-black-1 kernel: umodem_ioctl: unknown Jan 16 11:06:34 neo-black-1 kernel: umodem_cfg_set_rts: onoff=1 Jan 16 11:06:34 neo-black-1 kernel: umodem_ioctl: cmd=0x802c7416 Jan 16 11:06:34 neo-black-1 kernel: umodem_ioctl: unknown Jan 16 11:06:34 neo-black-1 kernel: umodem_ioctl: cmd=0x2000740d Jan 16 11:06:34 neo-black-1 kernel: umodem_ioctl: unknown Jan 16 11:06:34 neo-black-1 kernel: umodem_ioctl: cmd=0x402c7413 Jan 16 11:06:34 neo-black-1 kernel: umodem_ioctl: unknown Jan 16 11:06:34 neo-black-1 kernel: umodem_ioctl: cmd=0x802c7416 Jan 16 11:06:34 neo-black-1 kernel: umodem_ioctl: unknown Jan 16 11:06:34 neo-black-1 kernel: umodem_ioctl: cmd=0x8004667e Jan 16 11:06:34 neo-black-1 kernel: umodem_ioctl: unknown Jan 16 11:06:34 neo-black-1 kernel: umodem_ioctl: cmd=0x8004667d Jan 16 11:06:34 neo-black-1 kernel: umodem_ioctl: unknown Jan 16 11:06:35 neo-black-1 kernel: umodem0: at uhub5, port 1, addr 2 (disconnected) Jan 16 11:06:35 neo-black-1 kernel: umodem_detach: sc=0xd494c400 Jan 16 11:06:36 neo-black-1 kernel: umodem_cfg_set_break: onoff=0 Jan 16 11:06:36 neo-black-1 kernel: umodem0: detached Jan 16 11:06:42 neo-black-1 kernel: umodem_probe: Jan 16 11:06:42 neo-black-1 syslogd: last message repeated 1 times Jan 16 11:06:42 neo-black-1 kernel: umodem0 on uhub5 Jan 16 11:06:42 neo-black-1 kernel: umodem0: on usbus5 Jan 16 11:06:42 neo-black-1 kernel: umodem0: data interface 1, has no CM over data, has no break cheers, danny ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: usb QR reader
> On 5 Jan 2020, at 17:08, Hans Petter Selasky wrote: > > On 2020-01-05 15:32, Daniel Braniss wrote: >> status 0x6a1a3 >> >> 16:25:17.790304 usbus5.2 SUBM-CTRL-EP=,SPD=FULL,NFR=1,SLEN=8,IVAL=0 >> frame[0] WRITE 8 bytes >> 21 22 03 00 00 00 00 00 -- -- -- -- -- -- -- -- |!"..| >> flags 0x10 >> status 0x4a1a3 >> >> 16:25:17.790346 usbus5.2 >> DONE-CTRL-EP=,SPD=FULL,NFR=0,SLEN=0,IVAL=50,ERR=TIMEOUT >> flags 0 <0> >> status 0x8a1a5 >> >> 16:25:18.797312 usbus5.2 >> DONE-CTRL-EP=,SPD=FULL,NFR=0,SLEN=0,IVAL=0,ERR=TIMEOUT >> flags 0x10 > > Hi, > > There are some USB requests your USB device doesn't respond to. ERR=TIMEOUT > > You might find the corresponding driver and enable .debug=16 under : > > sysctl hw.usb | grep debug > > To get more information what exactly goes wrong. > > —HPS did that: sysctl hw.usb.debug=16 but can’t see any changes, /var/log/messages seems the same as before, BTW, the device works fine when I connect it to a mac, so it must be something in the umodem0 cheers, danny ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: usb QR reader
> On 3 Jan 2020, at 13:05, Hans Petter Selasky wrote: > > On 2020-01-03 11:56, Daniel Braniss wrote: >> Hi Hans, >> can you shed some light/help? >> thanks, >> danny >>> On 2 Jan 2020, at 11:11, Daniel Braniss wrote: >>> >>> Hi, >>> after connecting this QR reader I see a new /dev/ttyU but as soon as I try >>> tip, >>> the device disconnects. (BTW, it’s configured as a ‘Virtual Serial Port’) >>> >>> dmsg: >>> … >>> Jan 2 10:54:57 pampero kernel: umodem0 on uhub1 >>> Jan 2 10:54:57 pampero kernel: umodem0: >> 2/0, rev 1.10/1.00, addr 38> on usbus0 >>> Jan 2 10:54:57 pampero kernel: umodem0: data interface 1, has no CM over >>> data, has no break >>> Jan 2 10:56:01 pampero kernel: umodem0: at uhub1, port 2, addr 38 >>> (disconnected) >>> Jan 2 10:56:02 pampero kernel: umodem0: >>> Jan 2 10:56:02 pampero kernel: detached >>> Jan 2 10:56:03 pampero kernel: umodem0 on uhub1 >>> Jan 2 10:56:03 pampero kernel: umodem0: >> 2/0, rev 1.10/1.00, addr 38> on usbus0 >>> Jan 2 10:56:03 pampero kernel: umodem0: data interface 1, has no CM over >>> data, has no break >>> … >>> >>> and usbconfig: >>> pampero# usbconfig >>> ugen0.1: <0x8086 XHCI root HUB> at usbus0, cfg=0 md=HOST spd=SUPER >>> (5.0Gbps) pwr=SAVE (0mA) >>> ugen0.2: at usbus0, cfg=0 md=HOST spd=HIGH >>> (480Mbps) pwr=SAVE (500mA) >>> ugen0.4: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) >>> pwr=ON (98mA) >>> ugen0.5: at usbus0, cfg=0 >>> md=HOST spd=FULL (12Mbps) pwr=ON (100mA) >>> ugen0.6: at usbus0, cfg=0 md=HOST spd=SUPER >>> (5.0Gbps) pwr=SAVE (0mA) >>> ugen0.3: at usbus0, >>> cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) >>> ugen0.7: at usbus0, cfg=0 md=HOST spd=FULL >>> (12Mbps) pwr=ON (100mA) <— this is the QR >>> >>> any ideas? > > Can you run: > > usbdump -i usbus0 -f 7 -s 65536 -vvv > > Before attaching the device. Make sure numbers after ugen are 0 and 7. Look > for non ERR=0 . > > —HPS so I connected the QR reader to another host, running 12.1 stable. neo-black-2# usbconfig ugen0.1: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen1.1: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA) ugen2.1: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen3.1: at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA) ugen4.1: at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen5.1: at usbus5, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA) ugen5.2: at usbus5, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) and so i did neo-black-2# usbdump -i usbus5 -f2 -s 65536 -vvv nothing happens, so this is what I get after typing ’tip usb’ and nothing else - i don’t know who is doing the chitchat and after a very short while it disconnects. 16:25:16.753606 usbus5.2 SUBM-INTR-EP=0082,SPD=FULL,NFR=1,SLEN=0,IVAL=5 frame[0] READ 64 bytes flags 0x8a status 0xeb023 16:25:16.753645 usbus5.2 SUBM-CTRL-EP=,SPD=FULL,NFR=1,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 21 22 01 00 00 00 00 00 -- -- -- -- -- -- -- -- |!"..| flags 0x10 status 0xea1a3 16:25:16.755271 usbus5.2 DONE-CTRL-EP=,SPD=FULL,NFR=1,SLEN=0,IVAL=0,ERR=0 frame[0] WRITE 8 bytes flags 0x10 status 0xca1a1 16:25:16.808281 usbus5.2 SUBM-CTRL-EP=,SPD=FULL,NFR=1,SLEN=8,IVAL=50 frame[0] WRITE 8 bytes 02 01 00 00 81 00 00 00 -- -- -- -- -- -- -- -- || flags 0 <0> status 0x6a1a3 16:25:17.790304 usbus5.2 SUBM-CTRL-EP=,SPD=FULL,NFR=1,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 21 22 03 00 00 00 00 00 -- -- -- -- -- -- -- -- |!"..| flags 0x10 status 0x4a1a3 16:25:17.790346 usbus5.2 DONE-CTRL-EP=,SPD=FULL,NFR=0,SLEN=0,IVAL=50,ERR=TIMEOUT flags 0 <0> status 0x8a1a5 16:25:18.797312 usbus5.2 DONE-CTRL-EP=,SPD=FULL,NFR=0,SLEN=0,IVAL=0,ERR=TIMEOUT flags 0x10 status 0xaa1a5 16:25:18.850220 usbus5.2 SUBM-CTRL-EP=,SPD=FULL,NFR=1,SLEN=8,IVAL=50 frame[0] WRITE 8 bytes 02 01 00 00 81 00 00 00 -- -- -- -- -- -- -- -- || flags 0 <0> status 0x4a1a3 16:25:18.867314 usbus5.2 DONE-BULK-EP=0081,SPD=FULL,NFR=0,SLEN=0,IVAL=0,ERR=CANCELLED flags 0xa status 0xab00c 16:25:18.867332 usbus5.2 DONE-INTR-EP=0082,SPD=FULL,NFR=0,SLEN=0,IVAL=5,ERR=CANCELLED flags 0x8a status 0x8b01c 16:25:19.854309 usbus5.2 SUBM-CTRL-EP=,SPD=FULL,NFR=1,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 00 09 00 00 00 00 00 00 -- -- -- -- -- -- -- -- || flags 0x10 status 0x6a1a3 16:25:19.854355 usbus5.2 DONE-CTRL-EP=,SPD=FULL,NFR=0,SLEN=0,IVAL=50,ERR=TIMEOUT flags 0 <0> status 0xaa1a5 16:25:24.793325 usbus5.2 DONE-CTRL-EP=,SPD=FULL,NFR=0,SLEN=0,IVAL=0,ERR=TIMEOUT flags 0x10 status 0x8a1a5 16:25:25.382614 usbus5.2 SUBM-CTRL-EP=,SPD=FULL,NFR=1,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 00 05 02 00 00 00 00 00 -- -- -- -- -- -- -- -- || flags 0x50 status 0xea3a3 16:25:25.383872 usbus5.2
Re: usb QR reader
Hi Hans, can you shed some light/help? thanks, danny > On 2 Jan 2020, at 11:11, Daniel Braniss wrote: > > Hi, > after connecting this QR reader I see a new /dev/ttyU but as soon as I try > tip, > the device disconnects. (BTW, it’s configured as a ‘Virtual Serial Port’) > > dmsg: > … > Jan 2 10:54:57 pampero kernel: umodem0 on uhub1 > Jan 2 10:54:57 pampero kernel: umodem0: 2/0, rev 1.10/1.00, addr 38> on usbus0 > Jan 2 10:54:57 pampero kernel: umodem0: data interface 1, has no CM over > data, has no break > Jan 2 10:56:01 pampero kernel: umodem0: at uhub1, port 2, addr 38 > (disconnected) > Jan 2 10:56:02 pampero kernel: umodem0: > Jan 2 10:56:02 pampero kernel: detached > Jan 2 10:56:03 pampero kernel: umodem0 on uhub1 > Jan 2 10:56:03 pampero kernel: umodem0: 2/0, rev 1.10/1.00, addr 38> on usbus0 > Jan 2 10:56:03 pampero kernel: umodem0: data interface 1, has no CM over > data, has no break > … > > and usbconfig: > pampero# usbconfig > ugen0.1: <0x8086 XHCI root HUB> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) > pwr=SAVE (0mA) > ugen0.2: at usbus0, cfg=0 md=HOST spd=HIGH > (480Mbps) pwr=SAVE (500mA) > ugen0.4: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) > pwr=ON (98mA) > ugen0.5: at usbus0, cfg=0 > md=HOST spd=FULL (12Mbps) pwr=ON (100mA) > ugen0.6: at usbus0, cfg=0 md=HOST spd=SUPER > (5.0Gbps) pwr=SAVE (0mA) > ugen0.3: at usbus0, cfg=0 > md=HOST spd=FULL (12Mbps) pwr=ON (100mA) > ugen0.7: at usbus0, cfg=0 md=HOST spd=FULL > (12Mbps) pwr=ON (100mA) <— this is the QR > > any ideas? > > thanks, > danny > > ___ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
usb QR reader
Hi, after connecting this QR reader I see a new /dev/ttyU but as soon as I try tip, the device disconnects. (BTW, it’s configured as a ‘Virtual Serial Port’) dmsg: … Jan 2 10:54:57 pampero kernel: umodem0 on uhub1 Jan 2 10:54:57 pampero kernel: umodem0: on usbus0 Jan 2 10:54:57 pampero kernel: umodem0: data interface 1, has no CM over data, has no break Jan 2 10:56:01 pampero kernel: umodem0: at uhub1, port 2, addr 38 (disconnected) Jan 2 10:56:02 pampero kernel: umodem0: Jan 2 10:56:02 pampero kernel: detached Jan 2 10:56:03 pampero kernel: umodem0 on uhub1 Jan 2 10:56:03 pampero kernel: umodem0: on usbus0 Jan 2 10:56:03 pampero kernel: umodem0: data interface 1, has no CM over data, has no break … and usbconfig: pampero# usbconfig ugen0.1: <0x8086 XHCI root HUB> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) ugen0.2: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (500mA) ugen0.4: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (98mA) ugen0.5: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) ugen0.6: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) ugen0.3: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) ugen0.7: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) <— this is the QR any ideas? thanks, danny ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
