ok, my last post on this apparently didn't make it to the list for some
reason -- so here is the latest status again.
I did a double-check on the hardware this last weekend. Nothing
is out of order there -- No devices conflict, the serial port is setup
properly(this is a DTC 2278E board in case anyone wants to know).
I tried re-compiling the kernel with the proper values set in
serial.c, and I stopped using the setserial utility to set the parameters.
The kernel prints out the right information on bootup, but the same
problem persists. Using setserial doesn't appear to make a difference in
this re-compiled kernel, either.
At this point, I am open to more suggestions. Off the top of my
head, I would probably say that maybe we aren't initializing the card
properly, or we've found a bug in the DTC 2278 hardware, but I would also
be willing to admit I could be on shaky ground with this diagnosis(since
the mouse on com1 via the DTC works fine). TIA.
-- FAQ Suggestions: Q: I upgraded without reading release notes, now my system's broke - why? A: What the @!#* did you expect? (this assumes that someone reads the faq, of course ;)