http://qa.mandrakesoft.com/show_bug.cgi?id=3003
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2003-03-10 16:50 -------
Try mkinitrd-net-1.10-3mdk, just uploaded. Should be able to deal with nfs
integrated or as a module.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: RESOLVED
creation_date:
description:
How to reproduce the bug:
Launch drakTermServ
Click on Net Boot Images
Select a card under current kernel (vmlinuz-2.4.21-0.11mdk)
Click on Build Single NIC
It seems to work, but this is the console output:
Building NBIs for module set 3c509
modprobe: Can't locate module nfs
Cannot find any modules matching nfs
mkinitrd-net --nolink --kernel 2.4.21-0.11mdk -q 3c509 failed: No such file or
directory
Since I installed 9.1-RC2 as an upgrade from 9.0, it seems that mkinitrd-net
expects nfs to be loaded as a module (this was true in 9.0), instead of as part
of the kernel, which is the way 9.1 is configured.
Terminal Server works perfect otherwise; that is, I can boot from a remote PC
using an existing NBI (left over from last version, with kernel 2.4.19-16) and
login to a gnome session through gdm or xdm; dhcp, cluster nfs and tftp work
fine, and I can even create etherboot floppies.
But creating NBIs doesn't work.
Some versions of (possibly related) packages:
mkinitrd-3.1.6-37mdk
mkinitrd-net-1.10-2mdk
nfs-utils-clients-1.0.1-1mdk
clusternfs-3.0.rc2-7mdk
kernel-source-2.4.21-0.11mdk
