Fedora4 Installation issues

erd.firstapex · 02-20-2006, 12:35 AM

Hi guys!

I have got new System with the following configuration.
CPU: P-IV 2.8GHz
MainBoard: MSI 915G Combo MS-7058
HDD: Seagate SATA 120GB
RAM: DDR2 1GB
DVD: Sony DVD Writer

Iam trying to install the Fedora4 on this new system, It is giving the following problem:

Kernel panic - not syncing: Attempted to kill init.

I could not understand the problem is with RAM or HDD or With Mother board.

If any body has any solutions please let me know @ erd.firstapex@gmail.com

with regards,
Chandu

exvor · 02-20-2006, 05:28 PM

Does it give you this error when loading from the installation media ? or after its installed ?

erd.firstapex · 02-22-2006, 03:08 AM

It has happened While installing.
But using the same media (4cd), 3 successfull installation are done on different machines without ant issues.

I can eliminate the SATA HDD from my doubts. Because i tried with different ATA Disk on which I have already done linux installation.

It gives KERNEL PANIC Error messages soon after I hit Enter to install the linux.

Now Iam doubting only on MSI Mother board. My board code is MS-7058 for 915G Combo chipset Implementation.

Any help is appreciated.

Chandu.

bjs · 02-23-2006, 09:39 PM

Interesting. I am getting the EXACT same issue..

I have tried loading Fedora Core 4 on my PC with several different sets and types of install media and have run into the same problem each time.

I see the Fedora splash screen, I press enter to install in graphical mode (text mode causes the same error) and I get a black screen with white text. Highlights of which are as follows.

Tword the top it says

Kernel Panic - not synching: Attempting to kill init!

The very last line reads

[<c01012b1>]Kernel_Thread_Helper+0x15/0x14

and there it freezes

I thought it might be the install media, but all discs work fine on my wifes PC.

My machine is a fairly cookie cutter custom job. AMD XP2800 processor, gig of ram, nVidia 6800 vid card..

bjs · 02-23-2006, 09:46 PM

another note, based on your other post..

my motherboard is a MSI motherboard as well.

bjs · 02-23-2006, 09:57 PM

a gentleman on another thread got me the answer

type "garbage" at the prompt (without the quotes)
then when it reprompts, just press enter

wpg9210 · 03-04-2006, 06:53 AM

Im at a loss, garbage at the install prompt or what? it say failed to recognize kernel image garbage, I don't understand what prompt.

dave-a-mbs · 03-20-2006, 07:54 PM

Kernel panic - ttempted to kill init! - same problem
I'm using an MSI board also, SATA disabled or not, no difference. I've tested several clean installs -

My last lines are

Call Trace: c01bd14c probe_hwif [kernel] 0x27c (0xdffb9f54)
[<c01bdc28>]
ideprobe_init [kernel] 0xb8 (0xdffb9fd8))
[<c01050535>] init [kerne] 0x13 (0x0ffb9fd8))
[<c0105040>] init [kernel] 0x0 (0xdffb9fe0>))
[<c010742d>] kernel_thread_helper [kernel] 0x5 (0xdffb9ff0))
Code: ff 50 10 eb d0 eb 0d 90 90 90 90 ... 90
<0> Kernel panic attempted to kill init!

This has been a consistent behavior with several versions of Red Hat and Fedora - although the addresses may be different with each.

It crashes the same way whether I use a floppy or boot from HDD, although the latter is faster.

Browsing the posts suggests to me that it's a problem with the MSI - If we can build a case against them, maybe MSI would develop a patch?

dave

wpg9210 · 03-21-2006, 07:18 AM

I had a few problems related to this issue, in both mandriva and fedora 4. What seemed to fix it is to use linux -noapic when installing, also disable apic in the system bios.

Bill

Rian8605 · 04-02-2006, 04:22 PM

...........

jrocos · 06-05-2006, 06:37 PM

Quote:

Originally Posted by Rian8605

i am having the same problem with FC4...im installing it on a server (2 AMD 250's, 3 Gigs ECC Ram, 2 Sata II 67GB harddrive (hardware RAID 1), Tyan Mobo)

I have been looking in other forums and they say its because FC4 installer "forgets" to name the mount points...and that if you partition manually it will fix it...

in my case, i can do a full install then hit reboot. everything boots fine..but the next time i restart it (no matter how i set up the partitions) i get the following:

mkrootdev: label / not found
mount: error 2 mounting ext3
ERROR opening /dev/console!!!: 2
error dup2'ing fd of 0 to 0
error dup2'ing fd of 0 to 1
error dup2'ing fd of 0 to 2
switchroot: mount failed: 22
Kernel panic - not syncing: Attempted to kill init!

kinda looks like my problem is a little bit different than yours?

Its funny too..i installed it from the same disk and had it running for atleast a couple of days..i could shut it down or restart or whatever...then i let it sit for a week...and now this!

Can anybody help?

I having the same problem, and it looks like alot of other people
are as well. I am really in a fix because I can't use linux at
all since there are no other bootable kernels after the installation of FC4. Have you tried to go through manual partioning? I, as yet, have not. If the root=LABEL=/ is replaced by root=0x804 or root=/dev/sda4 it still doesn't work, and I am sure that this is the right device.

jrocos · 06-06-2006, 11:29 AM

I found that the problem with not finding the root device and getting the panic is fixed by doing the FC4 install as an INSTALL and not an UPGRADE.
I found that when you get to the part where you are using Disk Druid, you label the root device (in my case /dev/sda4) as "/".

It believe the partition was labeled this in the past (FC2) so the upgrade somehow seems to have stripped the labels off of the devices. When I did this the root=LABEL=/ line on the kernel line will cause the booter to find it. I had no success by setting root to anything else before.

sandeshavadhani · 06-18-2006, 08:18 AM

I have a fedoro core 4 cd images (4 disk images).I want to convert it to one DVD .Can anyone help??? please...

jrocos · 06-18-2006, 04:21 PM

I wasted a week messing with FC4 -- very bad release.

I suggest you download FC5 and save yourself some trouble.