[RC410] Xpress 200M hangs when resuming from suspend with DRI (needs KMS)

[gene]

Binary package hint: xserver-xorg-video-radeon

Since I upgraded to 8.10 from 8.04 the machine does not resume from suspend.
1) Depending on the tools it behaves the following way: when using usual (gnome) suspend, when trying to resume it turns on and off with a blank screen. When using pm-utils, it turns on but the screen is blank. In all of these cases, the system is irresponsive and requires a hard reboot (held down power button). Sometimes the system just restarts (reboots) on its own after one attempt.
2) There is also one more problem with the X that is conected. Occasionally, when booting the system before getting the login window the system hangs with the blank screen. It also remains totally irresponsive with no Magic Keys working.

The reason why I think the issue is related to "radeon" driver is the following. I've had a lot of problems be with the ATI/AMD proprietary fglrx driver (no dual head support, no xvid etc). However, when I upgraded to 8.10 I found the fglrx in use. Again, the performance was not good either (bad xv support and slow). But I could resume from suspend OK and do not remember any crashes when booting. I removed it and started using "radeon" driver. The performance was better, but I started experiencing the above-mentioned problems. I also tried "ati" driver (not sure if there is difference ) bu with no avail.
Someone found a similar bug a couple months ago and followed the suggested change in the Xorg.conf by trying different values for Option "AGPMode". it didn't work. I also tried hibernate tools. It did similar things. I tried with/without compiz, gives the same problem, as well as with the generic Xorg.conf file. I attach both below
My laptop is Toshiba Satellite l35 with ATI Technologies Inc RC410 [Radeon Xpress 200M].

$uname -a
             2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686 GNU/Linux
I am attaching some useful files below.
Thanks very much in advance for your help!
[lspci]
00:00.0 Host bridge: ATI Technologies Inc Device 5a31 (rev 01)
01:05.0 VGA compatible controller: ATI Technologies Inc RC410 [Radeon Xpress 200M] [1002:5a62]

[gene (eugenios)]

Forgot to mention to more things here.
1) the system resumes fom the hibernate without a problem, however
2) occasionally, when waking up from hibernate or booting (when the system gets there and doesn't hang) I see some change in the window decorations. Things appear different from my setting. I go to the gnome appearance menu. It either does not start and complains about gnome-setting-manager or just restarts X and everything look nice. Also when after hibernate I see some colored lines around the window frames, I fix it by the "compiz --replace" command. (But this last one might be just a gnome and/or compiz issue)

[gene (eugenios)]

Forgot to mention to more things here.
1) the system resumes from the hibernate without a problem, however
2) occasionally, when waking up from hibernate or booting (when the system gets there and doesn't hang) I see some change in the window decorations. Things appear different from my setting. I go to the gnome appearance menu. It either does not start and complains about gnome-setting-manager or just restarts X and everything look nice. Also when after hibernate I see some colored lines around the window frames, I fix it by the "compiz --replace" command. (But this last one might be just a gnome and/or compiz issue)

[gene (eugenios)]

I do not know why this issue does not deserve any attention from the Ubuntu developers.

I found that this problem is escalating now. Because, as I have mentioned earlier, sometimes the system stalls before the graphical login comes up. The ratio of successful logins over failed ones was 3/1, now it seems to be 1/5 and approaches zero as time goes by.

Since this issue is being neglected I am likely not to be able to get here soon...

This might be a very important problem, because it could be tampering with the hardware.

[Bryce Harrington (bryce)]

Please isolate whether this is a kernel issue or an X issue by switching to a tty console and running this:

sync; echo 1 > /sys/power/pm_trace; /etc/acpi/sleep.sh force

If you can reproduce the hang using that, then this is really a kernel issue and should be reassigned to linux.

[gene (eugenios)]

Thanks for taking your time to answer.
Yes it does a similar thing. When trying to resume the system (the machine rather, cause it never gets to that level) reboots itself. However, it still concerns the vga driver. Doesn't it? Or the corresponding module in the kernel? Please let me know.

[dimitri (dimitri-vanlanduyt)]

The same occurs to me; also Radeon 200M (RC410). After suspending (or hibernating for matter) the machine just returns to a blank screen, none of the Magic Keys (SysRq combinations) work.

I can reproduce this hang with the line presented above, should this bug report be forwarded?

[gene (eugenios)]

I switched to fglrx. fglrx is buggier, though.

however, as far as I remember, hibernation worked OK.... not always.

I think, the radeon open source driver developers should be notified about our problem.
I do not know how to do that. Do you?
Thanks

[gene (eugenios)]

Having experienced so much trouble with fglrx, decided to give another try to radeon. What bitter surprise. My problem has not been fixed yet. This problem persists. If anyone can give me a link to the radeon driver developers, so that I could notify them about this, I would appreciate.

However, Never never never buy from ati!

[gene (eugenios)]

i

[gene (eugenios)]

I tried to link this bug to the one I just reported. I did not find how to do that. I do not want it to be a duplicate of the other.
It is https://bugs.launchpad.net/bugs/340152 It concerns jaunty now.

[Tormod Volden (tormodvolden)]

It is unclear to me when reading your comments whether this is a problem with any graphics driver or the kernel. Can you please boot with the "text" boot parameter, and log in to the console and run "pm-suspend" ?

A possible related upstream report would be http://bugs.freedesktop.org/show_bug.cgi?id=19581 for radeon.

Also, today the linux-image-generic 2.6.28-11 is released in Jaunty and contains some drm updates. Please try it out.

[gene (eugenios)]

I will try that,
Thanks

[gene (eugenios)]

booted with the "text" boot parameter and ran "sudo pm-suspend" and was able to successfully resume back two times . However, I tried to reboot to X and ran "pm-suspend" - I failed to resume. Both WITHOUT any X conf file.

I will now try the newest kernel version available. I got 28-10 so far
Thanks

[gene (eugenios)]

No resume from suspend with 2.6.28-11-generic kernel

[gene (eugenios)]

Forgot to mention: when DRI is on

[dimitri (dimitri-vanlanduyt)]

This happens to me, too. On a fresh Jaunty install with DRI on. I have a Radeon Xpress 200M (RC410), regretfully...

suspending works, returning from suspend makes the machine hang.

Please tell me how I can give more info (which logs, which configfiles)

[Tormod Volden (tormodvolden)]

I would suggest trying out a 2.6.30 kernel, for instance from https://wiki.ubuntu.com/KernelMainlineBuilds and then ping the upstream bug.

[Giancaldo (giancaldo)]

I have the exact same problem with an Xpress 200M (RS480). I tried the 2.6.30 kernel but problem persists.

[Tormod Volden (tormodvolden)]

Giancaldo, there is a report on RS480 in bug 333377, however the difference there is that disabling DRI does not help. If it helps for you, please attach your Xorg.0.log for reference.

[Dimitri (dvanlanduyt)]

Tormod, I just tried the 2.6.30 (Rc3) kernel (linux-image-2.6.30-020630rc3-generic_2.6.30-020630rc3_i386.deb) from that link.
Alas, the problem persists.

Please educate me, which files/logs do I need to provide in order to be informative? To be sure, is "pinging the upstream bug" lingo for adding this information to the Linux Kernel bugzilla, as linked to above? http://bugzilla.kernel.org/show_bug.cgi?id=10258
This is a closed bug, correct?

[Tormod Volden (tormodvolden)]

Dimitri, the upstream (kernel bugzilla) bug was closed because of no activity, so it would be nice if you could attach your Xorg.0.log there. If you can attach dmesg output like the original reporter it is also good. Some of the information on https://wiki.ubuntu.com/X/Backtracing might be helpful for you or others trying to debug this.

[Tormod Volden (tormodvolden)]

I just realized that the bugzilla.kernel.org bug report was for another chipset, so maybe it is better to file a new bug instead. Anyway, please attach your logs to the bugzilla.freedesktop.org bug, but do the test that cooper suggests there to verify you see the same as Mark.

[Darrell Kavanagh (darrell)]

I can confirm that this behaviour persists under kernel 2.6.30rc3.

[Giancaldo (giancaldo)]

Actually, my card is an RC410 too so I'll attach my xorg.0.log file here I guess. The PCI bridge is the RS480. Sorry for the confusion.

[Giancaldo (giancaldo)]

Sorry, forget the dmesg.txt. I did try to do a backtrace but the net connection couldn't survive the suspend.

[Giancaldo (giancaldo)]

attached is dmesg output after the command sync; echo 1 > /sys/power/pm_trace; pm-suspend
I hope that is of some help.

[Giancaldo (giancaldo)]

Attached is the Xorg log file of a failed xorg backtrace, if it's of any use.

[Tormod Volden (tormodvolden)]

Again, please see https://wiki.ubuntu.com/X/Backtracing which explains how to use "screen" to debug across suspend.

[Giancaldo (giancaldo)]

i did try backtracing using screen but once ethernet and wifi went down when it entered suspend, I couldn't ssh to it as not even the net connections would resume.

[Darrell Kavanagh (darrell)]

Exactly the same here as it was for Giancaldo: backtrace using screen impossible as networking does not return.

I also enabled drm debug during a suspend/attempted-resume cycle. There are no messages in kern.log or syslog from drm after suspend until the machine is hard-rebooted.

[Tormod Volden (tormodvolden)]

Oh I see, sure, if not even wired network comes up, the screen trick won't help. If there is nothing written to the logs it could be that the whole bus is frozen and the disk is out of reach. The only trick left would be serial console debugging if you had serial ports, but I guess there are none on your laptops.

(Giancaldo, your Xorg.1.log is from the VESA driver.)

[Giancaldo (giancaldo)]

sorry about that, didn't realise it was the VESA driver.

I tried again a few times at backtracing, only once did it resume more or less functioning (after issuing the pm-suspend command only) but gdb for some reason didn't allow me to type any more commands in.

Attached is the message file if it's of any use.

[Giancaldo (giancaldo)]

attached is the rom.bin

[Tormod Volden (tormodvolden)]

Quite some broken stuff in your messages file, Giancaldo, looks like severe memory corruption on resume. For one thing, how come "Aug 10" shows up in there?

I also see there is some Sysrq calls, does it react to alt-sysrq-S-U-B to reboot? I think Dimitri said above that sysrq does not work.

Can you others please also attach your messages file?

[Giancaldo (giancaldo)]

I have no idea why "Aug 10" shows up.

Well I did the altgr-sysrq-k in the hope of rebooting the computer without doing a hard reset.

altgh-sysrq-s-u-b also seems to restart the computer. Sysrq seems to work for me, I also noticed that when i tried to resume after the 'pm-suspend' command, pressing the altgr-sysrq-.... would cause the very top left of the screen to become slightly blue.

[Darrell Kavanagh (darrell)]

Here is an extract from my messages file, from starting a drm-enabled X session to the necessary hard reset after the resume failure. Drm debugging was switched on and I also have an enormous syslog if that would be of any help.

Darrell

[Tormod Volden (tormodvolden)]

Darrell, your messages file is also messed up, probably from memory corruption.

Giancaldo, the funny date can be explained if you had been trying pm_trace, see https://wiki.ubuntu.com/DebuggingKernelSuspend.

[Darrell Kavanagh (darrell)]

Tormod, yes, it certainly seemed messed up to me as well, but I thought I would leave diagnosis to the expert :). The syslog/debug logs I have, full of dri debug messages also have some screwed up parts. So, what is the verdict so far - that using the current dri with the RC410 card corrupts memory? It sort of makes sense to me that this is possible, as the graphics card is sharing system memory. What are the next steps? Is there any further information/testing you require from my machine?

[Darrell Kavanagh (darrell)]

I should add, that from the timing of the garbage debug messages, the memory corruption (if that's what it is) is taking place during the suspend processing, not the attempted resume.

[Tormod Volden (tormodvolden)]

You can't always trust the timestamps in the messages around suspend time, the last messages during suspend are stored in a buffer and are timestamped and written out after resume. So typically all the suspend and the earliest resume messages will have the same timestamp.

For now I hope the upstream experts will chime in. In fact, with the 2.6.30 kernels I see similar issues on my X700 Mobility card (no shared memory BTW)...

[Giancaldo (giancaldo)]

Yep, I did try the pm_trace.

Although I don't have a serial port, I do have firewire. Would that be of any help?

[Petr Šigut (petr-sigut)]

I can confirm the problem, have X200M too (Thinkpad R51e) and with DRI "off" in xorg.conf notebook suspend&resume correctly, without it, it hangs after resume.

[PhobosK (phobosk)]

I confirm this bug too. I have exactly the same issues and tested it in the same way as @Darrell Kavanagh (bug #305301) - X200M, Fujitsu-Siemens Amilo Li 1718, kernel 2.6.28-13-generic on Jaunty, suspend/hibernate working with DRI off, not working if on. I managed to get a pm_trace that says:

[ 5.135993] Magic number: 0:81:18
[ 5.136051] hash matches /build/buildd/linux-2.6.28/drivers/base/power/main.c:390

I hope this will help.

[jetdog (slicksterdave)]

Hey all... just a tip:

* The fglrx driver works amazing currently. Make sure you use the version that still includes support for the xpress 200m - I have been using it for two years and it works wounders. (Also, this will likely be your last chance to experience aiglx with opengl 3.0 - since >= 2.6.29 is no longer supported on R200-R500 series ati cards via their proprietary driver - meaning this october you will be stuck with the radeon driver once again).

The proprietary driver had no suspend issues, with catalyst 9.3 (last support ever for < 2.6.29 (i.e. THIS version of ubuntu)) - and had amazing 3d support. Remember to use the aticonfig tool on a fresh Xorg.conf if you were to try and get this driver working.

(Information for x11-drivers/xf86-video-ati, version 6.12.2 - on xorg-x11-7.2):

I'm actually having problems with suspend on the x200m card too (only with radeon driver) - Although, on my gentoo system with the above versions, the system doesn't hang, but instead I get a friendly dialog from gnome indicating that the suspend failed. This kind of bug tends to lie within xorg's domain, which is difficult support to get here on launchpad, on a hardware-specific basis, without going right to xorg.

http://www.x.org/wiki/radeon

The above link contains some documentation and support-related links for the radeon driver. Currently, on their website, it says the the status of an R400-series's suspend ability is 'unknown'. A quick google indicates that all versions of the X200, including intel, amd, and mobile variants, are R400-series cards. If I get any further, I'll be sure to let you know.

Uploaded, is my Xorg.conf for the radeon driver. Again this is =NOT= an ubuntu version, but I would suggest that if you're trying to get somewhere with crash-related issues, that you try and tweak based on the information I have (or have not) put in there.

Please be aware that the radeon driver is actually pretty good at guessing most defaults (as evident by how much I have left out)

Also, good news: apparently, there are some improvements coming for this driver, with the arrival of 2.6.31, according to phronix.

[jetdog (slicksterdave)]

I forgot to mention in my above comment. The kernel version I am using is 2.6.29 (may have something to do with it).

[gene (eugenios)]

jetdo, thank you for your suggestions.

However, my experience with the fglrx has been awful. Yes I could suspend with 3d enabled, but... only a couple times. The time of resume after every suspend grew exponentially. The other day I waited for the system to wake up for more than 18 minutes! Right now (with radeon) I disabled 3d and have a perfect suspend with the 99% of suspend taking no more than 2 secs. Performance of Xvid and other issues like cpu usage with video, audacious have always been poor plus vt's can disappear all of a sudden. Radeon also has other issues, but not so many as fglrx does. I would not recommend using fglrx!

The best solution for the future is just keep far away from the infamous red tag saying "ATI".

[gene (eugenios)]

brrr...I meant that resume from the suspend takes 2 secs

[PhobosK (phobosk)]

@jetdog , probably you are talking about the working fglrx driver on Intrepid?
I tried two versions of the driver: the one that is in the default Jaunty installation as a restricted module, and the one that is compiled on the same system (the original ATI driver v9.3). No matter what xorg.conf i used (I played with almost all the options) it didn't work on my Fujitsu Siemens Amilo Li 1718 (having Xpress 200M ATI card). By "didn't work" i mean X hang and machine becoming totally unusable without a restart.
So the only solution for me was to use the radeon driver. It works ok and almost the same way as the fglrx on Intrepid (before upgrading to Jaunty), but if you do not disable DRI, resume from suspend is not possible. Here is the part of the xorg.conf that works for me with the radeon driver:

Section "Device"
 Identifier "ATI RADEON 200M"
 Driver "radeon"
 BusID "PCI:1:5:0"

 Option "DRI" "off"

 Option "AccelMethod" "EXA"
 Option "MigrationHeuristic" "greedy"
 Option "EnablePageFlip" "on"
 Option "EnableDepthMoves" "on"
 Option "ColorTiling" "on"
 Option "AccelDFS" "on"
 Option "FBTexPercent" "0"
 Option "RenderAccel" "on"
EndSection

-------------------------------------------------
Offtopic:

As a personal point of view.... I am sure I will NOT use anything that has the brand ATI from now on. And I am planning on changing my distro... because Ubuntu was my choice at the time it was known as the most stable and at the same time having best hardware support among all distros. But this I think is past... Ever since I upgraded to Intrepid with its funny KDE4 beta, i have only problems with Ubuntu... A few days ago I decided to upgrade to Jaunty... which was a great mistake.... and i have troubles again - not only with ATI.... I never do have serious troubles on my other two PCs - gentoo and mandriva behave much better nowadays... Anyway that was totally offtopic... Sorry :)

[Petr Šigut (petr-sigut)]

I tried suspend in Ubuntu 9.10 beta. Suspended successfully, but resume ended in console with full of errors.

Can anyone confirm?

[Mark (umberstark)]

Not working for me either, Amilo LI 1718 with an X200M card. Suspends fine but won't resume, requiring a powering off and on of the laptop.

Using the stock radeon driver with 9.10 Beta (daily build, todays).

Any news on this getting fixed? I'm not one for wizbang desktop effects, but the default set add nice nice bit of polish to Gnome, that I miss when DRI is off.

[Renate (yollywau)]

I have Radeon Xpress 200M, an Acer Aspire 5100 and the same problem. It goes to suspend mode, but it doesn´t resume.
Karmic beta 2.6.31-14-generic now. I must shut down in the hard way.

Today, after the hard reboot today, /etc/mtab was corrupted. My lappie didn´t boot again because of problems with mounting.

I looked with live-CD. /etc/mtab was empty. After renaming this file, it boots again.

[Tormod Volden (tormodvolden)]

Did suspend/resume ever work on an RC410 card with the radeon driver and DRI enabled?

Not that it helps you, but the same issue for my X700 card (comment 45) is now fixed, I am not sure exactly why but I think it was the kernel.

[dimitri (dimitri-vanlanduyt)]

Not for me. Last time I suspended and resumed successfully, it was with
fglrx.

Dimitri

On 10/14/2009 02:20 PM, Tormod Volden wrote:
> Did suspend/resume ever work on an RC410 card with the radeon driver and
> DRI enabled?
>
> Not that it helps you, but the same issue for my X700 card (comment 45)
> is now fixed, I am not sure exactly why but I think it was the kernel.
>
>

[subchee (subchee)]

Hello

dimitri: so I should try out the fglrx and it should work?

2009/10/14 dimitri <email address hidden>

> Not for me. Last time I suspended and resumed successfully, it was with
> fglrx.
>
> Dimitri
>
>
> On 10/14/2009 02:20 PM, Tormod Volden wrote:
> > Did suspend/resume ever work on an RC410 card with the radeon driver and
> > DRI enabled?
> >
> > Not that it helps you, but the same issue for my X700 card (comment 45)
> > is now fixed, I am not sure exactly why but I think it was the kernel.
> >
> >
>
> --
> [RC410] Xpress 200M hangs when resuming from suspend with DRI
> https://bugs.launchpad.net/bugs/305301
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[gene (eugenios)]

Hello subchee
I would not recommend fglrx. Last time I used it, the resume from suspend would barely work when you suspend 3-4 times. You have to wait for 10 minutes after you resume sometimes before the machine is functional again.
It is better just to disable DRI with he radeon driver
good luck

[Tormod Volden (tormodvolden)]

Has anyone tried 2.6.32-rc4 from http://kernel.ubuntu.com/~kernel-ppa/mainline/ ?

[subchee (subchee)]

I'll try the new kernel from the PPA, but I think this problem is related to
the vga driver.

I don't want to disable the DRI, because when I did it, there were only 256
colors on my notebook and my desktop looked horrible. (I use screenlets and
without DRI they are ugly) And the performance is very weak without the DRI.
:-(

I wish I could code C++ :-)

2009/10/14 Tormod Volden <email address hidden>

> Has anyone tried 2.6.32-rc4 from http://kernel.ubuntu.com/~kernel-
> ppa/mainline/ <http://kernel.ubuntu.com/%7Ekernel-%0Appa/mainline/> ?
>
> --
> [RC410] Xpress 200M hangs when resuming from suspend with DRI
> https://bugs.launchpad.net/bugs/305301
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[dimitri (dimitri-vanlanduyt)]

I just tried that version of the kernel: resuming from suspend stills
hangs my machine...

Dimitri

On 10/14/2009 08:25 PM, Tormod Volden wrote:
> Has anyone tried 2.6.32-rc4 from http://kernel.ubuntu.com/~kernel-
> ppa/mainline/ ?
>

[subchee (subchee)]

I also tried the 2.6.32-rc4 from the PPA, but my notebook can't boot up that
version at all. So I couldn't try the suspend/resume with this kernel
version.

2009/10/16 dimitri <email address hidden>

> I just tried that version of the kernel: resuming from suspend stills
> hangs my machine...
>
> Dimitri
>
>
> On 10/14/2009 08:25 PM, Tormod Volden wrote:
> > Has anyone tried 2.6.32-rc4 from http://kernel.ubuntu.com/~kernel-<http://kernel.ubuntu.com/%7Ekernel->
> > ppa/mainline/ ?
> >
>
> --
> [RC410] Xpress 200M hangs when resuming from suspend with DRI
> https://bugs.launchpad.net/bugs/305301
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Tormod Volden (tormodvolden)]

I would suggest that you update the upstream (linux and xorg) bug reports again. Use karmic + 2.6.32-rc5. Check also if newest Xorg packages from xorg-edgers help. Try to describe accurately what happens at resume (e.g. if the system comes back, switches to X, but then freezes, anything in logs etc). Also what Darren did in the xorg bug report: after reboot, stop X, unload radeon/drm and then try suspend. Try also KMS, although I don't expect that to work better at this point.

[Petr Šigut (petr-sigut)]

I tried with radeon.modeset=1 and after resume only black screen and freeze... after hardware shutdown and power on the screen still black, I had to remove battery:(

Nobody respond here
https://bugs.freedesktop.org/show_bug.cgi?id=19581
I am afraid it wont be better after update:(

[Renate (yollywau)]

when I type export PM_DEBUG=true and then sudo pm-suspend, the lappie is waking up.
echo 1 > /sys/power/pm_trace and then sudo pm-suspend, it works too.

But only sudo pm-suspend or typing the button, it doesn´t resume. I tried with init 1, and it didn´t work too.

[subchee (subchee)]

Renate,
how did you do the pm-suspend? In a tty console or you opened a Gnome
Terminal? What's the version of your kernel?

With 2.6.31-14-generic kernel and from Gnome Terminal I tried what you've
written, but my machine didn't wake up. It was frozen with blank screen and
didn't respond for any key. :(

Thanks in advance

2009/10/19 Renate <email address hidden>

> when I type export PM_DEBUG=true and then sudo pm-suspend, the lappie is
> waking up.
> echo 1 > /sys/power/pm_trace and then sudo pm-suspend, it works too.
>
> But only sudo pm-suspend or typing the button, it doesn´t resume. I
> tried with init 1, and it didn´t work too.
>
> ** Attachment added: "pm-suspend.log-failed"
> http://launchpadlibrarian.net/33956385/pm-suspend.log-failed
>
> --
> [RC410] Xpress 200M hangs when resuming from suspend with DRI
> https://bugs.launchpad.net/bugs/305301
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Tormod Volden (tormodvolden)]

Renate, your suspend log shows that /usr/lib/pm-utils/sleep.d/99video was disabled. Do you know why?

I also see that it suspends with these two quirks: --quirk-vbe-post --quirk-vbemode-restore
Did anyone try disabling one of those quirks?

[Renate (yollywau)]

I didn´t change files in pm-utils. And I don´t know, why /usr/lib/pm-utils/sleep.d/99video is disabled.

When I only type sudo pm-suspend in gnome-terminal, my machine doesn´t wake up. It is frozen and does not respond for any key. I didn´t try in a tty console, but I tried with init 1, the same as recovery mode. The machine didn´t wake up.

But when I am on gnome Desktop and type in gnome-terminal first export PM_DEBUG=true and afterwards sudo pm-suspend, the machine wakes up afterwards. I don´t understand why.

[Renate (yollywau)]

I went to tty console and sudo stop gdm. Then rmmod radeon ttm and drm. Afterward pm-suspend. For this time, it was waking up afterwards.

[Tormod Volden (tormodvolden)]

What if you do not rmmod the modules, but only stop gdm?

[Renate (yollywau)]

I made only stop gdm, and it was waking up. I am surprised...

[dimitri (dimitri-vanlanduyt)]

On 10/19/2009 07:07 PM, subchee wrote:
> Renate,
> how did you do the pm-suspend? In a tty console or you opened a Gnome
> Terminal? What's the version of your kernel?
>
> With 2.6.31-14-generic kernel and from Gnome Terminal I tried what you've
> written, but my machine didn't wake up. It was frozen with blank screen and
> didn't respond for any key. :(
>
The same applies to me, I tried the instructions Renate posted, but no
successful wakeup ...

Dimitri

[Renate (yollywau)]

my kernel is 2.6.31-14-generic. in post #74, I went to tty console and typed sudo stop gdm and afterwards sudo pm-suspend. It worked for one time. I don´t know if it always works.

In post #71, I was in gnome-terminal and X and first typed export PM_DEBUG=true and then sudo pm-suspend.

[Mark (umberstark)]

I've been having this problem too, on my Amilo LI1718 (Intel chipset variant of the X200M).

Just clean installed the Ubuntu RC and it took 7 attempts for xsplash to kick in (requiring a powering off and on of the laptop every time), and suspend/resume still doesn't work.

Joy...

[subchee (subchee)]

I've made some tests, here are the results:

test#1) I've booted up my most current Karmic with default options (ro
splash in grub.conf) and then I switched to tty1 and stopped the gdm with
"sudo stop gdm" command. After that I ran "sudo pm-suspend" command. My
notebook went to spleep, but it couldn't wake up at all. Just a blank screen
appeared and I couldn't switch to another tty. The LED of the caps lock key
was blinking.

test#2) I've booted up the same system with "ro text" options in the
grub.conf. I didn't do anything special, just took a look at the output of
the "lsmod | grep ati" command. I realised, that ati_agp is loaded. After
that, I ran the "sudo pm-suspend" command. The notebook went to sleep, and
surprising, it was waken up successfully when I pressed the power key. :-)

After it waked up, I started the Gnome with "startx". When the Gnome was
started, I switched to tty1 and stopped it with "sudo stop gdm" command. I
ran "sudo pm-suspend" and my computer went to sleep. But after that, it
couldn't wake up, I had only a black screen and a blinking caps lock led,
such as in test#1. :-(

I hope this informations could help to fix this bug.

Best regards,
 Szabolcs

2009/10/23 Mark <email address hidden>

> I've been having this problem too, on my Amilo LI1718 (Intel chipset
> variant of the X200M).
>
> Just clean installed the Ubuntu RC and it took 7 attempts for xsplash to
> kick in (requiring a powering off and on of the laptop every time), and
> suspend/resume still doesn't work.
>
> Joy...
>
> --
> [RC410] Xpress 200M hangs when resuming from suspend with DRI
> https://bugs.launchpad.net/bugs/305301
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Tormod Volden (tormodvolden)]

The word from the upstream developers is that fixing this on non-KMS is just too difficult. There are too many variations between OEM boards even with the same chipset. They concentrate all efforts on getting this fixed properly in KMS. Dave Airlie recently posted a patch which made resume work on his RC410 laptop. This patch might end up in a kernel soon. If any of you are into building your own kernels, please try the patch (using KMS of course).

http://sourceforge.net/mailarchive/forum.php?thread_name=1256605062-3237-1-git-send-email-airlied%40gmail.com&forum_name=dri-devel

[subchee (subchee)]

It sounds good :)
I messed up my Karmic with fglrx and after I installed X11R7.5 from PPA and
then reinstalled the xserver-xorg-video-ati.. so now everything is mixed.
I'll try to compile a kernel, but first I need to read more about KMS..

Thanks for the info

2009/10/28 Tormod Volden <email address hidden>

> The word from the upstream developers is that fixing this on non-KMS is
> just too difficult. There are too many variations between OEM boards
> even with the same chipset. They concentrate all efforts on getting this
> fixed properly in KMS. Dave Airlie recently posted a patch which made
> resume work on his RC410 laptop. This patch might end up in a kernel
> soon. If any of you are into building your own kernels, please try the
> patch (using KMS of course).
>
> http://sourceforge.net/mailarchive/forum.php?thread_name=1256605062-3237-1
> -git-send-email-airlied%40gmail.com&forum_name=dri-devel
>
> --
> [RC410] Xpress 200M hangs when resuming from suspend with DRI
> https://bugs.launchpad.net/bugs/305301
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Elie Charest (archiesteel)]

A friend's laptop is affected by this bug as well (Xpress 200M chipset)...I might try to compile a kernel, but I haven't done it in a while. Can anyone recommend a good, up-to-date KMS HowTo?

[Tormod Volden (tormodvolden)]

There is not much special about KMS, just make sure it is enabled in the kernel configuration, and boot with radeon.modeset=1 if it's not enabled by default. See also https://wiki.ubuntu.com/X/RadeonKMS

[Elie Charest (archiesteel)]

Thanks, although disabling DRI did not appear to completely solve the issue for me...Suspend/Resume will sometimes work, sometimes not.

I'll try the same with KMS...am I right in assuming I *won't* be needing to recompile my kernel, as KMS is apparently enabled by default in recent kernels?

https://launchpad.net/~xorg-edgers/+archive/radeon-kms

I wonder if the keyboard/synaptics touchpad aren't also to blame - when I resume to a black screen, I can activate/deactive the synaptics touchpad using its on/off button, but as soon as I touch any keyboard key, the touchpad will freeze in its current state (on or off). Perhaps that's just due to the X crash, however...

[Tormod Volden (tormodvolden)]

Elie, you will need to compile the kernel yourself in order to include the patch from Dave Airlie.

[Elie Charest (archiesteel)]

Sorry, sorry, you're right of course.

That said, I did try enabling KMS, and I can now suspend/resume without a hitch after deactivating DRI (which I couldn't before enabling KMS, even with DRI deactivated). More surprisingly, I can now suspend and resume even *with* DRI (and visual effects) enabled!

So I'll refrain from compiling a new kernel for now and continue testing this...but for all practical purposes switching KMS on solved my problem...

[Petr Šigut (petr-sigut)]

> Xpress 200M hangs when resuming from suspend with DRI (needs
> + KMS)

I disagree, (at least on my machine - Thinkpad R51e) it still does not work, I boot with radeon.modeset=1, and after pm-suspend I can't resume - only black screen, no reaction, need unplug&plug battery to boot again...

[Tormod Volden (tormodvolden)]

Petr, I guess you are running without the patch mentioned above.

[subchee (subchee)]

Tormod,

could please make a file from the patch? Because I don't know where is the
beginning and where is the ending of the patch, what should be in the patch
file... :(

Thanks in advance

2009/10/30 Tormod Volden <email address hidden>

> Petr, I guess you are running without the patch mentioned above.
>
> --
> [RC410] Xpress 200M hangs when resuming from suspend with DRI (needs KMS)
> https://bugs.launchpad.net/bugs/305301
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Petr Šigut (petr-sigut)]

> Petr, I guess you are running without the patch mentioned above.
You are right, I am sorry, I thought Elie Charest trying unpatched kernel too... but I think name of this bug should be "...suspend with DRI (needs KMS _and compiled patched kernel_) because just KMS do not solve the problem:)

Now I am trying to compile the kernel, but have troubles

The UTS Release version in include/linux/version.h
           ""
does not match current version:
           "2.6.32-rc5-custom1-next-20091029"

but this is different story.

[Elie Charest (archiesteel)]

Actually, I did try it with the unpatched 2.6.31-14 kernel and turning KMS on, and it works (though I sometimes lose keyboard and touchpad upon resume).

This is on a Compaq Presario V2310, which has a Turion64 processor (though I'm running 32-bit Karmic on it), so perhaps the problem isn't due *only* to the graphics chipset, but a combination of factors (which are among the worst bugs out there along with random crashes).

Let me know if I can provide any information, logs, etc. to help solve this issue.

[subchee (subchee)]

Which kernel source should be patched with Dave's patch? Because I tried
with the current (today) Ubuntu kernel source, but the patch failed with
this error: "patching file rs400.c Hunk #1 FAILED at 418."

I tried with 2.6.31-14 source also, but there were the same error with it
(it's rs400.c file doesn't have 418 line anyway).

2009/10/30 Elie Charest <email address hidden>

> Sorry, sorry, you're right of course.
>
> That said, I did try enabling KMS, and I can now suspend/resume without
> a hitch after deactivating DRI (which I couldn't before enabling KMS,
> even with DRI deactivated). More surprisingly, I can now suspend and
> resume even *with* DRI (and visual effects) enabled!
>
> So I'll refrain from compiling a new kernel for now and continue testing
> this...but for all practical purposes switching KMS on solved my
> problem...
>
> --
> [RC410] Xpress 200M hangs when resuming from suspend with DRI
> https://bugs.launchpad.net/bugs/305301
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Petr Šigut (petr-sigut)]

> Which kernel source should be patched with Dave's patch?

Dave's patch is already in linux-next

http://git.kernel.org/?p=linux%2Fkernel%2Fgit%2Fnext%2Flinux-next.git&a=search&h=HEAD&st=author&s=Dave+Airlie+

So I downloaded (kernel.org) full source of 2.6.32-rc5 and patched it to linux-next, successfully.

[Tormod Volden (tormodvolden)]

It might be easy to use the source package from the http://kernel.ubuntu.com/~kernel-ppa/mainline/ but I haven't tried.

[subchee (subchee)]

Can somebody upload a compiled kernel with Dave's patch, please? I
couldn't compile the linux-next because of several errors and I can't
apply Dave's patch the 2.6.32-rc5 kernel (source is downloaded from
Ubuntu kernel PPA), because of an error (Hunk #1 FAILED at 418.).

Thanks in advance

2009/10/30 Tormod Volden <email address hidden>
>
> It might be easy to use the source package from the
> http://kernel.ubuntu.com/~kernel-ppa/mainline/ but I haven't tried.
>
> --
> [RC410] Xpress 200M hangs when resuming from suspend with DRI (needs KMS)
> https://bugs.launchpad.net/bugs/305301
> You received this bug notification because you are a direct subscriber
> of the bug.

[Tormod Volden (tormodvolden)]

subchee, I haven't downloaded the full sources, but I picked the rs400.c file from the 2.6.32-rc5 git tag, and the patch applied well. So I guess you are not running the patch command correctly. Try something like: "patch drivers/gpu/drm/radeon/rs400.c ~/Desktop/patch-from-dave.patch" and use the raw patch from http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=commitdiff_plain;h=ea1495a6274c9542a168337536f8ce74d1173f23

[subchee (subchee)]

Thank you, I'll take a try.

2009/11/1 Tormod Volden <email address hidden>:
> subchee, I haven't downloaded the full sources, but I picked the rs400.c
> file from the 2.6.32-rc5 git tag, and the patch applied well. So I guess
> you are not running the patch command correctly. Try something like:
> "patch drivers/gpu/drm/radeon/rs400.c ~/Desktop/patch-from-dave.patch"
> and use the raw patch from
> http://git.kernel.org/?p=linux/kernel/git/next/linux-
> next.git;a=commitdiff_plain;h=ea1495a6274c9542a168337536f8ce74d1173f23
>
> --
> [RC410] Xpress 200M hangs when resuming from suspend with DRI (needs KMS)
> https://bugs.launchpad.net/bugs/305301
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[subchee (subchee)]

Hello all,

I've downloaded the latest 2.6.32-rc5 kernel build from Ubuntu PPA,
which contains Dave's patch. The KMS is enabled. The problem still
exists, my notebook (with RC410 chip) can't wake up from suspend. When
I try to resume, it's going to completely frozen state, I've got to
remove the battery from it. :-(

2009/11/1 Szabolcs Fazekas <email address hidden>:
> Thank you, I'll take a try.
>
> 2009/11/1 Tormod Volden <email address hidden>:
>> subchee, I haven't downloaded the full sources, but I picked the rs400.c
>> file from the 2.6.32-rc5 git tag, and the patch applied well. So I guess
>> you are not running the patch command correctly. Try something like:
>> "patch drivers/gpu/drm/radeon/rs400.c ~/Desktop/patch-from-dave.patch"
>> and use the raw patch from
>> http://git.kernel.org/?p=linux/kernel/git/next/linux-
>> next.git;a=commitdiff_plain;h=ea1495a6274c9542a168337536f8ce74d1173f23
>>
>> --
>> [RC410] Xpress 200M hangs when resuming from suspend with DRI (needs KMS)
>> https://bugs.launchpad.net/bugs/305301
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>

[Petr Šigut (petr-sigut)]

The 2.6.32-rc5 does not contain the patch.

[Tormod Volden (tormodvolden)]

subchee, which PPA are you talking about? As far as I know, there is no PPA that has this patch included.

[subchee (subchee)]

I talk about this PPA:
http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/

I've downloaded the source and checked the
/drivers/gpu/drm/radeon/rs400.c and the patch is in it.

As far as I know the daily kernel images was built from the source
what I downloaded. FIXME

2009/11/3 Tormod Volden <email address hidden>:
> subchee, which PPA are you talking about? As far as I know, there is no
> PPA that has this patch included.
>
> --
> [RC410] Xpress 200M hangs when resuming from suspend with DRI (needs KMS)
> https://bugs.launchpad.net/bugs/305301
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Tormod Volden (tormodvolden)]

Sounds good, the Mainline Kernel PPA. It is not 2.6.32-rc5 any longer then, but a daily build.

In this case it would make sense to add to the upstream bug report that the issue has not been fixed by Dave's patch, at least on your hardware.

[Petr Šigut (petr-sigut)]

> I've downloaded the source and checked the
>/drivers/gpu/drm/radeon/rs400.c and the patch is in it.

well, if I diff rs400.c from Ubuntu daily PPA and from linux 2.6.32-rc5 patched to next:
diff rs400.c /usr/src/linux-2.6.32-rc5/drivers/gpu/drm/radeon/rs400.c
420a421,422
> /* setup MC before calling post tables */
> rs400_mc_program(rdev);

so it seems not patched to me? Please correct me:)

[Tormod Volden (tormodvolden)]

You can see that the file has not been touched in a while in Linus's tree:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=history;f=drivers/gpu/drm/radeon/rs400.c;hb=HEAD
So the patch is not included in 2.6.32-rc6 either, which was released a few hours ago.

[gene (eugenios)]

Thanks a lot to Tormod and everyone!

Nevertheless, this "fix" does not seem to work for me. Now I am on patched and self-built kernel
uname -a gives " 2.6.32-rc5-custom #1 SMP Sun Nov 8 01:19:08" I edited rs400.c file on emacs, so it kept the original (~). Here's the diff output:

 diff instal/linux-source-2.6.32/drivers/gpu/drm/radeon/rs400.c~ instal/linux-source-2.6.32/drivers/gpu/drm/radeon/rs400.c
420a421,422
> /* setup MC before calling post tables */
> rs400_mc_program(rdev);

Further, I commented off the "dri off" line and the dri effects can work now. However, when resuming from suspend I get my laptop to unsuccessfully attempt to wake up with no avail. So, as always, I have to power it off.

Let me know what you think about this, guys

[gene (eugenios)]

Forgot to mention, I did not upgrade yet, so I am still on jaunty.

[Petr Šigut (petr-sigut)]

I tried Fedora 12 beta, which have patched kernel and it is even worse:) Not only I can't wake up, the Xorg is very unstable with KMS...

https://bugzilla.redhat.com/show_bug.cgi?id=533567

[gene (eugenios)]

All right guys,

I upgraded to 9.10. I can now witness the failure of the patch for my laptop to wake up successfully after suspend. I am on my self-build kernel 2.6.32-rc5.

Well, there might be some specifics in the /etc/X11/xorg.conf file Dave Arlie was using. I wonder, what was that?
Tormod, please, let me know if are aware of it
Thanks

[Tormod Volden (tormodvolden)]

I am pretty sure Dave is running without any xorg.conf (on Fedora 12).

[gene (eugenios)]

So, I would like to explain again what I did.

Downloaded the source package of 2.6.32-rc5 from ppa. Patched the rs400.c file (with emacs, not the patch command). Used my old config file to buikd the kernel using make-kpkg command and with the kernel debug off option.

Tormod, when you say "needs KMS", what do you mean? The patch or more than that, like some extra options to be checked with the menuconfig process?

I noticed, that versions as of 1.6.28* lacked some of the files related to radeon completely, like rs400.c. Is this what you call KMS?
Thanks

[subchee (subchee)]

I've built a 2.6.32-rc6 kernel with a patched rs400.c file (I patched
also "by hand") and it's also not working. For me, it's worst than the
2.6.31-14-generic kernel, because after the boot I've got only a
800x600 screen resulotion. After the suspend my notebook can't wake
up, just hangs on with a black screen and a lighting hdd led.. but
it's completely frozen.

I've also built a linux-next kernel (patched with "nov 6" patchset)
and in this source tree the rs400.c is already patched. With this
kernel I've got the same errors as with the 2.6.32-rc6 built on my
own..

2009/11/9 gene <email address hidden>:
> So, I would like to explain again what I did.
>
> Downloaded the source package of 2.6.32-rc5 from ppa. Patched the
> rs400.c file (with emacs, not the patch command). Used my old config
> file to buikd the kernel using make-kpkg command and with the kernel
> debug off option.
>
> Tormod, when you say "needs KMS", what do you mean? The patch or more
> than that, like some extra options to be checked  with the menuconfig
> process?
>
> I noticed, that versions as of 1.6.28* lacked some of the files related to radeon completely, like rs400.c. Is this what you call KMS?
> Thanks
>
> --
> [RC410] Xpress 200M hangs when resuming from suspend with DRI (needs KMS)
> https://bugs.launchpad.net/bugs/305301
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Tormod Volden (tormodvolden)]

gene, you will have to enable KMS if it is not on by default (it is not in the Ubuntu configuration). See comment 82.

[gene (eugenios)]

I will investigate this. However, I have a commented lene
# CONFIG_DRM_I915_KMS is not se
  in my kernel config. I skipped it, since I thought it was pertinent to intel chips.

Interesting, people reporting it not to work and brings more issues. In my case, besides the fact that the laptop boots SLOWER, the kernel is "fast" and nice. Could that misbehaving thing be a KMS option?
I will try to build with KMS and will compare.

Thanks

[gene (eugenios)]

Guys,
I have a request no to publish our email addresses. It would also be nice if a moderator could erase these.
Thanks

[flashog (wispster)]

I have the same issues and I really can't be bothered messing around with building my own kernel at the moment, so I'm curious to know what the ETA is for it to be implemented for us "common folks"?

[Tormod Volden (tormodvolden)]

gene, your e-mail address is not exposed, unless some people answer to the bug mail instead of posting comments via the web interface (please use the web interface) and quotes your e-mail and includes your e-mail address (please never quote mail if you absolutely have to use mail instead of web). In all cases, the web interface will try to hide all e-mail addresses from people who are not logged into launchpad.

subchee, you in particular should stop quoting everybody. It also makes the report long and unreadable.

gene, I915 is only for Intel cards. Your kernel is probably built with KMS support, you just need to enable it as explained in the wiki. You will see your text console getting small fonts, and loads of drm messages about resolution settings etc in dmesg.

flashog, we hope this will be solved in time for Ubuntu 10.04.

[gene (eugenios)]

Sorry about the whining, Tormod :)
I did as you suggested and a nice tiny font showed up in all of my vt's. Alas, it does not help our problem.
Once again after the suspend I cannot wake up the machine. Any ideas? Thanks

To flashdog: Well, first you might want to wait until this "fix" will help us, then we'll see :)
Actually, I also thought that building a kernel is a big deal, turned out to be a piece of cake. I can forward you the tutorial I was using.

[flashog (wispster)]

I used to compile my own kernels in gentoo all the time, but it's just all those options. I know it's gonna take some time to do the first couple of times, and I'm just too lazy at the moment.. maybe I should try though, but as you pointed out, it's rather useless if we already know that it won't solve the problem.

Cheers.

[subchee (subchee)]

Sorry guys for replying for emails, that why my comments are full of quotes.

Today I downloaded the 2.6.32-rc7 kernel and realized that Dave Arlie's patch is in it. So I compiled the kernel.
First, the radeon driver was built within the kernel (with option Y/*). In this way I can't boot up my machine with graphical environment.
Second, the radeon driver was built as a kernel module. This way the kernel works fine, everything is booting up normally (except my Atheros wifi, but it's another story), but the resume from suspend still doesn't work. It's the same as it was: seems like successfully suspend, but can't wake up, the notebook is completely frozen. :(

If you need further information or some output to find the bug, please write me.

[gene (eugenios)]

I tried rc7 too and it gave me a system lock with kms immediately. So I cannot say anything about the suspend problem here, sorry :(

I do not understand what subchee means about the radeon as a loadable module. It alway is, isn't it? It is build with the kernel together with hundreds of other ones... As far as the atheros module is concerned, I use the madwifi, which is supposed to be build outside of the kernel compilation. And every time for a custom kernel I have to compile it separately from source, not a big deal though. Most of people use ath5k or ath9k modules instead, which are built with the kernel....

[gene (eugenios)]

Tormod, should we change "needs KMS"? Although, kms is a great feature and everyone needs it, it does not help solving our problem even with the patch provided by Dave. Please, let me know, thanks

[Tormod Volden (tormodvolden)]

Yes, we still need KMS to get this fixed, but KMS needs fixing too :) It is pretty clear (from upstream) that this will never be fixed in the old non-KMS path. I can only recommend that you confirm in the freedesktop bug that -rc7 does not help.

Ubuntu 10.04 will probably use KMS by default on radeon, so it is good that you test it and help iron out bugs. The upstream developers do not care so much about non-KMS bugs any longer, and Ubuntu can not do this on its own.

[subchee (subchee)]

gene, not everything is a kernel module if you compile your own kernel. You can compile drivers directly into your new kernel image (vmlinuz). When you run "make menuconfig" you've got 3 options by side of components (eg. drivers): M means compile as module, * or Y means compile directly into the kernel, nothing or N means do not compile that part (neither as module nor part of the vmlinuz).

Tormod, could you please tell me where can I follow the status of the radeon driver development? :)
(I know that I could check the git sources on kernel.org every day but I'd like see some roadmap or something like that regarding the radon driver development if it's possible)

[Tormod Volden (tormodvolden)]

Yes, to follow the development git is the place: http://cgit.freedesktop.org/xorg/driver/xf86-video-ati/ and http://cgit.freedesktop.org/mesa/mesa/log/ or to see what the developers are discussing: IRC #radeon
For status on different features on cards, see http://wiki.x.org/wiki/RadeonFeature and other pages there.

[gene (eugenios)]

Hi guys!
I have a request to everyone with rc410 chip.

Have you been experiencing any system freezes lately? I do and the logs at the time of crashes are either missing or garbled. I reported this https://bugs.launchpad.net/ubuntu/+source/linux/+bug/489447

Freezes occur when I am with the radeon.modeset=1 boot option with compiz and when some windows are being manipulated (resized, moved etc). Have not tried without kms yet.
Please let me know
Thanks

[subchee (subchee)]

Have somebody tried out the latest kernel (2.6.33-rc1)? If yes, could you tell me please if the problem is still egzists? (I can't try it out, because I switched to Debian Lenny, it's stable and with the fglrx driver it works fine, 2 times faster (3D) than with radeon driver and suspend/resume also works)

[Petr Šigut (petr-sigut)]

I tried, just boot with KMS and suspend - and it does not work:(

[gene (eugenios)]

I do not think I will be interested in KMS in the nearest future, since it brings so many other much more serious bugs. So the question of whether a machine can resume from suspend or not is not important anymore. If and when suspend finally works for rc410, you might want to pay a little bit more attention to my comment #124.

[Apoorv Parle (apparle)]

I have Radeon Xpress 200 (RC410) on Foxconn RC410MA motherboard
Hibernate works fine
I also cannot resume from suspend. I have checked only with Karmic.
I didn't try building kernels and stuff but would surely try it when I have enough time

Being a desktop user suspend doesn't matter much to me.

[Karesz (lengyel-karesz)]

Have this problem got any better with the new 2.6.33 kernel? (It included radeon KMS)

[Mark (umberstark)]

Still happening for me (Amilo LI 1718) with the daily live CD (26th).

If I boot with radeon.modeset=0 the desktop won't corrupt and lock up after a few minutes as it does without this option set. But still won't resume the display from suspend or hibernate. Also, using that option results in a garbled login screen until I press alt+SysRq+K .

[Apoorv Parle (apparle)]

I have not tested on latest kernel but I have been facing the problem ever
since I have been using the earlier kernels ever since I have been using the
radeon driver. And the ati driver is same... it just calls the radeon driver

On Sat, Feb 27, 2010 at 7:10 AM, Karesz <email address hidden> wrote:

> Have this problem got any better with the new 2.6.33 kernel? (It
> included radeon KMS)
>
> --
> [RC410] Xpress 200M hangs when resuming from suspend with DRI (needs KMS)
> https://bugs.launchpad.net/bugs/305301
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in The Bugzilla Bug Tracking System: Invalid
> Status in The Linux Kernel: Invalid
> Status in X.Org X server: Invalid
> Status in “linux” package in Ubuntu: Confirmed
> Status in “xserver-xorg-video-ati” package in Ubuntu: Triaged
>
> Bug description:
> Binary package hint: xserver-xorg-video-radeon
>
> Since I upgraded to 8.10 from 8.04 the machine does not resume from
> suspend.
> 1) Depending on the tools it behaves the following way: when using usual
> (gnome) suspend, when trying to resume it turns on and off with a blank
> screen. When using pm-utils, it turns on but the screen is blank. In all of
> these cases, the system is irresponsive and requires a hard reboot (held
> down power button). Sometimes the system just restarts (reboots) on its own
> after one attempt.
> 2) There is also one more problem with the X that is conected.
> Occasionally, when booting the system before getting the login window the
> system hangs with the blank screen. It also remains totally irresponsive
> with no Magic Keys working.
>
> The reason why I think the issue is related to "radeon" driver is the
> following. I've had a lot of problems be with the ATI/AMD proprietary fglrx
> driver (no dual head support, no xvid etc). However, when I upgraded to
> 8.10 I found the fglrx in use. Again, the performance was not good either
> (bad xv support and slow). But I could resume from suspend OK and do not
> remember any crashes when booting. I removed it and started using "radeon"
> driver. The performance was better, but I started experiencing the
> above-mentioned problems. I also tried "ati" driver (not sure if there is
> difference ) bu with no avail.
> Someone found a similar bug a couple months ago and followed the suggested
> change in the Xorg.conf by trying different values for Option "AGPMode". it
> didn't work. I also tried hibernate tools. It did similar things. I tried
> with/without compiz, gives the same problem, as well as with the generic
> Xorg.conf file. I attach both below
> My laptop is Toshiba Satellite l35 with ATI Technologies Inc RC410 [Radeon
> Xpress 200M].
>
> $uname -a
> 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686
> GNU/Linux
> I am attaching some useful files below.
> Thanks very much in advance for your help!
> [lspci]
> 00:00.0 Host bridge: ATI Technologies Inc Device 5a31 (rev 01)
> 01:05.0 VGA compatible controller: ATI Technologies Inc RC410 [Radeon
> Xpress 200M] [1002:5a62]
>
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/bugzilla/+bug/305301/+subscribe
>

--
Absenc...

[gene (eugenios)]

We should be talking about two problems now. As I stated in #124, kms's introduces a more severe issue with "radeon.modeset=1" option causing the kernel to freeze on my machine while failing to fix the resume-after-suspend problem.

This results in the corrupted rsyslog data and makes it impossible (for me, at least) to debug. These is all exacerbated by everyone's silence and neglect.

Instead of trying to "fix" this issue, the community, in my mind, should compile a list of devices stubbornly adverse to the linux/BSD systems.

[Karesz (lengyel-karesz)]

Anyone who's affected by this bug, should take a look at this one: https://bugs.launchpad.net/bugs/509273
and take a try, if that one also affects her/him, and give a click to the "also affects me" button.

[Bryce Harrington (bryce)]

The upstream bug task on this report appears to be closed as fixed. Given the large number of comments on this bug I think maybe it's grown stale.

A couple options going forward:
a) Dupe this bug report to #509273 if it is indeed the same problem
b) File a new bug report upstream at bugs.freedesktop.org about the current state of the problem, and link a new upstream bug task here

Please let us know what option you think should be taken here. And if (b), if you feel like it please go ahead and do it.

[gene (eugenios)]

Well, I need to see that "fix". Tried with the option "radeon.modeset=1" and "pci=nomsi" options with 2.6.31-20-generic. Did not seem to get modesetting 1 at first, had to kill gdm and set it manually. Tried suspending - the good old problem remains.

#50927 seems to be related, however it talks about different chipsets (no RC410 and amd cpu ). I built and tested 2.6.32-rc5-custom and did not experience problems reported, except some ones (perhaps msi). Maybe a similar issue awaits us with ver. 33 and in Lucid. It will be scary to upgrade then :)

[Mark (umberstark)]

Would there be any benefit in providing the BIOS of the cards? There's a windows utility (not sure about one for linux) called ATI Tray Tools that can download it from the card in .bin format.

[gene (eugenios)]

Bryce, yes http://bugs.freedesktop.org/show_bug.cgi?id=22140 is a different one it is supposed to be fixed in 6.12 it says, the chip is RS482 . Can you file another one for us? Let me know, thanks.

to Mark: I guess on Linux you can use various utilities, "sudo lshw" is one of them. I think RC410 has the known internals, except what is the bloody ATI's secret (unavailable even to any Windows utility). This is the mother of all problems people have with ATI, in part., and with hardware, in general. Damn ATI!

[subchee (subchee)]

"Changed in: xserver-xorg-video-ati (Debian)
status: Unknown → Fix Released"

Is it serious? Should I try out the Debian sid?

[Apoorv Parle (apparle)]

It seems there are a lot of things similar to RS482 in my motherboard...
because it required a patch for soundcard similar to one required on a RS482
board.
Anyways....so is this fixed in general for both RS482 and RC410, or anyone
is filing new bug for RC410? And how much time would it take to get it fixed
in ubuntu?

On Thu, Apr 1, 2010 at 8:59 AM, gene <email address hidden> wrote:

> Bryce, yes http://bugs.freedesktop.org/show_bug.cgi?id=22140 is a
> different one it is supposed to be fixed in 6.12 it says, the chip is
> RS482 . Can you file another one for us? Let me know, thanks.
>
> to Mark: I guess on Linux you can use various utilities, "sudo lshw" is
> one of them. I think RC410 has the known internals, except what is the
> bloody ATI's secret (unavailable even to any Windows utility). This is
> the mother of all problems people have with ATI, in part., and with
> hardware, in general. Damn ATI!
>
> --
> [RC410] Xpress 200M hangs when resuming from suspend with DRI (needs KMS)
> https://bugs.launchpad.net/bugs/305301
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in The Bugzilla Bug Tracking System: Invalid
> Status in The Linux Kernel: Invalid
> Status in X.Org X server: Fix Released
> Status in “linux” package in Ubuntu: Confirmed
> Status in “xserver-xorg-video-ati” package in Ubuntu: Triaged
>
> Bug description:
> Binary package hint: xserver-xorg-video-radeon
>
> Since I upgraded to 8.10 from 8.04 the machine does not resume from
> suspend.
> 1) Depending on the tools it behaves the following way: when using usual
> (gnome) suspend, when trying to resume it turns on and off with a blank
> screen. When using pm-utils, it turns on but the screen is blank. In all of
> these cases, the system is irresponsive and requires a hard reboot (held
> down power button). Sometimes the system just restarts (reboots) on its own
> after one attempt.
> 2) There is also one more problem with the X that is conected.
> Occasionally, when booting the system before getting the login window the
> system hangs with the blank screen. It also remains totally irresponsive
> with no Magic Keys working.
>
> The reason why I think the issue is related to "radeon" driver is the
> following. I've had a lot of problems be with the ATI/AMD proprietary fglrx
> driver (no dual head support, no xvid etc). However, when I upgraded to
> 8.10 I found the fglrx in use. Again, the performance was not good either
> (bad xv support and slow). But I could resume from suspend OK and do not
> remember any crashes when booting. I removed it and started using "radeon"
> driver. The performance was better, but I started experiencing the
> above-mentioned problems. I also tried "ati" driver (not sure if there is
> difference ) bu with no avail.
> Someone found a similar bug a couple months ago and followed the suggested
> change in the Xorg.conf by trying different values for Option "AGPMode". it
> didn't work. I also tried hibernate tools. It did similar things. I tried
> with/without compiz, gives the same problem, as well as with the generic
> Xorg.conf file. I attach both below
> My laptop is Toshiba Satellite l35 with AT...

[acimmarusti (andrescimmarusti)]

Though I haven't been running Ubuntu in a long time, I've experienced this issue with Debian Squeeze. I've been constantly tracking this ubuntu bug for a workaround.
Fortunately I've found a fix that is working pretty well for me.

Go to System Tools > Configuration Editor
Now browse to: apps/gnome-power-manager/general/network_sleep
Enable network_sleep by checking the box.

Now try to suspend/hibernate!

My specs are:

Laptop: HP Pavilion dv5035nr
Video card: ATI Tecnologies Inc Radeon Xpress 200M 5955 (PCIE)
Kernel: 2.6.32-4 (basically 2.6.32.9 upstream with NO backported DRM from 2.6.33)
Radeon driver: 6.12.6 (No KMS capable!)

What strikes me the most about this, is that it works with DRI enabled and user modesetting (no KMS needed). I haven't tried this with KMS enabled. I will try it once Squeeze gets its 2.6.32-10 kernel (with DRM backported from 2.6.33) and the KMS capable radeon driver 6.12.192 or 6.13.0

I got the fix from: http://bbs.archlinux.org/viewtopic.php?pid=705928

Hope this solves this bug once and for all!

[gene (eugenios)]

2 acimmarusti : Thanks, I will try this out. However, I doubt it would work. First, your chip is different. I got rc410. Yours is 5955. I once installed Ubuntu on a friends computer last year. It was a desktop x200m with an amd cpu. I feared that Linux would be hostile to the neophytes. Everything went smoothly though then. It never worked for me with dri enabled.

I have no network_sleep nowhere in my gnome configs. gnome-power manager does not have. Maybe it is a different version.

2 Apoorv Parle: of course these two chips have a lot in common, I suppose. the are all x200m series. However , only rc410 is specially honored with this bug. If you'd like to file the bug, it'd be appreciated. I also have a request to you and to the launchpad team. PLEASE, do not publish our email addresses! there's no need to dump the old comments also.

[gene (eugenios)]

It is funny, status : fix released. Is it known to work? Where to find it? The fix was released 4 months ago?

I pretty much do not care. I am happy with no dri. GNU/Linux gave me so much opportunity on this chip laptop a Windex user would have never even dreamed of.

The lesson learned: stay away from ATI (and maybe AMD). Listen to rms more carefully next time.

offtopic: why is it not possible to use w3m with emacs to write the comments?

[acimmarusti (andrescimmarusti)]

Gene,

It's highly likely our chips are different, but they all seem related to RC410 -> http://www.x.org/wiki/Radeon%20ASICs

Nevertheless, try this: in a terminal run gconf-editor

Now there browse to: apps/gnome-power-manager/general/

On the righthand side you should see network_sleep (hopefully) and you can activate it.

Hope it works

[Mark (umberstark)]

The "network_sleep" tweak didn't work for me, Amilo LI1718 X200M, although I haven't tried with KMS disabled, as booting with "pci=nomsi" fixed the problem with KMS for me (although not all), and I'm reluctant to mess with that now.

[Mark (umberstark)]

As a follow up. As always happens after an unsuccessful suspend/sleep, my networking is now dead (not related to the "network_sleep" setting), both wired and wireless.

Re-install time...

[acimmarusti (andrescimmarusti)]

Mark,

I was having this problem before, you don't need to reinstall.

Just remove this file:

sudo rm /var/lib/NetworkManager/NetworkManager.state

This is known problem with Network-Manager: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571331

Now restart and upon login everything should work right

Andres

[gene (eugenios)]

2 acimmarusti: thanks a lot. It did not work. Strange that the "find" utility in gconf-editor did not fetch "network_sleep" for me. Anyways, isn't it network related option not our marvelous ATI card. So it might be that very secret of the damned ATI to include some specialty in rc410 only that prevents it from functioning properly with our FOSS driver (with dri enabled), as a matter of fact, the ATI's own driver fglrx is much much worse! Maybe in a few hundred years .....

Thanks again, acimmarusti!

[Apoorv Parle (apparle)]

Finally has anyone filed the bug for our chipset upstream similar to RS482,
I could have done but I am new to all this and not as experienced in linux
as you guys

On Fri, Apr 2, 2010 at 11:55 PM, gene <email address hidden> wrote:

> 2 acimmarusti: thanks a lot. It did not work. Strange that the "find"
> utility in gconf-editor did not fetch "network_sleep" for me. Anyways,
> isn't it network related option not our marvelous ATI card. So it might
> be that very secret of the damned ATI to include some specialty in
> rc410 only that prevents it from functioning properly with our FOSS
> driver (with dri enabled), as a matter of fact, the ATI's own driver
> fglrx is much much worse! Maybe in a few hundred years .....
>
> Thanks again, acimmarusti!
>
> --
> [RC410] Xpress 200M hangs when resuming from suspend with DRI (needs KMS)
> https://bugs.launchpad.net/bugs/305301
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in The Bugzilla Bug Tracking System: Confirmed
> Status in The Linux Kernel: Invalid
> Status in X.Org X server: Fix Released
> Status in “linux” package in Ubuntu: Confirmed
> Status in “xserver-xorg-video-ati” package in Ubuntu: Triaged
>
> Bug description:
> Binary package hint: xserver-xorg-video-radeon
>
> Since I upgraded to 8.10 from 8.04 the machine does not resume from
> suspend.
> 1) Depending on the tools it behaves the following way: when using usual
> (gnome) suspend, when trying to resume it turns on and off with a blank
> screen. When using pm-utils, it turns on but the screen is blank. In all of
> these cases, the system is irresponsive and requires a hard reboot (held
> down power button). Sometimes the system just restarts (reboots) on its own
> after one attempt.
> 2) There is also one more problem with the X that is conected.
> Occasionally, when booting the system before getting the login window the
> system hangs with the blank screen. It also remains totally irresponsive
> with no Magic Keys working.
>
> The reason why I think the issue is related to "radeon" driver is the
> following. I've had a lot of problems be with the ATI/AMD proprietary fglrx
> driver (no dual head support, no xvid etc). However, when I upgraded to
> 8.10 I found the fglrx in use. Again, the performance was not good either
> (bad xv support and slow). But I could resume from suspend OK and do not
> remember any crashes when booting. I removed it and started using "radeon"
> driver. The performance was better, but I started experiencing the
> above-mentioned problems. I also tried "ati" driver (not sure if there is
> difference ) bu with no avail.
> Someone found a similar bug a couple months ago and followed the suggested
> change in the Xorg.conf by trying different values for Option "AGPMode". it
> didn't work. I also tried hibernate tools. It did similar things. I tried
> with/without compiz, gives the same problem, as well as with the generic
> Xorg.conf file. I attach both below
> My laptop is Toshiba Satellite l35 with ATI Technologies Inc RC410 [Radeon
> Xpress 200M].
>
> $uname -a
> 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686
> GNU/Linux
> I am attac...

[Bryce Harrington (bryce)]

[This is an automatic notification.]

Hi gene,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 305301

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 305301 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/305301

[Karesz (lengyel-karesz)]

Well, I'm not Gene, but can confirm, that this bug still exists in Lucid :(

2010/5/5 Bryce Harrington <email address hidden>

> [This is an automatic notification.]
>
> Hi gene,
>
> This bug was reported against an earlier version of Ubuntu, can you
> test if it still occurs on Lucid?
>
> Please note we also provide technical support for older versions of
> Ubuntu, but not in the bug tracker. Instead, to raise the issue through
> normal support channels, please see:
>
> http://www.ubuntu.com/support
>
>
> If you are the original reporter and can still reproduce the issue on
> Lucid, please run the following command to refresh the report:
>
> apport-collect 305301
>
> If you are not the original reporter, please file a new bug report, so
> we can work with you as the original reporter instead (you can reference
> bug 305301 in your report if you think it may be related):
>
> ubuntu-bug xorg
>
> If by chance you can no longer reproduce the issue on Lucid or if you
> feel it is no longer relevant, please mark the bug report 'Fix Released'
> or 'Invalid' as appropriate, at the following URL:
>
> https://bugs.launchpad.net/ubuntu/+bug/305301
>
>
> ** Changed in: xserver-xorg-video-ati (Ubuntu)
> Status: Triaged => Incomplete
>
> ** Tags added: needs-retested-on-lucid-by-june
>
> --
> [RC410] Xpress 200M hangs when resuming from suspend with DRI (needs KMS)
> https://bugs.launchpad.net/bugs/305301
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Karesz (lengyel-karesz)]

I don't know if Gene is still watching this bug, but in case he doesn't,
should i file a new bug report about this?

2010/5/6 Lengyel Karesz <email address hidden>

> Well, I'm not Gene, but can confirm, that this bug still exists in Lucid :(
>
> 2010/5/5 Bryce Harrington <email address hidden>
>
> [This is an automatic notification.]
>>
>> Hi gene,
>>
>> This bug was reported against an earlier version of Ubuntu, can you
>> test if it still occurs on Lucid?
>>
>> Please note we also provide technical support for older versions of
>> Ubuntu, but not in the bug tracker. Instead, to raise the issue through
>> normal support channels, please see:
>>
>> http://www.ubuntu.com/support
>>
>>
>> If you are the original reporter and can still reproduce the issue on
>> Lucid, please run the following command to refresh the report:
>>
>> apport-collect 305301
>>
>> If you are not the original reporter, please file a new bug report, so
>> we can work with you as the original reporter instead (you can reference
>> bug 305301 in your report if you think it may be related):
>>
>> ubuntu-bug xorg
>>
>> If by chance you can no longer reproduce the issue on Lucid or if you
>> feel it is no longer relevant, please mark the bug report 'Fix Released'
>> or 'Invalid' as appropriate, at the following URL:
>>
>> https://bugs.launchpad.net/ubuntu/+bug/305301
>>
>>
>> ** Changed in: xserver-xorg-video-ati (Ubuntu)
>> Status: Triaged => Incomplete
>>
>> ** Tags added: needs-retested-on-lucid-by-june
>>
>> --
>> [RC410] Xpress 200M hangs when resuming from suspend with DRI (needs KMS)
>> https://bugs.launchpad.net/bugs/305301
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>
>

[gene (eugenios)]

2 Karesz
This is ok with me. I do keep an eye on this one, however, I don't have much faith in the slogan "kms+rc410=love", in another other life maybe... Since the upgrade to 10.04 I get a lot of bugs which as a good citizen I will have to report. So a lot of excuses So, good luck and thanks!

> I don't know if Gene is still watching this bug, but in case he doesn't,
> should i file a new bug report about this?
>

--

Please do not send me Microsoft Office/Apple iWork documents. Send OpenDocument instead! http://fsf.org/campaigns/opendocument

[gene (eugenios)]

I am sorry, forgot to also mention that suspend did not work for me either after the upgrade to Lucid:
$uname -a
Linux 2.6.32-22-generic #33-Ubuntu SMP Wed Apr 28 13:27:30 UTC 2010 i686 GNU/Linux
Not to mention that KMS has been very buggy for this video card: would frequently freeze the system (will report it later) and has a much inferior xvid performance. Too raw at the moment, the suspend issue is the minor one.

PS Will be using my mutt instead of firefox, since it has no emacs
--
            ἔρρωσο,

            Ευγενιος
--
              ___ __ __
|||/ _ _ ._ |_|_ (_ o._ _ ._ | _ (__|_ ._ o _|||
  |\(/_(/_|_) _|_|_ __)|| | ||_)|(/_o __)|_|_||_)|(_|
          | | / |
___ ___ __ __ _
 ||_ _ | |._ o |/ | (_ (_ |_)._o._ _o._ | _
 || |(/_ |_|| ||>< |\_|___)__) | | || |(_||_)|(/_
                                            |

Please do not send me Microsoft Office/Apple iWork documents. Send OpenDocument instead! http://fsf.org/campaigns/opendocument

[Karesz (lengyel-karesz)]

Well, you might be interested in this one also:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/576125

2010/5/7 gene <email address hidden>

> I am sorry, forgot to also mention that suspend did not work for me either
> after the upgrade to Lucid:
> $uname -a
> Linux 2.6.32-22-generic #33-Ubuntu SMP Wed Apr 28 13:27:30 UTC 2010 i686
> GNU/Linux
> Not to mention that KMS has been very buggy for this video card: would
> frequently freeze the system (will report it later) and has a much inferior
> xvid performance. Too raw at the moment, the suspend issue is the minor one.
>
> PS Will be using my mutt instead of firefox, since it has no emacs
> --
> ἔρρωσο,
>
> Ευγενιος
> --
> ___ __ __
> |||/ _ _ ._ |_|_ (_ o._ _ ._ | _ (__|_ ._ o _|||
> |\(/_(/_|_) _|_|_ __)|| | ||_)|(/_o __)|_|_||_)|(_|
> | | / |
> ___ ___ __ __ _
> ||_ _ | |._ o |/ | (_ (_ |_)._o._ _o._ | _
> || |(/_ |_|| ||>< |\_|___)__) | | || |(_||_)|(/_
> |
>
> Please do not send me Microsoft Office/Apple iWork documents. Send
> OpenDocument instead! http://fsf.org/campaigns/opendocument
>
> --
> [RC410] Xpress 200M hangs when resuming from suspend with DRI (needs KMS)
> https://bugs.launchpad.net/bugs/305301
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Karesz (lengyel-karesz)]

Okay, I've reported this bug again.
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/577340

2010/5/7 Lengyel Karesz <email address hidden>

> Well, you might be interested in this one also:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/576125
>
> 2010/5/7 gene <email address hidden>
>
> I am sorry, forgot to also mention that suspend did not work for me either
>> after the upgrade to Lucid:
>> $uname -a
>> Linux 2.6.32-22-generic #33-Ubuntu SMP Wed Apr 28 13:27:30 UTC 2010 i686
>> GNU/Linux
>> Not to mention that KMS has been very buggy for this video card: would
>> frequently freeze the system (will report it later) and has a much inferior
>> xvid performance. Too raw at the moment, the suspend issue is the minor one.
>>
>> PS Will be using my mutt instead of firefox, since it has no emacs
>> --
>> ἔρρωσο,
>>
>> Ευγενιος
>> --
>> ___ __ __
>> |||/ _ _ ._ |_|_ (_ o._ _ ._ | _ (__|_ ._ o _|||
>> |\(/_(/_|_) _|_|_ __)|| | ||_)|(/_o __)|_|_||_)|(_|
>> | | / |
>> ___ ___ __ __ _
>> ||_ _ | |._ o |/ | (_ (_ |_)._o._ _o._ | _
>> || |(/_ |_|| ||>< |\_|___)__) | | || |(_||_)|(/_
>> |
>>
>> Please do not send me Microsoft Office/Apple iWork documents. Send
>> OpenDocument instead! http://fsf.org/campaigns/opendocument
>>
>> --
>> [RC410] Xpress 200M hangs when resuming from suspend with DRI (needs KMS)
>> https://bugs.launchpad.net/bugs/305301
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>
>

[Petr Šigut (petr-sigut)]

I tried 10.10 alfa (kernel 2.6.35-rc3) and it takes very long to suspend and wake up is not functional at all.

[Karesz (lengyel-karesz)]

Same here, but it's a kernel still in development. Still, i don't beleive,
that it'll work in the final release. Hopefuly, the GPU scaling will.

2010/6/16 Petr Šigut <email address hidden>

> I tried 10.10 alfa (kernel 2.6.35-rc3) and it takes very long to suspend
> and wake up is not functional at all.
>
> --
> [RC410] Xpress 200M hangs when resuming from suspend with DRI (needs KMS)
> https://bugs.launchpad.net/bugs/305301
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[gene (eugenios)]

Hopefully, it will be fixed in a 100 years, when the amd finally decides to negotiate with the community. Long Live AMD/ATI and damn its products!

[Tormod Volden (tormodvolden)]

The maverick kernel recently fixed a long-standing Ubuntu-specific resume issue on my RV410 card. It was a general fix AFAIK, so maybe it is worth trying out 2.6.35-6-generic for you also.

[Petr Šigut (petr-sigut)]

Tormod Volden: Tried, fully updated Maverick, still the same.

[Karesz (lengyel-karesz)]

Hmm, looks promising: http://marc.info/?l=linux-kernel&m=127830148328681&w=2

"Dave Airlie (9):

drm/radeon: add quirk to make HP nx6125 laptop resume."

When it's up on kernel ppa, i'll try it!

Hopefully, it works for all X200m (rc410) notebooks.

2010/6/29 Petr Šigut <email address hidden>

> Tormod Volden: Tried, fully updated Maverick, still the same.
>
> --
> [RC410] Xpress 200M hangs when resuming from suspend with DRI (needs KMS)
> https://bugs.launchpad.net/bugs/305301
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Tormod Volden (tormodvolden)]

No, that's a specific quirk for that very model. See the "commitdiff" here: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=history;f=drivers/gpu/drm/radeon;hb=HEAD

[Bryce Harrington (bryce)]

Closing as expired since requested apport-collect files were not provided.

(Besides, I think this is more likely to be a kernel issue since it has to do with suspend/resume freezing, which almost always is something in the kernel, drm perhaps.)

[madbiologist (me-again)]

Re the patch mentioned in comment 161 - a version for the HP DV5000 series has been included upstream in kernel 2.6.35-rc6. From the changelog:

commit 52fa2bbc8ec46255039e2048d616bbd0852ee292
Author: Alex Deucher
Date: Wed Jul 21 23:54:35 2010 -0400

    drm/radeon/kms: add quirk to make HP DV5000 laptop resume

    Fixes:
    https://bugs.freedesktop.org/show_bug.cgi?id=29062

    Reported-by: Andres Cimmarusti
    Signed-off-by: Alex Deucher
    Signed-off-by: Dave Airlie

A PPA of this kernel is available at http://kernel.ubuntu.com/~kernel-ppa/mainline/

[Karesz (lengyel-karesz)]

I wonder if this problem still exists in natty. Anyone tried it?

2011/1/24 Bug Watch Updater <email address hidden>

> ** Changed in: linux
> Status: Invalid => Expired
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/305301
>
> Title:
> [RC410] Xpress 200M hangs when resuming from suspend with DRI (needs
> KMS)
>

[Karesz (lengyel-karesz)]

Okay, some progress (or regress maybe?)! So, I've tried a new hungarian
distribution called Little Susie ft. KDE3. It's pretty neat, and is made for
older machines. Just for my interest i've tried, if suspend to RAM, then
resume from RAM works on it. IT does! It is based on OpenSuSE 11.1, running
kernel 2.6.27-48 i686.
What if someone smarter than me would check the difference between that
kernel's resume functions, and maverick's/natty's kernel's resume functions,
because (what a surprise :D) it still doesn't work for me in Natty Narwhal
alpha 3! Or if we couldn't integrate the older kernels resume function in
the new kernel because of the new KMS/DRI2, then finding a workaround, like
when suspending to RAM, fallback to older driver, and after resume init the
new driver.

(I don't know if this discussion can be held up here, or if i should file a
new bug for Natty?)

Sincerely: Karesz

2011/2/6 Bug Watch Updater <email address hidden>

> ** Changed in: xorg-server
> Importance: Unknown => High
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/305301
>
> Title:
> [RC410] Xpress 200M hangs when resuming from suspend with DRI (needs
> KMS)
>

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.