[K12OSN] Lingering Release Issues

[Eric Harrison]

On Tue, 15 Aug 2006, Peter Hartmann wrote:

> I thought ltsp4.2 was supposed to have 7MB less residing in ram.
>
> Peter

Yes, in theory there should be LESS ram usage. But it was also mentioned
that this was a fairly old server (2.5 years old)... depending on exactly
what was installed and how it was used, it could have required less memory
on the terminals. I did a search for the error message that was posted
and didn't come up with anything... I just checked again and there was
a typo in the bug report that I didn't catch (sucks being dyslexic ;-),
I got a few hits this time.

Scott: the only errors I can find that are similar to this are for
Alpha servers (I'm sure you are not using those for terminals!), for
the old XFree86 3.x drivers (used 2.5 years ago, but not in K12LTSP 5),
and one reference to the i810 problems we had in the very early betas.

The fix for the i810 chipsets in the early betas was to specify the
vesa driver:

 	XSERVER = vesa

and later we found that it worked better to remove that line and to
specify a specific amount of memory used for video:

 	XVIDRAM="VideoRam 4096"

if that *still* doesn't work, try dropping it down to 2 megs:

 	XVIDRAM="VideoRam 2048"


Please post your findings and if possible please post exactly what
hardware is in the terminals that are not functioning properly.

-Eric

> On 8/15/06, R. Scott Belford <scott at hosef.org> wrote:
>> Eric Harrison wrote:
>> >
>> >
>> > try turning on swap, with LTSP 4.2 that is:
>> >
>> >     LTSP_USE_NBD_SWAP=Y
>> >
>> > -Eric
>> 
>> I have added this line to my lts.conf file.  I am using K12LTSP5.  If I
>> have added this correctly, then all of our problems persist.  Are there
>> any other suggestions?
>> 
>> I can downgrade to 4.2, but this seems the antithesis of what we are
>> trying to achieve.  Adding RAM to our clients is the antithesis of what
>> we are trying to achieve.  In my mind, if it works in one release, it
>> should work in the next.  If newer releases are going to demand more
>> resources of the clients, then we will not be able to follow the new
>> releases as we advocate for the use of older computers as thin clients.
>> 
>> --scott
>>