From: "Frédéric L. W. Meunier" <2@pervalidus.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: radeonfb blanks my monitor
Date: Thu, 3 Mar 2005 12:38:51 -0300 (BRT) [thread overview]
Message-ID: <Pine.LNX.4.62.0503031149280.311@darkstar.example.net> (raw)
In-Reply-To: <1109825452.5611.163.camel@gaston>
On Thu, 3 Mar 2005, Benjamin Herrenschmidt wrote:
> 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.
Yes, there were more in /var/log/syslog:
Mar 2 15:16:45 darkstar kernel: radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=325.00 Mhz, System=200.00 MHz
Mar 2 15:16:45 darkstar kernel: radeonfb: PLL min 20000 max 40000
Mar 2 15:16:45 darkstar kernel: i2c-algo-bit.o: monid seems to be busy.
Mar 2 15:16:45 darkstar kernel: radeonfb 0000:01:00.0: Failed to register I2C bus monid.
Mar 2 15:16:45 darkstar kernel: i2c-algo-bit.o: crt2 seems to be busy.
Mar 2 15:16:46 darkstar kernel: radeonfb 0000:01:00.0: Failed to register I2C bus crt2.
Mar 2 15:16:46 darkstar kernel: Console: switching to colour frame buffer device 90x25
Mar 2 15:16:46 darkstar kernel: radeonfb (0000:01:00.0): ATI Radeon AP
Do the "seems to be busy." and/or "Failed to register I2C bus"
indicate a problem ?
There's nothing about radeonfb in dmesg because I manually
loaded the modules.
I now compiled built-in with debug enabled and got the same
problem. Nothing got logged. Everything seems to stop when it
blanks, but SysRq works.
--
How to contact me - http://www.pervalidus.net/contact.html
next prev parent reply other threads:[~2005-03-03 15:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 2:51 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
2005-03-03 15:38 ` Frédéric L. W. Meunier [this message]
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=Pine.LNX.4.62.0503031149280.311@darkstar.example.net \
--to=2@pervalidus.net \
--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
Powered by JetHome