Don't worry. But i've already done that. This kernel was the first one I tried. LTSP-kernel pakage installs /tftpboot/lts/vmlinuz-2.4.18-ltsp-1. (The only difference is that i use .tgz pakages).I copied it to /tftpboot/vmlinuz. Jim and James have told me to do so two weeks ago.
Thanks anyway. :-) Alex Robertson Shane Kennedy wrote: > > Sorry, yes, and it's the ltsp-kernel rpm. Try that. > > Shane > > Alex Robertson wrote: > > :-( > > > > I got a "not a valid image" error message. > > > > Didn't you mean vmlinuz-???? instead of mbImage-???? > > > > > > Shane Kennedy wrote: > > > >>mknbi is ONLY if you build your own kernel. Just call the kernel from > >>the dhcpd.conf. Remove, or rename the old one, to be certain it is > >>loading the right one. > >> > >>Good luck. > >> > >>Alex Robertson wrote: > >> > >>>Ok. I've got them. And now? Must i call bzimage from dhcpd.conf? > >>>Or make 'mknbi-linux'? And witch parameters to use? > >>> > >>> > >>>Shane Kennedy wrote: > >>> > >>> > >>>>They SHOULD have been installed by ltsp-core, but here they are anyhow. > >>>>Check how you are displaying your incomming mail. If you don't see > >>>>attachments, you are probably displaying them 'in-line'.....Not much use > >>>>for binaries. > >>>> > >>>>Shane > >>>> > >>>>Alex Robertson wrote: > >>>> > >>>> > >>>>>And what must i do? > >>>>> > >>>>>my kernel is 2.4.18 > >>>>> > >>>>> > >>>>>Shane Kennedy wrote: > >>>>> > >>>>> > >>>>> > >>>>>>The stock ltsp kernel needs the initrd. > >>>>>>bzImage-2.4.9-ltsp-6 > >>>>>>initrd-2.4.9-ltsp-6.gz > >>>>>>the kerner loads, and expands. Then it loads and expands the > >>>>>>initrd(initial RamDisk) into /dev/ram0, which is its (temporary) > >>>>>>filesystem. This contains the f/s, and, vitally, a bunch of modules the > >>>>>>kernel needs to use the NIC (amongst others). It then mounts the server > >>>>>>s exported f/s, and swaps the ram0 for its nex, and permenant f/s. > >>>>>>If it doesn't have the initrd, it can't use the NIC for anything other > >>>>>>that tftp transfers. i.i. NO NFS. > >>>>>> > >>>>>>Shane > >>>>>> > >>>>>>Alex Robertson wrote: > >>>>>> > >>>>>> > >>>>>> > >>>>>>>shane, > >>>>>>> > >>>>>>>I'm using the default kernel and initrd srcipt (the ones that comes with > >>>>>>>ltsp packages) I have only changed its name. ( mv > >>>>>>>/tftpboot/lts/vmlinuz-ltsp???? /tftpboot/vmlinuz > >>>>>>>But initrd (linuxrc) isn't in /tftpboot dir. Is it suposed to be there? > >>>>>>> > >>>>>>>I found /mnt/initrd dir. And the linuxrc script in it. > >>>>>>>I also found lines in /tftpboot/vmlinuz (vi /tftpboot/vmlinuz) witch > >>>>>>>tells kernel to mount /dev/ram0 as rootdir and /linuxrc as innitial > >>>>>>>script (rootdir=/dev/ram0 init=/linuxrc) > >>>>>>> > >>>>>>> > >>>>>>>And about the NIC's, the answer is: No. I have 3. :-) > >>>>>>> > >>>>>>>Alex Robertson > >>>>>>> > >>>>>>>Shane Kennedy wrote: > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>>>It looks like the nbi kernel isn't making any mount requests. > >>>>>>>>What lernel, and initrd do you have in the tftpboot dir ?. > >>>>>>>>Do you have 2 NIC's in the server ?. Just for confirmation of messages > >>>>>>>>below. > >>>>>>>> > >>>>>>>>Shane > >>>>>>>>Alex Robertson wrote: > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>>>Shane, > >>>>>>>>> > >>>>>>>>>That's what i get in /var/log/messages when I try to boot my > >>>>>>>>>workstation. > >>>>>>>>>.... > >>>>>>>>>Sep 9 11:13:36 cafuba dhcpd: DHCPDISCOVER from 00:d0:10:fa:75:8a via > >>>>>>>>>eth1 > >>>>>>>>>Sep 9 11:13:36 cafuba dhcpd: DHCPOFFER on 192.168.0.1 to > >>>>>>>>>00:d0:10:fa:75:8a via eth1 > >>>>>>>>>Sep 9 11:13:36 cafuba dhcpd: DHCPREQUEST for 192.168.0.1 > >>>>>>>>>(192.168.0.254) from 00:d0:10:fa:75:8a via eth1 > >>>>>>>>>Sep 9 11:13:36 cafuba dhcpd: DHCPACK on 192.168.0.1 to > >>>>>>>>>00:d0:10:fa:75:8a via eth1 > >>>>>>>>>Sep 9 11:13:36 cafuba in.tftpd[3856]: connect from 192.168.0.1 > >>>>>>>>>Sep 9 11:13:36 cafuba tftpd[3857]: tftpd: trying to get file: vmlinuz > >>>>>>>>>Sep 9 11:13:36 cafuba tftpd[3857]: tftpd: serving file from /tftpboot > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>>Shane Kennedy wrote: > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>>>Have a look at /var/log/messages to see if the server is receiving nfs > >>>>>>>>>>requests. > >>>>>>>>>> > >>>>>>>>>>Alex Robertson wrote: > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>>>Shane, > >>>>>>>>>>> > >>>>>>>>>>>nfsd is running... > >>>>>>>>>>> > >>>>>>>>>>>$ ps ax | grep nfs > >>>>>>>>>>>102 ? SW 0:00 [nfsd] > >>>>>>>>>>>103 ? SW 0:00 [nfsd] > >>>>>>>>>>>106 ? SW 0:00 [nfsd] > >>>>>>>>>>>107 ? SW 0:00 [nfsd] > >>>>>>>>>>>108 ? SW 0:00 [nfsd] > >>>>>>>>>>>109 ? SW 0:00 [nfsd] > >>>>>>>>>>>110 ? SW 0:00 [nfsd] > >>>>>>>>>>>111 ? SW 0:00 [nfsd] > >>>>>>>>>>>4850 pts/0 S 0:00 grep nfs > >>>>>>>>>>>--------------- > >>>>>>>>>>>cat etc/exports (without comments) > >>>>>>>>>>> > >>>>>>>>>>>/opt/ltsp/i386 > >>>>>>>>>>>192.168.0.0/255.255.255.0(ro,no_root_squash) > >>>>>>>>>>>/var/opt/ltsp/swapfiles > >>>>>>>>>>>192.168.0.0/255.255.255.0(rw,no_root_squash) > >>>>>>>>>>># > >>>>>>>>>>>/home 192.168.0.0/255.255.255.0(rw,no_root_squash) > >>>>>>>>>>> > >>>>>>>>>>>I have rebooted sever. > >>>>>>>>>>>-------------- > >>>>>>>>>>>cat /etc/inittab > >>>>>>>>>>> > >>>>>>>>>>>... > >>>>>>>>>>># 4 = X11 with KDM/GDM/XDM (session managers) > >>>>>>>>>>># 5 = unused (but configured the same as runlevel 3) > >>>>>>>>>>># 6 = reboot > >>>>>>>>>>> > >>>>>>>>>>># Default runlevel. (Do not set to 0 or 6) > >>>>>>>>>>>id:5:initdefault: > >>>>>>>>>>> > >>>>>>>>>>>... > >>>>>>>>>>> > >>>>>>>>>>>Alex > >>>>>>>>>>> > >>>>>>>>>>>Shane Kennedy wrote: > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>>>Check your 'exports' file, and that nfs is running. > >>>>>>>>>>>>You DO need to reboot the server to activate the changed service list. > >>>>>>>>>>>>You also need the server to start in RL5 to use all the defaults, > >>>>>>>>>>>>otherwise, you need to set up rc3.d with extra services (dhcpd, and nfs). > >>>>>>>>>>>> > >>>>>>>>>>>>Shane > >>>>>>>>>>>> > >>>>>>>>>>>>Alex Robertson wrote: > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>>>>Jim / James, > >>>>>>>>>>>>> > >>>>>>>>>>>>>I have folowed James' directions and advice. I have Read the Full Manual > >>>>>>>>>>>>>and folowed all the instructions. > >>>>>>>>>>>>>Paths are default. No links to anywhere. I'm using the default kernel > >>>>>>>>>>>>>that comes with your kernel pakage (not core pakage like I said before). > >>>>>>>>>>>>>I did not use mknbi at any time.... > >>>>>>>>>>>>> > >>>>>>>>>>>>>But I still have a problem. I get a kernel panic message: > >>>>>>>>>>>>> > >>>>>>>>>>>>>"Kernel Panic: VFS: Unable to mount root fs on 01:00" > >>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>>>I don't know if it will help, but few lines before this message, there > >>>>>>>>>>>>>is a line telling ramdisk is ok: > >>>>>>>>>>>>> > >>>>>>>>>>>>>"RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize" > >>>>>>>>>>>>> > >>>>>>>>>>>>>What can you tell me now? > >>>>>>>>>>>>> > >>>>>>>>>>>>>Thanks. And sorry if I am too bore. :-) > >>>>>>>>>>>>> > >>>>>>>>>>>> > >>>> ------------------------------------------------------------------------ > >>>> Name: bzImage-2.4.9-ltsp-6 > >>>> bzImage-2.4.9-ltsp-6 Type: unspecified type (application/octet-stream) > >>>> Encoding: base64 > >>>> > >>>> Name: initrd-2.4.9-ltsp-6.gz > >>>> initrd-2.4.9-ltsp-6.gz Type: application/x-gzip > >>>> Encoding: base64 > >>> > >>> > > -- Alex G Robertson NOC - Microlink ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _____________________________________________________________________ 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
