VPC Mac Fedora Core 3 install?

Does anyone know of a MAC OSX fix for the Fedora 3 install problem?
I've tried all of the "fixes" in this group, as well as the fixes at
Bugzilla but I still can't get Fedora Core 3 to boot. Most of these
fixes seem to be for the Windows version of VPC since they want me to
set up networking and use samba to access a shared folder on my local
machine. Sounds like Windows to me? Does anyone know of a MAC OSX fix
for the Fedora 3 install problem? Thanks.

In article ,
"dougjmac" <dougjohnson DeleteThis @mac.com> wrote:

 > Does anyone know of a MAC OSX fix for the Fedora 3 install problem?
 > I've tried all of the "fixes" in this group, as well as the fixes at
 > Bugzilla but I still can't get Fedora Core 3 to boot. Most of these
 > fixes seem to be for the Windows version of VPC since they want me to
 > set up networking and use samba to access a shared folder on my local
 > machine. Sounds like Windows to me? Does anyone know of a MAC OSX fix
 > for the Fedora 3 install problem? Thanks.

I haven't tried Fedora 3 yet, but I did solve my problems installing
Fedora 2 on VPC 7 Mac. I will be trying Fedora 3 shortly.

1. After installation, I got "An unrecoverable processor error has been
encountered" every time I rebooted. To solve this, I booted the
recovery CD, did a 'chroot /mnt/sysimage', then rebuilt the kernel,
changing the processor type from Pentium-Pro to Pentium-MMX (one step
down). This was successful in creating a bootable kernel with the
kernel source in /usr/src/linux-2.6.5-1.358, as well as a freshly
downloaded 2.6.9 kernel source. Building the kernel did take a long
time. Obviously, to build a new kernel you need to have installed the
kernel source and compiler tools.

2. The ethernet interface wouldn't come up. Attempts to reference eth0
resulted in DEVICE NOT FOUND and similar errors, byt it showed up in
hwconf. In /etc/modprobe.conf, I changed 'alias eth0 tulip' to 'alias
eth0 de2104x'. Either a reboot or a 'modprobe eth0' then brings the
eth0 interface online (it shows up in ifconfig).

3. Iptables shutdown script frequently hung forever unloading one of the
modules. The modprobe command was 100% CPU bound. I haven't solved
this one, but worked around it by changing /etc/init.d/iptables to set

IPTABLES_MODULES_UNLOAD="no"

instead of the current "yes" so that it doesn't attempt to unload the
modules.

Without the network up you can still get files into your session from
the outside. Create a new VPC disk using VPC Disk Assistant. If you
double click on it, it will mount on the desktop as read/write. You can
drag files to it. When done, unmount it, assign it to your VPC Disk 2,
and boot. The only caveat is that you can not have it attached to an
active (or saved) VPC session and on the Mac desktop at the same time.

Wes