USB->Serial adapter, how to make /dev/cuad* appear?

Hello,

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).

Any help is appreciated!

Cheers
Benjamin

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/~r
smith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much
appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725
(KeyID: C321A725)

On Tue, Oct 23, 2007 at 08:17:01PM +0200, Benjamin Lutz
wrote:
> On Tuesday 23 October 2007 19:54:44 Rolannessto 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/~r
smith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much
appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725
(KeyID: C321A725)

Rolannessto wrote:
> On Tue, Oct 23, 2007 at 08:17:01PM +0200, Benjamin Lutz
wrote:
>> On Tuesday 23 October 2007 19:54:44 Rolannessto
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-questionsfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribefreebsd.org"

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/~r
smith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much
appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725
(KeyID: C321A725)

On 2007-10-24 17:15, Rolannessto 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

On Wed, Oct 24, 2007 at 05:23:48PM +0200, Benjamin Lutz
wrote:
> On 2007-10-24 17:15, Rolannessto 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/~r
smith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much
appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725
(KeyID: C321A725)