Follow a post-install guide and got lost (kernel 2.6.19)
I'm following this post-Slackware install guide, "How to Properly Set Up Slackware Linux" section "Building a New Kernel".
I used Links to download the 2.6.19 kernel from kernel.org and I downloaded the latest kernel patch from the "Beyond Sources". I put both in my home directory. I put that patch into my uncompressed kernel and typed "patch -p1 < patch-2.6.19-beyond2" When that was done, I grabbed a Slackware kernel configuration file from a mirror (2.6.18 was all I found), renamed it and put it into the uncompressed kernel directory. At this point I move the uncompressed kernel from my home directory to /usr/src. I ran "make oldconfig". After, I ran "make menuconfig". I tweaked it according to the guild. I didn't touch what I didn't understand. Then I ran "make" and let the computer do its thing for a few hours. When it was finished I ran: Code:
su -c 'make modules_install ' cp arch/i386/boot/bzImage /boot/vmlinux.custom ' ln -sf /boot/vmlinux.custom /boot/vmlinux ; /sbin/lilo' I edited my lilo.conf and changed "/boot/vmlinuz" to "/boot/vmlinux.custom". When I boot up I am still using the 2.4.33.3 kernel. I know I screwed up somewhere. Where? Any help would be appreciated. :study: |
Did you remember to run
Code:
/sbin/lilo |
seems like you are also needing to:
Code:
# cp System.map /boot/System.map-2.6.19.2 www.digitalhermit.com/ has always worked for me. I might also suggest you leave your old kernel linked in the lilo.conf by creating a new entry for the kernel that you are compiling. that way if you screw something up, you have a rescue kernel to get back into Slack from (speaking from personal experience here :) |
Well I screwed up badly so I decided to just re-install and start fresh. This time I'm going go by that guide bioe007 and see how it goes.
I'm sure I'll run into issues so y'all will see me again. In the meantime, I'll be studying. :) Thanks |
I revised the guide when I read this, but in the the version you followed you would simply have copied your new kernel over your old kernel, rerun lilo, and reboot. That's it. I was going for the simplest method possible. That was the idea, anyway; I noticed that I had some extraneous steps (which didn't hurt) in there for some reason, which I see you followed to the letter. :)
bioe007's advice to create a new entry in lilo.conf for the new kernel is good too. If you decide to do that, put a prompt at the beginning of lilo.conf and you'll get all your kernel choices on a boot-up menu. |
All times are GMT -5. The time now is 09:24 PM. |