Thanks for all the possibilities. I am running a 233MHz AMD K6 PC,
Debian. I'm not sure what the problem was, but I tried it once again
last night and it was working perfectly. Go figure. Perhaps I had a
screen session open in the background that was interfering, or maybe I
had a heavy load on my system and it was the interrupt thing. It worked
in both minicom and screen, BTW.
screen /dev/ttyS1 9600,ixoff
and minicom with the 9600 8N1 settings, no hardware or software control.
Thanks!
Hans :)
On Tue, May 07, 2002 at 02:03:52AM -0700, Christian Suder cried:
> Richard Hirst wrote:
>
> > On Tue, May 07, 2002 at 01:31:18AM -0700, Christian Suder wrote:
> > > Richard Hirst wrote:
> > > > What are you running minicom on? If it's a 386 using an old UART with no
> > > > FIFO then I'd suggest it just couldn't cope with bursts of data at 9.6K.
> > > > Not very likely though. When you type things at the BOOT_ADMIN prompt
> > > > is it all echoed back properly?
> > >
> > > No, the UART is certainly not a problem at 9600 bit/s.
> >
> > Well, if whatever is servicing the UART chooses to disable interrupts
> > for several milliseconds at a time, then you could get this effect.
>
> True, that is the theory - my empirical answer is that I have never seen any
> issues running 9600 bit/s even on a windooze machine. I certainly was using
> 14.4k modems with 19200 bit./s setting on the serial port years ago with both
> M$oft and linux (when it came on a stack of 5 1/4" diskettes... ;-)
>
> C,
>
>
> --
> To UNSUBSCRIBE, email to debian-hppa-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
--
YAAH! DEATH TO OATMEAL!
-- Calvin
Attachment:
pgpj4e0EXHowy.pgp
Description: PGP signature