COM 2 and COM 4 share and IRQ by DOS default. If they modem is configured Plug
and Play Win95 will assign it another IRQ to avoid conflicts (usually). To
accomplish this in Linux you need isapnptools. This will allow you to duplicate
your Win95 settings. If it is jumpered for IRQ 5 add a line to
/etc/rc.d/rc.local that reads
"setserial /dev/cua3 irq 5 uart 16550a spd_vhi" (minus the quotes)
this tells Linux that COM 4 is a non-standard port using IRQ 5, a 16550A uart
chip (to allow high speed communications) and to allow high speed communications
up to 115200BPS. Actually you will need this line to allow you to use IRQ 5 in
either case. Just read the isapnp man page or write me for help.
Helms, Phil wrote:
> I have Linux (kernel 2.0.30, Slackware 3.4) on a PC at home, trying to dial
> in using Minicom, to the host system where I work.
>
> I can do this quite well under Windows 95 using Reflections, but have had no
> success using Linux and Minicom. It appears to dial OK, and (judging by the
> speaker sound) appears to handshake OK, and Minicom even goes online, but
> I never see a connect message, and can get no response from the keyboard.
>
> I tried playing with the modem offline, but when I queried it for
> information
> it responded at the rate of one character every few seconds. (I caught
> some shut-eye waiting for the response to complete... I kid you not.)
>
> The modem is an internal Sportster 33.6, and is hooked into COM4 (cua3).
>
> When in Windows, I noticed that the IRQ for the modem was 5, while the IRQ
> for the COM port was 3, which also duplicated another COM port. Could this
> inconsistency and duplication in IRQ's be the cause of the problem? If so,
> how would I go about fixing it?
>
> I would be grateful for any help with this. I'm a VMS person, and I'm
> enjoying learning Linux, but setting it up has been very frustrating.
>
> --
> Phil Helms
> Community College Computer Services
> [EMAIL PROTECTED]
