Problems with DVI+LCD on IBM ThinkPad T42p (ATI Technologies Inc M10 NT [FireGL Mobility T2])

[Michel Dänzer]

On Tue, 2005-07-26 at 09:46 -0400, Alex Deucher wrote:
> On 7/26/05, Martin Knoblauch <spamtrap at knobisoft.de> wrote:
> > 
> > --- Alex Deucher <alexdeucher at gmail.com> wrote:
> > 
> > > On 7/26/05, Martin Knoblauch <spamtrap at knobisoft.de> wrote:
> > > >
> > > > Section "Device"
> > > >         Identifier      "RADEON"
> > > >         Driver          "radeon"
> > > >         Option  "BusType"       "AGP"
> > > > #       Option  "MonitorLayout" "TDMS,AUTO"
> > > >         Option  "MonitorLayout" "TMDS,LVDS"
> > > > EndSection
> > > >
> > > >  If I use the commented out MonitorLayout, the notebook LCD comes
> > > up
> > > > clean, but the DVI display stays dark.

'TDMS' is not a valid value for Option "MonitorLayout", so the driver
probably does autodetection, and as Alex explained, it can only use
either LVDS or TMDS at this point.


> > > >  I also tried the proprietary "fglrx" driver, but that is not
> > > working
> > > > at all with the DVI display.

FWIW, that should be fixed in the upcoming 8.16 release.


> > > the xorg radeon driver doesn't support similateous internal TMDS and
> > > LVDS at the same time yet.  I've been working on supporting that, but
> > 
> >  hmm. In my case it isn't really a question of "simultaneous"
> > operation. I have the artifact in the overlay plane when the LVDS is
> > alone.
> 
> well, the problem is the X server cannot be reconfigured on the fly.
> when you undock with X running, it's still configured for the TMDS
> port rather than LVDS.  You need to restart X when you undock so the
> proper output can be configured.

More explicitly, the Option "MonitorLayout" you're using forces the
driver to use TMDS, even if the DVI panel isn't connected.

BTW, this doesn't have anything to do with 'the overlay plane', the
internal LVDS panel probably just doesn't like being driven as if it
were TMDS... The fact that screenshots look fine doesn't tell you
anything more than that the data is correct in the framebuffer.


> > > I've been real busy catching up on things since I got back from
> > > vacation, so I haven't had time to work on it lately:
> > > https://bugs.freedesktop.org/show_bug.cgi?id=3621
> > >
> > 
> >  I looked at the description an it looks promising. At least worth a
> > try. Newbee question: how to build the radeon driver alone?
> 
> Not really possible at the moment, [...]

Sure it is, the ati/radeon driver was one of the first that was
modularized. See http://wiki.x.org/wiki/ModularDevelopersGuide . You'll
still need to build any dependency modules at least once though, unless
you can get binaries from somebody.


PS: The radeon driver doesn't understand Option "DesktopSetup", so I'm
not sure how that would make any difference...

-- 
Earthling Michel Dänzer      |     Debian (powerpc), X and DRI developer
Libre software enthusiast    |   http://svcs.affero.net/rm.php?r=daenzer