public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Michael Buesch <mb@bu3sch.de>
Cc: linux-fbdev-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: radeonfb: corrupted screen on bootup
Date: Thu, 29 Jun 2006 11:08:16 -0400	[thread overview]
Message-ID: <44A3ECE0.10104@tmr.com> (raw)
In-Reply-To: <200606282118.27750.mb@bu3sch.de>

Michael Buesch wrote:
> Hi,
> 
> I have a weird error with my PowerBook G4, which
> has a radeon card. I am using radeonfb.

I had a similar problem, and solved it by using the "wrong" (aty128fb) 
module which makes me happy. Booted working 5-6 times now, which is a 
few weeks since I run for long periods.

> After bootup, the screen sometimes looks like it is melting.
> I made a video to show you what is going on:
> http://bu3sch.de/misc/after_boot.avi  (6.1 MB)
> 
> It does only happen sometimes. I could not find
> a way to reproduce it.
> If I start X after boot with a melting screen, X is also
> melting:
> http://bu3sch.de/misc/after_x_switch.avi  (6.6 MB)
> 
> But here comes the interresting part:
> If I switch back into the console, the screen becomes
> normal again and I can continue to work as usual.
> 
> I am suspecting some initialization routine bug.
> It never happened when booting into OSX.
> 
> In X I use the "radeon" driver.

-- 
Bill Davidsen <davidsen@tmr.com>
   Obscure bug of 2004: BASH BUFFER OVERFLOW - if bash is being run by a
normal user and is setuid root, with the "vi" line edit mode selected,
and the character set is "big5," an off-by-one errors occurs during
wildcard (glob) expansion.


  parent reply	other threads:[~2006-06-29 15:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-28 19:18 radeonfb: corrupted screen on bootup Michael Buesch
2006-06-28 19:26 ` Ralf Hildebrandt
2006-06-29  0:07 ` Benjamin Herrenschmidt
2006-06-29 15:08 ` Bill Davidsen [this message]
2006-06-29 17:19 ` Pavel Machek

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=44A3ECE0.10104@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mb@bu3sch.de \
    /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