Help answer threads with 0 replies.
Go Back > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Slackware This Forum is for the discussion of Slackware Linux.


  Search this Thread
Old 05-27-2011, 02:38 PM   #1
LQ Newbie
Registered: Apr 2010
Location: Sergiev Posad
Distribution: Slackware
Posts: 4

Rep: Reputation: 0
Boot stops suddenly. x86_64 13.37

Boot process ends up as shown at attached jpg.
I use Biostar motherboard P35D2-A7
When I tried to use the kernel on the installation dvd I got working system.
But no succes with huge or generic (with initrd) kernels.

How to dig into this problem?
Attached Thumbnails
Click image for larger version

Name:	IMG_7925.1024.jpg
Views:	43
Size:	130.3 KB
ID:	7139  
Old 05-27-2011, 09:46 PM   #2
Registered: Dec 2004
Location: USA
Distribution: Slackware 12 and higher
Posts: 229

Rep: Reputation: 53
You could try copying the booting kernel from the install media to your machine's /boot directory, modify the machine's lilo.conf to add that kernel, run lilo with options set to write to the hard drive, and reboot.

-then-, -or-

The gzipped configuration (.config) of the booted kernel can usually be found in /proc/config.gz (there's a .config option for that). The config files for each installed kernel can be found in /boot. You could boot the install disk, copy the /proc/config.gz to your machine's hard drive, un-gzip it, then use diff tools to find the differences between a booting and non-booting kernel.

Once the booting config is copied to a permanent location you could also boot a livecd to do your diffs, or something like that.

Also, booting from the install disk, mount the machine's hard drive and check the hard drive's /var/log/syslog, /var/log/messages, and /var/log/dmesg files to look for messages or determine the last thing that was going on.

From that point start poking around in the startup scripts to see if you can figure out exactly what it was doing when it stopped. That early in the startup processes I'd look at the files I mentioned then probably concentrate on the first set of suggestions, above.

Good luck!

Last edited by jamesf; 05-27-2011 at 09:51 PM.
Old 05-27-2011, 11:05 PM   #3
Registered: Dec 2010
Location: California, USA
Distribution: Slackware
Posts: 153

Rep: Reputation: 27
Check the BIOS settings to make sure that the SATA ports on the hard disks are configured in "AHCI mode", not "IDE emulation" mode. Also, you may try disabling the IDE port and flash card reader in case they are being mistaken for a disk.
Old 05-28-2011, 03:32 AM   #4
LQ Newbie
Registered: Apr 2010
Location: Sergiev Posad
Distribution: Slackware
Posts: 4

Original Poster
Rep: Reputation: 0

I think the problem was with lilo which I used with previous Slackware (it was x86). It installed to mbr.
Now I`ve installed new lilo to the partition root with new Slackware (x86_64 13.37) and system boots fine.
Thanks anyway, guys


boot, fail, slackware

Thread Tools Search this Thread
Search this Thread:

Advanced Search

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
DSL suddenly stops Dutch72 Linux - Newbie 11 02-20-2009 02:44 AM
NIC stops working suddenly mhm Linux - Networking 5 06-10-2007 01:35 PM
Wireless service stops suddenly bogzab Slackware 6 05-08-2007 09:30 AM
Java suddenly stops working Wynd Linux - Software 2 04-23-2005 01:20 PM
grub suddenly stops booting XP mab_123 Linux - Software 3 03-26-2005 10:08 AM > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 06:24 AM.

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