From: "Yann Bizeul" <yann@tynsoe.com>
To: "P. Barrette" <barretp@mcmail.cis.McMaster.CA>,
Hollis R Blanchard <hollis+@andrew.cmu.edu>
Cc: puetzk6715@uni.edu, linuxppc-dev@lists.linuxppc.org,
linuxppc-user@lists.linuxppc.org
Subject: Re : X : caught signal 11 ?
Date: Wed, 21 Jul 1999 10:54:13 +0100 [thread overview]
Message-ID: <199907210848.DAA25068@lists.linuxppc.org> (raw)
Hi
> Hollis,
> I have the platinumfb too (7200), and I read your message, tried it and
> bang, x
> was down. I recompiled the kernel with the new driver (I didn't get it
> from your site it was mailed to me) and it is ok now. I never had this
> problem before with fvwm and accel X , maybe it is a Xpmac & the driver?
Which new driver do u use ?
I have recompiled the most recent stable kernel (2.2.10) and did not correct
that :'(
Thanks !
> --------
> Paul Barrette
> Ph.D. Candidate Classics (Latin Literature)
> System Administrator
> McMaster University
>
> "Oppositaque ad os manu nescio quid taetrum
> exsibilavit, quod postea Graecum esse affirmabat."
> --Petronius
>
> On Tue, 20 Jul 1999, Hollis R Blanchard wrote:
>
>>
>> On Tue, 20 Jul 1999 puetzk6715@uni.edu wrote:
>>
>> > Well, I switch on and off all the time (I have 6 console VT's and 2 X
>> > VT's). I used to get palette problems, but not since I applied anthony
>> > tong's patch and rebuilt X. It never died (well, it did in my cobbled
>> > pre-R5, but not in the released LinuxPPC 1999).
>>
>> I see. What video driver are you using? Yann, you too? As I mentioned, I'm
>> using platinumfb on a PowerCenter 132. I'm wondering if it's the driver. I
>> just got Mark Abene's updated driver but haven't had a chance to try it yet
>> (and won't for the rest of the week). For those of you who want to see if it
>> fixes anything, I've put it up at
>> http://www.andrew.cmu.edu/~hollis/platinumfb.c
>>
>> -Hollis
>>
>>
>>
>
>
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next reply other threads:[~1999-07-21 9:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-21 9:54 Yann Bizeul [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-07-21 9:55 Re : X : caught signal 11 ? Yann Bizeul
1999-07-20 17:41 Yann Bizeul
1999-07-20 15:57 Yann Bizeul
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=199907210848.DAA25068@lists.linuxppc.org \
--to=yann@tynsoe.com \
--cc=barretp@mcmail.cis.McMaster.CA \
--cc=hollis+@andrew.cmu.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=linuxppc-user@lists.linuxppc.org \
--cc=puetzk6715@uni.edu \
/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).