Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 209513 - sys-fs/udev: problem renaming interface with iwl3945
Summary: sys-fs/udev: problem renaming interface with iwl3945
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Mobile Herd (OBSOLETE)
URL: https://bugs.launchpad.net/ubuntu/+so...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-10 12:54 UTC by Pacho Ramos
Modified: 2009-12-24 11:22 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
70-persistent-net.rules.iwl (70-persistent-net.rules.iwl,712 bytes, text/plain)
2008-02-10 13:51 UTC, Pacho Ramos
Details
fix-persistent-net.pl (fix-persistent-net.pl,4.95 KB, text/plain)
2009-02-06 12:47 UTC, Pacho Ramos
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Pacho Ramos gentoo-dev 2008-02-10 12:54:32 UTC
I get the following error at boot (and also I get a 20 secs delay) when udev loads iwl3945 module:
"UDEV: Your system is having problems assigning persistent names" 

After that, I don't have eth1 interface, only "wlan0_rename" (that doesn't work also for me, but this seems a different problem)

Thanks a lot

Reproducible: Always
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2008-02-10 12:59:27 UTC

*** This bug has been marked as a duplicate of bug 199512 ***
Comment 2 Pacho Ramos gentoo-dev 2008-02-10 13:51:05 UTC
I have tried removing /etc/udev/rules.d/70-persistent-net.rules and running udevtrigger, I don't suffer now the delay, but the error is still being shown

I attach the new created rule (that doesn't also work)

Comment 3 Pacho Ramos gentoo-dev 2008-02-10 13:51:19 UTC
Created attachment 143117 [details]
70-persistent-net.rules.iwl
Comment 4 Jakub Moc (RETIRED) gentoo-dev 2008-02-10 13:56:33 UTC
Which driver are you using?
Comment 5 Pacho Ramos gentoo-dev 2008-02-10 14:29:29 UTC
iwl3945, from iwlwifi (I am trying to use it instead of old ipw3945)
Comment 6 Robert A. 2008-02-14 18:22:14 UTC
removing the old udev rules for ipw3945 in /etc/udev/rules.d/70-persistent-net.rules worked for me.

in your case remove both iwl entries from the file.

hth
Comment 7 Pavel Vondricka 2008-03-07 01:02:28 UTC
I had the same problem with stable udev and bc43 wifi after I upgraded to 2.6.24. I found out that the problem was mainly the necessity to get another (newer) version of firmware for b43, not only the rules. Maybe this should be mentioned somewhere too.
Comment 8 Laux 2008-10-24 10:01:17 UTC
(In reply to comment #7)
> I had the same problem with stable udev and bc43 wifi after I upgraded to
> 2.6.24. I found out that the problem was mainly the necessity to get another
> (newer) version of firmware for b43, not only the rules. Maybe this should be
> mentioned somewhere too.
> 
I've just solved this probem on my laptop (I think works for iwl3945 too), you have to del previous line in 70-persistent-net.rules.iwl for your old BCM43xx drivers, so udev will write correct line for you at next boot. I remember you the new driver works different from previous, also works fine!
This is mine, created at boot by udev:

# PCI device 0x14e4:0x4320 (b43-pci-bridge)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:90:4b:9e:f4:b0", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"




Comment 9 Pacho Ramos gentoo-dev 2009-02-06 11:56:56 UTC
This seems to be a common problem when updating from ipw3945 to iwlwifi:
http://wiki.debian.org/iwlwifi#head-c9ab967d827d9e5de52656b78edab5f349bc70f6

but I am not sure if there would be an "automagic" way for removing all lines automatically... :-/
Comment 10 Pacho Ramos gentoo-dev 2009-02-06 12:47:49 UTC
Created attachment 181149 [details]
fix-persistent-net.pl

Ubuntu is running this script for adding ADDR{type}=="1" to 70-persistent-net.rules when possible as can be read in its changelog:



This bug was fixed in the package udev - 117-6

---------------
udev (117-6) hardy; urgency=low

  * Automatically add ADDR{type}=="1" to 70-persistent-net.rules rules
    where we can or at least add a useful comment where the user has written
    their own rule that's broken in the same way. LP: #183968.
  * Automatically comment out rules from 70-persistent-net.rules that would
    match any device.

 -- Scott James Remnant <scott@ubuntu.com> Thu, 10 Apr 2008 23:49:41 +0100

But I cannot test as I no longer have old rules :-/
Comment 11 Pacho Ramos gentoo-dev 2009-12-24 11:22:18 UTC
I think that this can be closed as udev already shows tips about "persistent-net-rules" problem