Hi: A USB-serial adapter has been connected to my Compaq C301TU laptop. the other end connects to my AMD64 X2 box.
Both the systems are running DragonFly BSD 2.4.1. On the laptop, the USB-serial device is detected as ugen0: <Prolific Technology Inc. USB-Serial Controller, class 0/0, rev 1.10/3.00, addr 2> on uhub0 The entries in the /dev directory look like crw-r--r-- 1 root operator 27, 0x00000000 Oct 22 09:33 /dev/ugen0 crw-r--r-- 1 root operator 27, 0x00000001 Oct 22 09:33 /dev/ugen0.1 crw-r--r-- 1 root operator 27, 0x00000002 Oct 22 09:33 /dev/ugen0.2 crw-r--r-- 1 root operator 27, 0x00000003 Oct 22 09:33 /dev/ugen0.3 The output of the usbdevs -d -v command is Controller /dev/usb0: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 uhub0 port 1 addr 2: full speed, power 100 mA, config 1, USB-Serial Controller(0x2303), Prolific Technology Inc.(0x067b), rev 3.00 ugen0 port 2 powered Controller /dev/usb1: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 uhub1 port 1 powered port 2 powered Controller /dev/usb2: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 uhub2 port 1 powered port 2 powered The generic 'ucom' driver has been loaded using laptop# kldload -v ucom Loaded ucom, id=5 My query is: i donot see any cua0, ttyS0, ttyUSB0, so, what is the virtual serial device to be specified while running cu ? ie. # cu -s 19200 -l /dev/<device> thanks Saifi.
