I don't know if this will help exactly but I had a similar problem with getting an eeepc to work as a thin client a long time ago as it couldn't detect the ethernet driver on the client.
After doing the following it worked: $ sudo chroot /opt/ltsp/i386 # vi /etc/initramfs-tools/modules add the following: atl2 # update-initramfs -k 2.6.32-22-generic -c # exit $ sudo ltsp-update-kernels $ sudo ltsp-update-image --arch i386 Maybe there is a clue in there. I hope that helps. from Michael On 10/03/11 16:28, ttargownik wrote: > Does anyone know the 'proper' way to enable a kernel module within LTSP > 5.2.1? > > Let me elaborate on the problem that has steadfastly put me into a > quasi-comatose state for the past week... > > I have a piece of thinclient hardware (NorhTec MicroClient Jr DX - > eBox-3300MX) that utilises a Vortex86 SoC. > This particular SoC incorporates an "RDC Semiconductor, Inc. R6040 MAC > Controller" for ethernet functionality. > > It seems the default LTSP client image that is built after invoking > 'ltsp_build_client' excludes the required driver for the R6040 ethernet > controller, resulting in a "No interfaces found" error from the initrd when > trying to netboot LTSP. The required driver is available through > menuconfig, under 'Device Drivers--> Network Device Support --> Ethernet > (10 or 100Mbit) --> RDC R6040 Fast Ethernet Adapter Support'. > > I have tried re-building a custom kernel within the CHROOT environment, and > I have tried building the module from source against the appropriate kernel > headers, to no avail. Upon netbooting LTSP with my custom built module, I > have received errors such as "r6040: no symbol version for module_layout" > which seem to indicate that, well, I haven't compiled the module correctly! > I cannot seem to get the 'versionmagic' string to be identical to that of > the rest of the modules already included in the LTSP initrd. > > Hence, back to my first question. What is the proper way to add this module > to my current LTSP initrd? I would imagine the preferred way to do this is > to specify this in a .config file, so that when 'ltsp-build-client' is > called, is knows to include this particular module in the build. I've seen > all manner of things happening in: > /usr/share/ltsp/plugins/ltsp-build-client/ > ...but nothing that seems to allow including a previously-deselected module > in the kernel build process. > > I can't count how many times I've rebuilt the LTSP initrd in the past week, > so please do add your wisdom to this thread! > > Further information: > > I am running LTSP on the following platform: > Linux 2.6.32-24-server #43-Ubuntu SMP Thu Sep 16 16:05:42 UTC 2010 x86_64 > GNU/Linux > > With the following version of LTSP installed: > ii ltsp-server 5.2.1-0ubuntu9 > Basic LTSP server environment > > The currently active LTSP kernel is: > 2.6.32-29-generic > > > Thank you to all who have spared their time to listen to my incoherent > rambling. I hope you can make more sense of it than I can. > > Best regards, > Tomas > > ------------------------------------------------------------------------------ > Colocation vs. Managed Hosting > A question and answer guide to determining the best fit > for your organization - today and in the future. > http://p.sf.net/sfu/internap-sfd2d > _____________________________________________________________________ > 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 > > . > ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _____________________________________________________________________ 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
