Linux had crashed my computer and the bios reset the settings to default so i had to re-OC. That happened after the latest kernel update.
Ran into an interesting problem. Here are my specs.
OS (Dual Boot): Windows XP Pro 32 Bit, OpenSuse 11 64 Bit.
Mobo: GA-n650sli-DS4
CPU: Core 2 Duo E6420 @ 3.0GHz
-Voltages/Settings are as follows-
–CPU Clock Ratio: 8X
–DDR2 Voltage Control: +0.2
–FSB Voltage: +0.1
–CPU Voltage Core: +1.325
—CPU Host Freq. 375.0Mhz
—Memory Freq. 750.0Mhz
Everything else is untouched. Ran prime95 ( 2 instances 1 for each core for 24 hours, with no errors in windows xp 32 bit. after i boot up in linux after a few secs it crashes. but windows runs fine…any clue as to why linux is doing that?
well, the point of me getting 64bit linux was that i wanted linux to read all my ram in the first place…plus i wanted to make use of my core 2 duo, if i get a 32 bit one that would just waste my time, i want to make the 64 bit one work…
I’m new to the forums, and thought I’d make my first post here.
I agree that in order to fully establish what the cause of your problem is with have to compare like with like.
However I note your point that your ultimate goal is to get a 64Bit SUSE OS onto your PC.
This leaves us with a bit of a challenge with regards to how we acheive these objectives with the resources you have available to you.
I can see two good options (there may be more).
Option 1.
Clock it back down and see what happens. (You may have already tried this, if so what was the result?)
Option 2. Grab a spare hard disk, or partition off room for a 3rd instalation. Obviously the spare hard disk is easier as you won’t have the hassle of configuring/sorting out boot issues, and there is less risk to your existing installs. Once you have a bit of space for an installation try 32Bit SUSE and see if it works. What would be interesting is to start the installation on normal clocking, then once installed overclock and see what happens. I suspect a change in frequency shouldn’t affect things at all but you never know.
Once you know the answers to the above you will have narrowed it down enough to get an idea as to where the problem is. If 32Bit works fine overclocked or not you know its 64Bit specific, if 32Bit falls over as soon as you overclock you know its SUSE specific.
>
> Hi,
>
> I’m new to the forums, and thought I’d make my first post here.
>
> I agree that in order to fully establish what the cause of your problem
> is with have to compare like with like.
>
> However I note your point that your ultimate goal is to get a 64Bit
> SUSE OS onto your PC.
>
> This leaves us with a bit of a challenge with regards to how we acheive
> these objectives with the resources you have available to you.
>
> I can see two good options (there may be more).
>
> Option 1.
>
> Clock it back down and see what happens. (You may have already tried
> this, if so what was the result?)
>
> Option 2. Grab a spare hard disk, or partition off room for a 3rd
> instalation. Obviously the spare hard disk is easier as you won’t have
> the hassle of configuring/sorting out boot issues, and there is less
> risk to your existing installs. Once you have a bit of space for an
> installation try 32Bit SUSE and see if it works. What would be
> interesting is to start the installation on normal clocking, then once
> installed overclock and see what happens. I suspect a change in
> frequency shouldn’t affect things at all but you never know.
>
> Once you know the answers to the above you will have narrowed it down
> enough to get an idea as to where the problem is. If 32Bit works fine
> overclocked or not you know its 64Bit specific, if 32Bit falls over as
> soon as you overclock you know its SUSE specific.
>
> Hope this helps.
>
> Rich
>
>
I have to agree with a previous poster… Linux pushes hardware harder BY
DEFAULT. Which means linux is NOT as tolerant of overclocked system as
windows is.
As designed, windows has enough bottlenecks to slow down hardware accesses
and prevent most hardware issues… ever run REGMON on a windows system? The
crazy thing accesses the registry 500-1500 times a second… this slows down
the processor and prevents signal propagation errors and other things which
are occur when you push a system past its electronic limits. Yes, there’s
some slop in the speed determination, but you’re likely already past that,
pushing for just one for frame.
Linux (not just SUSE) can make your ‘normal’ computer FEEL like it’s
overclocked, yes, this is subjective, but try it… linux against windows on
same hardware… linux will outperform windows.
If you want to go faster, buy better hardware. Or invest in a nitrogen tank
out back to cool the system. Trying to get 3 fps more on some game isn’t
worth smoking a processor or gpu.
I do not run OpenSuse 11 (64 bit), but I did install it but re-formated and installed OpenSuse 10.3 (64 bit) again.
The reason for the downgrade is that I had been protein folding and with the newer OpenSuse 11 the folding was slower, but it still worked just fine with no problems. Protein folding definitely stresses your CPU somewhat.
I have an Intel Q6600 overclocked on air to 3.015, on an Abit iP35 Pro motherboard. This machine has been running protein folding 24/7 for over ten months now without missing a beat, so perhaps it is more your hardware not coping rather than the operating system.
I used to run at about 10% overclocked all the time using:
in BIOS, turn off cool’n’quite (whatever your equivalent like speedstep)
in SuSE, set all the cpu freq policy & active scheme to performance, etc – or they will be fighting.
also had my fan set to run max all the time – if they get hot, mobo should auto shut it down.
I haven’t OCed in a long time as I have good cpus that give me enough at stock speeds. And, cool’n’quite with powersave works to perfection.