Re: 2.1.9 still don't like gpm
Philippe Strauss (philou@sicel-home-1-4.urbanet.ch)
Wed, 13 Nov 1996 21:15:47 +0100 (MET)
Michael L. Galbraith wrote:
>
> On Wed, 13 Nov 1996, Philippe Strauss wrote:
> >
> > Exactly the same for me. The wild interrupt
> > detect doesn't work,it report irq 0 for both port,
> > hence the jerky mouse behaviour. My UART is a 16550A,
> > and is detected correctly. Was ok with 2.1.7,
> > start giving trouble with 2.1.8.
> >
> > --
> > Philippe Strauss, CH-1092 Belmont
> >
> > Email: <philippe.strauss@urbanet.ch>
> > Homepage: http://sicel-home-1-4.urbanet.ch
> >
> FYI: I am not seeing this problem w. 2.1.9 libc-5.4.11, and gpm X or no X.
> My motherboard is an original Intel product w. bios updated to fix PCI prob.
> Are your systems overclocked and possibly a little glitchy?
>
> My mouse has a cold-start problem as a bizzare after-effect of a lightning
> strike, but otherwise works fine.
> (Modem wasn't so lucky - chip with a big hole blown through the top) :(
>
> <dmesg snip>
> 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
My system is quiet stable, looooooooong time that I haven't
had any hardware failure, not overclocked (my mainboard
detect the trick and refuse to start when overclocking -
except from 75 to 90 MHz - triton chipset feature?)
kernel report:
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
0setserial from debian 1.1 (setserial is 2.10) report wrongly:
/dev/cua0 at 0x03f8 (irq = 0) is a 16550A
/dev/cua1 at 0x02f8 (irq = 0) is a 16550A
After forcing it manually:
/dev/cua0 at 0x03f8 (irq = 4) is a 16550A
/dev/cua1 at 0x02f8 (irq = 3) is a 16550A
and it work then fine.
libc-5.4.11, gcc-2.7.2, linux-2.1.9, no lightning strike, nor tornados.. :)
--
Philippe Strauss, CH-1092 Belmont
Email: <philippe.strauss@urbanet.ch>
Homepage: http://sicel-home-1-4.urbanet.ch