VM Ware

First off I would like to say awesome job on PC BSD, I really like what I see so far I am not a big *nix fan to begin with I want to use my computer, not configure it all the time :P

Now to my question. I havePC BSD installed on a VmWare 5.0 machine within Windows XP Pro, everything seems to be working but I am stuck in 800x600 , is there anything I can do to get a higher res in VMWare?


Thank You for your time

[sblevin]

I can't get the VMWare tools to reliably install - so here's what I do

/etc/X11/XF86Config

find the line starting with "Modes" in Section "Screen" and change it to


Modes "1024x768" "800x600" "640x480"


That will give you 1024 max res easily - to get higher than that you have to alter the


Section "Monitor"
Identifier "Monitor0"
HorizSync 31.5 - 48.5
VertRefresh 50.0 - 90.0


That is the default setting and I don't think it will allow a res higher than 1024.


***WARNING***
Everyone says that entering the wrong HorizSync and VertRefresh rate can break your monitor***

I'm not going there - sounds like "you need a screensaver or your screen will get pictures burnt on it" - well, 10 years or more ago perhaps........

I just don't want to get blamed for it : )

I edited my REAL settings in which I got from my monitor manual (or an online search). I am lucky, this is not a rebadged monitor so I know what it actually IS - not just Dell or HP or something stupid.

My monitor is a NEC Multisync FE950+. When I got the specs I edited my Section "Monitor" to be:


Section "Monitor"
Identifier "Monitor0"
HorizSync 30.0 - 96.0
VertRefresh 50.0 - 160.0
EndSection



and my Modes to be:

Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480"



There! Now I have to push my face up against the screen to see ANYTHING it's all so small : )

The only thing I have to do (like to do) is wait till X starts before switching VMWare fullscreen, otherwise the X display does not fill the screen 100%.

The VMWare tools would be nice to get working properly, but I simply don't want to spend any more time frigging around with them. They used to actually BREAK XF86Config.

My complete XF86Config file looks like this: (Probably won't work on yours just because of the CUSTOM sync and refresh rates that are specific to my monitor)


Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection

Section "Files"
RgbPath "/usr/X11R6/lib/X11/rgb"
ModulePath "/usr/X11R6/lib/modules"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/bitstream-vera/"
EndSection

Section "Module"
Load "extmod"
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "Auto"
Option "Device" "/dev/sysmouse"
Option "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection

Section "Monitor"
Identifier "Monitor0"
HorizSync 30.0 - 96.0
VertRefresh 50.0 - 160.0
EndSection

Section "Device"
Identifier "Card0"
Driver "vmware"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Modes "1280x1024" "1024x768" "800x600" "640x480" "320x240"
EndSubSection
EndSection

[Solarin]

***WARNING***
Everyone says that entering the wrong HorizSync and VertRefresh rate can break your monitor***


This is true actually. Although not for most modern monitors. Where older ones would just break, modern ones will cut out to protect themselves.

Downside is that you wouldn't be able to see anything on that monitor until you fixed the values :shock:

Solarin

[antik]

***WARNING***
Everyone says that entering the wrong HorizSync and VertRefresh rate can break your monitor***


This is true actually. Although not for most modern monitors. Where older ones would just break, modern ones will cut out to protect themselves.

Downside is that you wouldn't be able to see anything on that monitor until you fixed the values :shock:

Solarin

most good monitors says that "mode not supported" if you lousy monitor is on fire that means you have to buy new one anyway...

[sblevin]

***WARNING***
Everyone says that entering the wrong HorizSync and VertRefresh rate can break your monitor***

I used to have an old monitor, and when I cranked up the refresh rates too high it would sound like a dozen bats screaming hysterically while scraping their tiny fingernails down a long sheet of aluminium.

That was the warning sign I used to go on : )

Thanks for the info, it worked great well once I read about using su in a console window and had rights to edit the file ....... :wink:

I do have 2 more questions though. Is there a way I can login to x (KDE) as root and is there a command to stop the x server and drop to a CLI within x?




Thank you

[sblevin]

1) Is there a way I can login to x (KDE) as root?

I dont think so - but you can run any app as root by using the Run Program dialog (start menu or right click on the desktop) and there is an OPTIONS button - try that - I use it all the time to run graphical programs as root.

2) and is there a command to stop the x server and drop to a CLI within x?


You can prevent X from starting automatically this way:

http://www.pcbsd.org/forums/viewtopic.php?t=622

[Solarin]

If you press Ctrl + Alt + one of the F keys you'll be able to switch to a CLI, although X is still running.

F1 - F8 are ttyv0 - ttyv7 (CLI)
F9 is your KDE session.

So use Ctrl + Alt + F1 to switch to a CLI, then Ctrl + Alt + F9 to get back to KDE for example.

Hope that helps,

Solarin