Display problem

[Jose]

Lennart Sorensen wrote:
> On Thu, Sep 28, 2006 at 09:37:44AM -0500, Jose wrote:
>   
>> (II) TRIDENT(0): Ranges: V min: 50  V max: 120 Hz, H
>> min: 30  H max: 69 kHz, PixClock max 110 MHz
>> (II) TRIDENT(0): Serial No: 122CG43HE775
>> (II) TRIDENT(0): Monitor name: COMPAQ S710
>> (--) TRIDENT(0): Revision is 130
>> (--) TRIDENT(0): Found Blade3D chip
>> (--) TRIDENT(0): Unable to determine VideoRam,
>> defaulting to 1MB
>>     
>
> Hmm, that looks unfortunate.
>
>   
>> (--) TRIDENT(0): Using HW cursor
>> (--) TRIDENT(0): VideoRAM: 1024 kByte
>> (--) TRIDENT(0): Memory Clock is 90.38 MHz
>> (==) TRIDENT(0): Min pixel clock is 12 MHz
>> (--) TRIDENT(0): Max pixel clock is 115 MHz
>> (WW) TRIDENT(0): config file hsync range 28-60kHz not
>> within DDC hsync ranges.
>> (II) TRIDENT(0): Monitor[0]: Using hsync range of
>> 28.00-60.00 kHz
>> (II) TRIDENT(0): Monitor[0]: Using vrefresh range of
>> 50.00-60.00 Hz
>> (II) TRIDENT(0): Clock range:  12.00 to 115.00 MHz
>> (II) TRIDENT(0): Not using mode "1024x768"
>> (insufficient memory for mode)
>>     
>
> And explains this problem.
>
>   
>> (II) TRIDENT(0): Not using mode "800x600"
>> (insufficient memory for mode)
>>     
>
> And this one.
>
>   
>> (II) TRIDENT(0): Not using mode "768x576"
>> (insufficient memory for mode)
>>     
>
> And this one.
>
>   
>> (II) TRIDENT(0): Not using mode "640x480"
>> (insufficient memory for mode)A
>>     
>
> Now there are none of the modes you asked for in the config left.
>
>   
>> (II) TRIDENT(0): Not using default mode "800x512"
>> (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 "2048x1536"
>> (insufficient memory for mode)
>> (II) TRIDENT(0): Not using default mode "2048x1536"
>> (insufficient memory for mode)
>> (WW) TRIDENT(0): Mode pool is empty
>> (EE) TRIDENT(0): No valid modes found
>>     
>
> And the result is that there are no valid modes left for it to use, and
> hence it can't give you a display.
>
>   
>> (EE) Screen(s) found, but none have a usable
>> configuration.
>>
>> Fatal server error:
>> no screens found
>>     
>
> Which is clearly what it says here.
>
> So you have to tell it in the config exactly how much memory the video
> chip has since it apparently can't detect that on your particular chip.
>
> If you reduce colour depth to 8 bit, you would have enough memory even
> with 1MB to run your requested modes, but not in 24bit.
>
> --
> Len Sorensen
> --
> The Toronto Linux Users Group.      Meetings: http://gtalug.org/
> TLUG requests: Linux topics, No HTML, wrap text below 80 columns
> How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists
>
>
>   
Hi Lennart

Thanks for taking the time to look into the log, I would give it a try 
with the very minimal configuration, but why on failsafe mode gives me a 
gui?, I am still trying to figure that out?, I tried making a copy of 
the xrog.conf while on  failsafe mode, and then reapply it, but it 
didn't work.

Thanks again

Jose


--
The Toronto Linux Users Group.      Meetings: http://gtalug.org/
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists