[gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[Kevin O'Gorman]

[-- Attachment #1: Type: text/plain, Size: 635 bytes --]

I had to replace an 4:3 Westinghouse monitor this weekend.  I got a new ASUS
VH242H, which is very wide.  But Xorg is still running 1280x1024, instead of
the monitor's normal 1920x1080, according to xorg logs because of lack of
video memory (using the ATI on the motherboard).  I can make the screen use
a 4:3 aspect ratio, so I'm up and running, much better than I started, but
I'd like to do better.

I guess I've gotta look for a video card, but all I have is PCIX slots, so I
don't want to put a lot of money into it (I'll be upgrading the mobo when
finances permit -- which is not right now.)

Any ideas?

-- 
Kevin O'Gorman, PhD

[-- Attachment #2: Type: text/html, Size: 709 bytes --]

Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[Bill Longman]

[-- Attachment #1: Type: text/plain, Size: 1499 bytes --]

On Mon, Aug 23, 2010 at 7:27 PM, Kevin O'Gorman <kogorman@gmail.com> wrote:

> I had to replace an 4:3 Westinghouse monitor this weekend.  I got a new
> ASUS VH242H, which is very wide.  But Xorg is still running 1280x1024,
> instead of the monitor's normal 1920x1080, according to xorg logs because of
> lack of video memory (using the ATI on the motherboard).  I can make the
> screen use a 4:3 aspect ratio, so I'm up and running, much better than I
> started, but I'd like to do better.
>
> I guess I've gotta look for a video card, but all I have is PCIX slots, so
> I don't want to put a lot of money into it (I'll be upgrading the mobo when
> finances permit -- which is not right now.)
>
> Any ideas?
>

You'd kinda think that since AGP is kinda sorta a beefed up version of PCI,
kinda sorta like PCI-X, you ought to be able to find a boatload of cards
like this for the cheap on eBay. But finding one is like finding hen's
teeth. The only one I've found is a 3.3/5V 32/64bit 33/66MHz ATI card and
they're about $US500. The company that makes them does them for multi-head
displays such as NOC displays, etc, so if you can't spare the change for a
new mobo, then five hundred bucks for a video card in a worn-out bus format
is probably out of the question.

<rant>I've been looking for one for years now because I have this great Dell
server that just keeps on running and running but it has these beautiful 64
bit PCI-X slots just calling out for a decent video card -- but not
AGP!</rant>

[-- Attachment #2: Type: text/html, Size: 1903 bytes --]

Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[dennisonic]

[-- Attachment #1: Type: text/plain, Size: 1719 bytes --]

 On 24/08/10 03:38, Bill Longman wrote:
>
>
> On Mon, Aug 23, 2010 at 7:27 PM, Kevin O'Gorman <kogorman@gmail.com
> <mailto:kogorman@gmail.com>> wrote:
>
>     I had to replace an 4:3 Westinghouse monitor this weekend.  I got
>     a new ASUS VH242H, which is very wide.  But Xorg is still running
>     1280x1024, instead of the monitor's normal 1920x1080, according to
>     xorg logs because of lack of video memory (using the ATI on the
>     motherboard).  I can make the screen use a 4:3 aspect ratio, so
>     I'm up and running, much better than I started, but I'd like to do
>     better.
>
>     I guess I've gotta look for a video card, but all I have is PCIX
>     slots, so I don't want to put a lot of money into it (I'll be
>     upgrading the mobo when finances permit -- which is not right now.)
>
>     Any ideas?
>
>
> You'd kinda think that since AGP is kinda sorta a beefed up version of
> PCI, kinda sorta like PCI-X, you ought to be able to find a boatload
> of cards like this for the cheap on eBay. But finding one is like
> finding hen's teeth. The only one I've found is a 3.3/5V 32/64bit
> 33/66MHz ATI card and they're about $US500. The company that makes
> them does them for multi-head displays such as NOC displays, etc, so
> if you can't spare the change for a new mobo, then five hundred bucks
> for a video card in a worn-out bus format is probably out of the question.
>
> <rant>I've been looking for one for years now because I have this
> great Dell server that just keeps on running and running but it has
> these beautiful 64 bit PCI-X slots just calling out for a decent video
> card -- but not AGP!</rant>
>
Have you tried setting different modelines etc using cvt and xrandr?

[-- Attachment #2: Type: text/html, Size: 2825 bytes --]

Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[Kevin O'Gorman]

[-- Attachment #1.1: Type: text/plain, Size: 2005 bytes --]

On Mon, Aug 23, 2010 at 8:58 PM, <dennisonic@gmail.com> wrote:

>  On 24/08/10 03:38, Bill Longman wrote:
>
>
>
> On Mon, Aug 23, 2010 at 7:27 PM, Kevin O'Gorman <kogorman@gmail.com>wrote:
>
>> I had to replace an 4:3 Westinghouse monitor this weekend.  I got a new
>> ASUS VH242H, which is very wide.  But Xorg is still running 1280x1024,
>> instead of the monitor's normal 1920x1080, according to xorg logs because of
>> lack of video memory (using the ATI on the motherboard).  I can make the
>> screen use a 4:3 aspect ratio, so I'm up and running, much better than I
>> started, but I'd like to do better.
>>
>> I guess I've gotta look for a video card, but all I have is PCIX slots, so
>> I don't want to put a lot of money into it (I'll be upgrading the mobo when
>> finances permit -- which is not right now.)
>>
>> Any ideas?
>>
>
>
> Have you tried setting different modelines etc using cvt and xrandr?
>

No.  I ditched my xorg.conf completely; it had been there just because I
couldn't get the Westinghouse monitor to work without it.  The Xorg logs
show it recognizes a boatload of
modes that the monitor likes, but gives an alibi for not using the HD ones.
The approach
does not seem promising.

/var/log/Xorg.0.log attached.  I'm paying attention to lines 269 295 327 369
377 380 and 381

269: (II) MACH64(0): Modeline "1920x1080"x0.0  148.50  1920 2008 2052 2200
1080 1084 1089 1125 +hsync +vsync (67.5 kHz)
295: (II) MACH64(0): Modeline "1920x1080"x60.0  172.80  1920 2040 2248 2576
1080 1081 1084 1118 -hsync +vsync (67.1 kHz)
327: (II) MACH64(0): Estimated virtual size for aspect ratio 1.7931 is
1920x1080
369: (II) MACH64(0): Not using default mode "1920x1440" (insufficient memory
for mode)
377: (II) MACH64(0): Not using driver mode "1920x1080" (bad mode
clock/interlace/doublescan)
380: (II) MACH64(0): Not using driver mode "1920x1080" (bad mode
clock/interlace/doublescan)
381: (WW) MACH64(0): Shrinking virtual size estimate from 1920x1080 to
1280x1024

-- 
Kevin O'Gorman, PhD

[-- Attachment #1.2: Type: text/html, Size: 3149 bytes --]

[-- Attachment #2: Xorg.0.log --]
[-- Type: text/plain, Size: 33638 bytes --]


X.Org X Server 1.7.7
Release Date: 2010-05-04
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.34-gentoo-r1-kosmanor i686 
Current Operating System: Linux treat 2.6.34-gentoo-r1-kosmanor #2 SMP PREEMPT Fri Jul 30 08:41:44 PDT 2010 i686
Kernel command line: ro root=/dev/sda5
Build Date: 07 August 2010  09:04:19AM
 
Current version of pixman: 0.18.2
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Aug 23 19:10:43 2010
(II) Loader magic: 0x81da7e0
(II) Module ABI versions:
	X.Org ANSI C Emulation: 0.4
	X.Org Video Driver: 6.0
	X.Org XInput driver : 7.0
	X.Org Server Extension : 2.0
(++) using VT number 7

(--) PCI:*(0:7:1:0) 1002:4752:1002:0008 ATI Technologies Inc Rage XL rev 39, Mem @ 0xf9000000/16777216, 0xf8600000/4096, I/O @ 0x00006000/256, BIOS @ 0x????????/131072
(==) Using default built-in configuration (30 lines)
(==) --- Start of built-in configuration ---
	Section "Device"
		Identifier	"Builtin Default ati Device 0"
		Driver	"ati"
	EndSection
	Section "Screen"
		Identifier	"Builtin Default ati Screen 0"
		Device	"Builtin Default ati Device 0"
	EndSection
	Section "Device"
		Identifier	"Builtin Default vesa Device 0"
		Driver	"vesa"
	EndSection
	Section "Screen"
		Identifier	"Builtin Default vesa Screen 0"
		Device	"Builtin Default vesa Device 0"
	EndSection
	Section "Device"
		Identifier	"Builtin Default fbdev Device 0"
		Driver	"fbdev"
	EndSection
	Section "Screen"
		Identifier	"Builtin Default fbdev Screen 0"
		Device	"Builtin Default fbdev Device 0"
	EndSection
	Section "ServerLayout"
		Identifier	"Builtin Default Layout"
		Screen	"Builtin Default ati Screen 0"
		Screen	"Builtin Default vesa Screen 0"
		Screen	"Builtin Default fbdev Screen 0"
	EndSection
(==) --- End of built-in configuration ---
(==) ServerLayout "Builtin Default Layout"
(**) |-->Screen "Builtin Default ati Screen 0" (0)
(**) |   |-->Monitor "<default monitor>"
(**) |   |-->Device "Builtin Default ati Device 0"
(==) No monitor specified for screen "Builtin Default ati Screen 0".
	Using a default monitor configuration.
(**) |-->Screen "Builtin Default vesa Screen 0" (1)
(**) |   |-->Monitor "<default monitor>"
(**) |   |-->Device "Builtin Default vesa Device 0"
(==) No monitor specified for screen "Builtin Default vesa Screen 0".
	Using a default monitor configuration.
(**) |-->Screen "Builtin Default fbdev Screen 0" (2)
(**) |   |-->Monitor "<default monitor>"
(**) |   |-->Device "Builtin Default fbdev Device 0"
(==) No monitor specified for screen "Builtin Default fbdev Screen 0".
	Using a default monitor configuration.
(==) Not automatically adding devices
(==) Not automatically enabling devices
(WW) The directory "/usr/share/fonts/TTF/" does not exist.
	Entry deleted from font path.
(WW) The directory "/usr/share/fonts/OTF" does not exist.
	Entry deleted from font path.
(==) FontPath set to:
	/usr/share/fonts/misc/,
	/usr/share/fonts/Type1/,
	/usr/share/fonts/100dpi/,
	/usr/share/fonts/75dpi/
(==) ModulePath set to "/usr/lib/xorg/modules"
(==) |-->Input Device "<default pointer>"
(==) |-->Input Device "<default keyboard>"
(==) The core pointer device wasn't specified explicitly in the layout.
	Using the default mouse configuration.
(==) The core keyboard device wasn't specified explicitly in the layout.
	Using the default keyboard configuration.
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
	compiled for 1.7.7, module version = 1.0.0
	Module class: X.Org Server Extension
	ABI class: X.Org Server Extension, version 2.0
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
	compiled for 1.7.7, module version = 1.0.0
	Module class: X.Org Server Extension
	ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions/libglx.so
(II) Module glx: vendor="X.Org Foundation"
	compiled for 1.7.7, module version = 1.0.0
	ABI class: X.Org Server Extension, version 2.0
(==) AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions/librecord.so
(II) Module record: vendor="X.Org Foundation"
	compiled for 1.7.7, module version = 1.13.0
	Module class: X.Org Server Extension
	ABI class: X.Org Server Extension, version 2.0
(II) Loading extension RECORD
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions/libdri.so
(II) Module dri: vendor="X.Org Foundation"
	compiled for 1.7.7, module version = 1.0.0
	ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "dri2"
(II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
	compiled for 1.7.7, module version = 1.1.0
	ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(II) LoadModule: "ati"
(II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so
(II) Module ati: vendor="X.Org Foundation"
	compiled for 1.7.6, module version = 6.13.0
	Module class: X.Org Video Driver
	ABI class: X.Org Video Driver, version 6.0
(II) LoadModule: "mach64"
(II) Loading /usr/lib/xorg/modules/drivers/mach64_drv.so
(II) Module mach64: vendor="X.Org Foundation"
	compiled for 1.7.6, module version = 6.8.2
	Module class: X.Org Video Driver
	ABI class: X.Org Video Driver, version 6.0
(II) LoadModule: "vesa"
(II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
(II) Module vesa: vendor="X.Org Foundation"
	compiled for 1.7.6, module version = 2.3.0
	Module class: X.Org Video Driver
	ABI class: X.Org Video Driver, version 6.0
(II) LoadModule: "fbdev"
(II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
(II) Module fbdev: vendor="X.Org Foundation"
	compiled for 1.7.6, module version = 0.4.2
	ABI class: X.Org Video Driver, version 6.0
(II) LoadModule: "mouse"
(II) Loading /usr/lib/xorg/modules/input/mouse_drv.so
(II) Module mouse: vendor="X.Org Foundation"
	compiled for 1.7.6, module version = 1.5.0
	Module class: X.Org XInput Driver
	ABI class: X.Org XInput driver, version 7.0
(II) LoadModule: "kbd"
(II) Loading /usr/lib/xorg/modules/input/kbd_drv.so
(II) Module kbd: vendor="X.Org Foundation"
	compiled for 1.7.6, module version = 1.4.0
	Module class: X.Org XInput Driver
	ABI class: X.Org XInput driver, version 7.0
(II) MACH64: Driver for ATI Mach64 chipsets
(II) VESA: driver for VESA chipsets: vesa
(II) FBDEV: driver for framebuffer: fbdev
(II) Primary Device is: PCI 07@00:01:0
(WW) Falling back to old probe method for vesa
(WW) Falling back to old probe method for fbdev
(II) Loading sub module "fbdevhw"
(II) LoadModule: "fbdevhw"
(II) Loading /usr/lib/xorg/modules/linux/libfbdevhw.so
(II) Module fbdevhw: vendor="X.Org Foundation"
	compiled for 1.7.7, module version = 0.0.2
	ABI class: X.Org Video Driver, version 6.0
(EE) open /dev/fb0: No such file or directory
(II) MACH64(0): Creating default Display subsection in Screen section
	"Builtin Default ati Screen 0" for depth/fbbpp 24/32
(==) MACH64(0): Depth 24, (--) framebuffer bpp 32
(==) MACH64(0): Using XAA acceleration architecture
(II) MACH64: Mach64 in slot 7:1:0 detected.
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Loading /usr/lib/xorg/modules/libint10.so
(II) Module int10: vendor="X.Org Foundation"
	compiled for 1.7.7, module version = 1.0.0
	ABI class: X.Org Video Driver, version 6.0
(II) MACH64(0): Primary V_BIOS segment is: 0xc000
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Module "ddc" already built-in
(II) Loading sub module "vbe"
(II) LoadModule: "vbe"
(II) Loading /usr/lib/xorg/modules/libvbe.so
(II) Module vbe: vendor="X.Org Foundation"
	compiled for 1.7.7, module version = 1.1.0
	ABI class: X.Org Video Driver, version 6.0
(II) MACH64(0): VESA BIOS detected
(II) MACH64(0): VESA VBE Version 2.0
(II) MACH64(0): VESA VBE Total Mem: 8128 kB
(II) MACH64(0): VESA VBE OEM: ATI MACH64
(II) MACH64(0): VESA VBE OEM Software Rev: 1.0
(II) MACH64(0): VESA VBE OEM Vendor: ATI Technologies Inc.
(II) MACH64(0): VESA VBE OEM Product: MACH64GM
(II) MACH64(0): VESA VBE OEM Product Rev: 01.00
(II) MACH64(0): VESA VBE DDC supported
(II) MACH64(0): VESA VBE DDC Level 2
(II) MACH64(0): VESA VBE DDC transfer in appr. 2 sec.
(II) MACH64(0): VESA VBE DDC read successfully
(II) MACH64(0): Manufacturer: ACI  Model: 24f3  Serial#: 150141
(II) MACH64(0): Year: 2010  Week: 17
(II) MACH64(0): EDID Version: 1.3
(II) MACH64(0): Analog Display Input,  Input Voltage Level: 0.700/0.700 V
(II) MACH64(0): Sync:  Separate
(II) MACH64(0): Max Image Size [cm]: horiz.: 52  vert.: 29
(II) MACH64(0): Gamma: 2.20
(II) MACH64(0): DPMS capabilities: Off; RGB/Color Display
(II) MACH64(0): First detailed timing is preferred mode
(II) MACH64(0): redX: 0.644 redY: 0.332   greenX: 0.286 greenY: 0.601
(II) MACH64(0): blueX: 0.152 blueY: 0.076   whiteX: 0.312 whiteY: 0.328
(II) MACH64(0): Supported established timings:
(II) MACH64(0): 720x400@70Hz
(II) MACH64(0): 640x480@60Hz
(II) MACH64(0): 640x480@67Hz
(II) MACH64(0): 640x480@72Hz
(II) MACH64(0): 640x480@75Hz
(II) MACH64(0): 800x600@56Hz
(II) MACH64(0): 800x600@60Hz
(II) MACH64(0): 800x600@72Hz
(II) MACH64(0): 800x600@75Hz
(II) MACH64(0): 832x624@75Hz
(II) MACH64(0): 1024x768@60Hz
(II) MACH64(0): 1024x768@70Hz
(II) MACH64(0): 1024x768@75Hz
(II) MACH64(0): 1280x1024@75Hz
(II) MACH64(0): Manufacturer's mask: 0
(II) MACH64(0): Supported standard timings:
(II) MACH64(0): #0: hsize: 1152  vsize 864  refresh: 75  vid: 20337
(II) MACH64(0): #1: hsize: 1280  vsize 960  refresh: 60  vid: 16513
(II) MACH64(0): #2: hsize: 1280  vsize 1024  refresh: 60  vid: 32897
(II) MACH64(0): #3: hsize: 1440  vsize 900  refresh: 60  vid: 149
(II) MACH64(0): #4: hsize: 1680  vsize 1050  refresh: 60  vid: 179
(II) MACH64(0): #5: hsize: 1920  vsize 1080  refresh: 60  vid: 49361
(II) MACH64(0): Supported detailed timing:
(II) MACH64(0): clock: 148.5 MHz   Image Size:  521 x 293 mm
(II) MACH64(0): h_active: 1920  h_sync: 2008  h_sync_end 2052 h_blank_end 2200 h_border: 0
(II) MACH64(0): v_active: 1080  v_sync: 1084  v_sync_end 1089 v_blanking: 1125 v_border: 0
(II) MACH64(0): Serial No: A4LMTF150141
(II) MACH64(0): Ranges: V min: 55 V max: 75 Hz, H min: 30 H max: 85 kHz, PixClock max 160 MHz
(II) MACH64(0): Monitor name: ASUS VH242H
(II) MACH64(0): EDID (in hex):
(II) MACH64(0): 	00ffffffffffff000469f3247d4a0200
(II) MACH64(0): 	1114010368341d782ac720a455499927
(II) MACH64(0): 	135054bfef00714f814081809500b300
(II) MACH64(0): 	d1c001010101023a801871382d40582c
(II) MACH64(0): 	450009252100001e000000ff0041344c
(II) MACH64(0): 	4d54463135303134310a000000fd0037
(II) MACH64(0): 	4b1e5510000a202020202020000000fc
(II) MACH64(0): 	0041535553205648323432480a2000bf
(II) MACH64(0): EDID vendor "ACI", prod id 9459
(II) MACH64(0): Using EDID range info for horizontal sync
(II) MACH64(0): Using EDID range info for vertical refresh
(II) MACH64(0): Printing DDC gathered Modelines:
(II) MACH64(0): Modeline "1920x1080"x0.0  148.50  1920 2008 2052 2200  1080 1084 1089 1125 +hsync +vsync (67.5 kHz)
(II) MACH64(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz)
(II) MACH64(0): Modeline "800x600"x0.0   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz)
(II) MACH64(0): Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz)
(II) MACH64(0): Modeline "640x480"x0.0   31.50  640 664 704 832  480 489 492 520 -hsync -vsync (37.9 kHz)
(II) MACH64(0): Modeline "640x480"x0.0   30.24  640 704 768 864  480 483 486 525 -hsync -vsync (35.0 kHz)
(II) MACH64(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz)
(II) MACH64(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz)
(II) MACH64(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
(II) MACH64(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz)
(II) MACH64(0): Modeline "1024x768"x0.0   75.00  1024 1048 1184 1328  768 771 777 806 -hsync -vsync (56.5 kHz)
(II) MACH64(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz)
(II) MACH64(0): Modeline "832x624"x0.0   57.28  832 864 928 1152  624 625 628 667 -hsync -vsync (49.7 kHz)
(II) MACH64(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz)
(II) MACH64(0): Modeline "800x600"x0.0   50.00  800 856 976 1040  600 637 643 666 +hsync +vsync (48.1 kHz)
(II) MACH64(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz)
(II) MACH64(0): Modeline "1280x960"x0.0  108.00  1280 1376 1488 1800  960 961 964 1000 +hsync +vsync (60.0 kHz)
(II) MACH64(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
(II) MACH64(0): Modeline "1440x900"x0.0  106.50  1440 1520 1672 1904  900 903 909 934 -hsync +vsync (55.9 kHz)
(II) MACH64(0): Modeline "1680x1050"x0.0  146.25  1680 1784 1960 2240  1050 1053 1059 1089 -hsync +vsync (65.3 kHz)
(II) MACH64(0): Modeline "1920x1080"x60.0  172.80  1920 2040 2248 2576  1080 1081 1084 1118 -hsync +vsync (67.1 kHz)
(II) MACH64(0): BIOS Data:  BIOSSize=0x8000, ROMTable=0x0114.
(II) MACH64(0): BIOS Data:  ClockTable=0x082C, FrequencyTable=0x0000.
(II) MACH64(0): BIOS Data:  LCDTable=0x0000.
(II) MACH64(0): BIOS Data:  VideoTable=0x0000, HardwareTable=0x015E.
(II) MACH64(0): BIOS Data:  I2CType=0x0F, Tuner=0x00, Decoder=0x00, Audio=0x0F.
(--) MACH64(0): ATI 3D Rage XL or XC graphics controller detected.
(--) MACH64(0): Chip type 4752 "GR", version 7, foundry TSMC, class 0, revision 0x00.
(--) MACH64(0): PCI bus interface detected;  block I/O base is 0x6000.
(--) MACH64(0): ATI Mach64 adapter detected.
(!!) MACH64(0): For information on using the multimedia capabilities
	of this adapter, please see http://gatos.sf.net.
(--) MACH64(0): Internal RAMDAC (subtype 1) detected.
(==) MACH64(0): RGB weight 888
(==) MACH64(0): Default visual is TrueColor
(==) MACH64(0): Using gamma correction (1.0, 1.0, 1.0)
(II) MACH64(0): Using Mach64 accelerator CRTC.
(II) MACH64(0): Storing hardware cursor image at 0xF97FFC00.
(II) MACH64(0): Using 8 MB linear aperture at 0xF9000000.
(!!) MACH64(0): Virtual resolutions will be limited to 8191 kB
 due to linear aperture size and/or placement of hardware cursor image area.
(II) MACH64(0): Using Block 0 MMIO aperture at 0xF8600400.
(II) MACH64(0): Using Block 1 MMIO aperture at 0xF8600000.
(II) MACH64(0): MMIO write caching enabled.
(--) MACH64(0): 8192 kB of SGRAM (2:1) 32-bit detected (using 8191 kB).
(WW) MACH64(0): Cannot shadow an accelerated frame buffer.
(II) MACH64(0): Engine XCLK 60.044 MHz;  Refresh rate code 1.
(--) MACH64(0): Internal programmable clock generator detected.
(--) MACH64(0): Reference clock 157.5/11 (14.318) MHz.
(II) MACH64(0): <default monitor>: Using hsync range of 30.00-85.00 kHz
(II) MACH64(0): <default monitor>: Using vrefresh range of 55.00-75.00 Hz
(II) MACH64(0): <default monitor>: Using maximum pixel clock of 160.00 MHz
(II) MACH64(0): Estimated virtual size for aspect ratio 1.7931 is 1920x1080
(II) MACH64(0): Maximum clock: 120.00 MHz
(II) MACH64(0): Not using default mode "640x350" (vrefresh out of range)
(II) MACH64(0): Not using default mode "320x175" (vrefresh out of range)
(II) MACH64(0): Not using default mode "640x400" (vrefresh out of range)
(II) MACH64(0): Not using default mode "320x200" (vrefresh out of range)
(II) MACH64(0): Not using default mode "720x400" (vrefresh out of range)
(II) MACH64(0): Not using default mode "360x200" (vrefresh out of range)
(II) MACH64(0): Not using default mode "640x480" (vrefresh out of range)
(II) MACH64(0): Not using default mode "320x240" (vrefresh out of range)
(II) MACH64(0): Not using default mode "800x600" (vrefresh out of range)
(II) MACH64(0): Not using default mode "400x300" (vrefresh out of range)
(II) MACH64(0): Not using default mode "1024x768" (vrefresh out of range)
(II) MACH64(0): Not using default mode "512x384" (vrefresh out of range)
(II) MACH64(0): Not using default mode "1024x768" (vrefresh out of range)
(II) MACH64(0): Not using default mode "512x384" (vrefresh out of range)
(II) MACH64(0): Not using default mode "1280x960" (bad mode clock/interlace/doublescan)
(II) MACH64(0): Not using default mode "640x480" (hsync out of range)
(II) MACH64(0): Not using default mode "1280x1024" (bad mode clock/interlace/doublescan)
(II) MACH64(0): Not using default mode "1280x1024" (bad mode clock/interlace/doublescan)
(II) MACH64(0): Not using default mode "640x512" (hsync out of range)
(II) MACH64(0): Not using default mode "1600x1200" (height too large for virtual size)
(II) MACH64(0): Not using default mode "1600x1200" (height too large for virtual size)
(II) MACH64(0): Not using default mode "1600x1200" (height too large for virtual size)
(II) MACH64(0): Not using default mode "800x600" (hsync out of range)
(II) MACH64(0): Not using default mode "1600x1200" (height too large for virtual size)
(II) MACH64(0): Not using default mode "800x600" (hsync out of range)
(II) MACH64(0): Not using default mode "1600x1200" (height too large for virtual size)
(II) MACH64(0): Not using default mode "800x600" (hsync out of range)
(II) MACH64(0): Not using default mode "1792x1344" (insufficient memory for mode)
(II) MACH64(0): Not using default mode "1792x1344" (insufficient memory for mode)
(II) MACH64(0): Not using default mode "896x672" (bad mode clock/interlace/doublescan)
(II) MACH64(0): Not using default mode "1856x1392" (insufficient memory for mode)
(II) MACH64(0): Not using default mode "928x696" (hsync out of range)
(II) MACH64(0): Not using default mode "1856x1392" (insufficient memory for mode)
(II) MACH64(0): Not using default mode "928x696" (bad mode clock/interlace/doublescan)
(II) MACH64(0): Not using default mode "1920x1440" (insufficient memory for mode)
(II) MACH64(0): Not using default mode "960x720" (hsync out of range)
(II) MACH64(0): Not using default mode "1920x1440" (insufficient memory for mode)
(II) MACH64(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan)
(II) MACH64(0): Not using default mode "1400x1050" (bad mode clock/interlace/doublescan)
(II) MACH64(0): Not using default mode "1400x1050" (bad mode clock/interlace/doublescan)
(II) MACH64(0): Not using default mode "1920x1440" (insufficient memory for mode)
(II) MACH64(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan)
(II) MACH64(0): Not using default mode "2048x1536" (insufficient memory for mode)
(II) MACH64(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
(II) MACH64(0): Not using default mode "2048x1536" (insufficient memory for mode)
(II) MACH64(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
(II) MACH64(0): Not using default mode "2048x1536" (insufficient memory for mode)
(II) MACH64(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
(II) MACH64(0): Not using driver mode "1920x1080" (bad mode clock/interlace/doublescan)
(II) MACH64(0): Not using driver mode "1280x1024" (bad mode clock/interlace/doublescan)
(II) MACH64(0): Not using driver mode "1680x1050" (bad mode clock/interlace/doublescan)
(II) MACH64(0): Not using driver mode "1920x1080" (bad mode clock/interlace/doublescan)
(WW) MACH64(0): Shrinking virtual size estimate from 1920x1080 to 1280x1024
(--) MACH64(0): Virtual size is 1280x1024 (pitch 1280)
(**) MACH64(0): *Driver mode "1280x1024": 108.0 MHz, 64.0 kHz, 60.0 Hz
(II) MACH64(0): Modeline "1280x1024"x60.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
(**) MACH64(0): *Default mode "1280x1024": 108.0 MHz, 64.0 kHz, 60.0 Hz
(II) MACH64(0): Modeline "1280x1024"x60.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
(**) MACH64(0): *Driver mode "1440x900": 106.5 MHz, 55.9 kHz, 59.9 Hz
(II) MACH64(0): Modeline "1440x900"x59.9  106.50  1440 1520 1672 1904  900 903 909 934 -hsync +vsync (55.9 kHz)
(**) MACH64(0): *Driver mode "1280x960": 108.0 MHz, 60.0 kHz, 60.0 Hz
(II) MACH64(0): Modeline "1280x960"x60.0  108.00  1280 1376 1488 1800  960 961 964 1000 +hsync +vsync (60.0 kHz)
(**) MACH64(0): *Default mode "1280x960": 108.0 MHz, 60.0 kHz, 60.0 Hz
(II) MACH64(0): Modeline "1280x960"x60.0  108.00  1280 1376 1488 1800  960 961 964 1000 +hsync +vsync (60.0 kHz)
(**) MACH64(0): *Driver mode "1152x864": 108.0 MHz, 67.5 kHz, 75.0 Hz
(II) MACH64(0): Modeline "1152x864"x75.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz)
(**) MACH64(0): *Default mode "1152x864": 108.0 MHz, 67.5 kHz, 75.0 Hz
(II) MACH64(0): Modeline "1152x864"x75.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz)
(**) MACH64(0): *Driver mode "1024x768": 78.8 MHz, 60.0 kHz, 75.0 Hz
(II) MACH64(0): Modeline "1024x768"x75.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz)
(**) MACH64(0): *Driver mode "1024x768": 75.0 MHz, 56.5 kHz, 70.1 Hz
(II) MACH64(0): Modeline "1024x768"x70.1   75.00  1024 1048 1184 1328  768 771 777 806 -hsync -vsync (56.5 kHz)
(**) MACH64(0): *Driver mode "1024x768": 65.0 MHz, 48.4 kHz, 60.0 Hz
(II) MACH64(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz)
(**) MACH64(0): *Default mode "1024x768": 78.8 MHz, 60.0 kHz, 75.0 Hz
(II) MACH64(0): Modeline "1024x768"x75.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz)
(**) MACH64(0): *Default mode "1024x768": 75.0 MHz, 56.5 kHz, 70.1 Hz
(II) MACH64(0): Modeline "1024x768"x70.1   75.00  1024 1048 1184 1328  768 771 777 806 -hsync -vsync (56.5 kHz)
(**) MACH64(0): *Default mode "1024x768": 65.0 MHz, 48.4 kHz, 60.0 Hz
(II) MACH64(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz)
(**) MACH64(0): *Default mode "896x672": 102.4 MHz, 83.7 kHz, 60.0 Hz (D)
(II) MACH64(0): Modeline "896x672"x60.0  102.40  896 960 1060 1224  672 672 674 697 doublescan -hsync +vsync (83.7 kHz)
(**) MACH64(0): *Driver mode "832x624": 57.3 MHz, 49.7 kHz, 74.6 Hz
(II) MACH64(0): Modeline "832x624"x74.6   57.28  832 864 928 1152  624 625 628 667 -hsync -vsync (49.7 kHz)
(**) MACH64(0): *Default mode "832x624": 57.3 MHz, 49.7 kHz, 74.6 Hz
(II) MACH64(0): Modeline "832x624"x74.6   57.28  832 864 928 1152  624 625 628 667 -hsync -vsync (49.7 kHz)
(**) MACH64(0): *Driver mode "800x600": 49.5 MHz, 46.9 kHz, 75.0 Hz
(II) MACH64(0): Modeline "800x600"x75.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz)
(**) MACH64(0): *Driver mode "800x600": 50.0 MHz, 48.1 kHz, 72.2 Hz
(II) MACH64(0): Modeline "800x600"x72.2   50.00  800 856 976 1040  600 637 643 666 +hsync +vsync (48.1 kHz)
(**) MACH64(0): *Driver mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz
(II) MACH64(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz)
(**) MACH64(0): *Driver mode "800x600": 36.0 MHz, 35.2 kHz, 56.2 Hz
(II) MACH64(0): Modeline "800x600"x56.2   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz)
(**) MACH64(0): *Default mode "800x600": 49.5 MHz, 46.9 kHz, 75.0 Hz
(II) MACH64(0): Modeline "800x600"x75.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz)
(**) MACH64(0): *Default mode "800x600": 50.0 MHz, 48.1 kHz, 72.2 Hz
(II) MACH64(0): Modeline "800x600"x72.2   50.00  800 856 976 1040  600 637 643 666 +hsync +vsync (48.1 kHz)
(**) MACH64(0): *Default mode "800x600": 87.8 MHz, 81.2 kHz, 65.0 Hz (D)
(II) MACH64(0): Modeline "800x600"x65.0   87.75  800 832 928 1080  600 600 602 625 doublescan +hsync +vsync (81.2 kHz)
(**) MACH64(0): *Default mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz
(II) MACH64(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz)
(**) MACH64(0): *Default mode "800x600": 81.0 MHz, 75.0 kHz, 60.0 Hz (D)
(II) MACH64(0): Modeline "800x600"x60.0   81.00  800 832 928 1080  600 600 602 625 doublescan +hsync +vsync (75.0 kHz)
(**) MACH64(0): *Default mode "800x600": 36.0 MHz, 35.2 kHz, 56.2 Hz
(II) MACH64(0): Modeline "800x600"x56.2   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz)
(**) MACH64(0): *Default mode "700x525": 77.9 MHz, 81.5 kHz, 74.8 Hz (D)
(II) MACH64(0): Modeline "700x525"x74.8   77.90  700 732 892 956  525 526 532 545 doublescan +hsync +vsync (81.5 kHz)
(**) MACH64(0): *Default mode "700x525": 61.0 MHz, 64.9 kHz, 60.0 Hz (D)
(II) MACH64(0): Modeline "700x525"x60.0   61.00  700 744 820 940  525 526 532 541 doublescan +hsync +vsync (64.9 kHz)
(**) MACH64(0): *Default mode "640x512": 67.5 MHz, 80.0 kHz, 75.0 Hz (D)
(II) MACH64(0): Modeline "640x512"x75.0   67.50  640 648 720 844  512 512 514 533 doublescan +hsync +vsync (80.0 kHz)
(**) MACH64(0): *Default mode "640x512": 54.0 MHz, 64.0 kHz, 60.0 Hz (D)
(II) MACH64(0): Modeline "640x512"x60.0   54.00  640 664 720 844  512 512 514 533 doublescan +hsync +vsync (64.0 kHz)
(**) MACH64(0): *Driver mode "640x480": 31.5 MHz, 37.5 kHz, 75.0 Hz
(II) MACH64(0): Modeline "640x480"x75.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz)
(**) MACH64(0): *Driver mode "640x480": 31.5 MHz, 37.9 kHz, 72.8 Hz
(II) MACH64(0): Modeline "640x480"x72.8   31.50  640 664 704 832  480 489 492 520 -hsync -vsync (37.9 kHz)
(**) MACH64(0): *Driver mode "640x480": 30.2 MHz, 35.0 kHz, 66.7 Hz
(II) MACH64(0): Modeline "640x480"x66.7   30.24  640 704 768 864  480 483 486 525 -hsync -vsync (35.0 kHz)
(**) MACH64(0): *Driver mode "640x480": 25.2 MHz, 31.5 kHz, 59.9 Hz
(II) MACH64(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz)
(**) MACH64(0): *Default mode "640x480": 31.5 MHz, 37.5 kHz, 75.0 Hz
(II) MACH64(0): Modeline "640x480"x75.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz)
(**) MACH64(0): *Default mode "640x480": 31.5 MHz, 37.9 kHz, 72.8 Hz
(II) MACH64(0): Modeline "640x480"x72.8   31.50  640 664 704 832  480 489 492 520 -hsync -vsync (37.9 kHz)
(**) MACH64(0): *Default mode "640x480": 54.0 MHz, 60.0 kHz, 60.0 Hz (D)
(II) MACH64(0): Modeline "640x480"x60.0   54.00  640 688 744 900  480 480 482 500 doublescan +hsync +vsync (60.0 kHz)
(**) MACH64(0): *Default mode "640x480": 25.2 MHz, 31.5 kHz, 59.9 Hz
(II) MACH64(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz)
(**) MACH64(0): *Driver mode "720x400": 28.3 MHz, 31.5 kHz, 70.1 Hz
(II) MACH64(0): Modeline "720x400"x70.1   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz)
(**) MACH64(0): *Default mode "576x432": 54.0 MHz, 67.5 kHz, 75.0 Hz (D)
(II) MACH64(0): Modeline "576x432"x75.0   54.00  576 608 672 800  432 432 434 450 doublescan +hsync +vsync (67.5 kHz)
(**) MACH64(0): *Default mode "512x384": 39.4 MHz, 60.0 kHz, 75.0 Hz (D)
(II) MACH64(0): Modeline "512x384"x75.0   39.38  512 520 568 656  384 384 386 400 doublescan +hsync +vsync (60.0 kHz)
(**) MACH64(0): *Default mode "512x384": 37.5 MHz, 56.5 kHz, 70.1 Hz (D)
(II) MACH64(0): Modeline "512x384"x70.1   37.50  512 524 592 664  384 385 388 403 doublescan -hsync -vsync (56.5 kHz)
(**) MACH64(0): *Default mode "512x384": 32.5 MHz, 48.4 kHz, 60.0 Hz (D)
(II) MACH64(0): Modeline "512x384"x60.0   32.50  512 524 592 672  384 385 388 403 doublescan -hsync -vsync (48.4 kHz)
(**) MACH64(0): *Default mode "416x312": 28.6 MHz, 49.7 kHz, 74.7 Hz (D)
(II) MACH64(0): Modeline "416x312"x74.7   28.64  416 432 464 576  312 312 314 333 doublescan -hsync -vsync (49.7 kHz)
(**) MACH64(0): *Default mode "400x300": 24.8 MHz, 46.9 kHz, 75.1 Hz (D)
(II) MACH64(0): Modeline "400x300"x75.1   24.75  400 408 448 528  300 300 302 312 doublescan +hsync +vsync (46.9 kHz)
(**) MACH64(0): *Default mode "400x300": 25.0 MHz, 48.1 kHz, 72.2 Hz (D)
(II) MACH64(0): Modeline "400x300"x72.2   25.00  400 428 488 520  300 318 321 333 doublescan +hsync +vsync (48.1 kHz)
(**) MACH64(0): *Default mode "400x300": 20.0 MHz, 37.9 kHz, 60.3 Hz (D)
(II) MACH64(0): Modeline "400x300"x60.3   20.00  400 420 484 528  300 300 302 314 doublescan +hsync +vsync (37.9 kHz)
(**) MACH64(0): *Default mode "400x300": 18.0 MHz, 35.2 kHz, 56.3 Hz (D)
(II) MACH64(0): Modeline "400x300"x56.3   18.00  400 412 448 512  300 300 301 312 doublescan +hsync +vsync (35.2 kHz)
(**) MACH64(0): *Default mode "320x240": 15.8 MHz, 37.5 kHz, 75.0 Hz (D)
(II) MACH64(0): Modeline "320x240"x75.0   15.75  320 328 360 420  240 240 242 250 doublescan -hsync -vsync (37.5 kHz)
(**) MACH64(0): *Default mode "320x240": 15.8 MHz, 37.9 kHz, 72.8 Hz (D)
(II) MACH64(0): Modeline "320x240"x72.8   15.75  320 332 352 416  240 244 246 260 doublescan -hsync -vsync (37.9 kHz)
(**) MACH64(0): *Default mode "320x240": 12.6 MHz, 31.5 kHz, 60.1 Hz (D)
(II) MACH64(0): Modeline "320x240"x60.1   12.59  320 328 376 400  240 245 246 262 doublescan -hsync -vsync (31.5 kHz)
(**) MACH64(0): Display dimensions: (520, 290) mm
(**) MACH64(0): DPI set to (62, 89)
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules/libfb.so
(II) Module fb: vendor="X.Org Foundation"
	compiled for 1.7.7, module version = 1.0.0
	ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(II) Loading sub module "xaa"
(II) LoadModule: "xaa"
(II) Loading /usr/lib/xorg/modules/libxaa.so
(II) Module xaa: vendor="X.Org Foundation"
	compiled for 1.7.7, module version = 1.2.1
	ABI class: X.Org Video Driver, version 6.0
(II) Loading sub module "i2c"
(II) LoadModule: "i2c"
(II) Module "i2c" already built-in
(II) MACH64(0): I2C bus "Mach64" initialized.
(II) UnloadModule: "vesa"
(II) Unloading /usr/lib/xorg/modules/drivers/vesa_drv.so
(II) UnloadModule: "fbdev"
(II) Unloading /usr/lib/xorg/modules/drivers/fbdev_drv.so
(II) UnloadModule: "fbdevhw"
(II) Unloading /usr/lib/xorg/modules/linux/libfbdevhw.so
(--) Depth 24 pixmap format is 32 bpp
(WW) MACH64(0): DRI static buffer allocation failed -- need at least 12800 kB video memory
(II) MACH64(0): Largest offscreen areas (with overlaps):
(II) MACH64(0): 	1280 x 614 rectangle at 0,1024
(II) MACH64(0): 	256 x 615 rectangle at 0,1024
(II) MACH64(0): Using XFree86 Acceleration Architecture (XAA)
	Screen to screen bit blits
	Solid filled rectangles
	8x8 mono pattern filled rectangles
	Indirect CPU to Screen color expansion
	Solid Lines
	Setting up tile and stipple cache:
		20 128x128 slots
		5 256x256 slots
(==) MACH64(0): Backing store disabled
(==) MACH64(0): Silken mouse enabled
(==) MACH64(0): DPMS enabled
(II) MACH64(0): Direct rendering disabled
(==) RandR enabled
(II) Initializing built-in extension Generic Event Extension
(II) Initializing built-in extension SHAPE
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension BIG-REQUESTS
(II) Initializing built-in extension SYNC
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-MISC
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) AIGLX: Screen 0 is not DRI2 capable
(II) AIGLX: Screen 0 is not DRI capable
(II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so
(II) GLX: Initialized DRISWRAST GL provider for screen 0
(WW) <default pointer>: No Device specified, looking for one...
(II) <default pointer>: Setting Device option to "/dev/input/mice"
(--) <default pointer>: Device: "/dev/input/mice"
(==) <default pointer>: Protocol: "Auto"
(**) Option "CorePointer"
(**) <default pointer>: always reports core events
(==) <default pointer>: Emulate3Buttons, Emulate3Timeout: 50
(**) <default pointer>: ZAxisMapping: buttons 4 and 5
(**) <default pointer>: Buttons: 9
(**) <default pointer>: Sensitivity: 1
(II) XINPUT: Adding extended input device "<default pointer>" (type: MOUSE)
(**) <default pointer>: (accel) keeping acceleration scheme 1
(**) <default pointer>: (accel) acceleration profile 0
(II) <default pointer>: Setting mouse protocol to "ExplorerPS/2"
(II) <default pointer>: ps2EnableDataReporting: succeeded
(**) Option "CoreKeyboard"
(**) <default keyboard>: always reports core events
(**) Option "Protocol" "standard"
(**) <default keyboard>: Protocol: standard
(**) Option "XkbRules" "base"
(**) <default keyboard>: XkbRules: "base"
(**) Option "XkbModel" "pc105"
(**) <default keyboard>: XkbModel: "pc105"
(**) Option "XkbLayout" "us"
(**) <default keyboard>: XkbLayout: "us"
(**) Option "CustomKeycodes" "off"
(**) <default keyboard>: CustomKeycodes disabled
(II) XINPUT: Adding extended input device "<default keyboard>" (type: KEYBOARD)
(II) <default pointer>: ps2EnableDataReporting: succeeded

Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[d.fedorov]

> On Mon, Aug 23, 2010 at 8:58 PM, <dennisonic@gmail.com> wrote:
>
>>  On 24/08/10 03:38, Bill Longman wrote:
>>
>>
>>
>> On Mon, Aug 23, 2010 at 7:27 PM, Kevin O'Gorman
>> <kogorman@gmail.com>wrote:
>>
>>> I had to replace an 4:3 Westinghouse monitor this weekend.  I got a new
>>> ASUS VH242H, which is very wide.  But Xorg is still running 1280x1024,
>>> instead of the monitor's normal 1920x1080, according to xorg logs
>>> because of
>>> lack of video memory (using the ATI on the motherboard).  I can make
>>> the
>>> screen use a 4:3 aspect ratio, so I'm up and running, much better than
>>> I
>>> started, but I'd like to do better.
>>>
>>> I guess I've gotta look for a video card, but all I have is PCIX slots,
>>> so
>>> I don't want to put a lot of money into it (I'll be upgrading the mobo
>>> when
>>> finances permit -- which is not right now.)
>>>
>>> Any ideas?
>>>
>>
>>
>> Have you tried setting different modelines etc using cvt and xrandr?
>>
>
> No.  I ditched my xorg.conf completely; it had been there just because I
> couldn't get the Westinghouse monitor to work without it.  The Xorg logs
> show it recognizes a boatload of
> modes that the monitor likes, but gives an alibi for not using the HD
> ones.
> The approach
> does not seem promising.
>
> /var/log/Xorg.0.log attached.  I'm paying attention to lines 269 295 327
> 369
> 377 380 and 381
>
> 269: (II) MACH64(0): Modeline "1920x1080"x0.0  148.50  1920 2008 2052 2200
> 1080 1084 1089 1125 +hsync +vsync (67.5 kHz)
> 295: (II) MACH64(0): Modeline "1920x1080"x60.0  172.80  1920 2040 2248
> 2576
> 1080 1081 1084 1118 -hsync +vsync (67.1 kHz)
> 327: (II) MACH64(0): Estimated virtual size for aspect ratio 1.7931 is
> 1920x1080
> 369: (II) MACH64(0): Not using default mode "1920x1440" (insufficient
> memory
> for mode)
> 377: (II) MACH64(0): Not using driver mode "1920x1080" (bad mode
> clock/interlace/doublescan)
> 380: (II) MACH64(0): Not using driver mode "1920x1080" (bad mode
> clock/interlace/doublescan)
> 381: (WW) MACH64(0): Shrinking virtual size estimate from 1920x1080 to
> 1280x1024
>
> --
> Kevin O'Gorman, PhD
>

1) Did you made entries for right resolution mode in xorg.conf
2) Are u sure that 1920x1080 is supported resolution for your monitor?
3) BIOS of some graphic cards is trying to overide the data reported by
the monitor in its own way

Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[Petri Rosenström]

To display 1920x1080 resolution with 32 bit colors, you need 8,294,400
bytes of video memory. So if you have more than eight megs of video
mem you shouldn't need to buy a new one.

have you tried something like

xrandr --auto

---

Petri Rosenström



On Tue, Aug 24, 2010 at 8:40 AM,  <d.fedorov@timeweb.ru> wrote:
>> On Mon, Aug 23, 2010 at 8:58 PM, <dennisonic@gmail.com> wrote:
>>
>>>  On 24/08/10 03:38, Bill Longman wrote:
>>>
>>>
>>>
>>> On Mon, Aug 23, 2010 at 7:27 PM, Kevin O'Gorman
>>> <kogorman@gmail.com>wrote:
>>>
>>>> I had to replace an 4:3 Westinghouse monitor this weekend.  I got a new
>>>> ASUS VH242H, which is very wide.  But Xorg is still running 1280x1024,
>>>> instead of the monitor's normal 1920x1080, according to xorg logs
>>>> because of
>>>> lack of video memory (using the ATI on the motherboard).  I can make
>>>> the
>>>> screen use a 4:3 aspect ratio, so I'm up and running, much better than
>>>> I
>>>> started, but I'd like to do better.
>>>>
>>>> I guess I've gotta look for a video card, but all I have is PCIX slots,
>>>> so
>>>> I don't want to put a lot of money into it (I'll be upgrading the mobo
>>>> when
>>>> finances permit -- which is not right now.)
>>>>
>>>> Any ideas?
>>>>
>>>
>>>
>>> Have you tried setting different modelines etc using cvt and xrandr?
>>>
>>
>> No.  I ditched my xorg.conf completely; it had been there just because I
>> couldn't get the Westinghouse monitor to work without it.  The Xorg logs
>> show it recognizes a boatload of
>> modes that the monitor likes, but gives an alibi for not using the HD
>> ones.
>> The approach
>> does not seem promising.
>>
>> /var/log/Xorg.0.log attached.  I'm paying attention to lines 269 295 327
>> 369
>> 377 380 and 381
>>
>> 269: (II) MACH64(0): Modeline "1920x1080"x0.0  148.50  1920 2008 2052 2200
>> 1080 1084 1089 1125 +hsync +vsync (67.5 kHz)
>> 295: (II) MACH64(0): Modeline "1920x1080"x60.0  172.80  1920 2040 2248
>> 2576
>> 1080 1081 1084 1118 -hsync +vsync (67.1 kHz)
>> 327: (II) MACH64(0): Estimated virtual size for aspect ratio 1.7931 is
>> 1920x1080
>> 369: (II) MACH64(0): Not using default mode "1920x1440" (insufficient
>> memory
>> for mode)
>> 377: (II) MACH64(0): Not using driver mode "1920x1080" (bad mode
>> clock/interlace/doublescan)
>> 380: (II) MACH64(0): Not using driver mode "1920x1080" (bad mode
>> clock/interlace/doublescan)
>> 381: (WW) MACH64(0): Shrinking virtual size estimate from 1920x1080 to
>> 1280x1024
>>
>> --
>> Kevin O'Gorman, PhD
>>
>
> 1) Did you made entries for right resolution mode in xorg.conf
> 2) Are u sure that 1920x1080 is supported resolution for your monitor?
> 3) BIOS of some graphic cards is trying to overide the data reported by
> the monitor in its own way
>
>
>

Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[Kevin O'Gorman]

[-- Attachment #1: Type: text/plain, Size: 919 bytes --]

On Mon, Aug 23, 2010 at 10:40 PM, <d.fedorov@timeweb.ru> wrote:

>
>
> 1) Did you made entries for right resolution mode in xorg.conf
>

I modified xorg.conf just to change the idenity info about the monitor.  Not
seeing any effect, I
deleted xorg.conf entirely, and that's how I'm runnung now, and got the
Xorg.0.log I attached
to a previous post.


> 2) Are u sure that 1920x1080 is supported resolution for your monitor?
>
The 1920 part is for sure.  I've got 3-1/4" left and right unused margins of
perfectly usable LCD.


