On Fri, May 31, 2002 at 11:59:13AM +0200, Sune Rastad Bahn wrote: > 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 had some weird problems between `menu' versus `command line' but that was not related to network. So I think the driver is not at fault but there is indeed something messed up in the "parsing" of the menu. Problem is: is this related to some modification made recently or was it already the case in such cases with previous versions but nobody test them? I have no time _now_ but if nobody gives it a look I will try... later. Hint: would you mind trying the following in the menu: root (nd) kernel /vmlinuz-2.2.20 root=/dev/nfs and tell if segregating the device (root) from the filename works under the menu? Cheers, -- Thierry Laronde (Alceste) <[EMAIL PROTECTED]> Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C _______________________________________________ Bug-grub mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-grub