Fedora Linux Support Community & Resources Center
  #16  
Old 11th May 2008, 06:22 AM
eman_resu Offline
Registered User
 
Join Date: Apr 2008
Posts: 45
I changed it to 1280x800 in Display Manager and it worked, I'm in 1280x800. But direct rendering still isn't working.
Reply With Quote
  #17  
Old 11th May 2008, 06:27 AM
Hlingler's Avatar
Hlingler Offline
Administrator
 
Join Date: Sep 2006
Location: Connellsville, PA, USA
Posts: 11,289
Quote:
Originally Posted by eman_resu
I changed it to 1280x800 in Display Manager and it worked, I'm in 1280x800. But direct rendering still isn't working.
??? It should be! Everything except the resolution was 100% copacetic. I bet "Display Manager" wrecked the other settings.... *sigh*

Please attach current Xorg.0.log

And xorg.conf

V
Reply With Quote
  #18  
Old 11th May 2008, 06:31 AM
eman_resu Offline
Registered User
 
Join Date: Apr 2008
Posts: 45
Here's the files.
Attached Files
File Type: conf Xorg0log.conf (53.3 KB, 36 views)
File Type: conf xorg.conf (943 Bytes, 38 views)
Reply With Quote
  #19  
Old 11th May 2008, 06:40 AM
Hlingler's Avatar
Hlingler Offline
Administrator
 
Join Date: Sep 2006
Location: Connellsville, PA, USA
Posts: 11,289
Yeah, "Display Manager" blew away the existing xorg.conf and re-wrote it with only the modeline changes.

I edited it manually. Try the attached xorg.conf

V
Attached Files
File Type: conf radeon.xorg.conf (1.7 KB, 47 views)
Reply With Quote
  #20  
Old 11th May 2008, 06:53 AM
eman_resu Offline
Registered User
 
Join Date: Apr 2008
Posts: 45
Didn't work.
Attached Files
File Type: conf Xorg0log.conf (45.3 KB, 39 views)
Reply With Quote
  #21  
Old 11th May 2008, 07:06 AM
Hlingler's Avatar
Hlingler Offline
Administrator
 
Join Date: Sep 2006
Location: Connellsville, PA, USA
Posts: 11,289
OK, this time the Xorg.0.log is a little different: it shows compliance with the 1280x800 initial resolution - so I'm guessing that you have a successful GUI/desktop session, but not DRI? Because Xorg and it's spawn still insist on trying to map enough VRAM for 1400x1050, which you simply don't have, so the same error eventually occurs.

Try the attached xorg.conf - I applied those two over-ride options, see if they work.

All of your Xorg.0.logs show that Direct Rendering is working. That is good. It's up to you, but this is clearly just a matter of finding the correct settings in xorg.conf to force this recalcitrant software into compliance. I wish I knew exactly what those are, but I don't. And it's too late here tonite for me to continue now. If this xorg.conf doesn't work, please post back if you wish to continue to attempt to fix this, and I (or someone else) will get back to you later.

Good Luck,
V
Attached Files
File Type: conf radeon.xorg.conf (1.7 KB, 44 views)
Reply With Quote
  #22  
Old 11th May 2008, 07:19 AM
eman_resu Offline
Registered User
 
Join Date: Apr 2008
Posts: 45
That didn't work either. Thanks a lot for your help. I'll look around google for a few hours but I think I have to work in the morning. I attached the log file.
Attached Files
File Type: conf Xorg0log.conf (45.3 KB, 37 views)
Reply With Quote
  #23  
Old 11th May 2008, 06:28 PM
Hlingler's Avatar
Hlingler Offline
Administrator
 
Join Date: Sep 2006
Location: Connellsville, PA, USA
Posts: 11,289
Yeah, I wasn't paying attention: it's that funky display connection you've got, "LVDS" whatever that is - it's definitely not "standard", but I'm not very familiar with laptops. Reading up a little on the available documentation, this is from 'man radeon':
Code:
Option "LVDSProbePLL" "boolean"
              When  BIOS panel informations aren’t available (like on PowerBooks), it may still be necessary to use the firmware provided PLL values
              for the panel or flickering will happen. This option will force probing of the current value programmed in the chip when X is launched
              in that case.  This is only useful for LVDS panels (laptop internal panels).  The default is on.
