我使用VMWare 安裝Fedora Core 2卻近不了圖形介面

[巫拉]

是的是的，boot：linux vdso=0 按Enter即可。^^
下面是原文解說：
After a bit of tweaking this evening, I got Fedora Core 2 Test 3 running under VMware 4.5.1. Here's how.

★Host Configuration:
Toshiba Satellite Laptop
512MB RAM
40GB Internal HD
Windows XP Pro SP1 with all updates
VMware 4.5.1

★Guest VM Configuration:
Fedora Core 2 Test 3 (downloaded .iso files)
"Other Linux 2.6.x Kernel"
256MB RAM
4GB HD (/dev/sda1 = /boot, /dev/sda2 = /)
1GB HD (/dev/sdb1 = <swap>)
Installation

1.Boot installation CD.
2.At boot: prompt, type "linux vdso=0". This is very important, otherwise VMware will crash.
3.Install as usual, configure however you like. You'll need to ensure "vdso=0" is set in the "advanced boot configuration" options.
4.If you just reboot at the end of the install, the system will "freak out" a bit trying to start the x server. You can avoid this by editing the boot line (at the Fedora grub splash screen) and appending a 3 to the line.
5.Boot.
6.Unpack the VMware Tools tarball, then apply the patch below (vmware-fc2t3.patch) to vmwares-tools-distrib/bin/vmware-config-tools.pl.
7.Install VMware tools. Use the defaults for all questions, except say NO when asked if you want to compile a vmhgfs module. It doesn't seem compile with the 2.6 kernel headers.
8.Reboot, and enjoy.

Notes:

1.Thanks to Daniel Arial at VMware for the "vdso=0" tip. I would have never found this on my own!
2.Don't take this patch or these instructions too seriously. I just came up this this while hacking around tonight. All of the usual disclaimers apply. Your mileage may vary. I am not responsible for data loss, unusual hair growth, or any other rude behavior exhibited by your computer. You have been warned.
3.In my experience, Fedora Core 2 Test 3 is extremely slow under VMware 4.5.1 (much slower than FC1). It takes about 11 minutes (!!) from the grub splash screen to the GUI login prompt. This is probably in large part due to the eleventy-bazillion services installed by default.
4.I've noticed some bizarre problems with initialzing the guest keyboard and mouse. Apparently, if the VMware VM doesn't have focus while the guest OS is booting, there is a non-zero chance the keyboard will not initialize correctly. Or, the failure could just be completely random; I don't know yet. FWIW, I've never seen this with other guest OS's, only FC2T3.

轉自：http://kerneltrap.org/node/view/3097