Mailinglist Archive: radeonhd (622 mails)
| < Previous | Next > |
Re: [radeonhd] EDID works after one suspend/resume-to-ram cycle!
- From: Ruediger Oertel <ro@xxxxxxx>
- Date: Wed, 3 Oct 2007 15:37:33 +0200 (CEST)
- Message-id: <Pine.LNX.4.64.0710031535030.21042@xxxxxxxxxxxxx>
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,
"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.
--
with kind regards (mit freundlichem Grinsen),
Ruediger Oertel (ro@xxxxxxxxxx,ro@xxxxxxx,bugfinder@xxxxxxxxxxx)
----------------------------------------------------------------------
Linux Fatou 2.6.22.5-31-default #1 SMP 2007/09/21 22:29:00 UTC x86_64
Key fingerprint = 17DC 6553 86A7 384B 53C5 CA5C 3CE4 F2E7 23F2 B417
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
> 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,
"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.
--
with kind regards (mit freundlichem Grinsen),
Ruediger Oertel (ro@xxxxxxxxxx,ro@xxxxxxx,bugfinder@xxxxxxxxxxx)
----------------------------------------------------------------------
Linux Fatou 2.6.22.5-31-default #1 SMP 2007/09/21 22:29:00 UTC x86_64
Key fingerprint = 17DC 6553 86A7 384B 53C5 CA5C 3CE4 F2E7 23F2 B417
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
| < Previous | Next > |