Can the JS-1 do "crap VGA" 640x480 ?
Todd Whitesel
over e-bay right now) can be set to "crap VGA" 640x480 resolution??
If so, then I am probably gonna buy about three dozen of those things,
and use them as thin clients (networked ASCII terminals, really, with
support for a printer on the serial port).
Todd Whitesel
toddpw @ best.com
Jason R Thorpe
> Does anyone know if the JavaStation-1 (the system that's being dumped all
> over e-bay right now) can be set to "crap VGA" 640x480 resolution??
The TCX framebuffer in the JS-1 might do the monitor sense properly
and set itself to that resolution. You'd almost have to check it,
really.
I can happily report, however, that my JS-1 works quite well with
a 15'' TFT display at 1024x768.
--
-- Jason R. Thorpe <tho...@zembu.com>
Todd Whitesel
> and set itself to that resolution. You'd almost have to check it,
> really.
Hm. Any chance I could drop by later this week with a monitor and some
keyboards to try out??
Jason R Thorpe
> Hm. Any chance I could drop by later this week with a monitor and some
> keyboards to try out??
That'd be fine with me .. but, much later ... maybe weekend?
Todd Whitesel
> > keyboards to try out??
>
> That'd be fine with me .. but, much later ... maybe weekend?
Hold on that... Thanks to Matt Thomas I now have a few days' access to
a JS-1 and we'll see how far I get.
How -current do I have to be to expect JS-1 support to work?
(Or is the latest 1.5ALPHA snapshot good enough?)
Josh Davidson
http://metalab.unc.edu/pub/Linux/docs/HOWTO/other-formats/html_single/JavaStatio
n-HOWTO.html
It seems pretty informative, but it may already be stuff you know.
Later,
Josh
*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/
Josh Davidson ** ** **** ** ****** ** **
Sys/Net Admin ** ** ** ** ** ** ****
PHAT Beach Records ** ** ** ** ** ** ** **
****** ** **** ****** ** **
*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/
Todd Whitesel
>
> http://metalab.unc.edu/pub/Linux/docs/HOWTO/other-formats/html_single/JavaStation-HOWTO.html
>
> It seems pretty informative, but it may already be stuff you know.
Thanks, that was a more complete version of the one I already found.
Still no mention of the keyboard problem we are seeing however.
I tried hooking up a DEC-made PS/2 keboard and got the exact same
results "keyboard not found, switching to serial" as with the JS-1's
included Sun keyboard. (I also tried connecting the mouse in case that
had any side effects -- didn't make a difference.)
Is everyone's JS-1 colored like a typical SparcStation? According to the
FAQ URL above, the one I have is "Mr. Coffee White Case Variation #2" but
I note that in the last picture on the page (the lab picture), all of the
visible JavaStations look like the non-white-case "Mr. Coffee".
Maybe the white-case versions had hardware bugs? It's already clear from
the release note in the shipping carton that it was a developer's early
access version.
Erik E. Fair
and properies from NetBSD?
Erik <fa...@clock.org>
Steinar Hamre
> I tried hooking up a DEC-made PS/2 keboard and got the exact same
> results "keyboard not found, switching to serial" as with the JS-1's
> included Sun keyboard. (I also tried connecting the mouse in case that
> had any side effects -- didn't make a difference.)
The OpenBoot does not know how to access the keyboard. (At least for
the 2.30 version.) Changing the hardware can't have any effect.
But, the OpenBoot probably do know how to talk to a sun Type-4 and
Type-5-keyboard over the exact same chip used for the PS/2
keyboard. But testing that would require some serious hardware
hacking.
> Is everyone's JS-1 colored like a typical SparcStation? According to
> the FAQ URL above, the one I have is "Mr. Coffee White Case
> Variation #2" but I note that in the last picture on the page (the
> lab picture), all of the visible JavaStations look like the
> non-white-case "Mr. Coffee".
All we have is purplegrayish, like the one on the picture.
> Maybe the white-case versions had hardware bugs? It's already clear from
> the release note in the shipping carton that it was a developer's early
> access version.
Don't think so. The keyboard does not work in the PROM because this
was never designed to work.
Steinar
Josh Davidson
do the Linux guys handle this problem?
Quoting Steinar Hamre <stei...@stud.fim.ntnu.no>:
/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-
Josh Davidson ** ** **** ** ****** ** **
Sys/Net Admin ** ** ** ** ** ** ****
PHAT Beach Records ** ** ** ** ** ** ** **
****** ** **** ****** ** **
/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-*/-
Eduardo Horvath
> Are you guys trying this with the NetBSD driver for the type 3-4-5 driver? How
> do the Linux guys handle this problem?
If you really want to know the details of all those boxes ask Pete
Zaitzev.
Eduardo Horvath
Todd Whitesel
> was never designed to work.
Amazing...
Has anyone had success with the keyboard at all yet?
Steinar Hamre
Josh Davidson <dog...@ductape.net> writes:
> Are you guys trying this with the NetBSD driver for the type 3-4-5
> driver? How do the Linux guys handle this problem?
I was talking about the PROM. Whether it works in the monitor has
nothing with NetBSD to do.
Making the keyboard work after NetBSD is booted is a completely
separate issue. This is of course possible. (If it's not already
done. Due to lack of disk on the compile and boot server, and the lack
of time to do anything about that, I haven't gotten around to do any
testing for the last couple of months.)
Steinar
Paul Kranenburg
> and properies from NetBSD?
I used it a long time ago; maybe it still works.
-pk