From: Joerg Dorchain <joerg@dorchain.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: 2.6.13 ati (ibook) frambuffer problem
Date: Tue, 18 Oct 2005 10:49:35 +0200 [thread overview]
Message-ID: <20051018084935.GE28756@Redstar.dorchain.net> (raw)
In-Reply-To: <1129585466.7620.90.camel@gaston>
[-- Attachment #1: Type: text/plain, Size: 910 bytes --]
On Tue, Oct 18, 2005 at 07:44:26AM +1000, Benjamin Herrenschmidt wrote:
> > The 2.6.12 version worked. Would it make sense to post the complete
> > .config?
I got 2.6.13.4 booting. The last change I did was deselecting
CONFIG_FB_TILEBLITTING. Unfortunately, I have no idea how this actually
affects the ATI frambebuffer.
To make it even more strange, after reenabling CONFIG_FB_TILEBLITTING,
it still boots up cleanly. Obviously, I missed out on something.
Besides, I have the impression that the disk reacts slower. As hdparm
does not tell a difference, it might be due the coffein, tough.
>
> Nope. What may help is a bit more debugging. For example, does the
> kernel actually boots if you add "video=ofonly" to the kernel command
> line.
No effect.
Well, the good point is, it works again. The bad point, I do not know
why. Anyway, thanks for the support.
Bye,
Joerg
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-10-18 8:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-14 12:38 2.6.13 ati (ibook) frambuffer problem Joerg Dorchain
2005-10-14 21:58 ` Benjamin Herrenschmidt
2005-10-16 8:17 ` Joerg Dorchain
2005-10-16 8:42 ` Benjamin Herrenschmidt
2005-10-17 18:34 ` Joerg Dorchain
2005-10-17 21:44 ` Benjamin Herrenschmidt
2005-10-18 8:49 ` Joerg Dorchain [this message]
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=20051018084935.GE28756@Redstar.dorchain.net \
--to=joerg@dorchain.net \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
/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).