SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Well the short of it is that I messed up my kernel compile, and I REALLY need to get it back (for obvious reasons) back to the way I had it. Network and sound don't work on it. And I really don't have the knowledge or the time to find what i did wrong to the old kernel. My vmlinuz.old somehow got transformed into a copy of my new kernel. I don't want to recompile a new kernel if I don't have to.
Is there anyway I can use the kernel install from the CD without installing the whole system over again? I selected bare.i and it recognized all of my hardware beautifully. I looked around the slack CD but I don't know what I can use. Any help on how to recover it from the Slack CD or some other source (NOT RECOMPILING) is greatly appreciated.
Just boot the Slackware CD, set up your source and target partitions (but *don't* format the latter ), skip the package selection and go straight to the configuration section., You should be able to skip everything except the kernel installation bit. One of the options you're given is to use a kernel from the installation CDROM. Select that and from the list provided, find and select bare.i. Skip the rest of the sections until you're back at the main Slackware installation menu then exit and reboot. With any luck bare.i should be reinstalled and your system should boot properly.
You had the right idea. Slackware install won't let me skip right down to the configuration, so what I did was to do the install with only the base system changing. Slackware even offered to keep my old configuration files, how nice of it. So now everyone knows: If you mess up your kernel compile just install but only select the kernel packages from the list.
Actually, the procedure as I outlined it should have worked, it's exactly the same procedure I used to install the scsi.s kernel on a Slackware VM that I accidentally installed bare.i on rendering it unbootable....
Originally posted by Zb7 Slackware even offered to keep my old configuration files, how nice of it. So now everyone knows: If you mess up your kernel compile just install but only select the kernel packages from the list.
Slackware is great...so far, I've yet to find a distro that even came close to my liking. JAMD is neat...but Slack is tha shiznit.
I always recompile; it doesn't take long if you know what areas you are having problems in. No sound? make xconfig and go to the sound section...check settings, make changes. save, exit...make bzImage and so on.
But, the Slack setup CD is a great recovery tool as well. Glad it helped save the day for you.
It's hard to recompile when you can't even boot after a botched compile
Seriously though, another good troubleshooting aid is a basic Gentoo LiveCD. I've used mine to rescue not only my own Gentoo system but also a Debian box suffering a severe case of "crappyinstalleritis".
I like to add a Linux_safe LILO boot option before I start playing around with kernel compiles. Simply copy a good vmlinuz to vmlinuz.safe, then make the necessary entry in /etc/lilo.conf (dont for get to run lilo!) That way if a newly-compiled kernel panics, you can choose Linux_safe to boot and fix the problem.
Originally posted by eric.r.turner I like to add a Linux_safe LILO boot option before I start playing around with kernel compiles. Simply copy a good vmlinuz to vmlinuz.safe, then make the necessary entry in /etc/lilo.conf (dont for get to run lilo!) That way if a newly-compiled kernel panics, you can choose Linux_safe to boot and fix the problem.
Me too...well, mine is vmlinuz.stable I think, but same thing. Always good to have backup.
It is always good to have a backup or safe option in lilo when you are compiling kernels. You can also use the Slack CD for a more straightforward approach to saving yourself. You can boot from it, login, but instead of running setup simply mount your file systems and copy the bare.i kernel (or whatever kernel you need) over to your installation, changing the name to vmlinuz or whatever name you have lilo pointing to.