[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: stock kernel 2.6.12 eth0/eth1 swapped

On Fri, Dec 09, 2005 at 10:06:37PM -0500, Rich Johnson wrote:
> I've hit another snag trying to get etch up and running on my G4 Cube.
> The path so far has been
> - woody install (hey! it works!)
> - apt-get dist-upgrade
> - apt-get install linux-image-2.6.12-1-powerpc
> - manually modify yaboot.conf to reference the supplied initrd
> - install hotplug
> - remove hotplug
> - install ifrename--noted as being incompatible with hotplug.
> The problem is that the 2.6.12 stock kernel  identifies the firewire  
> interface as eth0 and the _normal_ interface as eth1.
> Meanwhile 2.4.18-newpmac stock kernel does not provide a firewire  
> ethernet and the _normal_ interface is eth0.
> The bottom line is that a 2.6.12 stock kernel cannot access the network.

I have definitely a problem with believing that one ... :)

> I'm a bit lost as to whether ifrename is the ''correct'' way to  
> correct this problem.  Its man page reports that it _cannot reliably_  
> rename eth0 and eth1.

I never, IIRC, used 'ifrename'.. 

IIRC: I did a 'ifconfig -a', checked which interface were the correct
one I needed for my Ethernet connection, and then set the
/etc/network/interfaces file to exactly the interface (i.e. eth0,
eth1, whatever ...) that was recognised by the system to be
responsible for my (wired) ethernet connection to the world ... :)

Before I change /etc/network/interfaces I use this little script:

#!/bin/sh -x 

echo "Stopping networking .. " && \

/etc/init.d/portmap stop && \
/etc/init.d/dnsmasq stop && \
/etc/init.d/networking stop && \
/etc/init.d/ifupdown stop && \
/etc/init.d/dns-clean stop && \

echo "OK: Network is down"

after changing the aforementioned 'interfaces' file:


echo "Bringing up networking ..." && \

/etc/init.d/dns-clean start && \
/etc/init.d/ifupdown start && \
/etc/init.d/networking start && \
/etc/init.d/dnsmasq start && \
/etc/init.d/portmap start && \
echo "OK: Network is up and running"

Both of these scripts work, but I think they're very rudimentary,
probably even wrong. I'm not good in scripting ... So please don't use
them on your system.

All the above only provided my lousy memory serves me well ... :)

> Have any of you folks encountered this? 

Yes, at least similar to it:


Best Regards

Wolfgang Pfeiffer

Key ID: E3037113
Key fingerprint = A8CA 9D8C 54C4 4CC1 0B26  AA3C 9108 FB42 E303 7113

Reply to: