From: Matthias Schwarzott <zzam@gentoo.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Problems with udev > 106 and multiple network cards
Date: Thu, 12 Apr 2007 09:12:02 +0000 [thread overview]
Message-ID: <200704121112.02335.zzam@gentoo.org> (raw)
In-Reply-To: <461BFFDD.2040401@googlemail.com>
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?
> 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.
Btw. why does this driver uses eth? as the device name and not something
prefixed with firewire?
Regards
Matthias
--
Matthias Schwarzott (zzam)
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2007-04-12 9:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-10 21:21 Problems with udev > 106 and multiple network cards Gabriel C
2007-04-11 2:59 ` Andrey Borzenkov
2007-04-11 6:41 ` Matthias Schwarzott
2007-04-11 11:14 ` Gabriel C
2007-04-11 13:27 ` Gabriel C
2007-04-11 17:51 ` Gabriel C
2007-04-12 9:12 ` Matthias Schwarzott [this message]
2007-04-12 17:43 ` Gabriel C
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200704121112.02335.zzam@gentoo.org \
--to=zzam@gentoo.org \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).