Ross Drummond wrote:
On Thu, 22 Mar 2007 18:10, Nick Rout wrote:
Due to a power supply letting out the magic smoke I moved my mythtv main
OS drive into another case with a different motherboard etc. Of course
all the chipsets are different, what was via-rhine is now sis900 etc.
now the sis video card is recognised on boot, and there is an eth0
created, as one would expect on a reasonably modern kernel. The trouble
is it is not getting an IP address on bootup. /etc/networking/interfaces
looks right (and indeed is unchanged, so should work). It is set to
dhcp. Running "/etc/init.d/networking restart" after boot works, but is
a PITA for a machine with (usually) no keyboard.
Can anyone tell me where to look to determine why eth0 is not
automatically getting an ip address?
knoppmyth is based on knoppix which is basically debian. I figure that:
1. I changed nothing in terms of settings (except the
/etc/X11/Xf86config-4 file)
2. eth0 is detected and the driver loaded by the kernel, same as before
(albeit a different driver, but its still eth0)
3. By the time the startup scripts run /etc/init.d/networking it should
ready to obtain an IP address, the same as before.
Try running;
ifconfig -a
I recently had a problem similar to yours with dhcp not working on boot up. I
had recently updated udev which had arbitrarily reassigned eth0 to a firwire
device and the network card to eth1. The init scripts were trying to use the
eth0 device to to establish network connections and failing
The -a argument displays the status of all interfaces, even those that are
down.
Cheers Ross Drummond
eth0 is still the ethernet, because when I run /etc/init.d/networking
restart, after bootup is completed, eth0 gets a dhcp address as normal.
What i can't figure is why it isn't doing it earlier.
