In my particular problem, I installed Slackware without a hitch but upon first reboot, the kernel would panic and complain about the bus error your mentioned in your first post. If your install doesn't complete in the first place, this isn't gonna help you out.
On most linux distributions, kernel modules will be installed under
Code:
/lib/modules/<kernelVersion>/
On my system the agpgart.o.gz was located at
Code:
/lib/modules/2.4.31/kernel/drivers/char/agp/agpgart.o.gz
To stop that module from loading on boot I (in a very sloppy and lazy move) simply renamed it to
Code:
/lib/modules/2.4.31/kernel/drivers/char/agp/AGPGART
Of course, to be able to do that, you'll have to get the machine to boot and mount the hard drive. There are a million ways to go about that, but I used a Slackware 10.2 install CD.
After booting off the CD, Slackware asks you to choose a keyboard setup. The defaults it offers are correct for the Parallels VM.
Then Slack will tell you that you can login as root. Do so. All you have to do is enter
at the login prompt.
You'll notice that you've got a pretty basic shell. The following sequence of commands is what I used to complete the task. Keep in mind that your partition scheme may be different than mine. My setup is
Code:
/dev/hda1 Linux Swap
/dev/hda2 /boot
/dev/hda3 /
Anyway, on with the commands.
Code:
mkdir disk
mount /dev/hda3 disk
mv disk/lib/modules/2.4.31/kernel/drivers/char/agp/agpgart.o.gz disk/lib/modules/2.4.31/kernel/drivers/char/ago/AGPGART
umount disk
reboot
Keep in mind that those exact commands may not work on your system. Your kernel modules could be installed in a different place because, for instance, you could be running a different kernel version, or Suse could install them someplace different.
After you reboot, you'll probably notice at least one error in the dmesg output saying something about agpgart failing to load. The boot process should proceed.
I guess if you really wanted to be serious about fixing the problem the "right" way, you'd modify the appropriate config files or compile your own kernel. I've been playing with my VM in the "lazily renamed kernel module" state for a few days now and everything seems to be just peachy. In fact, I'm making this post with my VM now.
To answer your question about what media I used, I used a Slackware iso file as my media. If you can't get your choosen installer to work, you can always switch to Slack. It's the best distro anyway