I have SuSe 11.3 installed on the same system and have run it overclocked for quite some time. I have run mprime for 12 hours and the the system does not over heat and is as solid as a rock. I discovered that I had to remove the overclock whilst installing 12.2. What is distressing is that now I cannot get 12.2 to boot while overclocked. I can still boot the 11.3 system fine with the overclock (it is in a separate partition.) I think that the problem is related to the “fast boot” feature? How do I turn this off? Or is there something else that prevents SuSe 12.2 from booting on an overclocked system?
Thank you for your responses and I apologize if this has been asked before. I searched the forum and didn’t find this exact subject. (If I missed it, please just direct me to where it is discussed.)
I switched from GRUB2 to GRUB and added another boot option. I cloned the existing 12.2 entry and removed the trailing commands (as they didn’t exist on the 11.3 boot command that DOES work). I removed " splash=silent quiet showopts". I didn’t expect it to work (and it didn’t). Still boots normal, but hangs on the overclock boot.
I should also include the message I got from trying to install while overclocked. (I had to write it down on paper, so it may not be complete.)
Starting udev… udevd[123]: RUN+=“socket:/org/kernel/dm/multipath_event”
support will be removed from future releases
Please remove it from /etc/udev/rules.d/71-multipath.rules
and use libudev to subscribe to events
I have looked at this file and sure enough it seems to contain the offending line.
Looks like you might be correct. I backed the overclock off by 2.5% and it started booting. Unfortunate that I will have to revailidate this system all over again and lost valuable clock cycles in the bargain. You would think that stable hardware is stable. I will load sensors, gkrelm and mprime and get to work. Thanks for the reply.
Here is the tale of the tape, for anyone who might be interested.
It is a issue of timings and how instructions are called. Why do you need to over clock, that hardware is quite fast anyway or are you just a speed freak
Well, I did run in the same issue as kaptdeath](http://forums.opensuse.org/members/kaptdeath.html) Thanks for sharing this issue. :good:
Reduction of the OC by 1 step (-4,6% in my case) made it stable. It must be something in the new kernel but hey I can live with that.