I'm getting an LK201 and already have a 3W3 breakout cable, so now I'm
wondering if the graphics hardware in the 4000/60 or 4000/90 can properly
operate as a console and/or run X?
It's not clear of the work done back in 2004 / 2005 properly made it into
the tree in a usable form. If it did, then it's probably time to update
the list of NetBSD supported VAX hardware.
Also, does anyone know the specs of mice which will work with these VAXen?
Will any VAX mouse work with the VAXstation 4000s? Or should I just
connect a serial mouse to the spare serial port and configure X to use
that?
Thanks,
John Klos
--
Your mother manages RSX systems in Hell!
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-...@muc.de
happy hacking,
isildur
On Sun, 12 Jun 2011, John Klos wrote:
> Date: Sun, 12 Jun 2011 01:52:54 +0000 (UTC)
> From: John Klos <jo...@ziaspace.com>
> To: port...@NetBSD.org
> Subject: LCSPX / SPXg / LCG?
LCSPX works as console in 5.1, SPXg should also work, LCG does not IIRC.
I never tried X.
> It's not clear of the work done back in 2004 / 2005 properly made it into
> the tree in a usable form. If it did, then it's probably time to update
> the list of NetBSD supported VAX hardware.
Yes please :)
Hans
--
%SYSTEM-F-ANARCHISM, The operating system has been overthrown
>> I'm getting an LK201 and already have a 3W3 breakout cable, so now I'm
>> wondering if the graphics hardware in the 4000/60 or 4000/90 can properly
>> operate as a console and/or run X?
>
> LCSPX works as console in 5.1, SPXg should also work, LCG does not IIRC.
> I never tried X.
XdecNetBSD needs some minor modifications to work with the these
graphics hardware, but I think the vax has been switched to the xorg
version now, and XdecNetBSD doesn't exist for xorg.
The LCG is missing a driver though - the last one Blaz Antonic provided
was not working and I had set it aside for a while at the time. A few
months ago I was trying to get NetBSD installed on a 4000/60 and ran into
the missing graphics console driver problem, and started trying to get the
LCG driver working again. I was able to figure why it originally wasn't
working, but then I ran into a problem with the new locking code and
haven't figured out what to do with that problem yet.
The current problem I have with LCG is that the FIFO for sending
commands to the hardware can fill up easily, and I don't see any way to
sleep waiting for the hardware to catch up. I've got it working by just
waiting for the FIFO to empty out, but that leaves the machine sitting in
a short cpu loop with interrupts blocked.
Mike
--
Michael L. Hitch mhi...@montana.edu
Computer Consultant
Information Technology Center
Montana State University Bozeman, MT USA