Before booting: Press ‘c’ to get to the grub2-command line
Load kernel with “linux /boot/vmlinux mem=4G”
Load initrd with “initrd /boot/initrd”
Boot with “boot”
Downgrade kernel
I don’t know under which circumstances this happens. I also run an AMD system, like the posters in the ArchLinux thread. The problem occured after upgrading to kernel 3.6.4-9.1 (desktop flavour), which is currently offered by Tumbleweed.
So I have no idea what is wrong with Tumbleweed, but I heard an intrd issue also kept kernel 3.7-fcx from working. No matter if you use Tumbleweed or not, you can serve up the latest kernel version using SAKC:
However, compiling the kernel by myself defies the basic idea of TW, being up-to-date without having to do too much manual work ;). Then I can also start compiling other software by hand, Gentoo-style.
…and as other distribution users report this problem too, allegedly fixed as of 3.7rc3 (see linked ArchLinux thread), blaming the TW compilation and compiling 3.6.4 yourself probably would not help in any case…
I am running kernel 3.6.4 on my PC’s and having no problems after being compiled using SAKC. It is worth a try and not much trouble at all. You should give it a try.
Compiling kernels myself is something I did back in SuSE 5.x days. Nowadays I spend my time more on real-life problems and avoid compiling stuff… only eats up time without too much of a personal benefit. Usually TW gives me enough “bleeding edge” feeling for my advanced age without completely messing up my system with unstable stuff… usually.
I think that anyone that tries using SAKC, will see that it is a breeze to use. If you really have a dead slow PC, it might take a while to compile, a fast PC takes nine minutes, my laptop takes 48, but you can just put the terminal session into the background. SAKC will, if your sound system works, notify you by sound that the compile has finish successfully. You don’t need to know a thing. Download the kernel tarball into your Downloads folder. Open up a terminal session and type in sakc or if you have KDE desktop loaded, you will get a menu application icon that you can select after the first time sakc has been run and nothing else you need to know or to do.
I’ll stop answering because I really don’t know what your advertisment for SAKC has to do with the problem I reported :. And if you would have read the post I linked to, you would see that it probably has nothing to do with compiling the kernel yourself, simply 3.6.4 seems to have problems on some AMD CPUs with more than 4G RAM. Read also here https://bugs.archlinux.org/task/32307.
The issue with the kernel appears to be related to the usage of Tumbleweed. If you want the latest kernel there is more than one way to obtain it. The availability to use a bash script like SAKC is just another feature of openSUSE. You are free as always to use what you want, but if you feel you have a problem that is kernel related, then SAKC is one very free and open source option that you. I as SAKC’s author hope it is found to be useful to our users here. Good luck in what ever you decide to do.
NO, NO, NO, how often do I have to repeat it? The issue has to do with kernel 3.6.4, no matter how you get it. Do you ever read the stuff I post?
Hi all, turns out there was an issue with Linux 3.6.4 on some AMD systems with more than 4GB of RAM. 3.6.5 fixed this bug. Unfortunately this was a little too late for the recent ISO image. I was wondering what was the best way to handle issues like this. One of the benefits of monthly releases is that we have more than one image available which is recent enough to install your system. Instead of aiming for the perfect, bug free system I would prefer to update the download page with a "known issues" section and a link to the last two previous install images. I think it might be saner to solve the problem this way; for example 3.6.5 might fix this issue but as the changelog is quite long its possible new bugs were introduced at the same time. In this particular case a simple workaround exists by adding "mem=3G" to your boot parameters.
I am sorry but I am using kernel 3.6.5 now, but no Tumbleweed and I have no such problems on three machines. The problem is not the kernel its self and I can read.
If you’d read the linked thread you’d have found out that the problem only occurs on certain AMD systems and not every systen - and that everybody who had problems with 3.6.4 has a working system again with 3.6.5 >:).