I recently installed OpenSuse 11.1 on my PC with ATI HD4850 and Iiyama Visionmaster 1451 CRT. For some reason, I am unable to select any refresh rate higher than 60 Hz in any mode using Desktop settings, or using VertRefresh settings in xorg.conf. Incidentally, the hor. and vert. refresh rate in xorg.conf are identical to those specified by the manufacturer.
As it’s a CRT, if you lower the resolution you get higher refresh rate options?
I vaguely remember that with CRT’s there’s a trade-off between resolution an refresh rate, so that at maximum resolution you only get the lowest refresh rate, usually 60 Hz (or 50 Hz in really, really old monitors).
Check your monitor specs, the info should be there. In an off-chance, also check the maximum output your video card can deliver.
From what I managed to trawl from Google, this monitor is capable of Max Resolution 1600 x 1200 @ 76 Hz. Usually, it is just a matter of selecting the correct monitor via sax2. Sometimes, a generic CRT monitor of similar specs has to be selected. If this doesn’t work for your monitor, then the manual method is to add a modeline to xorg.conf with some help from gtf:
I had already tried this, it does not work. In fact, it even messes up the screen. Do you have any other ideas? I am beginning to think something in my installation is messed up.
For some strange reason I have a new phenomenon now: after SaX has started xserver all I see is a cursor (not blinking) in a black screen. However, the system appears to be responding, because <Ctrl>+<Alt>+<Del> does perform a reboot. As far as I am aware of, I did not change anything in my configuration between the last time when xserver was correctly started and today…
In any case, I am able to login to console using the init 3 boot option. I was able to run hwinfo and the ouput is:
If you haven’t already, have a look at /var/log/Xorg.0.log. It’s readable, and each start-up generates a new one. Notice the explanation of “Markers” in the first few lines. initially scan for any EE or WW messages. The log should show you if on probing, your monitor’s default modes are being detected. It will also show how modelines known to Xorg are being used or rejected.
If you want help with interpretation, you should post back here and include the relevant lines from your Xorg.0.log file.
I did as you suggested, but the xorg.0.log only contained the warning “Force AIGLX enabled” and no error messages.
Because I was at a loss how to find out what is wrong, I decided to reinstall Linux (as this was a not so time consuming option) and start from scratch. What I found is this:
After installing it is impossible to start SaX, it exits with the warnings “FW FB scratch area not located at end of VRAM”, “No outputs definitively connected” and “Unable to find initial modes”, and with the error " RadeonHD(0): RandR No valid modes".
I tried installing the latest ATI driver, using the build rpm method (see ATI installation manual), and then “rpm -Uvh fglrx*.rpm”. This fails however, with multiple warnings of (I write this down from memory) “Duplicate files” (or similar wording) and then listing all instances of Xfgrlx as duplicates for the ATI versions.
I tried removing the existing fglrx files with rpm -e, then rebuilding the kernel from source with the ATI drivers. This seems to succeed, however generated some warnings (about casts failing and unused variables, forgot to write it down). After initializing with “aticonfig --initial” and “sax2 -r -m 0=fglrx” and rebooting, sax succesfully starts the x server, however an error message pops up after boot complete “Application KWin crashed… likely due to a bug” (also from memory). After this, the screen looks displaced and I am unable to use the keyboard to enter text in any window, however the mouse functions correctly.
Well, hope anyone can help me get out of this mess
Good, you found the log but what did it tell you in (II) messages, about the default modes detected on probing (module “ddc”) your monitor?
It should be using that information to select the correct modes. After the probing shown in the log, you should see a lot of modes being rejected if they are outside the vertical or horizontal refresh rates specified in the xorg.conf file (they should match your monitor specs).
I can’t help with the ATI driver specifics, but others may do so.