Hi,
Today, out of curiosity, I pulled 2.6.23-rc7 (leave on the edge in a quiet weekend).

Anyway, it seems that radeonfb and my:

"01:05.0 VGA compatible controller: ATI Technologies Inc ATI Radeon XPRESS 200M 5955 (PCIE)"

don't get along anymore, by:

a) X somehow fails to initialize the card and everything moves really slow (I can

   see how surfaces are drawn pixel-by-pixel); furthermore, garbage stuff appears

   on the screen;

b) after powering up from a s2ram, the system freezes;
b) is not that bad, s2ram never worked on my machine (kjournald and some other kernel

processes, enter disk-sleep and in a matter of seconds, everything just... freezes.

I can type a few commands at the normal console but that is all);
Following the advices in 'Documentation/power/s2ram.txt' helped. Using the regular

VGA console got X on the right track (no more slowness);
Now that I got my hands "dirty", I'm in the mood to make my s2ram work (I've

been using Linux (exclusively) for three years now, it's about time I do a small

contribution). What kernel option must I enable to determine why some processes

enter (and stay in) disk-sleep? I'm on a laptop and I don't think it will withstand

too many reboots :)
I've also attached the output of lspci and dmesg. Maybe someone spots something.
Thanks,
--

Mihai Don

Have you tried to boot your kernel with
   video=radeonfb:noaccel
I usual add this kernel parameter when running radeonfb and X.
Otherwise I've observed the same symptoms (e.g. with my radeon card

at home: Radeon X300SE, 1002:5b70).
Regards,
Andreas
-

It works. Golden option. Should be documented somewhere.
Thanks,
--

Mihai Donțu

-

Looks like radeonfb needs a radeonfb.txt file in

Documentation/fb/.  There is a txt file for aty128fb which does

include this option and others...
---

~Randy

Phaedrus says that Quality is about caring.

-

On Saturday 22 September 2007, Mihai Don

Heh, yup.
There have been some radeonfb patches around -rc6 or so. Can you try

backing them out and letting us know if that helps a) ?
In that case, Linus, we probably want to revert them...
Though looking at your PCI ID (5955), I don't think the patches should

have changed anything.
Ben.
-

After four hours of bisecting, I got this, which dates back to 2.6.21, but

I've been on 2.6.21.3 for too long and thus missed the commit (I just decided

to be a good citizen and test things before they get out).
dd1447134454b169d5ae353aceb93f2368db8547 is first bad commit

commit dd1447134454b169d5ae353aceb93f2368db8547

Author: johan henriksson <jhn98032@gmail.com>

Date:   Tue May 8 00:37:59 2007 -0700
    radeonfb: Add support for Radeon xpress 200m
    Added support for radeon xpress 200m(rs480).  Note that the card doesn't

    like dynclk turned on.
    Signed-off-by: Johan Henriksson <jhn98032@gmail.com>

    Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>

    Cc: "Antonino A. Daplas" <adaplas@pol.net>

    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
I turned dynclk off, no result (although dynclk is preferred).
What is interesting, is that the driver ignores "vga=normal" and "jumps" to

a quite high res (I think is 1024x768 or something; the fonts look really nice

though :)).
--

Mihai Donțu

-

Something strange is going on here: after I cleaned up the bisect kernels,

  I booted 2.6.23-rc7 using something like:

  "vga=normal nohz=on root=/dev/sda7 libata.noacpi=0 pci=assing-busses"

  and explicitly selecting "Enable Video Mode Handling Helpers" (which normally

  gets automatically selected once I choose "ATI Radeon display support" but I

  - suffering from intense paranoia - selected it by hand prior to selecting ATI

  Radeon ...).
  I works! X is no longer acting weird. I can't use "vga=791" anymore (the screen

  goes blank until X loads => timings definitely changed) but it *works* and I don't

  know why _and_ I can't seem to be able to make it go back to being bad :)
  I did a diff between the .config used in bisect and the current .config. I don't

  see anything suspicious.
  I'll to do a full cleanup and start all over. I'm going to nail this thing down if

  it's the last thing I do! (so help me God) :)
--

Mihai Donțu

-

Found it!
  The problem was "Framebuffer Console support". It was enabled by default in older

  configs (like 2.6.22.7) but I think someone noticed this was bad and put it to

  default N in newer (2.6.23-rc7); and since I reused the .config from 2.6.21.3 ...
  So there, if one wants "ATI Radeon display support" on Radeon XPRESS 200M with

  X using radeon_drv.so, *should* put "Framebuffer Console support" to N (if it's

  not already).
  Now all I have to do is figure out what's the equivalent of "vga=791" on the new

  kernel (default text console looks really bad on my laptop).
  Sorry for all the noise (and spam),
--

Mihai Donțu

-

No, this actually is valuable information, thanks for it. :-)
[I have missed your first post, sorry for that.]
Greetings,

Rafael

-

On Sunday 23 September 2007, Rafael J. Wysocki wrote:

quoted text
> On Sunday, 23 September 2007 20:31, Mihai Don

It might have simply not initialized :-)
Ben.
-

* Sun, 23 Sep 2007 22:22:28 +0300

* Organization: Home
In fact, it's known statement, that there must only one hardware driver

for graphic adapter. Be it framebuffer with X fb driver on it or legacy

VGA text and X with its driver.so and 3D stuff.
(i choose legacy text without X for the most of my time, though :)

_____

-

Not quite ... on PowerMacs, we've been routinely using radeonfb and X

together. However, for that to work, in general, one has to be careful

to switch back to console mode before suspending and back to X after

resume, which seems to have been broken by many distro lately, probably

because somebody made it optional in the kernel...
Ben.
-