> 3) BIOS of some graphic cards is trying to overide the data reported by
> the monitor in its own way
>
The logs show Xorg seriously considering 1920x1080.  I don't know what to do
about it's complaint about the modeline.  My fear is that the 2002 vintage
MACH64 motherboard video isn't capable of the speeds required, but I'm not
sure how to run that experiment.



-- 
Kevin O'Gorman, PhD

[-- Attachment #2: Type: text/html, Size: 1651 bytes --]

Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[Adam Carter]

[-- Attachment #1: Type: text/plain, Size: 1769 bytes --]

> No.  I ditched my xorg.conf completely; it had been there just because I
> couldn't get the Westinghouse monitor to work without it.  The Xorg logs
> show it recognizes a boatload of
> modes that the monitor likes, but gives an alibi for not using the HD
> ones.  The approach
> does not seem promising.
>
> /var/log/Xorg.0.log attached.  I'm paying attention to lines 269 295 327
> 369 377 380 and 381
>
> 269: (II) MACH64(0): Modeline "1920x1080"x0.0  148.50  1920 2008 2052 2200
> 1080 1084 1089 1125 +hsync +vsync (67.5 kHz)
> 295: (II) MACH64(0): Modeline "1920x1080"x60.0  172.80  1920 2040 2248
> 2576  1080 1081 1084 1118 -hsync +vsync (67.1 kHz)
> 327: (II) MACH64(0): Estimated virtual size for aspect ratio 1.7931 is
> 1920x1080
> 369: (II) MACH64(0): Not using default mode "1920x1440" (insufficient
> memory for mode)
> 377: (II) MACH64(0): Not using driver mode "1920x1080" (bad mode
> clock/interlace/doublescan)
> 380: (II) MACH64(0): Not using driver mode "1920x1080" (bad mode
> clock/interlace/doublescan)
> 381: (WW) MACH64(0): Shrinking virtual size estimate from 1920x1080 to
> 1280x1024
>
>
I assume 269 and 295 are related to 377 and 380. I remember i had a lot of
pain getting a Geforce 440MX to do 16:9, but it was all in the modelines.
There are some modeline calculators on the web, but be warned that some of
them produce bad output. I did eventually get it to work after a lot of
trial and error.

Also because of this;

(II) MACH64(0): <default monitor>: Using hsync range of 30.00-85.00 kHz
(II) MACH64(0): <default monitor>: Using vrefresh range of 55.00-75.00 Hz
(II) MACH64(0): <default monitor>: Using maximum pixel clock of 160.00 MHz

you may need to set the ranges in your xorg.conf instead. check the
monitors specs first tho.

[-- Attachment #2: Type: text/html, Size: 2121 bytes --]

Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[Mick]

On 24 August 2010 11:23, Adam Carter <adamcarter3@gmail.com> wrote:
>
>> No.  I ditched my xorg.conf completely; it had been there just because I
>> couldn't get the Westinghouse monitor to work without it.  The Xorg logs
>> show it recognizes a boatload of
>> modes that the monitor likes, but gives an alibi for not using the HD
>> ones.  The approach
>> does not seem promising.
>>
>> /var/log/Xorg.0.log attached.  I'm paying attention to lines 269 295 327
>> 369 377 380 and 381
>>
>> 269: (II) MACH64(0): Modeline "1920x1080"x0.0  148.50  1920 2008 2052
>> 2200  1080 1084 1089 1125 +hsync +vsync (67.5 kHz)
>> 295: (II) MACH64(0): Modeline "1920x1080"x60.0  172.80  1920 2040 2248
>> 2576  1080 1081 1084 1118 -hsync +vsync (67.1 kHz)
>> 327: (II) MACH64(0): Estimated virtual size for aspect ratio 1.7931 is
>> 1920x1080
>> 369: (II) MACH64(0): Not using default mode "1920x1440" (insufficient
>> memory for mode)
>> 377: (II) MACH64(0): Not using driver mode "1920x1080" (bad mode
>> clock/interlace/doublescan)
>> 380: (II) MACH64(0): Not using driver mode "1920x1080" (bad mode
>> clock/interlace/doublescan)
>> 381: (WW) MACH64(0): Shrinking virtual size estimate from 1920x1080 to
>> 1280x1024
>>
>
> I assume 269 and 295 are related to 377 and 380. I remember i had a lot of
> pain getting a Geforce 440MX to do 16:9, but it was all in the modelines.
> There are some modeline calculators on the web, but be warned that some of
> them produce bad output. I did eventually get it to work after a lot of
> trial and error.
>
> Also because of this;
>
> (II) MACH64(0): <default monitor>: Using hsync range of 30.00-85.00 kHz
> (II) MACH64(0): <default monitor>: Using vrefresh range of 55.00-75.00 Hz
> (II) MACH64(0): <default monitor>: Using maximum pixel clock of 160.00 MHz
>
>
> you may need to set the ranges in your xorg.conf instead. check the monitors
> specs first tho.

What does xrandr -q show?
-- 
Regards,
Mick

Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[Kevin O'Gorman]

[-- Attachment #1: Type: text/plain, Size: 2842 bytes --]

On Tue, Aug 24, 2010 at 4:27 AM, Mick <michaelkintzios@gmail.com> wrote:

> On 24 August 2010 11:23, Adam Carter <adamcarter3@gmail.com> wrote:
> >
> >> No.  I ditched my xorg.conf completely; it had been there just because I
> >> couldn't get the Westinghouse monitor to work without it.  The Xorg logs
> >> show it recognizes a boatload of
> >> modes that the monitor likes, but gives an alibi for not using the HD
> >> ones.  The approach
> >> does not seem promising.
> >>
> >> /var/log/Xorg.0.log attached.  I'm paying attention to lines 269 295 327
> >> 369 377 380 and 381
> >>
> >> 269: (II) MACH64(0): Modeline "1920x1080"x0.0  148.50  1920 2008 2052
> >> 2200  1080 1084 1089 1125 +hsync +vsync (67.5 kHz)
> >> 295: (II) MACH64(0): Modeline "1920x1080"x60.0  172.80  1920 2040 2248
> >> 2576  1080 1081 1084 1118 -hsync +vsync (67.1 kHz)
> >> 327: (II) MACH64(0): Estimated virtual size for aspect ratio 1.7931 is
> >> 1920x1080
> >> 369: (II) MACH64(0): Not using default mode "1920x1440" (insufficient
> >> memory for mode)
> >> 377: (II) MACH64(0): Not using driver mode "1920x1080" (bad mode
> >> clock/interlace/doublescan)
> >> 380: (II) MACH64(0): Not using driver mode "1920x1080" (bad mode
> >> clock/interlace/doublescan)
> >> 381: (WW) MACH64(0): Shrinking virtual size estimate from 1920x1080 to
> >> 1280x1024
> >>
> >
> > I assume 269 and 295 are related to 377 and 380. I remember i had a lot
> of
> > pain getting a Geforce 440MX to do 16:9, but it was all in the modelines.
> > There are some modeline calculators on the web, but be warned that some
> of
> > them produce bad output. I did eventually get it to work after a lot of
> > trial and error.
> >
> > Also because of this;
> >
> > (II) MACH64(0): <default monitor>: Using hsync range of 30.00-85.00 kHz
> > (II) MACH64(0): <default monitor>: Using vrefresh range of 55.00-75.00 Hz
> > (II) MACH64(0): <default monitor>: Using maximum pixel clock of 160.00
> MHz
> >
> >
> > you may need to set the ranges in your xorg.conf instead. check the
> monitors
> > specs first tho.
>
> What does xrandr -q show?
> --
> Regards,
> Mick
>
>
treat log # xrandr -q
Screen 0: minimum 320 x 240, current 1280 x 1024, maximum 1440 x 1024
default connected 1280x1024+0+0 0mm x 0mm
   1280x1024      60.0*
   1440x900       60.0
   1280x960       60.0
   1152x864       75.0
   1024x768       75.0     70.0     60.0
   896x672        60.0
   832x624        75.0
   800x600        75.0     72.0     60.0     56.0     65.0
   700x525        75.0     60.0
   640x512        75.0     60.0
   640x480        75.0     73.0     67.0     60.0
   720x400        70.0
   576x432        75.0
   512x384        75.0     70.0     60.0
   416x312        75.0
   400x300        75.0     72.0     60.0     56.0
   320x240        75.0     73.0     60.0
treat log #

-- 
Kevin O'Gorman, PhD

[-- Attachment #2: Type: text/html, Size: 3779 bytes --]

Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[Paul Hartman]

On Tue, Aug 24, 2010 at 12:10 PM, Kevin O'Gorman <kogorman@gmail.com> wrote:
>
>
> On Tue, Aug 24, 2010 at 4:27 AM, Mick <michaelkintzios@gmail.com> wrote:
>>
>> On 24 August 2010 11:23, Adam Carter <adamcarter3@gmail.com> wrote:
>> >
>> >> No.  I ditched my xorg.conf completely; it had been there just because
>> >> I
>> >> couldn't get the Westinghouse monitor to work without it.  The Xorg
>> >> logs
>> >> show it recognizes a boatload of
>> >> modes that the monitor likes, but gives an alibi for not using the HD
>> >> ones.  The approach
>> >> does not seem promising.
>> >>
>> >> /var/log/Xorg.0.log attached.  I'm paying attention to lines 269 295
>> >> 327
>> >> 369 377 380 and 381
>> >>
>> >> 269: (II) MACH64(0): Modeline "1920x1080"x0.0  148.50  1920 2008 2052
>> >> 2200  1080 1084 1089 1125 +hsync +vsync (67.5 kHz)
>> >> 295: (II) MACH64(0): Modeline "1920x1080"x60.0  172.80  1920 2040 2248
>> >> 2576  1080 1081 1084 1118 -hsync +vsync (67.1 kHz)
>> >> 327: (II) MACH64(0): Estimated virtual size for aspect ratio 1.7931 is
>> >> 1920x1080
>> >> 369: (II) MACH64(0): Not using default mode "1920x1440" (insufficient
>> >> memory for mode)
>> >> 377: (II) MACH64(0): Not using driver mode "1920x1080" (bad mode
>> >> clock/interlace/doublescan)
>> >> 380: (II) MACH64(0): Not using driver mode "1920x1080" (bad mode
>> >> clock/interlace/doublescan)
>> >> 381: (WW) MACH64(0): Shrinking virtual size estimate from 1920x1080 to
>> >> 1280x1024
>> >>
>> >
>> > I assume 269 and 295 are related to 377 and 380. I remember i had a lot
>> > of
>> > pain getting a Geforce 440MX to do 16:9, but it was all in the
>> > modelines.
>> > There are some modeline calculators on the web, but be warned that some
>> > of
>> > them produce bad output. I did eventually get it to work after a lot of
>> > trial and error.
>> >
>> > Also because of this;
>> >
>> > (II) MACH64(0): <default monitor>: Using hsync range of 30.00-85.00 kHz
>> > (II) MACH64(0): <default monitor>: Using vrefresh range of 55.00-75.00
>> > Hz
>> > (II) MACH64(0): <default monitor>: Using maximum pixel clock of 160.00
>> > MHz
>> >
>> >
>> > you may need to set the ranges in your xorg.conf instead. check the
>> > monitors
>> > specs first tho.
>>
>> What does xrandr -q show?
>> --
>> Regards,
>> Mick
>>
>
> treat log # xrandr -q
> Screen 0: minimum 320 x 240, current 1280 x 1024, maximum 1440 x 1024
> default connected 1280x1024+0+0 0mm x 0mm
>    1280x1024      60.0*
>    1440x900       60.0
>    1280x960       60.0
>    1152x864       75.0
>    1024x768       75.0     70.0     60.0
>    896x672        60.0
>    832x624        75.0
>    800x600        75.0     72.0     60.0     56.0     65.0
>    700x525        75.0     60.0
>    640x512        75.0     60.0
>    640x480        75.0     73.0     67.0     60.0
>    720x400        70.0
>    576x432        75.0
>    512x384        75.0     70.0     60.0
>    416x312        75.0
>    400x300        75.0     72.0     60.0     56.0
>    320x240        75.0     73.0     60.0
> treat log #

Until you can replace the video card, maybe you can come up with a
modeline for a lower resolution with 16:9 aspect ratio, such as:

852x480
1280x720
1365x768
1600x900

It wouldn't be optimal, but at least it would fill your screen without
being stretched strangely.

Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[Kevin O'Gorman]

[-- Attachment #1: Type: text/plain, Size: 3908 bytes --]

On Tue, Aug 24, 2010 at 11:48 AM, Paul Hartman <
paul.hartman+gentoo@gmail.com <paul.hartman%2Bgentoo@gmail.com>> wrote:

> On Tue, Aug 24, 2010 at 12:10 PM, Kevin O'Gorman <kogorman@gmail.com>
> wrote:
> >
> >
> > On Tue, Aug 24, 2010 at 4:27 AM, Mick <michaelkintzios@gmail.com> wrote:
> >>
> >> On 24 August 2010 11:23, Adam Carter <adamcarter3@gmail.com> wrote:
> >> >
> >> >> No.  I ditched my xorg.conf completely; it had been there just
> because
> >> >> I
> >> >> couldn't get the Westinghouse monitor to work without it.  The Xorg
> >> >> logs
> >> >> show it recognizes a boatload of
> >> >> modes that the monitor likes, but gives an alibi for not using the HD
> >> >> ones.  The approach
> >> >> does not seem promising.
> >> >>
> >> >> /var/log/Xorg.0.log attached.  I'm paying attention to lines 269 295
> >> >> 327
> >> >> 369 377 380 and 381
> >> >>
> >> >> 269: (II) MACH64(0): Modeline "1920x1080"x0.0  148.50  1920 2008 2052
> >> >> 2200  1080 1084 1089 1125 +hsync +vsync (67.5 kHz)
> >> >> 295: (II) MACH64(0): Modeline "1920x1080"x60.0  172.80  1920 2040
> 2248
> >> >> 2576  1080 1081 1084 1118 -hsync +vsync (67.1 kHz)
> >> >> 327: (II) MACH64(0): Estimated virtual size for aspect ratio 1.7931
> is
> >> >> 1920x1080
> >> >> 369: (II) MACH64(0): Not using default mode "1920x1440" (insufficient
> >> >> memory for mode)
> >> >> 377: (II) MACH64(0): Not using driver mode "1920x1080" (bad mode
> >> >> clock/interlace/doublescan)
> >> >> 380: (II) MACH64(0): Not using driver mode "1920x1080" (bad mode
> >> >> clock/interlace/doublescan)
> >> >> 381: (WW) MACH64(0): Shrinking virtual size estimate from 1920x1080
> to
> >> >> 1280x1024
> >> >>
> >> >
> >> > I assume 269 and 295 are related to 377 and 380. I remember i had a
> lot
> >> > of
> >> > pain getting a Geforce 440MX to do 16:9, but it was all in the
> >> > modelines.
> >> > There are some modeline calculators on the web, but be warned that
> some
> >> > of
> >> > them produce bad output. I did eventually get it to work after a lot
> of
> >> > trial and error.
> >> >
> >> > Also because of this;
> >> >
> >> > (II) MACH64(0): <default monitor>: Using hsync range of 30.00-85.00
> kHz
> >> > (II) MACH64(0): <default monitor>: Using vrefresh range of 55.00-75.00
> >> > Hz
> >> > (II) MACH64(0): <default monitor>: Using maximum pixel clock of 160.00
> >> > MHz
> >> >
> >> >
> >> > you may need to set the ranges in your xorg.conf instead. check the
> >> > monitors
> >> > specs first tho.
> >>
> >> What does xrandr -q show?
> >> --
> >> Regards,
> >> Mick
> >>
> >
> > treat log # xrandr -q
> > Screen 0: minimum 320 x 240, current 1280 x 1024, maximum 1440 x 1024
> > default connected 1280x1024+0+0 0mm x 0mm
> >    1280x1024      60.0*
> >    1440x900       60.0
> >    1280x960       60.0
> >    1152x864       75.0
> >    1024x768       75.0     70.0     60.0
> >    896x672        60.0
> >    832x624        75.0
> >    800x600        75.0     72.0     60.0     56.0     65.0
> >    700x525        75.0     60.0
> >    640x512        75.0     60.0
> >    640x480        75.0     73.0     67.0     60.0
> >    720x400        70.0
> >    576x432        75.0
> >    512x384        75.0     70.0     60.0
> >    416x312        75.0
> >    400x300        75.0     72.0     60.0     56.0
> >    320x240        75.0     73.0     60.0
> > treat log #
>
> Until you can replace the video card, maybe you can come up with a
> modeline for a lower resolution with 16:9 aspect ratio, such as:
>
> 852x480
> 1280x720
> 1365x768
> 1600x900
>
> It wouldn't be optimal, but at least it would fill your screen without
> being stretched strangely.
>
>
Yah, I might have some luck with that.  Since I'm years out of practice
fooling with this stuff (last seen in 2002) can someone point me at the
tools for
1) Computing a modeline (I understand the quality varies a lot)
2) Configuring an xorg.conf




-- 
Kevin O'Gorman, PhD

[-- Attachment #2: Type: text/html, Size: 5409 bytes --]

Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[Paul Hartman]

On Tue, Aug 24, 2010 at 5:07 PM, Kevin O'Gorman <kogorman@gmail.com> wrote:
> On Tue, Aug 24, 2010 at 11:48 AM, Paul Hartman
> <paul.hartman+gentoo@gmail.com> wrote:
>>
>> On Tue, Aug 24, 2010 at 12:10 PM, Kevin O'Gorman <kogorman@gmail.com>
>> wrote:
>> >
>> >
>> > On Tue, Aug 24, 2010 at 4:27 AM, Mick <michaelkintzios@gmail.com> wrote:
>> >>
>> >> On 24 August 2010 11:23, Adam Carter <adamcarter3@gmail.com> wrote:
>> >> >
>> >> >> No.  I ditched my xorg.conf completely; it had been there just
>> >> >> because
>> >> >> I
>> >> >> couldn't get the Westinghouse monitor to work without it.  The Xorg
>> >> >> logs
>> >> >> show it recognizes a boatload of
>> >> >> modes that the monitor likes, but gives an alibi for not using the
>> >> >> HD
>> >> >> ones.  The approach
>> >> >> does not seem promising.
>> >> >>
>> >> >> /var/log/Xorg.0.log attached.  I'm paying attention to lines 269 295
>> >> >> 327
>> >> >> 369 377 380 and 381
>> >> >>
>> >> >> 269: (II) MACH64(0): Modeline "1920x1080"x0.0  148.50  1920 2008
>> >> >> 2052
>> >> >> 2200  1080 1084 1089 1125 +hsync +vsync (67.5 kHz)
>> >> >> 295: (II) MACH64(0): Modeline "1920x1080"x60.0  172.80  1920 2040
>> >> >> 2248
>> >> >> 2576  1080 1081 1084 1118 -hsync +vsync (67.1 kHz)
>> >> >> 327: (II) MACH64(0): Estimated virtual size for aspect ratio 1.7931
>> >> >> is
>> >> >> 1920x1080
>> >> >> 369: (II) MACH64(0): Not using default mode "1920x1440"
>> >> >> (insufficient
>> >> >> memory for mode)
>> >> >> 377: (II) MACH64(0): Not using driver mode "1920x1080" (bad mode
>> >> >> clock/interlace/doublescan)
>> >> >> 380: (II) MACH64(0): Not using driver mode "1920x1080" (bad mode
>> >> >> clock/interlace/doublescan)
>> >> >> 381: (WW) MACH64(0): Shrinking virtual size estimate from 1920x1080
>> >> >> to
>> >> >> 1280x1024
>> >> >>
>> >> >
>> >> > I assume 269 and 295 are related to 377 and 380. I remember i had a
>> >> > lot
>> >> > of
>> >> > pain getting a Geforce 440MX to do 16:9, but it was all in the
>> >> > modelines.
>> >> > There are some modeline calculators on the web, but be warned that
>> >> > some
>> >> > of
>> >> > them produce bad output. I did eventually get it to work after a lot
>> >> > of
>> >> > trial and error.
>> >> >
>> >> > Also because of this;
>> >> >
>> >> > (II) MACH64(0): <default monitor>: Using hsync range of 30.00-85.00
>> >> > kHz
>> >> > (II) MACH64(0): <default monitor>: Using vrefresh range of
>> >> > 55.00-75.00
>> >> > Hz
>> >> > (II) MACH64(0): <default monitor>: Using maximum pixel clock of
>> >> > 160.00
>> >> > MHz
>> >> >
>> >> >
>> >> > you may need to set the ranges in your xorg.conf instead. check the
>> >> > monitors
>> >> > specs first tho.
>> >>
>> >> What does xrandr -q show?
>> >> --
>> >> Regards,
>> >> Mick
>> >>
>> >
>> > treat log # xrandr -q
>> > Screen 0: minimum 320 x 240, current 1280 x 1024, maximum 1440 x 1024
>> > default connected 1280x1024+0+0 0mm x 0mm
>> >    1280x1024      60.0*
>> >    1440x900       60.0
>> >    1280x960       60.0
>> >    1152x864       75.0
>> >    1024x768       75.0     70.0     60.0
>> >    896x672        60.0
>> >    832x624        75.0
>> >    800x600        75.0     72.0     60.0     56.0     65.0
>> >    700x525        75.0     60.0
>> >    640x512        75.0     60.0
>> >    640x480        75.0     73.0     67.0     60.0
>> >    720x400        70.0
>> >    576x432        75.0
>> >    512x384        75.0     70.0     60.0
>> >    416x312        75.0
>> >    400x300        75.0     72.0     60.0     56.0
>> >    320x240        75.0     73.0     60.0
>> > treat log #
>>
>> Until you can replace the video card, maybe you can come up with a
>> modeline for a lower resolution with 16:9 aspect ratio, such as:
>>
>> 852x480
>> 1280x720
>> 1365x768
>> 1600x900
>>
>> It wouldn't be optimal, but at least it would fill your screen without
>> being stretched strangely.
>>
>
> Yah, I might have some luck with that.  Since I'm years out of practice
> fooling with this stuff (last seen in 2002) can someone point me at the
> tools for
> 1) Computing a modeline (I understand the quality varies a lot)
> 2) Configuring an xorg.conf

Check out x11-apps/amlc -- it has an interactive modeline generator
where you tell it the aspect ratio & size of your screen and it spits
out modelines for you.  You'll still need to fill in the
HSync/VSync/Clock speed stuff.

Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[Dale]

Paul Hartman wrote:
> On Tue, Aug 24, 2010 at 5:07 PM, Kevin O'Gorman<kogorman@gmail.com>  wrote:
>    
>>
>> Yah, I might have some luck with that.  Since I'm years out of practice
>> fooling with this stuff (last seen in 2002) can someone point me at the
>> tools for
>> 1) Computing a modeline (I understand the quality varies a lot)
>> 2) Configuring an xorg.conf
>>      
> Check out x11-apps/amlc -- it has an interactive modeline generator
> where you tell it the aspect ratio&  size of your screen and it spits
> out modelines for you.  You'll still need to fill in the
> HSync/VSync/Clock speed stuff.
>
>
>    

Does this help any?

Section "Screen"
     Identifier     "Screen0"
     Device         "Card0"
     Monitor        "Monitor0"
     Option         "DPMS" "TRUE"
     SubSection     "Display"
         Viewport    0 0
         Depth       24
         Modes      "1280x1024" "1024x768" "800x600"
     EndSubSection
     SubSection     "Display"
         Viewport    0 0
         Modes      "1280x1024" "1024x768" "800x600"
     EndSubSection
     SubSection     "Display"
         Viewport    0 0
         Depth       4
         Modes      "1280x1024" "1024x768" "800x600"
     EndSubSection
     SubSection     "Display"
         Viewport    0 0
         Depth       8
         Modes      "1280x1024" "1024x768" "800x600"
     EndSubSection

That's just a part of my xorg.conf.  I don't use hal and don't like udev 
doing mine so I still got my full xorg.conf file.  If you need more, 
just let me know.  Heck, I'll post the whole thing if it will help you any.

Also, have you tried running "X -configure" yet?  I used it on another 
machine and it worked pretty well.

Dale

:-)  :-)

Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[Paul Hartman]

On Tue, Aug 24, 2010 at 5:37 PM, Dale <rdalek1967@gmail.com> wrote:
> Paul Hartman wrote:
>>
>> On Tue, Aug 24, 2010 at 5:07 PM, Kevin O'Gorman<kogorman@gmail.com>
>>  wrote:
>>
>>>
>>> Yah, I might have some luck with that.  Since I'm years out of practice
>>> fooling with this stuff (last seen in 2002) can someone point me at the
>>> tools for
>>> 1) Computing a modeline (I understand the quality varies a lot)
>>> 2) Configuring an xorg.conf
>>>
>>
>> Check out x11-apps/amlc -- it has an interactive modeline generator
>> where you tell it the aspect ratio&  size of your screen and it spits
>> out modelines for you.  You'll still need to fill in the
>> HSync/VSync/Clock speed stuff.
>>
>>
>>
>
> Does this help any?
>
> Section "Screen"
>    Identifier     "Screen0"
>    Device         "Card0"
>    Monitor        "Monitor0"
>    Option         "DPMS" "TRUE"
>    SubSection     "Display"
>        Viewport    0 0
>        Depth       24
>        Modes      "1280x1024" "1024x768" "800x600"
>    EndSubSection
>    SubSection     "Display"
>        Viewport    0 0
>        Modes      "1280x1024" "1024x768" "800x600"
>    EndSubSection
>    SubSection     "Display"
>        Viewport    0 0
>        Depth       4
>        Modes      "1280x1024" "1024x768" "800x600"
>    EndSubSection
>    SubSection     "Display"
>        Viewport    0 0
>        Depth       8
>        Modes      "1280x1024" "1024x768" "800x600"
>    EndSubSection
>
> That's just a part of my xorg.conf.  I don't use hal and don't like udev
> doing mine so I still got my full xorg.conf file.  If you need more, just
> let me know.  Heck, I'll post the whole thing if it will help you any.
>
> Also, have you tried running "X -configure" yet?  I used it on another
> machine and it worked pretty well.
>
> Dale

