From: jason@openinformatics.com (Jason E. Stewart)
To: debian-powerpc@lists.debian.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: Success! (was Re: External Monitor under Pismo)
Date: 03 May 2001 20:10:31 -0600 [thread overview]
Message-ID: <87wv7x984o.fsf@amadeus.openinformatics.com> (raw)
In-Reply-To: <3AEDEF2D.4B823134@iiic.ethz.ch>
"Michel Dänzer" <michdaen@iiic.ethz.ch> writes:
> I am reluctant to do that. I'd prefer to get a solution into XFree86.
>
> Someone please try the attached patch against current CVS. It turns Option
> "UseBIOSDisplay" (which probably doesn't work for us - no BIOS here...) into
> Option "Display" which accepts modes "CRT", "FP", "Mirror" and "BIOS".
Hey Michel,
I've had a heck of a time with this one. Using the new r128_drv.o that
I compile from the CVS HEAD gives me an error that the module is using
a newer ABI than the server...
So I compiled and installed the whole X package from CVS (into
/usr/X11R6-local using ProjectRoot). I get some strange behavior,
namely it doesn't find my .xsession and the keyboard input is messed
up (I have to type '1', 'n', '5', '3', '8') to type exit<return>.
I tried to use my old X configuration and it doesn't work at all,
server just hangs. I figured some configuration files in /etc/X11 must
have gotten stomped by the CVS install of X, so I ran dpkg --remove of
xserver-common and xserver-xfree86, followed by an apt-get install,
but it's still hosed.
Help???
jas.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-05-04 2:10 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-04 9:21 External Monitor under Pismo Iain Sandoe
2001-04-04 17:01 ` Andrew Sharp
2001-04-04 18:43 ` Jason E. Stewart
2001-04-04 18:01 ` Michel Dänzer
2001-04-04 19:28 ` Jason E. Stewart
2001-04-04 21:45 ` Michel Dänzer
2001-04-04 23:19 ` Jason E. Stewart
2001-04-04 22:22 ` Michel Dänzer
2001-04-05 19:55 ` Jason E. Stewart
2001-04-05 19:48 ` Michel Dänzer
2001-04-05 21:49 ` Jason E. Stewart
2001-04-05 23:46 ` Jason E. Stewart
2001-04-05 23:28 ` Michel Dänzer
2001-04-06 3:04 ` Steven Hanley
[not found] ` <87itjmf7lf.fsf_-_@amadeus.openinformatics.com>
2001-04-30 23:03 ` Success! (was Re: External Monitor under Pismo) Michel Dänzer
2001-05-04 2:10 ` Jason E. Stewart [this message]
2001-05-03 22:18 ` Michel Dänzer
2001-05-04 9:08 ` Jason E. Stewart
2001-05-04 12:05 ` Michel Dänzer
2001-05-04 17:14 ` Jason E. Stewart
2001-05-04 17:16 ` Jason E. Stewart
2001-05-05 1:37 ` Michel Dänzer
2001-05-05 9:38 ` Jason E. Stewart
2001-05-05 17:59 ` Michel Dänzer
2001-05-05 21:14 ` Jason E. Stewart
2001-05-06 13:32 ` Michel Dänzer
2001-05-06 21:55 ` Jason E. Stewart
2001-05-07 8:15 ` Michel Dänzer
2001-05-04 12:29 ` Benjamin Herrenschmidt
2001-05-04 13:34 ` Sven LUTHER
2001-05-04 13:57 ` Benjamin Herrenschmidt
2001-05-04 14:06 ` Sven LUTHER
2001-05-04 14:13 ` Benjamin Herrenschmidt
2001-05-04 14:14 ` Geert Uytterhoeven
2001-05-04 14:23 ` Sven LUTHER
2001-05-04 14:54 ` Benjamin Herrenschmidt
2001-05-04 15:05 ` Ramprasad Rao
2001-05-04 15:09 ` Benjamin Herrenschmidt
2001-05-04 15:17 ` Ramprasad Rao
2001-05-04 20:50 ` Michael Schmitz
2001-05-05 1:03 ` Benjamin Herrenschmidt
2001-05-05 18:49 ` Michael Schmitz
2001-05-04 17:10 ` Jason E. Stewart
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=87wv7x984o.fsf@amadeus.openinformatics.com \
--to=jason@openinformatics.com \
--cc=debian-powerpc@lists.debian.org \
--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).