Guest G3ck0G33k Posted March 27, 2003 Report Share Posted March 27, 2003 Hi, I upgraded my old Mdk 9.0 installation with Mdk 9.1 (final) yesterday. However, I have had several glitches: (1) The kernel remains 2.4.19-16mdk (2) Message "Already in UTF8 mode" (3) Shut down halts (4) Upgade doesn't allow me to choose packages These are the ones I can think of for now. When I have turn on my computer and get to the (non-GUI) login I see: --- Mandrake Linux release 9.1 (bamboo) for i586 Kernel 2.4.19-16mdk on an i686/ tty1 ... Already in UTF8 mode -bash-2.05b$_ --- The "..." stands for "login:" etc. Somehow this seems wong... How do I get the new kernel and what is UTF8? Ok, so I close X, type "reboot" (or "halt") to check with the installation CD1. Now, the system dosen't reboot or halt but gives me the message: ;2R Huh? Something is wrong here. I need to retype "halt" and couple of times before the system responds. Ok, and when I load the CD1 there is no option to select individual packages but it starts installing and upgrading whatever I had. Please, help! What is wrong? Quote Link to comment Share on other sites More sharing options...
aru Posted March 27, 2003 Report Share Posted March 27, 2003 Somehow this seems wong... How do I get the new kernel and what is UTF8? mount the cd that has the new kernel and run: rpm -ivh /path/to/kernel/kernel-version.rpm or rpm -ivh ftp://ftp.lip6.fr/pub/linux/distributions...nel-version.rpm UTF8, just a hint: UTF8 - What is it and why is it important? Quote Link to comment Share on other sites More sharing options...
Guest G3ck0G33k Posted March 27, 2003 Report Share Posted March 27, 2003 Hi! Thanks for your help! Using "rpm -ivh /path/to/kernel/kernel-version.rpm" I get the following message: kernel-smp-2.4.21.0.13mdk-1-1mdk.i586.rpm [root@computer g3ckog33k]# rpm -ivh /mnt/cdrom/Mandrake/RPMS/kernel-2.4.21.0.13mdk-1-1mdk.i586.rpm Preparing... ########################################### [100%] package kernel-2.4.21.0.13mdk-1-1mdk is already installed [root@computer g3ckog33k]# Puzzling! UTF8, just a hint: UTF8 - What is it and why is it important? Ok, thanks, but why does it display that "Already installed" message? It seems unnecessary. Quote Link to comment Share on other sites More sharing options...
tyme Posted March 27, 2003 Report Share Posted March 27, 2003 so, you did an upgrade, not a new install, right? if so, the issue is your bootloader. it's still pointing to and using the old kernel as default, for whatever reason. er, i think. post the contents of /etc/lilo.conf edit: removed something after realizing i read what you said wrong (about the individual packages). Quote Link to comment Share on other sites More sharing options...
aru Posted March 27, 2003 Report Share Posted March 27, 2003 just to advance some steps. If your boot loader is lilo, then edit the lilo.conf file (the one tyme said) and make sure that the 'default' flag points to the 2.4.21 kernel label. Once you make the changes, run /sbin/lilo (check "man lilo" and "man lilo.conf" if you have any doubts) BTW, does anybody know why mandrake has released a 2.4.21 kernel which AFAIK is not stable yet? The lastest stable kernel is the 2.4.20 :shock: Quote Link to comment Share on other sites More sharing options...
SoulSe Posted March 27, 2003 Report Share Posted March 27, 2003 Don't even try and fix an upgrade - make backups and install Bamboo fresh. Quote Link to comment Share on other sites More sharing options...
Guest G3ck0G33k Posted March 27, 2003 Report Share Posted March 27, 2003 SoulSe: Yes, I am considering that... However, perhaps... Here is my lilo.conf Yes, I know, I never dared to remove those old Windows-pointers... ;) ============== boot=/dev/hda map=/boot/map vga=normal default="linux" keytable=/boot/se-latin1.klt prompt nowarn timeout=100 message=/boot/message menu-scheme=wb:bw:wb:bw image=/boot/vmlinuz label="linux" root=/dev/hda8 initrd=/boot/initrd.img append="devfs=mount acpi=off" read-only other=/dev/hdb1 label="windows" table=/dev/hdb map-drive=0x80 to=0x81 map-drive=0x81 to=0x80 other=/dev/fd0 label="floppy" unsafe other=/dev/hdb1 label="old_windows" table=/dev/hdb map-drive=0x80 to=0x81 map-drive=0x81 to=0x80 other=/dev/hdb1 label="old2_windows" table=/dev/hdb map-drive=0x80 to=0x81 map-drive=0x81 to=0x80 other=/dev/hdb1 label="old3_windows" table=/dev/hdb map-drive=0x80 to=0x81 map-drive=0x81 to=0x80 other=/dev/hdb1 label="old4_windows" table=/dev/hdb map-drive=0x80 to=0x81 map-drive=0x81 to=0x80 image=/boot/vmlinuz-2.4.19-16mdk label="old_linux" root=/dev/hda8 initrd=/boot/initrd-2.4.19-16mdk.img append="hdd=ide-scsi devfs=mount acpi=off" read-only image=/boot/vmlinuz-2.4.19-16mdk label="2419-16" root=/dev/hda8 initrd=/boot/initrd-2.4.19-16mdk.img append="devfs=mount acpi=off" read-only image=/boot/vmlinuz label="failsafe" root=/dev/hda8 initrd=/boot/initrd.img append="devfs=nomount acpi=off failsafe" read-only Quote Link to comment Share on other sites More sharing options...
aru Posted March 27, 2003 Report Share Posted March 27, 2003 This is more or less what you should do: Note: I'm supposing that there is already a kernel image on /boot named: vmlinuz-2.4.21.0.13mdk As you have a 'generic' entry in you lilo.conf that points to a symlink that itself points to a 'real' image: image=/boot/vmlinuz label="linux" root=/dev/hda8 initrd=/boot/initrd.img append="devfs=mount acpi=off" read-only all you have to do is run the following commands (check that the real image "vmlinuz-2.4.21.0.13mdk" or similar exists on /boot): ~# rm -f /boot/vmlinuz ~# ln -s /boot/vmlinuz-2.4.21.0.13mdk /boot/vmlinuz ~# /sbin/lilo (*) or even better: ~# rm -f /boot/vmlinuz /boot/initrd.img ~# ln -s /boot/vmlinuz-2.4.21.0.13mdk /boot/vmlinuz ~# ln -s /boot/initrd.img-2.4.21.0.13mdk /boot/initrd.img ~# /sbin/lilo (*) Those commands do: - remove the soft link /boot/vmlinuz that points to a real kernel image - create a new soft link that links the image you want to run (vmlinuz-2.4.21.0.13mdk) to /boot/vmlinuz - run lilo to write the changes to your boot sector. Finally reboot and choose the 'linux' entry at your lilo boot screen HTH Quote Link to comment Share on other sites More sharing options...
Guest G3ck0G33k Posted March 27, 2003 Report Share Posted March 27, 2003 Ok, now i'm in a mess... :) I did your "even better" option, but now the system won't let me create a softlink to "vmlinuz-2.4.21.0.13mdk.img" [Note the .img! which is the only such file around] If I reboot now, i won't have a lilo... Please, help. :? Quote Link to comment Share on other sites More sharing options...
Guest G3ck0G33k Posted March 27, 2003 Report Share Posted March 27, 2003 Ok, please ignore the latest message... I had a typo in the image file name. Quote Link to comment Share on other sites More sharing options...
Guest G3ck0G33k Posted March 27, 2003 Report Share Posted March 27, 2003 It rebooted with the new lilo.conf to no avail. Yet, it appears as if all linked files in /boot have been linked to the old kernel, therefore the trouble. But, there is one link, "/boot/kernel.h", which points to "/boot/kernel.h-2.4.19-16mdk". However should i emove that link i don't have a kenel.h for the new kenel... What should I do now?! SoulSe's remark may now seem to be an option. Thanks for any help! Quote Link to comment Share on other sites More sharing options...
aru Posted March 27, 2003 Report Share Posted March 27, 2003 Sorry, it was my fault! As I've never used an initrd.img to boot, I mistaked the way it works. To create a valid initrd.img run: ~# mkinitrd /boot/initrd-2.4.21.0.13mdk.img 2.4.21.0.13mdk Then link: ~# ln -s /boot/initrd-2.4.21.0.13mdk.img /boot/initrd.img and finally run lilo again Sorry for my mistake (and correct me if I'm wrong) Quote Link to comment Share on other sites More sharing options...
Guest G3ck0G33k Posted March 27, 2003 Report Share Posted March 27, 2003 Ok, but before I do that I wish to make sure of one thing. Shouldn't ~# mkinitrd /boot/initrd-2.4.21.0.13mdk.img 2.4.21.0.13mdk be ~# mkinitrd /boot/initrd-2.4.21.0.13mdk.img initrd-2.4.21.0.13mdk Please confirm. Thanks! Quote Link to comment Share on other sites More sharing options...
aru Posted March 27, 2003 Report Share Posted March 27, 2003 No, it is as: mkinitrd initrd_image_name kernel_version The full thing is: ~# rm -f /boot/vmlinuz /boot/initrd.img ~# ln -s /boot/vmlinuz-2.4.21.0.13mdk /boot/vmlinuz ~# mkinitrd /boot/initrd-2.4.21.0.13mdk.img 2.4.21.0.13mdk ~# ln -s /boot/initrd-2.4.21.0.13mdk.img /boot/initrd.img ~# /sbin/lilo Quote Link to comment Share on other sites More sharing options...
Guest G3ck0G33k Posted March 27, 2003 Report Share Posted March 27, 2003 Ok! Thanks. Now it seems to work. Just a detail. mkinitrd /boot/initrd-2.4.21.0.13mdk.img 2.4.21.0.13md should have been ~# mkinitrd /boot/initrd-2.4.21.0.13mdk.img 2.4.21-0.13mdk with a hyphen Otherwise I'm going down for a re-boot now (fingers crossed) Thanks for your help! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.