Ok i have changed fstab and lilo back to default fstab is as before and lilo is


running lilo in chroot now gives

just rebooting now

I guess I was not very clear in my previous post...

If your "boot" entry in lilo.conf was "/dev/hde1" before the upgrade to -current, it should be "/dev/sda1" now.

The entry to boot Slackware should be:
When you ran lilo, was /boot mounted, or did you copy the kernel to /boot on the / partition?

Something like this happened to me as well
(not finding the kernel modules).

I went from kernel 2.6.32.3 -> 2.6.32.5
and was already using sd? for the drives.

After I did the update, made the initrd as usual,
re-ran lilo (no errors from lilo or mkinitrd), and
rebooted...the problem occurred.

I ended up booting with the first disc from slackware 13...
mounted the drives (using hd?), adjusted lilo to use hd? (for boot and root), and set the system to boot using the huge kernel.

I then re-ran lilo and booted with the huge kernel and remade the initrd,readjusted fstab, and re-ran lilo...

And I was back in business.
I have no idea what went wrong because I did not see any
obvious errors during the update process.

Anyway, HTH
Cheers

Now things seem to be worse.

If i boot with new or old config files i just get 9A 9A 9A repeted for 10 lines.

I think it is from when i set the partition as bootable to try and fix the error with lilo telling me the partition was not active. Removing this flag doesn't help either.

Is there any special reason why you used /dev/hde1 (now /dev/sda1) for lilo instead of /dev/hde (now /dev/sda) ?

I always use the mbr for lilo and never a specific partition.

From the info you gave us, it doesn't seem that this box is a multi-boot system, with several installations of Linux or combinations with Windows, correct?

<edit>The 9a error means that there is something wrong with the "mapping" of the disk. This means it cannot find something. Yeah, not a great help, I know... Does the word "LILO" form completely? It actually forms the word letter by letter and each one means that is passed to the next stage. (see here)</edit>

The only reason is because that is the way i have always done it.

Thats correct just slackware on that pc.

Well, I would suggest trying just /dev/sda then... Tell us what the output of running lilo is.

Thank you very much that has fixed it now i am back with a working Slackware just got to see if i can get my wifi going again.

Glad I could be of any help!

I have a similar problem - I updated in current to kernel 2.6.32.2 and cannot boot (I am using by system with Lxubuntu at present).

I use grub to load the kernel directly however I am reading that I need a initrd file with this new kernel now? It is not present in my boot directory - it created by lilo?

Just wondering if you could explain how I make the initrd ?

Have tried the readme file example: mkinitrd -c -k 2.6.32.2 -m ext4 and various others but no go.

http://www.slackware.com/~alien/tool...d_generator.sh

Download this script and run it. It will output the mkinitrd command you need. Run the outputted command which will create your initrd in /boot/initrd.gz.

Then edit /etc/lilo.conf with the line Rerunning lilo may or may not be neccessary.

I might have gotten ahead of myself, those insttructions are for LILO. Do you run LILO or do you boot directly from Grub?

For future reference (in general) ...I've always found when kernel updates are in the changelog...wait a day or three for your selected mirror to sync

vigi, the link damgar posted should help you get the correct command you need to run in order to create your initrd.

then it should be just a matter of updating grub's menu.lst file.

you can google to see some examples or maybe if you posted your menu.lst after you have created your initrd, someone here more knowledgeable in grub could assist you getting it configured?

Where exactly is the HEART of TX?