After finding out what my problem was... I'm sorry for posting this
message *blush* It turned out that my serial port on the back of the
computer was loose not making total contact with the serial cable. I
tightened it up, it worked. Thanks to all who responded.
Just a note for those this may be of interest to...
out of The Linux Serial HOWTO v1.9, 2 January 1997
note that IRQ 2 is the same as IRQ 9. You can call it either 2 or 9, the
serial driver is very understanding.
This is my understanding or these IRQ's
Irq 9 is redirected to irq2. irq2 on AT systems is the Cascade interrupt
for irq 8-15.
Using one of these two lines in /etc/rc.boot/0setserial has the same
outcome, it will be detected as irq2:
${SETSERIAL} -b /dev/ttyS3 irq 9 port 0x2E8 skip_test autoconfig
${STD_FLAGS}
${SETSERIAL} -b /dev/ttyS3 irq 2 port 0x2E8 skip_test autoconfig
${STD_FLAGS}
again thanks for all of the replies..
- [EMAIL PROTECTED]
On Mon, 18 Aug 1997, Joost Kooij wrote:
>
>
> On Sun, 17 Aug 1997, Ricardo Muggli wrote:
>
> > How do I set up a com port in debian that has a non standard irq?
> > The port I want to use is 0x2E8 irq2
>
> Um, I don't think it is a very healthy practice to use irq 2 for a serial
> port.
>
> Irq 2 is called the "cascade interrupt". Pc-xt's, which have only one
> interrupt controller, have 8 irq's, but in at's a second controller is
> cascaded from the primary interrupt controller's irq 2 to yield a total of
> 15 usable interrupts (because you cannot use irq 2 for a real interrupt
> anymore.) Read a pc-hardware faq if you want to know more about this.
>
> So unless you are running linux on a 8086, you can forget irq 2, I think.
>
>
> Joost
>
>
> --
> TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
> [EMAIL PROTECTED] .
> Trouble? e-mail to [EMAIL PROTECTED] .
>
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
