On Fri, Oct 12, 2001 at 03:04:46PM -0400, AUSTIN MURPHY wrote:
>
> I have had some luck passing the following parameters to the kernel:
>
> root=/dev/nfs ip=dhcp
>
> the root= forces the kernel to use wait forever for the network to be
> configured and the ip= forces a dhcp request, rath
On Thu, Oct 11, 2001 at 06:01:38PM +0200, Geert Stappers wrote:
> At 17:00 +0200 10/11/01, Stephane Enten wrote:
> >On Wed, Oct 10, 2001 at 03:32:03PM +0200, Geert Stappers wrote:
> snip
> > >
> > > I suggest you append an other parameter.
> > > Such as "ether=9,0,eth0" which means eth0 at
On Wed, Oct 10, 2001 at 03:32:03PM +0200, Geert Stappers wrote:
> At 23:19 +0200 10/9/01, Stephane Enten wrote:
> snip
> >
> >Regarding the tests-of-the-day, I found something I'd call a bug:
> >in my kernels (2.4.10 and 2.4.9), if you just put the nfsroot= kernel
> >parameter in your "appen
On Tue, Oct 09, 2001 at 12:12:49PM +0200, Thomas Lange wrote:
> Is the computer connected to a switch ? There were problems when
> connected to a Cisco switch, because packets from the computer did not
> pass the switch directly. I think it was a 2.2.18 kernel when I had
> this problem but in
Is the computer connected to a switch ? There were problems when
connected to a Cisco switch, because packets from the computer did not
pass the switch directly. I think it was a 2.2.18 kernel when I had
this problem but in 2.2.19 the parameters were changes so this problem
disappeared.
Try incr
> On Mon, 8 Oct 2001 19:16:08 +0200 (MET DST), Jens Ruehmkorf
><[EMAIL PROTECTED]> said:
> What about a compromise: put all relevant log- and config files
> (dhcpd.conf etc.) on a webpage and let an email point to that. I
> think the problem itself is interesting enough to most o
On Mon, Oct 08, 2001 at 07:53:45PM +0200, Geert Stappers wrote:
> At 17:55 +0200 10/8/01, Stephane Enten wrote:
> >
> >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.
> (
> $ st
On Mon, Oct 08, 2001 at 07:16:08PM +0200, Jens Ruehmkorf wrote:
> > Do not mail a kernel config file to the mailling list, because it's
> > big and uninteresting to most of the list subscribers.
>
> What about a compromise: put all relevant log- and config files
> (dhcpd.conf etc.) on a webp
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 kern
> Do not mail a kernel config file to the mailling list, because it's
> big and uninteresting to most of the list subscribers.
What about a compromise: put all relevant log- and config files
(dhcpd.conf etc.) on a webpage and let an email point to that. I think the
problem itself is interesting e
On Mon, Oct 08, 2001 at 01:03:18PM +0200, Thomas Lange wrote:
> > On Fri, 5 Oct 2001 18:53:10 +0200, Stephane Enten <[EMAIL PROTECTED]> said:
>
> Do you really need the 2.4.X kernel during installation ? Try the
> 2.2.19 version during installation and install a 2.4 Kernel to the
> insta
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,
Do remember to check the actual boot time parameters. Try the following if
you're having problems with DHCP not successfully specifying the nfsroot.
append="root=nfs nfsroot=IPADDR_OF_NFSROOT_SERVER"
Yes, it's not automatic, but at least you'll be able to boot and install.
--
Chad C. Wa
> On Fri, 5 Oct 2001 18:53:10 +0200, Stephane Enten <[EMAIL PROTECTED]> said:
Do you really need the 2.4.X kernel during installation ? Try the
2.2.19 version during installation and install a 2.4 Kernel to the
install clients. You can also send a detailed log of the error
messages and the ke
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,
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
On Sat, Oct 06, 2001 at 04:52:23PM +0200, Stephane Enten wrote:
[...]
> I attach the .config used for the minimalist kernel used.
[...]
Obviously it would be more usefull if I actually attach the file.
Sorry for the double-mail :)
Stephane
#
# Automatically generated by make menuconf
On Sat, Oct 06, 2001 at 12:38:32AM +0200, Jens Ruehmkorf wrote:
> Hi Stephane, hi all!
Hi!
> > However, when booting the client machine with this floppy,
> > "nothing happens", sniffing the network (with tcpdump
> > analyzing broadcasts and also packets from/to the MAC
> > address of the in
Hi Stephane, hi all!
> However, when booting the client machine with this floppy,
> "nothing happens", sniffing the network (with tcpdump
> analyzing broadcasts and also packets from/to the MAC
> address of the interface) showed that the kernel isn't
> even doing the initial BOOTP/DHCP request.
I've been reading everything I found on that but it seems
to be an unusual problem since nobody faced it.
We have a clean FAI installation, everything worked as
expected during the installation process and we ended
up with a custom boot floppy with a kernel of ours
(DHCP, NFS and NFSROOT ready).
20 matches
Mail list logo
