From: "Frédéric L. W. Meunier" <2@pervalidus.net>
To: unlisted-recipients:; (no To-header on input)
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: radeonfb blanks my monitor
Date: Fri, 4 Mar 2005 14:14:37 -0300 (BRT) [thread overview]
Message-ID: <Pine.LNX.4.62.0503041407230.163@darkstar.example.net> (raw)
In-Reply-To: <Pine.LNX.4.62.0503032044350.416@darkstar.example.net>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 3238 bytes --]
On Thu, 3 Mar 2005, Frédéric L. W. Meunier wrote:
> On Fri, 4 Mar 2005, Benjamin Herrenschmidt wrote:
>
>> Well, I would need the full log, and with radeonfb verbose debug enabled
>> in the config.
>
> I'll later try as module with debug.
Here's:
/var/log/messages:
Mar 4 14:00:29 pervalidus kernel: radeonfb: Found Intel x86 BIOS ROM Image
Mar 4 14:00:29 pervalidus kernel: radeonfb: Retreived PLL infos from BIOS
Mar 4 14:00:30 pervalidus kernel: radeonfb: Monitor 1 type CRT found
Mar 4 14:00:30 pervalidus kernel: radeonfb: EDID probed
Mar 4 14:00:30 pervalidus kernel: radeonfb: Monitor 2 type no found
/var/log/syslog:
Mar 4 14:00:28 pervalidus kernel: radeonfb_pci_register BEGIN
Mar 4 14:00:28 pervalidus kernel: radeonfb (0000:01:00.0): Found 262144k of DDR 128 bits wide videoram
Mar 4 14:00:29 pervalidus kernel: radeonfb (0000:01:00.0): mapped 16384k videoram
Mar 4 14:00:29 pervalidus kernel: radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=325.00 Mhz, System=200.00 MHz
Mar 4 14:00:29 pervalidus kernel: radeonfb: PLL min 20000 max 40000
Mar 4 14:00:29 pervalidus kernel: 1 chips in connector info
Mar 4 14:00:29 pervalidus kernel: - chip 1 has 2 connectors
Mar 4 14:00:29 pervalidus kernel: * connector 0 of type 2 (CRT) : 2300
Mar 4 14:00:29 pervalidus kernel: * connector 1 of type 3 (DVI-I) : 3221
Mar 4 14:00:29 pervalidus kernel: Starting monitor auto detection...
Mar 4 14:00:29 pervalidus kernel: radeonfb: I2C (port 1) ... not found
Mar 4 14:00:29 pervalidus kernel: radeonfb: I2C (port 2) ... not found
Mar 4 14:00:29 pervalidus kernel: radeonfb: I2C (port 3) ... found CRT display
Mar 4 14:00:30 pervalidus kernel: radeonfb: I2C (port 4) ... not found
Mar 4 14:00:30 pervalidus kernel: radeonfb: I2C (port 2) ... not found
Mar 4 14:00:30 pervalidus kernel: radeonfb: I2C (port 4) ... not found
Mar 4 14:00:30 pervalidus kernel: radeonfb: I2C (port 3) ... found CRT display
Mar 4 14:00:30 pervalidus kernel: hStart = 694, hEnd = 757, hTotal = 795
Mar 4 14:00:30 pervalidus kernel: vStart = 402, vEnd = 408, vTotal = 418
Mar 4 14:00:30 pervalidus kernel: h_total_disp = 0x590062^I hsync_strt_wid =0x8702c0
Mar 4 14:00:30 pervalidus kernel: v_total_disp = 0x18f01a1^I vsync_strt_wid = 0x860191
Mar 4 14:00:30 pervalidus kernel: pixclock = 85925
Mar 4 14:00:30 pervalidus kernel: freq = 1163
Mar 4 14:00:30 pervalidus kernel: freq = 1666, PLL min = 20000, PLL max = 40000
Mar 4 14:00:30 pervalidus kernel: ref_div = 12, ref_clk = 2700, output_freq = 26656
Mar 4 14:00:30 pervalidus kernel: ref_div = 12, ref_clk = 2700, output_freq = 26656
Mar 4 14:00:30 pervalidus kernel: post div = 0x5
Mar 4 14:00:30 pervalidus kernel: fb_div = 0x76
Mar 4 14:00:30 pervalidus kernel: ppll_div_3 = 0x50076
Mar 4 14:00:30 pervalidus kernel: Console: switching to colour frame buffer device 90x25
Mar 4 14:00:30 pervalidus kernel: radeonfb (0000:01:00.0): ATI Radeon AP
Mar 4 14:00:30 pervalidus kernel: radeonfb_pci_register END
BTW, I noticed that it locking the system. I was able to issue
a shutdown. The commands still work, but beep is disabled.
--
How to contact me - http://www.pervalidus.net/contact.html
next prev parent reply other threads:[~2005-03-04 17:21 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
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 [this message]
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.0503041407230.163@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
all inboxes | Powered by JetHome®