after ip=autoconf WAS: Kernel (2.4.X series) not doing the initial boot.
amurphy at nbcs.rutgers.edu
Fri Oct 12 21:04:46 CEST 2001
I have had some luck passing the following parameters to the kernel:
the root= forces the kernel to use wait forever for the network to be
configured and the ip= forces a dhcp request, rather than letting the
kernel decide what to request.
I have had trouble with incorrect information via RARP kernel config but
that may have been due to other problems here. The DHCP usually takes a
few minutes to actually recognize the response sent from the server. I
have snooped my boot sequence and there are some unexplainable delays
between when the server sends a DHCP assignment and when the client
A separate problem that I am having is that when i use only the above two
kernel switches, I get my nfsroot mounted read only! I have had some
success with adding the nfsroot= switch but I am looking into ways around
Student Systems Programmer
Open Systems Support
On Thu, 11 Oct 2001, Stephane Enten wrote:
> > >However, the DHCP code still did not accept the DHCPOFFER.
> > >I explored the net/ipv4/ipconfig.c again and found that there is some
> > >code to check if ic_myaddr equals INADDR_NONE.
> > >
> > >I found that my ic_myaddr was set at 22.214.171.124 at the DHCP request time,
> > >don't know why.
> > >
> > >So I added "ip=255.255.255.255:autoconf" in my kernel config, then the
> > >ic_myaddr was at INADDR_NONE (255.255.255.255) and the kernel was happy,
> > >did the NFS mount and now I can work on tweaking the installation part :)
More information about the linux-fai