>After a reboot, I have two problems. One is that neither of the NIC's is
>brought up at startup, despite these lines in /etc/conf.modules:
>alias eth0 eepro100
>alias eth1 ne
>options ne io=0x240 irq=3
you need to check to make sure the "ONBOOT=" flag is set correctly (to yes)
in /etc/sysconfig/network-scripts/ifcfg-eth0 (& eth1) - this is a redhat
thing, I don't know
about other distros.
>I know that the 8390 module is required to use the ne, so I am suspecting
>that it has to be inserted into this file for the ne to be brought up
>successfully, maybe appended to the second line? However, this still
doesn't
>explain the eepro100 not being loaded in.
nope, linux will bring up the interface intelligently and load any modules
it depends on, I think it uses modprobe to do this, but I havent check the
init script. so basically you don't need to specify 8390. I know insmod
isn't that smart, but modprobe is.
>My second problem is that once I do insert the modules manually, I can
>configure both cards and see the network, but I can't get dhcpcd to assign
>the ne's IP address. After running it:
>dhcpcd -h <hostname> interface eth1
>it seems to run and exit (or fork(), whatever it does) successfully, but
>checking ifconfig shows the interface remains unchanged. Mind you, this
>command worked flawlessly previously.
If your using Redhat's way, it uses a program called kudzu to probe for new
hardware, so when you installed the new nic, it might of botched your
installation slightly, Ive found that it doesnt do everything correctly
especially configuring nics. You should see if your external cable modem nic
is configured to accept DHCP requests in the above eth0 file, apart from
that, I'm unsure.
--Stephen
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
