I just tried to upgrade to a new kernel for Slackware. I used the 2.6.8.1 kernel. My initial compile went well and everything worked except my internet connection. I ran make gconfig command and I found that I did not have my Network Devices properly configured. I fixed that problem and ran the necessary commands again to recompile.

make bzImage

cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-2.6.8.1

make modules

make modules_install

I updated my System.map and config.map files in the /boot directory and ran /sbin/lilo

I rebooted and got to the lilo login screen but I can't access either my old kernel or kernel 2.6.8.1, the screen just goes blank after I hit enter.

Did I do something wrong when I recompiled (obviously I did!)

Can I access my files that were stored on my linux partition or am I S.O.L?

If it seems like I made a real newbie mistake please let me know. I should have played around with Slackware a little longer before I attempted something like this, but I can't help it, I like to tweak things, that's half the reason I started using Linux (although in this case, I think I bit off more than I can chew).

Anyway, if there is any way I can rescue my system I would be grateful. I had everything perfect (except the kernel). Thanks

you say you ran /sbin/lilo, but did you edit /etc/lilo.conf first? If when you did:
you copied over the kernel that booted before, and then ran lilo, it could have messed up what lilo thinks is where.

You weren't clear whether you got to lilos' kernel selection screen - usually hold down Shift at boot to get there, and select a known good kernel. If you didn't keep any known good kernels, then you will need to boot a rescue disk (slack CD1 works). This will let you get to your files, edit lilo, etc. once you mount your partitions. Follow the rescue disks instructions if you don't know how.

with linux you're never SOL...(hardly ever; there's almost always a way to fix your problem w/o reinstalling)

When I run lilo, I always run it like this:

/sbin/lilo -v

It's verbose so I can confirm that the proper changes have been made. But yeah, I didn't see anything about setting your lilo.conf ... and to get back in, you did make a bootdisk during install, right?
That's saved me more than a few times .... especially when I hose-up lilo.

- JJ

Eek! I did not make a boot disk or rescue disk. I still have my Slackware 10.0 CD1. I will try that. Also, yes, the lilo bootloader menu pops up. I have the selection

Windows
Linux 2.6.8.1 (new kernel)
Linux (old kernel)


Neither of the Linux selections currently work. I will try to use the CD1.

Thanks

I did not edit my /etc/lilo.conf file. When I recompiled I deleted the old vmlinz-2.6.8.1 file (from my first complie) that was in the /boot directory and replaced it with the new vmlinz-2.6.8.1 (from my second compile). My lilo.conf file showed.....

# Linux bootable partition config begins
image = /boot/vmlinuz-2.4.22
root = /dev/hda2
label = Linux 2.6.8.1
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends


I assumed it was okay to leave the lilo.conf as it was since the recompiled vmlinuz-2.6.8.1 file was the same name and in the same directory.

When I recompile a new kernel do I have to delete all files created by the previous compile?

hm, then I don't see where the problem is...one of those should do _something_. Well, see what you can figure out w/ the rescue disk. Maybe try recopying bzImage to a new spot and give lilo.conf a new entry. You should try re-running lilo while you're in there, do it like so:
mount -t reiserfs /dev/hda3 /mnt #mount root reiserfs? partition
<mount any other partitions you need (/boot?)>
<copy/edit?>
/sbin/lilo -v -r /mnt
nope

Do you remember where you installed lilo during install (mbr or superblock of root partition)?

"image = /boot/vmlinuz-2.4.22" should be "image = /boot/vmlinuz-2.6.8.1"
edit it and type " lilo"
that should do it....

egag

egag

Oh, sorry, that is actually a typo on my post. The actual image does read /boot/vmlinuz-2.6.8.1 (my bad).

fphillips

Can I use slackware CD1 as a rescue disk? When I use it to boot up I get a boot command but all I can type is setup of bare.i. I am new at this so I don't know what commands to run.

Can this error be from a compile error and not the result of a mislabled link?

Also, lilo is installed on the mbr. I can still boot windows from lilo but not slackware.

hi,

you can boot from cd1. just type : "bare.i mount root=......(etc)" at the boot prompt as you are instructed on the screen.
then you can run " /sbin/lilo -v" and look at the output for errors.

and when compiling a kernel & modules , i always issue :" make clean" and "make mrproper" to get rid of the old stuff. then copy the config-file from /boot to /usr/scr/linux. ( all done in the /usr/src/linux -dir )
then run xconfig or so...

good luck.

egag