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).
> Hmm. Could you show me the dmesg output that parport gives please?
0x378: FIFO is 16 bytes
0x378: writeIntrThreshold is 8
0x378: readIntrThreshold is 8
0x378: PWord is 8 bits
0x378: Interrupts are ISA-Pulses
0x378: possible IRQ conflict!
0x378: ECP port cfgA=0x10 cfgB=0x00
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]
parport0: cpp_daisy: aa5500ff(98)
parport0: assign_addrs: aa5500ff(98)
parport0: Legacy device
lp0: using parport0 (interrupt-driven).
0x278: CTR: wrote 0x0c, read 0xeb
parport1: PC-style at 0x278, irq 5 [PCSPP]
parport1: cpp_mux: aa55f00f52ad51(87)
parport1: cpp_daisy: aa5500ff(80)
parport1: assign_addrs: aa5500ff(80)
parport1: cpp_mux: aa55f00f52ad51(87)
parport1: cpp_daisy: aa5500ff(80)
parport1: assign_addrs: aa5500ff(80)
lp1: using parport1 (interrupt-driven).
-- Bernd Paysan "If you want it done right, you have to do it yourself" http://www.jwdt.com/~paysan/- 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 : Fri Jul 07 2000 - 21:00:14 EST