On Thu, 1 Jul 1999, Mike Abney wrote:
> So far, my searches and the responses I've receive thus far haven't
> solved the problem. (BTW, thanks Jeremy for the suggestion, but no
> luck. Also, hey bug, does an external modem try to show up as PCI or
> ISA? That seems a bit strange to me.)
>
uh. gulp. sorry. I thought I had read in the message it was an internal
modem. Built in serial ports are on PCI architecture and should be known.
Plugged in serial ports (com3/com4..com5/com6..com7/com8) are usually ISA.
My bios allows me to disable/enable on board serial ports and change
which serial port (com1/com2) is associated with which plug on the
computer.
In any case, setserial is used to set the baud rate of the modem port.
If you want to go over 9600 (or is it 19,200), you have to set a high baud
rate parameter before you program the data rate of the ports. Aeons ago I
got modems to work on linux, and then didn't need them any more. You may
have a conflict with getty (or mgetty or agetty or uucp or the last
minicom invocation or ...) and that port isn't available. Also the port
can be locked against usage with a lock file in /var/lock.
Also you may not have read/write permissions to the port as the user you
are running as. also minicom can be persnickity. I stopped it
and started it once, and it started working. Also, handshaking may not be
quite right, have you tried no-handshake on the port? Also, on the newer
version of linux, /dev/cuax isn't the port any more. I believe it is only
/dev/ttySx. Maybe you are still trying to use /dev/cuax? .....
I think you get the picture. It takes perserverance and sometimes test
equipment to get a modem to work under linux once it decides to be
stubbor, unless you've done it a million times before <exaggggggeration>
:)
bug
