From: "Hans-Jürgen Koch" <hjk@linutronix.de>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: "Michel Dänzer" <michel@tungstengraphics.com>,
xorg@lists.freedesktop.org
Subject: Re: [Linux-fbdev-devel] Radeon X300, radeonfb, dual head
Date: Wed, 18 Apr 2007 17:02:20 +0200 [thread overview]
Message-ID: <200704181702.21359.hjk@linutronix.de> (raw)
In-Reply-To: <1176903932.10554.248.camel@thor.sulgenrain.local>
Am Mittwoch, 18. April 2007 15:45 schrieb Michel Dänzer:
> On Wed, 2007-04-18 at 14:09 +0200, Hans-Jürgen Koch wrote:
> >
> > 1.) I compiled radeonfb statically into my kernel and booted with
> > video=radeonfb:1280x1024-32@60. This works fine, the framebuffer
> > console works as expected. But the X server doesn't come up
> > properly. Xorg.0.log ends like this:
> >
> > [...]
> > (**) RADEON(0): RADEONSaveScreen(2)
> > (**) RADEON(0): FIFO timed out: 2 entries, stat=0x80026102
> > (EE) RADEON(0): FIFO timed out, resetting engine...
>
> Please file a bug for this at http://bugs.freedesktop.org if it hasn't
> been reported yet.
I'll do that, but want to experiment a little bit more first.
> Does this also happen if you don't enable the DRI?
Thanks for reminding me - I didn't enable DRM in my kernel yet, so DRI
was always off. I now enabled it, and (to answer your question), this is
no issue. Even AIGLX starts up properly, but everything else is as before.
I still have the same picture on both monitors.
>
>
> > 2.) I compiled vesafb statically, radeonfb only as module. If I boot
> > with vga=0x318, the framebuffer console works as expected. The
> > X server starts up, Xorg.0.log looks good (except that DRI is disabled).
> >
> > But when kdm comes up, I see the same picture on both monitors. What I
> > see looks like the right half of the 3360x1050 desktop (mouse can be
> > moved across the left border of the screen, stops at the right border).
> > Both screens are driven properly with 1680x1050. I tried several
> > modifications of my xorg.conf, but never managed to get different
> > images on the two monitors, they always show the same.
>
> [...]
>
> > Option "MonitorLayout" "TMDS,TMDS"
>
> The driver doesn't support this combination yet, and it doesn't match
> your setup anyway.
Well, the manpage says:
CRT -- Analog CRT monitor
TMDS -- Desktop flat panel
So I thought the latter would be appropriate for two LCD monitors.
The manpage also doesn't mention any illegal combinations.
> What happens if you comment out this option or change
> it to "CRT,CRT"?
Nothing, no change.
Thanks,
Hans
next prev parent reply other threads:[~2007-04-18 15:02 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 ` Hans-Jürgen Koch [this message]
2007-04-18 21:20 ` [Linux-fbdev-devel] " 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 ` Radeon X300, radeonfb, dual head - conclusion Hans-Jürgen Koch
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=200704181702.21359.hjk@linutronix.de \
--to=hjk@linutronix.de \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=michel@tungstengraphics.com \
--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).