LinuxQuestions.org - [SOLVED] Slackware Current (13.37) iso fails to boot on Asus P8Z68-V LE with 3506/3702 BIOS

- Slackware - Installation (https://www.linuxquestions.org/questions/slackware-installation-40/)

- - Slackware Current (13.37) iso fails to boot on Asus P8Z68-V LE with 3506/3702 BIOS (https://www.linuxquestions.org/questions/slackware-installation-40/slackware-current-13-37-iso-fails-to-boot-on-asus-p8z68-v-le-with-3506-3702-bios-940376/)

Slackware Current (13.37) iso fails to boot on Asus P8Z68-V LE with 3506/3702 BIOS

In an attempt to solve a problem I'm having with 13.37, I'm trying Slack Current for the first time. For the last two days I was unable to get Slack Current to boot, either from an install iso or from an installation to hard disk.

Slack 13.37 unaltered booted fine with the 3702 BIOS (March 2012) but not with the older 3506 BIOS on this motherboard (Asus P8Z68-V LE, i5-2400 CPU). The installation CD/DVD booted fine on several older computers.

Slack loaded the kernel and initrd.img then failed when executing. It always failed in the same spot. The last few lines on the display, prefaced with the usual [..] [<..>], are:

Code:

acpi_bus_register_driver

acpi_pci_root_init

do_one_initcall

? radix_tree_lookup

? irq_to_desc

? init_irq_proc

kernel_init

? start_kernel

kernel_thread_helper

SOLVED: Yeah! Add the boot parameter "acpi=off" (no quotes) and it boots fine both from the iso and from the installation on a hard disk.

The boot parameter "noacpi" does NOT appear to be currently valid and had no effect. I saw this parameter mentioned frequently in various places online by responders to requests for help.

I spent the last couple of days on this and had used this invalid parameter many times early in my trials. Tonight, when finally giving up and writing this forum request for help and wanting to get the details exact in my summary, I found my mistake when going back and researching this parameter.

In the future when I have a problem I'll just create a request for help forum message with all the details. Then I'll be able to solve the problem without having to actually post the messsage. :)

In Slackware Current don't use "noacpi" use "acpi=off".

I found the boot parameter information at the dated, but obviously helpful web page: http://www.cyberciti.biz/howto/quest...parameters.php

I hope the forum rules don't forbid my posting of a solved problem that may help others. I'm new here.

Tracy Tiger

Hi,

There's no rule against posting a problem and including the solution in my opinion. If you encounter a problem you want to ask help for then you post it. If after some time you find a solution and post that, then that's only good and helpful so by this I thank you. I'm sure your problem/solution will be helpful to someone. Marking it as solved also is good practice since it indicates your thread/post contains a solution. That in combination with a descriptive title can do magic on LQ.

Have fun with Linux.

Kind regards,

Eric

The correct option (which I always see mentioned) is not "noacpi" but "noapic" !
In full, you would pass "acpi=off noapic" to the kernel on boot in order to resolve hardware issues which prevent a successfull boot.

Eric

Hi,

For future reference then look at: kernel-parameters.txt

Quote:

Originally Posted by Alien Bob (Post 4655827)

Online I found incorrect recommendations to use both "noacpi" and "noapic" for the two different features. I just picked wrongly worded recommendations to follow and should have investigated more thoroughly. I had the solution but didn't properly implement it. It's good that you bring this up to separate the two features and clarify the syntax. It's easy to get the two mixed up or to not realize they are two different things with two different syntax.

Quote:

Originally Posted by onebuck (Post 4656218)

For future reference then look at: kernel-parameters.txt

I didn't know about the "doc" resource at kernel.org. I only ever used the site to pull down kernels/patches. It appears there is a LOT of information in kernel.org/doc and kernel.org/doc/Documention. I have so much to learn.

Thank you both for your responses.