Fw: ATI Radeon Mobility M6 LY w/LVDS panel and DRI
Vince Schiavoni <[email protected]> Sun, 18 May 2008 01:45:06 -0700 (PDT)
| Newsgroups | gmane.comp.video.dri.user |
|---|---|
| Message-ID | <[email protected]> |
--===============1612506803== Content-Type: multipart/alternative; boundary="0-220345488-1211100306=:77328" --0-220345488-1211100306=:77328 Content-Type: text/plain; charset=us-ascii 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, Vince "I may detest what you say, but I will defend to the death your right to say it." EB Hall, "Friends of Voltaire", 1906 ----- Forwarded Message ---- From: Garry Hurley <[email protected]> To: Alex Deucher <[email protected]> Cc: Vince Schiavoni <[email protected]>; [email protected] Sent: Saturday, May 17, 2008 12:05:0-1 PM Subject: Re: [Dri-users] ATI Radeon Mobility M6 LY w/LVDS panel and DRI 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. Garry On Fri, May 16, 2008 at 8:39 AM, Alex Deucher <[email protected]> wrote: On Fri, May 16, 2008 at 2:10 AM, Vince Schiavoni <[email protected]> wrote: > > > > Hello: > > > > > 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: > http://forum.fedoraforum.org/forum/showthread.php?t=187984 > > > > 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 > appreciated. > You don't have enough vram for DRI at depth 24. try depth16: Section "Screen" Identifier "Screen0" Device "Videocard0" DefaultDepth 16 SubSection "Display" Viewport 0 0 Depth 16 EndSubSection EndSection 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: Section "Screen" Identifier "Screen0" Device "Videocard0" DefaultDepth 24 SubSection "Display" Virtual 1024 768 Viewport 0 0 Depth 24 Modes "1024x768" "800x600" "640x480" EndSubSection EndSection Alex ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ -- _______________________________________________ Dri-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dri-users --0-220345488-1211100306=:77328 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable <html><head><style type=3D"text/css"><!-- DIV {margin:0px;} --></style></he= ad><body><div style=3D"font-family:"Verdana [microsoft]", "Helvetica [Adobe= ]", sans-serif;font-size:10pt"><P>Hello Garry and All:<BR></P><P></P><P>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 proc= ess, so I think that the OP has learned the hazards of using it - he actual= ly said he prefers manual edits.=A0 I have repeatedly cautioned him (and ot= hers) about this exact issue.=A0 And I personally know that Xorg likes to p= ick the highest possible resolution and color depth possible - even if it r= esults in DRI being disabled and/or a failed X-session.=A0 And Fedora uses = only the one standard file: /etc/X11/xorg.conf, no others.=A0 I just posted= another message to say that Alex's suggestions worked: DRI is enabled and working splendidly.=A0 But thanks for your quick response and the heads-up= .</P><P></P><P>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.=A0 Fortunately not an issue in this case....</P><P= ></P><P>Thank You again, Gentlemen, for your quick and knowledgable help on= this matter.</P><P></P><P>Thanx Again and Best Regards,</P><P>Vince</P><DI= V>=A0</DIV>"I may detest what you say, but I will defend to the death your = right to say it." EB Hall, "Friends of Voltaire", 1906<BR><DIV style=3D"fon= t-family:verdana, helvetica, sans-serif;font-size:10pt"><BR><BR><DIV style= =3D"font-family:times new roman, new york, times, serif;font-size:12pt">---= -- Forwarded Message ----<BR>From: Garry Hurley <[email protected]= om><BR>To: Alex Deucher <[email protected]><BR>Cc: Vince Schia= voni <[email protected]>; [email protected]<BR>Sent: Saturday, May 17, 2008 12:05:0-1 PM<BR>Subject: Re: [Dri-users] ATI Radeon= Mobility M6 LY w/LVDS panel and DRI<BR><BR>=0AAnother 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 a= nd using some automatic configuration editor in Fedora Core.=A0 Most Linux = distributions have one, except Slackware-based distros (for which I am extr= emely happy), and they tend to choose the "best" settings for your hardware= .=A0 The problem is that sometimes what the chipset supports is not what th= e particular card supports, i.e. some chipsets support up to a 1600x1200 re= solution but the amount of memory available on the card can barely do 1084x= 768.=A0 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-k= nowing" automatic tools.<BR><BR>Also, check to see if the xorg.conf file th= at he is editing is the one that his system is actually using.=A0 Some syst= ems duplicate the xorg.conf in multiple locations in the file system.=A0 Editing the system file when he may have = a user version would cause the same problem.=A0 I realize you may have alre= ady checked these things, but sometimes users can be as thick as bricks.<BR= ><BR>Garry<BR><BR><DIV class=3D"gmail_quote">On Fri, May 16, 2008 at 8:39 A= M, Alex Deucher <<A rel=3D"nofollow" ymailto=3D"mailto:alexdeucher@gmail= .com" target=3D"_blank" href=3D"mailto:[email protected]">alexdeucher@g= mail.com</A>> wrote:<BR><BLOCKQUOTE class=3D"gmail_quote" style=3D"borde= r-left:1px solid rgb(204, 204, 204);margin:0pt 0pt 0pt 0.8ex;padding-left:1= ex;"><DIV class=3D"Ih2E3d">On Fri, May 16, 2008 at 2:10 AM, Vince Schiavoni= <<A rel=3D"nofollow" ymailto=3D"mailto:[email protected]" target=3D"_b= lank" href=3D"mailto:[email protected]">[email protected]</A>> wrote:<= BR>=0A><BR>=0A><BR>=0A><BR>=0A> Hello:<BR>=0A><BR>=0A><BR= >=0A><BR>=0A><BR>=0A> I'm trying to help a guy on <A rel=3D"nofoll= ow" target=3D"_blank" href=3D"http://fedoraforum.org">fedoraforum.org</A> f= orums that has an ATI Radeon<BR>=0A> Mobility M6 LY chipset to get DRI w= orking. =A0Here's the thread:<BR>=0A> <A rel=3D"nofollow" target=3D"_bla= nk" href=3D"http://forum.fedoraforum.org/forum/showthread.php?t=3D187984">h= ttp://forum.fedoraforum.org/forum/showthread.php?t=3D187984</A><BR>=0A><= BR>=0A><BR>=0A><BR>=0A> That chipset is supported by the DRI 'rade= on' driver. =A0The Xorg.0.logs look<BR>=0A> good and show that everythin= g is working great - right up until Xorg and/or<BR>=0A> the driver(s) tr= y to map enough VRAM to cover the 1400x1050 LVDS panel he's<BR>=0A> got,= at which point it all chokes because he doesn't have enough VRAM (19800<BR= >=0A> KB required, 16000 KB available). =A0We've tried every xorg.conf<B= R>=0A> option/setting that seems helpful, to reduce the display resoluti= on to<BR>=0A> 1280x800 or less, but no matter what, Xorg or the drivers = keep adding that<BR>=0A> 1400x1050 mode to the list, which inevitably le= ads to a failed VRAM mapping<BR>=0A> and DRI is disabled at that point. = =A0Maybe we're missing something obvious,<BR>=0A> but I just can't figur= e out how to set the display resolution to a<BR>=0A> reasonable number t= hat the available VRAM could handle, and not have the<BR>=0A> software a= dd any more higher values to the list. =A0I'm hoping that someone on<BR>=0A= > this list has experience with this kind of hardware, or has some<BR>= =0A> advice/suggestions as to what to try to set/keep the display resolu= tion,<BR>=0A> without having it be over-ridden by the drivers. =A0Any he= lp will be greatly<BR>=0A> appreciated.<BR>=0A><BR><BR></DIV>You don'= t have enough vram for DRI at depth 24. =A0try depth16:<BR>=0ASection "Scre= en"<BR>=0AIdentifier "Screen0"<BR>=0ADevice "Videocard0"<BR>=0ADefaultDepth= 16<BR>=0ASubSection "Display"<BR>=0AViewport 0 0<BR>=0ADepth 16<BR>=0AEndS= ubSection<BR>=0AEndSection<BR><BR>=0Aif you want to keep depth 24, you'll h= ave to either reduce the size of<BR>=0Ayour front buffer or depth buffer.<B= R>=0Ayou can use a 16 bit depth buffer by setting:<BR>=0AOption "DepthBits"= "16"<BR><BR>=0Ato reduce the size of your front buffer, adjust the virtual= size down:<BR>=0ASection "Screen"<BR>=0AIdentifier "Screen0"<BR>=0ADevice = "Videocard0"<BR>=0ADefaultDepth 24<BR>=0ASubSection "Display"<BR>=0AVirtual= 1024 768<BR>=0AViewport 0 0<BR>=0ADepth 24<BR>=0AModes =A0 =A0 =A0 =A0 =A0= "1024x768" "800x600" "640x480"<BR>=0AEndSubSection<BR>=0AEndSection<BR><BR= >=0AAlex<BR><BR>=0A--------------------------------------------------------= -----------------<BR>=0AThis <A target=3D"_blank" href=3D"http://SF.net">SF= .net</A> email is sponsored by: Microsoft<BR>=0ADefy all challenges. Micros= oft(R) Visual Studio 2008.<BR><A rel=3D"nofollow" target=3D"_blank" href=3D= "http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/">http://clk.atdmt.= com/MRT/go/vse0120000070mrt/direct/01/</A><BR><FONT color=3D"#888888">--<BR= >=0A_______________________________________________<BR>=0ADri-users mailing= list<BR><A rel=3D"nofollow" ymailto=3D"mailto:[email protected].= net" target=3D"_blank" href=3D"mailto:[email protected]">Dri-= [email protected]</A><BR><A rel=3D"nofollow" target=3D"_blank" hr= ef=3D"https://lists.sourceforge.net/lists/listinfo/dri-users">https://lists= .sourceforge.net/lists/listinfo/dri-users</A><BR></FONT></BLOCKQUOTE></DIV>= <BR></DIV></DIV></div><br>=0A=0A=0A=0A </body></html> --0-220345488-1211100306=:77328-- --===============1612506803== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ --===============1612506803== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- _______________________________________________ Dri-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dri-users --===============1612506803==--