Re: USB-Serial adapter, how to make /dev/cuad* appear?
Benjamin Lutz wrote: Roland Smith wrote: Looking at ucom(4): FILES /dev/cuaU? See if that exists. No such luck I'm afraid. There's only cuaU0, which belongs to the onboard serial port too. No, cuaU0 belongs to the ucom(4) driver. It certainly does _not_ belong to the sio(4) driver. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd ... there are two ways of constructing a software design: One way is to make it so simple that there are _obviously_ no deficiencies and the other way is to make it so complicated that there are no _obvious_ deficiencies.-- C.A.R. Hoare, ACM Turing Award Lecture, 1980 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB-Serial adapter, how to make /dev/cuad* appear? [Solved]
I finally figured this out. Turns out the FreeBSD side of things worked from the start, and it was the hardware that was broken. A replacement adapter works like a charm. Oh and yes, Oliver, you're perfectly right, /dev/cuaU0 is indeed created by ucom. I was confused by the device having the creation date of when the system was booted, even though it was dynamically created a couple of days later. Thanks for all your help! Cheers Benjamin signature.asc Description: This is a digitally signed message part.
Re: USB-Serial adapter, how to make /dev/cuad* appear?
On Tue, 23 Oct 2007 18:06:08 +0200 Benjamin Lutz [EMAIL PROTECTED] wrote: I've bought an USB-Serial adapter in order to use an old serial 33.6k modem. I've loaded the uplcom and ucom modules, but am unsure how to proceed from here. The system runs FreeBSD 6.2-RELEASE-p8. When connecting the adapter, dmesg says: ucom0: Prolific Technology Inc. USB-Serial Controller D, rev 1.10/4.00, addr 3 usbdevs -v says: port 6 addr 3: full speed, power 100 mA, config 1, USB-Serial Controller D(0x2303), Prolific Technology Inc.(0x067b), rev 4.00 I'd expect some device to show up in /dev, cuad1, ucom0, something like that, but I get nothing. (cuad0 is taken by the onboard serial port, which, alas, isn't wired to the outside of the case). Perhaps you need to load umodem(4) also? Cheers, Ian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB-Serial adapter, how to make /dev/cuad* appear?
Roland Smith wrote: On Tue, Oct 23, 2007 at 08:17:01PM +0200, Benjamin Lutz wrote: On Tuesday 23 October 2007 19:54:44 Roland Smith wrote: On Tue, Oct 23, 2007 at 06:06:08PM +0200, Benjamin Lutz wrote: I'd expect some device to show up in /dev, cuad1, ucom0, something like that, but I get nothing. (cuad0 is taken by the onboard serial port, which, alas, isn't wired to the outside of the case). Looking at ucom(4): FILES /dev/cuaU? See if that exists. No such luck I'm afraid. There's only cuaU0, which belongs to the onboard serial port too. Does the onboard serial port work via USB? How odd! On my standard PC, the serial ports are driven by the sio driver, and have /dev/cuad* and /dev/ttyd* devices, noc cuaU. No, that one's a standard serial port, driven by sio as well, and creates /dev/cuad0, /dev/cuaU0, maybe some /dev/tty* as well, I don't know. Do you have the correct driver for the converter loaded next to ucom? The ucom manual page gives a list of them. Yes, uplcom is the right driver. (Or at least I think so, because the device and manufacturer ids that usbdevs -v gives me match those in /usr/src/sys/dev/usb/uplcom.c .) Besides, without the uplcom module loaded, I only get an ugen device, so it seems to attach to the device ok. Cheers Benjamin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB-Serial adapter, how to make /dev/cuad* appear?
Ian Smith wrote: On Tue, 23 Oct 2007 18:06:08 +0200 Benjamin Lutz [EMAIL PROTECTED] wrote: I've bought an USB-Serial adapter in order to use an old serial 33.6k modem. I've loaded the uplcom and ucom modules, but am unsure how to proceed from here. The system runs FreeBSD 6.2-RELEASE-p8. When connecting the adapter, dmesg says: ucom0: Prolific Technology Inc. USB-Serial Controller D, rev 1.10/4.00, addr 3 usbdevs -v says: port 6 addr 3: full speed, power 100 mA, config 1, USB-Serial Controller D(0x2303), Prolific Technology Inc.(0x067b), rev 4.00 I'd expect some device to show up in /dev, cuad1, ucom0, something like that, but I get nothing. (cuad0 is taken by the onboard serial port, which, alas, isn't wired to the outside of the case). Perhaps you need to load umodem(4) also? Tried that, it has no effect. Cheers Benjamin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB-Serial adapter, how to make /dev/cuad* appear?
On Wed, Oct 24, 2007 at 09:26:20AM +0200, Benjamin Lutz wrote: Does the onboard serial port work via USB? How odd! On my standard PC, the serial ports are driven by the sio driver, and have /dev/cuad* and /dev/ttyd* devices, noc cuaU. No, that one's a standard serial port, driven by sio as well, and creates /dev/cuad0, /dev/cuaU0, maybe some /dev/tty* as well, I don't know. How do you know that cuaU0 belongs to the sio driver? It should belong to ucom. According to the manual, sio(4) devices only create ttyd and cuad devices. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgphtsum9H1Mv.pgp Description: PGP signature
Re: USB-Serial adapter, how to make /dev/cuad* appear?
On 2007-10-24 17:15, Roland Smith wrote: On Wed, Oct 24, 2007 at 09:26:20AM +0200, Benjamin Lutz wrote: Does the onboard serial port work via USB? How odd! On my standard PC, the serial ports are driven by the sio driver, and have /dev/cuad* and /dev/ttyd* devices, noc cuaU. No, that one's a standard serial port, driven by sio as well, and creates /dev/cuad0, /dev/cuaU0, maybe some /dev/tty* as well, I don't know. How do you know that cuaU0 belongs to the sio driver? It should belong to ucom. According to the manual, sio(4) devices only create ttyd and cuad devices. I'm guessing based on its timestamp pointing to the last system boot, when the USB adapter wasn't connected, based on the device persisting when I unplug the USB adapter. Cheers Benjamin pgpUzEzgy1i5J.pgp Description: PGP signature
Re: USB-Serial adapter, how to make /dev/cuad* appear?
On Wed, Oct 24, 2007 at 05:23:48PM +0200, Benjamin Lutz wrote: On 2007-10-24 17:15, Roland Smith wrote: On Wed, Oct 24, 2007 at 09:26:20AM +0200, Benjamin Lutz wrote: Does the onboard serial port work via USB? How odd! On my standard PC, the serial ports are driven by the sio driver, and have /dev/cuad* and /dev/ttyd* devices, noc cuaU. No, that one's a standard serial port, driven by sio as well, and creates /dev/cuad0, /dev/cuaU0, maybe some /dev/tty* as well, I don't know. How do you know that cuaU0 belongs to the sio driver? It should belong to ucom. According to the manual, sio(4) devices only create ttyd and cuad devices. I'm guessing based on its timestamp pointing to the last system boot, when the USB adapter wasn't connected, based on the device persisting when I unplug the USB adapter. Is ucom loaded as a module? If so, try unloading and re-loading it and uplcom. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgp9tLW0SulGe.pgp Description: PGP signature
Re: USB-Serial adapter, how to make /dev/cuad* appear?
On Tue, Oct 23, 2007 at 06:06:08PM +0200, Benjamin Lutz wrote: I'd expect some device to show up in /dev, cuad1, ucom0, something like that, but I get nothing. (cuad0 is taken by the onboard serial port, which, alas, isn't wired to the outside of the case). Looking at ucom(4): FILES /dev/cuaU? See if that exists. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpGwot6d1Idk.pgp Description: PGP signature
Re: USB-Serial adapter, how to make /dev/cuad* appear?
On Tuesday 23 October 2007 19:54:44 Roland Smith wrote: On Tue, Oct 23, 2007 at 06:06:08PM +0200, Benjamin Lutz wrote: I'd expect some device to show up in /dev, cuad1, ucom0, something like that, but I get nothing. (cuad0 is taken by the onboard serial port, which, alas, isn't wired to the outside of the case). Looking at ucom(4): FILES /dev/cuaU? See if that exists. No such luck I'm afraid. There's only cuaU0, which belongs to the onboard serial port too. Cheers Benjamin signature.asc Description: This is a digitally signed message part.
Re: USB-Serial adapter, how to make /dev/cuad* appear?
On Tue, Oct 23, 2007 at 08:17:01PM +0200, Benjamin Lutz wrote: On Tuesday 23 October 2007 19:54:44 Roland Smith wrote: On Tue, Oct 23, 2007 at 06:06:08PM +0200, Benjamin Lutz wrote: I'd expect some device to show up in /dev, cuad1, ucom0, something like that, but I get nothing. (cuad0 is taken by the onboard serial port, which, alas, isn't wired to the outside of the case). Looking at ucom(4): FILES /dev/cuaU? See if that exists. No such luck I'm afraid. There's only cuaU0, which belongs to the onboard serial port too. Does the onboard serial port work via USB? How odd! On my standard PC, the serial ports are driven by the sio driver, and have /dev/cuad* and /dev/ttyd* devices, noc cuaU. Do you have the correct driver for the converter loaded next to ucom? The ucom manual page gives a list of them. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpxD3nYXTpZk.pgp Description: PGP signature
