Messages in this thread | | | Date | Fri, 8 Jan 1999 22:23:55 -0800 | From | Sang Kang <> | Subject | Re: serial port problem with 2.1.132-2.2.0pre5 |
| |
On Fri, Jan 08, 1999 at 11:46:42PM -0500, Theodore Y. Ts'o wrote: > Date: Thu, 7 Jan 1999 04:09:29 -0800 > From: Sang Kang <kernel@mocha.sarang.net> > > The issue is that, when I first issued that command (at+...?) using > the mouse's middle button, not all characters were copiled to the serial > port but rather forgotten some characters, only displaying "at+". > when I typed the entire AT command, it worked fine, but when the input > is too fast it seems to loose the characters. > Changing the baud rate lower didn't help. > > This one's easy. You have one of the buggy uart's which failed to > deal with the new IRQ autodetection (which changed as part of code > simplification and an attempt to deal with other buggy uarts....) > > Check with setserial; you probably have an rc.serial file which is > trying to do IRQ autodetection, and the autodetection is failing, > leaving your IRQ for the port set to zero. Hmm... perhaps I should > patch the serial driver to set the irq back to its original value if the > autodetect fails, since that's more likely to work. > <snip>
Thanks for reply, but I don't think I would agree with that. I had setserial /dev/ttyS0 irq 4 port 0x3f8 uart 16550 in my rc.local for a year now (since the purchase of modem, recently switched from cua0 to ttyS0). And if buggy UART is the case (btw, it's an external modem w/ UART on motherboard) the following questions arise:
1) I doubt Intel(Triton) will manufacture such a buggy motherboard. 2) Why would kernel 2.0.36 work then?
Sang Kang
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |