This is probably an etherboot issue rather than a grub bug, but nevertheless:
using the D-link card DFE-530ct together with the otulip driver gives the following curious behavior: when booting a kernel: (nd)/vmlinuz-2.2.20 root=/dev/nfs from the grub menu it hangs and oops on a regular basis whereas booting the same kernel from the grub-prompt (with the exact same parameters) reveals no apparent problems. I have compiled grub-0.92 using ./configure --enable-otulip If I use the regular tulip driver instead grub still probe the card but fails to configure the card (bootp doesn't work). If I use a different card (via-rhine based) there is no problem booting the above mentioned kernel. >From the fact that the behavior of the otulip driver depends on the way I use grub, my best guess is that the otulip driver somehow interferes with grub, causing the kernel image to be corrupted when booting from the grub menu. This is just a guess. If someone bother to look into it, I would be very pleased to hear from them. best, Sune Rastad Bahn _______________________________________________ Bug-grub mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-grub
