linux-mips
[Top] [All Lists]

Re: configuring 2 ethernet ports

To: linux-mips@linux-mips.org
Subject: Re: configuring 2 ethernet ports
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Date: Fri, 24 Oct 2003 16:40:12 +0200
In-reply-to: <Pine.GSO.4.44.0310240931350.17395-100000@ares.mmc.atmel.com>
Mail-followup-to: linux-mips@linux-mips.org
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20031024131838.GE12395@lug-owl.de> <Pine.GSO.4.44.0310240931350.17395-100000@ares.mmc.atmel.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.4i
On Fri, 2003-10-24 09:41:23 -0400, David Kesselring <dkesselr@mmc.atmel.com>
wrote in message <Pine.GSO.4.44.0310240931350.17395-100000@ares.mmc.atmel.com>:
> On Fri, 24 Oct 2003, Jan-Benedict Glaw wrote:
> > On Fri, 2003-10-24 09:11:26 -0400, David Kesselring <dkesselr@mmc.atmel.com>
> > wrote in message 
> > <Pine.GSO.4.44.0310240905590.17395-100000@ares.mmc.atmel.com>:
> > > /etc/sysconfig/network-scripts/ifcfg-eth1. After boot, when I look at
> > > /proc/pci it looks like the system detected the card fine but ifconfig
> > > only shows eth0 (the builtin port). How is the pci id linked to a
> > > particular driver? What else do I need to do? I've scoured google but have
> >
> > In 2.4.x, drivers tend to only have internal knowledge on which hardware
> > they work. So you need to give some 'alias eth1 wlanmodulename' in your
> > /etc/modules.conf file.
> >
> I am using 2.4. Why does eth1 need a modules.conf file and eth0 doesn't. I

This is the case if you've compiled the driver for eth0 directly into
the kernel. Then, it'll automatically be started and userspace got an
interface to configure.

If it isn't directly compiled in, you've to give it a chance to figure
out the correct driver, eg. by a module.conf "alias" line or by a simple
modprobe somewhere...

> do not have loadable modules configured for my kernel. Do I have to? I
> don't even have a current modules.conf file.

You don't *need* to have modules. ...but then, you need to have the
correct driver compiled in. If it's already compiled in, then it
apparently doesn't recognize the card. In this case, the PCI table
inside the module's code is missing the PCI vendor/device ID.

> I also checked /etc/sysconfig/hwconf. This has the pci listing for my card
> but does not recognize the vendor or id. I did add an entry in the kernel
> source pci_ids.h for my card.

That's not enough. By doing this, you tell the *readers* of this header
file that there's a new vendor or device. That doesn't tell the
*drivers* that they've got a new supported device. So if you compiled-in
the correct driver and 'ifconfig -a' doesn't show it, then it seems that
the (correct) driver incorrectly doesn't know your device IDs. Add those
to the driver's PCI ID table.

MfG, JBG

-- 
   Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
   ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

Attachment: signature.asc
Description: Digital signature

<Prev in Thread] Current Thread [Next in Thread>