Syslinux - Mar 2003 - pxelinux kernel 2.4.20 nfs server is not asked

intel etherexpress pro 100 nics at my lan, server with tftp, nfsserver
and pxelinux running for about half a year at my lan.

Hi,

When I use a kernel v.2.4.20 the pxe boot loads the pxefiles, kernel and
then stops asking for files from the server and complains about a
"Root-NFS: No NFS server available, giving up." and messages about to
insert a disk...
... the same .config used with kernelsources 2.4.19 boots fine without
problems (getting root fs over nfs).

I have searched about the origin, weather it is the kernel 2.4.20 or the
syslinux version I use, but couldn't solve it.

Can you provide me with information concerning this problem?

cheers,
Sascha
-- 
GNU Linux | The chief cause of problems is solutions.  
2.4.20-xf | 
on a      |  
i586      |

Hi,

Sascha W?stemann <sascha at killerhippy.de> schrieb am 27.03.03
22:46:42:
> intel etherexpress pro 100 nics at my lan, server with tftp, nfsserver
> and pxelinux running for about half a year at my lan.
> 
> When I use a kernel v.2.4.20 the pxe boot loads the pxefiles, kernel and
> then stops asking for files from the server and complains about a
> "Root-NFS: No NFS server available, giving up." and messages
about to
> insert a disk...
> ... the same .config used with kernelsources 2.4.19 boots fine without
> problems (getting root fs over nfs).
> 
> I have searched about the origin, weather it is the kernel 2.4.20 or the
> syslinux version I use, but couldn't solve it.
Do you use the kernel-based or the userspace nfs server? I've seen the knfsd
fail on a recent debian installation, but the userspace nfsd works without
problem.

Did the client try the correct IP address (i.e.did you see any packets coming
from
the client accessing the NFS server?). Did the client get an IP address,
especially
the kernel?

BTW, this has not much to do with pxelinux ...

Regards,

Josef


______________________________________________________________________________
Mit der Gruppen-SMS von WEB.DE FreeMail erreichen Sie mit einem Klick 
alle Freunde gleichzeitig! http://freemail.web.de/features/?mc=021180

Hi,

Sascha W?stemann <sascha at killerhippy.de> schrieb am 28.03.03
11:28:17:
> On Fri, Mar 28, 2003 at 11:14:43AM +0100 or thereabouts, Josef Siemes
wrote:
> I use the kernel-based nfs server which worked perfectly prior to my
> current problem.
> The client is not contacting the server for nfs requests at all,
> although the client shows the correct IP-addresses data when recieving it
> via tftp. I probed that with watching the packets using tcpdump on
> server side. -  So it makes no difference using userland nfs, right?
The IP address used within tftp is not obtained the same way the kernel obtains
its IP address (it may even be a different address!). So how do you give the IP 
address to the kernel? With ipappend, kernel level IP config, initrd & dhcpd
or else? I think the client"s kernel somehow didn't get an IP address
for the interface,
and thus can't contact the NFS server.

Regards,

Josef

______________________________________________________________________________
Mit der Gruppen-SMS von WEB.DE FreeMail erreichen Sie mit einem Klick 
alle Freunde gleichzeitig! http://freemail.web.de/features/?mc=021180

Hi,

please also cc: the list. Maybe someone else has a better idea, or even someone
else
has your problem and waits for an answer.

Sascha W?stemann <sascha at killerhippy.de> schrieb am 28.03.03
12:25:56:
> 
> On Fri, Mar 28, 2003 at 12:01:58PM +0100 or thereabouts, Josef Siemes
wrote:
> > The IP address used within tftp is not obtained the same way the
kernel obtains
> > its IP address (it may even be a different address!). So how do you
give the IP
> > address to the kernel? With ipappend, kernel level IP config, initrd
& dhcpd
> > or else? I think the client"s kernel somehow didn't get an IP
address for the interface,
> > and thus can't contact the NFS server.
> > 
> 
> Here's an excerpt of my kernel .config answering your questions.
> 
> ---schnipp---
> #
> # Block devices
> #
> CONFIG_BLK_DEV_RAM=y
> CONFIG_BLK_DEV_RAM_SIZE=4096
> CONFIG_BLK_DEV_INITRD=y
> 
> #
> # Networking options
> #
> CONFIG_IP_PNP=y
> CONFIG_IP_PNP_DHCP=y
> # CONFIG_IP_PNP_BOOTP is not set
> # CONFIG_IP_PNP_RARP is not set
> # CONFIG_NET_IPIP is not set
> 
> #
> # Network device support
> #
> CONFIG_NETDEVICES=y
> CONFIG_NET_ETHERNET=y
> CONFIG_NET_PCI=y
> CONFIG_EEPRO100=y
> 
> #
> # Network File Systems
> #
> CONFIG_NFS_FS=y
> CONFIG_NFS_V3=y
> CONFIG_ROOT_NFS=y
> CONFIG_NFSD=y
> CONFIG_NFSD_V3=y
> # CONFIG_NFSD_TCP is not set
> ---schnapp---
> 
> The nfs-server's ip address is given through the
> pxelinux.cfg/<HEXNUMBER> config file, which works with kernels prior
> v.2.4.20, see here:
> 
> ---schnipp---
> DEFAULT kernel
> APPEND root=/dev/nfs
nfsroot=172.16.0.1:/mnt/hdc2,rsize=8192,wsize=8192,timeo=14
ip=172.16.0.12:172.16.0.1:172.16.0.1:255.255.255.0:bootbaby:eth0:'bootp'
rw panic=10
> ---schnapp---
> BTW: setting CONFIG_IP_PNP_BOOTP makes no difference.
So you give the address directly via "ip=". Why do you give the
"bootp"-parameter
at the end of "ip="? It is supposed to be "ip=n.n.n.n:[...]"
or 'ip=bootp' or 'ip=dhcp'.
Maybe that confuses your kernel - I haven't tried that out. Look into the
kernel's
Documentaton tree for additional infos about the "ip="-parameter.

BTW: If you have the IP address already in the kernel parameter, you don't
need
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
this is only used for kernel level dhcp/bootp/rarp support.

Regards,

Josef

______________________________________________________________________________
Ihre eigene Internet-Seite! Kinderleicht f?r Anfaenger und Profis
Kostenlos testen unter http://mypage.web.de/?mc=021110