https://bugzilla.novell.com/show_bug.cgi?id=708214 https://bugzilla.novell.com/show_bug.cgi?id=708214#c2 --- Comment #2 from Neil Rickert 2011-09-04 04:05:29 UTC --- I reinstalled M5, this time as 64 bit. The desktop kernel is fine for the 64 bit install. It was the 32 bit install that failed to load. (I suspect the PAE functionality was the problem). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=708214 https://bugzilla.novell.com/show_bug.cgi?id=708214#c4 --- Comment #4 from Neil Rickert 2011-10-06 16:25:47 UTC --- Yet another datapoint. I installed Beta1 32 bit on another system with AMD athlon processor. The Desktop kernel loads there. The system has only 2G of memory, while the system where it does not load has 6G. And a comment: I am doubting that this will be fixed in time for the 12.1 release (or perhaps ever). We probably need to advise people with more than 4G of memory, that they should install a 64 bit system and not depend on the PAE extensions for the 32 bit kernel. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=708214 https://bugzilla.novell.com/show_bug.cgi?id=708214#c5 --- Comment #5 from Neil Rickert 2011-10-23 05:26:07 UTC --- One more datapoint. The problem still exists with rc1 (as I expected). However, I found another complication. This time I installed from the DVD instead of from the live CD. The installer chose the desktop kernel. Unfortunately, I could not select the default kernel due to bug 725874. The result was an installed but incompletely configured system that would not boot. Perhaps the installer should always select the default kernel on 32 bit systems, as long as this bug is there. Otherwise inexperienced user may get an unbootable system if they happen to have hardware where the desktop kernel fails to load. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=708214 https://bugzilla.novell.com/show_bug.cgi?id=708214#c7 Frank Knoben changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |admin@igpm.rwth-aachen.de --- Comment #7 from Frank Knoben 2012-01-02 14:30:24 UTC --- My problems with booting the standard kernel were fixed, after adding an iommu option to the kernel parameters. The kernel had problems with the bios iommu setup. I think, the handling of the memory hole between 15M-16M causes the system to crash while booting. I added iommu=noaperture to the boot parameters. If that does not work, maybe another iommu option will work. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=708214 https://bugzilla.novell.com/show_bug.cgi?id=708214#c9 Ned Ulbricht changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nedu@netscape.net --- Comment #9 from Ned Ulbricht 2012-01-30 22:13:17 UTC --- I am NOT seeing this on 32bit-desktop running on 32bit system with 5 GB memory: Machine is IBM Intellistation 6221 with dual Xeon processors (2 x Intel SL6VN) and 5 GB ECC memory (Intel E7505 MCH). Boots and runs kernel-desktop-3.1.9-1.4.1.i586 from openSUSE 12.1 without seeing hang at initrd. (During lifetime, this machine has also run openSUSE 11.1, 11.2, 11.3 and several earlier 12.1 kernels.) Does this bug only manifest on 64bit systems? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.