Under 2.2 and 2.4, I have gotten away with doing the following (assuming
the module does not require a port address or irq):
alias eth0 modulename
alias eth1 modulename
This assumes the kernel sees both cards (look in your kernel ring log,
typically /var/log/dmesg). If the entries are both there for eth0 and
eth1 and irq and port addresses are correct, you're ready to go. I have
had no problems with DLink DE220s for example (NE2000 clones).
If it does not see the 2nd card (eth1), then go for something like
"ether=0,0,eth1" in at the boot prompt (use the append option for LILO
to make it permanent if you're using LILO). If that does not work, then
provide "ether=11,0x300,eth1" (example of IRQ11, IO address 300 hex).
The man page on bootparam will explain a little further.
The above was sometimes necessary for ISA, but the PCI world should
require less intervention.
Thomas Duffy wrote:
>On 04 Aug 2001 13:21:59 +1200, Chris Wedgwood wrote:
>
>>the kernel calls modprobe asking for the network device 'eth0',
>>modprobe uses the configuration file to map this to a module
>>
>
>so, what happens when you have two eth cards that use the same module?
>in the isa land, the order you pass the io=0x300,0x240 would determine
>which order the eth?'s go to...how about in the pci world?
>
>-tduffy
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" 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.tux.org/lkml/
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" 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.tux.org/lkml/