Based on what I see in your Xorg.0.log, the 1400x1050 mode keeps getting auto-added to the list of modes, screwing up the VRAM. So: please remove those other two special options I added to xorg.conf (since they obviously don't work they're pointless and just clutter things up) and add the following option to section 'Device':
Code:
Option "LVDSProbePLL" "off"
Then re-startx. If that doesn't work, there are still many other options I found, but I suggest trying them one at a time until the right one(s) is found....

And again, it's up to you, but I'm certain that this is fixable - direct rendering is clearly working right up until the point where the VRAM error forces it off.

V
Reply With Quote
  #24  
Old 11th May 2008, 06:33 PM
eman_resu Offline
Registered User
 
Join Date: Apr 2008
Posts: 45
I guess I messed up last night on overwrote my backup with one of the modified xorg.conf files. So now it won't boot to X server, I'm in Windows now. I have xorg.conf~ in there, which looks like the original, also I have it posted in the first post. I don't know what the ~ means. I think I'm going to try just moving that to /etc/X11 and renaming it. Then I'll try your post.
Reply With Quote
  #25  
Old 11th May 2008, 06:40 PM
Hlingler's Avatar
Hlingler Offline
Administrator
 
Join Date: Sep 2006
Location: Connellsville, PA, USA
Posts: 11,289
Here's your last xorg.conf with the latest changes/fixes I described in my last post.

V
Attached Files
File Type: conf radeon.xorg.conf (1.7 KB, 42 views)
Reply With Quote
  #26  
Old 11th May 2008, 06:54 PM
eman_resu Offline
Registered User
 
Join Date: Apr 2008
Posts: 45
That didn't work.
Attached Files
File Type: conf Xorg0log.conf (45.3 KB, 36 views)
Reply With Quote
  #27  
Old 11th May 2008, 07:04 PM
Hlingler's Avatar
Hlingler Offline
Administrator
 
Join Date: Sep 2006
Location: Connellsville, PA, USA
Posts: 11,289
Well, poo, no it didn't: your last Xorg.0.log shows that Xorg blew right past that option and once again probed the display. Try this instead:
Code:
Option "PanelSize" "string"
              Should only be used when driver cannot detect the correct panel size.  Apply to both desktop (TMDS) and laptop (LVDS) digital  panels.
              When  a valid panel size is specified, the timings collected from DDC and BIOS will not be used. If you have a panel with timings dif-
              ferent from that of a standard VESA mode, you have to provide this information through the Modeline.
              For example, Option "PanelSize" "1400x1050"
              The default value is none.
So try:
Code:
Option "PanelSize" "1280x800"
V
Reply With Quote
  #28  
Old 11th May 2008, 07:19 PM
eman_resu Offline
Registered User
 
Join Date: Apr 2008
Posts: 45
Did not work.
Attached Files
File Type: conf Xorg0log.conf (45.3 KB, 30 views)
Reply With Quote
  #29  
Old 11th May 2008, 07:26 PM
Hlingler's Avatar
Hlingler Offline
Administrator
 
Join Date: Sep 2006
Location: Connellsville, PA, USA
Posts: 11,289
AHHRRRRGGGGG!

OK, I spotted this in Xorg.0.log:
Code:
(II) RADEON(0): Max desktop size set to 1600x1200
(II) RADEON(0): For a larger or smaller max desktop size, add a Virtual line to your xorg.conf
(II) RADEON(0): If you are having trouble with 3D, reduce the desktop size by adjusting the Virtual line to your xorg.conf
So, let's try that; add the line in red to your xorg.conf:
Code:
Section "Screen"
        Identifier "Screen0"
        Device     "Videocard0"
        Monitor    "Monitor0"
        Virtual 1280 800
        DefaultDepth     24
Reply With Quote
  #30  
Old 11th May 2008, 07:38 PM
eman_resu Offline
Registered User
 
Join Date: Apr 2008
Posts: 45
Didn't work.
Attached Files
File Type: conf Xorg0log.conf (45.3 KB, 36 views)
Reply With Quote
Reply

Tags
acceleration, ati, graphics, solved

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Graphics acceleration The Mishanator Using Fedora 10 5th September 2009 05:35 AM
Switch off Graphics Hardware acceleration swashplate Using Fedora 0 30th May 2009 06:45 PM
VMWare's 3D graphics acceleration just around the corner? stephanie.steve Linux Chat 0 28th September 2007 02:18 PM
nVidia and ATI graphics acceleration in FC5 smfinley Guides & Solutions (No Questions) 27 5th April 2006 08:13 AM


Current GMT-time: 13:51 (Saturday, 18-05-2013)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat