I have been running ltsp 3.0 successfully for a couple months. Unfortunately it seems that I need to build a kernel in order to solve a couple of issues. I have a dlink 530tx+ nic.
I downloaded the 2.4.9 kernel sources from kernel.org and place them into a working directory "/download/kernel". I also downloaded "ltsp_initrd_kit-3.0.1-i386.tgz" into another working directory. I then installed "mknbi-1.2-6" from an rpm. I changed to the top level directory of the kernel source and copied "config.2.4.9-ltsp-5" from the initrd dir to ".config" in the kernel dir. I ran "make dep" and "make bzImage". This created "arch/i386/boot/bzImage". Note these are the only two commands that I used. I did not do a "make modules" and did not think that I need to. I am uncertain of this? I changed to the initrd directory. I modified the lines near the end of the "buildk" script file as follows: prepare_kernel /download/linux 2.4.9-ltsp-5 prepare_kernel /download/linux 2.4.9-ltsp-lpp-5 I executed the buildk script file. It created /tftpboot/lts/vmlinuz-2.4.9-ltsp-5 and vmlinuz-2.4.9-ltsp-lpp-5. I noted that these files were different sizes than the original default kernels, 803840 bytes versus 1054720 bytes. I tried booting but it would not work. The nic supposedly uses an "rtl8139" driver, but there was none to be found. I then added option 128 & 129 to the dhcpd.conf files to try the "via-rhine" driver. I could not locate the driver or directory. For some reason, that I do not understand, paths never work properly for things like modprobe, insmod, etc. I finally went back to the original kernel. This would not load with the option 128 & 129 in the dhcpd.conf file. I removed those 2 lines and tried again. This time it was able to load the kernel but died complaining with the following problems: (EE) Unable to locate/open config file (EE) Error from xf86HandleConfigFile() Fatal Server error: no screens found I tried to modify the kernel Makefile in order to set "EXTRAVERSION = -ltsp-5". I was hoping that this would fix the path problems. It didn't make any difference. At one point in the middle of all this, I thought that the new kernel had booted and so I attempted to build and install the nVidia kernel driver (from tgz sources). I built it in a working directory, but it actually intalled "NVdriver" into the real location for my server kernel. Fortunately I was able to undo this and get the server working again. I don't think this caused any damage to the workstation. At this point, the workstation is not booting into level 5 (only level 3). I am completely stuck. 1. Does anyone has an explanation and solution to getting the workstation running again? 2. Does anyone know what went wrong with building the kernel and have a solution to that? 3. Can anyone explain how these paths work for modprobe, insmod, etc? Thanks, Rob _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp. _____________________________________________________________________ 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.openprojects.net
