Re: Fedora core in vmware (From original poster)RE:1



Patser. wrote:
ken wrote:

Patser. wrote:
Hi,

I currently have fedora core 2 running in a vmware box on my
laptop but I have a problem with my console resolution.
When I try to change it with kernel parameters such as vga=
it just hangs and restart the xwindows of my host which is
SuSE Linux 9.3. Does anybody know how to safely switch the
resolution under vmware without hanging when I switch from
graphic mode to text console?

Thanx for the reply Ken, I guess I'll have a go with FC 5 some day. Currently I am now trying (don't laugh!) windows XP, which wil most likely even run on my toaster if I had one.. :P
Anyway I'll see what I can do with FC 5 or otherwise I'll try
some other distro.

There does appear to be a problem with the initial kernel for Tettnang.
It should not however crash "X" on your host machine. It did go blank
if you started vga=791 as soon as "X" started. If you boot to runlevel
3, or normal console resolution, and upgrade to the latest FC2 modules,
the problem does go away, at least with FC5 as the host. "X" will
successfully start under VMWare at kernel-2.6.10-1.771_FC2, it failed
under kernel-2.6.5-1.358, when vga=791 was set. I cannot speak to the
kernels in between. There is a newer kernel at fedorlegacy.org.

If you are using the console after going into "X",I don't think it will
be very useful. Though it doesn't crash, it has more problems. This
does not occur with FC5 under VMWare.

Ken


Why should I laugh? Running WinXP under VMWare is how I connect to work. They do not support Linux connections to work, and I need the Windows interface to do my job, well part of it, as I administer Windows and RHEL servers. Work pays for the licenses, such as VMWare Workstation for Linux and the Windoze license.

The kernel on FedoraLeagacy, kernel-2.6.10-2.3.legacy_FC2, behaves the same as the final kernel from Fedora itself. (It is the same behavior I have seen on a couple distros, even on real hardware. I have not bothered to find a way around it, as the versions I usually use do not behave this way, and I was not issuing vga=791 when I ran FC2. I think that started with FC4, though I have used it on RHEL 3 and 4 as well as CentOS 3 and 4.)

Ken
.



Relevant Pages

  • Re: Java problem
    ... VMware source shim to get it to compile, ... upstream kernel, where modules belong, not as a separate package. ... after all, one of the Fedora Packaging Guidelines, that there be no package ... kernel developers' fault and VMware's fault, ...
    (Fedora)
  • vmware sound
    ... kernel: i810_audio: DMA overrun on write ... I did a new install of the OS to Fedora Core 1. ... After running vmware-config.pl, I started vmware and reinstalled VMWare ... Controller ...
    (Fedora)
  • Re: Problem Installing VMware Tools in Fedora-9
    ... error message: "The directory of kernel headers ... of Fedora on VMware and never encountered a problem like this. ... VMware does not support Fedora because it considers it to ...
    (Fedora)
  • Re: Problem Installing VMware Tools in Fedora-9
    ... "The directory of kernel headers ... of Fedora on VMware and never encountered a problem like this. ... VMware does not support Fedora because it considers it to ... Downloading the Workstation version as we speak. ...
    (Fedora)
  • Re: VmWare Workstation and 2.6.8.1 kernel
    ... > back to vmware unfortunatly they do not provide support for demo user. ... thread because it suggests that VMWare can be run under a 64 bit kernel. ... I'll install the 64 bit version Fedora Core 3 on ... Linux, Windows 9x, Windows NT, Windows 2000, Windows XP ...
    (Fedora)