LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 11-03-2005, 09:27 PM   #1
shepper
Member
 
Registered: Mar 2003
Location: Dry, Dusty and Conservative
Distribution: OpenBSD, Debian Wheezy/Jessie
Posts: 449

Rep: Reputation: 33
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
 
Old 11-04-2005, 01:23 AM   #2
uselpa
Senior Member
 
Registered: Oct 2004
Location: Luxemburg
Distribution: Slackware, OS X
Posts: 1,507

Rep: Reputation: 47
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.
 
Old 11-04-2005, 01:39 AM   #3
adz
Senior Member
 
Registered: Jun 2003
Location: Sydney
Distribution: Debian, FreeBSD
Posts: 1,713

Rep: Reputation: 53
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.

Last edited by adz; 11-04-2005 at 01:41 AM.
 
Old 11-04-2005, 01:42 AM   #4
adz
Senior Member
 
Registered: Jun 2003
Location: Sydney
Distribution: Debian, FreeBSD
Posts: 1,713

Rep: Reputation: 53
Damn it, you beat me uselpa.... And even posted the same links.
 
Old 11-04-2005, 01:45 AM   #5
uselpa
Senior Member
 
Registered: Oct 2004
Location: Luxemburg
Distribution: Slackware, OS X
Posts: 1,507

Rep: Reputation: 47
adz, Slackware still uses lilo as of version 10.2.
 
Old 11-04-2005, 01:51 AM   #6
adz
Senior Member
 
Registered: Jun 2003
Location: Sydney
Distribution: Debian, FreeBSD
Posts: 1,713

Rep: Reputation: 53
Okie-dokie, then. LILO it is.
 
Old 11-04-2005, 08:30 AM   #7
shepper
Member
 
Registered: Mar 2003
Location: Dry, Dusty and Conservative
Distribution: OpenBSD, Debian Wheezy/Jessie
Posts: 449

Original Poster
Rep: Reputation: 33
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
 
Old 11-10-2005, 10:50 AM   #8
shepper
Member
 
Registered: Mar 2003
Location: Dry, Dusty and Conservative
Distribution: OpenBSD, Debian Wheezy/Jessie
Posts: 449

Original Poster
Rep: Reputation: 33
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.

Last edited by shepper; 11-10-2005 at 10:52 AM.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
a little confusion..... b0nd Linux - Newbie 1 02-17-2005 06:45 AM
acpi (no /proc/acpi)??? JimDog Linux - Newbie 2 01-25-2004 12:14 AM
kernel 2.4.20 & acpi-20021212-2.4.20.diff => no /proc/acpi Tinkster Linux - Software 5 03-24-2003 01:56 PM
WM Confusion phoeniXflame Slackware 3 02-16-2003 05:19 AM
Some confusion about RH 7.3 psyklops Linux - Distributions 2 05-08-2002 03:08 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 03:56 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration