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

Further investigation shows that if I connect the Gbit interface to a 10Mbs 
hub everything works ok, e.g. using the ksdevice=eth2 boot option works as 
expected.

I have narrowed this down to the following problem:  When the init process 
tries to configure the eth2 with dhcp it fail, but if I logon as root and run

/etc/init.d/network start

everything works ok.  Subsequent reboots also works ok because now the 
information is cached in /etc/dhcpc/.  If I remove the cached info the 
problem turn up again.

Do anyone know what could be different between init running the network start 
and when root does it?

r.




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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-09  8:30 [Linux-ia64] disabling nics using boot options Roy Dragseth
2003-01-09 15:16 ` Roy Dragseth [this message]

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-105590709805656@msgid-missing \
    --to=roy.dragseth@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