From: Matthias Schwarzott <zzam@gentoo.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Problems with udev > 106 and multiple network cards
Date: Wed, 11 Apr 2007 06:41:16 +0000 [thread overview]
Message-ID: <200704110841.17145.zzam@gentoo.org> (raw)
In-Reply-To: <461BFFDD.2040401@googlemail.com>
On Dienstag, 10. April 2007, Gabriel C wrote:
> Hello,
>
> I have some problems with udev 107 and 108 with my network cards.
>
> This box has 3 network cards ( 2 at the moment ) a buildin sis900 , and
> 2 RealTek cards one USB and one pcmcia.
>
> I use the pcmcia RealTek one as default , sis900 is not used while
> borken and the usb one is used just sometimes for my LAN.
>
> I use on this box minimal initramfs ( FS drivers etc to boot ) but I get
> the same problem without initramfs too.
>
> After upgrading from udev 106 to 107 ( later to 108 ) and rebooting the
> box my network stoped working.
>
> I figured the 'cards names' looks weird , random they are called now
> ethX_rename (
> http://frugalware.org/~crazy/other/udev/sys_class_net.txt |
> http://frugalware.org/~crazy/other/udev/ifconfig-a.txt )
> as well I get for each card an long timeout ( 5 to 15 seconds for each
> wrong named card ) on boot because the 70-persistent-net.rules.
>
> Deleting the rules before udev starts make the timout be human again (
> like 2 - 3 seconds ) but the rules are still wrong because I get as
> NAME ethX_rename.
>
I suspect it is this bug:
http://thread.gmane.org/gmane.linux.hotplug.devel/11001
Look into /etc/udev/rules.d/70-persistent-net.rules, and
into /dev/.udev/tmp-rules--70-persistent-net.rules if there are rules that
set the same name for two different cards (mac addresses).
The tmp-location is used as long as / is read-only at udev startup time.
Easiest is to delete both files and reboot / or edit the set names for
net-devices to be unique. Then the error should be gone.
If not you found another bug.
>
> I noticed one more strange thing with the db , while in <= 106 the db
> was like foo\@bar -> something , >106 looks here like %2fbar%2fbaz ->
> something
> ( http://frugalware.org/~crazy/other/udev/udev_db.txt )
>
This is OK, it's the new name-encoding.
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-11 6:41 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 [this message]
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
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=200704110841.17145.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).