From: Len Brown <len.brown@intel.com>
To: Dieter Jurzitza <dieter.jurzitza@t-online.de>
Cc: Linux ACPI <linux-acpi@vger.kernel.org>
Subject: Re: Blacklisted system / blacklisting bad
Date: Wed, 20 Sep 2006 00:55:42 -0400 [thread overview]
Message-ID: <200609200055.42958.len.brown@intel.com> (raw)
In-Reply-To: <200609031134.33024.dieter.jurzitza@t-online.de>
On Sunday 03 September 2006 05:34, Dieter Jurzitza wrote:
> I recently got a HP VISUALIZE NT workstation, using 2x 1GHz PIII processors
>. After installation ACPI was always disabled, the on board USB interface did not work
>(kernel 2.6.11.4 (SuSE linux 9.3)
>
> I tested using acpi=force on the commandline and that solved two problems:
>
> 1.) shutdown -h now switches the machine off (should be expected :-):-) )
> 2.) much more important: the onboard USB interface works now.
>
> After patching dmi_scan.c and removing the blacklist-entry I get the following
> message at boot time:
....
ACPI is necessary to get the interrupts right for USB to work on this box.
pci=noacpi and acpi=ht will cause ACPI to be disabled for interrupt routing
and thus USB will fail with those.
As Luming pointed out, Shaohua's _CRS workaround for the _BBN BIOS bug
is what your system needed, and that is why "acpi=force" is working.
It seems that perhaps the DMI blacklist entry pre-dated that workaround.
Please verify that 2.6.18-rc7 works with "acpi=force" on this box,
and if it does, please send me a patch to remove the entry in that kernel.
thanks,
-Len
next prev parent reply other threads:[~2006-09-20 4:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-03 9:34 Blacklisted system / blacklisting bad Dieter Jurzitza
2006-09-05 6:43 ` Yu Luming
2006-09-20 4:55 ` Len Brown [this message]
2006-09-24 18:35 ` Dieter Jurzitza
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200609200055.42958.len.brown@intel.com \
--to=len.brown@intel.com \
--cc=dieter.jurzitza@t-online.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.