[K12OSN] k12ltsp 5beta2 details

[Angus Carr]

That's the ticket!

I cleared out my various attempts, went back to a raw lts.conf, and then 
put X_VIDEORAM in as a global entry (All my terminals are identical old 
Dell GX150's) and voila! It worked.

Thanks.

Angus Carr.

Eric Harrison wrote:
>
> On my i810 box, setting the X video ram to 16M does the trick:
>
>     X_VIDEORAM = 16384
>
> -Eric
>
> On Mon, 24 Apr 2006, Angus Carr wrote:
>
>> Tried it today (after doing a yum upgrade on my K12LTSP 5 Beta 
>> machine) and it still reports that it cannot load the agpgart module 
>> (as before).
>>
>> If I do a vga module instead (with colour depth 8), the screen goes 
>> graphical at 800x600. That's not what I want, but it does do it.
>>
>> Angus.
>>
>> Jim McQuillan wrote:
>>> Angus,
>>>
>>> Can you try:    XSERVER = i810
>>>
>>> I just found today, that we are missing some entries in the vidlist 
>>> file for some of the i810 chipsets.
>>>
>>> I'll have an update soon, but you can force it with the line above.
>>>
>>> Jim McQuillan
>>> jam at Ltsp.org
>>>
>>>
>>>
>>> Angus Carr wrote:
>>>> I just did a yum upgrade, and it's still Broke.
>>>>
>>>> XSERVER=auto  ==> agpgart error, screen flashes, then returns to 
>>>> text mode, reporting X has failed.
>>>> XSERVER=vesa ==> grey garbage screen, although clearly derived from 
>>>> the default background.
>>>>
>>>> Eric Harrison wrote:
>>>>> On Wed, 12 Apr 2006, Jim McQuillan wrote:
>>>>>
>>>>>> Roy,
>>>>>>
>>>>>> My understanding of the i810 issue is that it's related to udev 
>>>>>> rules that didn't properly create the device node that the i810 
>>>>>> driver requires.  Scott has fixed the rules, and we've got an 
>>>>>> updated LTSP package for that.  I think this was fixed last 
>>>>>> friday, and I don't know if Eric has updated his copy of the LTSP 
>>>>>> sources, so he may not have that fix yet.
>>>>>
>>>>> I updated my packages this afternoon, but have not had the chance 
>>>>> to test
>>>>> them against my i810-based terminal. The attached udev rules match 
>>>>> the
>>>>> new K12LTSP packages, so hopefully that is the fix.
>>>>>
>>>>> The new packages have been added to the K12LTSP repository.
>>>>>
>>>>> -Eric
>>>>>
>>>>>> I've attached the 2 new udev rules files.
>>>>>>
>>>>>> Drop them into /opt/ltsp/i386/etc/udev/rules.d, and try booting 
>>>>>> your client.
>>>>>>
>>>>>> Let us know if that takes care of the problem.
>>>>>>
>>>>>> Jim McQuillan
>>>>>> jam at Ltsp.org
>>>>>>
>>>>>>
>>>>>>
>>>>>> Roy wrote:
>>>>>>> I haven't been able to use my i810 since K12-FC5 so I the vesa 
>>>>>>> thing and the
>>>>>>> gui comes up but I have a frequency issue. I'm guessing I will 
>>>>>>> have to set
>>>>>>> that manually too. Do you know what could have happened? My i810 
>>>>>>> always
>>>>>>> worked before.
>>>>>>>
>>>>>>> Roy
>>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: k12osn-bounces at redhat.com 
>>>>>>> [mailto:k12osn-bounces at redhat.com] On Behalf
>>>>>>> Of Eric Harrison
>>>>>>> Sent: Wednesday, April 12, 2006 4:56 PM
>>>>>>> To: Support list for opensource software in schools.
>>>>>>> Subject: Re: [K12OSN] k12ltsp 5beta2 details
>>>>>>>
>>>>>>> Angus Carr wrote:
>>>>>>>
>>>>>>>> Hi, all, and particularly Eric.
>>>>>>>>
>>>>>>>> I had a few minor issues setting up 5beta2, and I thought I should
>>>>>>>>
>>>>>>> share...
>>>>>>>
>>>>>>>> 1) The default internal LAN address was 192.168.0.254, which 
>>>>>>>> isn't a
>>>>>>>> problem, unless you already sit on such a LAN. Our main LAN is
>>>>>>>> 192.168.0.*, and my LTSP LAN is 192.168.200.*. This really isn't a
>>>>>>>> problem, but not all the files were correctly written. 
>>>>>>>> k12ltsp-DHCP.conf
>>>>>>>> (or whatever it was called) required a search and replace.
>>>>>>>>
>>>>>>>
>>>>>>> Thanks, I have checking that on my todo list (which I'm working 
>>>>>>> on right
>>>>>>> now ;-)
>>>>>>>
>>>>>>>
>>>>>>>> 2) The firewall was up by default on the internal address, and 
>>>>>>>> that
>>>>>>>> didn't allow tftp. I dropped it, but that was slightly wrong. 
>>>>>>>> One day, I
>>>>>>>> might even bring it back up, but this is internal, on a quiet 
>>>>>>>> LAN behind
>>>>>>>> another firewall. I'm not too worried... (for now).
>>>>>>>>
>>>>>>>
>>>>>>> Possible related to #1. I have not seen a problem with the default
>>>>>>> 192.168.0.254.
>>>>>>>
>>>>>>>
>>>>>>>> 3) Other than that, there were no issues. I just feel that a 
>>>>>>>> numbered
>>>>>>>> list should have more than two bullets.
>>>>>>>>
>>>>>>>
>>>>>>> Good to hear.
>>>>>>>
>>>>>>>
>>>>>>>> 4) Oh, right, my i810/agpgart problem. Hmmm.... don't know what 
>>>>>>>> to do
>>>>>>>> about that, but there is usually some response on the list...
>>>>>>>>
>>>>>>>
>>>>>>> I scrounged up a box with an i810, I saw the same problem. 
>>>>>>> Untested, but
>>>>>>> the vesa driver will probably be a quick work-around:
>>>>>>>
>>>>>>>     XSERVER = vesa
>>>>>>>
>>>>>>>
>>>>>>>> Thanks, again, for the work of putting this together. I 
>>>>>>>> appreciate it as
>>>>>>>> much as anyone else on the list.
>>>>>>>>
>>>>>>>> Angus Carr.
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> -Eric