On Wed, 15 Aug 2007 04:28:05 GMT Larry Finger <(E-Mail Removed)> wrote:
|
phil-news-(E-Mail Removed) wrote:
|> On Tue, 14 Aug 2007 22:25:17 GMT Larry Finger <(E-Mail Removed)> wrote:
|> |
phil-news-(E-Mail Removed) wrote:
|> |> Anyone know what HP screwed up on the DC7700 series computers that prevents
|> |> Linux from coming up unless ACPI is completely shut off?
|> |
|> | No, but the output of dmesg will give you some instructions on commands to run and where to send the
|> | output. Keeping the ACPI code working with the brain-dead BIOS's in new machines is a full-time
|> | activity. Your output will help them fix Linux to work with that machine.
|>
|> In what system will dmesg tell me where to send its output? On normal
|> machines, dmesg gives me recent kernel printk output, but nothing about
|> where to send stuff. And I assume what they want is the output with
|> ACPI off ... since I can't run dmesg with it on since the kernel does
|> not make it all the way up to start userland.
|
| Your original message implied that your computer did come up with ACPI off. In that case, you would
| get dmesg output. On one system that I have been helping debug a problem, the dmesg output includes
| the following:
|
| ACPI: System BIOS is requesting _OSI(Linux)
| ACPI: Please test with "acpi_osi=!Linux"
| Please send dmidecode to
linux-(E-Mail Removed)
|
| If your ACPI is broken, it should be issuing this, or similar, messages.
I rebuilt a kernel without ACPI because I will be running it via PXE without
an interactive prompt. Would it still work that way? I should have a chance
to test it today, anyway.
--
|---------------------------------------/----------------------------------|
| Phil Howard KA9WGN (ka9wgn.ham.org) / Do not send to the address below |
| first name lower case at ipal.net /
spamtrap-2007-08-15-(E-Mail Removed) |
|------------------------------------/-------------------------------------|
Linear Mode
