Hi Without lots of work you can't do this.
The 2.6 kernels use a differant set of mod utils. You would need to add the new mod-utils to the lbe, build a new lbe and then use. Probably a simple error, but I have not been able to do this. My modules won't load. So until I solve the problem, or some else does, your only chance is to try a monolithic kernel James > I am trying to recompile the 2.6.7 kernel for use with LTSP. I have everything > working fine with the kernel version that comes with LTSP 4.1. I gotta say together > with the atspadmin and ltspcfg program, it is quite a package. I have been very > happy... > > Any way, I want to be able to compile the new kernel, so I went through these steps > (my client and server are both the same type of IBM machines): > > 1.) I compiled a kernel for the server to test out my skills with make xconfig. > 2.) Once I got the 2.6.7 kernel to boot on the server, I figured it was just a > matter of tagging it and adding it to my dhcp.conf file so the client could load > it... > 3.) I ran buildk to tag the kernel and create the initrd. > 4.) I copied the /lib/modules/2.6.7 dir to /opt/ltsp/i386/lib/modules dir > 5.) I copied the new tagged kernel (bzImage-2.6.7, vmlinux-2.6.7, and the > initrd-2.6.7.gz file) to a newly made /tftboot/lts/2.6.7 dir > 6.) I copied the pxelinux.0 and pxelinux.cfg file and dir to the new > /tftboot/lts/2.6.7 dir > 7.) I changed the default file (I'm using pxe, which works like a charm so far) to > read: > > prompt=0 > label linux > kernel bzImage-2.6.7 > append init=/linuxrc/ rw root=/dev/ram0 initrd-2.6.7.gz > > 8.) I modified my dhcp.conf file to point to location of my new kernel with the line: > > filename "/lts/2.6.7/pxelinux.0" > > 9.) Now I boot my client and everything looks great with the kernel loading and PXE > until it tries to load my NIC module (e100): > > Freeing unused kernel memory: 164K free > ===================================================================== > Running /linuxrc > Mounting /proc > linuxrc: Installing e100 driver > modprobe e100 > modprobe: QM_MODULES: %m > > modprobe: QM_MODULES: %m > > modprobe: Can't locate module e100 > > ERROR! Failed to install the NIC driver module! > This could be caused by the wrong module for your particular > network interface card. Double check the 'option-129' entry > in your /etc/dhcp.conf file. > > Kernel panic: Attempted to kill init! > > > > I desperately need your help. I tried recompiling the kernel with the NIC module > compiled into the kernel and not a module. I also tried to copy the modules for NIC > (e100) from the old kernel modules dir to the new 2.6.7 modules dir. I looked at the > modules dirs on the server and it seems that in 2.6.7 there is an e100.ko file but > there is no e100 folder like there was in the LTSP kernel's module dir. > > Can someone please provide some insight? My project requires that I use the 2.6.7 > kernel. I recall that the LTSP master (jam) replied to somoene that he would not > change to the 2.6 kernel until version 2.6.7 because he just thought it would be > stable by then. I know he is a busy guy doing great work, so I would like to get > this running myself. Thanks for reading this... ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _____________________________________________________________________ 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
