From: wmoore@pitt.edu (William D Moore) Subject: Re: [ANSWERS]: Serial Comm Problems Date: 5 May 1993 17:24:02 GMT
Rick Miller - Linux Device Registrar (rick@ee.uwm.edu) wrote:
: You should use /dev/cuaS3 for your modem. You probably don't yet *have*
: this device though, so you'll need to do like so:
: mknod /dev/cuaS3 c 5 66
: and use /dev/cuaS3 when calling out. You should use /dev/ttyS3 for
: setting up dial-in through the same modem though. Two names for the
: same device... one for dial-IN, the other for dial-OUT. This is so
: the kernel can do the locking for you (to prevent you from stomping
: on some poor luser's dial-up login).
I've done something similar to this based on a posting someone made to this
group a while ago. Per that same posting I also made sure the modem group
was set probably, and created a link to a file /dev/modem.
When I try to use kermit, it begins the dialout sequence, hangs, and then
gives me a "Can't initialize modem" message. When I try to use setserial
on /dev/modem or /dev/cua0 (the device file I created with mknod) I always
get a message that says something about the file name I'm passing as a
parameter to setserial is invalid and that it can't get the info.
I've tried to recreate these character files but still get the same messages.
I'm obviously missing something when I set this up, but I'm no unix expert
(yet!) so any advice would be appreciated.
Oh, by the way. I'm using an external 2400 baud modem that's connected to
the COM1 port IRQ4.