Has the 11.2 RC2 kernel stolen a CPU?

[hcvv]

I promised that I woul try again which boot from the 11.2 RC1 DVD worked.

Simple boot gives the same as the "nolapic" above: after kernel loads to 100% a dark screen for some 5 - 10 secs and then reboot.

All three possibilities in the menu under F5 (safe settings, no apci, no local apic) result in the splash screen, etc.

I had the same with the 11.2 M7 KDE live CD. And under VM it would not boot at all.

[Akoellh]

Sounds like a very strange (and rare?) interaction with your specific hardware setup.

Filing a bugreport would be a good idea IMHO.

Akoellh wrote:

> Sounds like a very strange (and rare?) interaction with your specific
> hardware setup.
>
> Filing a bugreport would be a good idea IMHO.

I agree.

That way others experiencing the same problem will benefit from that.

Greetings,

--
Camaleón

[hcvv]

https://bugzilla.novell.com/show_bug.cgi?id=551641
I hope something is doen before 10.3 expires

Thanks everybody for your suggestions, etc.

[Akoellh]

You should also try another kernel flavor (default/pae) to see if it is related to the "desktop" kernel.

P.S.

Just a side note(?):

I find it quite odd, that the newer kernel (2.6.31 in 11.2) needs "nolapic" to boot while the "older" one (2.6.22 in 10.3) boots without that restriction. The other way around wouldn't be less of a surpise.

[hcvv]

Originally Posted by Akoellh

You should also try another kernel flavor (default/pae) to see if it is related to the "desktop" kernel.

I was only trying out how 11.2 would work and how to make a transition plan going over to 11.2 on about 4 to 5 systems, partly a considerable distance away. The whole transition will also take a lot of convincing the end-users. The end-users are not at al willing to leave their trusted environment to find their way in KDE 4, etc.

I am not sure if I am willing to invest in finding out how to put a non standard kernel into 11.2 and, when it works on this system, then finding out which kenel has to go to which system and how to handle coming security updates on the systems (something I learned some end-users to do).

I am a bit in a low tide on 11.2 now and can only hope the bug report will attain something.

Originally Posted by Akoellh

I find it quite odd, that the newer kernel (2.6.31 in 11.2) needs "nolapic" to boot while the "older" one (2.6.22 in 10.3) boots without that restriction. The other way around wouldn't be less of a surpise.

Same to me. I was allready amazed when the 11.2 M7 (and when I remember correct even the 11.1 DVD) did only boot after meddling at the options under F5.

[oldcpu]

Originally Posted by hcvv

I am not sure if I am willing to invest in finding out how to put a non standard kernel into 11.2 and, when it works on this system, then finding out which kenel has to go to which system and how to handle coming security updates on the systems (something I learned some end-users to do).

There is a reasonable likelihood, that when addressing your bug report, you may be asked to install and test a kernel that they have specially packaged for you.

In truth, its not difficult if it is packaged as an rpm, and indeed one can easily setup the boot manager to boot to separate kernel versions on the same openSUSE installation. There are some important things to know:

• a. backup one's /boot/grub/menu.lst file so as to have available as a baseline reference.
• b. switch to using a VESA graphic driver or an openGL graphic driver, so that no matter what kernel one boots to, the driver will work. In the case of openSUSE-11.2 RC2, just do not use the proprietary graphic driver if one knows they will be testing different kernels. There is no xorg.conf so graphics should work easily between kernels.
• c. download "updated" kernel rpms to one's hard drive and install with the "rpm -ivh <kernel-app><kernel-app> " command. Note "ivh" and not "Uvh". With "ivh" one keeps the old kernel in parallel with the new. Do NOT reboot yet.
• d. take a look now at the /boot/grub/menu.lst file. A script in the new rpms will have modified that file. Check that updated file against the backed up menu.lst file (from step "a" ). Ensure that both kernels are now selections for booting. Note if one has multiple openSUSE versions on one's PC, the rpm script files can get mixed up when updating the /boot/grub/menu.lst file, so this check is essential.
• e. Now when you reboot, you will be given a choice in grub to boot to the old kernel, or to the new kernel.
• f. when removing the kernel, also before rebooting pay very careful to the /boot/grub/menu.lst file to ensure it has been updated properly.

The key here is to use a recommended rpm(s) for the new kernel that you want to test. Make certain you are clear as to what kernel rpms you need to install via "rpm -ivh .... ". I confess I have lost track as to what the various kernel apps are for (ie whats the difference between: kernel-default, kernel-default-extra, kernel-default-base) or what ever, ... but I am fairly confident someone who knows a lot more than I can easily chime in and sort this (lack of knowledge on my part).

[hcvv]

Thank you very much oldcpu. Reading it at a glance I think even I can do this . I will study it to the bottom when need arises.

b) might be usefull. I did install a Nvidia driver "the hard way" because 11.2 R1 did not have an NVIDIA repo and I allready found out I had to redo things because of the update to R2. I think I can handle that. Though I think for the test it is not needed because the dmesg | grep CPU and cat /proc/cpuinfo, that will reveal if the kernel sees the correct CPU, do work also in runlevel 3.

And yes I have to keep track of not only one, but two menu.lst files. Becasue I installed 11.2 on a new (logical, the first in the extended) partition and the install replaced the boot from the old 10.3 partition to the extended partition. Thus at the moment the system boots into the 11.2 menu.lst, where it shows also the 10.3 as a possibility. When choosing that one it comes up with the 10.3 menu.list. Isn't that called "chain loading"? But as long as I do understand what happens it is OK for me. When I install 11.2 in earnest that will all be remedied.

Thanks again for this workflow, makes me more confident.

[Akoellh]

Why so complicated?

Just install it via zypper (zypper in kernel-$FLAVOR) and reboot.

No fiddling around with drivers etc. just boot into RL1 with that new kernel, run "cat /proc/cpuinfo" and see if there is a difference.

After that, you can remove it again.

Thtat's the same what I did yesterday, took less than 5 minutes.

[oldcpu]

Originally Posted by Akoellh

Why so complicated?

Just install it via zypper (zypper in kernel-$FLAVOR) and reboot.

No fiddling around with drivers etc. just boot into RL1 with that new kernel, run "cat /proc/cpuinfo" and see if there is a difference.

After that, you can remove it again.

Thtat's the same what I did yesterday, took less than 5 minutes.

IMHO thats fraught with risk and ASSUMES the rpm script will perfectly handle the grub /boot/grub/menu.lst file edits, where experience has taught me that is not always the case. Each to their own but I would NOT recommend that without checking the menu.lst file.