With just the masked ltsp-core installed, etherbooting my terminal (a Pentium 200 with 96MB of RAM, other specs available as needed) works fine, boots into X, and displays the GDM login screen. Once the masked ltsp-sound package is installed, etherbooting still works correctly and X starts, but GDM never displays. As an addendum, I did not yet turn on sound support in lts.conf, so it shouldn't even be attempting to load anything. Reproducible: Always Steps to Reproduce: 1. ACCEPT_KEYWORDS="~x86" emerge ltsp-core ltsp-sound 2. etherboot a network client. 3. Actual Results: The emerge works fine, but etherbooted client never displays a login screen. Expected Results: Following X startup, GDM should be displayed. emerge info: Portage 2.0.49-r20 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r9, 2.6.1-gentoo) ================================================================= System uname: 2.6.1-gentoo i686 AMD Athlon(tm) MP 2000+ Gentoo Base System version 1.4.3.10 distcc 2.11.1 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=athlon-mp -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3/share/config /usr/share/config /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /var/bind /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O3 -march=athlon-mp -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox userpriv" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="3dnow X X509 Xaw3d aalib acl acpi alsa apache2 apm arts avi berkdb bonobo cdr crypt cscope cups curl dga dillo directfb doc dvd emacs encode esd ethereal evms2 evo faad fbcon flash foomaticdb gb gd gdbm ggi gif gnome gnomedb gnutls gpm gtk gtk2 gtkhtml guile imap imlib innodb ipv6 jack java jikes jpeg kde ladcca lcd leim libg++ libgda libwww mad maildir mbox memlimit mikmod mmx motif mozilla mpeg mule mysql nas ncurses nls nvidia odbc offensive oggvorbis opengl oss pam pda pdflib perl plotutils png postgres ppds python qt quicktime readline ruby samba sasl sdl slang slp spell sse ssl tcltk tcpd tetex tiff transcode truetype usb v4l videos wxwindows x86 xface xinerama xml xml2 xmms xosd xv xvid zlib"
It probably was the ltsp4 core you emerged. You don't need and shouldn't be using ltsp-sound then. Ltsp4 includes already ltsp-sound and ltsp-sound ebuild in portage is ment for ltsp3 core. So it should break something with ltsp4...
Heh. Silly me, it -would- be something like that. I suppose, in that case, that ltsp-core for version 4 and the ltsp-sound package should be mutually blocking.
I'll fix the ltsp-sound ebuild in cvs soon to depend on ltsp-core 3 and not newer...