[ltp] Anyone got Suspend-to-Ram with fglrx driver works?
Osho GG
linux-thinkpad@linux-thinkpad.org
Fri, 11 Nov 2005 11:14:55 -0800
------=_Part_26971_17814690.1131736495008
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Yes, susend-to-ram works with fglrx driver using vbetool work-around. Here
is a cheat-sheet that I have written for it. It has been 100% reliable on m=
y
T42p.
0. First, make sure that ACPI suspend/resume works well with radeon
X.org<http://x.org/>
driver. This is necessary to make sure that all non-graphics driver related
issues are resolved. I presume you have already got this working.
1. Download and compile the vbetool
http://freshmeat.net/projects/vbetool/
You will need to download two files:
http://www.srcf.ucam.org/~mjg59/vbetool/vbetool_0.2.orig.tar.gz<http://www.=
srcf.ucam.org/%7Emjg59/vbetool/vbetool_0.2.orig.tar.gz>
http://www.srcf.ucam.org/~mjg59/vbetool/vbetool_0.2-1.diff.gz<http://www.sr=
cf.ucam.org/%7Emjg59/vbetool/vbetool_0.2-1.diff.gz>
Untar and unzip the first file and apply the patch from the second file.
Compile vbetool and put vbetool binary somewhere in the system PATH.
2. Modify ACPI suspend/resume scripts to include vbetool in it. This depend=
s
on your distribution. Whatever function is called when ACPI suspend is
called, add the following to it.
chvt 2
/usr/sbin/vbetool vbestate save > /var/tmp/vbestate
sync
3. Next, Whatever function is called when ACPI resume is called, put the
following into it.
/usr/sbin/vbetool post
/usr/sbin/vbetool vbestate restore < /var/tmp/vbestate
chvt 7
This presumes that 7 is the virtual terminal on which you have the X window
running. You can make this more robust by using fgconsole.
Osho
On 11/10/05, Jiang Qian <qian2@fas.harvard.edu> wrote:
>
> By the way did anyone get resume from Suspend-to-Ram with fglrx driver
> to work? Maybe on a T43/T43p even, which uses pci-express instead of
> AGP? If so could you share with us your /etc/acpi/sleep.sh
> /etc/acpi/resume.sh and maybe /etc/acpi/prepare.sh if you have one?
> I tried all these vbetool gymnastics and none of them works.
> Thanks in advance.
> Also if you get it to work, do 3D-acceleration still work after resume?
> Jiang
>
>
> On Thu, Nov 10, 2005 at 02:22:03PM -0500, Gavin W. Burris aka 86 wrote:
> > Same problem here. I'm guessing that the fglrx driver changes quite a
> > few settings on the video card that the radeon driver doesn't know
> > about, and they are only re-initialized after a hardware reset.
> >
> > Jiang Qian wrote:
> > > Hi All:
> > > In order to view stellarium, I installed the latest proprietary fglrx
> > > driver for 3D. I switched to a xorg.conf file with fglrx driver,
> > > everything works fine with 3D acceleration. However when I stopped X,
> > > then copy back the old xorg.conf file and restart x with radeon
> driver,
> > > the screen is garbled. See this:
> > > http://physics.harvard.edu/~jqian/computer/garbled_screen.png
> > > When I switch again to fglrx driver it is fine again. The problem is
> > > that I can't get fglrx driver to sleep, so I'd like to have my radeon
> > > driver xorg back when I'm done with stellarium stuff. Any idea how?
> > >
> > > After a full reboot back to radeon driver, it is fine. Yet the funny
> > > thing is that if I init 1 then init 5, without going through the tota=
l
> > > reboot, the radeon is still garbled. Why does it make a difference
> > > between a full reboot and init 1 then init 5?
> > >
> > > /var/log/Xorg.log does not show any warning about radeon driver.
> > >
> > > I'm using ubuntu Hoary with 2.12.4 kernel and fglrx version 8.18.8
> > >
> > > Thanks in advance for any suggestion.
> >
> > --
> > Gavin W. Burris aka 86
> > Senior Systems Programmer
> > Penn State Visualization Group
> > http://viz.aset.psu.edu/ga5in
> > --
> > The linux-thinkpad mailing list home page is at:
> > http://mailman.linux-thinkpad.org/mailman/listinfo/linux-thinkpad
> --
> The linux-thinkpad mailing list home page is at:
> http://mailman.linux-thinkpad.org/mailman/listinfo/linux-thinkpad
>
--
Osho
------=_Part_26971_17814690.1131736495008
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Yes, susend-to-ram works with fglrx driver using vbetool work-around.
Here is a cheat-sheet that I have written for it. It has been 100%
reliable on my T42p.<br>
<br>
<br>
0. First, make sure that ACPI suspend/resume works well with radeon <a oncl=
ick=3D"return top.js.OpenExtLink(window,event,this)" href=3D"http://x.org/"=
target=3D"_blank">X.org</a><br>
driver. This is necessary to make sure that all non-graphics driver related=
<br>
issues are resolved. I presume you have already got this working.<br>
<br>
1. Download and compile the vbetool<br>
<br>
<a onclick=3D"return top.js.OpenExtLink(window,event,this)" href=3D"http://=
freshmeat.net/projects/vbetool/" target=3D"_blank">http://freshmeat.net/pro=
jects/vbetool/</a><br>
<br>
You will need to download two files:<br>
<br>
<a onclick=3D"return top.js.OpenExtLink(window,event,this)" href=3D"http://=
www.srcf.ucam.org/%7Emjg59/vbetool/vbetool_0.2.orig.tar.gz" target=3D"_blan=
k">http://www.srcf.ucam.org/~mjg59/vbetool/vbetool_0.2.orig.tar.gz</a><br>
<a onclick=3D"return top.js.OpenExtLink(window,event,this)" href=3D"http://=
www.srcf.ucam.org/%7Emjg59/vbetool/vbetool_0.2-1.diff.gz" target=3D"_blank"=
>http://www.srcf.ucam.org/~mjg59/vbetool/vbetool_0.2-1.diff.gz</a><br>
<br>
Untar and unzip the first file and apply the patch from the second file.<br=
>
Compile vbetool and put vbetool binary somewhere in the system PATH.<br>
<br>
2. Modify ACPI suspend/resume scripts to include vbetool in it. This depend=
s<br>
on your distribution. Whatever function is called when ACPI suspend is<br>
called, add the following to it.<br>
<br>
chvt 2<br>
/usr/sbin/vbetool vbestate save > /var/tmp/vbestate<br>
sync<br>
<br>
3. Next, Whatever function is called when ACPI resume is called, put the<br=
>
following into it.<br>
<br>
/usr/sbin/vbetool post<br>
/usr/sbin/vbetool vbestate restore < /var/tmp/vbestate<br>
chvt 7<br>
<br>
This presumes that 7 is the virtual terminal on which you have the X window=
<br>
running. You can make this more robust by using fgconsole.<br>
<br>
Osho<br><br><div><span class=3D"gmail_quote">On 11/10/05, <b class=3D"gmail=
_sendername">Jiang Qian</b> <<a href=3D"mailto:qian2@fas.harvard.edu">qi=
an2@fas.harvard.edu</a>> wrote:</span><blockquote class=3D"gmail_quote" =
style=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8=
ex; padding-left: 1ex;">
By the way did anyone get resume from Suspend-to-Ram with fglrx =
driver<br>to work? Maybe on a T43/T43p even, which uses pci-express instead=
of<br>AGP? If so could you share with us your /etc/acpi/sleep.sh<br>/etc/a=
cpi/resume.sh and maybe /etc/acpi/prepare.sh if you have one?
<br>I tried all these vbetool gymnastics and none of them works.<br>Thanks =
in advance.<br>Also if you get it to work, do 3D-acceleration still work af=
ter resume?<br>Jiang<br><br><br>On Thu, Nov 10, 2005 at 02:22:03PM -0500, G=
avin W. Burris aka 86 wrote:
<br>> Same problem here. I'm guessing that the fglrx driver c=
hanges quite a<br>> few settings on the video card that the radeon drive=
r doesn't know<br>> about, and they are only re-initialized after a hard=
ware reset.
<br>><br>> Jiang Qian wrote:<br>> > Hi All:<br>> > In ord=
er to view stellarium, I installed the latest proprietary fglrx<br>> >=
; driver for 3D. I switched to a xorg.conf file with fglrx driver,<br>> =
> everything works fine with 3D acceleration. However when I stopped X,
<br>> > then copy back the old xorg.conf file and restart x with rade=
on driver,<br>> > the screen is garbled. See this:<br>> > <a hr=
ef=3D"http://physics.harvard.edu/~jqian/computer/garbled_screen.png">http:/=
/physics.harvard.edu/~jqian/computer/garbled_screen.png
</a><br>> > When I switch again to fglrx driver it is fine again. The=
problem is<br>> > that I can't get fglrx driver to sleep, so I'd lik=
e to have my radeon<br>> > driver xorg back when I'm done with stella=
rium stuff. Any idea how?
<br>> ><br>> > After a full reboot back to radeon driver, it is=
fine. Yet the funny<br>> > thing is that if I init 1 then init 5, wi=
thout going through the total<br>> > reboot, the radeon is still garb=
led. Why does it make a difference
<br>> > between a full reboot and init 1 then init 5?<br>> ><br=
>> > /var/log/Xorg.log does not show any warning about radeon driver.=
<br>> ><br>> > I'm using ubuntu Hoary with 2.12.4 kernel and fg=
lrx version=20
8.18.8<br>> ><br>> > Thanks in advance for any suggestion.<br>&=
gt;<br>> --<br>> Gavin W. Burris aka 86<br>> Senior Systems Progra=
mmer<br>> Penn State Visualization Group<br>> <a href=3D"http://viz.a=
set.psu.edu/ga5in">
http://viz.aset.psu.edu/ga5in</a><br>> --<br>> The linux-thinkpad mai=
ling list home page is at:<br>> <a href=3D"http://mailman.linux-thinkpad=
.org/mailman/listinfo/linux-thinkpad">http://mailman.linux-thinkpad.org/mai=
lman/listinfo/linux-thinkpad
</a><br>--<br>The linux-thinkpad mailing list home page is at:<br><a href=
=3D"http://mailman.linux-thinkpad.org/mailman/listinfo/linux-thinkpad">http=
://mailman.linux-thinkpad.org/mailman/listinfo/linux-thinkpad</a><br></bloc=
kquote>
</div><br><br clear=3D"all"><br>-- <br>Osho<br><br>
------=_Part_26971_17814690.1131736495008--