Tirsdag den 5. december 2006 10:44 skrev Andy Rabagliati: See my 10 cents below...
> Folks, > > A little background .. > > We are keen to stick with dapper for servers, for Long Term Support. > > I installed dapper, and (from dapper) all the listed dependencies for > /edgy/ ltsp-build-client. I then installed edgy ltsp-build-client, > pointed it to an edgy repo, and ran it. > > So, I have a dapper server, and an edgy client. I know there will be > some issues trying to log in, but at the moment I just want ldm to > come up on the client. > > An identical setup on Debian sarge (copy of /opt/ltsp, dhcpd.conf) > worked great. I copied it from the non-working dapper setup. > I just need it to work on dapper. > > On the client, it gets as far as "Running: /scripts/init-bottom" > from the initrd, and then times out - > > nfs: server 192.168.42.1 not responding > > I turned logging on, the server indicates successful mount. > > Dec 5 11:22:28 musselcracker mountd[4045]: authenticated mount request > from owl.aims.ac.za:995 for /opt/ltsp/i386 (/opt/ltsp) > > There are no firewall rules, nothing in hosts.allow/deny. > > Where should I start looking ? > > Cheers, Andy! The wiki helped me out some time ago, I had exactly the same problem. I took the liberty to paste from the wiki: ---------------- begin ------------------------------- nfs warning: server not responding The problem is caused by the 2.6 kernels using a large default blocksize for NFS packets. The 2.6 kernels use 32k blocks, where the older kernels used 8k blocks. What happens is the 32k byte blocks need to be broken down into 1500 byte datagrams. Simple math will tell you that you need a whole lot more 1500 byte datagrams to make up a full 32kbyte block. Sending those datagrams to a 10mbit card takes too long for all of the datagrams to get there, so the NFS client times out before getting all of the fragments. Fortunately, there's an easy fix. You need to pass some options to the client to tell it to use smaller block sizes for NFS. Take a look at KernelOptions for more info passing command line args to the kernel. Solution when using Etherboot You'll need to add the following lines to your dhcpd.conf file. option option-128 code 128 = string; option option-129 code 129 = text; option option-128 e4:45:74:68:00:00; option option-129 "MOPTS=nolock,ro,wsize=2048,rsize=2048"; If you are wondering what the e4:45:74:68:00:00 is, read the KernelOptions page to learn about something called an "Etherboot Signature". Solution when using PXE Robbie had success with append NFSOPTS="-o etx" You'll need to add the options to the pxelinux config file. By default, the config file is /tftpboot/lts/2.4.26-ltsp-3/pxelinux.cfg/default prompt 0 label linux kernel bzImage-2.4.26-ltsp-3 append init=/linuxrc rw root=/dev/ram0 initrd=initrd-2.4.26-ltsp-3.gz MOPTS=nolock,ro,wsize=2048,rsize=2048 ------------------------ end -------------------------------------- As I use PXE, I entered as described. It worked flawlessly in the first go. -- ------------------------------ Med venlig hilsen/Best regards Verner Kjærsgaard ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _____________________________________________________________________ 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
