Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: Association between eth0 and 3c59x...
- To: <tlug@example.com>
- Subject: Re: Association between eth0 and 3c59x...
- From: "roylo" <roylo@example.com>
- Date: Fri, 31 Aug 2001 21:19:43 -0700
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain;charset="iso-8859-1"
- Delivered-To: tlug@example.com
- List-Help: <mailto:tlug-request@example.comsubject=help>
- List-Post: <mailto:tlug@example.com>
- List-Subscribe: <mailto:tlug-request@example.comsubject=subscribe>
- List-Unsubscribe: <mailto:tlug-request@example.comsubject=unsubscribe>
- Old-Return-Path: <roylo@example.com>
- References: <Pine.BSO.4.30.0109011229510.32242-100000@example.com> <000b01c1329b$64eda4a0$0200a8c0@example.com>
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <ge4jMC.A.M8.gHGk7@example.com>
- Resent-Sender: tlug-request@example.com
opps, hit the send bottom too fast to make long story short by doing a cat on /proc/pci will show you the device with it's IRQ number and then cat /proc/interrupts to find out which eth(#) device it is. (If you have more than one eth card in this case) example here: doing "cat /proc/pci" you will get infos like this Bus 0, device 9, function 0: Ethernet controller: 3Com Corporation 3c905C-TX [Fast Etherlink] (rev 116). IRQ 7. Master Capable. Latency=32. Min Gnt=10.Max Lat=10. I/O at 0xd000 [0xd07f]. Non-prefetchable 32 bit memory at 0xe1800000 [0xe180007f]. Bus 0, device 14, function 0: Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 48). IRQ 3. Master Capable. Latency=32. Min Gnt=10.Max Lat=10. I/O at 0xb000 [0xb07f]. Non-prefetchable 32 bit memory at 0xe1000000 [0xe100007f]. And "cat /proc/interrupts" to match it CPU0 0: 95908889 XT-PIC timer 1: 103276 XT-PIC keyboard 2: 0 XT-PIC cascade 3: 1123802 XT-PIC eth1 7: 29979290 XT-PIC eth0 10: 0 XT-PIC EMU10K1 12: 395650 XT-PIC PS/2 Mouse 14: 173303 XT-PIC ide0 15: 236820 XT-PIC ide1 NMI: 0 ERR: 0 MIS: 0 So in this case we know that 3c905C-TX is eth0 and 3c905B is eth1 ----- Original Message ----- From: "roylo" <roylo@example.com> To: <tlug@example.com> Sent: Friday, August 31, 2001 9:05 PM Subject: Re: Association between eth0 and 3c59x... > Also to add on top of that; if it is a pci ethernet card you do a cat on > /proc/pci and it will show you the info as well. > and if you have the drivers installed as modules then you can do /sbin/lsmod > as well too > > > > ----- Original Message ----- > From: "Tim Hurman" <kano-tlug@example.com> > To: "Tokyo Linux Users' Group" <tlug@example.com> > Sent: Friday, August 31, 2001 8:38 PM > Subject: Re: Association between eth0 and 3c59x... > > > > you can figure it out indirectly by knowing the MAC address of your card. > > then by typing ifconfig you get: > > ifconfig -a > > eth0 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx > > which should match. > > > > also the output of 'dmesg' will tell you > > dmesg | grep eth0 > > (same info in /var/adm/messages) > > > > if it is a standard pci card, the contents of /proc/ioports or iomem will > > reveal the card. ifconfig also reports the base address of the card (and > > interrupt) in question. > > > > hope that helps, > > > > Tim. > > > > > > On Fri, 31 Aug 2001, Scott M. Stone wrote: > > > > > > > > How can you figure out, by querying the kernel, what ethernet driver is > > > bound, say, to eth0? shouldn't the kernel keep track of this somewhere? > > > I can't find any ioctl, any system call, etc, that will give me this > > > information. > > > > > > I would think there's some way to ask the kernel, "what driver is giving > > > you eth0" without having to look through dmesg, conf.modules, etc, etc.. > > > > > > -------------------------- > > > Scott M. Stone <sstone@example.com> > > > Director of Information Technology, Director of Research and Development > > > ITIsOpen, Inc. - http://www.itisopen.com > > > Cisco Certified Network Associate, Sun Solaris Certified Systems > Administrator > > > > > > ----------------------------------------------------------------------- > > > Next Technical Meeting: Sat, Sep 15 13:30- Leading Edge Co., Place > Canada > > > Next Nomikai Meeting: Fri, Oct 19 19:30- Tengu Tokyo Eki-Mae > > > ----------------------------------------------------------------------- > > > more info: http://www.tlug.gr.jp Sponsor: Global Online Japan > > > > > > > > > > ----------------------------------------------------------------------- > > Next Technical Meeting: Sat, Sep 15 13:30- Leading Edge Co., Place > Canada > > Next Nomikai Meeting: Fri, Oct 19 19:30- Tengu Tokyo Eki-Mae > > ----------------------------------------------------------------------- > > more info: http://www.tlug.gr.jp Sponsor: Global Online Japan > > ----------------------------------------------------------------------- > Next Technical Meeting: Sat, Sep 15 13:30- Leading Edge Co., Place Canada > Next Nomikai Meeting: Fri, Oct 19 19:30- Tengu Tokyo Eki-Mae > ----------------------------------------------------------------------- > more info: http://www.tlug.gr.jp Sponsor: Global Online Japan
- Follow-Ups:
- Re: Association between eth0 and 3c59x...
- From: "Scott M. Stone" <sstone@example.com>
- References:
- Re: Association between eth0 and 3c59x...
- From: Tim Hurman <kano-tlug@example.com>
- Re: Association between eth0 and 3c59x...
- From: "roylo" <roylo@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: Association between eth0 and 3c59x...
- Next by Date: serial and other devices programming.
- Prev by thread: Re: Association between eth0 and 3c59x...
- Next by thread: Re: Association between eth0 and 3c59x...
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links