SuSE 10.0 boot problems with CPU changed 2351

On Sunday 27 August 2006 13:17, composlinuxmisc stood up and addressed the mbuttes incomp.os.linux.miscas follows...:

Most likely the latter, I'd say. I don't see why you would need to reinstall an entire distribution only because a CPU has been swapped for another one, especially if the new CPU is of the same brand and generation as the original CPU.

In your case, it wouldn't even make a difference if you were running Gentoo - which is entirely compiled for your specific hardware, rather than to go with a generic "one size fits all" binary code for everything in the distribution.

As a sidenote, I've known entire installed distributions to work when the hard disk was simply moved to another computer, which included moving the disk from an Athlon XP based machine to a Pentium III. This variety of target computers is exactly why distribution vendors typically compile a "one size fits all" distro - this is of course less so forx86-64,since there are only two major types of CPU's in this clbutt: the Intel EM64T and the AMD64 platform.

Most stock distribution kernels forIA32have been compiled to work on a generici586or perhaps ai686,and they contain enough genericx86code to keep the kernel happy whether it is running on an Intel Pentium 4 or on an AMD K-6. The Athlon XP is ani686and should therefore be able to handle any generici586ori686stock kernel and distribution. I believe SuSE is compiled asi586code.

There is a good reason as to why overclocking is generally discouraged, and you are now experiencing that reason... Most likely you've burned more than just your CPU...

With a bit of luck, it'll only be the memory modules, or perhaps you've accidentally disconnected something or knocked something out of the socket while you were replacing the CPU, but I suspect a lot more damage has been done... :-

While it is true that Intel CPU's can take less heat than a comparable AMD CPU, an Intel CPU has an overheating protection, and most recent Intels all have thermal throttling. As far as I know, AMD's don't have that and will allow you to toast them.

Intel nags and freezes, but AMD goes all the way until it burns up. And that's apparently what happened to your original CPU. However, imagine what such a thermal torture does to the rest of the chips...

I myself have only had one machine going "black screen" on me before - even the POST information didn't appear on the screen - and that was because the machine had suffered a lightning strike through the cable modem. Needless to say that most of the hardware was toast, all except for the floppy drive, the Adaptec 29160 SCSI adapter, the IBM SCSI hard disk and the Plextor SCSI CD-RW device. A true testimonial of quality for the SCSI stuff - I'm actually using all of it in this very machine now, after it was all tested electronically - and it's already been running without any problems in this machine here for about two years now.

On the other hand, the Intel Pentium III and the i810 chipset-based Chaintech motherboard, the Chaintech videocard, the Hitachi monitor - which was in standby mode at the time of the strike - the Creative Soundblaster and the Iomega 2 GB Jaz - which was also SCSI, but Jaz drives were never really that good - were all waste.

Computers are very sophisticated pieces of hardware, and they're not exactly given away for free in a pack of cookies either, so don't mess with the clock speeds anymore... ;-)

Sorry for the lecture, but I guess it was necessary... ;-)

-- With kind regards,

*Aragorn* (registered GNU-Linux user #223157)