Hi all,

I am a relative newbie when it comes to Linux, so please go slowly with
me

I have (apparently successfully) installed the Fedora 2.6.9-1.667
distribution into a Virtual PC. I say "apparently successful" because
the entire (graphical) installation process completed without incident.

This uses grub as the boot-loader.

(1) The start of the boot process (including the first of the errors)
looks something like this :

Booting 'Fedora Core (2.6.9-1.667)'

root (hd0,0)
Filesystem type is ext2fs, partition type 0x83
kernel /vmlinuz-2.6.9-1.667 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
[Linux-bzImage, setup=0x1400, size=0x155da5]
initrd /initrd-2.6.9-1.667.img
[Linux-initrd @ 0x7ef3000, oxec00e bytes]

Uncompressing Linux... Ok, booting the kernel.
audit(1138175330.804:0): initialized
isapnp: checksum for device 1 is not valid (0x80)
isapnp: checksum for device 2 is not valid (0xbe)
....

(2) Further along the boot up process, I am getting multiple errors of
the form :

/etc/init.d/functions: line 381: 542 Segmentation fault ........

(3) It culminates in errors of the form :

INIT: Id "x" respawning too fast: disabled for 5 minutes

where x appears to be any number between 1 and 7.

Any help appreciated.

regards,
Andrew Fortune

<mathman@ains.net.au> wrote in message
news:1138143108.316545.116670@g44g2000cwa.googlegr oups.com...
>
> Hi all,
>
> I am a relative newbie when it comes to Linux, so please go slowly with
> me
>
> I have (apparently successfully) installed the Fedora 2.6.9-1.667
> distribution into a Virtual PC. I say "apparently successful" because
> the entire (graphical) installation process completed without incident.

2.6.9 is the default kernel for Fedora Core 3. Why aren't you using Fedora
Core 4? And is there any reason not to do all the updates and get it up to
at least the published 2.6.11 kernel that FC3 updates provide?

"Virtual PC" is a Microsoft product. That's.... asking for Linux not to
work, since Microsoft support for any Linux is asking for pain, or even
asking for them to deliberately break Linux compatibility. I'd return it
immediately and buy VMWare with the money, if you can. VMware is generally
better.

> This uses grub as the boot-loader.
>
> (1) The start of the boot process (including the first of the errors)
> looks something like this :
>
> Booting 'Fedora Core (2.6.9-1.667)'
>
> root (hd0,0)
> Filesystem type is ext2fs, partition type 0x83
> kernel /vmlinuz-2.6.9-1.667 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
> [Linux-bzImage, setup=0x1400, size=0x155da5]
> initrd /initrd-2.6.9-1.667.img
> [Linux-initrd @ 0x7ef3000, oxec00e bytes]
>
> Uncompressing Linux... Ok, booting the kernel.
> audit(1138175330.804:0): initialized
> isapnp: checksum for device 1 is not valid (0x80)
> isapnp: checksum for device 2 is not valid (0xbe)
> ...
>
> (2) Further along the boot up process, I am getting multiple errors of
> the form :
>
> /etc/init.d/functions: line 381: 542 Segmentation fault ........

Uh-oh. This is not good. Take a look at what that line does.


> (3) It culminates in errors of the form :
>
> INIT: Id "x" respawning too fast: disabled for 5 minutes
>
> where x appears to be any number between 1 and 7.
>
> Any help appreciated.

If you have a working console for the system, put it in runlevel 3 by
logging in as a root user or by using sudo to get root privileges, then use
"/sbin/telinit 3" to change the runlevel, then run "system-config-display"
to reset the X settings for whatever the Virtual PC might be able to
support.

I hope that helps!

mathman@ains.net.au wrote:
> Hi all,
>
> I am a relative newbie when it comes to Linux, so please go slowly with
> me

All my VM experience is with VM under Linux, but some of these things
are undoubtedly similar to the problems I've seen.
>
> I have (apparently successfully) installed the Fedora 2.6.9-1.667
> distribution into a Virtual PC. I say "apparently successful" because
> the entire (graphical) installation process completed without incident.

That's a good sign. At least the virtualization was good enough to avoid
comment.
>
> This uses grub as the boot-loader.
>
> (1) The start of the boot process (including the first of the errors)
> looks something like this :
>
> Booting 'Fedora Core (2.6.9-1.667)'
>
> root (hd0,0)
> Filesystem type is ext2fs, partition type 0x83
> kernel /vmlinuz-2.6.9-1.667 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
> [Linux-bzImage, setup=0x1400, size=0x155da5]
> initrd /initrd-2.6.9-1.667.img
> [Linux-initrd @ 0x7ef3000, oxec00e bytes]
>
> Uncompressing Linux... Ok, booting the kernel.
> audit(1138175330.804:0): initialized
> isapnp: checksum for device 1 is not valid (0x80)
> isapnp: checksum for device 2 is not valid (0xbe)

I don't have a copy of FC3 handy, but this is probably not a show
stopper unless your video card is ISQA rather than PCI (or simulated
ISA). It means the check (firmware?) of the device failed. I suspect
that the kernel used for the install is not the same one you are
booting, or is configured at runtime to use other devices or modes.
> ...
>
> (2) Further along the boot up process, I am getting multiple errors of
> the form :
>
> /etc/init.d/functions: line 381: 542 Segmentation fault ........

That appears to be the failure() procedure, and it may have written more
information in a log file.
>
> (3) It culminates in errors of the form :
>
> INIT: Id "x" respawning too fast: disabled for 5 minutes
>
> where x appears to be any number between 1 and 7.

That could be any of several things, 1-6 are the virtual terminals of
the console, the getty program is probably messed up, and since it has a
"restart" in /etc/inittab it get created and dies until the init process
gets tired of it and prints the message you see.
>
> Any help appreciated.

Let me offer a thought which may address "poor virtualization" issues...
when you get the grub prompt, immediately press the ENTER or SPACE key
(forget which is used in FC3) and you should see the list of available
kernels (may only be one, not a problem). Then press 'a' to edit the
boot options. You should see the cursor at the end of the options line,
type a space and the option "noacpi" and hit enter.

That prevents a lot of detailed probing of the hardware, which is
probably emulated incorrectly. I suspect the virtualization you chose
was not tested with Linux, or was tested but not fixed.

One more thought: google "colinux," which is Linux booted from a file
(or CD) which uses the Windows drivers but really runs Linux. Totally
neat stuff if it works for your version of Windows. If that provides the
functionality you need it may be an alternate solution.
>
> regards,
> Andrew Fortune
>


--
bill davidsen
SBC/Prodigy Yorktown Heights NY data center
http://newsgroups.news.prodigy.com

Thanks, Bill. The 'noacpi' parameter didn't seem to make any difference
to me, so I'll give colinux a try.