public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Charles Johnston <cjohnston@networld.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.3-rc4 Massive strange corruption with new radeonfb
Date: Tue, 17 Feb 2004 15:53:11 -0700	[thread overview]
Message-ID: <40329B57.9060901@networld.com> (raw)
In-Reply-To: <1077055997.1076.23.camel@gaston>

Benjamin Herrenschmidt wrote:
> On Wed, 2004-02-18 at 07:08, Charles Johnston wrote:
> 
>>Upon bootup, radeonfb is obviously not initializing the hardware 
>>correctly.  Massive amounts of random-looking garbage, plus a weird 
>>effect I've never seen before, like someone pouring milk _up_ the
>>screen. (Yeah, it's the best I could come up with)
>>
>>It's a Dell Inspiron 8600 with Mobile Radeon 9600 and 1920x1200 LCD.
> 
> 
> Looks like the driver cannot find any info about your flat panel
> in the BIOS ROM image. I suppose we can thank DELL for hacking the
> BIOS in ways that aren't compatible with all others laptops...
> 
> Can you try commenting out the call to radeon_map_ROM() and let it
> look for the RAM based BIOS instead ? Let me know...
>  

Ok, it worked fine with that line commented out.  I can switch vt's, be 
in X, etc. no problems.

The only issue I see is when I do a 'clear' on the vt, it doesn't clear 
the text, but blanks every nth row of pixels.  Switching vt's and back 
clears the screen.

There are also a few rows of garbage pixels at the bottom that linger 
across vt switches.


Charles Johnston
cjohnston@networld.com

  reply	other threads:[~2004-02-17 22:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-17 20:08 Linux 2.6.3-rc4 Massive strange corruption with new radeonfb Charles Johnston
2004-02-17 22:13 ` Benjamin Herrenschmidt
2004-02-17 22:53   ` Charles Johnston [this message]
2004-02-17 23:31     ` Benjamin Herrenschmidt
2004-02-18  0:23       ` Charles Johnston
2004-02-18  0:36         ` Benjamin Herrenschmidt

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=40329B57.9060901@networld.com \
    --to=cjohnston@networld.com \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.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