Aonghus Posted March 16, 2005 Report Share Posted March 16, 2005 (edited) Hi, I'm very new to Linux, so I hope you'll bear with me. I have kernel-2.6.8-1.10mdk-up-1GB (in Mandrake 10.1 community) installed on my PC with AMD K6 500Mhz processor and 256MB RAM. It seems that this is an unnecessary variant to use, since I don't have <1GB memory (I presume it refers to RAM?), and it was suggested to me when getting help with installing something else that the standard 2.6.8-1.10mdk kernel would be more appropriate. (The up-1MB kernel was installed by the installation discs automatically - or at least I dont' think I had an option to change it). So, I installed the kernel-2.6.8-1.10mdk rpm, which seemed to work fine, and appended a section to my lilo.conf that was identical to the others, except that it refered to different image and initrd files. Now, when I boot, I have the old kernel as default, plus an option for the new kernel, but when I choose the new one, the computer just reboots. My inittab file has 5 as the boot option, but this must only apply to the old kernel? I've appended the lilo.conf at the end of this message, but every section is identical, so I guess the problem isn't there. Does anyone know how to stop it rebooting? Any help would be greatly appreciated, regards, Aonghus liloconf.txt Edited March 24, 2005 by Aonghus Quote Link to comment Share on other sites More sharing options...
liquidzoo Posted March 16, 2005 Report Share Posted March 16, 2005 I don't see your lilo.conf file here, could you paste it so we can take a look? Quote Link to comment Share on other sites More sharing options...
Aonghus Posted March 16, 2005 Author Report Share Posted March 16, 2005 Sorry, forgot to attach it - it's there now Quote Link to comment Share on other sites More sharing options...
liquidzoo Posted March 16, 2005 Report Share Posted March 16, 2005 I assume it's this part that is having the problem: image=/boot/vmlinuz-2.6.8.1-10mdk label="2681-10" root=/dev/hda1 initrd=/boot/initrd-2.6.8.1-10mdk.img append="devfs=nomount acpi=ht resume=/dev/hda5 splash=silent" vga=788 read-only right? Do this for me. Open a terminal and type: ls-la /boot Copy and paste the output in here (to copy and paste, highlight with your mouse to copy, click on your mouse button to paste) Quote Link to comment Share on other sites More sharing options...
Aonghus Posted March 16, 2005 Author Report Share Posted March 16, 2005 Just reread my post - I should add that I didn't edit the Lilo.conf myself but that it was autogenerated when I installed the kernel rpm. I think it said that on the lilo file anyway... So, here's the contents of my /boot folder total 4812 drwxr-xr-x 3 root root 4096 Mar 16 01:31 ./ drwxr-xr-x 19 root root 4096 Mar 16 01:31 ../ -rw-r--r-- 1 root root 512 Mar 12 23:37 boot.0300 lrwxrwxrwx 1 root root 32 Mar 16 01:31 config -> config-2.6.8.1-10mdk-i586-up-1GB -rw-r--r-- 1 root root 60397 Sep 8 2004 config-2.6.8.1-10mdk -rw-r--r-- 1 root root 60295 Sep 8 2004 config-2.6.8.1-10mdk-i586-up-1GB -rw-r--r-- 1 root root 5032 Sep 14 2004 diag1.img -rw-r--r-- 1 root root 16796 Sep 14 2004 diag2.img drwxr-xr-x 2 root root 4096 Mar 12 23:07 grub/ -rw-r--r-- 1 root root 167695 Mar 15 14:14 initrd-2.6.8.1-10mdk-i586-up-1GB.img -rw------- 1 root root 184326 Mar 15 21:18 initrd-2.6.8.1-10mdk.img lrwxrwxrwx 1 root root 36 Mar 15 21:34 initrd.img -> initrd-2.6.8.1-10mdk-i586-up-1GB.img lrwxrwxrwx 1 root root 40 Mar 16 01:31 kernel.h -> /boot/kernel.h-2.6.8.1-10mdk-i586-up-1GB -rw-r--r-- 1 root root 537 Mar 12 23:42 kernel.h-2.6.8.1-10mdk-i586-up-1GB -rw------- 1 root root 376832 Mar 15 21:34 map lrwxrwxrwx 1 root root 15 Mar 15 21:34 message -> message-graphic -rw-r--r-- 1 root root 280792 Mar 15 21:18 message-graphic -rw-r--r-- 1 root root 116 Mar 15 21:34 message-text lrwxrwxrwx 1 root root 36 Mar 12 23:41 System.map -> System.map-2.6.8.1-10mdk-i586-up-1GB -rw-r--r-- 1 root root 547171 Sep 8 2004 System.map-2.6.8.1-10mdk -rw-r--r-- 1 root root 545730 Sep 8 2004 System.map-2.6.8.1-10mdk-i586-up-1GB -rw-r--r-- 1 root root 256 Mar 12 23:37 uk.klt lrwxrwxrwx 1 root root 33 Mar 15 21:34 vmlinuz -> vmlinuz-2.6.8.1-10mdk-i586-up-1GB -rw-r--r-- 1 root root 1309730 Sep 8 2004 vmlinuz-2.6.8.1-10mdk -rw-r--r-- 1 root root 1278195 Sep 8 2004 vmlinuz-2.6.8.1-10mdk-i586-up-1GB Hope this means something to you :) As an aside, anyone have an idea why I got the up-1GB kernel automatically in the first place? Thanks, Aonghus [formatted by spinynorman] Quote Link to comment Share on other sites More sharing options...
adamw Posted March 16, 2005 Report Share Posted March 16, 2005 Everything is actually as it should be. First, the kernel installed for you was the correct one. -up-1GB does not mean 'more than 1GB of memory'. It means UniProcessor (i.e., one CPU, not a dual CPU or more system) with 1GB of RAM or less. The default kernel is also built for a single CPU with up to 1GB of RAM. However, since 10.1 (IIRC), it is also built with i686 optimizations. It therefore does not work on CPUs that are not truly i686 compatible. K6 CPUs aren't; they are missing several options that true i686 CPUs support. As far as Linux (or more accurately, GCC) is concerned, a K6 is an i586 CPU. Therefore the installer is written to detect K6 CPUs and install the non-i686 kernel for them. That's why this kernel was selected and installed for you, and that's why it works but the 'default' kernel doesn't. So basically, there's nothing wrong, don't worry :). You just can't use the 'default' kernel on that machine, it tries to use things your CPU just can't do, which is why it dies. Stick to the one that was installed for you, it's the correct one. Quote Link to comment Share on other sites More sharing options...
Aonghus Posted March 19, 2005 Author Report Share Posted March 19, 2005 Thanks Adamw, I took the 'up-1GB' to mean 'upwards from' rather than 'up to'. I'll stick to the kernel I have, so; (although this means I have to do more of the work myself to get my linmodem going ;) ). thanks again, Aonghus (Sorry for the delay in response - I've been away from my computer for a few days) 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.