From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gabriel C Date: Thu, 12 Apr 2007 17:43:00 +0000 Subject: Re: Problems with udev > 106 and multiple network cards Message-Id: <461E6FA4.1000408@googlemail.com> List-Id: References: <461BFFDD.2040401@googlemail.com> In-Reply-To: <461BFFDD.2040401@googlemail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: linux-hotplug@vger.kernel.org Matthias Schwarzott wrote: > On Mittwoch, 11. April 2007, Gabriel C wrote: > =20 >> I have also an FireWire device too which is there as : >> >> /sys/class/net/eth0 -> ../../devices/virtual/net/eth0/ >> >> INTERFACE=3D"eth0" DEVPATH=3D"/sys/class/net/eth0" \ >> >> > sudo /lib/udev/write_net_rules >> >> No MAC address for eth0. >> >> This virtual device is causing the whole problem. Udev does not write >> any rules for it ( knows about it ? ) and without to blacklist the >> firewire driver >> =20 > > Perhaps you miss some rule like: > ACTION=3D"add", SUBSYSTEM=3D"net", WAIT_FOR_SYSFS=3D"address" > > Does udevtrigger creates an appropriate rule? > =20 Yes I was actually missing it. Thx. > =20 >> eth0 is always the firewire devices as : >> >> eth0 Link encap:UNSPEC HWaddr >> 00-40-D0-01-00-15-F6-9E-00-00-00-00-00-00-00-00 >> .... >> >> Booting with Firewire device the sis and pcmcia card I get this rules , >> generated by udev : >> >> >> =20 > > > =20 >> With the patch from git and blacklisted eth1394 driver things are >> working again but is again ugly workarounded. >> >> I guess to fix this problem udev need to ignore such /virtual/ devices ? >> >> =20 > Ignoring will not help, as then udev still hangs on its (60sec) timeout i= f the=20 > name it wants to give to some eth card is used by your eth1394 device. > Perhaps post the content of 70-persistent-net.rules, and=20 > udevinfo -a -p /sys/class/net/eth? for the eth1394 device. > =20 I solved it by adding the missing rules and prefixing firewire with=20 fw-eth%n as you suggested. Thank you very much for your help. > Btw. why does this driver uses eth? as the device name and not something = > prefixed with firewire? > =20 Good question :) I never cared about because everything worked fine. I'm not really sure what the best method is to match all firewire=20 devices with a udev rules. So far I see all this ethX_firewire devices have : ATTR{type}=3D"24" So I've created a rule like this one : ACTION=3D"add", SUBSYSTEM=3D"net", ATTR{type}=3D"24", NAME=3D"fw-eth%n" which works fine but may be not the best solution. Do you know the right=20 way to do this ? Maybe udev should have some rules to prefix this devices by default ? > Regards > Matthias > > =20 Regards, Gabriel ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=DEVD= EV _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel