On Mon, 25 Jun 2007 17:10:34 -0400 Dan Williams <dcbw-H+wXaHxf7aLQT0dZR+AlfA@xxxxxxxxxxxxxxxx> wrote: > On Mon, 2007-06-25 at 14:50 -0500, Larry Finger wrote: > > Matteo Croce wrote: > > > Exactly, the boot process goes so: > > > 1) udev loads forcedeth.ko and it gets eth0 > > > 2) udev also loads airo.ko > > > 3) forcedeth loads very fast and udev renames it to eth1 according to /etc/iftab > > > 4) airo slowly init the card and try to get eth1 as name, but found it busy and die() > > > > > > Personally I solved this by deleting forcedeth.ko. I know that it's ugly, but I don't use wired etherned > > > and i hate do "rmmod airo ; modprobe airo" at every boot, also in a shell script. > > > > What does /etc/udev/rules.d/30-net_persistent_names.rules say about the name for the MAC address of > > the wired interface? On my system, the wired one is forced to be eth0 and the wireless to be eth1. > > Even so, drivers need to be safe against device renames at any stage. > > Dan > > Name should NOT be used for anything but messages (and request_irq). The driver should use ifindex if it needs some persistent token. Using rtnl_lock() works but it can't be held across hotplug or other events. - To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
