Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#24754 - [netcfg] strange warning about nl80211 but works anyway

Attached to Project: Arch Linux
Opened by Philipp (hollunder) - Friday, 17 June 2011, 10:27 GMT
Last edited by Rémy Oudompheng (remyoudompheng) - Saturday, 30 July 2011, 19:11 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Rémy Oudompheng (remyoudompheng)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
nl80211: 'nl80211' generic netlink not found

Additional info:
* package version(s)
netcfg v2.5.5
b43-firmware 4.178.10.4-1
broadcom-wifi-builder 5.100.82.38-1

* config and/or log files etc.
CONNECTION='wireless'
DESCRIPTION='router'
INTERFACE='wlan0'
ESSID='myessid'
SECURITY='wpa'
KEY='censored'
IP='dhcp'
QUIRKS=(prescan)
TIMEOUT=10

Steps to reproduce:
I simply start netcfg with a wlan profile.
The module isn't loaded and can't be loaded manually, seems like it doesn't exist. No idea what tries to load it and why.
This task depends upon

Closed by  Rémy Oudompheng (remyoudompheng)
Saturday, 30 July 2011, 19:11 GMT
Reason for closing:  Not a bug
Comment by Rémy Oudompheng (remyoudompheng) - Monday, 20 June 2011, 06:15 GMT
Do you also see the message with the "iw" command? It might be a "feature" of your particular driver.
Comment by Ion Mudreac (mudrii) - Friday, 24 June 2011, 20:41 GMT
same issue running on wirless
nl80211: 'nl80211' generic netlink not found
and find a libk to the forum with the same problem
https://bbs.archlinux.org/viewtopic.php?pid=940669

as a driver used is broadcom-wl

issue can be related to wpa_supplicant
Comment by Leonid Isaev (lisaev) - Thursday, 14 July 2011, 20:14 GMT
And, as it was mentioned in comment #6 of the above link, this is a non-issue, because your wpa_supplicant falls back to wext.

Loading...