public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Roy Dragseth <royd@cc.uit.no>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: disabling nics using boot options.
Date: Thu, 09 Jan 2003 20:16:59 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709805658@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805657@msgid-missing>

On Thursday 09 January 2003 18:01, Bill Nottingham wrote:
> So, it works post-install, but not in the installer? Hm. The dhcp client
> code is different in the two cases, but not in a way that should
> significantly affect this case.

Well, it doesn't work during a normal bootup either.  If I remove the cached 
info in /etc/dhcpc/ and reboots, the network initialization fails:

Setting network parameters:  [  OK  ]
Bringing up interface lo:  [  OK  ]
Bringing up interface eth2:  dhcpcd[536]: timed out waiting for a valid DHCP 
server response
Determining IP information for eth2... failed.
[FAILED]

If I log in and run /etc/init.d/network start everything works ok:

root@compute-1-1 root]# /etc/init.d/network start
Setting network parameters:  [  OK  ]
Bringing up interface lo:  [  OK  ]
Bringing up interface eth2:  [  OK  ]

I cannot see what it is different when init starts the network from when root 
is doing it.

r.

-- 

  The Computer Center, University of Tromsø, N-9037 TROMSØ, Norway.
	      phone:+47 77 64 41 07, fax:+47 77 64 41 00
     Roy Dragseth, High Performance Computing System Administrator
	 Direct call: +47 77 64 62 56. email: royd@cc.uit.no



  reply	other threads:[~2003-01-09 20:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-09 17:01 [Linux-ia64] Re: disabling nics using boot options Bill Nottingham
2003-01-09 20:16 ` Roy Dragseth [this message]
2003-01-09 20:27 ` Bill Nottingham
2003-01-09 20:41 ` Roy Dragseth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-ia64-105590709805658@msgid-missing \
    --to=royd@cc.uit.no \
    --cc=linux-ia64@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox