This is really important, since i'm horrendously stuck in getting any updated Linux systems onto my box, so 500 points straightaway for real help.
Situation: Hardware is not too old, Pentium IV, 215 MB RAM, on latest AmiBIOS & so on . . . two harddisks, WD & Maxtor, each 80 MB, (more details if required)
There is a working SUSE 9.0 with kernel 2.4 series intalled on the first harddisk & backed up on the second harddisk.
Important to keep in mind with the following: The SUSE Linux 9.0, kernel 2.4 is working ok !! on the hardware concerned here, right.
My goal in present time is , to get an updated 10.0 SUSE Linux with 2.6 kernel series onto same box.
The installation went basically ok, though there are some packages of minor importance which didn't go in from DVD. Interesting is, i tried installation
a couple of times & with eeach try, the set of packages, that did not install, was different. I am talking about 2-5 packages out of about 1800.
Interesting: packages, that did not go in with one install, did go in with an other & vice versa.
YET, THIS IS NOT MY MAIN CONCERN,since failed packages which are not system dependant, I could install manually after boot.
PROBLEM: When install is finished SUSE installer goes for reboot, and then THE BOOT fails after the point where it says something like:
"This system has been setup" // then in the next line:
Init Panic: segmentation violation at 0xffffe420!
sleeping for 30 seconds"
Now, after that line, the system hangs completely (it doesn't wake up after 30 seconds)
& I have to reboot the machine. Whatever I have tried, I won't get over that point with the Init Panic: ............with that kernel 2.6 insttallation.
Why I put focus onto 2.6 kernel here:
I have a working 2.4 kernel system on the same hardware setup - no problem.
I tried to install other Linux distributions: (Mandrake 10.1, Debian Sarge, - with kernel 2.6 series - & they failed as well)
Now let's concentrate on this SUSE 10.0 and let's see how to fix it. I already put a service request to Novell, but
so far not a lot of help: They recommended to put "exec-shield=off" as a kernel boot option, which I tried, but did lead to the same
bummer- result. Maybe anyone of you has some more insight into this.
PS: When I do the memory test, which I can initiate under the GRUB shell, before boot, then I get report that tests on lots of RAM addresses produce an error.
First I thought, my memory (RAM) is corrupt, but how shall I explain that my SUSE 9.0 is working with the same RAM module flublessly ?