http://bugzilla.kernel.org/show_bug.cgi?id=5832
------- Comment #22 from [EMAIL PROTECTED] 2007-08-07 10:56 ------- Thanks for trying those. But I'm afraid I wasted your time. This tells us what we already knew: the port works when we run it with interrupts and DMA disabled. The question for me is whether the problem is in PNPACPI (where I might be able to fix it) or in the parport driver (where I don't have any clue what to look for). PNPACPI tells us the device uses IRQ 7 and DMA channel 3. Without PNPACPI, the probe found IRQ 7 (but didn't use the IRQ) and didn't look for the DMA channel. So I think PNPACPI is probably telling us the right thing. You don't have Windows on this box also, do you? If we could tell that Windows uses IRQ 7 and DMA channel 3, I'd be even more confident that the PNPACPI info is correct. I suspect this is really a parport_pc driver problem. I don't have any good ideas about how to explore that. -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
