From: Pavel Machek <pavel@ucw.cz>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Christian Hoffmann <Christian.Hoffmann@wallstreetsystems.com>,
Andrew Morton <akpm@osdl.org>,
Solomon Peachy <pizza@shaftnet.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
linux-fbdev-devel@lists.sourceforge.net,
LKML <linux-kernel@vger.kernel.org>,
Christian@ogre.sisk.pl, Hoffmann@albercik.sisk.pl
Subject: Re: Fwd: [Suspend-devel] resume not working on acer ferrari 4005 with radeonfb enabled
Date: Sun, 12 Nov 2006 13:13:35 +0100 [thread overview]
Message-ID: <20061112121334.GC9989@elf.ucw.cz> (raw)
In-Reply-To: <1163285379.4982.233.camel@localhost.localdomain>
Hi!
> > Then the radeonfb doesn't kick in at all (guess some pci ids are added
> > in that patch).
> >
> > BTW: resume/suspend works ok if I have the vesa fb enabled.
>
> In that case (vesafb), when does the screen come back precisely ? Do you
> get console mode back and then X ? Or it only comes back when going back
> to X ? Do you have some userland-type vbetool thingy that bring it
> back ?
He's using s3_bios+s3_mode, so kernel does some BIOS calls to reinit
the video. It should come out in text mode, too.
Christian, can you unload radeonfb before suspend/reload it after
resume?
Next possibility is setting up serial console and adding some printks
to radeon...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2006-11-12 12:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-11 11:36 Fwd: [Suspend-devel] resume not working on acer ferrari 4005 with radeonfb enabled Christian Hoffmann
2006-11-11 22:49 ` Benjamin Herrenschmidt
2006-11-12 12:13 ` Pavel Machek [this message]
2006-11-12 12:28 ` Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2006-11-13 22:08 Christian Hoffmann
2006-11-13 23:08 ` Rafael J. Wysocki
2006-11-14 18:51 ` Christian Hoffmann
2006-11-14 21:47 ` Christian Hoffmann
2006-11-14 22:07 ` Benjamin Herrenschmidt
2006-11-15 0:54 ` Christian Hoffmann
2006-11-15 1:48 ` Benjamin Herrenschmidt
2006-11-15 10:09 ` Rafael J. Wysocki
2006-11-16 22:17 ` Christian Hoffmann
2006-11-16 22:44 ` Rafael J. Wysocki
2006-11-17 5:27 ` [Linux-fbdev-devel] " Stuffed Crust
2006-11-17 6:17 ` Benjamin Herrenschmidt
2006-11-17 14:36 ` [Linux-fbdev-devel] " Stuffed Crust
2006-11-17 21:57 ` Benjamin Herrenschmidt
2006-11-17 6:07 ` [Linux-fbdev-devel] " Stuffed Crust
2006-11-17 15:41 ` Stuffed Crust
2006-11-17 20:33 ` Christian Hoffmann
2006-11-17 21:59 ` Benjamin Herrenschmidt
2006-11-14 22:56 ` Pavel Machek
2006-11-14 22:57 ` [Linux-fbdev-devel] " Rafael J. Wysocki
2006-11-14 23:12 ` Pavel Machek
2006-11-13 10:51 Christian Hoffmann
2006-11-13 14:06 ` Rafael J. Wysocki
2006-11-13 17:07 ` Pavel Machek
2006-11-11 23:02 Christian Hoffmann
2006-11-11 14:27 Christian Hoffmann
2006-11-11 10:17 Christian Hoffmann
2006-11-10 23:31 Rafael J. Wysocki
2006-11-11 1:49 ` Benjamin Herrenschmidt
2006-11-11 2:02 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061112121334.GC9989@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=Christian.Hoffmann@wallstreetsystems.com \
--cc=Christian@ogre.sisk.pl \
--cc=Hoffmann@albercik.sisk.pl \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pizza@shaftnet.org \
--cc=rjw@sisk.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).