> This does not work since /lib/modules/'uname
> -r'/kernel/drivers/gpu/drm/via ,this path does not exist in the chroot
> enviroment,
> 
> Question 1: How do I compile the driver in the chroot enviroment?

Ok, there's two issues here. First 'uname -r' is going to return the
active kernel version, but that's not necessrily whats on the
client. Second, you're probably going to need the kernel headers for
the kernel your client is using, otherwise it's not going to work
anyway.

So, look in your chroot and see what /lib/modules has inside it or
look in your tftp directory and find out what kernel your thin clients
are running. At this point there are a few different ways you can deal
with it, but one of the easiest (perhaps not the best) would be to
install linux-headers-<kernel_ver> in the and all your build tools
inside the, then follow the same process inside the chroot. 

> Problem 2:

An xorg.conf is going to be the easiest way to get done what you
want. I'd start by making everything work with the static xorg, then
figure out the xrandr stuff after you know that everything works under
xorg.

In order to give you any better advice I'd have to look at the scripts
for jaunty, and I don't really have it installed anywhere so... good
luck.

------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations 
Conference from O'Reilly Media. Velocity features a full day of 
expert-led, hands-on workshops and two days of sessions from industry 
leaders in dedicated Performance & Operations tracks. Use code vel09scf 
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
_____________________________________________________________________
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