public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Frédéric L. W. Meunier" <2@pervalidus.net>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: radeonfb blanks my monitor
Date: Thu, 03 Mar 2005 15:50:51 +1100	[thread overview]
Message-ID: <1109825452.5611.163.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.62.0503030134200.311@darkstar.example.net>

On Thu, 2005-03-03 at 01:39 -0300, Frédéric L. W. Meunier wrote:
> On Thu, 3 Mar 2005, Benjamin Herrenschmidt wrote:
> 
> > On Wed, 2005-03-02 at 23:51 -0300, Frédéric L. W. Meunier wrote:
> >> I just replaced my Matrox G400 with a Jetway Radeon 9600LE
> >> (256Mb). If I run 'modprobe radeonfb', the monitor blanks out
> >> and the power on light keeps flashing.
> >>
> >> What may be wrong ? Using 2.6.11.
> >
> > Do you have a way to capture the dmesg log produced ?
> 
> These are the lines before I have to use SysRq.
> 
> Mar  2 15:16:45 darkstar kernel: radeonfb: Found Intel x86 BIOS ROM Image
> Mar  2 15:16:45 darkstar kernel: radeonfb: Retreived PLL infos from BIOS
> Mar  2 15:16:45 darkstar kernel: i2c-algo-bit.o: dvi passed test.
> Mar  2 15:16:45 darkstar kernel: i2c-algo-bit.o: vga passed test.
> Mar  2 15:16:46 darkstar kernel: radeonfb: Monitor 1 type CRT found
> Mar  2 15:16:46 darkstar kernel: radeonfb: EDID probed
> Mar  2 15:16:46 darkstar kernel: radeonfb: Monitor 2 type no found
> 
> BTW, I don't know if it could be related, but my motherboard 
> only supports AGP 4x

There should be more than these... Does it continue booting afte the
screen goes blank or not at all ? Can you send the full dmesg log too ?
Also, enable radeonfb verbose debug in the config.

> > Also, does it work if radeonfb is built-in ?
> 
> I'll try later. Time to sleep.

Ok, thanks.


  reply	other threads:[~2005-03-03  4:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-03  2:51 radeonfb blanks my monitor Frédéric L. W. Meunier
2005-03-03  4:10 ` Benjamin Herrenschmidt
2005-03-03  4:39   ` Frédéric L. W. Meunier
2005-03-03  4:50     ` Benjamin Herrenschmidt [this message]
2005-03-03 15:38       ` Frédéric L. W. Meunier
2005-03-03 22:48         ` Benjamin Herrenschmidt
2005-03-03 23:48           ` Frédéric L. W. Meunier
2005-03-04 17:14             ` Frédéric L. W. Meunier
2005-03-04 10:39         ` Jean Delvare
2005-03-04 17:16           ` Frédéric L. W. Meunier
2005-03-04 20:46             ` Jean Delvare

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=1109825452.5611.163.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=2@pervalidus.net \
    --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