From: Jason Lunz <lunz@falooley.org>
To: Ben Gamari <ben@mw0.ath.cx>
Cc: ipw3945-devel@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: iwlwifi initial bugs/thanks
Date: Tue, 13 Feb 2007 14:13:13 -0500 [thread overview]
Message-ID: <20070213191313.GA2427@metaxa.reflex> (raw)
In-Reply-To: <1171382436.12035.38.camel@localhost>
On Tue, Feb 13, 2007 at 04:00:36PM +0000, Ben Gamari wrote:
> That being said, now come the problems. When I first loaded the driver,
> I found that it had created two interfaces as mentioned in earlier
> threads. On my machine these are named eth1 and wlan0_rename (can
> someone confirm what the names are supposed to be and which interface
> does what?). Strangely, it appears that wlan0_rename is the actual
> wireless adapter as evidenced by the attached console session. In that
The "_rename" suffix is an indication that you have udev rules that are
attempting to assign the same name to two different netdevs. Try to
disable udev device renaming, or make the rules more specific.
The attached kernel patch makes it easier to figure out what udev is
trying to do in situations like yours. It keeps getting rejected from
linux upstream, but that could change with enough encouragement.
Jason
---
Keep track about which network interface names were renamed after the
network device driver printed its banner.
Signed-off-by: Olaf Hering <olaf@aepfle.de>
---
net/core/dev.c | 4 ++++
1 file changed, 4 insertions(+)
Index: linux-2.6.20-uml/net/core/dev.c
===================================================================
--- linux-2.6.20-uml.orig/net/core/dev.c
+++ linux-2.6.20-uml/net/core/dev.c
@@ -754,7 +754,11 @@
else if (__dev_get_by_name(newname))
return -EEXIST;
else
+ {
+ if (strncmp(newname, dev->name, IFNAMSIZ))
+ printk(KERN_INFO "%s renamed to %s\n", dev->name, newname);
strlcpy(dev->name, newname, IFNAMSIZ);
+ }
err = class_device_rename(&dev->class_dev, dev->name);
if (!err) {
next parent reply other threads:[~2007-02-13 20:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1171382436.12035.38.camel@localhost>
2007-02-13 19:13 ` Jason Lunz [this message]
2007-02-13 20:18 ` iwlwifi initial bugs/thanks Pavel Roskin
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=20070213191313.GA2427@metaxa.reflex \
--to=lunz@falooley.org \
--cc=ben@mw0.ath.cx \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=netdev@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).