From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: Admar Schoonen <admar@luon.net>, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: sparc64, 2 x mach64 & 2.6.8-rc4: no working XFree86
Date: Sat, 14 Aug 2004 21:24:34 +0000 (UTC)
Date: Wed, 15 Sep 2004 05:21:45 +0800 [thread overview]
Message-ID: <200409150521.47587.adaplas@hotpop.com> (raw)
In-Reply-To: <20040814135408.GM21828@azrael.luon.net>
On Saturday 14 August 2004 21:54, Admar Schoonen wrote:
> Hi
>
> I have a sun blade 100 with 1 onboard PGX64 and 1 pci card PGX64 (both
> Ati mach64 cards).
>
> With linux 2.4 series, both framebuffers worked, and XFree86 worked on
> both cards.
>
> With 2.6.X (X <= 7), only the primary (onboard) card worked ; secondary
> was always black in console and in XFree86.
con2fb was broken before that version.
>
> Starting with 2.6.8-rc1, the console works on both cards again, however,
> XFree86 doesn't work anymore. It crashes with signal 11 even before it
> can display it's famous black & white dot pattern.
I tried with 1 PCI and 1 AGP nVidia card, PCI is primary. I use vesafb on the
primary, and I have no problems launching X on the secondary. If I initialize
the secondary card's ROM-BIOS, I can also modprobe rivafb and launch X-fbdev on
both the primary and secondary.
I cannot use rivafb for both because of conflicts.
Tony
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
next prev parent reply other threads:[~2004-08-14 21:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-14 13:54 sparc64, 2 x mach64 & 2.6.8-rc4: no working XFree86 Admar Schoonen
2004-08-14 21:24 ` Antonino A. Daplas [this message]
2004-08-18 19:27 ` Admar Schoonen
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=200409150521.47587.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--cc=adaplas@pol.net \
--cc=admar@luon.net \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).