From: Roland Dreier <roland@topspin.com>
To: <linux-kernel@vger.kernel.org>
Subject: radeonfb problems with 2.6.2-rc2
Date: 26 Jan 2004 20:12:51 -0800 [thread overview]
Message-ID: <52y8rughbw.fsf@topspin.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0311111019210.30657-100000@home.osdl.org>
I just decided to give radeonfb a try with a 2.6 kernel (2.6.2-rc2 to
be specific). I have a Radeon 9000 Pro with two 1280x1024 LCDs
connected, one to the DVI connector and one to the CRT connector.
When it boots, I get a glimpse of the penguin logo for a moment, and
then the screen goes blank and stays blank. If I start the Radeon
XFree86 server then both screens come back to life and work fine.
I get the following in my boot log:
Linux version 2.6.2-rc2 (root@gold) (gcc version 2.95.4 20011002 (Debian prerelease)) #1 Mon Jan 26 11:41:46 PST 2004
[...]
radeonfb_pci_register BEGIN
radeonfb: ref_clk=2700, ref_div=12, xclk=27500 from BIOS
radeonfb: probed DDR SGRAM 65536k videoram
radeon_get_moninfo: bios 4 scratch = a00000a
radeonfb: panel ID string: ªhé£\x05
radeonfb: detected DFP panel size from BIOS: 1x0
radeonfb: detected DFP panel size from registers: 1280x1024
radeonfb: ATI Radeon 9000 If DDR SGRAM 64 MB
radeonfb: DVI port DFP monitor connected
radeonfb: CRT port CRT monitor connected
radeonfb_pci_register END
[...]
hStart = 680, hEnd = 960, hTotal = 1056
vStart = 482, vEnd = 501, vTotal = 522
h_total_disp = 0x4f0083 hsync_strt_wid = 0xa302a2
v_total_disp = 0x1df0209 vsync_strt_wid = 0x9301e1
post div = 0x8
fb_div = 0x59
ppll_div_3 = 0x30059
ron = 828, roff = 19684
vclk_freq = 2503, per = 703
Console: switching to colour frame buffer device 80x30
I've seen some radeonfb patches floating around, but my impression was
that 2.6.2-rc2 should work. If anyone has something for me to try,
I'd be happy to give it a spin. Otherwise I guess I'll try to figure
out what that debugging output is telling me.
Thanks,
Roland
next prev parent reply other threads:[~2004-01-27 4:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-11 17:21 2.6 /proc/interrupts fails on systems with many CPUs Erik Jacobson
2003-11-11 17:29 ` Randy.Dunlap
2003-11-11 17:51 ` Robert Love
2003-11-11 18:02 ` Martin J. Bligh
2003-11-11 18:24 ` Linus Torvalds
2003-11-11 18:57 ` Martin J. Bligh
2003-11-11 18:36 ` Linus Torvalds
2003-11-11 20:14 ` Anton Blanchard
2003-11-11 22:41 ` Martin J. Bligh
2003-11-11 22:32 ` Zwane Mwaikambo
2004-01-27 4:12 ` Roland Dreier [this message]
2003-11-11 18:17 ` Linus Torvalds
2003-11-11 18:22 ` viro
2003-11-11 20:15 ` Jonathan Corbet
2003-11-11 18:32 ` Randy.Dunlap
2003-11-11 19:19 ` Anton Blanchard
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=52y8rughbw.fsf@topspin.com \
--to=roland@topspin.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.