> For the most part, LTSP does a very good job of detecting what hardware’s on > your thin client. However, it’s possible that you may want to manually > specify > a kernel module to load after boot.
...._after boot_ ...which implies you got past the NFSroot mounting...which he can't since he doesn't have the correct NIC driver from what I can read. ET On 2010-01-27, at 5:57 PM, Xavier Brochard wrote: > Le mercredi 27 janvier 2010 18:44:40, Michael George a écrit : >> On Tue, Jan 26, 2010 at 06:20:38AM -0500, Michael George wrote: >>> I'm trying to move to LTSP 5 on my Gentoo system. I have the client >>> system built, the TFTP (tftp-hpa) and DHCP (dhcp) working to provide the >>> necessary files, but the terminal hits a kernel panic when it tries to >>> mount / over NFS. It says that there's no network available. >>> >>> I know the connection is good, because it pulled the kernel and >>> initramfs. It looks like it picks the tg3 NIC driver to use for network- >>> ing, but the system uses the 3C950 chipset and would need the 3C95x >>> driver. >>> >>> I'm wondering if anyone here uses LTSP much and might be successfully >>> using old Dell Optiplex GX1's and could perhaps give me some insight. >> >> Is there a way I can force specific modules to be loaded by LTSP >> clients? That would at least allow me to test whether that it the only >> problem I have. > > See chapter 12 of the documentation: > http://sourceforge.net/apps/mediawiki/ltsp/index.php?title=Ltsp_LtspDocumentationUpstream > Some extract below: > > Modules and startup scripts > ================== > For the most part, LTSP does a very good job of detecting what hardware’s on > your thin client. However, it’s possible that you may want to manually > specify > a kernel module to load after boot. Alternatively, you may have a script > you’ve written that you’ve put in the chroot, and want to make sure gets run > at startup. LTSP provides some hooks to allow you to do this. > > MODULE_01...MODULE_10 string, default unset > Up to 10 kernel modules can be loaded by using these configuration entries. > The > entire command line that you would use when running insmod can be specified > here. For example: > MODULE_01 = uart401.o > MODULE_02 = "sb.o io=0x220 irq=5 dma=1" > MODULE_03 = opl3.o > > If the value of this parameter is an absolute path name, then insmod will be > used to load the module. Otherwise, modprobe will be used. > In normal circumstances, you shouldn’t need to specify anything here, as most > hardware will be auto-detected. > > > Xavier > xav...@alternatif.org - 09 54 06 16 26 > > ------------------------------------------------------------------------------ > The Planet: dedicated and managed hosting, cloud storage, colocation > Stay online with enterprise data centers and the best network in the business > Choose flexible plans and management services without long-term contracts > Personal 24x7 support from experience hosting pros just a phone call away. > http://p.sf.net/sfu/theplanet-com > _____________________________________________________________________ > 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 ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _____________________________________________________________________ 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
