Messages in this thread |  | | From | (Mark Crichton) | Subject | Re: 2.1.8 Problems (Serial problems) | Date | Wed, 13 Nov 1996 10:39:20 -0500 |
| |
Well, with all this talk about serial problems, I'd like to toss in my little problem that cropped up with 2.1.8. Below is some kernel boot output: POSIX conformance testing by UNIFIX Serial driver version 4.20 with no serial options enabled tty00 at 0x03f8 (irq = 4) is a 16550A tty01 at 0x02f8 (irq = 3) is a 16550A tty02 at 0x03e8 (irq = 4) is a 16550A
Everything's fine, until my init kicks up the 0setserial script I've got, a sample from the script is below: ~ # setserial -b /dev/cua0 auto_irq skip_test autoconfig session_lockout ~ # setserial -bg /dev/cua* /dev/cua0 at 0x03f8 (irq = 0) is a 16550A /dev/cua1 at 0x02f8 (irq = 0) is a 16550A /dev/cua2 at 0x03e8 (irq = 0) is a 16550A
I find it odd that my irq's were set to 0 (the UARTs are correctly as well as the port addresses). The ports are usable, but the character loss is EXTREMELY bad. Simply doing a 'setserial /dev/cua0 irq 4' allows everything to work normally.
The script worked well in 2.1.7, in 2.1.8 setserial doesn't like something. The setserial is the version that comes with Debian 1.1 (10 something I believe)
Could this be of use?
Mark Crichton
|  |