[SOLVED] ATI driver install - monitor out-of-range
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Hi, thanks for the suggestion. I tried this but no joy - as soon as I rebooted I got "out of range".
Unfortunely now I have no video in X at all. I have tried copying the xorg file back and then starting sax2 with various combinations of switches like -a, -l, --vesa 0:800x600@60, -m 0=radeonhd etc but no joy - I either get "out of range", "no input signal" or the system just hangs and I have to ctrl+C to get back to prompt. Sometimes the kernel seems to freeze too, and I have to use the reset button.
Is there a help manual for aticonfig? Perhaps with different settings I can get it working, but it reports there is no manual available, and typing aticonfig --help just spams my screen and I can only read the last few lines.
I do not have the answer you require, only a suggestion:
ATI have historically provided poor support for linux. This is rumoured to be improving, but not much has happened yet it seems.
NVIDIA have partly risen to the challenge linux presents by offering closed source linux drivers for their hardware. To their credit, these are regularly updated and usually "just work".
In my experience these drivers work so well with linux that I will currently not buy any hardware that doesn't already have, or doesn't have the option to install ( eg a laptop or netbook ) an NVIDIA GPU. Otherwise it has always proven to be too much of a headache, and my time is limited.
So my suggestion is: Get an NVIDIA GPU. Install their (politically incorrect) closed source module and all should be sweet.
Eventually the other manufacturers may wake up to linux. Meanwhile I am happy to support (and "advertise" here for) the ones that do support linux. Hewlett Packard also gets a "thumbs up" here for their printer drivers for linux.
Every hit the hardware manufacturer's "Linux Drivers Download" page gets means they think .... "Oh! Maybe there is a growing market here. Maybe we should employ someone to support the purchasers of our hardware who are running linux".
It's a commercial thing:
"You pays your money and you makes your choice".
Or you can continue to bang your head against the wall.
Hope you get something sorted out to your satisfaction.
There are a couple of hardware avenues I can try, but this card worked pefectly under Suse 11.0 with the one-click install process before, and I only reinstalled after some hard drive problems I had before.
The only changes that have been made to the system besides the new HDD are I changed the AGP aperture from 128 to 256MB and I slowed the memory bus speed to 166 (333 as it's DDR1) to match the processor. I found that LOTRO was doing weird things under Windows when the mem was running at 200 (400) when the proc only has a 166FSB (sempron 2.8GHz).
I'll try changing the AGP aperture and perhaps change the mem bus speed back up to 200 and see if that changes anything. I have another vid card I can try which is nVidia, but it's an old GeForce4 Ti 4200 so graphics in LOTRO will be appauling.
I'll POST resutls if I get it working.
Edit: the affected system is a different one to the one in my sig
Last edited by khinch; 06-17-2009 at 12:52 PM.
What does /var/log/Xorg.0.log have to say on the subject? It sounds like the fglrx install screwed up your monitor settings. You may need a VirtualX setting, (If still valid) or HorizSync & VertRefresh.
X will just throw out modes it doesn't like even if you specify them. I wonder what modes you have set?
Thanks for the suggestions. I have tried putting the AGP aperture back to 128MB and the memory bus speed back up to 200 but it was still the same, and these are the only differences since it worked perfectly with the FGLRX drivers before.
There are no KVMs or anything in the loop - just a DVI-VGA adapter and a VGA cable.
The monitor I have been using always seems to report itself as liking 68Hz refresh, which is visible but a bit garbled and dark. As soon as I manually select 60 or 75Hz it's fine. This happens with all linux distros and even Windows XP and 7, so the monitor must be reporting itself like that. Having said that, this fault happens with another monitor also, with a totally different VGA lead and DVI-VGA adapater.
Further to that, I experimented with installing Ubuntu 9.04 and then letting it install the FGLRX drivers automatically - same thing - as soon as it reboots, "out-of-range".
I'll get the output of /var/log/Xorg.0.log and post it up later, the difficulty being that once the fault has occurred I can only access the system at runlevel 3, so I'll have to save the output to USB stick and read it with a live distro or Windows7.
Out of interest, I did manage to get some output in 800x600 mode at one point, but stupidly hadn't logged whether it was FGLRX or radeonHD driver I used to get it, and then tried 1024x768 with the same command which borked the system so I couldn't check previous commands (had to press reset button).
I'll post any more results when I get them.
Edit: I forgot to mention, this card is an AGP Radeon HD2600pro, so it's quite a rare card. It could be that the more recent FGLRX drivers have broken compatibility, but I'll keep an open mind while testing.
Last edited by khinch; 06-20-2009 at 12:43 PM.
Well I have had some brief success - I managed to get a desktop working on fglrx driver, but it only worked until I rebooted for some reason. Here's what I did:
A fresh install of OpenSuSE 11.1 with all updates performed at install time. I then backed up my xorg.conf and Xorg.99.log, which are attached (xorg.conf.original.txt and Xorg99log_original.txt). I added the ATi repositories, downloaded the fglrx and pae kernel module, then switched to runlevel 3.
I have found (through experimentation) that sax2 only works after the "aticonfig --initial", which is strange I think. If I reboot straight after the aticonfig command I get out of range. So, I ran "aticonfig --initial" before backing up the Xorg.conf and Xorg99log again (first one attached as xorg.conf.aticonfig.txt - max files uploaded) and then "sax2 -r -l -m 0=fglrx". At this point I get a sax2 config screen at 800x600. If I attemt to change any of the settings at this stage I get no video again, so I left it unchanged and rebooted.
This worked, and I got a desktop running on fglrx at 800x600. I then ran amdcccle and the refresh rate was running at 72Hz for some reason. I set refresh to 60 as I know through Windows this monitor likes 60 or 75, and then changed resolution to 1024x768. This worked! And I got glxgears and xgl_glxgears scores of 3000+ and 600 respectively. The problem was as soon as I rebooted - out-of-range.
So, I know this card is capably of working correctly, I just need to find out how to convince it.
What could have changed between the reboot? Is there a config file I am missing?
I also have a couple of sax2 error logs and a Xorg99logto upload, but I have reached the 3file cap for this post.
You have two section for everything!!! You have two device sections. One using the radeonhd open driver and the next is for fglrx. You cannot use both drivers in the conf file. You also have two screen sections which I did not quote; it has some virtual resolutions that are pretty high.
Here is an modified version of xorg.conf that i want you to try:
# SaX generated X11 config file
# Created on: 2009-06-20T22:47:03+0100.
# Version: 8.1
# Contact: Marcus Schaefer <email@example.com>, 2005
# Contact: SaX-User list <https://lists.berlios.de/mailman/listinfo/sax-users>
# Automatically generated by [ISaX] (8.1)
# PLEASE DO NOT EDIT THIS FILE!
Warning! Long post - only read if you can spare 10mins.
Also, thanks for the replies, I think you all (especially Steel_J) have spent a lot of time helping me out here.
Now from what I understand you an recreate your success of 800x600 at will so
Within reason I can. Sometimes I seem to break it so bad I have to re-install (read on for more info about that).
Do you know how to use VI or VIM command line text editors? Because that is the secret to fixing these problems. I have a little guide I can post for you that I keep around if you like. Let me know.
Actually, not before today, but I have become very used to things like :qa! and :wq and :startinsert today. However, the guide would be much appreciated! The help files in Vi are comprehensive and good, but take a lot of searching when you're new.
You have two section for everything!!!
I'm glad you said that, because I noticed that today and was going to ask about it on here. So that answers my question, it's not normal.
Here is an modified version of xorg.conf that i want you to try:
I'm up for that, but I discovered something about the fglrx driver today that leads me to believe there is more to this than the xorg.conf file.
Also one last question. How many monitors do you have?
I have three available for testing. I have been using mainly my 15" LCD which has these probs. I have a 17" LCD, but don't tend to use it as it powers off after 1-2 hours use, and then subsequently every 5 mins, but it can be useful for testing. I also have a 15" CRT if necessary.
This site is only where I live on weekdays, my home machine is the one profiled in my sig, and is working fine right now, but here I have to make do with stuff I have lying around. I know for sure the monitor and vid card are OK, because they are both rock solid in WindowsXP and Windows7, and used to be rock solid in SuSE 11.0 until I had a hard drive prob. However, again, read on....
Also, I hear what you're saying about sax2 etc, but it I did all this stuff this morning, so I can take this advice forwards.
Ready? Got a cup of tea/coffee/beer/whisky? Then read my next POST.
Last edited by khinch; 06-21-2009 at 02:23 PM.
Fresh install of OpenSuSE 11.1 with all updates installed. I then backed up xorg.conf and Xorg.99.log, which should be identical to the ones previously posted. I installed the Ati repositories, and installed files X11-video-fglrxG01 and ati-fglrxG01-kmp-pae. I then did:
At which point I backed up my xorg.conf, which is attached as xorg.conf_2.txt. I know from experience if I reboot at this stage then I will get out-of-range, so I took business_kid's suggestion and used Vi to edit the file, setting horizsync to 31.5-55 and vertrefresh to 40.0-70.0. Reboot and...... out-of-range.
Rebooted to init3 and did:-
sax2 -r -l -m 0=fglrx
reboot to init6 worked fine with 800x600 desktop. At this point I backed up xorg.conf again, which is attached as xorg.conf_3.txt.
So, knowing I know have a working fglrx desktop, I booted to init3 and used Vi to change xorg.conf, under the screen section I changed all instances of 800x600 to 1024x768. Saved, rebooted and out-of-range. Rebooted to init3 and put them back fine again at 800x600.
I then noticed that since running sax2 the horizsync and vertrefresh had changed from the original. With a fresh install the monitor sits at 1024x768 fine using the radeonhd driver, so I changed the horizsync and vertrefresh to match the originals (horizsync from 20-46 to 30-62, and vertrefresh from 50-60 to 43-75), put screen res back to 1024x768. Deep breath, reboot and out-of-range.
At this point I realised all the rebooting was unnecessary and time consuming, so another reboot to init3 lasted me for the next hour or so. Also, at this point I KNOW that this monitor will display 1024x768 at 60Hz, so it's only the horizsync I have to worry about (or so I thought). I also know that some value between 30-62KHz must be OK since that is the values in the original xorg.conf, which works fine at 1024x768 @60Hz. I set the horizsync value to 30, 31, 32etc up to 62 in increments of 1 and tried startx each time, every single one out-of-range. (I got very quick at up- up- enter- :startinsert- backspace- number- :wq- enter- up -up enter- ctrl+alt+backspace- up -up etc...)
So, another tactic needed. I put the settings in xorg.conf back to 800x600, horizsync 20-46, vert refresh 43-75 and rebooted worked fine again at 800x600. I then checked the settings in YAST - > monitor settings - > where strangely the monitor values showed up as horiz 30-46K and vert 50-75 totally different from the ones in the xorg.conf file that I just set. So, in this section of YAST I set the monitor to 1024x768 blackscreen on monitor, power LED still green no response not even an out-of-range (I know, almost refreshing at this point). Tried ctrl+alt+backspace, tried alt+sysreq+R,E,I,S,U,B nothing. Kernel crashed. I had to hit reset.
Thankfully the settings didn't stick back to init5 and I'm at 800x600 again. This time I used amdcccle. I set monitor to 1024x768 fine. It defaulted to 72Hz for some reason, but it was also fine at 75Hz and 60Hz. I left it at 60 as I know for sure it works there in Windows and in SuSE11.0 before. I ran glxgears and fgl_glxgears 3600+ and 600+ rates so it's definitely working. I backed up the output of glxinfo and fglrxinfo to text files at this point if anyone wants to see them, but there is a 3file cap on here so can't add to this post. So, reboot to init5 and deep breath no GUI, it just went directly to command prompt with a message skipped services in runlevel 5. At this point I saved my xorg.conf again as xorg.conf_4.txt.
I checked xorg.conf and amdcccle has edited it since it's labelled itself all over the place, and changed the vertrefresh to 43-75, so I changed it back to 50-60. Rebooted at this point and it went straight back to command prompt again - skipped services in runlevel 5.
I noticed at this point that the resolutions in the screen section were still set to 800x600, despite amdcccle editing it when I set it to 1024x768. So I put it back to 1024x768, rebooted, X failed again dumping me back at the command prompt with my new best friend: skipped services in runlevel 5.
So, at this point I copied a known-good xorg.conf back, good ol' xorg.conf_3.txt was copied back, since it worked fine before for ages. Rebooted command prompt skipped services in runlevel 5. Now, I tried the sax2 route again as that's what got me working with the 800x600 desktop before, so once again I tried: sax2 -r -l -m 0=fglrx, but the kernel crashed again this time and I had to reset again. Not even alt+sysreq+REISUB worked.
So, back to runlevel3, ran aticonfig --initial, went OK. So as in previous cases I tried what got me a working 800x600 desktop: sax2 -r -l -m 0=fglrx yielded
XC: Sorry, could not start configuration server
XC: for details refer to the log file:
(I have this log file backed up also, if it's useful).
So, back to basics once more. I coped the file xorg.conf_original back to /etc/X11/xorg.conf and ran aticonfig --initial, followed by sax2 -r -l -m 0=fglrx and was met once again by a black screen with another kernel crash. At this point I reinstalled from scratch, and have a shiny new installation to break.
What is making me wonder, is that most of the severe problems only started after running amdcccle, it seems to have made changes to files other than xorg.conf. Even when I copied back a known-good xorg.conf file and repeated processes that worked previously, after running amdcccle it all went downhill. However, strangely, amdcccle is the only utility that has got me a working 1024x768 fglrx desktop, but it only works until reboot. So I know for sure this monitor will display 1024x768 at 60Hz from this video card using the fglrx driver, since it did it for a short time before reboot, I just have to find the right file I think. Very frustrating.
So, does anyone know what else amdcccle changes that could affect this? I can try any other xorg.conf if anyone thinks it will help, but my experience today suggests that Ati have made changes that use more than just this one file.