public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jerry A! <jerry@thehutt.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] gentoo installation problems
Date: Wed Jul 11 11:47:02 2001	[thread overview]
Message-ID: <20010711134514.A3295@gemini.thehutt.org> (raw)
In-Reply-To: <E15KNPL-00007h-00@cvs.gentoo.org>; from shalidor@cfl.rr.com on Wed, Jul 11, 2001 at 01:07:07PM -0400

On Wed, Jul 11, 2001 at 01:07:07PM -0400, Marcus A Martin wrote:
: > 
: >Use the "-d" flag for debug.  This should throw out copious amounts of
: >information.  In addition to "-d" you may want to use the "-T" flag for
: >test mode.  It'll show you what's supposed to happen, but won't actually
: >change anything (not like it matters right now, but for future
: >edification).
:
: With the -d option, I discovered that failure occurs on the
: DHCP_DISCOVER call.  This is really odd.  Like I said, my dhcp server
: has a debian box and 2 windows boaxes connecting to it and they run
: fine.  Do I need to do anything before I attempt to run dhcp eth0?  The
: only thing that I have done is enabled the network card by loading the
: tulip driver with modprobe.  Is there something else I should do first?

You can try issuing "ifconfig eth0 up" to make sure that the interface
is up and then run "dhcpcd -d eth0".

Without knowing you network topology there's not much more help I can
be.

You may not be connecting b/c the card isn't correctly auto-negotiating
with the switch/hub it's plugged into.  Maybe you DHCP server has
tresholds or does expect a hostname or MAC address.  Maybe the network
card is bad.  Try swapping it with one of the working ones.

: >What version are you running.  I just looked at both the i686-exclusive
: >and x86-build cds that I have and OFF_inet.dhcp_eth0 used dhcpcd.
:
: I have noticed that both the binary and build CD have dhcpcd but the
: OFF_inet.dhcp_eth0 file uses dhclient in the script.  You may want to
: either update the script or add the dhclient file back into the sbin
: directory.

I'll make a note on the Wiki to update the script (unless Dan or Achim
beat me to it).

: Is there a rc4 iso image that I can get at?  Maybe using a different
: image will be of help?

I don't think it'll help.  Right now we need to figure out what's hosing
your network.

        --Jerry

name:  Jerry Alexandratos         ||  Open-Source software isn't a
phone: 703.599.6023               ||  matter of life or death...
email: jerry@thehutt.org          ||  ...It's much more important
                                  ||  than that!



  reply	other threads:[~2001-07-11 17:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-11 11:05 [gentoo-dev] gentoo installation problems Marcus A Martin
2001-07-11 11:47 ` Jerry A! [this message]
2001-07-11 13:15   ` Daniel Robbins
  -- strict thread matches above, loose matches on Subject: below --
2001-07-12  7:28 Marcus A Martin
2001-07-11 12:37 Marcus A Martin
2001-07-11 12:56 ` Jerry A!
2001-07-11  9:09 Marcus A Martin
2001-07-11  9:23 ` Jerry A!
2001-07-11  8:48 Marcus A Martin
2001-07-11  9:02 ` Jerry A!
2001-07-10 23:00 Marcus A Martin
2001-07-10 23:54 ` Jerry A!
2001-07-11  7:53   ` Marcus Martin
2001-07-11  8:48     ` Jerry A!
2001-07-11 23:54   ` Marcus A Martin
2001-07-12  0:31     ` Jerry A!

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=20010711134514.A3295@gemini.thehutt.org \
    --to=jerry@thehutt.org \
    --cc=gentoo-dev@cvs.gentoo.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