Bug#373587: fai-nfsroot: RPC call returned error 101 on v20z

2006-06-15 Thread Thomas Lange
IMO you can enter the network card BIOS, and disable the PXE booting. Currently I do not know how to enter it (ecom uses atl-ctrl-b, intel uses ctrl-s). THere you should may select boot from local disk first. Maybe this disables the MBA (or PXE) bootig from this NIC. So it should be possible to

Bug#373587: fai-nfsroot: RPC call returned error 101 on v20z

2006-06-14 Thread Enrique de la Torre
Package: fai-nfsroot Version: 2.10.2 Severity: grave Justification: renders package unusable Hi all, I'm trying to install a v20z beowulf cluster using FAI. Just made two changes to make fai-setup work: 1. add APT::Cache-Limit 141943904; to apt.org. I'm using testing and cant find one mirror

Bug#373587: fai-nfsroot: RPC call returned error 101 on v20z

2006-06-14 Thread Thomas Lange
To see which network card is used by the second dhcp call, please edit the lib/get-boot-info script in your nfsroot. Locate the line: dhclient -lf /dev/null -cf /etc/dhcp3/dhclient-fai.conf -sf /etc/dhcp3/dhclient-fai-script $netdevices $bootlog 2 $LOGDIR/dhclient.log and remove the

Bug#373587: fai-nfsroot: RPC call returned error 101 on v20z

2006-06-14 Thread Thomas Lange
Maybe this helps: http://www.science.uva.nl/research/air/wiki/LogicalInterfaceNames Try ether=0,0,eth0 (or netdev= which is the same) as kernel parameter (you can give it with fai-chboot). You have to force the kernel not to activate the oTher NIC, which is not defined in dhcpd.conf. The

Bug#373587: fai-nfsroot: RPC call returned error 101 on v20z

2006-06-14 Thread Enrique de la Torre Gordaliza
El Miércoles, 14 de Junio de 2006 15:32, Thomas Lange escribió: searching the link at www.science.uva.nl... [...] Based on the physical location in the computer Warning: This only works if the driver is built into the kernel, not as a loadable module. [...] Is tg3 built into kernel on