Date: Wed, 24 Nov 2004 13:27:37 +0100 From: Erik Norgaard <norgaard@locolomo.org> To: questions@freebsd.org Subject: Strange problem with pxeboot Message-ID: <41A47E39.7080300@locolomo.org>
next in thread | raw e-mail | index | archive | help
Hi, Sorry - I have no more descriptive subject because this is really strange: I have set up a server to serve clients booting with pxeboot and fetching kernel and a memory disk root file system with tftp. So far so good. What is strange is this: 1) If the local harddrive (which contains an old FreeBSD 4.9) is installed, the client correctly configures the ethernet card (vr0) and tries to mount a root file system using NFS - but the whole idea was to avoid using NFS at all. If I leave the root-path unset in the dhcpd.conf the client will try to mount the root file system from <next-server>:/pxeroot 2) If I remove the harddrive, then it mounts the memory file system as root file system and launches sysinstall (which is what I really want) - however, it fails to initialize the network card, and there is (obviously) no disk to install on. the ethernet driver is compiled into the kernel - no modules need to be loaded, these are my loader files: loader.rc: include /boot/loader.4th start loader.conf: init_path="/sbin/init:/stand/sysinstall" rootfs_load="YES" rootfs_name="/boot/mfsroot" rootfs_type="mfs_root" autoboot_delay=5 boot/ on tftp server: defaults kernel loader.gz pxeboot device.hints loader.4th loader.rc support.4th frames.4th loader.conf mfsroot Any hints would be greatly appreciated! Thanks, Erik -- Ph: +34.666334818 web: www.locolomo.org S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt Subject ID: A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9 Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41A47E39.7080300>