After creating a basic xorg.conf the modeline should go in the
"Monitor" section. I don't use a modeline now but the only example I
have from my xorg.conf archives are these:

Section "Monitor"
  # 2048x1152 @ 50.00 Hz (GTF) hsync: 59.30 kHz; pclk: 162.24 MHz
  Modeline "2048x1152_50.00"  162.24  2048 2176 2392 2736  1152 1153
1156 1186  -HSync +Vsync
  # 2048x1152 @ 60.00 Hz (GTF) hsync: 71.52 kHz; pclk: 197.97 MHz
  Modeline "2048x1152_60.00"  197.97  2048 2184 2408 2768  1152 1153
1156 1192  -HSync +Vsync
EndSection

And then in the Screen section like Dale posted you'd use for example
"2048x1152_60.00" as your modeline (or whatever you decided to entitle
your modes).

At least that's how it used to work. With modern video cards & modern
Xorg/Gnome/KDE it does a pretty good job of autodetecting that kind of
thing so I haven't had to worry about it in a long time. :)

Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[dhk]

On 08/24/2010 06:59 PM, Paul Hartman wrote:
> On Tue, Aug 24, 2010 at 5:37 PM, Dale <rdalek1967@gmail.com> wrote:
>> Paul Hartman wrote:
>>>
>>> On Tue, Aug 24, 2010 at 5:07 PM, Kevin O'Gorman<kogorman@gmail.com>
>>>  wrote:
>>>
>>>>
>>>> Yah, I might have some luck with that.  Since I'm years out of practice
>>>> fooling with this stuff (last seen in 2002) can someone point me at the
>>>> tools for
>>>> 1) Computing a modeline (I understand the quality varies a lot)
>>>> 2) Configuring an xorg.conf
>>>>
>>>
>>> Check out x11-apps/amlc -- it has an interactive modeline generator
>>> where you tell it the aspect ratio&  size of your screen and it spits
>>> out modelines for you.  You'll still need to fill in the
>>> HSync/VSync/Clock speed stuff.
>>>
>>>
>>>
>>
>> Does this help any?
>>
>> Section "Screen"
>>    Identifier     "Screen0"
>>    Device         "Card0"
>>    Monitor        "Monitor0"
>>    Option         "DPMS" "TRUE"
>>    SubSection     "Display"
>>        Viewport    0 0
>>        Depth       24
>>        Modes      "1280x1024" "1024x768" "800x600"
>>    EndSubSection
>>    SubSection     "Display"
>>        Viewport    0 0
>>        Modes      "1280x1024" "1024x768" "800x600"
>>    EndSubSection
>>    SubSection     "Display"
>>        Viewport    0 0
>>        Depth       4
>>        Modes      "1280x1024" "1024x768" "800x600"
>>    EndSubSection
>>    SubSection     "Display"
>>        Viewport    0 0
>>        Depth       8
>>        Modes      "1280x1024" "1024x768" "800x600"
>>    EndSubSection
>>
>> That's just a part of my xorg.conf.  I don't use hal and don't like udev
>> doing mine so I still got my full xorg.conf file.  If you need more, just
>> let me know.  Heck, I'll post the whole thing if it will help you any.
>>
>> Also, have you tried running "X -configure" yet?  I used it on another
>> machine and it worked pretty well.
>>
>> Dale
> 
> After creating a basic xorg.conf the modeline should go in the
> "Monitor" section. I don't use a modeline now but the only example I
> have from my xorg.conf archives are these:
> 
> Section "Monitor"
>   # 2048x1152 @ 50.00 Hz (GTF) hsync: 59.30 kHz; pclk: 162.24 MHz
>   Modeline "2048x1152_50.00"  162.24  2048 2176 2392 2736  1152 1153
> 1156 1186  -HSync +Vsync
>   # 2048x1152 @ 60.00 Hz (GTF) hsync: 71.52 kHz; pclk: 197.97 MHz
>   Modeline "2048x1152_60.00"  197.97  2048 2184 2408 2768  1152 1153
> 1156 1192  -HSync +Vsync
> EndSection
> 
> And then in the Screen section like Dale posted you'd use for example
> "2048x1152_60.00" as your modeline (or whatever you decided to entitle
> your modes).
> 
> At least that's how it used to work. With modern video cards & modern
> Xorg/Gnome/KDE it does a pretty good job of autodetecting that kind of
> thing so I haven't had to worry about it in a long time. :)
> 
> 

