Re: Parport-PS/2 mouse conflicts (2.4.0-test2)

From: Tim Waugh (twaugh@redhat.com)
Date: Mon Jul 10 2000 - 06:57:55 EST


On Tue, Jul 04, 2000 at 10:14:48AM +0200, Bernd Paysan wrote:

> Tim Waugh wrote:
> > > a) set DMA channel to 1
> > > b) set IRQ to 7 instead of auto
> > > c) put modprobe lp right into /etc/rc.d/boot.local
> >
> > Could you please try to make it go wrong again, so we know which one
> > fixes it?
>
> Ok, backwards. rmmod lp parport_pc; modprobe -k lp; while X running did
> work. Then I set IRQ back to auto, removed and modprobed again, and
> tried to move the mouse -> hang (the autodetected IRQ is 7). It's the
> IRQ autoprobing. Now what I haven't done yet is to try if IRQ
> autoprobing would work before X starts up (i.e. conflict only with
> active PS/2 mouse).

Right. I suppose that's worth trying.

> > Hmm. Could you show me the dmesg output that parport gives please?
>
[...]
> 0x378: ECP settings irq=<none or set by other means> dma=<none or set by
> other means>
> parport0: PC-style at 0x378 (0x778), irq 7, dma 1 [PCSPP,TRISTATE,ECP,DMA]
[...]
> 0x278: CTR: wrote 0x0c, read 0xeb
> parport1: PC-style at 0x278, irq 5 [PCSPP]
[...]

Could you try getting rid of the options that you're giving to
parport_pc, to see if that actually does help (with your current
theory, it will).

Tim.
*/



-
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/



This archive was generated by hypermail 2b29 : Sat Jul 15 2000 - 21:00:11 EST