http://bugzilla.kernel.org/show_bug.cgi?id=5832
------- Comment #41 from [EMAIL PROTECTED] 2007-11-11 07:32 ------- Sorry it is ecp_probe (modinfo should show you): ecp_probe= Another test revealed that it's probably not that easy -> the correct ACPI device seem to get used. You could also add: CONFIG_PNP_DEBUG=y and add a #define DEBUG 1 in drivers/parport/parport_pc.c between: #undef DEBUG and #ifdef DEBUG and a: #define DEBUG_PARPORT 1 in include/linux/parport_pc.h after: #include <asm/io.h> If you run this with PNPBIOS and PNPACPI, I think we should have a all debug info that could be "quickly" fetched for the parallel device. But this might also not bring us further... PNPACPI BIOS parts export different settings than PNPBIOS parts and I am pretty sure the parsing etc. is correct. Maybe this machine is only supported with PNPBIOS and PNPACPI simply returns copy and pasted, wrong ACPI code that never was tested (supported Windows OS did only use PNPBIOS code in old times?). In this case pnpacpi=off is the only workaround that makes sense, maybe a blacklist could be added to activate this on all machines, which BIOS is older than xy like we do with acpi in general? -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------------------------------------------------------------------------- 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
