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

Bug#407460: USB ethernet interface renamed after installation on NSLU2 which causes the system to be inaccessible

On Mon, Feb 12, 2007 at 10:40:39AM +0100, Marco d'Itri wrote:
> On Feb 12, Steve Langasek <vorlon@debian.org> wrote:

> > The problem seems as simple as that the ipx4xx driver is *not* included in
> > d-i, but is included in the installed kernel; so in the installer, the
> > module is never loaded resulting in the USB adapter getting the eth0 name,
> > but after a reboot the ipx4xx driver is found first, breaking the handling
> > of persistent device names.
> No, wait... When a new network interface is added it will get the next
> available name, this is a supported configuration.

Ok, so this is true when the built-in device is loaded first at boot time
and is initially assigned eth0, there is no rule saying to rename it, and
there is a rule saying to rename another interface to eth0?

> The problem is that for some reason udev believes that both devices
> should get the same name. I had no time to properly review this bug,
> but my bet is that udev thinks that one of the devices (eth0) should
> not be renamed, so trying to rename the other one to eth0 too will fail.
> Maybe DRIVERS=="?*" (which is needed to ignore stuff like VLAN
> subinterfaces) is not matching.

Ok, thanks for the info.

Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
vorlon@debian.org                                   http://www.debian.org/

Reply to: