David-
Not sure about this, but it looks like the X stuff in LTSP changed between
3.0 and 4.2, and your modeline isn't what it needs any more. If you can
somehow boot a Knoppix or Ubuntu live disk on crow-apm, take a look at
what it puts in X logfile and see if you can apply that to this situat
I think you'll see why it's doing that (and why it's unimportant) if you
$ cat /etc/hosts|grep
What I get is:
192.168.1.79ws079.ltsp ws079
Those entries in that file are made by ltspcfg for a "pool" approach to
assigning IP addresses - really quite wrong for me, now, but I hav
Hey-
I've poked around a good bit on the local system and not found what I'm
looking for (the stuff that goes flying by when the workstation is in the
process of booting up.) Anybody know where to direct me to find the dmesg-
equivalent file? I've seen some interesting-looking stuff there, and
Greetings.
We just had a big discussion about this a couple of weeks ago. I recommend
you do a search in the archives for:
[Ltsp-discuss] What distribution should I use?
With kind regards,
Peter, hieromonk
Dormition Skete
Our Monastery Website: http://www.DormitionSkete.org
Our Catech
Hey-
I don't think anyone will be able to help much with the information
provided so far. Perhaps you could start with a copy of your entire
dhcp.conf and some additional detail about the workstation (especially
what LAN card/chip is used, etc.)
-Krishna
On Sat, 17 Jun 2006, Metal Gear wrote:
Jim-
You're right, there was a "range" statement left over in my dhcp.conf from
the past when I was (unwisely) doing DHCP with both a pool of addresses
and specific MAC addresses. I had picked up on the need to comment out the
"get-lease-hostnames true;" line when using
"use-host-dec
Stefan-
I have M7VIG-400 motherboard with a VIA chipset video up as a terminal on
LTSP-4.2, and it took not only specifying the VIA driver, but also setting
limits on sync rates (based on my monitor's capacity) to force correct
calculation of the "modelines". I think that driver's a little bugg
Tim-
I had noted the same difference on my setup, but making that change didn't
do any good. I since switched it back, and as you said, "it just decided
to work" when I made the change to a different version of FUSE. It does
seem like the switch to a local terminal helps - watching the response
