Subject: Re: X on Turbo Channel system
To: None <M.Drochner@fz-juelich.de>
From: Murat Kumykov <firstname.lastname@example.org>
Date: 09/01/1999 16:21:22
This is a multi-part message in MIME format.
Content-Type: text/plain; charset=us-ascii
Matthias Drochner wrote:
> email@example.com said:
> > wsconscfg: WSDISPLAYIO_ADDSCREEN: Device busy wsconscfg:
> > WSDISPLAYIO_ADDSCREEN: Cannot allocate memory
> That's normal: The first screen does already exist because
> it is the system console. A second screen cannot be created
> because the graphics hardware driver doesn't support to
> allocate a second one. No framebuffer driver supports it at
> the moment. (Wouldn't be hard to add - more a matter of
> test equipment.)
> > and startx quits saying that no screens available.
> Don't know about X. Didn't even know that there is an X server
> for TC alphas.
Well, that was why I started playing with that, documentation on X
server for alphas
says that framebuffer is supported, but because no keyboard and mouse
support - no use
for it. But now keyboard and mouse works fine, so theoretically X should
And I remember someone noted about X running on this type of hardware
couple months ago, thats what I basically trying to reproduce.
Content-Type: text/x-vcard; charset=us-ascii;
Content-Description: Card for Murat Kumykov
adr:version:2.1;;One Cambridge Ctr;Cambridge;MA;02142;United States