Suse 10.1 beta 9 loads wrong kernel
I have installed the Suse 10.1 beta9 on my Inspiron 8500 and it comes up that the smp kernel is loaded instead of the default i386 kernel. Both are shown in /lib/modules. Boot log shows smp kernel loaded. How can I get it to load the default kernel instead of the smp kernel? Apparently this is a bug in this version according to bugzilla. Art
Art Fore wrote:
I have installed the Suse 10.1 beta9 on my Inspiron 8500 and it comes up that the smp kernel is loaded instead of the default i386 kernel. Both are shown in /lib/modules. Boot log shows smp kernel loaded. How can I get it to load the default kernel instead of the smp kernel?
Install the default kernel, then modify lilo.conf as appropriate. /Per Jessen, Zürich
On Tue, 2006-04-11 at 19:32 +0200, Per Jessen wrote:
Art Fore wrote:
I have installed the Suse 10.1 beta9 on my Inspiron 8500 and it comes up that the smp kernel is loaded instead of the default i386 kernel. Both are shown in /lib/modules. Boot log shows smp kernel loaded. How can I get it to load the default kernel instead of the smp kernel?
Install the default kernel, then modify lilo.conf as appropriate.
/Per Jessen, Zürich
Could not find any istall procedure or howto. Did try to rename the /boot/vmlinuz-2.6.16-18-default to vmlinuz but now it comes up with no /lib/modules/2.6.16-18-default/modules.dep, even though it is there so guess I will just reinstall 10.0 and try a 10.1 rc1 when it comes out. Could not find where the .Trash-user file was to recover the file, seem to be a deep dark secret that not even Google knows about. Art
Art Fore wrote:
Install the default kernel, then modify lilo.conf as appropriate.
/Per Jessen, Zürich
Could not find any istall procedure or howto.
Apologies - you install the default kernel using YaST - nothing unusual or complicated about it. I believe YaST will also modify the lilo.conf (or grub equivalent), but I'm not 100% certain, so check it before you reboot.
Did try to rename the /boot/vmlinuz-2.6.16-18-default to vmlinuz but now it comes up
It's best/easiest to just use symlinks when playing around with different kernels - if you do it often enough, it's probably worth adding entries to lilo. /Per Jessen, Zürich
On Tuesday 11 April 2006 21:51, Per Jessen wrote:
Art Fore wrote:
Install the default kernel, then modify lilo.conf as appropriate.
/Per Jessen, Zürich
Could not find any istall procedure or howto.
Apologies - you install the default kernel using YaST - nothing unusual or complicated about it. I believe YaST will also modify the lilo.conf (or grub equivalent), but I'm not 100% certain, so check it before you reboot.
Did try to rename the /boot/vmlinuz-2.6.16-18-default to vmlinuz but now it comes up
It's best/easiest to just use symlinks when playing around with different kernels - if you do it often enough, it's probably worth adding entries to lilo.
Maybe worth mentioning: one can install another kernel next to an existing one with: rpm -ihv /path/to/other/kernel-xx.xx.xx.rpm Takes care of /boot/grub/menu.lst and initrd too. Cheers, Leen
Art Fore wrote:
On Tue, 2006-04-11 at 19:32 +0200, Per Jessen wrote:
Art Fore wrote:
I have installed the Suse 10.1 beta9 on my Inspiron 8500 and it comes up that the smp kernel is loaded instead of the default i386 kernel. Both are shown in /lib/modules. Boot log shows smp kernel loaded. How can I get it to load the default kernel instead of the smp kernel?
Install the default kernel, then modify lilo.conf as appropriate.
/Per Jessen, Zürich
Could not find any istall procedure or howto. Did try to rename the /boot/vmlinuz-2.6.16-18-default to vmlinuz but now it comes up with no /lib/modules/2.6.16-18-default/modules.dep, even though it is there so guess I will just reinstall 10.0 and try a 10.1 rc1 when it comes out. Could not find where the .Trash-user file was to recover the file, seem to be a deep dark secret that not even Google knows about.
Art
Isn't your laptop an Intel processor with hyperthreading. If it is so, I believe that it thinks it has two processors, thus it is loading the correct kernel. this is a side effect of the hyperthreading I think. -- Joseph Loo jloo@acm.org
Joseph Loo wrote:
Isn't your laptop an Intel processor with hyperthreading. If it is so, I believe that it thinks it has two processors, thus it is loading the correct kernel. this is a side effect of the hyperthreading I think.
I assumed Art had checked that - he mentioned a bugreport - but absolutely, that is the most likely reason. And of course, if you want to benefit, however slightly, from using hyperthreading, you need an SMP kernel. /Per Jessen, Zürich
On Wed, 2006-04-12 at 08:34 +0200, Per Jessen wrote:
Joseph Loo wrote:
Isn't your laptop an Intel processor with hyperthreading. If it is so, I believe that it thinks it has two processors, thus it is loading the correct kernel. this is a side effect of the hyperthreading I think.
I assumed Art had checked that - he mentioned a bugreport - but absolutely, that is the most likely reason. And of course, if you want to benefit, however slightly, from using hyperthreading, you need an SMP kernel.
/Per Jessen, Zürich
All I know is it is a 2.2GHz Pentium-M processor. Art
Art Fore wrote:
All I know is it is a 2.2GHz Pentium-M processor.
What does "cat /proc/cpuinfo" tell you? I don't know if Pentium-Ms have hyperthreading, but /proc/cpuinfo will tell you immediately. If you see two CPUs listed, you're using the correct kernel. /Per Jessen, Zürich
On Wed, 2006-04-12 at 09:57 +0200, Per Jessen wrote:
Art Fore wrote:
All I know is it is a 2.2GHz Pentium-M processor.
What does "cat /proc/cpuinfo" tell you? I don't know if Pentium-Ms have hyperthreading, but /proc/cpuinfo will tell you immediately. If you see two CPUs listed, you're using the correct kernel.
/Per Jessen, Zürich
Appears to be only one. linux:~ # cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 2 model name : Mobile Intel(R) Pentium(R) 4 - M CPU 2.20GHz stepping : 7 cpu MHz : 2193.917 cache size : 512 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid xtpr bogomips : 4392.38
Art Fore wrote:
On Wed, 2006-04-12 at 09:57 +0200, Per Jessen wrote:
Art Fore wrote:
All I know is it is a 2.2GHz Pentium-M processor.
What does "cat /proc/cpuinfo" tell you? I don't know if Pentium-Ms have hyperthreading, but /proc/cpuinfo will tell you immediately. If you see two CPUs listed, you're using the correct kernel.
/Per Jessen, Zürich
Appears to be only one.
There's nothing really wrong with running an SMP kernel on a uni-processor system, but I can understand you'd rather have the default kernel installed. /Per
On Wednesday 12 April 2006 8:52 am, Art Fore wrote:
On Wed, 2006-04-12 at 09:57 +0200, Per Jessen wrote:
Art Fore wrote:
All I know is it is a 2.2GHz Pentium-M processor.
What does "cat /proc/cpuinfo" tell you? I don't know if Pentium-Ms have hyperthreading, but /proc/cpuinfo will tell you immediately. If you see two CPUs listed, you're using the correct kernel.
/Per Jessen, Zürich
Appears to be only one.
linux:~ # cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 2 model name : Mobile Intel(R) Pentium(R) 4 - M CPU 2.20GHz stepping : 7 cpu MHz : 2193.917 cache size : 512 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid xtpr bogomips : 4392.38
I'm not an expert on these things, but I thought that the "ht" flag implied hyperthreading? -- Don
On Wed, 2006-04-12 at 08:34 +0200, Per Jessen wrote:
Joseph Loo wrote:
Isn't your laptop an Intel processor with hyperthreading. If it is so, I believe that it thinks it has two processors, thus it is loading the correct kernel. this is a side effect of the hyperthreading I think.
I assumed Art had checked that - he mentioned a bugreport - but absolutely, that is the most likely reason. And of course, if you want to benefit, however slightly, from using hyperthreading, you need an SMP kernel.
/Per Jessen, Zürich
Sorry for sending the email to Jessen and the list. Forgot to change the to line. One thing I noted, OOo writer opens in 6 seconds with quickstarter in 10.0 and 12 seconds in 10.1 when it was using the smp kernel with quickstarter. Art
participants (5)
-
Art Fore -
Don Raboud -
Joseph Loo -
Leendert Meyer -
Per Jessen