Installing fdrom tftp to nfs and booting from nfs fails
Hi.
I installed a multia via bootp and tfptboot.img. Everything worked
fine up to "Installing Kernel...".
It downloaded the rescue.bin and drivers.tgz via http and placed them
in /target/tmp/ (which is on nfs). Because it can't loopback from nfs,
the installer seems to copy the file to a ramdisk and tries to mount
that, which fails.
I tried to have the rescue.bin on a ramdisk and to installed from a
mounted filesystem, same problem.
I also tried changing /dev/fd1 to a ramdisk and dd'ing rescue.bin
there. I could mount that fine, but the install couldn't and after the
instalöler tried I couldn't anymore. It seems to break the image on
the way while trying to mount it.
So installing the rescue disk seems pretty broken.
Then I just copied the kernel by hand and extracted the drivers by
hand and went on installing base, which worked fine again.
But how do I boot the system now? I tried setting "root=/dev/nfs
nfsroot=ip:path" and booting with the tftpboot.img, which just starts
the installation again. I tried using a kernel as tfptboot.img, which
fails to start at all (I had a look at how the boot-floppies create a
kernel and saw that they tweaked it to use bootp.c instead of
boot.c). Then I tried to change the boot flags in the tftpboot.img,
which got cut of after 16 characters.
So how can I get the Alpha to boot without compiling a new
kernel. There should be a tftp bootable kernel in 2.2r1 for this
case. Any voluntier to change the boot-floppy package?
Now I have to build a kernel at home and upload that to the tftp
server or build one after chroot to the installed system. Pretty sad.
May the Source be with you.
Goswin
PS: I want to use the multia with the big, new, shiny, realy flat 24"
Monitor and all I can do is run dbootstrap. :(
Reply to: