I have a Samsung 226BW Monitor, it’s native recommended resolution is 1680 x 1050, but my eyes are not what they were, and I have problems when running windows inside a VBOX at this resolution. VBOX effectively will not allow a lesser resolution than the host to run in the guest, so I can’t see text etc in some programs.
I decided after weeks of adjusting fonts dpi’s etc in both host and guest, that the simple way would be to reduce my resolution.
Now the monitor is 16:10 aspect ratio, so I found a list of 16:10 resolutions, and tried in YAST (saX2), to select a lower resolution, also at 16:10 ratio using the drop menu in YAST
I first selected 1440 x 900, clicked “test” and the res. changed BUT it changed to 1152 x 864 (= 13.3333:10 or 1.3333:1 ratio.) I tried again, but no mistake, openSuse REFUSES the 1440 x 900.
OK I will try 1600 x 1000, obviously this is 16:10…
But saX2 also refused to reset to this res., autoselecting instead 1280 x 960 (!!!) which is very different, and is also 1.333:1.
I have nVidia drivers, which have given no problems so far…
Can anyone explain in layman’s terms what is happening, and whether I can run these screen resolutions?
I would post my xorg.conf, but I do not know which of the following is “active”
Do you have the VBOX Guest additions installed ? I guess not. If you update VBOX the best thing is to uninstall the guest additions in Windows and then reinstall them via VBOX.
As it happens Knurpht I updated vBox about a week ago and the Guest additions upgraded smoothly as well, I asked around and it seems vbox can’t full screen at a lesser res than the host, if I adjust the XP screen res. (guest) the window appears in a tiny hole surrounded by black, If I fullscreen it it auto-adjusts back to the the largest possible res, ie just smaller than that of the host (openSuse).
Yes, you can enter them manually but you better make sure that whatever you enter is supported by the hardware. With LCD panels, anything other than the native resolution might look quite gruesome and put your eyes under much more strain than the native, although higher, res.
Hmmmm (strokes beard)
16:10 resolutions are NOT there, BUT 1680/1050=exactly 1.6
Whereas 1400/1050, on the list = 1.333:1 !!
I AM CONFUSED!
Where does xandr get its “ideas” from?
directly from the EDID of the monitor?
Or from the video driver?
or from xorg.conf?
I notice that in my
file:///etc/X11/xorg.conf.nvidia-post
, “Preferred Mode” is set at 1280x1024… 1280/1024 = 1.25:1…
Could it be that the monitor has been wrongly identified by nvidea, overwriting the CORRECT id by xorg.conf (??)(??)
Allows you to override what the NVIDIA kernel module detects is connected to your video card. This may be useful, for example, if you use a KVM (keyboard, video, mouse) switch and you are switched away when X is started. In such a situation, the NVIDIA kernel module cannot detect what display devices are connected, and the NVIDIA X driver assumes you have a single CRT.
Valid values for this option are "CRT" (cathode ray tube), "DFP" (digital flat panel), or "TV" (television); if using TwinView, this option may be a comma-separated list of display devices; e.g.: "CRT, CRT" or "CRT, DFP".
NOTE: anything attached to a 15 pin VGA connector is regarded by the driver as a CRT. “DFP” should only be used to refer to digital flat panels connected via a DVI port.*
Default: string is NULL (the NVIDIA driver will detect the connected display devices).
I guess this explains why nVidia-settings reports CRT-0 ?
Pretty daft IMHO, my gpu ONLY has a 15 pin VGA OUT! and IS nVidia.If I get a vga/dvi converter, would this overule do you thinks?
In other posts you’ve written about the resolution of your monitor. You were advised to use LCD@1920x1080. Here I see that the monitor is configured to be a Samsung with preferred mode 1280x1024. There’s definitely something going wrong and I think you’re trying to solve different things at the same time. Therefor I’m out.
Knurpht, I have never owned, borrowed, used or even considered using a monitor even capable of 1920x1080. As my eyes are bad I cannot even imagine a scenario where I would need or even want such a resolution (well maybe if I wanted to put my computer output to a wall mounted 2 metre wide television)
You must have mistaken me for someone else, or there has been a major typo somewhere!
xxx
Wakou.
I owe you an apology. Think it was indeed a thread by another poster, where you just replied. My mistake. So, I’m back in.
To help you out:
In your xorg.conf there are no Mode lines above 1280x1024. The monitor also has a Preferred Mode of this value.
What I suggest is that you go into runlevel 3 (logout, Hit Ctrl-Alt-F1, login, do " su -c ‘init 3’ "), next do:
su -c ‘sax2 -r -m0=nvidia’
This starts sax2 to create a new xorg.conf. In the first screen pick ‘Change Configuration’. You will enter the sax2 interface. The video card is shown, the monitor and the preferred resolution. If all is shown correctly, save and exit. Save and exit. You can now type ‘startx’ to see if things have improved.
If not, repeat procedure above, instead go into monitor properties and either:
pick LCD as the manufacturor, resolution from the list on the right, I usually try lowest refresh rate first. Click OK, check if preferred resolution is OK, save and exit, startx
or:
insert the disk that came with your monitor, and click on the Utility disk button. It will look for the .INF file for your display and create config settings from it. Works most of the time. Click OK, check preferred resolution, save and exit. startx
Hope this helpes to get you where you want. Apologied again.
Thanks Knurpht! I had an interesting excursion into the world of runlevel 3. I tried your suggestions, but no joy there :(:(
I also with some help of some folks on IRC #nvidia had a look around in var/log/Xorg.0.log, and SaX.log, I could post them if they would help, but it seems that my monitor DOES provide EDID info via the 15pin Dsub connection.
The first of your suggestions seemed to not change much, the second, selecting a generic LCD monitor was also unsuccesful. *If *I get 1440x900 as an option and “test” in Sax, it falls back to a wholly unsuitable resolution (?1152x9nn? or similar), whether using sax from runlevel3 or from KDE.
I have no working DVD drive ATM, so I did not try the 3rd suggestion, but I am pretty certain that my monitor is being correctly detected via EDID.
In both SaX.log and Xorg.0.log it rejects 1440x900 as a possible mode, even though I know for certain that both monitor and GPU can provide it.
I also tried after some googling, entering a modeline in to Xorg.conf which I had generated for 1440 x 900, but this was still rejected.
Maybe a simpler solution is a pair of very strong spectacles, but this goes against my stubborn nature!
Any further suggestions as to how to get wxga+ or wsxga+ resolutions LOWER than 1680x1050 on my wsxga+ monitor?
One problem I encountered whilst doing this is that “startx” from runlevel3 starts me up in (I think!??) KDE4, which I have (obv) installed, but have never used and therefore gives me a blank green suse desktop; if I system re-boot it starts up in my usual KDE 3.5.1, with all my settings and desktop as usual. Any ideas as to why this might be, or should I start a new thread for this separate issue?
Unfortunately, Knurpht I am running KDE 3.5.1, as I mention in my sig. as well as here:
*One problem I encountered whilst doing this is that “startx” from runlevel3 starts me up in (I think!??) KDE4, which I have (obv) installed, but have never used and therefore gives me a blank green suse desktop; if I system re-boot it starts up in my usual KDE 3.5.1, with all my settings and desktop as usual. Any ideas as to why this might be, or should I start a new thread for this separate issue?
I did, I think, find out how to solve the mini-problem (startx):
Edit file /etc/sysconfig/windowmanager to show startkde3
