Linux PARISC architecture development
 help / color / mirror / Atom feed
From: "B. Douglas Hilton" <bdhilton@charter.net>
To: Tobias Giesen <tobias_subscriber@tgtools.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Question (fbdev, fbset, debconf)
Date: Fri, 23 Aug 2002 22:46:35 -0400	[thread overview]
Message-ID: <3D66F38B.40705@charter.net> (raw)
In-Reply-To: 002901c24afe$88ca1990$a80251d9@PLUTO

Don't get a Visualize-24 card. I don't think those
work right now either. Your choice of graphics boards
for a C200 is pretty slim. You have to be careful,
I found that out the HCRX-24Z board apparently fried
my onboard LAN devices when I plugged it onto the GSC bus.
I'm selling it on Ebay right now, so don't buy it,
it won't work :-)

Visualize-EG boards were the low-end boards for C-200
and I think C-180 machines. You may be able to scrounge
one if you are patient. I believe the one you want
is the A4450A. Even still it only has 8-bit color.

I'm going to be attempting to get a *Voodoo2* board
working with X, so if you hang around I may be able
to write a HOWTO-hppa-Voodoo2-XFree86 guide, assuming
it works.

In the meantime, consider getting a used dumb terminal.
I have one and it is pretty convenient at times like
these. If I was getting a new one I think I'd take my
chances on a Wyse-30, they are extremely compact, but
I'm not sure how developed their terminfo support is.
I used my dumb terminal to initially bootstrap my
machine.

Or just run a null modem cable into the serial port
of your other linux box and use something like minicom
to be its terminal.

I realize I'm ramlbing here. Well, I believe that people
are working on getting the FX2/4/6 board working, so
don't get rid of it just yet.




Tobias Giesen wrote:
>>get a used cheap Visualize-EG card somewhere.
> 
> 
> I see - any other models that will work? I read your post about a
> Visualize-24. Also, do all the different Visualize-EG models work?
> 

Not sure. Be careful about putting cards from older machines
into the C200. May cause hardware damage.

  reply	other threads:[~2002-08-24  2:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <002701c24af3$c5cb2b50$a80251d9@PLUTO>
2002-08-23 23:02 ` [parisc-linux] Question (fbdev, fbset, debconf) B. Douglas Hilton
2002-08-23 23:40   ` Tobias Giesen
2002-08-24  2:46     ` B. Douglas Hilton [this message]
2002-08-24  3:29       ` [parisc-linux] Voodoo2 (was: Question ...) Tobias Giesen
2002-08-24  4:13         ` B. Douglas Hilton
2002-08-24 14:14           ` Alan Cox
2002-08-25 16:54           ` Tobias Giesen
2002-08-25 20:47             ` Alan Cox
2002-08-24 14:01         ` Alan Cox
2002-08-25  8:48           ` Derek Engelhaupt
     [not found] <3D66B277.4020002@charter.net>
2002-08-23 22:16 ` [parisc-linux] Question (fbdev, fbset, debconf) Tobias Giesen
2002-08-23 19:59 Tobias Giesen

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=3D66F38B.40705@charter.net \
    --to=bdhilton@charter.net \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=tobias_subscriber@tgtools.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