hi folks
I've got a PXE booting machine setup to boot to my FC2 LTSP4.1 newly installed server, and it boots fine.
But another machine, a 486, boots, loads the system and proceeds up to "Doing pivot_root" then stops telling us that "the NFS server is not responding. Still trying..." It turns off (APM in BIOS or something) after an hour approx.
In the /var/log/messages the two nfs event entries for the two machines are identical (not the ws name of course): "ws105.ltsp rpc.mountd authenticated for /opt xxxx" (don't remember exactly, I can get the exact text if needed)
Both these machines worked on the RH9 LTSP3.0 server. Any ideas why the 486 won't boot? (Amount of RAM in the 486 is only 27M, but there is no room for more)
messages:
Mar 20 10:36:17 pastel dhcpd: DHCPACK on 192.168.0.109 to 00:80:13:15:a2:76 via eth0
Mar 20 10:36:18 pastel rpc.mountd: authenticated mount request from ws109.ltsp:6 56 for /opt/ltsp/i386 (/opt/ltsp)
(Then it's saying "server not responding, still trying..")
Mar 20 10:39:50 pastel dhcpd: DHCPDISCOVER[...
...] DHCPACK on 192.168.0.105 to 00:06:29:d3:1a:5c via eth0
Mar 20 10:40:03 pastel rpc.mountd: authenticated mount request from ws105.ltsp:6 57 for /opt/ltsp/i386 (/opt/ltsp)
Mar 20 10:40:15 ws105.ltsp syslogd started: BusyBox v0.60.4 (2004.07.12-19:22+00 00)
Mar 20 10:41:19 ws105.ltsp init: Entering runlevel: 5
The ws109 is bad guy. ws105 is good guy.
Arno
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _____________________________________________________________________ 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
