LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   ACPI confusion (https://www.linuxquestions.org/questions/slackware-14/acpi-confusion-379778/)

shepper 11-03-2005 09:27 PM

ACPI confusion
 
I just setup a box with Slackware 10.2 and the 2.6.13 kernel have everything working except acpi shutdown. It goes through the sequence but seems to reboot instead. I have tried shutdown -h now and it still restarts. I have a Gigabyte GA-7VTX flashed to the latest stable bios. The bios in beta does not have any changes that address apci. I used the same kernel .config as I had on a test box. (amd and via north and south bridges) and it shutdown fine on the test box.

I saw something about some trouble with acpi in the later kernels and tried the 2.6.14 kernel and it still restrarts. The only log message that seems out of sorts is this one
Quote:

Kernel command line: BOOT_IMAGE=Linux ro root=305
Local APIC disabled by BIOS -- you can enable it with "lapic"
mapped APIC to ffffd000 (01402000)
I tried searching here and at google and am still at loss as to how to fix this.
Is lapic a command i pass to the kernel in lilo? If so could someone post their lilo.conf
showing how to make this entry.

Does this mean I have two competing apci's. One in the bios and one in the kernel (?the local APIC). In the 2.4 kernel series I would have no problem with apic enabled and "button" as a module.

Any helpful links, suggestions appreciated

uselpa 11-04-2005 01:23 AM

APIC has nothing to do with ACPI.

I had the same issue on a very old board, but I never solved it. All I found on the net were references to broken BIOSes, but that's probably not your case.

adz 11-04-2005 01:39 AM

APIC and ACPI are two very different things. I would make sure that ACPI is definetly turned on. Make sure that there is a line that reads:
Code:

append "acpi=on"
In the appropriate stanza of your lilo.conf. Then run the lilo command.

Similarly. if you wish to anable local APIC then make sure there is a line that reads:
Code:

append "lapic=on"
In the appropriate stanza of our lilo.conf and run the lilo command again.

One other thing. I don't use slackware but there's a good chance that the newer versions of it use GRUB instead of LILO. So check that out first.

adz 11-04-2005 01:42 AM

Damn it, you beat me uselpa.... And even posted the same links.

uselpa 11-04-2005 01:45 AM

adz, Slackware still uses lilo as of version 10.2.

adz 11-04-2005 01:51 AM

Okie-dokie, then. LILO it is.

shepper 11-04-2005 08:30 AM

Thanks for the replies. I think I may have found the problem. The hardware clock won't stay set after powerdown and the bios version reverts back which suggests that the cmos battery has gone to battery heaven. I'm gonna replace the battery and see if that fixes things

shepper 11-10-2005 10:50 AM

Still having trouble with shutdown after battery replacement and sucessful flashing of the bios. I reinstalled the system with the bareacpi.i kernel and still have the system go through the shutdown sequence only to not fully shutdown and reboot. The only other thing I changed was to upgrade the video card from a radeon7500 to a radeon9250 with 256mb of video ram. Google searches were not helpful and my dmesg log does not show any errors.

I'm going to try putting the older card back in and if that changes things I will report back. I would like to get the benefits of the new card eventually.


All times are GMT -5. The time now is 01:51 PM.