How to have two ethernet cards.

Hi,
I've a system with two ethernet cards, one Winbond W89C940 and another
D-Link DFE-520TX (Via Rhine III). I've a custom kernel with both
inbuilt, no modules. I want to have them as eth0 and eth1
automatically. Whenever i boot them Winbond is recognised as eth0 but
not D-link. I've removed Winbond and booted to find that now dlink is
recognised as eth0. What i'd like to see is both of them getting
recognised at bootup. My kernel is 2.6.7. What are the boot options
that i must give inorder to have them detected. lspci detects both of
them. Cant i do away with boot options? I mean even if i did not
provide the irq, I/O address as boot options wont both of my cards get
recognised?

Kindly help me,
-- Masood Ahmed

(Visit my blog at http://linsysadmin.blogspot.com)

On 12/10/05 11:23, Masood Ahmed wrote:

> Hi,
> I've a system with two ethernet cards, one Winbond W89C940 and another
> D-Link DFE-520TX (Via Rhine III). I've a custom kernel with both
> inbuilt, no modules. I want to have them as eth0 and eth1
> automatically. Whenever i boot them Winbond is recognised as eth0 but
> not D-link. I've removed Winbond and booted to find that now dlink is

Do you provide commands to configure eth1?

> recognised as eth0. What i'd like to see is both of them getting
> recognised at bootup. My kernel is 2.6.7. What are the boot options
> that i must give inorder to have them detected. lspci detects both of
> them. Cant i do away with boot options? I mean even if i did not
> provide the irq, I/O address as boot options wont both of my cards get
> recognised?

Compile them as modules and put in /etc/modprobe.conf the following:

alias eth0 module_for_winbond_card
alias eth1 module_for_via_rhine

Configuring eth0 and eth1 will load the proper module.

Ciao
Giovanni
--
A computer is like an air conditioner,
it stops working when you open Windows.
Registered Linux user #337974 <http://counter.li.org/>

ya, i did tried to configure using

ifconfig eth0 192.168.1.1 up, it worked fine but
ifconfig eth1 192.168.1.2 up didnt. It said there was no device. When i
removed winbond card and did ifconfig eth0 192.168.1.1 up it worked
fine. I dont want to compile them as modules. Surely there must be a
way to compile them directly into linux and get them both recognised. I
know there are some boot params to pass, like ether=xxx i dont know for
sure. Kindly help me on this.

Thanks for your reply,
--Masood Ahmed

On 12/10/05 11:49, Masood Ahmed wrote:
> ya, i did tried to configure using
>
> ifconfig eth0 192.168.1.1 up, it worked fine but
> ifconfig eth1 192.168.1.2 up didnt. It said there was no device. When i
> removed winbond card and did ifconfig eth0 192.168.1.1 up it worked
> fine. I dont want to compile them as modules. Surely there must be a
> way to compile them directly into linux and get them both recognised. I
> know there are some boot params to pass, like ether=xxx i dont know for
> sure. Kindly help me on this.
>
> Thanks for your reply,
> --Masood Ahmed
>

You can try with the boot parameters in lilo:
append='ether=irq,iobase[,param_1[,...param_8]],ethx'

See man pages for: bootparam, lilo, lilo.conf

Ciao
Giovanni

--
A computer is like an air conditioner,
it stops working when you open Windows.
Registered Linux user #337974 <http://counter.li.org/>

I hope the same command line addition works for grub, i use grub

In comp.os.linux.networking Masood Ahmed <(E-Mail Removed)>:
> Hi,
> I've a system with two ethernet cards, one Winbond W89C940 and another
> D-Link DFE-520TX (Via Rhine III). I've a custom kernel with both
> inbuilt, no modules. I want to have them as eth0 and eth1

Why? What is the reason for doing so? It sounds like you bought a
Porsche and tell us you just removed one front tire.

> automatically. Whenever i boot them Winbond is recognised as eth0 but
> not D-link. I've removed Winbond and booted to find that now dlink is
> recognised as eth0. What i'd like to see is both of them getting
> recognised at bootup. My kernel is 2.6.7. What are the boot options

Why using such an old version? Current is 2.6.14 (iirc).

> that i must give inorder to have them detected. lspci detects both of
> them. Cant i do away with boot options? I mean even if i did not
> provide the irq, I/O address as boot options wont both of my cards get
> recognised?

See Documentation/kernel-parameters.txt in you kernel source dir.

Good luck

--
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo (E-Mail Removed) | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 5: static from plastic slide rules