SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello, I am new to the linux scene so please be gentle
Has anyone heard of a slackware install turn the pc off? I have downloaded the iso from the net and all works fine until it installs it. I have followed the instructions in the slackbook so i am sure I havent missed anything out but because I am new to linux im wondering whether i am missing anything blatantly obvious?
Just a shot in the dark, as keefaz has pointed out that you've
omitted all the nice, juicy details which will help us help you.
Your HSF is so full of dirt that it can't properly cool your CPU.
So when you're installing Slackware packages, the extra
work on the CPU is causing it to overheat, and your BIOS
is set to shutdown the PC to save your mobo, etc.
Hello, I am new to the linux scene so please be gentle
Has anyone heard of a slackware install turn the pc off? I have downloaded the iso from the net and all works fine until it installs it. I have followed the instructions in the slackbook so i am sure I havent missed anything out but because I am new to linux im wondering whether i am missing anything blatantly obvious?
Bruce has a point about the 'HSF' and temperature. I would add; did you check the md5sum for the downloaded iso and check md5sum for the burnt cd image with the original iso md5sum? You can search for this as it has been covered a lot on LQ.
I have heard of the fans not working properly during the install process (though they should work after the system is installed -- it may or may not require manual loading of modules), which can cause overheating as Bruce Hill suggests. Although I myself haven't experienced this (the fans on my computer are controlled by the BIOS -- though I can override them in Linux if I want), I remember a thread quite a while ago dealing with this. You could try to get the fans working during the install procedure (which will probably not work), take the case off of your PC during the install process (unless it is a laptop, obviously), or...stand in a fridge?
Thanks for your help, I had never considered this to be an option as it has never happend before. After taking alook round the forum, they suggest you use the command acpi=off in the kernal, can anyone tell me where exactly in the setup I type this? do i type it when i type setup?
Thanks for your help, I had never considered this to be an option as it has never happend before. After taking alook round the forum, they suggest you use the command acpi=off in the kernal, can anyone tell me where exactly in the setup I type this? do i type it when i type setup?
You could include it in your '/etc/lilo.conf' file in the global section or in the stanza you wish to use it.
Code:
#portion of '/etc/lilo.conf' Global section;
#message = /boot/boot_message.txt
# Append any additional kernel parameters:
append="noapic acpi=off vt.default_utf8=0"
prompt
timeout = 300
Code:
sample '/etc/lilo.conf' partition stanzas;
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
addappend = "acpi=off"
root = /dev/sda5
label = Slackware12.1
read-only # Partitions should be mounted read-only for checking
# Linux bootable partition config ends
# Windows bootable partition config begins
other = /dev/sda1
label = WinXP
# map-drive = 0x80
# to = 0x81
# map-drive = 0x81
# to = 0x80
table = /dev/sda
# Windows bootable partition config ends
Code:
excerpt 'man lilo.conf';
KERNEL OPTIONS (image=)
If the booted image is a Linux kernel, then one may pass command line
parameters to this kernel.
addappend=<string>
(22.6) The kernel parameters from the specified string, are con-
catenated to the parameter(s) from an append= specification (see
below). The string must be enclosed within double quotes. Usu-
ally, the previous append= will specify parameters common to all
kernels by appearing in the top, or global, section of the con-
figuration file and addappend= will be used to add local parame-
ter(s) to an individual image. Addappend= may be used only once
per "image=" section.
append=<string>
Appends the options specified to the parameter line passed to
the kernel. This is typically used to specify hardware parame-
ters that can't be entirely auto-detected or for which probing
may be dangerous. Multiple kernel parameters are separated by a
blank space, and the string must be enclosed in double quotes.
A local append= appearing withing an image= section overrides
any global append= appearing in the top section of the configu-
ration file. Append= may be used only once per "image=" sec-
tion. To concatenate parameter strings, use "addappend=". Exam-
ple:
append="mem=96M hd=576,64,32 console=ttyS1,9600"
You could have your 'append = ' in the Global section then add the 'addapend =" in the stanza. If you use the 'append =' in the stanza then that will override the global 'append ='. This can be used to your advantage.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.