Re: External Video on Thinkpad T30

[Michael B Allen <mba2000 ioplex com>]

On Fri, 30 May 2003, Alex Deucher wrote:
> 
> using fn-f7 uses the bios to switcht the ports, and I don't think it or
> X are aware of each other so that is probably messing things up.  If
> you want the vga port to be primary add the option "MonitorLayout"
> "CRT, LVDS" to you xf86config file.  that will tell the board to use
> the crt port with he primary crtc (normally on notebooks, the primary
> crtc drives the LCD panel).

Well that definately changed the behavior. The builtin LCD longer comes on
*at all* even when I do Ctrl-Alt-F1. Fortunately I'm a good blind typer.

But the hsync problem remains. It is using the default:

(WW) RADEON(0): Monitor0: Using default hsync range of 28.00-33.00kHz
(WW) RADEON(0): Monitor0: using default vrefresh range of 43.00-72.00Hz
(II) RADEON(0): Clock range:  12.00 to 350.00 MHz
(II) RADEON(0): Not using mode "1280x1024" (hsync out of range)

But my Monitor section clearly specifies a wider range. It's being
overidden somewhere. I need a double-secret-override!

Section "Monitor"
        Identifier   "Monitor0"
        VendorName   "Monitor Vendor"
        ModelName    "Monitor Model"
        HorizSync   31.0-120.0
        VertRefresh 50.0-160.0
        Option "dpms"

<snip other modes except the one I know drives this LCD>
# -- 1600x1200 --
# 1600x1200 @ 60Hz, 75.00 kHz hsync
    Modeline "1600x1200"  162   1600 1664 1856 2160
                                1200 1201 1204 1250 +HSync +VSync

EndSection
Section "Device"
	Identifier   "ATI Radeon Mobility M7"
        Driver       "radeon"
        VendorName   "ATI Radeon Mobility M7"
        BoardName    "ATI Radeon Mobility M7"
        Option       "MonitorLayout" "CRT,LVDS"
EndSection
Section "Screen"
	Identifier   "Screen0"
        Device       "ATI Radeon Mobility M7"
        Monitor      "Monitor0"
	DefaultDepth	24

	Subsection "Display"
        	Depth       24
                Modes       "1600x1200" "1400x1050" "1280x1024"
	EndSubsection
EndSection

Incedentally, I noticed if I try Depth 24 I get a 'static allocation
failed' message. If I change that to 16 I don't and DRI kicks in. The
end result is no different however.

Mike

-- 
A  program should be written to model the concepts of the task it
performs rather than the physical world or a process because this
maximizes  the  potential  for it to be applied to tasks that are
conceptually  similar and, more important, to tasks that have not
yet been conceived.