(Adding CC to suspend-devel)
On 10/3/07, Ruediger Oertel
On Wed, 3 Oct 2007, Ruediger Oertel wrote:
On Wed, 3 Oct 2007, Luca wrote: [...]
Ah, this one is a Mac; if it's using the EFI to boot (I think it is) probably the BIOS on the card is not run; s2ram uses vbetool during resume, which may post the card BIOS. So I guess the card is not fully initialized (or it's just in an "unexpected" state) when radeonhd starts poking at it right after a cold boot.
ah, a good hint. Actually I'm booting not directly from EFI but via rEFIt and grub and such should have some legacy BIOS services but playing with vbetool on a freshly booted machine might reveal something.
no ...
"vbetool post" actually reset's the machine,
This is bad, "MacBook2,1" and "MacBookPro2,2" are both listed to POST the card on resume. Does plain s2ram kill this machine too?
"vbetool vbestate save > outfile ; vbetool vbestate restore < outfile" does not change anything either
but as before, a plain "s2ram -f" (the "-f" here used to keep it from using any hacks that just break it for me) works to get proper DDC output afterwards.
Can you send us the output of "s2ram -i"? Luca -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org