Mailinglist Archive: radeonhd (622 mails)
| < Previous | Next > |
Re: [radeonhd] EDID works after one suspend/resume-to-ram cycle!
- From: Ruediger Oertel <ro@xxxxxxx>
- Date: Thu, 4 Oct 2007 00:27:21 +0200 (CEST)
- Message-id: <Pine.LNX.4.64.0710040022220.27558@xxxxxxxxxxxxx>
On Wed, 3 Oct 2007, Luca wrote:
> (Adding CC to suspend-devel)
>
> On 10/3/07, Ruediger Oertel <ro@xxxxxxx> wrote:
> > 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?
it just depends on which X driver you use. Since I'm still running
fglrx, I had the best results by keeping s2ram from any games
with the vbe data ...
Yes, I heard that the s2ram defaults (see below, VBE_POST,VBE_MODE)
work if you are not using the fglrx driver, but vesafb is not really
an option for me ;)
>
> > "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"?
of course:
# s2ram -i
This machine can be identified by:
sys_vendor = "Apple Computer, Inc."
sys_product = "MacBookPro2,2"
sys_version = "1.0"
bios_version = " MBP22.88Z.00A5.B07.0708131242"
See http://suspend.sf.net/s2ram-support.html for details.
If you report a problem, please include the complete output above.
# s2ram -n
Machine matched entry 4:
sys_vendor = 'Apple Computer, Inc.'
sys_product = 'MacBookPro2,2'
sys_version = ''
bios_version = ''
Fixes: 0x88 VBE_POST VBE_MODE
This machine can be identified by:
sys_vendor = "Apple Computer, Inc."
sys_product = "MacBookPro2,2"
sys_version = "1.0"
bios_version = " MBP22.88Z.00A5.B07.0708131242"
See http://suspend.sf.net/s2ram-support.html for details.
If you report a problem, please include the complete output above.
--
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)
> (Adding CC to suspend-devel)
>
> On 10/3/07, Ruediger Oertel <ro@xxxxxxx> wrote:
> > 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?
it just depends on which X driver you use. Since I'm still running
fglrx, I had the best results by keeping s2ram from any games
with the vbe data ...
Yes, I heard that the s2ram defaults (see below, VBE_POST,VBE_MODE)
work if you are not using the fglrx driver, but vesafb is not really
an option for me ;)
>
> > "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"?
of course:
# s2ram -i
This machine can be identified by:
sys_vendor = "Apple Computer, Inc."
sys_product = "MacBookPro2,2"
sys_version = "1.0"
bios_version = " MBP22.88Z.00A5.B07.0708131242"
See http://suspend.sf.net/s2ram-support.html for details.
If you report a problem, please include the complete output above.
# s2ram -n
Machine matched entry 4:
sys_vendor = 'Apple Computer, Inc.'
sys_product = 'MacBookPro2,2'
sys_version = ''
bios_version = ''
Fixes: 0x88 VBE_POST VBE_MODE
This machine can be identified by:
sys_vendor = "Apple Computer, Inc."
sys_product = "MacBookPro2,2"
sys_version = "1.0"
bios_version = " MBP22.88Z.00A5.B07.0708131242"
See http://suspend.sf.net/s2ram-support.html for details.
If you report a problem, please include the complete output above.
--
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 > |