LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
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 01-26-2014, 12:48 PM   #1
ibrunton
LQ Newbie
 
Registered: Jan 2014
Location: Canada
Distribution: Gentoo, Slackware
Posts: 9

Rep: Reputation: Disabled
Custom kernel doesn't work, but now even generic and huge kernels panic.


I tried compiling a custom kernel from the 3.10.17 source installed with Slackware 14.1. I've compiled a couple of kernels successfully in Gentoo, so I figured I'd give it a try in Slackware. I followed the instructions in AlienBob's kernel wiki article.

The custom kernel didn't work (it would boot, but once I logged in and executed xinit, I had no mouse or keyboard input). I tried to reboot with the generic kernel, and got a kernel panic. I tried to reboot with the huge kernel and got a kernel panic. I don't know what I did that would affect those kernels (their config and initrd and System.map files are still in /boot).

Is there a way to get things working again? I can access the file system from Gentoo installed on the same machine, but I can't boot Slackware at all.

Edit: I don't know if this is relevant or not, but it appears that when I attempted to compile the custom kernel again (to fix the keyboard/mouse issue), somehow the CONFIG_LOCALVERSION got unset (I don't recall running make mrproper, but...). So the recompiled modules would have been installed into /lib/modules/3.10.17/ instead of /lib/modules/1.10.17-idb/ and the generic and huge kernels are looking at those instead of the originals (which presumably have been overwritten and are gone).

Last edited by ibrunton; 01-26-2014 at 12:56 PM. Reason: Additional information
 
Old 01-26-2014, 02:13 PM   #2
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-{14.1,current} on a Lenovo Thinkpad T61 6457-4XG
Posts: 4,260

Rep: Reputation: 1051Reputation: 1051Reputation: 1051Reputation: 1051Reputation: 1051Reputation: 1051Reputation: 1051Reputation: 1051
Boot your Slackware installation media, login but don't run setup.

Then, do this:
Code:
# Assuming you inserted a Slackware DVD, mount it
mkdir /DVD # mount point for the Slackware DVD 
mount /dev/sr0 /DVD
fdisk -l  # to check which partition is / 
mount /dev/sda1 /mnt # Assuming / is on /dev/sda1
# remove possibly damaged packages
ROOT=/mnt removepkg /mnt/var/log/packages/kernel*smp*txz
# reinstall needed packages
# if slackare64, replace slackware with slackare64 below
installpkg --root /mnt /slack/slackware/a/kernel*smp*txz
umount /DVD
# Now, remove the DVD and reboot
Please report the outcome.

If you still have a problem, you'll need to chroot into your system (still booting from the Slackware DVD), possibly edit /etc/lilo.conf then re run lilo. If you need guidance for that, just ask.

Last edited by Didier Spaier; 01-26-2014 at 02:51 PM. Reason: remove possibly damaged pacakes before reinstalling them
 
2 members found this post helpful.
Old 01-27-2014, 01:44 PM   #3
ibrunton
LQ Newbie
 
Registered: Jan 2014
Location: Canada
Distribution: Gentoo, Slackware
Posts: 9

Original Poster
Rep: Reputation: Disabled
Thanks, Didier, that fixed it. Huge kernel works fine again.
 
Old 01-27-2014, 02:03 PM   #4
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-{14.1,current} on a Lenovo Thinkpad T61 6457-4XG
Posts: 4,260

Rep: Reputation: 1051Reputation: 1051Reputation: 1051Reputation: 1051Reputation: 1051Reputation: 1051Reputation: 1051Reputation: 1051
At second thought, I think that the removepkg command was not necessary: it removes only files (and directories, if empty) that were installed from the genuine package, unless also found in other packages, but not "alien" files, so probably running installpkg was sufficient. But at least that didn't hurt and you can boot again, so all is well that ends well. Happy slacking
 
  


Reply


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
devisse assignment different in huge and generic kernels metageek Slackware 5 01-11-2013 02:44 PM
[SOLVED] Generic and custom kernel work in 14.0, but I have a question about initrd. tfrei Slackware 3 10-02-2012 09:28 AM
What Do I Need To Know About Huge vs. Generic Kernels During Installation? joncr Slackware 16 07-18-2012 06:29 AM
13.0 64 bit just Huge & Generic, no "smp" kernels installed acummings Slackware 2 10-01-2009 09:59 AM
generic or huge kernels? metrofox Slackware 25 04-15-2009 04:04 AM


All times are GMT -5. The time now is 09:30 PM.

Main Menu
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