From: Michel Dänzer <daenzer@relog.ch>
To: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>
Cc: Sinan Gürkan <sgurkan@superonline.com>,
linux-apus-user@lists.sourceforge.net,
debian-powerpc@lists.debian.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: New experimental X 4.0 not working
Date: Tue, 06 Jun 2000 22:07:04 +0200 [thread overview]
Message-ID: <393D59E8.9656E51E@relog.ch> (raw)
In-Reply-To: Pine.LNX.4.10.10006062156360.1984-100000@opal.biophys.uni-duesseldorf.de
Michael Schmitz wrote:
>
> > > I installed XFree4.0b...but it doesn`t work...
> > > after startx command it loads a bit and it freezes the whole system.
> > > You have to reboot and filesystem is corrupted..(I ran fsck 3 times :) )
> >
> > Do you use update/bdflush/whatever? I get lotsa lockups when hacking
> > kernels and X servers, but I've never had to run fsck more than twice
> > (once automatically and once manually).
>
> I had a case where such a freeze hosed various things on my root and usr
> partitions. That was during the XFree 4.0 PCI resources trouble hacking.
> Is the machine in question one with Mach64 graphics?
No, it's an Amiga with Permedia2 and he used the wrong binary.
Michel
--
So many Christians, so few lions.
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-06-06 20:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <yam8192.1708.1987516072@mail.superonline.com>
2000-06-06 14:40 ` New experimental X 4.0 not working Michel Dänzer
2000-06-06 19:58 ` Michael Schmitz
2000-06-06 20:07 ` Michel Dänzer [this message]
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=393D59E8.9656E51E@relog.ch \
--to=daenzer@relog.ch \
--cc=daenzerm@student.ethz.ch \
--cc=debian-powerpc@lists.debian.org \
--cc=linux-apus-user@lists.sourceforge.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=schmitz@opal.biophys.uni-duesseldorf.de \
--cc=sgurkan@superonline.com \
/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).