On Mon, 23 Sep 1996, Susan G. Kleinmann wrote:
> ${SETSERIAL} -b /dev/cua2 ${AUTO_IRQ} skip_test autoconfig ${STD_FLAGS}
>
> If so, you need to change it to this:
> ${SETSERIAL} -b /dev/cua2 ${AUTO_IRQ} skip_test autoconfig ${STD_FLAGS}
> spd_vhi
>
> Or you could be more brute-force about it an
On Mon, 23 Sep 1996, Rob Hanson wrote:
> Hey there everyone,
>
> I am a bit new to the linux thing, and I seem to be having some trouble
> locating my modem. It is an internal 33.6 cardinal voice modem, and it
> uses com3 on my win95 setup. Being an internal com port, I don't think
> it was con
Rob Hanson wrote:
> I am a bit new to the linux thing, and I seem to be having some
> trouble locating my modem. It is an internal 33.6 cardinal voice
> modem, and it uses com3 on my win95 setup.
You need to use the 'setserial' command to tell the system about your
modem. You should be able to
Hi Rob --
If your modem is on COM3, then it is referred to as /dev/cua2 during boot-up
and as /dev/ttyS2 for most operations thereafter. If you are trying to get
it to work at high speed, then I think what you need to do is to change
a line in /etc/rc.boot/0setserial. I suspect you have a line
Hey there everyone,
I am a bit new to the linux thing, and I seem to be having some trouble
locating my modem. It is an internal 33.6 cardinal voice modem, and it
uses com3 on my win95 setup. Being an internal com port, I don't think
it was configured when I added the serial ports to the kernel
5 matches
Mail list logo