My monitor resolution is a little off after the last Xorg upgrade today.
 Everything looks larger than usual.  As far as this email thread goes,
I thought xorg.conf was obsolete.

Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[Kevin O'Gorman]

[-- Attachment #1: Type: text/plain, Size: 1243 bytes --]

On Tue, Aug 24, 2010 at 4:10 PM, dhk <dhkuhl@optonline.net> wrote:

> On 08/24/2010 06:59 PM, Paul Hartman wrote:
> > On Tue, Aug 24, 2010 at 5:37 PM, Dale <rdalek1967@gmail.com> wrote:
> >> Paul Hartman wrote:
> >>>
> >>> On Tue, Aug 24, 2010 at 5:07 PM, Kevin O'Gorman<kogorman@gmail.com>
> >>>  wrote:
> >>>
> >>>>
> >>>> Yah, I might have some luck with that.  Since I'm years out of
> practice
> >>>> fooling with this stuff (last seen in 2002) can someone point me at
> the
> >>>> tools for
> >>>> 1) Computing a modeline (I understand the quality varies a lot)
> >>>> 2) Configuring an xorg.conf
> >>>>
> >>>
> >>> Check out x11-apps/amlc -- it has an interactive modeline generator
> >>> where you tell it the aspect ratio&  size of your screen and it spits
> >>> out modelines for you.  You'll still need to fill in the
> >>> HSync/VSync/Clock speed stuff.
>

 [SNIP]


> My monitor resolution is a little off after the last Xorg upgrade today.
>  Everything looks larger than usual.  As far as this email thread goes,
> I thought xorg.conf was obsolete.
>
>
It should be obsolete in a modern system (if you trust hal, udev, etc.), but
the relevant parts include the video card which is very much non-modern.

-- 
Kevin O'Gorman, PhD

[-- Attachment #2: Type: text/html, Size: 2376 bytes --]

Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[Dale]

dhk wrote:
> On 08/24/2010 06:59 PM, Paul Hartman wrote:
>    
>> On Tue, Aug 24, 2010 at 5:37 PM, Dale<rdalek1967@gmail.com>  wrote:
>>      
>>> Paul Hartman wrote:
>>>        
>>>> On Tue, Aug 24, 2010 at 5:07 PM, Kevin O'Gorman<kogorman@gmail.com>
>>>>   wrote:
>>>>
>>>>          
>>>>> Yah, I might have some luck with that.  Since I'm years out of practice
>>>>> fooling with this stuff (last seen in 2002) can someone point me at the
>>>>> tools for
>>>>> 1) Computing a modeline (I understand the quality varies a lot)
>>>>> 2) Configuring an xorg.conf
>>>>>
>>>>>            
>>>> Check out x11-apps/amlc -- it has an interactive modeline generator
>>>> where you tell it the aspect ratio&   size of your screen and it spits
>>>> out modelines for you.  You'll still need to fill in the
>>>> HSync/VSync/Clock speed stuff.
>>>>
>>>>
>>>>
>>>>          
>>> Does this help any?
>>>
>>> Section "Screen"
>>>     Identifier     "Screen0"
>>>     Device         "Card0"
>>>     Monitor        "Monitor0"
>>>     Option         "DPMS" "TRUE"
>>>     SubSection     "Display"
>>>         Viewport    0 0
>>>         Depth       24
>>>         Modes      "1280x1024" "1024x768" "800x600"
>>>     EndSubSection
>>>     SubSection     "Display"
>>>         Viewport    0 0
>>>         Modes      "1280x1024" "1024x768" "800x600"
>>>     EndSubSection
>>>     SubSection     "Display"
>>>         Viewport    0 0
>>>         Depth       4
>>>         Modes      "1280x1024" "1024x768" "800x600"
>>>     EndSubSection
>>>     SubSection     "Display"
>>>         Viewport    0 0
>>>         Depth       8
>>>         Modes      "1280x1024" "1024x768" "800x600"
>>>     EndSubSection
>>>
>>> That's just a part of my xorg.conf.  I don't use hal and don't like udev
>>> doing mine so I still got my full xorg.conf file.  If you need more, just
>>> let me know.  Heck, I'll post the whole thing if it will help you any.
>>>
>>> Also, have you tried running "X -configure" yet?  I used it on another
>>> machine and it worked pretty well.
>>>
>>> Dale
>>>        
>> After creating a basic xorg.conf the modeline should go in the
>> "Monitor" section. I don't use a modeline now but the only example I
>> have from my xorg.conf archives are these:
>>
>> Section "Monitor"
>>    # 2048x1152 @ 50.00 Hz (GTF) hsync: 59.30 kHz; pclk: 162.24 MHz
>>    Modeline "2048x1152_50.00"  162.24  2048 2176 2392 2736  1152 1153
>> 1156 1186  -HSync +Vsync
>>    # 2048x1152 @ 60.00 Hz (GTF) hsync: 71.52 kHz; pclk: 197.97 MHz
>>    Modeline "2048x1152_60.00"  197.97  2048 2184 2408 2768  1152 1153
>> 1156 1192  -HSync +Vsync
>> EndSection
>>
>> And then in the Screen section like Dale posted you'd use for example
>> "2048x1152_60.00" as your modeline (or whatever you decided to entitle
>> your modes).
>>
>> At least that's how it used to work. With modern video cards&  modern
>> Xorg/Gnome/KDE it does a pretty good job of autodetecting that kind of
>> thing so I haven't had to worry about it in a long time. :)
>>
>>
>>      
> My monitor resolution is a little off after the last Xorg upgrade today.
>   Everything looks larger than usual.  As far as this email thread goes,
> I thought xorg.conf was obsolete.
>
>    

It is if you can use udev and hal to sort out things.  Only thing is, if 
hal or udev doesn't work, you are stuck with using xorg.conf.  As some 
may know here, hal didn't work for me.  It was good at locking up my 
keyboard and mouse tho.  At one point, even the SysRq key wouldn't work.

I don't know where but I also read where someone had trouble with a LCD 
screen one time.  It would work on a console but no GUI.  They had to 
use a xorg.conf file to set the display up properly so that it would 
work.  Hal works for most people  but doesn't for others.  Then some 
others can do some minor tweaking and get it to work.

I wouldn't even think of trying to tell someone how to tweak hal's 
config file.  It's in xml and I can't read that.

I did find this link which may help.  The part at the bottom is what I 
think you need.

http://howto-pages.org/ModeLines/

Hope that helps.

Dale

:-)  :-)

Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[dhk]

On 08/24/2010 08:07 PM, Dale wrote:
> dhk wrote:
>> On 08/24/2010 06:59 PM, Paul Hartman wrote:
>>   
>>> On Tue, Aug 24, 2010 at 5:37 PM, Dale<rdalek1967@gmail.com>  wrote:
>>>     
>>>> Paul Hartman wrote:
>>>>       
>>>>> On Tue, Aug 24, 2010 at 5:07 PM, Kevin O'Gorman<kogorman@gmail.com>
>>>>>   wrote:
>>>>>
>>>>>         
>>>>>> Yah, I might have some luck with that.  Since I'm years out of
>>>>>> practice
>>>>>> fooling with this stuff (last seen in 2002) can someone point me
>>>>>> at the
>>>>>> tools for
>>>>>> 1) Computing a modeline (I understand the quality varies a lot)
>>>>>> 2) Configuring an xorg.conf
>>>>>>
>>>>>>            
>>>>> Check out x11-apps/amlc -- it has an interactive modeline generator
>>>>> where you tell it the aspect ratio&   size of your screen and it spits
>>>>> out modelines for you.  You'll still need to fill in the
>>>>> HSync/VSync/Clock speed stuff.
>>>>>
>>>>>
>>>>>
>>>>>          
>>>> Does this help any?
>>>>
>>>> Section "Screen"
>>>>     Identifier     "Screen0"
>>>>     Device         "Card0"
>>>>     Monitor        "Monitor0"
>>>>     Option         "DPMS" "TRUE"
>>>>     SubSection     "Display"
>>>>         Viewport    0 0
>>>>         Depth       24
>>>>         Modes      "1280x1024" "1024x768" "800x600"
>>>>     EndSubSection
>>>>     SubSection     "Display"
>>>>         Viewport    0 0
>>>>         Modes      "1280x1024" "1024x768" "800x600"
>>>>     EndSubSection
>>>>     SubSection     "Display"
>>>>         Viewport    0 0
>>>>         Depth       4
>>>>         Modes      "1280x1024" "1024x768" "800x600"
>>>>     EndSubSection
>>>>     SubSection     "Display"
>>>>         Viewport    0 0
>>>>         Depth       8
>>>>         Modes      "1280x1024" "1024x768" "800x600"
>>>>     EndSubSection
>>>>
>>>> That's just a part of my xorg.conf.  I don't use hal and don't like
>>>> udev
>>>> doing mine so I still got my full xorg.conf file.  If you need more,
>>>> just
>>>> let me know.  Heck, I'll post the whole thing if it will help you any.
>>>>
>>>> Also, have you tried running "X -configure" yet?  I used it on another
>>>> machine and it worked pretty well.
>>>>
>>>> Dale
>>>>        
>>> After creating a basic xorg.conf the modeline should go in the
>>> "Monitor" section. I don't use a modeline now but the only example I
>>> have from my xorg.conf archives are these:
>>>
>>> Section "Monitor"
>>>    # 2048x1152 @ 50.00 Hz (GTF) hsync: 59.30 kHz; pclk: 162.24 MHz
>>>    Modeline "2048x1152_50.00"  162.24  2048 2176 2392 2736  1152 1153
>>> 1156 1186  -HSync +Vsync
>>>    # 2048x1152 @ 60.00 Hz (GTF) hsync: 71.52 kHz; pclk: 197.97 MHz
>>>    Modeline "2048x1152_60.00"  197.97  2048 2184 2408 2768  1152 1153
>>> 1156 1192  -HSync +Vsync
>>> EndSection
>>>
>>> And then in the Screen section like Dale posted you'd use for example
>>> "2048x1152_60.00" as your modeline (or whatever you decided to entitle
>>> your modes).
>>>
>>> At least that's how it used to work. With modern video cards&  modern
>>> Xorg/Gnome/KDE it does a pretty good job of autodetecting that kind of
>>> thing so I haven't had to worry about it in a long time. :)
>>>
>>>
>>>      
>> My monitor resolution is a little off after the last Xorg upgrade today.
>>   Everything looks larger than usual.  As far as this email thread goes,
>> I thought xorg.conf was obsolete.
>>
>>    
> 
> It is if you can use udev and hal to sort out things.  Only thing is, if
> hal or udev doesn't work, you are stuck with using xorg.conf.  As some
> may know here, hal didn't work for me.  It was good at locking up my
> keyboard and mouse tho.  At one point, even the SysRq key wouldn't work.
> 
> I don't know where but I also read where someone had trouble with a LCD
> screen one time.  It would work on a console but no GUI.  They had to
> use a xorg.conf file to set the display up properly so that it would
> work.  Hal works for most people  but doesn't for others.  Then some
> others can do some minor tweaking and get it to work.
> 
> I wouldn't even think of trying to tell someone how to tweak hal's
> config file.  It's in xml and I can't read that.
> 
> I did find this link which may help.  The part at the bottom is what I
> think you need.
> 
> http://howto-pages.org/ModeLines/
> 
> Hope that helps.
> 
> Dale
> 
> :-)  :-)
> 
> 

We'll I have an LCD screen that stopped displaying correctly yesterday
after the Xorg update.  It's not terrible, but not like it was.  I may
have to use xorg.conf now.

Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[Kevin O'Gorman]

[-- Attachment #1: Type: text/plain, Size: 696 bytes --]

On Tue, Aug 24, 2010 at 3:18 PM, Paul Hartman
<paul.hartman+gentoo@gmail.com<paul.hartman%2Bgentoo@gmail.com>
> wrote:

> On Tue, Aug 24, 2010 at 5:07 PM, Kevin O'Gorman <kogorman@gmail.com>
> wrote:
> > On Tue, Aug 24, 2010 at 11:48 AM, Paul Hartman
>
> [major snippage]


> Check out x11-apps/amlc -- it has an interactive modeline generator
> where you tell it the aspect ratio & size of your screen and it spits
> out modelines for you.  You'll still need to fill in the
> HSync/VSync/Clock speed stuff.
>
>
I found the specs with Hsync and VSync limits, but they don't mention the
clock speed.  I guess I'll just have to fool with it until it works or
catches fire.

-- 
Kevin O'Gorman, PhD

[-- Attachment #2: Type: text/html, Size: 1286 bytes --]

Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[Paul Hartman]

On Tue, Aug 24, 2010 at 7:03 PM, Kevin O'Gorman <kogorman@gmail.com> wrote:
> I found the specs with Hsync and VSync limits, but they don't mention the
> clock speed.  I guess I'll just have to fool with it until it works or
> catches fire.

That basically describes the way I've done my X monitor settings for
the past 10 years or so. I just made up a bunch of numbers and hope
they accidentally work. :) Now I'm thankful for EDID in monitors and
smarter video drivers.

Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[Mick]

On 25 August 2010 15:17, Paul Hartman <paul.hartman+gentoo@gmail.com> wrote:
> On Tue, Aug 24, 2010 at 7:03 PM, Kevin O'Gorman <kogorman@gmail.com> wrote:
>> I found the specs with Hsync and VSync limits, but they don't mention the
>> clock speed.  I guess I'll just have to fool with it until it works or
>> catches fire.
>
> That basically describes the way I've done my X monitor settings for
> the past 10 years or so. I just made up a bunch of numbers and hope
> they accidentally work. :) Now I'm thankful for EDID in monitors and
> smarter video drivers.

I think that if xrandr -q does not show the resolution you are
seeking, then the video card or driver in question cannot provide it.
I'm not sure that feeding xorg any odd modeline will change things,
plus unlike a CRT monitor, LCDs only provide a clear image at their
native resolution (denoted by '+' in the xrandr list of resolutions)
-- 
Regards,
Mick

Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[Paul Hartman]

On Wed, Aug 25, 2010 at 9:25 AM, Mick <michaelkintzios@gmail.com> wrote:
> On 25 August 2010 15:17, Paul Hartman <paul.hartman+gentoo@gmail.com> wrote:
>> On Tue, Aug 24, 2010 at 7:03 PM, Kevin O'Gorman <kogorman@gmail.com> wrote:
>>> I found the specs with Hsync and VSync limits, but they don't mention the
>>> clock speed.  I guess I'll just have to fool with it until it works or
>>> catches fire.
>>
>> That basically describes the way I've done my X monitor settings for
>> the past 10 years or so. I just made up a bunch of numbers and hope
>> they accidentally work. :) Now I'm thankful for EDID in monitors and
>> smarter video drivers.
>
> I think that if xrandr -q does not show the resolution you are
> seeking, then the video card or driver in question cannot provide it.
> I'm not sure that feeding xorg any odd modeline will change things,
> plus unlike a CRT monitor, LCDs only provide a clear image at their
> native resolution (denoted by '+' in the xrandr list of resolutions)

I've been able to generate modelines in the past for all kinds of
crazy non-standard resolutions. I think the ones listed may be the
ones defined in the card's BIOS.

I just remembered about CVT, I think it's what I used to generate the
modelines I posted earlier. It is part of the x11-base/xorg-server
package and will generate the frequencies and everything for you based
on VESA standards. You simply give it X and Y resolution and it does
the rest. For example:

$ cvt 1280 720
# 1280x720 59.86 Hz (CVT 0.92M9) hsync: 44.77 kHz; pclk: 74.50 MHz
Modeline "1280x720_60.00"   74.50  1280 1344 1472 1664  720 723 728
748 -hsync +vsync

Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[Mick]

On 25 August 2010 15:38, Paul Hartman <paul.hartman+gentoo@gmail.com> wrote:
> On Wed, Aug 25, 2010 at 9:25 AM, Mick <michaelkintzios@gmail.com> wrote:
>> On 25 August 2010 15:17, Paul Hartman <paul.hartman+gentoo@gmail.com> wrote:
>>> On Tue, Aug 24, 2010 at 7:03 PM, Kevin O'Gorman <kogorman@gmail.com> wrote:
>>>> I found the specs with Hsync and VSync limits, but they don't mention the
>>>> clock speed.  I guess I'll just have to fool with it until it works or
>>>> catches fire.
>>>
>>> That basically describes the way I've done my X monitor settings for
>>> the past 10 years or so. I just made up a bunch of numbers and hope
>>> they accidentally work. :) Now I'm thankful for EDID in monitors and
>>> smarter video drivers.
>>
>> I think that if xrandr -q does not show the resolution you are
>> seeking, then the video card or driver in question cannot provide it.
>> I'm not sure that feeding xorg any odd modeline will change things,
>> plus unlike a CRT monitor, LCDs only provide a clear image at their
>> native resolution (denoted by '+' in the xrandr list of resolutions)
>
> I've been able to generate modelines in the past for all kinds of
> crazy non-standard resolutions. I think the ones listed may be the
> ones defined in the card's BIOS.
>
> I just remembered about CVT, I think it's what I used to generate the
> modelines I posted earlier. It is part of the x11-base/xorg-server
> package and will generate the frequencies and everything for you based
> on VESA standards. You simply give it X and Y resolution and it does
> the rest. For example:
>
> $ cvt 1280 720
> # 1280x720 59.86 Hz (CVT 0.92M9) hsync: 44.77 kHz; pclk: 74.50 MHz
> Modeline "1280x720_60.00"   74.50  1280 1344 1472 1664  720 723 728
> 748 -hsync +vsync

Fair enough, but anything other than the native resolution on an LCD
monitor will end looking distorted or blurred.
-- 
Regards,
Mick

Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[Paul Hartman]

On Wed, Aug 25, 2010 at 9:44 AM, Mick <michaelkintzios@gmail.com> wrote:
> On 25 August 2010 15:38, Paul Hartman <paul.hartman+gentoo@gmail.com> wrote:
>> On Wed, Aug 25, 2010 at 9:25 AM, Mick <michaelkintzios@gmail.com> wrote:
>>> On 25 August 2010 15:17, Paul Hartman <paul.hartman+gentoo@gmail.com> wrote:
>>>> On Tue, Aug 24, 2010 at 7:03 PM, Kevin O'Gorman <kogorman@gmail.com> wrote:
>>>>> I found the specs with Hsync and VSync limits, but they don't mention the
>>>>> clock speed.  I guess I'll just have to fool with it until it works or
>>>>> catches fire.
>>>>
>>>> That basically describes the way I've done my X monitor settings for
>>>> the past 10 years or so. I just made up a bunch of numbers and hope
>>>> they accidentally work. :) Now I'm thankful for EDID in monitors and
>>>> smarter video drivers.
>>>
>>> I think that if xrandr -q does not show the resolution you are
>>> seeking, then the video card or driver in question cannot provide it.
>>> I'm not sure that feeding xorg any odd modeline will change things,
>>> plus unlike a CRT monitor, LCDs only provide a clear image at their
>>> native resolution (denoted by '+' in the xrandr list of resolutions)
>>
>> I've been able to generate modelines in the past for all kinds of
>> crazy non-standard resolutions. I think the ones listed may be the
>> ones defined in the card's BIOS.
>>
>> I just remembered about CVT, I think it's what I used to generate the
>> modelines I posted earlier. It is part of the x11-base/xorg-server
>> package and will generate the frequencies and everything for you based
>> on VESA standards. You simply give it X and Y resolution and it does
>> the rest. For example:
>>
>> $ cvt 1280 720
>> # 1280x720 59.86 Hz (CVT 0.92M9) hsync: 44.77 kHz; pclk: 74.50 MHz
>> Modeline "1280x720_60.00"   74.50  1280 1344 1472 1664  720 723 728
>> 748 -hsync +vsync
>
> Fair enough, but anything other than the native resolution on an LCD
> monitor will end looking distorted or blurred.

