[2887] in SIPB_Linux_Development
Re: Athena 8.4 install and HP Vetra VE8's.
daemon@ATHENA.MIT.EDU (Thomas Bushnell, BSG)
Fri Jul 21 14:41:18 2000
To: Bill Cattey <wdc@MIT.EDU>
Cc: linux-dev@MIT.EDU
From: tb@MIT.EDU (Thomas Bushnell, BSG)
Date: 21 Jul 2000 14:40:57 -0400
In-Reply-To: Bill Cattey's message of "Thu, 20 Jul 2000 22:59:15 +0000 ()"
Bill Cattey <wdc@MIT.EDU> writes:
> Bad News:
> The file tries to drive the display MUCH too hard. It starts X in
> 1600x1200 mode with too fast a refresh and I get a jaggy screen.
When you use the default install, you are promising that your monitor
can support an hsync range of 30-96 and vsync of 48-120. In order to
support cluster's install requirements, we have to hard code *some*
value in, that corresponds to the cluster workstations.
Some monitors (but not many) are able to be automatically detected and
configured, but not all, and in particular, not the exact ones we have
in the cluster.
Anyone whose monitor does not meet those requirements, must select
"custom install" and then "do custom X setup" which will run
Xconfigurator in non-automated mode, and everything will be fine.
This is therefore a documentation/advertising bug. When we have
complete installation instructions, I'll make sure to deal with it.
> Also, the extra memory is still ignored until I hand-edit lilo.conf.
This is a known sort of Linux kernel problem; I don't know any
automated way to deal with it. The kernel is supposed to be detecting
how much memory you have correctly, and the fact that it isn't is a
misfeature of your specific hardware in some way. I don't know a lot
about it, except that it's a persistent problem with Linux.
