Hi Again,

For what its worth, I installed OpenSuse 11.0 Alpha0 on the Dell
Latitude C400.
Xorg.0.log says that it is using intel_drv.so version 2.2.0

s2ram fails in a very similar way to version 2.1.1 (but not exactly the
same).
If you leave the machine running for a while after booting, then do an
s2ram, everything is perfect after the resume.
[Also, interestingly, after that it will survive many rapid s2ram/resume
cycles].

However if you boot it, then quickly do an s2ram, X is unusable after
the resume.
The machine is fully functional and the backlight is on but the mouse is
the only thing visible on the screen.

Does this help? If any further information would be useful, please let
me know.

All the best,

Andy

Andy Low wrote:
> Hi again,
>
> I was too quick in emailing you before.  Now mine fails all the time -
> whatever the screen depth.
> Maybe it just took me a long time to change the xorg.conf file. 
> Odd, though, before I emailed you last time I managed about 20 s2ram
> cycles without a single failure.  It could have been a nice idea!
>
> If you get a proper solution, maybe you could let me know?
>
> All the best,
>
> Andy
>
> Mark J. Small wrote:
>   
>> On December 19, 2007, Andy Low wrote:
>>   
>>     
>>> Hi Mark & Brice,
>>>
>>> I thought you might be interested to know that I had the same issue as
>>> you after an otherwise successful s2ram using OpenSuse 10.3 on my Dell
>>> Latitude C400.  Suspend to ram worked fine using Ubuntu 7.10.
>>>
>>> I found that Ubuntu sets the xorg screen depth to 24 but OpenSuse uses
>>> 16.  After changing xorg.conf in OpenSuse to 24 bits, s2ram works
>>> perfectly!
>>>
>>> Hope this helps.  If you would like any more info on the configuration
>>> here, please let me know.
>>>
>>> All the best,
>>>
>>> Andy
>>>     
>>>       
>> I just tried changing the default depth to 24 on my C400 running debian 
>> testing, and it didn't help.  I still had video corruption.  I still find 
>> that the longer the computer has been on, the more likely s2ram will work 
>> properly.  
>>
>> Thanks for the idea,
>>
>> Mark
>>
>>   
>>     
>
>   



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to