Jump to content

ACPI in MDK9.2


ac_dispatcher
 Share

Recommended Posts

OK I could get acpi working in 9.1 real easy. MDK9.2 its a no go.

 

on boot:

 

Looking for DSDT in initrid ... not found!

ACPI breakpoint: Executed AML Breakpoint opcode

 

What does that mean?

 

I have tried other kernels with no luck. Any idea?

 

In my lilo.conf it states acpi=ht (I think it was ht not home right now) what does ht mean? when I change it to acpi=on I get the above error.

 

I do believe that when I first did a mdk upgrade (9.1 to 9.2) acpi worked if I used the 9.1 kernel. But do to many upgrade issues I had to do a clena install.

Edited by ac_dispatcher
Link to comment
Share on other sites

Found it

 

Error scenario: When enabling ACPI in the kernel (by removing acpi=ht from the kernel boot options), the system freezes very early

Why: There seems to be a bad interaction with Local APIC, which is enabled by default in the kernel. This can be seen by adding vga=0 to try to see the last kernel message before it locks solid (a message like "Looking for DSDT in initrd... not found"). This seems to happen with certain HP laptops. Other reports also indicate that if you remove AC power from a laptop (ie. Dell latitude C640; possibly others) it will freeze requiring a power off. (re: Bugzilla #5821)

Solution: Add "nolapic" to the kernel boot options to resolve both issues.

 

http://www.mandrakelinux.com/en/errata.php3#nolapic

Link to comment
Share on other sites

If your remove acpi=ht, acpi will not work. Or, have they built acpi INTO the kernel instead of as modules? That would be insanely stupid but wouldn't suprise me a bit. ACPI use to only work with acpi=on as a kernel parameter which is how it should be. So, the errata makes no sense to me. For ML9.1 I had to acpi=off noapic . If I tried to enable either, nothing worked rt. ML9.2 onlt acpi=ht will enable anything to work. Any other parameter screws everything up. They seem to have taken a step backward.

 

So did it work for you? Is acpi being used? What chipset?

Link to comment
Share on other sites

OK I got it to work

 

lilo.conf:

 

boot=/dev/hda

map=/boot/map

vga=normal

lba32

default="WindowsXP"

keytable=/boot/us.klt

prompt

nowarn

timeout=100

message=/boot/xray-blue.boot

#message=/boot/penguins.boot

#message=/boot/message

#menu-scheme=wb:bw:wb:bw

image=/boot/vmlinuz-2.4.22-10mdk

label="Mandrake9.2"

root=/dev/hda7

initrd=/boot/initrd-2.4.22-10mdk.img

append="devfs=mount hdc=ide-scsi acpi=on nolapic resume=/dev/hda9 splash=silent"

vga=788

read-only

other=/dev/hda2

label="WindowsXP"

table=/dev/hda

other=/dev/fd0

label="floppy"

unsafe

image=/boot/vmlinuz-2.4.22-10mdk

label="default"

root=/dev/hda7

initrd=/boot/initrd-2.4.22-10mdk.img

append="devfs=mount hdc=ide-scsi acpi=ht resume=/dev/hda9 splash=silent"

vga=normal

read-only

###

 

notice the acpi=on. If it was acpi=ht it would not work(with my Laptop)

 

I have read somewhere that acpi=force sometimes works also

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...