SuSe 8.2 EIP install problems

Ulysses_93674 · 06-05-2003, 08:22 AM

Hello, Obviously I'm new to Linux, so I'm not sure how difficult a problem this is. When I try to install SuSE Pro. 8.2 on an old
Pentium 133/128Mb Ram system (which meets the req. incidentally), I get a message during the Kernel unpacking:
Bad EIP value.
<0> Kernel Panic: Attempted to kill init!

Of course there's other information if needed. I should add that I had the same problem with Mandrake but when I tried an install of Red Hat 7.1 it went without a flaw. Maybe it's to do with the newer kernel?

I should add that I really need to get this machine working, hopefully with SuSE.

Regards
Ulysses_93674

P.S. I just tried a Slackware boot disk of the same kernel type-it loaded perfectly. As SuSE and Mandrake are supposed to be easy to use, have they added something really helpful I don't need?

Ulysses_93674 · 06-05-2003, 02:57 PM

Right, I just tried older boot disks from the SuSE site to see if they worked:
7.1 YES
8.1 YES
8.2 (Current/mine) NO!!

And no it's not the kernel version.

carlywarly · 06-06-2003, 01:39 AM

Have you tried the other install options, safe install etc?

Ulysses_93674 · 06-06-2003, 07:22 AM

All of the options, also tried a bootdisk for Red Hat 9.0 and that had the same problems as SuSE and Mandrake. I'm guessing that Slackware and Debian et al because they are simpler during install i.e no reeeaaallly helpful additions to the kernel, they'll work ok. They have to have added something to 8.2 over 8.1 that's causing a conflict.

Ulysses_93674 · 06-08-2003, 08:01 AM

Right, after taking it all apart and doing repeated reboots I found the problem, namely the on board IDE controllers (yes I know). If one, say the primary is on-no problem, but if you enable both in the BIOS-kernel panic. So therefore if you have a similar problem try setting the Master/Slave and running your equipment off one of the IDE sockets only (after disabling the other in the BIOS natch). I still don't know if it's my hardware or the kernel, but to be honest it's probably both, however here are the facts:

The newer kernel, the larger one i.e. distro. bootdisk, won't load with both on, but will if one's disabled.

The newer kernel will load if it's a simpler one i.e. like Slackware's
bare.i-IDE support one, even if both are on.

The problem is NOT distro. specific

All the older kernels, right up to the last major releases work fine regardless of the settings.

Regards
Ulysses_93674