[ltp] External Video on T30

[Richard Neill]

Just a thought - try setting the horiz,vert clocks to a much wider 
range. Eg my a22p requires:

HorizSync 20-140
VertRefresh 50-275

Yes, I know they look crazy! However, it might help. On a modern 
display, you can't risk damaging it with too high a frequency, so it's 
safe to experiment.

Richard




Michael B Allen wrote:
> Hi,
> 
> I've been stuggling to get the dsub out on the t30 to give me anything but
> 640x480. I need it to 1600x1200 for it to look even sane on the flatpanel
> display I have (DVI doesn't work). Does anyone have the external video
> working on the t30? This works under Win2K although it looks pretty
> bad. Here are lines that looked insteresting from the log:
> 
> XFree86 Version 4.3.0 (Custom Build: 4.3.0-10)
> OS Kernel: Linux version 2.4.20-13.7 (root@quark) (gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-110)) #1 Sat May 24 02:53:22 EDT 2003 
> (==) Using config file: "/etc/X11/XF86Config-4"
> (--) PCI:*(1:0:0) ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500] rev 0, Mem @ 0xe8000000/27, 0xd0100000/16, I/O @ 0x3000/8
> (II) LoadModule: "radeon"
> (II) Loading /usr/X11R6/lib/modules/drivers/radeon_drv.o
> (II) Module radeon: vendor="The XFree86 Project"
> 	compiled for 4.3.0, module version = 4.0.1
> 	Module class: XFree86 Video Driver
> 	ABI class: XFree86 Video Driver, version 0.6
> (II) LoadModule: "ati"
> (II) RADEON(0): Primary Display == Type 2
> (II) RADEON(0): Clone Display == Type 1
> (II) RADEON(0): Panel ID string: SXGA+ Single (85MHz)    
> (II) RADEON(0): Panel Size from BIOS: 1400x1050
> (II) RADEON(0): BIOS provided dividers will be used.(II) RADEON(0): PLL parameters: rf=2700 rd=12 min=12000 max=35000; xclk=18300
> (WW) RADEON(0): Monitor1: Using default hsync range of 28.00-33.00kHz
> (WW) RADEON(0): Monitor1: 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 "1600x1200" (hsync out of range)
> (II) RADEON(0): Not using mode "1600x1200" (no mode of this name)
> (II) RADEON(0): Not using mode "1400x1050" (no mode of this name)
> (**) RADEON(0): Virtual size is 1600x1200 (pitch 1600)
> (**) RADEON(0): *Mode "1600x1200"
> (**) RADEON(0): *Mode "1400x1050"
> (**) RADEON(0):  Default mode "640x480": 25.2 MHz, 31.5 kHz, 60.0 Hz
> (II) RADEON(0): Modeline "640x480"   25.20  640 656 752 800  480 490 492 525 -hsync -vsync
> (**) RADEON(0):  Default mode "320x240": 12.6 MHz, 31.5 kHz, 60.1 Hz (D)
> (II) RADEON(0): Modeline "320x240"   12.60  320 328 376 400  240 245 246 262 doublescan -hsync -vsync
> (WW) RADEON(0): Mode 1600x1200 is out of range.
> (WW) RADEON(0): Valid modes must be between 320x200-1400x1050
> (II) RADEON(0): Valid mode using on-chip RMX: 1400x1050
> (II) RADEON(0): Total number of valid FP mode(s) found: 1
> (**) RADEON(0): Virtual size is 1600x1200 (pitch 1600)
> (**) RADEON(0): *Mode "1400x1050": 85.0 MHz (scaled from 0.0 MHz), 53.1 kHz, 50.0 Hz
> (==) RADEON(0): Write-combining range (0xe8000000,0x1000000)
> (WW) RADEON(0): Static buffer allocation failed -- need at least 22500 kB video memory
> (II) RADEON(0): Direct rendering disabled
> 
> Here's what I thought would have worked (simplified for breivity):
> 
> Section "Monitor"
>         Identifier   "Monitor0"
>         VendorName   "Monitor Vendor"
>         ModelName    "Monitor Model"
>         HorizSync   31.0-94.0
>         VertRefresh 50.0-160.0
>         Option "dpms"
> 
> # 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"
> EndSection
> 
> Section "Screen"
>         Identifier   "Screen0"
>         Device       "ATI Radeon Mobility M7"
>         Monitor      "Monitor0"
>         DefaultDepth    24
> 
>         Subsection "Display"
>                 Depth       24
>                 Modes       "1600x1200"
>         EndSubsection
> 
> EndSection
> 
> I'm willing to get my hands dirty for this. Where does this radeon driver
> come from exactly?
> 
> Mike
>