From: Ray Olszewski <ray@comarre.com>
To: linux-newbie@vger.kernel.org
Subject: Re: Netconfig Fail
Date: Fri, 07 Oct 2005 10:23:24 -0700 [thread overview]
Message-ID: <4346AF0C.6070905@comarre.com> (raw)
In-Reply-To: <43465A15.5090708@gelm.net>
chuck gelm wrote:
[...]
>> Yes neither in Fedora nor in DSL had I to enter anything. In Fedora I
>> just
>> had to activate eth1, eth0 was taken by the onboard LAN card.
>
>
> It seems to me that Fedora is finding your add-on PCI card and
> assigning it eth0, yet Slackware is assigning it eth1 !?
>
> I expected, since you disabled the on-board ether device,
> all distributions would only find a 'eth0'.
>
> So, if Slackware assigns it 'eth1' and your rc.inet1.conf assigns
> DHCP to eth0, it will not work.
>
> Run dhcpcd from a console. If Slackware sees your PCI NIC as eth1;
> dhcpcd eth1
>
> If that works, you can either edit rc.inet1.conf or add
> 'dhcpcd eth1' to rc.local.
>
Chuck -- I think you read Peter's message backwards. The ifconfig output
he posted said (as I read it) that *Slackware* assigned the NIC to eth0,
while *Fedora* assigned it to eth1. Not the other way aound. (I'm
assuming, of course, that Peter is able to distinguish the 2 NICs
correctly, presumably by having noted their MAC addresses.)
So the main thing that this means is that Peter is being inexact when he
says yes to my question: Was everything else the same (across the 3
tests)? I note now, in what you posted (and I requote above), that Peter
says he did NOT disable (in the BIOS) the on-mobo NIC for the Fedora test.
As usual with these problems, the devil is in the details, and as is too
often the case, we have here the added problem of needing to get the
details reported correctly before we can do useful troubleshooting.
At this stage, I'd suggest that Peter repost his trouble report from the
beginning, this time putting in all the relevant details (e.g.,
complete, unedited "ifconfig -a" output from all 3 tests; complete,
unedited "lsmod" results from all 3 tests; complete "dmesg" output
regarding NIC detection from all 3 tests; and complete dhcpcd, or
whatever DHCP client the others use, logging from all 3 tests) ... and
this time doing all 3 tests with the on-mobo NIC disabled in BIOS and
EVERYTHING ELSE, except choice of distro, the same across all 3 tests.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2005-10-07 17:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-06 13:15 Netconfig Fail Peter
2005-10-06 7:33 ` Ray Olszewski
2005-10-07 16:23 ` Peter
2005-10-07 5:49 ` Ray Olszewski
2005-10-07 11:20 ` chuck gelm
2005-10-07 17:23 ` Ray Olszewski [this message]
2005-10-08 15:43 ` Peter
2005-10-08 15:22 ` Peter
2005-10-07 11:36 ` chuck gelm
2005-10-08 15:39 ` Peter
2005-10-08 4:18 ` Ray Olszewski
[not found] ` <200510052204.15272.david@fierbaugh.org>
2005-10-06 14:54 ` Peter
2005-10-06 12:53 ` David Fierbaugh
2005-10-06 18:52 ` chuck gelm
-- strict thread matches above, loose matches on Subject: below --
2005-10-08 18:33 Peter
2005-10-08 16:01 ` Ray Olszewski
2005-10-09 1:33 ` Peter
2005-10-09 7:04 ` Peter
2005-10-09 15:29 ` Peter
2005-10-09 18:00 ` chuck gelm
2005-10-09 7:08 Peter
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=4346AF0C.6070905@comarre.com \
--to=ray@comarre.com \
--cc=linux-newbie@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