Another thing you might want to make certain of, and this is no indictment of the Red Hat product line or its customers, is that the guy you are trying to help isn't going back and using some automatic configuration editor in Fedora Core. Most Linux distributions have one, except Slackware-based distros (for which I am extremely happy), and they tend to choose the "best" settings for your hardware. The problem is that sometimes what the chipset supports is not what the particular card supports, i.e. some chipsets support up to a 1600x1200 resolution but the amount of memory available on the card can barely do 1084x768. Again, this is not the fault of anyone, but once the Xorg.conf file has been manually edited, it should never be changed by running any "all-knowing" automatic tools.
Also, check to see if the xorg.conf file that he is editing is the one that his system is actually using. Some systems duplicate the xorg.conf in multiple locations in the file system. Editing the system file when he may have a user version would cause the same problem. I realize you may have already checked these things, but sometimes users can be as thick as bricks.
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