how to upgrade slackware 13.0 to 13.1

pupok · 11-20-2010, 05:26 AM

Quote:

Originally Posted by wakkana12

that's the problem.. earlier im having problem on 2.6.36 custom kernel because it doesn't appear on my lilo even though i followed the tutorial on how to upgrade.. when running /sbin/lilo command it returned that linux2 was added which is my 2.6.36 custom kernel.. but when i restart my computer it doesn't show the linux2 on the lilo. i already posted my lilo.conf and the result of

Code:

ls -la /boot

Could you post output of

Code:

fdisk -l /dev/hda

Anyway, setting /dev/hda2 as bootable is still not enough if you have old lilo installed in /dev/hda MBR.

njb · 11-20-2010, 08:53 AM

Good idea to try upgrade first.
It's a good exercice to improve the slackware knowledge.

But if you get annoyed, and you're newbi, or use a single desktop PC, then make a new slackware 13.1 installation and benefit from a clean upgraded machine.

NjB

wakkana12 · 11-20-2010, 03:06 PM

Quote:

Originally Posted by pupok

Could you post output of

Code:

fdisk -l /dev/hda

Anyway, setting /dev/hda2 as bootable is still not enough if you have old lilo installed in /dev/hda MBR.

here's the output of fdisk -l

Code:

Disk /dev/hda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x879a879a

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1               1         608     4883728+  82  Linux swap
/dev/hda2   *         609        1824     9767520   83  Linux
/dev/hda3            1825        9729    63496912+  83  Linux

i think any changes in my lilo.conf doesn't affect it even if after changing the config file and running

Code:

/sbin/lilo

. what seems to be the problem?

linus72 · 11-20-2010, 03:56 PM

change hda to sda in everything, lilo.conf too
then rerun lilo

if all else fails, change the symlink vmlinuz to point to the 2.6.36 kernel, rerun lilo and reboot

cd /boot
ln -sf vmlinuz6 vmlinuz
/sbin/lilo

wakkana12 · 11-20-2010, 11:50 PM

Quote:

Originally Posted by linus72

change hda to sda in everything, lilo.conf too
then rerun lilo

if all else fails, change the symlink vmlinuz to point to the 2.6.36 kernel, rerun lilo and reboot

cd /boot
ln -sf vmlinuz6 vmlinuz
/sbin/lilo

after running the

Code:

slackpkg update && slackpkg upgrade slackpkg

it installs everything and also created new kernel and deleted the old one it also creates a symlink to vmlinuz. all i have to do is edit the fstab and lilo.conf then run /sbin/lilo.. after running /sbin/lilo it said that i have added the new kernel.. but after restarting all changes in the lilo doesn't seems to take effect. i still have the same kernel but when running ls -la /boot there's no more 2.6.29.6 kernel and i couldn't enter my x..

what i did is to format my computer.. right now i tried editing lilo.conf and setting the

Code:

timeout = 100

then run /sbin/lilo and restarted my computer.. it still doesn't take effect.. did i miss something?

pupok · 11-21-2010, 04:27 PM

I have no idea how you managed to boot without kernel in place. Do you happen to have 2 disks?
What says

Code:

dmesg | grep Attached
uname -vr
mount
ls -l /boot/vmlinuz
grep -A 4 -E "^image|^boot" /etc/lilo.conf

If there is no other OS on your machine, then it's safe to install lilo into your MBR (Master boot record). Though always have a live CD handy and expect kernel panic.

Until now, you always put lilo into boot record of partition 2 (/dev/hda2). But it seems that at some point in history, you accidentally put lilo also into MBR (/dev/hda). At boot time, lilo in MBR has precedence over lilo in boot record of your bootable partition.

Now you just need to edit boot line in lilo.conf from

Code:

boot /dev/hda2

to

Code:

boot /dev/hda

Then please post lilo -v output here.

HTH