I downloaded the latest version of Yoper a couple of days ago and burned the iso. When I tried to install it on my P4 machine it starts up, runs a few seconds and then comes up with an error message and locks. The message was something about kernal panic.

Does anyone know what the problem is here? The machine is a P4 3.0 ghz with 2 gigs of ram. Using a P4G800 asus mb and 120 gig hard drive.

the kernel provided may be broken...
try pasting the whole error here

I tried two different versions and get the same results. The full message is:

Code: 8b 46 dc 8d 48 6c....goes on and on and then
<0>Kernel Panic: Attempted to kill init !

As the install disks worked on my Compaq laptop and do not give the error on my amd desktop I figure it has to be some conflict with Yoper and intel or something.

I rather suspect the iso/CDROM to be broken

Are you saying the iso is bad? I downloaded it from the one of the ftp sites shown here in the usa. Matter of fact I downloaded it twice to be sure and I also used an earlier version that I had installed on my laptop which I know works.

Or are you saying that there is comething wrong with the drive I am using to load from? It is a brand new drive only about a week old that works just fine with everything else...

The fact that the iso worked on my laptop and it also works on my amd powered desktop leads me to believe there is some kind of conflict between yoper and my P4 3.0 intel system. It can't be lack of ram as I have 2 gigs ram. Does yoper not like hyperthreading possibly? Any other ideas?

Well you could always try disabling hyperthreading in the bios just to make sure that isn't the conflict. I dought it but you never know with computers.

Hi James

As I remember there is an option to check the file integrity of your install CD in the very start of the installation process. Perhaps you could try that, just to rule out the possibility of an borken ISO. Otherwise, you could try removing some of your RAM, as I seem to remember that there can be troble for the kernel to address such an high ammount of RAM (I think 1GB is ok). Again this is of course not a permanent solution, just to try and rule out possible problems.

Regards
Janus

Kernal panic ?

I rather suspect that your machine P4 3.0 ghz with 2 gigs of ram is unsupported. The distro yoper can't running installation with 3.0 ghz can cause that kernel as shown

Code: 8b 46 dc 8d 48 6c....goes on and on and then
<0>Kernel Panic: Attempted to kill init !
I suggest bellow 2.8 Ghz it would load successfully..
About 2 GByte RAM and 120 gig hard drive is support for all distro....

Where did you get that from? I say the hardware is probably faulty. Attempting to kill init usually means faulty memory. Either than or the kernel with which Yoper shipped for some reason has been compiled not to support so much memory. Either than or something is fishy with the system...

Do any other distros run OK on this same system? Does Windows run OK on this system? If so then it's probably not the memory, and most likely the kernel with which Yoper ships.

In any case, try taking out some of your memory (bring it down to 1 gig) and see if you see the same error message.

However, the most likely cause of your troubles is probably a currupted download. Use a tool like MD5Summer to verify the "fingerprint" of your ISO file, and compare it to the MD5 checksum (fingerprint) posted on the Yoper download web site. If they don't match exactly your ISO is corrupted and using it to install Yoper will only lead to trouble such as this. In this case, it's best to download it from scratch again.

I am successfully running Yoper v2.1 on a P4 3.0 GHz with Hyperthreading. It installed correctly the first time and I've had no problems. Don't mean to rub it in, just ruling out the HT argument.

My first suspicion would also be to check your ISO before installing. Any number of things could go wrong even if you got the correct iso and burned it correctly on a new perfectly functioning burner. And it can't hurt, just takes a little time. And once done, at least you know what the problem isn't.

One more note:
http://www.yoper.com/forum2/index.php?showtopic=4009

This guy had some strange behavior with multiple CD-ROM drives that caused "kernel panic," take a look.