Unix Technical Forum

SEO

vBulletin Search Engine Optimization


Go Back   Unix Technical Forum > Unix Operating Systems > Debian Linux > Debian Linux support

Register FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 04-07-2008, 08:33 AM
John F. Morse
 
Posts: n/a
Default X.Org vs XFree86

Most of my GNU/Linux installations use Debian 3.1, with older Ubuntu,
Fedora Core, Lindows, Mandrake, Red Hat, Slackware, etc. IIRC, these all
use XFree86, and I had to learn to fine-tune it over the years.

Debian 4.0 uses X.Org.

I presently have a "portable" ViewSonic 21 monitor plugged into one
Debian box, which I have recently upgraded from Sarge to Etch, and now
cannot get a higher resolution than 640x480. This is, of course, a
ridiculous resolution for a 21" screen.

Even trying other multiscan/multifrequency 17" and "dumb" 15" monitors
will not allow any resolution change.

To make matters worse, the detected Trident video card causes a failure
when xorg tries to initialize a screen.

Of course the TTY terminals all work, so I do have access to vi for
xorg.conf edits. The only method I've found to startx for a GUI DE is to
manually edit xorg.conf and replace "trident" with "vesa" as the driver.

Running "dpkg-reconfigure -phigh xorg-server" will only rebuild
xorg.conf back to the detected trident driver.

The monitor frequency rates also makes no difference if I edit xorg.conf
and change them to the correct values for the monitor.

The Trident video card has sufficient memory, and is used in eleven
other identical PCs which run Debian Sarge fine under XFree86. However
Sarge support is ending so I must upgrade to Etch as time permits.

Below is the total /var/log/Xorg.0.log for examination (the font
problems are of no concern).

Perhaps someone has an idea that I might try? The xorg.conf can also be
posted if requested.

These Debian servers all run headless anyway, but at this point in time,
I'd certainly like to find and resolve this X.Org resolution problem.

TIA.


X Window System Version 7.1.1
Release Date: 12 May 2006
X Protocol Version 11, Revision 0, Release 7.1.1
Build Operating System: UNKNOWN
Current Operating System: Linux optima12 2.6.18-4-486 #1 Mon Mar 26
16:39:10 UTC 2007 i586
Build Date: 24 January 2008
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
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: Tue Apr 1 01:42:25 2008
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Default Layout"
(**) |-->Screen "Default Screen" (0)
(**) | |-->Monitor "Generic Monitor"
(**) | |-->Device "Trident Microsystems TGUI 9660/938x/968x"
(**) |-->Input Device "Generic Keyboard"
(**) |-->Input Device "Configured Mouse"
(WW) The directory "/usr/X11R6/lib/X11/fonts/misc" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/X11R6/lib/X11/fonts/cyrillic" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/X11R6/lib/X11/fonts/100dpi/" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/X11R6/lib/X11/fonts/75dpi/" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/X11R6/lib/X11/fonts/Type1" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/X11R6/lib/X11/fonts/100dpi" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/X11R6/lib/X11/fonts/75dpi" does not exist.
Entry deleted from font path.
(WW) The directory "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
does not exist.
Entry deleted from font path.
(**) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi
(==) RgbPath set to "/etc/X11/rgb"
(==) ModulePath set to "/usr/lib/xorg/modules"
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.3
X.Org Video Driver: 1.0
X.Org XInput driver : 0.6
X.Org Server Extension : 0.3
X.Org Font Renderer : 0.5
(II) Loader running on linux
(II) LoadModule: "bitmap"
(II) Loading /usr/lib/xorg/modules/fonts/libbitmap.so
(II) Module bitmap: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.0.0
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.5
(II) Loading font Bitmap
(II) LoadModule: "pcidata"
(II) Loading /usr/lib/xorg/modules/libpcidata.so
(II) Module pcidata: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.0.0
ABI class: X.Org Video Driver, version 1.0
(++) using VT number 7

(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 8086,7100 card 0000,0000 rev 01 class 06,00,00
hdr 00
(II) PCI: 00:07:0: chip 8086,7110 card 0000,0000 rev 01 class 06,01,00
hdr 80
(II) PCI: 00:07:1: chip 8086,7111 card 0000,0000 rev 01 class 01,01,80
hdr 00
(II) PCI: 00:07:2: chip 8086,7112 card 0000,0000 rev 01 class 0c,03,00
hdr 00
(II) PCI: 00:07:3: chip 8086,7113 card 0000,0000 rev 01 class 06,80,00
hdr 00
(II) PCI: 00:08:0: chip 1274,5880 card 1274,2000 rev 02 class 04,01,00
hdr 00
(II) PCI: 00:09:0: chip 10ec,8139 card a0a0,0027 rev 10 class 02,00,00
hdr 00
(II) PCI: 00:0a:0: chip 1023,9660 card 0000,0000 rev d3 class 03,00,00
hdr 00
(II) PCI: End of PCI scan
(II) Host-to-PCI bridge:
(II) Bus 0: bridge is at (0:0:0), (0,0,0), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 0 I/O range:
[0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[b]
(II) Bus 0 non-prefetchable memory range:
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[b]
(II) Bus 0 prefetchable memory range:
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[b]
(II) PCI-to-ISA bridge:
(II) Bus -1: bridge is at (0:7:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set)
(--) PCI:*(0:10:0) Trident Microsystems TGUI 9660/938x/968x rev 211, Mem
@ 0xff800000/22, 0xffef0000/16, BIOS @ 0xffee0000/16
(II) Addressable bus resource ranges are
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[b]
[1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[b]
(II) OS-reported resource ranges:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[5] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
(II) Active PCI resource ranges:
[0] -1 0 0xffedf800 - 0xffedf8ff (0x100) MX[b]
[1] -1 0 0xffee0000 - 0xffeeffff (0x10000) MX[b](B)
[2] -1 0 0xffef0000 - 0xffefffff (0x10000) MX[b](B)
[3] -1 0 0xff800000 - 0xffbfffff (0x400000) MX[b](B)
[4] -1 0 0x0000d800 - 0x0000d8ff (0x100) IX[b]
[5] -1 0 0x0000d000 - 0x0000d03f (0x40) IX[b]
[6] -1 0 0x0000ffa0 - 0x0000ffaf (0x10) IX[b]
(II) Inactive PCI resource ranges:
[0] -1 0 0x00004000 - 0x0000401f (0x20) IX[b]
(II) Active PCI resource ranges after removing overlaps:
[0] -1 0 0xffedf800 - 0xffedf8ff (0x100) MX[b]
[1] -1 0 0xffee0000 - 0xffeeffff (0x10000) MX[b](B)
[2] -1 0 0xffef0000 - 0xffefffff (0x10000) MX[b](B)
[3] -1 0 0xff800000 - 0xffbfffff (0x400000) MX[b](B)
[4] -1 0 0x0000d800 - 0x0000d8ff (0x100) IX[b]
[5] -1 0 0x0000d000 - 0x0000d03f (0x40) IX[b]
[6] -1 0 0x0000ffa0 - 0x0000ffaf (0x10) IX[b]
(II) Inactive PCI resource ranges after removing overlaps:
[0] -1 0 0x00004000 - 0x0000401f (0x20) IX[b]
(II) OS-reported resource ranges after removing overlaps with PCI:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[5] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
(II) All system resource ranges:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0xffedf800 - 0xffedf8ff (0x100) MX[b]
[5] -1 0 0xffee0000 - 0xffeeffff (0x10000) MX[b](B)
[6] -1 0 0xffef0000 - 0xffefffff (0x10000) MX[b](B)
[7] -1 0 0xff800000 - 0xffbfffff (0x400000) MX[b](B)
[8] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[9] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
[10] -1 0 0x0000d800 - 0x0000d8ff (0x100) IX[b]
[11] -1 0 0x0000d000 - 0x0000d03f (0x40) IX[b]
[12] -1 0 0x0000ffa0 - 0x0000ffaf (0x10) IX[b]
[13] -1 0 0x00004000 - 0x0000401f (0x20) IX[b]
(II) LoadModule: "i2c"
(II) Loading /usr/lib/xorg/modules/libi2c.so
(II) Module i2c: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.2.0
ABI class: X.Org Video Driver, version 1.0
(II) LoadModule: "bitmap"
(II) Reloading /usr/lib/xorg/modules/fonts/libbitmap.so
(II) Loading font Bitmap
(II) LoadModule: "ddc"
(II) Loading /usr/lib/xorg/modules/libddc.so
(II) Module ddc: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.0.0
ABI class: X.Org Video Driver, version 1.0
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions/libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(II) Loading sub module "drm"
(II) LoadModule: "drm"
(II) Loading /usr/lib/xorg/modules/linux/libdrm.so
(II) Module drm: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension XFree86-DRI
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "freetype"
(II) Loading /usr/lib/xorg/modules/fonts/libfreetype.so
(II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
compiled for 7.1.1, module version = 2.1.0
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.5
(II) Loading font FreeType
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions/libglx.so
(II) Module glx: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(==) AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "int10"
(II) Loading /usr/lib/xorg/modules/libint10.so
(II) Module int10: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.0.0
ABI class: X.Org Video Driver, version 1.0
(II) LoadModule: "vbe"
(II) Loading /usr/lib/xorg/modules/libvbe.so
(II) Module vbe: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.1.0
ABI class: X.Org Video Driver, version 1.0
(II) LoadModule: "trident"
(II) Loading /usr/lib/xorg/modules/drivers/trident_drv.so
(II) Module trident: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.2.3
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 1.0
(II) LoadModule: "kbd"
(II) Loading /usr/lib/xorg/modules/input/kbd_drv.so
(II) Module kbd: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.1.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.6
(II) LoadModule: "mouse"
(II) Loading /usr/lib/xorg/modules/input/mouse_drv.so
(II) Module mouse: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.1.1
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.6
(II) TRIDENT: driver for Trident chipsets: tvga9000, tvga9000i, tvga8900c,
tvga8900d, tvga9200cxr, tgui9400cxi, cyber9320, cyber9388, cyber9397,
cyber9397dvd, cyber9520, cyber9525dvd, cyberblade/e4, tgui9420dgi,
tgui9440agi, tgui9660, tgui9680, providia9682, providia9685,
cyber9382, cyber9385, 3dimage975, 3dimage985, blade3d, cyberbladei7,
cyberbladei7d, cyberbladei1, cyberbladei1d, cyberbladeAi1,
cyberbladeAi1d, bladeXP, cyberbladeXPAi1, cyberbladeXP4, XP5
(II) Primary Device is: PCI 00:0a:0
(--) Chipset tgui9660 found
(II) resource ranges after xf86ClaimFixedResources() call:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0xffedf800 - 0xffedf8ff (0x100) MX[b]
[5] -1 0 0xffee0000 - 0xffeeffff (0x10000) MX[b](B)
[6] -1 0 0xffef0000 - 0xffefffff (0x10000) MX[b](B)
[7] -1 0 0xff800000 - 0xffbfffff (0x400000) MX[b](B)
[8] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[9] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
[10] -1 0 0x0000d800 - 0x0000d8ff (0x100) IX[b]
[11] -1 0 0x0000d000 - 0x0000d03f (0x40) IX[b]
[12] -1 0 0x0000ffa0 - 0x0000ffaf (0x10) IX[b]
[13] -1 0 0x00004000 - 0x0000401f (0x20) IX[b]
(II) resource ranges after probing:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0xffedf800 - 0xffedf8ff (0x100) MX[b]
[5] -1 0 0xffee0000 - 0xffeeffff (0x10000) MX[b](B)
[6] -1 0 0xffef0000 - 0xffefffff (0x10000) MX[b](B)
[7] -1 0 0xff800000 - 0xffbfffff (0x400000) MX[b](B)
[8] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b]
[9] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b]
[10] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b]
[11] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[12] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
[13] -1 0 0x0000d800 - 0x0000d8ff (0x100) IX[b]
[14] -1 0 0x0000d000 - 0x0000d03f (0x40) IX[b]
[15] -1 0 0x0000ffa0 - 0x0000ffaf (0x10) IX[b]
[16] -1 0 0x00004000 - 0x0000401f (0x20) IX[b]
[17] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b]
[18] 0 0 0x000003c0 - 0x000003df (0x20) IS[b]
(II) Setting vga for screen 0.
(**) TRIDENT(0): Depth 24, (--) framebuffer bpp 32
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/lib/xorg/modules/libvgahw.so
(II) Module vgahw: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 0.1.0
ABI class: X.Org Video Driver, version 1.0
(II) TRIDENT(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset
is 0x0000
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Loading /usr/lib/xorg/modules/libramdac.so
(II) Module ramdac: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 0.1.0
ABI class: X.Org Video Driver, version 1.0
(==) TRIDENT(0): RGB weight 888
(==) TRIDENT(0): Default visual is TrueColor
(==) TRIDENT(0): Using gamma correction (1.0, 1.0, 1.0)
(==) TRIDENT(0): Using XAA for acceleration
(==) TRIDENT(0): Linear framebuffer at 0xFF800000
(--) TRIDENT(0): IO registers at 0xFFEF0000
(II) Loading sub module "vbe"
(II) LoadModule: "vbe"
(II) Reloading /usr/lib/xorg/modules/libvbe.so
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Reloading /usr/lib/xorg/modules/libint10.so
(II) TRIDENT(0): initializing int10
(II) Loading sub module "vm86"
(II) LoadModule: "vm86"
(II) Loading /usr/lib/xorg/modules/libvm86.so
(II) Module vm86: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.0.0
ABI class: X.Org Video Driver, version 1.0
(II) TRIDENT(0): Primary V_BIOS segment is: 0xc000
(WW) System lacks support for changing MTRRs
(II) TRIDENT(0): VESA BIOS detected
(II) TRIDENT(0): VESA VBE Version 1.2
(II) TRIDENT(0): VESA VBE Total Mem: 1024 kB
(II) TRIDENT(0): VESA VBE OEM: Trident TGUI96xx
(--) TRIDENT(0): Revision is 1
(--) TRIDENT(0): Found TGUI9680 chip
(--) TRIDENT(0): RAM type is EDO Ram
(--) TRIDENT(0): Using HW cursor
(--) TRIDENT(0): VideoRAM: 1024 kByte
(--) TRIDENT(0): Memory Clock is 42.95 MHz
(==) TRIDENT(0): Min pixel clock is 12 MHz
(--) TRIDENT(0): Max pixel clock is 40 MHz
(II) TRIDENT(0): Generic Monitor: Using hsync range of 28.00-80.00 kHz
(II) TRIDENT(0): Generic Monitor: Using vrefresh range of 43.00-60.00 Hz
(II) TRIDENT(0): Clock range: 12.00 to 40.00 MHz
(II) TRIDENT(0): Not using default mode "640x350" (vrefresh out of range)
(II) TRIDENT(0): Not using default mode "320x175" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using default mode "640x400" (vrefresh out of range)
(II) TRIDENT(0): Not using default mode "320x200" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using default mode "720x400" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "360x200" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using default mode "640x480" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "320x240" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using default mode "640x480" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "320x240" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using default mode "640x480" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "320x240" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using default mode "640x480" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "320x240" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using default mode "800x600" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "400x300" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using default mode "800x600" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "400x300" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using default mode "800x600" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "400x300" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using default mode "800x600" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "400x300" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using default mode "800x600" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "400x300" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using default mode "1024x768" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "512x384" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using default mode "1024x768" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "512x384" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using default mode "1024x768" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "512x384" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using default mode "1024x768" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "512x384" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using default mode "1024x768" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "512x384" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using default mode "1152x864" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "576x432" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using default mode "1280x960" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "640x480" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "1280x960" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "640x480" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "1280x1024" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "640x512" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "1280x1024" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "640x512" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "1280x1024" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "640x512" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "1600x1200" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "800x600" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "1600x1200" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "800x600" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "1600x1200" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "800x600" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "1600x1200" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "800x600" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "1600x1200" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "800x600" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "1792x1344" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "896x672" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "1792x1344" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "896x672" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "1856x1392" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "928x696" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "1856x1392" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "928x696" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "1920x1440" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "960x720" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "1920x1440" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "960x720" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "832x624" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "416x312" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using default mode "1280x768" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "640x384" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using default mode "1280x800" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "640x400" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using default mode "1152x768" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "576x384" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using default mode "1152x864" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "576x432" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using default mode "1400x1050" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "700x525" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "1400x1050" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "700x525" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "1400x1050" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "700x525" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "1400x1050" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "700x525" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "1440x900" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "720x450" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "1600x1024" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "800x512" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "1680x1050" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "840x525" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "1920x1200" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "960x600" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "1920x1200" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "960x600" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "1920x1440" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "960x720" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "2048x1536" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "1024x768" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "2048x1536" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "1024x768" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "2048x1536" (insufficient memory
for mode)
(II) TRIDENT(0): Not using default mode "1024x768" (insufficient memory
for mode)
(WW) TRIDENT(0): Mode pool is empty
(EE) TRIDENT(0): No valid modes found
(II) UnloadModule: "trident"
(II) UnloadModule: "vm86"
(II) Unloading /usr/lib/xorg/modules/libvm86.so
(II) UnloadModule: "int10"
(II) UnloadModule: "vbe"
(II) UnloadModule: "ramdac"
(II) Unloading /usr/lib/xorg/modules/libramdac.so
(II) UnloadModule: "vgahw"
(II) Unloading /usr/lib/xorg/modules/libvgahw.so
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found


--
John

No Microsoft, Apple, Intel, Trend Micro, nor Ford products were used in the preparation or transmission of this message.

The EULA sounds like it was written by a team of lawyers who want to tell me what I can't do. The GPL sounds like it was written by a human being, who wants me to know what I can do.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #2 (permalink)  
Old 04-07-2008, 08:33 AM
Mumia W.
 
Posts: n/a
Default Re: X.Org vs XFree86

On 04/03/2008 06:45 PM, John F. Morse wrote:
> Most of my GNU/Linux installations use Debian 3.1, with older Ubuntu,
> Fedora Core, Lindows, Mandrake, Red Hat, Slackware, etc. IIRC, these all
> use XFree86, and I had to learn to fine-tune it over the years.
>
> Debian 4.0 uses X.Org.
>
> I presently have a "portable" ViewSonic 21 monitor plugged into one
> Debian box, which I have recently upgraded from Sarge to Etch, and now
> cannot get a higher resolution than 640x480. This is, of course, a
> ridiculous resolution for a 21" screen.
>
> Even trying other multiscan/multifrequency 17" and "dumb" 15" monitors
> will not allow any resolution change.
>
> To make matters worse, the detected Trident video card causes a failure
> when xorg tries to initialize a screen.
>
> Of course the TTY terminals all work, so I do have access to vi for
> xorg.conf edits. The only method I've found to startx for a GUI DE is to
> manually edit xorg.conf and replace "trident" with "vesa" as the driver.
>
> Running "dpkg-reconfigure -phigh xorg-server" will only rebuild
> xorg.conf back to the detected trident driver.
>


Try this instead:
dpkg-reconfigure -plow xserver-xorg

> The monitor frequency rates also makes no difference if I edit xorg.conf
> and change them to the correct values for the monitor.
>


Well that confuses me, since that was going to be my first suggestion of
something to look into.

> The Trident video card has sufficient memory, and is used in eleven
> other identical PCs which run Debian Sarge fine under XFree86. However
> Sarge support is ending so I must upgrade to Etch as time permits.
>
> Below is the total /var/log/Xorg.0.log for examination (the font
> problems are of no concern).
>
> Perhaps someone has an idea that I might try? The xorg.conf can also be
> posted if requested.
>
> These Debian servers all run headless anyway, but at this point in time,
> I'd certainly like to find and resolve this X.Org resolution problem.
>
> TIA.
> [...]
>


Xorg reports 1024KiB of memory for your card--is this true?

Try to disable direct rendering for right now. You probably don't need
DRI on a server anyway.

Also, try to use a lower color depth; you're using 24 bits right now;
perhaps you need to change that to 16.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #3 (permalink)  
Old 04-07-2008, 08:33 AM
Steffen Pohle
 
Posts: n/a
Default Re: X.Org vs XFree86


Hi there,

I checked your logfile. First of all for a resolution with 800x600 by
24bit you need at last 1.4MB video memory. You can go down to 16bpp
which will give you a resolution of 800x600 pixel.

Another thing could you also send to here your xorg.conf file? That
would help to find the problem. Because it seems as if you have alot of
modelines configured. In xorg you shouldn't need anymore modelines, the
only thing you have to do is tell the server the frequencies of your
monitor and thats it.

Another thing is that the pixel clock can limitate your screen
resolution.

> (==) TRIDENT(0): Min pixel clock is 12 MHz
> (--) TRIDENT(0): Max pixel clock is 40 MHz
> (II) TRIDENT(0): Generic Monitor: Using hsync range of 28.00-80.00 kHz
> (II) TRIDENT(0): Generic Monitor: Using vrefresh range of 43.00-60.00 Hz
> (II) TRIDENT(0): Clock range: 12.00 to 40.00 MHz


Since 1024x786 by 60Hz makes around 48 MHz and the card only alows you to
set it to 40MHz.

bye bye,
Steffen

--
Steffen Pohle (stpohle@gmx.net)
http://stpohle.dyndns.org

***** Instant Messanger Contact ******
* Skype: stpohle Yahoo: stpohle *
* MSN: stpohle@hotmail.com *
**************************************


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFH9h2bj6xnrikWYrkRApSRAJ48YQxWxVRxvfFQN466tP/ZEDHdMQCfaUf1
s0YjotrC5Ah3pspUH0pE3AQ=
=IKUC
-----END PGP SIGNATURE-----

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #4 (permalink)  
Old 04-07-2008, 08:33 AM
sk8r-365
 
Posts: n/a
Default Re: X.Org vs XFree86

Thus spake Steffen Pohle:
<snip>
> In xorg you shouldn't need anymore modelines, the only thing you have
> to do is tell the server the frequencies of your monitor and thats it.

<snip>

Am I correct that LCD monitors don't use/require horizontal and vertical
rates?

--
sk8r-365
Take therefore the talent from him, and give it unto him which hath
ten talents. -- Matthew 25:28
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #5 (permalink)  
Old 04-07-2008, 08:33 AM
Dave Uhring
 
Posts: n/a
Default Re: X.Org vs XFree86

On Fri, 04 Apr 2008 18:58:40 -0500, sk8r-365 wrote:

> Thus spake Steffen Pohle:
> <snip>
>> In xorg you shouldn't need anymore modelines, the only thing you have
>> to do is tell the server the frequencies of your monitor and thats it.

> <snip>
>
> Am I correct that LCD monitors don't use/require horizontal and vertical
> rates?


I don't think so. Both of my have those specs and if not written into
xorg.conf the displays don't go to 1280x1024, except in Solaris.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #6 (permalink)  
Old 04-07-2008, 08:33 AM
John F. Morse
 
Posts: n/a
Default Re: X.Org vs XFree86

Mumia W. wrote:
> Try this instead:
> dpkg-reconfigure -plow xserver-xorg



Ah ha! That is the configure/reconfigure routine I remember in XFree86
for Sarge.

A few days ago after checking the man page, I took "high" priority to
mean it would ask everything. It actually means the opposite.

Thanks Mumia for making me try this "low" priority or I would have never
discovered this!

Of course these various responses can always be manually edited in
xorg.conf just like they were in the XF86Config-4 file, but it was good
to see the familiar monitor sync range settings.


>> The monitor frequency rates also makes no difference if I edit
>> xorg.conf and change them to the correct values for the monitor.

>
> Well that confuses me, since that was going to be my first suggestion
> of something to look into.
>
>> The Trident video card has sufficient memory, and is used in eleven
>> other identical PCs which run Debian Sarge fine under XFree86.
>> However Sarge support is ending so I must upgrade to Etch as time
>> permits.
>>
>> Below is the total /var/log/Xorg.0.log for examination (the font
>> problems are of no concern).
>>
>> Perhaps someone has an idea that I might try? The xorg.conf can also
>> be posted if requested.
>>
>> These Debian servers all run headless anyway, but at this point in
>> time, I'd certainly like to find and resolve this X.Org resolution
>> problem.
>>

>
> Xorg reports 1024KiB of memory for your card--is this true?



I can only go by the report. My old notes for this PC's video card also
mention 1024k.

However I did find that this is the only PC of the "identical" 13 I
originally purchased that has a Trident chipset on the video card. All
the others are ATI based, and seem to work fine (AFAIK). So my earlier
statement is incorrect.

If I can't make this Trident card work correctly, I could always swap it
with an ATI card that is in the single Windows 98SE PC. I don't really
need a GUI right now, but it is nice to have for some possible future use.


> Try to disable direct rendering for right now. You probably don't need
> DRI on a server anyway.
>
> Also, try to use a lower color depth; you're using 24 bits right now;
> perhaps you need to change that to 16.



Well, after trying your suggestions around 0400 this morning, nothing
has changed. Tonight I'm going to reduce the bit depth like Steffen
suggested and see if the problem is the video card's memory is too small.

Here's how she's configured after last night's work (including the
correct monitor info):


john@optima12:/etc/X11$ cat xorg.conf
# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the /etc/X11/xorg.conf manual page.
# (Type "man /etc/X11/xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "Files"
FontPath "/usr/share/fonts/X11/misc"
FontPath "/usr/X11R6/lib/X11/fonts/misc"
FontPath "/usr/share/fonts/X11/cyrillic"
FontPath "/usr/X11R6/lib/X11/fonts/cyrillic"
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
FontPath "/usr/share/fonts/X11/Type1"
FontPath "/usr/X11R6/lib/X11/fonts/Type1"
FontPath "/usr/share/fonts/X11/100dpi"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi"
FontPath "/usr/share/fonts/X11/75dpi"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi"
# path to defoma fonts
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection

Section "Module"
Load "bitmap"
Load "ddc"
Load "extmod"
Load "freetype"
Load "glx"
Load "int10"
Load "vbe"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc104"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/psaux"
Option "Protocol" "ImPS/2"
Option "Emulate3Buttons" "true"
EndSection

Section "Device"
Identifier "Trident Microsystems TGUI 9660/938x/968x"
Driver "trident"
BusID "PCI:0:10:0"
VideoRam 1024
EndSection

Section "Monitor"
Identifier "ViewSonic 21"
Option "DPMS"
HorizSync 30-82
VertRefresh 50-150
EndSection

Section "Screen"
Identifier "Default Screen"
Device "Trident Microsystems TGUI 9660/938x/968x"
Monitor "ViewSonic 21"
DefaultDepth 16
SubSection "Display"
Depth 1
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 4
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 15
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
EndSection

Section "DRI"
Mode 0666
EndSection
john@optima12:/etc/X11$


--
John

No Microsoft, Apple, Intel, Trend Micro, nor Ford products were used in the preparation or transmission of this message.

The EULA sounds like it was written by a team of lawyers who want to tell me what I can't do. The GPL sounds like it was written by a human being, who wants me to know what I can do.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #7 (permalink)  
Old 04-07-2008, 08:33 AM
sk8r-365
 
Posts: n/a
Default Re: X.Org vs XFree86

Thus spake Dave Uhring:
> On Fri, 04 Apr 2008 18:58:40 -0500, sk8r-365 wrote:
>
>> Thus spake Steffen Pohle:
>> <snip>
>>> In xorg you shouldn't need anymore modelines, the only thing you have
>>> to do is tell the server the frequencies of your monitor and thats it.

>> <snip>
>>
>> Am I correct that LCD monitors don't use/require horizontal and vertical
>> rates?

>
> I don't think so. Both of my have those specs and if not written into
> xorg.conf the displays don't go to 1280x1024, except in Solaris.


Hmm, I ask because it makes no difference on my setup. At least I can't
detect any benefit or harm as it is. Appears to work fine as is
currently edited:

Section "Monitor"
Identifier "Generic Monitor"
Option "DPMS"
#HorizSync 28-84
#VertRefresh 43-60

The monitor in use is a Samsung SyncMaster 205bw. What do you think?

--
sk8r-365
And saying, We have piped unto you, and ye have not danced; we have
mourned unto you, and ye have not lamented. -- Matthew 11:17
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #8 (permalink)  
Old 04-07-2008, 08:33 AM
John F. Morse
 
Posts: n/a
Default Re: X.Org vs XFree86

sk8r-365 wrote:
> Thus spake Dave Uhring:
>
>> On Fri, 04 Apr 2008 18:58:40 -0500, sk8r-365 wrote:
>>
>>
>>> Thus spake Steffen Pohle:
>>> <snip>
>>>
>>>> In xorg you shouldn't need anymore modelines, the only thing you have
>>>> to do is tell the server the frequencies of your monitor and thats it.
>>>>
>>> <snip>
>>>
>>> Am I correct that LCD monitors don't use/require horizontal and vertical
>>> rates?
>>>

>> I don't think so. Both of my have those specs and if not written into
>> xorg.conf the displays don't go to 1280x1024, except in Solaris.
>>

>
> Hmm, I ask because it makes no difference on my setup. At least I can't
> detect any benefit or harm as it is. Appears to work fine as is
> currently edited:
>
> Section "Monitor"
> Identifier "Generic Monitor"
> Option "DPMS"
> #HorizSync 28-84
> #VertRefresh 43-60
>
> The monitor in use is a Samsung SyncMaster 205bw. What do you think?



I bought a Samsung SyncMaster 931B "19") and replaced the ViewSonic A75f
(17"), which is now on another couple of PCs through a KVM.

I have never changed the xorg.conf though, and the SyncMaster is running
fine.

Here is the old but still being used xorg.conf monitor section:

Section "Monitor"
Identifier "A75f"
Option "DPMS"
HorizSync 30-70
VertRefresh 50-160

You probably have an "Auto" button like mine on the bottom edge of the
monitor bezel. When it is pushed the monitor seems to know what is best.

Of course it makes me wonder if the signal is not really optimal, could
it be improved so the monitor doesn't need to (possibly) distort it?


--
John

No Microsoft, Apple, Intel, Trend Micro, nor Ford products were used in the preparation or transmission of this message.

The EULA sounds like it was written by a team of lawyers who want to tell me what I can't do. The GPL sounds like it was written by a human being, who wants me to know what I can do.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #9 (permalink)  
Old 04-07-2008, 08:33 AM
John F. Morse
 
Posts: n/a
Default Re: X.Org vs XFree86

Steffen Pohle wrote:
> Hi there,
>
> I checked your logfile. First of all for a resolution with 800x600 by
> 24bit you need at last 1.4MB video memory. You can go down to 16bpp
> which will give you a resolution of 800x600 pixel.
>
> Another thing could you also send to here your xorg.conf file? That
> would help to find the problem. Because it seems as if you have alot of
> modelines configured. In xorg you shouldn't need anymore modelines, the
> only thing you have to do is tell the server the frequencies of your
> monitor and thats it.
>
> Another thing is that the pixel clock can limitate your screen
> resolution.
>
>
>> (==) TRIDENT(0): Min pixel clock is 12 MHz
>> (--) TRIDENT(0): Max pixel clock is 40 MHz
>> (II) TRIDENT(0): Generic Monitor: Using hsync range of 28.00-80.00 kHz
>> (II) TRIDENT(0): Generic Monitor: Using vrefresh range of 43.00-60.00 Hz
>> (II) TRIDENT(0): Clock range: 12.00 to 40.00 MHz
>>

>
> Since 1024x786 by 60Hz makes around 48 MHz and the card only alows you to
> set it to 40MHz.
>
> bye bye,
> Steffen



Thanks, Steffen. Your idea was the solution!

I decided to get to work early tonight....

First I tried a depth of four bits, but it was rejected by
dpkg-reconfigure as not available for my video card.

So I tried eight bits and it is now working at 800x600. The 16bpp needs
960 kB, so it should also work.

My calculations also indicate that 1024x768 at 8bpp will work (786,432
Bytes required). Do you agree (is my math correct)?

Also, now with the real monitor sync range, is the pixel clock still a
concern?

Here is the newly-generated xorg.conf with only eight bits selected for
the depth.


john@optima12:/etc/X11$ cat xorg.conf
# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the /etc/X11/xorg.conf manual page.
# (Type "man /etc/X11/xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "Files"
FontPath "/usr/share/fonts/X11/misc"
FontPath "/usr/X11R6/lib/X11/fonts/misc"
FontPath "/usr/share/fonts/X11/cyrillic"
FontPath "/usr/X11R6/lib/X11/fonts/cyrillic"
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
FontPath "/usr/share/fonts/X11/Type1"
FontPath "/usr/X11R6/lib/X11/fonts/Type1"
FontPath "/usr/share/fonts/X11/100dpi"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi"
FontPath "/usr/share/fonts/X11/75dpi"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi"
# path to defoma fonts
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection

Section "Module"
Load "bitmap"
Load "ddc"
Load "extmod"
Load "freetype"
Load "glx"
Load "int10"
Load "vbe"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc104"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/psaux"
Option "Protocol" "ImPS/2"
Option "Emulate3Buttons" "true"
EndSection

Section "Device"
Identifier "Trident Microsystems TGUI 9660/938x/968x"
Driver "trident"
BusID "PCI:0:10:0"
EndSection

Section "Monitor"
Identifier "ViewSonic 21"
Option "DPMS"
HorizSync 30-82
VertRefresh 50-150
EndSection

Section "Screen"
Identifier "Default Screen"
Device "Trident Microsystems TGUI 9660/938x/968x"
Monitor "ViewSonic 21"
DefaultDepth 8
SubSection "Display"
Depth 1
Modes "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 4
Modes "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 15
Modes "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "800x600" "640x480"
EndSubSection
EndSection

Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
EndSection

Section "DRI"
Mode 0666
EndSection



--
John

No Microsoft, Apple, Intel, Trend Micro, nor Ford products were used in the preparation or transmission of this message.

The EULA sounds like it was written by a team of lawyers who want to tell me what I can't do. The GPL sounds like it was written by a human being, who wants me to know what I can do.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #10 (permalink)  
Old 04-07-2008, 08:33 AM
John F. Morse
 
Posts: n/a
Default Re: X.Org vs XFree86

sk8r-365 wrote:
> Thus spake John F. Morse:
> <snip>
>
>> I bought a Samsung SyncMaster 931B "19") and replaced the ViewSonic A75f
>> (17"), which is now on another couple of PCs through a KVM.
>>
>> I have never changed the xorg.conf though, and the SyncMaster is running
>> fine.
>>
>> Here is the old but still being used xorg.conf monitor section:
>>
>> Section "Monitor"
>> Identifier "A75f"
>> Option "DPMS"
>> HorizSync 30-70
>> VertRefresh 50-160
>>
>> You probably have an "Auto" button like mine on the bottom edge of the
>> monitor bezel. When it is pushed the monitor seems to know what is best.
>>
>> Of course it makes me wonder if the signal is not really optimal, could
>> it be improved so the monitor doesn't need to (possibly) distort it?
>>
>>

>
> I do have that "auto" buton, but when depressed a message reads, "Auto
> Adjustment Not Available". Go figure. Just for the heck of it I
> uncommented the HSync and VRefesh digits, then restarted X ... nothing
> of note. Hmmm? I *guess* for LCD's it's not important.



I don't know if it matters, but I'm using the analog (HDDB-15)
interface, and not the digital interface.

If the digital interface was being used, there is a possibility the
monitor may be controlled by the video card, kind of like a HDMI cable
can support between a TV and a home theater.

I'll have to reconfigure my xorg.conf someday when I need to reboot.


--
John

No Microsoft, Apple, Intel, Trend Micro, nor Ford products were used in the preparation or transmission of this message.

The EULA sounds like it was written by a team of lawyers who want to tell me what I can't do. The GPL sounds like it was written by a human being, who wants me to know what I can do.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT. The time now is 08:03 PM.


Powered by vBulletin® Version 3.6.5
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Optimization by vBSEO 3.1.0

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62