From: "Yann Bizeul" <yann@tynsoe.com>
To: Chris Baker <cbaker@adrenalin.com>,
Hollis R Blanchard <hollis+@andrew.cmu.edu>
Cc: linuxppc-dev@lists.linuxppc.org, linuxppc-user@lists.linuxppc.org
Subject: Re : X : caught signal 11 ?
Date: Tue, 20 Jul 1999 18:41:58 +0100 [thread overview]
Message-ID: <199907201636.LAA22308@lists.linuxppc.org> (raw)
>>
>> I also have problem 1), though I guess I've managed to disable xscreensaver
so
>> X does its built-in blanking thing (with no power saving =( ).
>
> I'm assuming you mean something along the lines of
>
> $ xset s off
>
> Does X have a built in blanking thing other than that? Or is it an Apple
hardware
> thing?
Ok, I did xset -s off, and it prevents xscreensaver from launchin...
Tha good question is about the built-in blanking :
All the time under R4, the screen (under X or console) goes black itself,
but I notice that under X, with R5, the screen does not fade out, but it
does in the console ?
hu ?
do ya understand something ?
>
>>
>>
>> To crash X:
>> startx
>> ctrl-cmd-F1
>>
>> Poof. All gone. If you have xdm set up, xdm reloads (and takes you to vc 7
>> from wherever you wanted to go in the first place). I'm using platinumfb. Is
>> anyone else out there able to use virtual consoles without X crashing?
>
> I can switch consoles o.k. I'm on a pb3400c so I guess that makes me
chips65550fb
> (?). If I put the machine to sleep for any significant period of time, X
dies.
>
> Is this just an xfree problem or is it in xpmac also?
>
> cheers,
>
> cbb
>
>
>
> [[ This message was sent via the linuxppc-user mailing list. Replies are ]]
> [[ not forced back to the list, so be sure to Cc linuxppc-user if your ]]
> [[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
> [[ and http://www.linuxppc.org/ for useful information before posting. ]]
>
>
[[ 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-20 17:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-20 17:41 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-21 9:54 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=199907201636.LAA22308@lists.linuxppc.org \
--to=yann@tynsoe.com \
--cc=cbaker@adrenalin.com \
--cc=hollis+@andrew.cmu.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=linuxppc-user@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).