[Ltsp-discuss] Xorg uses all the CPU.
The server, the client and the net is overdimensioned. The client has slowing downs when it manages modifications of screen. Sometimes it stops completely for 1 or 2 seconds. If I use top on local bash, I see that it's xorg to occupy all the resources. Radeon module is on and glxinfo is ok. If I start OS on client I haven't problem with xorg. Ubuntu 64 for server. 386 image for client. Xfce or TDE is equal. What can I do for resolve the problem? Thanks. Rodolfo -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _ 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
[Ltsp-discuss] Best way to connect to server
Hi List, I have a running LTSP server (Debian based) I have a very old laptop (P 166 based / 48 MB RAM) that does not have floppy nor cdrom nor pxe capability. The NIC is a PCMCIA One. After trying mutiple solutions (gPXE, netboot ...) I finally installed a minimal debian system on it, and made the PCMCIA work. What is the best way to connect to the server ? - Some kind of chainloading to boot from the server once the network is up ? - some floppy image (like wireless_ltsp) that I did not manage to boot using LILO ? - Install a minimal X and connect trough it ? (I am afraid doing so would lead to sound and usb issues as well as slow performance) Thank's for your advice. -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _ 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
Re: [Ltsp-discuss] Xorg uses all the CPU.
Some tweaks you can do to get Xorg CPU usage down, in lts.conf: X_COLOR_DEPTH=16 LDM_DIRECTX=True Read the manpage for lts.conf what these are exactly. Enabling LDM_DIRECTX could pose a security threat on networks where packet sniffing might be an issue. On the other hand, if you trust the people connected to your LTSP network, you could very well enable it. Met vriendelijke groet, Jan Middelkoop Recreatie en Zorg Groep B.V. -- Website: http://www.recreatie-zorg.nl/ E-mail: j...@recreatie-zorg.nl Telefoon: +31 10 714 22 97 Op 14-03-12 09:43, relosrl schreef: The server, the client and the net is overdimensioned. The client has slowing downs when it manages modifications of screen. Sometimes it stops completely for 1 or 2 seconds. If I use top on local bash, I see that it's xorg to occupy all the resources. Radeon module is on and glxinfo is ok. If I start OS on client I haven't problem with xorg. Ubuntu 64 for server. 386 image for client. Xfce or TDE is equal. What can I do for resolve the problem? Thanks. Rodolfo -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _ 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 -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _ 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
Re: [Ltsp-discuss] Best way to connect to server
On 14/03/2012 04:51 μμ, Pierre AUSSAGUEL wrote: ...The NIC is a PCMCIA One. What is the best way to connect to the server ? You only need to transfer the LTSP kernel and initrd to your local disk. Copy the kernel from /srv/tftp/ltsp/i386/vmlinuz etc to a new /ltsp/ dir on your client. Then create grub entries (from /etc/grub.d/40-custom or so) for this kernel, with the same boot parameters as specified in your server's /srv/tftp/ltsp/i386/pxelinux.cfg/default. If special steps were needed for your PCMCIA card to work, do them in your server LTSP chroot to get an initramfs that supports it. -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _ 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
Re: [Ltsp-discuss] Best way to connect to server
Quoting Pierre AUSSAGUEL pierre_aussag...@yahoo.fr: Hi List, I have a running LTSP server (Debian based) I have a very old laptop (P 166 based / 48 MB RAM) that does not have floppy nor cdrom nor pxe capability. The NIC is a PCMCIA One. After trying mutiple solutions (gPXE, netboot ...) I finally installed a minimal debian system on it, and made the PCMCIA work. What is the best way to connect to the server ? - Some kind of chainloading to boot from the server once the network is up ? I think this approach. I've only done this sort of thing on 4.2 (compiled myself but based on the wireless-ltsp work). Once you've got a running kernel on your guest, which should include all the LTSP init stuff in there by the way - the process should continue. Basically, try putting the LTSP chroot's kernel on the thin client and see what happens. Perhaps this could be done by installing ltsp-client or ltsp-client-core on the thin client Debian install. There may be further ammendments to the initramfs before it'll work for your specific clients. Have a look at the following file in the ltsp-client-core packages for more clues as to what is happening: /usr/share/initramfs-tools/conf.d/ltsp /usr/share/initramfs-tools/hooks/ltsp_nbd /usr/share/initramfs-tools/hooks/udhcp /usr/share/initramfs-tools/scripts/init-premount/udhcp /usr/share/initramfs-tools/scripts/ltsp_nbd /usr/share/initramfs-tools/scripts/nfs-bottom/ltsp Hope this gives you some clues, and I hope you furnish the LTSP project with a working PXEless client image once you've completed it! Please please let us know how it goes, I've been wanting to sort this sort of booting for 5.x for some time but not got round to it. For reference, the rest of ltsp-client-core: http://packages.debian.org/squeeze/i386/ltsp-client-core/filelist Cheers, == From Ben Green -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _ 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
