Tony Lawrence wrote:
>
> I've seen this same thing now on three 4.1.1 installs.. I
> just added an "ifup eth1" to S99local to kick start it, but
> there's definitely something wrong here.
There certainly is, and we would like to track down the problem or problems. We certainly don't want people to have to resort to editing scripts.
> One of mine was an unsupported isa card which I had
> configured in conf.modules,
Even with an ISA card, as long as the EthernetDriver2 parameters is correctly configured in the e-smith configuration database, and any options specified correctly in /etc/modules.conf (this replaces /etc/conf.modules in e-smith 4.0 and earlier), it should work correctly without any script modifications.
> but another was on a statically
> configured pci and the third was a dhcp configured pci card.
> All were on the external cards.
It surprises me that a statically configured PCI card did not work "out of the box", but did work when you did "ifup eth1". The only failure mode that I know of for static IP configured cards is if the driver is not compatible with the card, and that won't magically work if you run ifup. For DHCP configured cards, I've seen eth1 fail to start on an @home system - the failure seemed to be due to a slow or unreliable DHCP server not offering a DHCP lease. In that case, "ifup eth1" also worked very intermittently.
Tony, could you please send details of each of these cases to bugs@e-smith.com? I'm particularly interested in any messages in /var/log/messages at boot up time, when I assume that you get a "FAILED" showing on the console.
Thanks
Charlie