13.0 to 13.1 via Slackpkg - is it possible?

BobNutfield · 06-28-2010, 07:29 AM

Well, got everything I need, followed all the instructions, and it won't boot. I don't know why I thought it would, no upgrade I have ever tried worked without headaches.

I get a kernel panic, not syncing, which I know is because it can't find the boot partition. When running lilo, I get a warning,
LBA32 addressing assumed.

My lilo.conf:

Code:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/sda
#compact        # faster, but won't work on all systems.
# Standard menu.
message = /boot/boot_message.txt

# Append any additional kernel parameters:
append=" vt.default_utf8=0"
#prompt
timeout = 5
# Normal VGA console
vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# ramdisk = 0     # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sda1
  label = Linux
  read-only  # Partitions should be mounted read-only for checking
# Linux bootable partition config ends

My /etc/fstab:

Code:

/dev/sda6        swap             swap        defaults         0   0
/dev/sda1        /                ext4        defaults         1   1
/dev/sda5        /home            ext4        defaults         1   2
#/dev/cdrom      /mnt/cdrom       auto        noauto,owner,ro  0   0
/dev/fd0         /mnt/floppy      auto        noauto,owner     0   0
devpts           /dev/pts         devpts      gid=5,mode=620   0   0
proc             /proc            proc        defaults         0   0
tmpfs            /dev/shm         tmpfs       defaults         0   0

I don't see what I did wrong. If anyone can take a look, I would appreciate it.

Thanks
Bob

selfprogrammed · 07-19-2010, 05:28 PM

I am seeing something on my 2.6 install that may be relevant.
When running lilo, it complains that the 2.6 kernel does not have the device-mapping, it cannot get the dev name to block number mapping from the kernel.
If I go back to an old kernel like 2.4, then lilo runs fine.
You might have a messed up device-mapping, in which case boot an older kernel and run lilo from there.
This is just a wild guess.

How sure are you that the kernel you see booting, is the one that you think that you just installed ??

It would not hurt to post the exact panic message, even if you have to copy it by hand. I have had these error messages be misleading, and found some really round-about causes.

Do you have an older kernel to boot from that is working ??

shadowsnipes · 07-19-2010, 10:22 PM

Also, what kernel does vmlinuz point to? I'm assuming you meant it to point to the huge kernel, or else pointing it to the generic kernel without an initrd is your problem.