Date: Fri, 24 Feb 2006 00:17:13 -0500 From: Bob Perry <rperry@gti.net> To: Kevin Oberman <oberman@es.net> Cc: freebsd-gnome@FreeBSD.org Subject: Re: [Fwd: Only 640x480 Resolution Available After Upgrade] Message-ID: <43FE96D9.9010704@gti.net> In-Reply-To: <20060224044356.435A74504C@ptavv.es.net> References: <20060224044356.435A74504C@ptavv.es.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Kevin Oberman wrote: >> Date: Thu, 23 Feb 2006 21:31:26 -0500 >> From: Bob Perry <rperry@gti.net> >> Sender: owner-freebsd-gnome@freebsd.org >> >> This message was run in another mailing list with no resolution. >> Thought I'd try it in the gnome list. >> >> Any suggestions are welcome. >> >> Thnx, >> Bob >> >> -------- Original Message -------- >> Subject: Only 640x480 Resolution Available After Upgrade >> Date: Sun, 19 Feb 2006 13:33:09 -0500 >> From: Bob Perry <rperry@gti.net> >> To: freebsd-x11@freebsd.org >> >> I'm running FreeBSD RELEASE 5.4 and recently upgraded my xorg port. Ran >> into several problems since then, one of which included loss of >> available screen resolution modes. Prior to the upgrade, I ran at >> 1024x768. Following the upgrade, 640x480 is the only mode available. I >> had a bad day with the upgrade so I assume I did something wrong/stupid. >> >> Regardless, my xorg.conf file reflects the following: >> Section "Screen" >> Identifier "Screen0" >> Device "Card0" >> Monitor "Monitor0" >> DefaultDepth 24 >> Subsection "Display" >> Viewport 0 0 >> Depth 24 >> Modes "1024x768" "800x600" "640x480" >> EndSubSection >> EndSection >> >> I don't believe the file changed and question where else can I look to >> troubleshoot the problem? > > There are lots of things that can effect this. Monitor definition is most > significant. The first thing to look at is your /var/log/Xorg.0.log > file. It's long and lots of it is not relevant, but it contains a rather > long section detailing the selection of the display resolution and the > monitor and card capability. > > I quick thing to try is to rename your configuration and starting > Xorg. It will generate its configuration by probing the system and > usually does quite well. I'll try that. This problem occurred just after a portupgrade so I thought it might be a problem with the xorg upgrade. thnx much, Bob
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43FE96D9.9010704>