bigjohn Posted June 15, 2004 Report Share Posted June 15, 2004 So after asking a few boot related questions, and reading some other thread's (about booting and about installing a network printer) It appear's that one of the most straight forward thing's would be to upgrade my kernel from 2.6.3-7 to the latest 2.6.3-13. previously (when I had the CE version of mandrake 10) I just installed the new kernel, upgraded the kernel sources and then re-installed the nvidia driver. So I've used the installer in the MCC but I can't get the 2.6.3-13 kernel booting. I've tried the kde>system>Boot Manager (LILO) facility kindly suggested by chris z in this thread but when I look at the lilo.conf it shows this:- # File generated by DrakX/drakboot # WARNING: do not forget to run lilo after modifying this file boot=/dev/hda map=/boot/map default="windows" keytable=/boot/uk.klt prompt nowarn timeout=100 message=/boot/message menu-scheme=wb:bw:wb:bw image="/boot/vmlinuz" label="linux" root="/dev/hda5" initrd="/boot/initrd.img" append="devfs=mount acpi=ht resume=/dev/hda3 splash=silent" vga=788 read-only image=/boot/vmlinuz label="linux-nonfb" root=/dev/hda5 initrd=/boot/initrd.img append="devfs=mount acpi=ht resume=/dev/hda3" read-only image=/boot/vmlinuz label="failsafe" root=/dev/hda5 initrd=/boot/initrd.img append="failsafe acpi=ht resume=/dev/hda3 devfs=nomount" read-only other=/dev/hda1 label="windows" table=/dev/hda other=/dev/fd0 label="floppy" unsafe image=/boot/vmlinuz-2.6.3-13mdk label=263-13 root=/dev/hda5 read-only optional vga=788 append=" devfs=mount acpi=ht resume=/dev/hda3 splash=silent" initrd=/boot/initrd-2.6.3-13mdk.img Now as you can see, it's there, but if I try to run lilo, I get this [root@johnspc john]# /sbin/lilo -v LILO version 22.5.8, Copyright (C) 1992-1998 Werner Almesberger Development beyond version 21 Copyright (C) 1999-2003 John Coffman Released 10-Oct-2003, and compiled at 18:03:01 on Feb 19 2004 Reading boot sector from /dev/hda Using GRAPHIC secondary loader Calling map_insert_data Mapping message file /boot/message -> message-graphic Calling map_insert_file Boot image: /boot/vmlinuz -> vmlinuz-2.6.3-7mdk Mapping RAM disk /boot/initrd.img -> initrd-2.6.3-7mdk.img Added linux Boot image: /boot/vmlinuz -> vmlinuz-2.6.3-7mdk Mapping RAM disk /boot/initrd.img -> initrd-2.6.3-7mdk.img Added linux-nonfb Boot image: /boot/vmlinuz -> vmlinuz-2.6.3-7mdk Mapping RAM disk /boot/initrd.img -> initrd-2.6.3-7mdk.img Added failsafe Boot other: /dev/hda1, on /dev/hda, loader CHAIN Added windows * Boot other: /dev/fd0, loader CHAIN Pseudo partition start: 0 Added floppy Skipping /boot/vmlinuz-2.6.3-13mdk Writing boot sector. /boot/boot.0300 exists - no boot sector backup copy made. [root@johnspc john]# Hence on boot up, the 2.6.3-13 version doesn't show up as an option, and I can't try to install my network printer or config/reinstall the nvidia drivers for it Perhap's someone could advise me as to what I need to do next? regards John Quote Link to comment Share on other sites More sharing options...
chris z Posted June 15, 2004 Report Share Posted June 15, 2004 (edited) image=/boot/vmlinuz-2.6.3-13mdklabel=263-13 root=/dev/hda5 read-only optional vga=788 append=" devfs=mount acpi=ht resume=/dev/hda3 splash=silent" initrd=/boot/initrd-2.6.3-13mdk.img the "append=******" line in that last entry has an incorrect spacing before devfs=. it should read like......... append="devfs=blah,blah........" no space between the " & devfs. fix that, rerun lilo -v, reboot. gotta watch your p's & q's (& spacing) when editing lilo. :P Chris Edited June 15, 2004 by chris z Quote Link to comment Share on other sites More sharing options...
bigjohn Posted June 15, 2004 Author Report Share Posted June 15, 2004 OK i'll go and try that. Thank Heaven for you guy's who know what you're doing :D, maybe I'll get there one day (in about 100 year's :)) regards John Quote Link to comment Share on other sites More sharing options...
bigjohn Posted June 15, 2004 Author Report Share Posted June 15, 2004 the kde boot manager is still showing the 2.6.3-13 entry like this image=/boot/vmlinuz-2.6.3-13mdk label=263-13 root=/dev/hda5 read-only optional vga=788 append="devfs=mount acpi=ht resume=/dev/hda3 splash=silent" initrd=/boot/initrd-2.6.3-13mdk.img i.e. with the space taken out, but /sbin/lilo -v still seems to be doing this Skipping /boot/vmlinuz-2.6.3-13mdk Writing boot sector. /boot/boot.0300 exists - no boot sector backup copy made. [root@johnspc john]# Now I'm really confused. Should I delete the /boot/boot.0300 file maybe ?? regards John Quote Link to comment Share on other sites More sharing options...
chris z Posted June 15, 2004 Report Share Posted June 15, 2004 you need to rearrange some lines. here's how your entry should look........... image=/boot/vmlinuz-2.6.3-13mdklabel=263-13 root=/dev/hda5 initrd=/boot/initrd-2.6.3-13mdk.img append="devfs=mount acpi=ht resume=/dev/hda3 splash=silent" read-only optional vga=788 don't forget to run lilo -v afterwards. Chris Quote Link to comment Share on other sites More sharing options...
bigjohn Posted June 15, 2004 Author Report Share Posted June 15, 2004 Righto! regards John Quote Link to comment Share on other sites More sharing options...
bigjohn Posted June 15, 2004 Author Report Share Posted June 15, 2004 Ho hum!:) the little bugger. Now the kde boot manager is showing it like this image=/boot/vmlinuz-2.6.3-13mdk label=263-13 root=/dev/hda5 initrd=/boot/initrd-2.6.3-13mdk.img append="devfs=mount acpi=ht resume=/dev/hda3 splash=silent" read-only optional vga=788 i.e. with the changes made, but running lilo is still showing this (after a reboot, just in case) bash-2.05b$ su Password: [root@johnspc john]# mount /dev/hda2 [root@johnspc john]# /sbin/lilo -v LILO version 22.5.8, Copyright (C) 1992-1998 Werner Almesberger Development beyond version 21 Copyright (C) 1999-2003 John Coffman Released 10-Oct-2003, and compiled at 18:03:01 on Feb 19 2004 Reading boot sector from /dev/hda Using GRAPHIC secondary loader Calling map_insert_data Mapping message file /boot/message -> message-graphic Calling map_insert_file Boot image: /boot/vmlinuz -> vmlinuz-2.6.3-7mdk Mapping RAM disk /boot/initrd.img -> initrd-2.6.3-7mdk.img Added linux Boot image: /boot/vmlinuz -> vmlinuz-2.6.3-7mdk Mapping RAM disk /boot/initrd.img -> initrd-2.6.3-7mdk.img Added linux-nonfb Boot image: /boot/vmlinuz -> vmlinuz-2.6.3-7mdk Mapping RAM disk /boot/initrd.img -> initrd-2.6.3-7mdk.img Added failsafe Boot other: /dev/hda1, on /dev/hda, loader CHAIN Added windows * Boot other: /dev/fd0, loader CHAIN Pseudo partition start: 0 Added floppy Skipping /boot/vmlinuz-2.6.3-13mdk Writing boot sector. /boot/boot.0300 exists - no boot sector backup copy made. [root@johnspc john]# Erm I don't suppose it matters or not where on the list it is? regards John Quote Link to comment Share on other sites More sharing options...
chris z Posted June 15, 2004 Report Share Posted June 15, 2004 ok........brain fart here, sorry. you said you upgraded the kernel. so, the main linux boot option in lilo should be your new kernel. did you also upgrade the kernel source? look in /usr/src & see if there's a kernel named 2.6.3-13mdk. if there isn't, then that last entry is pointing to a nonexistant kernel. if your old kernel (2.6.3-7mdk) is in /usr/src, then that's what that last lilo entry should point to. sorry, i'm at work, gotta run. check what's in /usr/src & adjust from there. get the 2.6.3-13mdk sources if you didn't already. Chris Quote Link to comment Share on other sites More sharing options...
bigjohn Posted June 15, 2004 Author Report Share Posted June 15, 2004 I stared at it hard and suddenly though it could be because there where no "" round the entry parameters, (your p's and q's/crossing t's and dotting i's comment), and moved the 2.6.3-13 entry under the "normal" one, but it didn't like that at all. So as you can see # File generated by DrakX/drakboot # WARNING: do not forget to run lilo after modifying this file boot=/dev/hda map=/boot/map default="windows" keytable=/boot/uk.klt prompt nowarn timeout=100 message=/boot/message menu-scheme=wb:bw:wb:bw image="/boot/vmlinuz" label="linux" root="/dev/hda5" initrd="/boot/initrd.img" append="devfs=mount acpi=ht resume=/dev/hda3 splash=silent" vga=788 read-only #image="/boot/vmlinuz-2.6.3-13mdk" #label="263-13" #root="/dev/hda5" #initrd="/boot/initrd-2.6.3-13mdk.img" #append="devfs=mount acpi=ht resume=/dev/hda3 splash=silent" #vga=788 #read-only image=/boot/vmlinuz label="linux-nonfb" root=/dev/hda5 initrd=/boot/initrd.img append="devfs=mount acpi=ht resume=/dev/hda3" read-only image=/boot/vmlinuz label="failsafe" root=/dev/hda5 initrd=/boot/initrd.img append="failsafe acpi=ht resume=/dev/hda3 devfs=nomount" read-only other=/dev/hda1 label="windows" table=/dev/hda other=/dev/fd0 label="floppy" unsafe for the time being, it's commented out, but I still think that it looks correct i.e. exactly the same as the entry above with seems to boot. It's as if somethings missing. So here's the content's of my /boot [root@johnspc john]# ls -l /boot total 6928 lrwxrwxrwx 1 root root 1 May 14 17:35 boot -> ./ -rw-r--r-- 1 root root 512 Jun 7 12:58 boot.0300 -rw-r--r-- 1 root root 54087 Mar 17 14:58 config-2.6.3-7mdk -rw-r--r-- 1 root root 5032 Feb 19 17:03 diag1.img -rw-r--r-- 1 root root 16796 Feb 19 17:03 diag2.img drwxr-xr-x 2 root root 4096 Jun 11 11:28 grub/ -rw-r--r-- 1 root root 174166 Jun 15 14:03 initrd-2.6.3-13mdk.img -rw-r--r-- 1 root root 174419 Jun 7 12:58 initrd-2.6.3-7mdk.img -rw-r--r-- 1 root root 1323821 May 14 18:12 initrd-2.6.5-gentoo-r1 lrwxrwxrwx 1 root root 21 Jun 11 11:50 initrd.img -> initrd-2.6.3-7mdk.img -rw-r--r-- 1 root root 1969598 May 14 18:03 kernel-2.6.5-gentoo-r1 lrwxrwxrwx 1 root root 29 Jun 11 11:28 kernel.h -> /boot/kernel.h-2.6.3-7mdkBOOT -rw------- 1 root root 517632 Jun 15 15:23 map lrwxrwxrwx 1 root root 15 Jun 11 11:54 message -> message-graphic -rw-r--r-- 1 root root 442273 Jun 15 14:03 message-graphic -rw-r--r-- 1 root root 116 Jun 11 11:54 message-text -rw-r--r-- 1 root root 898908 Mar 17 14:58 System.map-2.6.3-7mdk -rw-r--r-- 1 root root 256 Jun 11 11:50 uk.klt lrwxrwxrwx 1 root root 18 Jun 11 11:50 vmlinuz -> vmlinuz-2.6.3-7mdk -rw-r--r-- 1 root root 1440198 Mar 17 14:58 vmlinuz-2.6.3-7mdk [root@johnspc john]# Now as far as I can see, the system is saying that the 2.6.3-13 was installed correctly (both the kernel and kernel sources), but I can't see any config-2.6.3-13 and the kernel.h is pointing to the wrong kernel version, there's no indication of /boot/kernel.h-2.6.3-13mdkBOOT etc etc (system.map, vmlinuz-2.6.3-13) does this mean that it's ended up somewhere else when I did the install (if I try urpmi kernel it say's which one 3-7 and 3-13, I say 3-13 and it replies that everythin is installed) ????? regards John Quote Link to comment Share on other sites More sharing options...
bigjohn Posted June 15, 2004 Author Report Share Posted June 15, 2004 And yes, there is the 2.6.3-13mdk in /usr/src. Actually there's a shortcut to /usr/src/linux-2.6.3-13mdk and the /usr/src/linux-2.6.3-13mdk directory itself, plus a directory call RPMS regards John Quote Link to comment Share on other sites More sharing options...
chris z Posted June 15, 2004 Report Share Posted June 15, 2004 install the sources for 2.6.3-13............ (see my post above the one you just made) Chris Quote Link to comment Share on other sites More sharing options...
chris z Posted June 15, 2004 Report Share Posted June 15, 2004 ok. let's start over from the beginning. when you say you got the kernel upgrade, are you sure it was a kernel upgrade or was it a kernel-source upgrade? they are 2 different things. IE: you can be running kernel 2.6.3-7 but actually have sources for 2.6.3-13. looking at your /boot, you have no vmlinuz-2.6.3-13mdk to boot to. that's telling me that you just installed the sources for 2.6.3-13, but not a kernel itself. in terminal, as root, type uname -a & tell me what kernel it says you are currently running. if it says 2.6.3-7, then you need to get the 2.6.3-13 kernel itself for that last entry to work. Chris Quote Link to comment Share on other sites More sharing options...
bigjohn Posted June 15, 2004 Author Report Share Posted June 15, 2004 (edited) Ok since your last post, I decided to look in the mandrake control centre>rpmdrake>rpmdrake- both the kernel and the kernel sources where there. I'd downloaded them together, and for some reason, the kernel hadn't installed properly (well that's what I'm presuming anyway - given the missing stuff from the /boot. So I uninstalled them both, and then re-installed them, kernel first, followed by the sources. When I went into the kde boot manager, I could then see the 263-13 entry, so caution to the wind and rebooted. On the lilo prompt, I selected the 263-13 entry and things booted fine. I did uname -r which showed me to be in the 2.6.3-13mdk kernel, that go 1 :D So I did a reboot and selected "linux", and booted into that fine as well, again the uname -r showed me to be in the 2.6.3-13mdk kernel so that got a So I then looked at the lilo.conf as show by the kde boot manager, and it look's like this at the moment: # File generated by DrakX/drakboot # WARNING: do not forget to run lilo after modifying this file boot=/dev/hda map=/boot/map default="windows" keytable=/boot/uk.klt prompt nowarn timeout=100 message=/boot/message menu-scheme=wb:bw:wb:bw image="/boot/vmlinuz" label="linux" root="/dev/hda5" initrd="/boot/initrd.img" append="devfs=mount acpi=ht resume=/dev/hda3 splash=silent" vga=788 read-only #image="/boot/vmlinuz-2.6.3-13mdk" #label="263-13" #root="/dev/hda5" #initrd="/boot/initrd-2.6.3-13mdk.img" #append="devfs=mount acpi=ht resume=/dev/hda3 splash=silent" #vga=788 #read-only image=/boot/vmlinuz label="linux-nonfb" root=/dev/hda5 initrd=/boot/initrd.img append="devfs=mount acpi=ht resume=/dev/hda3" read-only image=/boot/vmlinuz label="failsafe" root=/dev/hda5 initrd=/boot/initrd.img append="failsafe acpi=ht resume=/dev/hda3 devfs=nomount" read-only other=/dev/hda1 label="windows" table=/dev/hda other=/dev/fd0 label="floppy" unsafe image=/boot/vmlinuz-2.6.3-13mdk label=263-13 root=/dev/hda5 read-only optional vga=788 append=" devfs=mount acpi=ht resume=/dev/hda3 splash=silent" initrd=/boot/initrd-2.6.3-13mdk.img You'll notice that there's still the space before devfs in the append line, and that the rest of it's still "arse about face", but it's booting, also all the stuff for the "linux" entry seems to be pointing to the right places, so I'm going to leave things as they are (but I'm still gonna have to sit and plough my way though the man page for lilo :() So as thing's seemed to be going well, I logged in as root, did the ctrl+alt+backspace trick to kill the xserver and just followed the instructions and re-installed the nvidia driver. Which mean's that with your help, I've managed to go from to :headbang: Brilliant. many many thanks for your help and assistance - hope your work wasn't too stressful (I'm not at work till about 10pm tonight :() regards John Edited June 15, 2004 by bigjohn Quote Link to comment Share on other sites More sharing options...
bigjohn Posted June 15, 2004 Author Report Share Posted June 15, 2004 Well I've also removed both the commented out vmlinuz/2.6.3-13 entry and the space in the append line of the 2.6.3-13 entry at the bottom (and renamed it mandrake, I might move it later, we'll see if it bug's me). Again, thanks for the help/assistance, "mucho appreciado" as they say in bad "spanglish"! regards John Quote Link to comment Share on other sites More sharing options...
chris z Posted June 15, 2004 Report Share Posted June 15, 2004 w00t! glad to hear you got it working! looks like you did the important leg work. good job! :D Chris 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.