So, who creates /tftpboot/lts/vmlinuz-2.4.18-ltsp-1 ??? The kernel pakage?
[EMAIL PROTECTED] wrote: > > Hmm, interesting. > > You say that you are using the default kernel that > comes with ltsp_core-3.0.5-i386.tgz. > > The interesting part is there is NO kernel included with > the ltsp_core package. > > Jim. > > On Wed, 28 Aug 2002, Alex Robertson wrote: > > > [EMAIL PROTECTED] wrote: > > > > > > Alex, > > > > > > Which LTSP kernel are you using ? > > > > > > I added the sis900 driver when I build the vmlinuz-2.4.18-ltsp-1 > > > kernel that is in the ltsp_kernel-3.0.4 package. I'm guessing > > > that you are using an older LTSP kernel. > > > > > > Jim McQuillan > > > [EMAIL PROTECTED] > > > > Jim > > > > I'm using the default kernel placed in > > /tftpboot/lts/vmlinuz-2.4.18-ltsp-1 that cames with > > ltsp_core-3.0.5-i386.tgz pakage. I gess this one is newer than that in > > the ltsp_kernel-3.0.4 pakage. > > Anyway, I compiled a new kernel :-) using your config-2.4.18-ltsp-1 file > > as start point. The unique modification i have done is to support sis900 > > and realtek cards (we have a lot of theses cards here) built in the > > kernel. They were supported as modules. > > > > I also tried the vmlinuz-2.4.18-ltsp-1 kernel in the ltsp_kernel-3.0.4 > > pakage > > > > I have always gotten the same error. > > > > Alex Robertson > > > > > > > On Wed, 28 Aug 2002, Alex Robertson wrote: > > > > > > > [EMAIL PROTECTED] wrote: > > > > > > > > > > Alex, > > > > > > > > > > No need to tag the kernel again. Just use the standard > > > > > ltsp kernel and change your root-path > > > > > statement in the /etc/dhcpd.conf file to point to the new > > > > > directory. > > > > > > > > Ok. It worked! But now, while running linuxrc, I get the message: > > > > " > > > > modprobe: sis900 > > > > modprobe: Can't locate module sis900 > > > > > > > > ERROR! Failed to install the NIC driver module .......... > > > > ...... > > > > Kernel panic: Attempted to kill init! > > > > " > > > > > > > > What must i do? I think I must put sis900.o in some directory on the > > > > opt/ltsp/i386 dir. Ok?! > > > > > > > > > If you really want to build your own kernel, then make > > > > > sure you enable devfs in your kernel config, so that you > > > > > don't get that 'Unable to open an initial console' error. > > > > > > > > > > If building your own kernel, you should also have the > > > > > ltsp_initrd_kit, and use the buildk script to set it all up for > > > > > you. > > > > > > > > > > Hope that helps, > > > > > Jim McQuillan > > > > > [EMAIL PROTECTED] > > > > > > > > > > On Mon, 26 Aug 2002, Alex Robertson wrote: > > > > > > > > > > > Here I go again... > > > > > > > > > > > > Let me explain all the situation. > > > > > > > > > > > > I use slackware 8.1 - kernel 2.4.18. (server and workstation) > > > > > > > > > > > > I changed some paths because of disk space. I installed ltsp another > > > > > > directory. DHCPD, exportfs, and others know this new location. AND I > > > > > > also created a sim-link in /opt/tlsp pointing to that new location. > > > > > > > > > > > > I built my own kernel for the workstation. I have built more than 20 > > > > > > different configurations. I have started with .config from a tlsp > > > > > > package. > > > > > > > > > > > > Using mknbi, I passed root path parameter for the kernel. > > > > > > (rootdir=/dev/ram0). Then I got a "Unable to mount root fs on 01:00" > > > > > > error message. > > > > > > I also tried to pass rootdir=/opt/ltsp/i386. Then, it mounted root fs > > > > > > and I got a "unable to open an initial console" warning. I know it's not > > > > > > the right way. > > > > > > > > > > > > But i found on the /mnt directory on the server a ./initrd directory. > > > > > > Its contents seemed to be the root fs to be mounted on the client's ram. > > > > > > there is also a /mnt/initrd/linuxrc file. Then i tried to make this > > > > > > directory to be the root fs. rootdir=/mnt/initrc. It does not work. > > > > > > PROPERLY! > > > > > > > > > > > > If I do not append an init command, i get a busybox error. > > > > > > But if I append a init=/linuxrc command, the script is run, /proc is > > > > > > mounted. But when it tries to install sis900 driver it stops. => > > > > > > > > > > > > ERROR! Failed to install the NIC driver module .......... > > > > > > ...... > > > > > > Kernel panic: Attempted to kill init! > > > > > > > > > > > > I know it's not the right way, but it almost worked. :-) > > > > > > > > > > > > > > > > > > The question is: > > > > > > What can i do to stop this kind of error? > > > > > > May i comment lines that loads the modules, once i have all built in the > > > > > > kernel? > > > > > > > > > > > > thanks in advance. > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > > > -- > > > > > > -- -- Alex G Robertson NOC - Microlink ------------------------------------------------------- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim _____________________________________________________________________ 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
