From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Subject: Re: Netconfig Fail Date: Sat, 8 Oct 2005 11:43:22 -0400 Message-ID: <20051008114322.5c86c6b5.heisspf@skyinet.net> References: <20051006091512.7dd839e8.heisspf@skyinet.net> <4344D330.2050005@comarre.com> <20051007122344.3780b5c0.heisspf@skyinet.net> <43465A15.5090708@gelm.net> <4346AF0C.6070905@comarre.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4346AF0C.6070905@comarre.com> Sender: linux-newbie-owner@vger.kernel.org List-Id: Content-Type: text/plain; charset="us-ascii" To: Ray Olszewski Cc: linux-newbie@vger.kernel.org On Fri, 07 Oct 2005 10:23:24 -0700 Ray Olszewski wrote: > 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. > OK I will try to get it all together. Jumping from distro to distro hoping staying online which I was not this morning for 4 hours. - 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