From: "Sven Köhler" <skoehler@upb.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [ACPI] p2b-ds blacklisted?
Date: Thu, 02 Oct 2003 03:02:15 +0200 [thread overview]
Message-ID: <blftgg$9ui$1@sea.gmane.org> (raw)
In-Reply-To: <blen4v$a42$1@sea.gmane.org>
> I would like to try what happens if i remove the board from the
> blacklist.
So that was what i just did. I removed the board from the blacklist,
recompiled the kernel and booted.
The kernel started and there were some issues with the interrupt
routing. I don't remember the exact messages but i could post a dmesg if
you like.
With "pci=noapci" the computer hang upon loading the kernel module for
the SCSI controller. I remember that to be an issue too when i had
windows2k installed on that box but i could "fix" that by changing the
IRC setting in the BIOS. Changing those settings didn't help Linux to boot.
At first sight ACPI (without pci=noacpi) seemed to work but pressing the
power button didn't generate any events although the power button was
detected properly during boot.
After all i think i know why P2B-S and -DS are blacklisted. The board
with on-board SCSI controller are messed up somehow.
I haven't tried to install BIOS 1014beta3 yet. BIOS 1014beta2 is
currently installed but i guess the update won't solve anything.
With acpi=ht it works for now, but doesn't acpi=ht imply pci=noacpi?
next prev parent reply other threads:[~2003-10-02 1:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-01 14:07 [ACPI] p2b-ds blacklisted? Sven Köhler
2003-10-01 14:16 ` Andrew de Quincey
2003-10-01 14:53 ` Sven Köhler
2003-10-01 15:05 ` Andrew de Quincey
2003-10-01 17:11 ` Jeff Garzik
2003-10-01 17:16 ` Sven Köhler
2003-10-01 18:23 ` Mike Dresser
2003-10-02 1:02 ` Sven Köhler [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-03 6:07 Brown, Len
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='blftgg$9ui$1@sea.gmane.org' \
--to=skoehler@upb.de \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox