On 2007.12.18 18:50, Nyle Davis wrote:
> Roy,
> 
> On that last Q.  Display is AMW MR19C-AB LCD screen.  VIC is 
> Diamond Stealth 64 with S3 chip, MB is ECS 755-A with no 
> onboard VIC, so all should go to the PCI Diamond Stealth 64 card.
> 
> Have disabled all calls to module and the "glx" nvidia error still 
> occurs.  Seems to be coming from something else driven in the 
> config, when machine boots.  Went to /etc/rc2.d and rename the 
> S13gdm to _S13gdm and the S20xserver-xorg to _S20xserver-
> xorg, but still getting error even after reboot.
> 
> Seems to be Ubuntu specific config, so querying on #ubuntu to see 
> what I do next.  Will send you results, if I have them before the pm.
> 
> Thanks!
> 
> Nyle Davis
> davisoft@megsinet.net
> (214)-227-7677 Office
> (214)-779-6918 Cell
> 
> 
Nyle,

RL has soaked up some of my free time.  Lets have a look at your log.
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules//libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
	compiled for 4.0.2, module version = 1.0.9639
	Module class: X.Org Server Extension
	ABI class: X.Org Server Extension, version 0.1
Tells that your glx library is provided by nVidia. Thats no use to you 
as it only works with the nVidia binary blob driver, which in turn 
needs nVidia hardware.
Gentoo keeps the various glx libraries separate and provides eselect 
opengl to chose one to be used. Binary distros normally have no need of 
this. You need to get the xorg replacement for /usr/lib/xorg/modules//
libglx.so to fix this.  Its only a problem if you tried to use OpenGL. 
Everything else should work, so its not your blank screen issue.

This section tells about your display the data is read from the EDID 
data provided by the display.
(--) s3(0): Max pixel clock at this depth is 135 Mhz
(II) s3(0): AMW MR19C-AB: Using hsync range of 30.00-160.00 kHz
(II) s3(0): AMW MR19C-AB: Using vrefresh range of 55.00-120.00 Hz
(II) s3(0): Clock range:  15.60 to 135.00 MHz

The Using vrefresh range of 55.00-120.00 Hz is a little worrying as 
most LCDs start lower and don't go so high. Google dosn't help and the 
AMW web site is totally useless.

From your config file 	
	HorizSync	30 - 160
	VertRefresh	55 - 120
Xorg seems to be doing what you tell it. Comment those two lines out.
For testing, comment out your Modeline, which xorg has picked up.  It 
may use that in preference to the EDID provided values.


The EDID should provide correct values. If that fails try a fixed 
	VertRefresh	60
As every LCD ever made will operate at 60Hz. Do not specifiy a 
HorizSync. 

It may well be that your monitor does not support 1152x864@73 but a 
lower refresh rate will be ok.

Starting here
(--) s3(0): Virtual size is 1152x864 (pitch 1280)
(**) s3(0): *Mode "1152x864@73": 107.7 MHz, 66.3 kHz, 73.1 Hz
(II) s3(0): Modeline "1152x864@73"  107.74  1152 1184 1592 1624  864 
881
891 908
(**) s3(0): *Default mode "1152x864": 121.5 MHz, 77.5 kHz, 85.1 Hz
(II) s3(0): Modeline "1152x864"  121.50  1152 1216 1344 1568  864 865
868 911 +hsync -vsync
xorg tells its operating at 1152x864 but its not clear which modeline 
is in use. 


(**) s3(0): Depth 8, (--) framebuffer bpp 8
(==) s3(0): Default visual is PseudoColor
Says the system is operating in 8 bit colour This ties in nicely with 
your 	
DefaultDepth	8 
statement in the config.  


The log says (--) s3(0): videoRam = 2048 Kb
so you have at most 1Mb for your pixel buffer while you use the double 
buffer extension (dbe)  1152x864 just fits, you need 995,328 bytes


Everything else looks normal.

Its worth reading   man s3 to see if the s3 driver supports any LCD 
specific options. Some drivers need to know if the display is an LCD or 
CRT, some don't.

Just now, I suspect your display is blank because it does not support 
the resolution you are trying to operate in.

I hope that helps,


Roy Bamford
(NeddySeagoon)