Yahooo!
I've got a working LTSP kernel for the TUSI-M Motherboard
with the new Sis630ET chipset.
Many thanks to Jim McQuillan who guided me through the
debugging process.
For those of you interested, the process is:
1. download the 2.4.18 kernel from ftp.kernel.org
The RPM will install this into /usr/src/linux
rename this directory to /usr/src/linux2.4.18
All you want from this is the new sis900.c and sis900.h
files.
2 Download the 2.4.9 kernel source from the same location.
Find the sis900 files in this tree and replace them with
those from the .18 kernel.
3. Dowmload the initrd_kit. (this is a tar.gz file). You
can put it anywhere - I put it in /opt/ltsp.
Expode the tar file: tar xvfz initrd_kit-3.0.3-i386.tgz
3. Follow Jim's instructions from the LTSP docs
Edit the Makefile. I made EXTRAVERSION = ltsp-6et
copy the file config-2.4.9-ltsp-6 to .config in the
/usr/src/linux-2.4.9 directory
Then do the nakes as per the docs:
make xconfig
nake dep
make bzImage
make modules
make modules_install
There will be errors compiling sis900.c
Respond to these (only 2 lines need changing)
Email me for details if you need to.
Edit the sis900.c file then cd to the top level
directory /usr/src/linux-2.4.9/ to run make again.
4. Now go into your initrd directory and run the
buildk script:
./buildk
This will prompt you with questions:
answer 1600 (instead of 1300 ) blocks
answer 140 (instead of 120) inodes
Watch carefully for error messages (out of space etc)
5. At this point you should now have a RAM disk image which
contains your new sis900.o file. This image will have
been tacked onto the bzImage kernel and will have the
name: vmlinuz-2.4.9-ltsp-6et. Copy this file into
/tftpboot/ltsp/
6. Do the right configuration things.
edit filename = vmlinuz-2.4.9-ltsp-6et
in /etc/dhcpd.conf
Then try it out!
A really useful trick Jim taught me here was to
activate (uncomment ) the option-128 and option-129
entries in /etc/dhcpd.conf - option-129 = "INITRD_DBG=1"
This will cause the linuxrc script to stop before
modprobing the sis900 and give you a shell pronpt.
You can mow mosy around the workstation and try the
modprobe and insmod commands by hand. Setting the DBG to
other numbers causes the escape to the shell to happen
at later phases in the startup process.
Most of the troubles I had had were due to an empty
modules.dep file. This had been due to running out
of space and/or inodes in the RAM disk.
John O'Gorman
_____________________________________________________________________
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
