LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
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-05-2012, 02:42 AM   #1
J1NKL3
Member
 
Registered: Mar 2012
Distribution: Slackware64-current
Posts: 77

Rep: Reputation: Disabled
Custom Kernel won't boot


So I installed 3.2.30 around the time Slackware 14 was released. Past couple of days I've been having problems launching random programs and upon rebooting it freezes at the "Loading Linux-3.2.30........" screen after about 8 dots or so. Any idea what would cause this or what logs I could check to help me figure it out?
 
Old 11-05-2012, 05:30 AM   #2
guanx
Senior Member
 
Registered: Dec 2008
Posts: 1,014

Rep: Reputation: 146Reputation: 146
Quote:
Originally Posted by J1NKL3 View Post
... I've been having problems launching random programs ...
What problems?
 
Old 11-05-2012, 05:32 AM   #3
J1NKL3
Member
 
Registered: Mar 2012
Distribution: Slackware64-current
Posts: 77

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by guanx View Post
What problems?
Well they just fail to launch... xpdf, gwenview, ktorrent... the 3.2.28 kernel launches fine but the newer kernel freezes during loading
 
Old 11-05-2012, 12:55 PM   #4
dwblas
Member
 
Registered: Jun 2011
Posts: 57

Rep: Reputation: Disabled
Possibly, you should have an initrd in order to boot, depending on whether you compiled a huge kernel or not. See /boot/README.initrd and execute mkinitrd with the proper kernel version, etc., and change LILO per the instructions.

Last edited by dwblas; 11-05-2012 at 12:56 PM.
 
Old 11-06-2012, 01:31 AM   #5
J1NKL3
Member
 
Registered: Mar 2012
Distribution: Slackware64-current
Posts: 77

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by dwblas View Post
Possibly, you should have an initrd in order to boot, depending on whether you compiled a huge kernel or not. See /boot/README.initrd and execute mkinitrd with the proper kernel version, etc., and change LILO per the instructions.
It was booting fine without an initrd before this weekend. I booted in and out several times without problems and then had it up for 30+ days until this weekend when I started having problems.
 
Old 11-06-2012, 02:29 PM   #6
BlackRider
Member
 
Registered: Aug 2011
Distribution: Slackware
Posts: 261

Rep: Reputation: 82
It does not really seem to be a kernel problem, or at least a fully kernel related trouble.

If you keep a copy of the Slackware stock kernel, you should return to it and do some testing to ensure the problem is kernel related. Usually, when it is a problem with the kernel you get Panics, warnings and all kind of messages and hints. You can try to surf the logs and use "dmsg" to get a sight about what is going on, given you are able to load the system first.

Common applications failing are more likely problems in the userspace, or may indicate your filesystem has been damaged. You may want to check the system binaries and filesystems are not doomed (you can compare the checksums of the system files with the checksums of the files of the slackware packages).
 
Old 11-08-2012, 11:22 AM   #7
jheengut
Member
 
Registered: Sep 2006
Location: Providence, Moka Mauritius
Distribution: Slackware, OpenSuse, Debian, Fedora, Mageia, Ubuntu, RedHat, BSD, Gentoo, Puppy
Posts: 187
Blog Entries: 2

Rep: Reputation: 3
Quote:
Originally Posted by BlackRider View Post
You can try to surf the logs and use "dmsg" to get a sight about what is going on, given you are able to load the system first.

its
"dmesg" not "dmsg"


If you can drop to a rescue shell before the rootfs '/' is mount rw you can perform a fsck."your rootfs type" on the partition and reboot .

I do not remember how but if you can manually add a ` rescue ` option on the boot command line of lilo or grub then boot .
 
Old 11-08-2012, 06:54 PM   #8
pokute
LQ Newbie
 
Registered: May 2012
Posts: 3

Rep: Reputation: Disabled
If the system was fine for 30 days, and then you started having random exe failures, and then the kernel hung at boot, you have filesystem corruption. Possible causes are hardware failure, bad kernel (improper options chosen at build time, bad options in /etc/fstab, or possibly bad code in fs driver), or being logged in as root and making a mess.

If you get back to the point where you run fine for N days, and then some exe randomly fails, run the exe under strace to see why it's failing. Usually when people report what you are reporting, there are libraries that are missing or corrupted, or deleted symlinks.

If you have an SSD and you are certain that you didn't F up anything, your SSD is probably ready to go back to China for a vacation.
 
Old 11-09-2012, 02:07 AM   #9
J1NKL3
Member
 
Registered: Mar 2012
Distribution: Slackware64-current
Posts: 77

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by pokute View Post
If the system was fine for 30 days, and then you started having random exe failures, and then the kernel hung at boot, you have filesystem corruption. Possible causes are hardware failure, bad kernel (improper options chosen at build time, bad options in /etc/fstab, or possibly bad code in fs driver), or being logged in as root and making a mess.

If you get back to the point where you run fine for N days, and then some exe randomly fails, run the exe under strace to see why it's failing. Usually when people report what you are reporting, there are libraries that are missing or corrupted, or deleted symlinks.

If you have an SSD and you are certain that you didn't F up anything, your SSD is probably ready to go back to China for a vacation.
The stock kernel works fine though on the same drive. Shouldn't both fail if I had filesystem problems?
 
Old 11-09-2012, 11:01 AM   #10
pokute
LQ Newbie
 
Registered: May 2012
Posts: 3

Rep: Reputation: Disabled
Then (assuming everything happened exactly as described) the kernel you BUILT corrupted the FS in a way that the stock kernel was able to recover. If it were my system, I would do destructive badblocks testing on the drive and then reinstall.
 
  


Reply

Tags
kernel, 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
[SOLVED] Custom kernel won't mount eSata Ben Briedis Linux - Kernel 1 03-22-2012 08:17 AM
3d won't initialize with radeon 5470 and debian lenny with custom kernel icon269 Linux - Hardware 7 05-14-2010 02:42 PM
iiyama monitor won't turn on until booted into OS (Dual boot set up, custom built pc) user1010 Linux - Newbie 3 02-13-2010 04:40 PM
kernel panic - custom kernel won't mount file system j-osh Fedora 8 11-19-2008 02:13 AM
Custom Kernel Won't Boot!?!?1 martinman Linux - General 1 07-12-2003 02:10 AM


All times are GMT -5. The time now is 09:13 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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration