Re: [Bug #13667] drm: display arifacts when X.Org is stopped

Frans Pop
2009-07-09T01:28:52Z

On Thursday 09 July 2009, Dave Airlie wrote:
> > [1] I'd even go so far as to feel it should be a standard test case
> > for video driver developers, given that this is the third time it's
> > shown regressions :-) For the third case the bug was in the X.Org
> > i830 driver: http://bugs.freedesktop.org/show_bug.cgi?id=14481.
>
> It might surprise you to learn this, but vesafb has never been
> considered supportable by the X.org community, and you'll notice not
> very many distros ship with it enabled, it breaks suspend/resume on
> many machines for example.

I beg to disagree.
- Debian does have it enabled by default.
- I have always used it on all my machines without any problems.
- Both my laptops and my desktop suspend and resume perfectly with vesafb
and X.Org.
- Jesse Barnes seems to disagree with you. To quote from the BR cited
above (comment #11): "and you're right, making things work with vesafb
isn't unreasonable".

I do know intelfb is considered to be terminally broken, but have always
understood the use of vesafb to be accepted.

> As I said having two drivers thinking they own the GPU is a recipe for
> total disaster and thats why we've designed the new KMS code so you can
> get cool bootup logos and avoid the insanity dance.

Yes, and I really welcome the great progress being made there. But for me
it's not yet an option as I run Debian stable on these boxes.

> However we shall endeavour to fix this issues as it may be systemic of
> something else going wrong in the new PAT/AGP code.

Great. Thanks in advance, I do appreciate it.

BTW, today I noticed another regression, but I have not yet looked into it
deeply. When I suspend I normally see at least some console messages from
the suspend procedure on the framebuffer console, but with .31-rc2 I only
see a cursor. It does not really affect the suspend/resume.
Could possibly be related. Will investigate further.

Cheers,
FJP