I have been having a weird problem with X consistently using the resolution I choose. I am using an ATI AIW 8500DV AGp card and a Samsung 955DF mointor right now. X currently defaults to 1280x1024 and I can't reliably get anything higher. Once in a while it does come up as 1600x1200 or 1400x1050 all on its own while sitting at the GUI login screen. It is then a noticeably different desktop experience because all application's fonts are a lot smaller, more screen realestate, icons different size, etc! I can't find a reliable way to repoduce this or get it to consistenetly run at the resolution I specify. This has been going on since SUSE 7.3 Pro through 9.1 Pro. I have had an ATI AIW 128 PCI card or an ATI AIW 8500DV AGP card on at least two different Samsung monitors (17" and 19" that can do 1280x1024 or 1600x1200 respectively). Same main board, MSI K7T266 Pro2RU lastest BIOS. Have tried almost all combos of BIOS settings available to me. Have tried pci=noacpi, acpi=on/off, apm=on/off and combos of these settings. Moved the other PCI cards around the PCI slots and pulled them all out too. I have tried kdm, xdm and gdm with no discernable differences. I have verified my /etc/X11/XF86Config file every which way I can think of. I have used Sax/Yast to define my graphics subsystem (in single user and init 3 and init 5) and also just plain edited XF86Config by hand. I have used the default radeon drivers that come with each version of SUSE and the Gatos drivers at sourceforge to enable the All In Wonder capabilities of the cards. I've tried the ATI drivers but they didn't change the symptoms. Tried various color depths also 8, 15, 16, 24 etc. Different monitor definitions and edited the Monitors database too. I've tried running with and without the vga= line in the kernel boot options for grub or lilo. Currently at vga=0x031a or 1280x1024 16bit. This doesn't seem to make any difference. What am I missing? Any other troubleshooting steps? Why would X not read my XF86Config file and use its settings on a consistent basis? My hardware does support up to 1600x1200 at 16bit and either 60Hz or 65Hz. Thanks, Stan
On Wednesday 02 June 2004 21.30, SRGlasoe wrote:
What am I missing? Any other troubleshooting steps?
grab a copy of /var/log/XFree86.0.log once from each resolution and compare what it says. It sounds extremely odd, but the log hopefully has at least a clue about what's different
On Wednesday 02 June 2004 02:38 pm, Anders Johansson wrote:
On Wednesday 02 June 2004 21.30, SRGlasoe wrote:
What am I missing? Any other troubleshooting steps?
grab a copy of /var/log/XFree86.0.log once from each resolution and compare what it says. It sounds extremely odd, but the log hopefully has at least a clue about what's different
Been checking that log, no clue yet. Haven't saved versions for various resolutions though. Will do now though. Extremely difficult to get it above 1280x1024... Thanks.
On Wednesday 02 June 2004 02:38 pm, Anders Johansson wrote:
On Wednesday 02 June 2004 21.30, SRGlasoe wrote:
What am I missing? Any other troubleshooting steps?
grab a copy of /var/log/XFree86.0.log once from each resolution and compare what it says. It sounds extremely odd, but the log hopefully has at least a clue about what's different
Comparing a couple of these logs one thing that stood out was the use of (++) Using config file: "/tmp/sax2-8473/XF86Config" -or- (++) Using config file: "/tmp/sax2-4958/XF86Config" I knew it wasn't using /etc/X11/XF86Config! These are after init 3/5 or hard reboots too when I expect it to use /etc/X11/XF86Config. Any thoughts? Stan
On Thursday 03 June 2004 16.21, SRGlasoe wrote:
On Wednesday 02 June 2004 02:38 pm, Anders Johansson wrote:
On Wednesday 02 June 2004 21.30, SRGlasoe wrote:
What am I missing? Any other troubleshooting steps?
grab a copy of /var/log/XFree86.0.log once from each resolution and compare what it says. It sounds extremely odd, but the log hopefully has at least a clue about what's different
Comparing a couple of these logs one thing that stood out was the use of (++) Using config file: "/tmp/sax2-8473/XF86Config" -or- (++) Using config file: "/tmp/sax2-4958/XF86Config"
Are you sure you're looking at the latest log file there? I have never seen that, I would expect that to be from when you're running sax
I knew it wasn't using /etc/X11/XF86Config! These are after init 3/5 or hard reboots too when I expect it to use /etc/X11/XF86Config.
Any thoughts?
If those logs are really from when you're starting X, I have no idea why it's behaving like that. The only thing I can suggest is to delete them and try to force X's hands by launching it from the command line with the -config parameter, to see if you get the correct resolution when you're using the right config file
On Thursday 03 June 2004 11:34 am, Anders Johansson wrote:
On Thursday 03 June 2004 16.21, SRGlasoe wrote:
On Wednesday 02 June 2004 02:38 pm, Anders Johansson wrote:
On Wednesday 02 June 2004 21.30, SRGlasoe wrote:
What am I missing? Any other troubleshooting steps?
Anders and Ed, SOLVED. Tried Ed's suggested xorg.conf file and from then on I have had the correct resolution after logging in. I can't get it NOT to work correctly! Amazing. I've switched between the 9.1 default radeon drivers and the latest drivers from Gatos and the resolution at the desktop is correct in every desktop manager I've tried so far. This never happened before in a reliable and consistent manner. THANKS, Stan
** Reply to message from SRGlasoe
What am I missing? Any other troubleshooting steps? Why would X not read my XF86Config file and use its settings on a consistent basis? My hardware does support up to 1600x1200 at 16bit and either 60Hz or 65Hz.
Thanks, Stan
I had a lot of X problems until I discovered xf86cfg. It configures X and gives the option to save as /etc/X11/xorg.conf. Mouse started working, resolution i chose finally stuck, etc. Try copying /etc/X11/XF86Config to /etc/X11/xorg.conf. Log out. Restart X Server in KDM, or at a separate console (Ctl-Alt-F3), login as root and do an init 3 and an init 5. After the X Server is restarted, login in via gdm or kdm and see it the problems go away.
participants (3)
-
Anders Johansson -
Ed Harrison -
SRGlasoe