Can anybody help this guy?
------- Forwarded Message
Date: Thu, 18 Jan 2001 22:33:14 +0100
From: ilsensine <ilsensine@inwind.it>
User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.0 i686; en-US; m18) Gecko/20001107 Netscape6/6.0
X-Accept-Language: it, en
MIME-Version: 1.0
To: Philip.Blundell@pobox.com
Subject: parport_pc and via vt82c686a
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
I report here a strange behaviour of the parport_pc module on my k7m
m/b. I use a 2.4.0 kernel.
My bios settings enable both ecp and epp protocols on parallel port;
when I load parport_pc I get the following message in syslog:
Jan 18 22:01:59 Ilsensine kernel: 0x378: FIFO is 16 bytes
Jan 18 22:01:59 Ilsensine kernel: 0x378: writeIntrThreshold is 8
Jan 18 22:01:59 Ilsensine kernel: 0x378: readIntrThreshold is 8
Jan 18 22:01:59 Ilsensine kernel: 0x378: PWord is 8 bits
Jan 18 22:01:59 Ilsensine kernel: 0x378: Interrupts are ISA-Pulses
Jan 18 22:01:59 Ilsensine kernel: 0x378: possible IRQ conflict!
Jan 18 22:01:59 Ilsensine kernel: 0x378: ECP port cfgA=0x10 cfgB=0x00
Jan 18 22:01:59 Ilsensine kernel: 0x378: ECP settings irq=<none or set
by other means> dma=<none or set by other means>
Jan 18 22:01:59 Ilsensine kernel: parport0: PC-style at 0x378 (0x778),
irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,ECP,DMA]
Jan 18 22:01:59 Ilsensine kernel: parport0: cpp_daisy: aa5500ff(38)
Jan 18 22:01:59 Ilsensine kernel: parport0: assign_addrs: aa5500ff(38)
Jan 18 22:01:59 Ilsensine kernel: parport0: cpp_daisy: aa5500ff(38)
Jan 18 22:01:59 Ilsensine kernel: parport0: assign_addrs: aa5500ff(38)
Jan 18 22:01:59 Ilsensine kernel: parport_pc: Via 686A parallel port:
io=0x378, irq=7, dma=3
As you can see, a "possible IRQ conflict" is detected, and the epp
protocol is not shown as available. Actually, irq 7 is owened only by
the parallel port. This message occours *only* if I enable both ecp and
epp by bios; I also tried many solutions (various bios settings and
parameters to parport_pc), but the message is always the same. I use at
wotk a PIII-based pc with the same kernel, but it doesn't seem to have
this problem.
I'm not so skilled in kernel matters, but I think It's a problem of the
686a controller (wich also seems to cause troubles to many kernel
developers, as I read). What do you think?
Please email me if you need more details.
Thank you for your contribute to the linux kernel :-)
Giancarlo Formicuccia
ilsensine@inwind.it
------- End of Forwarded Message
-- To unsubscribe, send mail to: linux-parport-request@torque.net --
-- with the single word "unsubscribe" in the body of the message. --
This archive was generated by hypermail 2b29 : Thu Jan 18 2001 - 16:52:17 EST