Kernel (2.4.X series) not doing the initial boot.

[Geert Stappers]

At 17:55 +0200 10/8/01, Stephane Enten wrote:
>On Sat, Oct 06, 2001 at 09:47:20PM +0200, Geert Stappers wrote:
> > At 17:10 +0200 10/6/01, Stephane Enten wrote:
> > >On Sat, Oct 06, 2001 at 04:52:23PM +0200, Stephane Enten wrote:
> > >[...]
> > > > I attach the .config used for the minimalist kernel used.
> > >[...]
> >
> > I'm not completely sure, but go for "FILTER"
> > DHCP relies on it.
> >
> > Please report your results to list ( for the searchable archive )
>
>I re-tested with CONFIG_FILTER enabled, without any results.

Thanks for the report.

The CONFIG_FILTER idea came for a bad encounter I had with dhcpd.
(
$ strings /usr/sbin/dhcpd-2.2.x  | grep -i filter
CONFIG_PACKET=y and CONFIG_FILTER=y
CONFIG_PACKET and CONFIG_FILTER are defined
Can't install packet filter program: %m
policy-filter
$
)

CONFIG_PACKET is set in the .config you sent to the list.

>
>Trying to find out the problem, I enabled IPCONFIG_DEBUG in the
>ipconfig (net/ipv4/ipconfig.c) code, hoping to see some debug
>message, but didn't get one. I did the same with NFSROOT_DEBUG
>(in fs/nfs/nfsroot.c) with the same result.
>
>I start to be in doubt if the ipconfig code is executed at all ...
>
>I'll now examine the remaining things:
> - Trying to force the root= and nfsroot= params (as Chad suggested)
> - Trying with an older kernel (2.4.4 as Jens suggested)
> - Trying a "known to work" 2.2 kernel as Thomas suggested

I'm also clueless.
When bright ideas don't work,
I fall back to simple ideas as checking UTP cables
and having the link LED lit on the repeater.


>
>	Stephane



Kind Regards, Geert Stappers
---------------------
The Future is now, be part of it.