From: "Hans-Jürgen Koch" <hjk@linutronix.de>
To: xorg@lists.freedesktop.org
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Radeon X300, radeonfb, dual head - conclusion
Date: Fri, 20 Apr 2007 23:54:41 +0200 [thread overview]
Message-ID: <200704202354.42019.hjk@linutronix.de> (raw)
In-Reply-To: <200704181409.51475.hjk@linutronix.de>
I'd like to bring this thread to a preliminary conclusion. Today I experimented a little more,
with the following results:
Short summary:
We're talking about this card:
01:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)]
This is a MSI RX300HM, with an X300SE and 128MB RAM. The card has one DVI-I, one VGA, and
one S-Video connector. I have two NEC MultiSync LCD2070WNX 20" monitors (1680x1050 each).
The monitors have both VGA and DVI-D inputs. Computer has a Core2Duo@1.86GHz, Intel ICH8
chipset, 1GB RAM.
X server is xserver-xorg from Debian unstable. Kernel is vanilla 2.6.21-rc7.
X server is configured for mergedfb to achieve a 3360x1050 desktop across the two monitors.
All tests were performed with KDE 3.5.5 from Debian unstable.
Results:
1.) The monitor connected to the DVI port MUST use a DVI cable. Connecting it with a
DVI-VGA adapter does not work. Using an adapter causes the same picture being displayed
on both monitors. This might only happen with this special card.
2.) Using DRM does NOT work. Compiling radeon drm as a kernel module and configuring
dri in xorg.conf leads to fine 3D acceleration (glxgears -printfps says 1400fps), but
only on the first monitor. The second monitor always shows a black image. It is probably
a correct 1680x1050 video signal (monitor doesn't complain), but only black.
If I compile the kernel without drm support, and delete the dri lines in xorg.conf,
I have a working dual head setup with Pseudo-Xinerama.
3.) Using radeonfb does NOT work. I tried to compile it into the kernel to have a
framebuffer console at boot time, but that's not possible. I noticed two effects:
3.1.) if drm is also enabled, the X server hangs at 100% CPU with black screens on both
monitors. Framebuffer console before X starts is OK.
3.2.) if drm is not enabled, the X server starts, but with a garbled screen that is
hardly useable. Framebuffer console before X starts is fine.
4.) Using vesafb instead of radeonfb works. I have a framebuffer console, and X works
as expected. No DRI, of course (glxgears -printfps says 900fps).
I'd really like to see these issues fixed. I'm willing and able to help on the kernel
side of the story, although I never looked into fb or drm code yet. I won't compile
X servers, though.
Any comments?
Any ideas how we could proceed?
Thanks,
Hans
prev parent reply other threads:[~2007-04-20 21:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-18 12:09 Radeon X300, radeonfb, dual head Hans-Jürgen Koch
2007-04-18 12:58 ` Jerome Glisse
2007-04-18 13:26 ` Hans-Jürgen Koch
2007-04-18 13:45 ` Michel Dänzer
2007-04-18 15:02 ` [Linux-fbdev-devel] " Hans-Jürgen Koch
2007-04-18 21:20 ` Hans-Jürgen Koch
2007-04-18 21:45 ` Alex Deucher
2007-04-19 7:00 ` Hans-Jürgen Koch
2007-04-19 6:04 ` Michel Dänzer
2007-04-19 8:35 ` Jimmy Jazz
[not found] ` <46272535.5040303@cryosphere.shacknet.nu>
2007-04-19 8:44 ` Hans-Jürgen Koch
2007-04-20 21:54 ` Hans-Jürgen Koch [this message]
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=200704202354.42019.hjk@linutronix.de \
--to=hjk@linutronix.de \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=xorg@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).