Of course, and I agree completely, but what I was going for was at
least he can get blurry 16:9 that fills the whole screen rather than
4:3 that is either stretched or leaves gaps on the sides. :)

Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[Kevin O'Gorman]

[-- Attachment #1: Type: text/plain, Size: 4834 bytes --]

On Wed, Aug 25, 2010 at 7:57 AM, Paul Hartman
<paul.hartman+gentoo@gmail.com<paul.hartman%2Bgentoo@gmail.com>
> wrote:

> On Wed, Aug 25, 2010 at 9:44 AM, Mick <michaelkintzios@gmail.com> wrote:
> > On 25 August 2010 15:38, Paul Hartman <paul.hartman+gentoo@gmail.com<paul.hartman%2Bgentoo@gmail.com>>
> wrote:
> >> On Wed, Aug 25, 2010 at 9:25 AM, Mick <michaelkintzios@gmail.com>
> wrote:
> >>> On 25 August 2010 15:17, Paul Hartman <paul.hartman+gentoo@gmail.com<paul.hartman%2Bgentoo@gmail.com>>
> wrote:
> >>>> On Tue, Aug 24, 2010 at 7:03 PM, Kevin O'Gorman <kogorman@gmail.com>
> wrote:
> >>>>> I found the specs with Hsync and VSync limits, but they don't mention
> the
> >>>>> clock speed.  I guess I'll just have to fool with it until it works
> or
> >>>>> catches fire.
> >>>>
> >>>> That basically describes the way I've done my X monitor settings for
> >>>> the past 10 years or so. I just made up a bunch of numbers and hope
> >>>> they accidentally work. :) Now I'm thankful for EDID in monitors and
> >>>> smarter video drivers.
> >>>
> >>> I think that if xrandr -q does not show the resolution you are
> >>> seeking, then the video card or driver in question cannot provide it.
> >>> I'm not sure that feeding xorg any odd modeline will change things,
> >>> plus unlike a CRT monitor, LCDs only provide a clear image at their
> >>> native resolution (denoted by '+' in the xrandr list of resolutions)
> >>
> >> I've been able to generate modelines in the past for all kinds of
> >> crazy non-standard resolutions. I think the ones listed may be the
> >> ones defined in the card's BIOS.
> >>
> >> I just remembered about CVT, I think it's what I used to generate the
> >> modelines I posted earlier. It is part of the x11-base/xorg-server
> >> package and will generate the frequencies and everything for you based
> >> on VESA standards. You simply give it X and Y resolution and it does
> >> the rest. For example:
> >>
> >> $ cvt 1280 720
> >> # 1280x720 59.86 Hz (CVT 0.92M9) hsync: 44.77 kHz; pclk: 74.50 MHz
> >> Modeline "1280x720_60.00"   74.50  1280 1344 1472 1664  720 723 728
> >> 748 -hsync +vsync
> >
> > Fair enough, but anything other than the native resolution on an LCD
> > monitor will end looking distorted or blurred.
>
> Of course, and I agree completely, but what I was going for was at
> least he can get blurry 16:9 that fills the whole screen rather than
> 4:3 that is either stretched or leaves gaps on the sides. :)
>
>
Precisely my goal when I started this thread.  In my case, native appears to
be 1920x1080.
With no xorg.conf, X finds 1280x1024, which is usable either stretched, or
with the gaps.
There is no discernable flicker, blur or distortion, just capacity that is
not being used.

There are some confusing things about this.
-  The log contains 1920x1080 modelines, but is not using them or clearly
stating the reason.
-  The log contains the lines
      (!!) MACH64(0): Virtual resolutions will be limited to 8191 kB
          due to linear aperture size and/or placement of hardware cursor
image area.

    I have no idea how to reconcile that with the fact that the resolution
being used results in
    1310720 (1.3 million) pixels, at 3 bytes (24 bits) per pixel, which
sounds to me like over
    3 megabytes.  The desired resolution would have 2073600 (2 million)
pixels and about
    6 megabytes.  They sound too big, but the first one actually works. I
don't understand this at all.

 - (--) MACH64(0): Internal programmable clock generator detected.
   (--) MACH64(0): Reference clock 157.5/11 (14.318) MHz.
   (II) MACH64(0): <default monitor>: Using hsync range of 30.00-85.00 kHz
   (II) MACH64(0): <default monitor>: Using vrefresh range of 55.00-75.00 Hz
   (II) MACH64(0): <default monitor>: Using maximum pixel clock of 160.00
MHz
   (II) MACH64(0): Estimated virtual size for aspect ratio 1.7931 is
1920x1080
                                  (this bothers me because, 1920/1080 is
more like 1.7777)
   (II) MACH64(0): Maximum clock: 120.00 MHz

So it's still contemplating 1920x1080,   but mentions both 120MHz and 160MHz
as the max
for pixel clock.  Anyway, for 2 million pixels, 120MHz is not going to cover
any overhead at 60 Hz, and 55Hz might not make it either.  Maybe the MACH64
cannot actually get above 120 MHz.  How to find out if that's what the log
is trying to say?

 - it complains about memory for 2048x1536, but not for anything smaller (I
don't think the monitor has that many pixels anyway.)  So I guess there's
memory enough for all the others. Instead it complains about many modelines
in this fashion (but showing just the last 2 lines)
      (II) MACH64(0): Not using driver mode "1920x1080" (bad mode
clock/interlace/doublescan)
      (WW) MACH64(0): Shrinking virtual size estimate from 1920x1080 to
1280x1024


-- 
Kevin O'Gorman, PhD

[-- Attachment #2: Type: text/html, Size: 5960 bytes --]

Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[Walter Dnes]

On Wed, Aug 25, 2010 at 01:29:29PM -0700, Kevin O'Gorman wrote

> There are some confusing things about this.
> -  The log contains 1920x1080 modelines, but is not using them or
> clearly stating the reason.
> -  The log contains the lines
>       (!!) MACH64(0): Virtual resolutions will be limited to 8191 kB
>       due to linear aperture size and/or placement of hardware cursor
>       image area.

  1920x1080 uses how many pixels?
$ echo $(( 1920 * 1080 ))
2073600

  The programmers writing X drivers use ***FOUR*** bytes per pixel for
24-bit colour.  This is due to double-word addressing being *MUCH*
easier and faster than sliding groups of 3 bytes per pixel.  This means
that to support 1920x1080 at 24 bits requires how many Kbytes...

$ echo $(( 1920 * 1080 * 4 / 1024 ))
8100

  It'll just barely squeeze in a 1920x1080 image, but forget about
acceleration or backing store, because there's almost no spare memory.
What you might want to try is forcing 16-bit colour, which would use
half the memory.  See http://www.gentoo.org/doc/en/xorg-config.xml

  The magic option is DefaultDepth.  You would want something like so,
the identifiers changed to match your setup...

Section "Screen"
  Identifier  "Default Screen"
  Device    "RadeonHD 4550"
  Monitor   "Generic Monitor"
  DefaultDepth  16
  # Skipping some text to improve readability
  SubSection "Display"
    Depth   16
    Modes   "1920x1080"
  EndSubSection
EndSection

  When viewing hi-res colour images, you may see some banding due to
the limited colourspace (64 K colours instead of 16 million), but it may
offer full pixel resolution, and the banding may not be noticable most
of the time.

-- 
Walter Dnes <waltdnes@waltdnes.org>

Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[Peter Humphrey]

On Wednesday 25 August 2010 15:44:58 Mick wrote:

> Fair enough, but anything other than the native resolution on an LCD
> monitor will end looking distorted or blurred.

Why? Granted, LCD panels are made up of discreet pixels, but so are 
CRTs: the dots are deposited in trios, each illuminated through a hole 
in the shadow mask.

-- 
Rgds
Peter.          Linux Counter 5290, 1994-04-23.

Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[Maciej Grela]

2010/8/25 Peter Humphrey <peter@humphrey.ukfsn.org>:
> On Wednesday 25 August 2010 15:44:58 Mick wrote:
>
>> Fair enough, but anything other than the native resolution on an LCD
>> monitor will end looking distorted or blurred.
>
> Why? Granted, LCD panels are made up of discreet pixels, but so are
> CRTs: the dots are deposited in trios, each illuminated through a hole
> in the shadow mask.

Right, but nature does a better job at upsampling an image than DSPs.

Br,
Maciej Grela

Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[Peter Humphrey]

On Wednesday 25 August 2010 17:39:15 Maciej Grela wrote:
> 2010/8/25 Peter Humphrey <peter@humphrey.ukfsn.org>:
> > On Wednesday 25 August 2010 15:44:58 Mick wrote:
> >> Fair enough, but anything other than the native resolution on an
> >> LCD monitor will end looking distorted or blurred.
> > 
> > Why? Granted, LCD panels are made up of discreet pixels, but so are
> > CRTs: the dots are deposited in trios, each illuminated through a
> > hole in the shadow mask.
> 
> Right, but nature does a better job at upsampling an image than DSPs.

Can't say I've noticed it, but then maybe my eyes aren't good enough to 
see the difference. They certainly aren't very good.

-- 
Rgds
Peter.          Linux Counter 5290, 1994-04-23.

Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[Maciej Grela]

2010/8/25 Peter Humphrey <peter@humphrey.ukfsn.org>:
> On Wednesday 25 August 2010 15:44:58 Mick wrote:
>
>> Fair enough, but anything other than the native resolution on an LCD
>> monitor will end looking distorted or blurred.
>
> Why? Granted, LCD panels are made up of discreet pixels, but so are
> CRTs: the dots are deposited in trios, each illuminated through a hole
> in the shadow mask.

Right, but nature does a better job at upsampling an image than DSPs.

Br,
Maciej Grela

Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[Alan McKinnon]

Apparently, though unproven, at 18:30 on Wednesday 25 August 2010, Peter 
Humphrey did opine thusly:

> On Wednesday 25 August 2010 15:44:58 Mick wrote:
> > Fair enough, but anything other than the native resolution on an LCD
> > monitor will end looking distorted or blurred.
> 
> Why? Granted, LCD panels are made up of discreet pixels, but so are
> CRTs: the dots are deposited in trios, each illuminated through a hole
> in the shadow mask.

That is incorrect.

A CRT display is not pixelated - it is made up of triads (not trios) and there 
is no way of knowing which triad is lit up for any given "logical pixel". The 
electron beam is an analogue signal and it works mainly because there are more 
triads than logical pixels.

LCDs on the other hand are pixelated. Each group of three display elements is 
addressable in a consistent fashion. 

CRTs and LCDs are about as different as cassette tapes and CDs, and just as 
incompatible. Both cases need lots of magic voodoo to arrive at some 
commonality.


-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[Adam Carter]

[-- Attachment #1: Type: text/plain, Size: 301 bytes --]

> I guess I've gotta look for a video card, but all I have is PCIX slots, so
> I don't want to put a lot of money into it (I'll be upgrading the mobo when
> finances permit -- which is not right now.)
>
>
"newer 3.3-volt PCI cards will work in a PCI-X slot" - from
http://en.wikipedia.org/wiki/PCI-X.

[-- Attachment #2: Type: text/html, Size: 557 bytes --]

Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[Håkon Alstadheim]

Den 24. aug. 2010 04:27, skrev Kevin O'Gorman:
> I had to replace an 4:3 Westinghouse monitor this weekend.  I got a 
> new ASUS VH242H, which is very wide.  But Xorg is still running 
> 1280x1024, instead of the monitor's normal 1920x1080, according to 
> xorg logs because of lack of video memory (using the ATI on the 
> motherboard).  I can make the screen use a 4:3 aspect ratio, so I'm up 
> and running, much better than I started, but I'd like to do better.
>
> I guess I've gotta look for a video card, but all I have is PCIX 
> slots, so I don't want to put a lot of money into it (I'll be 
> upgrading the mobo when finances permit -- which is not right now.)

Just did a cursory read of the entire thread here. I notice the card is 
on the mobo, did you try to see if there is a BIOS setting to increase 
the amount of video RAM? I.e enter BIOS setup during boot, and look 
around in the chip setup.

Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[Kevin O'Gorman]

[-- Attachment #1: Type: text/plain, Size: 1104 bytes --]

On Wed, Aug 25, 2010 at 1:48 PM, Håkon Alstadheim
<hakon@alstadheim.priv.no>wrote:

> Den 24. aug. 2010 04:27, skrev Kevin O'Gorman:
>
>  I had to replace an 4:3 Westinghouse monitor this weekend.  I got a new
>> ASUS VH242H, which is very wide.  But Xorg is still running 1280x1024,
>> instead of the monitor's normal 1920x1080, according to xorg logs because of
>> lack of video memory (using the ATI on the motherboard).  I can make the
>> screen use a 4:3 aspect ratio, so I'm up and running, much better than I
>> started, but I'd like to do better.
>>
>> I guess I've gotta look for a video card, but all I have is PCIX slots, so
>> I don't want to put a lot of money into it (I'll be upgrading the mobo when
>> finances permit -- which is not right now.)
>>
>
> Just did a cursory read of the entire thread here. I notice the card is on
> the mobo, did you try to see if there is a BIOS setting to increase the
> amount of video RAM? I.e enter BIOS setup during boot, and look around in
> the chip setup.
>

Hmmmmmmmmmmmmmmm.   Be right back.


-- 
Kevin O'Gorman, PhD

[-- Attachment #2: Type: text/html, Size: 1562 bytes --]

Re: [gentoo-user] New HD monitor stretches everything. How to teach Xorg?

[Kevin O'Gorman]

[-- Attachment #1: Type: text/plain, Size: 1420 bytes --]

On Wed, Aug 25, 2010 at 1:56 PM, Kevin O'Gorman <kogorman@gmail.com> wrote:

> On Wed, Aug 25, 2010 at 1:48 PM, Håkon Alstadheim <
> hakon@alstadheim.priv.no> wrote:
>
>> Den 24. aug. 2010 04:27, skrev Kevin O'Gorman:
>>
>>  I had to replace an 4:3 Westinghouse monitor this weekend.  I got a new
>>> ASUS VH242H, which is very wide.  But Xorg is still running 1280x1024,
>>> instead of the monitor's normal 1920x1080, according to xorg logs because of
>>> lack of video memory (using the ATI on the motherboard).  I can make the
>>> screen use a 4:3 aspect ratio, so I'm up and running, much better than I
>>> started, but I'd like to do better.
>>>
>>> I guess I've gotta look for a video card, but all I have is PCIX slots,
>>> so I don't want to put a lot of money into it (I'll be upgrading the mobo
>>> when finances permit -- which is not right now.)
>>>
>>
>> Just did a cursory read of the entire thread here. I notice the card is on
>> the mobo, did you try to see if there is a BIOS setting to increase the
>> amount of video RAM? I.e enter BIOS setup during boot, and look around in
>> the chip setup.
>>
>
> Hmmmmmmmmmmmmmmm.   Be right back.
>
> Well, it was an interesting thought, but no joy.  Lots of configuration
things showed up -- I didn't
realize I did not have the ECC memory to alert on uncorrectable errors, so
it wasn't all a waste.


-- 
Kevin O'Gorman, PhD

[-- Attachment #2: Type: text/html, Size: 2175 bytes --]