| View previous topic :: View next topic |
| Author |
Message |
gep642
n00b
Joined: 12 Sep 2007
Posts: 9
|
 Posted: Fri Oct 12, 2007 9:07 pm Post subject: [Solved] B43 module: Problem assigning persistent names |
 |
|
When I boot my computer (using the 2.6.23-rc8-mm2 kernel), it takes a while while loading the b43 module (5-10 seconds), then gives me this:
| Quote: | * UDEV: Your system has a problem assigning persistent names
* to these network interfaces: wmaster0_rename
* Checking persistent-net rules:
* Found no duplicate names in persistent-net rules,
* there must be some other problem! |
I checked dmesg after I finished booting and saw:
| Quote: | b43-phy0: Broadcom 4306 WLAN found
phy0: Selected rate control algorithm 'simple'
wmaster0 renamed to wmaster0_rename
sysfs: duplicate filename 'wmaster0_rename' can not be created
WARNING: at fs/sysfs/dir.c:433 sysfs_add_one()
[<c01042cc>] dump_trace+0x66/0x1d0
[<c010444e>] show_trace_log_lvl+0x18/0x2c
[<c0104ceb>] show_trace+0xf/0x11
[<c0104dc7>] dump_stack+0x11/0x13
[<c0181229>] sysfs_add_one+0x54/0xb7
[<c0181d89>] sysfs_create_link+0x9a/0x109
[<c0271319>] device_rename+0x138/0x191
[<c02f89c6>] dev_change_name+0x13a/0x1fb
[<c02f916c>] dev_ioctl+0x32d/0x42b
[<c0158f2d>] do_ioctl+0x19/0x4d
[<c0159156>] vfs_ioctl+0x1f5/0x20c
[<c01591a0>] sys_ioctl+0x33/0x4b
[<c0103bc2>] sysenter_past_esp+0x5f/0x85
[<b7fb4410>] 0xb7fb4410
=======================
net wmaster0_rename: device_rename: sysfs_create_symlink failed (-17) |
Any idea why this is happening? Is this the right place to even ask?
Also, I tried the 2.6.23-mm1 kernel (to see if it would go away), got the same error, but my wireless LED wouldn't come on when my card was active, so I went back to this one. Is there somewhere I could report that bug (I assume it's a bug)?
Edit: BTW, my card is working (and better than it did in 2.6.22, at that), despite this error.
Last edited by gep642 on Wed Nov 28, 2007 4:26 am; edited 1 time in total |
|
| Back to top |
|
 |
gep642
n00b
Joined: 12 Sep 2007
Posts: 9
|
| Posted: Sun Oct 14, 2007 4:54 pm Post subject: |
|
|
| Bump? |
|
| Back to top |
|
|
b33fc0d3
Retired Dev
Joined: 22 Jun 2006
Posts: 128
|
|
| Back to top |
|
|
gep642
n00b
Joined: 12 Sep 2007
Posts: 9
|
| Posted: Wed Nov 28, 2007 4:26 am Post subject: |
|
|
| Well, I figured it out. I had assigned a name in my persistent net rules to my wireless card, when I deleted that, the error went away and my computer booted well again. |
|
| Back to top |
|
|
kiksen
Guru
Joined: 24 Jun 2002
Posts: 401
Location: Denmark
|
| Posted: Wed Jan 16, 2008 4:56 pm Post subject: |
|
|
I was experiencing the same problem on a fully updated ~x86 system. Although I haven't made any udev rules myself and always keep my configuration updated with dispatch-conf, removing rules.d/* and remerging udev fixed it.
Something is not updated correctly when updating udev?
/kiksen |
|
| Back to top |
|
|
coolsnowmen
Veteran
Joined: 30 Jun 2004
Posts: 1479
Location: No.VA
|
| Posted: Thu Jan 17, 2008 8:25 pm Post subject: |
|
|
had name problems which were causing HUGE bootup delays!!
removing the rules.d directory then reemerge udev worked, thank you for this post
_________________
emerge: there are no ebuilds to satisfy "moo" |
|
| Back to top |
|
|
|
Kernel & Hardware
