From: Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>
To: Ralf Ackermann <rac@KOM.tu-darmstadt.de>
Cc: linux-mips@linux-mips.org
Subject: Re: Q: XFree86 (on MeshCube) from Debian?
Date: Wed, 11 Aug 2004 20:45:57 +0200 [thread overview]
Message-ID: <87smatpl7e.fsf@mrvn.homelinux.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0408110935080.16674@shofar.kom.e-technik.tu-darmstadt.de> (Ralf Ackermann's message of "Wed, 11 Aug 2004 09:35:35 +0200 (CEST)")
Ralf Ackermann <rac@KOM.tu-darmstadt.de> writes:
> Hello,
>
> thanks a lot to the persons who helped me setting up a Debian/Sarge
> environment for the MeshCube (using cdebootstrap worked like a charm).
>
> I may go on with an XFree86 server now (I tried using the ati module):
> ...
> XFree86 Version 4.3.0.1 (Debian 4.3.0.dfsg.1-6 20040709164028
> root@remake.rfc822
> .org)
> Release Date: 15 August 2003
> X Protocol Version 11, Revision 0, Release 6.6
> Build Operating System: Linux 2.4.25 mips [ELF]
> Build Date: 10 July 2004
> ...
>
> Nevertheless - the server refuses to start because of:
> Fatal server error:
> xf86OpenConsole: Cannot open /dev/tty0 (No such file or directory)
>
> Can this be fixed without having to install an alternative kernel on the
> cube? (e.g. by loading an additional / which? kernel module?)
cdebootstrap only creates the absolutely essential device nodes for a
chroot. You need more device nodes, udev or devfs.
cd /dev
MAKEDEV generic
> best regards and thanks for your help
> Ralf
MfG
Goswin
prev parent reply other threads:[~2004-08-11 18:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-11 7:35 Q: XFree86 (on MeshCube) from Debian? Ralf Ackermann
2004-08-11 8:07 ` Tiemo Krüger - mycable GmbH
2004-08-11 9:05 ` Michael Stickel
2004-08-11 18:45 ` Goswin von Brederlow [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=87smatpl7e.fsf@mrvn.homelinux.org \
--to=brederlo@informatik.uni-tuebingen.de \
--cc=linux-mips@linux-mips.org \
--cc=rac@KOM.tu-darmstadt.de \
/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