<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [Ubuntu 12.04 LTS 32-bit] Occasional ATI Radeon 9800 Pro and Intel D815EEA2 ACPI S3 State Resume Freeze"
href="https://bugs.freedesktop.org/show_bug.cgi?id=54583#c16">Comment # 16</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [Ubuntu 12.04 LTS 32-bit] Occasional ATI Radeon 9800 Pro and Intel D815EEA2 ACPI S3 State Resume Freeze"
href="https://bugs.freedesktop.org/show_bug.cgi?id=54583">bug 54583</a>
from <span class="vcard"><a class="email" href="mailto:mypersonalmailbox1@mail.com" title="mypersonalmailbox1@mail.com">mypersonalmailbox1@mail.com</a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=54583#c9">comment #9</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=54583#c8">comment #8</a>)
> > Is it possible you can give me detailed instructions on how to do this?
> > I have gone to grub by pressing shift key during boot, and furthermore pressed
> > e key to edit the boot script.
>
> That's correct. Just append radeon.agpmode=-1 to the kernel line.
>
> > I don't know how to make the change permanent from grub's simple editor.
> > How to I know from Ubuntu's GUI that I am running in PCI mode instead of AGP
> > mode?
>
> To make it permanent, edit the /etc/grub2.cfg and manually make the change.
> You can check the radeon dmesg messages to see whether the card is loaded in
> AGP or non-AGP mode.</span >
Hi Alex,
I postponed working on this issue for a while because I was not able to figure
out how to permanently alter GRUB loader options.
I broke down, and decided to insert radeon.agpmode=-1 everytime I boot for
testing purposes.
By the way, even after adding radeon.agpmode=-1, I still see random freezes and
or instability with Radeon 9800 Pro.
Looking at the dmesg.0.txt messages, I think my Radeon 9800 Pro is still being
considered an AGP device despite adding the radeon.agpmode=-1 option in GRUB.
Anyway, I added various log files related to power management to the bug
report.
Note the time jump between Oct 13 16:38, Oct 13 16:44, and Oct 13 16:49.
I believe at one of those times, the computer froze (with a blank screen).
You can take a look at it to see what is going on.
Regards,
fpgahardwareengineer</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>