Re: Problems with udev > 106 and multiple network cards

[Gabriel C <nix.or.die@googlemail.com>]

Matthias Schwarzott wrote:
> On Mittwoch, 11. April 2007, Gabriel C wrote:
>   
>> I have also an FireWire device too which is there as :
>>
>> /sys/class/net/eth0 -> ../../devices/virtual/net/eth0/
>>
>> INTERFACE="eth0" DEVPATH="/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
>>     
>
> Perhaps you miss some rule like:
> ACTION="add", SUBSYSTEM="net", WAIT_FOR_SYSFS="address"
>
> Does udevtrigger creates an appropriate rule?
>   

Yes I was actually missing it. Thx.

>   
>> 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 :
>>
>>
>>     
>
>
>   
>> 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 ?
>>
>>     
> Ignoring will not help, as then udev still hangs on its (60sec) timeout if the 
> 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 
> udevinfo -a -p /sys/class/net/eth? for the eth1394 device.
>   

I solved it by adding the missing rules and prefixing firewire with 
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?
>   

Good question :) I never cared about because everything worked fine.

I'm not really sure what the best method is to match all firewire 
devices with a udev rules.

So far I see all this ethX_firewire devices have :

ATTR{type}="24"

So I've created a rule like this one :

ACTION="add", SUBSYSTEM="net", ATTR{type}="24", NAME="fw-eth%n"

which works fine but may be not the best solution. Do you know the right 
way to do this ?

Maybe udev should have some rules to prefix this devices by default ?

> Regards
> Matthias
>
>   

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=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
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