HowTo Configure an External Modem Attached via USB 2.0 to Serial Adapter Cable

[Dog Walker]

On 7/7/07, Net Llama! <netllama at linux-sxs.org> wrote:
> On Sat, 7 Jul 2007, Dog Walker wrote:
> > On 7/7/07, Net Llama! <netllama at linux-sxs.org> wrote:
> >> On Sat, 7 Jul 2007, Dog Walker wrote:
> >>> SuSE 10.2
> >>> (This all works in WindowXP where the modem is at COM4)
> >>> --------------------------------------------------------------------------------------
> >>> dw at linux:~/myprojects/python> /usr/sbin/hwinfo --usb
> >>> 01: USB 101.0: 10a00 Hub
> >>>  [Created at usb.113]
> >>>  Unique ID: B3Fu.00ImP66eyQ9
> >>>  Hardware Class: hub
> >>>  Model: "USB UHCI Root Hub"
> >>>  Hotplug: USB
> >>>  Device: "USB UHCI Root Hub"
> >>>  Serial ID: "1060"
> >>>  USB GUID: 000000000000000000001060
> >>>  USB Device status: driver active ("hub")
> >>>  Speed: 1.5 Mbps
> >>>  Config Status: cfg=no, avail=yes, need=no, active=unknown
> >>> dw at linux:~/myprojects/python>
> >>> --------------------------------------------------------------------------------------
> >>> The modem in question is a Microcom 415 which works without incident
> >>> when connected to the serial port of a SuSE 9.0 box. I guess I need to
> >>> know how to set up a device for it as connected and tell YAST to use
> >>> it as the modem. Do I need a driver for the adapter cable?
> >>> Thanks for any help!
> >>
> >> I must be dense, because i don't see a question anywhere in your email.
> >> What's the problem you're having?
> >>
> >
> > The question, restated, is how to connect the modem one configures
> > with YAST, to an external serial modem connected via a USB 2.0 to
> > Serial Port cable adapter. The answer appears to be to link
> > /dev/ttyUSB0 to one of the devices in the dropdown list in the modem
> > configuration dialog: I chose /dev/modem. I suppose choosing one of
> > the USB devices would work as well. Or one of the serial port devices.
> > The problem arose because the box lacks a serial port and I have an
> > external serial modem.
>
> I still don't understand the purpose of your email if you already know the
> answer to your question.  Are you having a problem or not?
>

Not. (Was having a problem. Found answer and posted it.)

> Anyway, in my experience USB serial modems are identified as /dev/ttyACMx,
> not /dev/ttyUSB0, which is a usb serial converter.
>
> I think you'd be far better off if you stopped using yast altogether, and
> actually understood what was going on.
>

Thanks to your information, I think I now understand what I needed to
do. I didn't know that the serial converter got a device number. Now I
do.

Yast just knows about /dev/modem, /dev/ttyACMx, and /dev/ttySx. Linux
assigns /dev/ttyUSB0 to the USB->Serial Port Adapter. If I link
/dev/ttyUSB0 to /dev/ttyS0, I can choose it as the modem, just as if
it were an actual serial port.

Thanks Lonni!

> --
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Lonni J Friedman                        netllama at linux-sxs.org
> LlamaLand                               http://netllama.linux-sxs.org
> _______________________________________________
> Linux-users mailing list ( Linux-users at linux-sxs.org )
> Unsub/Password/Etc: http://mail.linux-sxs.org/cgi-bin/mailman/listinfo/linux-users
>
> ***  OFF TOPIC conversations should get sent to general at linux-sxs.org.  This rule will be strictly enforced.  ***
>
> Need to chat further on this subject? Check out #linux-users on irc.linux-sxs.org !
>


-- 
I have seen the future and I'm not in it!