I just added a third ethernet card to my firewall machine in preparation 
for setting up a web server/DMZ subnet.

This new card is identical to the other two already in the machine which 
are both working (fwiw, they're all ISA NE2000 clones, hard-configured to 
non-overlapping IRQs and io addresses). I've identified them to lilo.conf 
_and_ in modules.conf, and done a lilo -v.

When I boot with the stock RH 6.2 kernel v2.2.16, all three interfaces are 
recognized, initialized, and run fine (and catting /proc/interrupts and 
/proc/ioaddresses confirms the cards' IRQ/IO address parameters given below 
are correct).

But when I boot with my home-built "minimal" v2.2.17 kernel, only eth0 and 
eth1 are even seen (they work fine). eth2 isn't initialized or even probed, 
as far as I can tell.

What could be missing from my kernel or init files that's causing this 
behavior? (Remember, these are literally identical cards from the same 
manufacturer.)

One possible clue: since I built ne2k support directly into my 2.2.17 
kernel, it uses only the lilo.conf "append" commands to configure the NICs 
- in contrast, the 2.2.16 kernel, with loadable module support, uses 
modules.conf for that purpose. But everything below looks good with both 
files, so....?

TIA for any (informed) speculation. Newbies replying with copies of man 
pages will be cheerfully ignored. :)

/David/

in /etc/lilo.conf:
image=/boot/vmlinuz-2.2.17jdr
         label=linux.2.2.17jdr
         read-only
         append="ether=10,0x300,eth0 ether=11,0x320,eth1 ether=12,0x340,eth2"
         root=/dev/hda3


in /etc/modules.conf:
alias parport_lowlevel parport_pc
alias eth0 ne
alias eth1 ne
alias eth2 ne
options ne io=0x300,0x320,0x340 irq=10,11,12        



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to