Jim-

I have a newproblem with that setting (monitor = "mode not supported" and 
reports the H-freq as 53.7KHz, V-freq as 85.1 Hz.) If I put a # at the 
beginning of the line and comment it out, it will still fall back to VESA 
and boot up - and I can see the xorg.log either way. However I don't have 
ftp to the server when I am in that shell, so I can't send it to you. I do 
see "chipset KM400/KN400 not found" there under the via setting, which I 
assume is the problem. Is the latest version from the unichrome website? 
Maybe I could use the VT7205 driver, if available, as that seems to be the 
one needed for this chip (see http://unichrome.sourceforge.net/).

-Krishna

On Sat, 27 May 2006, Jim McQuillan wrote:

Krishna,

for via unichrome, you need:

   XSERVER = via


If you want to see the logfile, it exists in a ramdisk on the thin client.  You
can't see it from the server.  You need to set:

    SCREEN_01 = shell

Then, when you boot the client, you'll get a shell prompt.  at that point, type
'startx' and it will attempt to run the Xserver.  When it fails, then you can go
look at /tmp/mnt/X.log

Jim McQuillan
[EMAIL PROTECTED]



[EMAIL PROTECTED] wrote:
> Dear Petre, Sudev, Jim, et. al.:
> 
> Thanks again for all your help. I've now got it to at least read the
> section of lts.conf that relates to the host now named ws079, but it gives
> a fatal error when booting into X, with reference to a log I can't find
> (/tmp/mnt/X.log or something like that - neither/var/log/, /tmp/, nor
> /opt/ltsp/ contain anything related AFAIK.) I guess I really need to know
> what video to specify for a VIA Unichrome device, if that's included in
> the video section available, or load a new driver. I suppose I'll like the
> non-slow non-VESA compatibility mode performance better than what I'm
> getting now.
> 
> -Krishna
> 
> On Sat, 27 May 2006, Petre Scheie wrote:
> 
> Put this in /etc/dhcpd.conf and then restart dhcpd:
> 
> host ws079 {
>          hardware ethernet    00:16:ec:1d:6c:49;
>       fixed-address           192.168.1.79;
> }
> 
> There are other parameters that can be added, but this will get you started.
> 
> Petre
> 
> Krishna Murphy wrote:
>   
> > Dear Sudev:
> > 
> > Thanks!
> > 
> > I thought that it being identified by its NIC, and then as 192.168.1.79
> >     
> would
>   
> > be sufficient to make the numeric portion of [ws079] the link between
> >     
> the two.
>   
> > How does one enter the hostname in the dhcpd.conf?
> > -Krishna
> > 
> > On Sat, 27 May 2006, Sudev Barar wrote:
> > 
> > On 26/05/06, Krishna Murphy <[EMAIL PROTECTED]> wrote:
> > 
> >     
> > > Jim-
> > > 
> > > Thanks! I'll put some ***s before my responses, below.
> > > 
> > > -Krishna
> > > 
> > >       
> > Krishna an inline bottom posting would work much better ;-)
> > 
> > 
> >     
> > > I'm guessing that the specific workstation doesn't know it's own
> > >       
> hostname.
>   
> > > Or,
> > > it doesn't match what you've put in [xxxx] in the lts.conf file.
> > >       
> > [SNIP]
> > 
> > In the section below of lts.conf you are giving a host name ws079
> > 
> > 
> >     
> > > [ws079]
> > >         XSERVER = savage
> > >         X_MODE_0 = 800x600
> > >         X_MODE_1 = 640x480
> > >         X_MODE_2 = 1024x768
> > >         SCREEN_02 = shell
> > >       
> > [SNIP]
> > 
> >     
> > > > Here's the dhcpd.conf:
> > > >         
> > > _______________________________________________________________________________
> > > # dhcpd.conf
> > > 
> > >       
> > [SNIP]
> > 
> >     
> > >         host test1 {
> > >         hardware ethernet 00:16:ec:1d:6c:49;
> > >                 fixed-address 192.168.1.79;
> > >                 filename "/lts/2.6.16.1-ltsp-2/pxelinux.0";
> > >                 }
> > >     if substring (option vendor-class-identifier, 0, 9) = "PXEClient" {
> > >         filename "/lts/vmlinuz-2.6.16.1-ltsp-2";
> > > }
> > > 
> > >       
> > But you are not defining the host name in dhcpd.conf above. You neet
> > to add a line  like within the curly brackets for each host:
> > 
> > option host-name "test1";
> > 
> > I hope this should solve the problem.
> > 
> > 
> > 
> > 
> > -------------------------------------------------------
> > All the advantages of Linux Managed Hosting--Without the Cost and Risk!
> > Fully trained technicians. The highest number of Red Hat certifications in
> > the hosting industry. Fanatical Support. Click to learn more
> > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
> > _____________________________________________________________________
> > Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
> >       https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> > For additional LTSP help,   try #ltsp channel on irc.freenode.net
> > 
> >     
> 
> 
> 
> 
> -------------------------------------------------------
> All the advantages of Linux Managed Hosting--Without the Cost and Risk!
> Fully trained technicians. The highest number of Red Hat certifications in
> the hosting industry. Fanatical Support. Click to learn more
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
> _____________________________________________________________________
> Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
>       https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help,   try #ltsp channel on irc.freenode.net
>   


-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Reply via email to