Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
|
01-26-2014, 01:48 PM
|
#1
|
LQ Newbie
Registered: Jan 2014
Location: Canada
Distribution: Slackware
Posts: 15
Rep:
|
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 01:56 PM.
Reason: Additional information
|
|
|
01-26-2014, 03:13 PM
|
#2
|
LQ Addict
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,220
Rep:
|
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 03:51 PM.
Reason: remove possibly damaged pacakes before reinstalling them
|
|
2 members found this post helpful.
|
01-27-2014, 02:44 PM
|
#3
|
LQ Newbie
Registered: Jan 2014
Location: Canada
Distribution: Slackware
Posts: 15
Original Poster
Rep:
|
Thanks, Didier, that fixed it. Huge kernel works fine again.
|
|
|
01-27-2014, 03:03 PM
|
#4
|
LQ Addict
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,220
Rep:
|
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
|
|
|
All times are GMT -5. The time now is 04:09 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|