[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200809221701.13569.bjorn.helgaas@hp.com>
Date: Mon, 22 Sep 2008 17:01:13 -0600
From: Bjorn Helgaas <bjorn.helgaas@...com>
To: Martin Doucha <next_ghost@...ck.cz>
Cc: Linux Kernel list <linux-kernel@...r.kernel.org>,
matthieu castet <castet.matthieu@...e.fr>,
bugme-daemon@...zilla.kernel.org
Subject: Re: [Bug 11603] Re: ACPI PnP on Intel MU440EX
Your logs are perfect, which makes me happy because it's the first
time I've successfully used the byzantine ACPI debug infrastructure.
> Log with parport set to auto/bidirectional in BIOS for comparison. PNPBIOS does
> detect it in this setting, ACPI doesn't. Same with auto/EPP which I used until
> now.
I think this is a BIOS defect.
When you set the port to "enabled" in the BIOS, Linux finds and uses
the parallel port with no problem.
When you set the port to "auto/bidirectional" or "auto/EPP" in the BIOS,
the _STA methods on all the parallel devices return 0:
bus-0117 [00] bus_get_status : Device [LPT] status [00000000]
bus-0117 [00] bus_get_status : Device [EPP] status [00000000]
bus-0117 [00] bus_get_status : Device [ECP] status [00000000]
A zero _STA means the device is not present at all, so I think Linux
is right to ignore the devices.
I suppose we could try to add a quirk to Linux to work around this,
but I'm not sure whether it's worth it. Your machine is from 1998,
and some distros blacklist ACPI on old machines because it's not
worth the trouble to fix all of them.
Some drivers will blindly probe for hardware if PNP doesn't report
anything. Is parport one of them, i.e., if you load it by hand, does
it work?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists