From: "Michel Dänzer" <michel@daenzer.net>
To: Jeffery von Ronne <jronne@ics.uci.edu>
Cc: Kaoru Fukui <k_fukui@highway.ne.jp>, linuxppc-dev@lists.linuxppc.org
Subject: Re: two aty128 frame buffers?
Date: 06 Feb 2002 01:08:28 +0100 [thread overview]
Message-ID: <1012954108.1885.3328.camel@pismo> (raw)
In-Reply-To: <20020205151625.D761@reepicheep.ics.uci.edu>
On Mit, 2002-02-06 at 00:16, Jeffery von Ronne wrote:
> On Tue, Feb 05, 2002 at 10:28:33AM +0100, Michel Dänzer wrote:
> > > Unfortunately, that was not my real problem. I guess I forgot to mention
> > > that it crashes with a "signal 11" after the error message; now it crashes
> > > with a signal 11 and no error message.
> >
> > You need a hack like the attached one.
>
> I tried applying your hack to a virgin XF 4.2.0 source tree, and
> I get a signal 11 crash. The last output shows the X server loading
> vgahw.
Hmm, isn't info->VBIOS == NULL? If not, enforce the other route in that
if construct. :)
--
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member / CS student, Free Software enthusiast
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-02-06 0:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-04 23:46 two aty128 frame buffers? Jeffery von Ronne
2002-02-05 5:21 ` Kaoru Fukui
2002-02-05 6:22 ` Jeffery von Ronne
2002-02-05 9:28 ` Michel Dänzer
2002-02-05 23:16 ` Jeffery von Ronne
2002-02-06 0:08 ` Michel Dänzer [this message]
2002-02-06 23:37 ` Jeffery von Ronne
2002-02-07 1:11 ` Michel Dänzer
2002-02-07 5:12 ` Ani Joshi
2002-02-07 18:29 ` Derrik Pates
2002-02-07 19:26 ` Ani Joshi
2002-02-07 22:35 ` Jeffery von Ronne
2002-02-07 20:35 ` Timothy A. Seufert
2002-02-07 19:55 ` Jeffery von Ronne
2002-02-08 1:15 ` Jeffery von Ronne
2002-02-08 1:34 ` Michel Dänzer
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=1012954108.1885.3328.camel@pismo \
--to=michel@daenzer.net \
--cc=jronne@ics.uci.edu \
--cc=k_fukui@highway.ne.jp \
--cc=linuxppc-dev@lists.linuxppc.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).