Hello Garry and All:
Yes, I agree: the auto-config tools are actually dangerous in some cases, and in fact we got burned already by having the Fedora "Display Manager" (aka 'system-config-display') "fix" a perfectly usable xorg.conf during this process, so I think that the OP has learned the hazards of using it - he actually said he prefers manual edits. I have repeatedly cautioned him (and others) about this exact issue. And I personally know that Xorg likes to pick the highest possible resolution and color depth possible - even if it results in DRI being disabled and/or a failed X-session. And Fedora uses only the one standard file: /etc/X11/xorg.conf, no others. I just posted another message to say that Alex's suggestions worked: DRI is enabled and working splendidly. But thanks for your quick response and the heads-up.
Actually, I consider that hideous nvidia-settings utility to be far more dangerous than any other - it has wrecked more xorg.conf files than I care to mention. Fortunately not an issue in this case....
Thank You again, Gentlemen, for your quick and knowledgable help on this matter.
Thanx Again and Best Regards,
On Fri, May 16, 2008 at 2:10 AM, Vince Schiavoni <firstname.lastname@example.org> wrote:You don't have enough vram for DRI at depth 24. try depth16:
> I'm trying to help a guy on fedoraforum.org forums that has an ATI Radeon
> Mobility M6 LY chipset to get DRI working. Here's the thread:
> That chipset is supported by the DRI 'radeon' driver. The Xorg.0.logs look
> good and show that everything is working great - right up until Xorg and/or
> the driver(s) try to map enough VRAM to cover the 1400x1050 LVDS panel he's
> got, at which point it all chokes because he doesn't have enough VRAM (19800
> KB required, 16000 KB available). We've tried every xorg.conf
> option/setting that seems helpful, to reduce the display resolution to
> 1280x800 or less, but no matter what, Xorg or the drivers keep adding that
> 1400x1050 mode to the list, which inevitably leads to a failed VRAM mapping
> and DRI is disabled at that point. Maybe we're missing something obvious,
> but I just can't figure out how to set the display resolution to a
> reasonable number that the available VRAM could handle, and not have the
> software add any more higher values to the list. I'm hoping that someone on
> this list has experience with this kind of hardware, or has some
> advice/suggestions as to what to try to set/keep the display resolution,
> without having it be over-ridden by the drivers. Any help will be greatly
Viewport 0 0
if you want to keep depth 24, you'll have to either reduce the size of
your front buffer or depth buffer.
you can use a 16 bit depth buffer by setting:
Option "DepthBits" "16"
to reduce the size of your front buffer, adjust the virtual size down:
Virtual 1024 768
Viewport 0 0
Modes "1024x768" "800x600" "640x480"
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
Dri-users mailing list