You are not logged in.

#26 2012-09-10 14:41:11

twelveeighty
Member
From: Alberta, Canada
Registered: 2011-09-04
Posts: 309

Re: [SOLVED] Drivers for Broadcom 4365 WiFi module (Dell Vostro 3560)

Crap - I'm running into some "n00b" problems. AUR won't let me submit the package without a "URL" type source. The problem is that I do not have the original upstream source URL. The only thing I have is is the .deb link from this semprefidelis.pl site. So, I just turned that into a source tar ball, but AUR won't let me submit it as such.

I'll post in the AUR forum to see what our options are.

OK - proof that this is my official first submission to AUR: it was simply complaining about the missing URL variable in the PKGBUILD, which I pointed to this forum msg. Problem fixed

Package uploaded successfully. Here is the link:

https://aur.archlinux.org/packages.php?ID=62666

Last edited by twelveeighty (2012-09-10 14:51:30)

Offline

#27 2012-09-10 17:17:25

b3niup
Member
Registered: 2012-07-26
Posts: 13

Re: [SOLVED] Drivers for Broadcom 4365 WiFi module (Dell Vostro 3560)

twelveeighty wrote:

Crap - I'm running into some "n00b" problems. AUR won't let me submit the package without a "URL" type source. The problem is that I do not have the original upstream source URL. The only thing I have is is the .deb link from this semprefidelis.pl site. So, I just turned that into a source tar ball, but AUR won't let me submit it as such.

I'll post in the AUR forum to see what our options are.

OK - proof that this is my official first submission to AUR: it was simply complaining about the missing URL variable in the PKGBUILD, which I pointed to this forum msg. Problem fixed

Package uploaded successfully. Here is the link:

https://aur.archlinux.org/packages.php?ID=62666


Great job, thanks!

Offline

#28 2012-10-16 06:46:00

tuxuls
Member
Registered: 2012-09-29
Posts: 15

Re: [SOLVED] Drivers for Broadcom 4365 WiFi module (Dell Vostro 3560)

is this module work under linux 3.6?
i have trobles to start my notebook with this aur-package and linux3.6 from core (core/linux 3.6.2-1)

can you help me? thanks

Offline

#29 2012-10-16 14:31:33

twelveeighty
Member
From: Alberta, Canada
Registered: 2011-09-04
Posts: 309

Re: [SOLVED] Drivers for Broadcom 4365 WiFi module (Dell Vostro 3560)

tuxuls wrote:

i have trobles to start my notebook with this aur-package and linux3.6 from core (core/linux 3.6.2-1)

My mirror hasn't caught up with the kernel yet to 3.6 so it's still running 3.5. I guess it's possible that the driver breaks in 3.6, but is your dkms.service running? Please provide some logs, etc. so we can help.

Offline

#30 2012-10-16 20:31:12

tuxuls
Member
Registered: 2012-09-29
Posts: 15

Re: [SOLVED] Drivers for Broadcom 4365 WiFi module (Dell Vostro 3560)

I had to uninstall broadcom-wl (dkms uninstall) because the system flatly went into kernel-panic. Tell me, what files, logs should show you?

Offline

#31 2012-10-16 21:00:37

tuxuls
Member
Registered: 2012-09-29
Posts: 15

Re: [SOLVED] Drivers for Broadcom 4365 WiFi module (Dell Vostro 3560)

something stange. I reinstall aur package.

sudo lspci -s 02:00.0 -vv
02:00.0 Network controller: Broadcom Corporation BCM43142 802.11b/g/n (rev 01)
	Subsystem: Dell Wireless 1704 802.11n + BT 4.0
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at f1500000 (64-bit, non-prefetchable) [size=32K]
	Capabilities: [40] Power Management version 3
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=2 PME-
	Capabilities: [58] Vendor Specific Information: Len=78 <?>
	Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
		Address: 0000000000000000  Data: 0000
	Capabilities: [d0] Express (v1) Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited
			ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend-
		LnkCap:	Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <4us, L1 <64us
			ClockPM+ Surprise- LLActRep- BwNot-
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+
			ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
	Capabilities: [100 v1] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
		AERCap:	First Error Pointer: 14, GenCap+ CGenEn- ChkCap+ ChkEn-
	Capabilities: [13c v1] Virtual Channel
		Caps:	LPEVC=0 RefClk=100ns PATEntryBits=1
		Arb:	Fixed- WRR32- WRR64- WRR128-
		Ctrl:	ArbSelect=Fixed
		Status:	InProgress-
		VC0:	Caps:	PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
			Arb:	Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
			Ctrl:	Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
			Status:	NegoPending- InProgress-
	Capabilities: [160 v1] Device Serial Number 00-00-85-ff-ff-c3-c0-18
	Capabilities: [16c v1] Power Budgeting <?>
iwconfig
eth0      no wireless extensions.

lo        no wireless extensions.
rfkill list
4: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no

no wifi , only bluetooth.. and,, no kernek panic ..

Offline

#32 2012-10-17 02:35:25

twelveeighty
Member
From: Alberta, Canada
Registered: 2011-09-04
Posts: 309

Re: [SOLVED] Drivers for Broadcom 4365 WiFi module (Dell Vostro 3560)

It could be the same problem that is reported in the broadcom-wl 5.100.82.112-8 package on AUR (https://aur.archlinux.org/packages.php? … mments=all).

If that's the case, this is not good news... It appears something very specific to 3.6 is introduced and the code for wl_cfg80211.c needs to be changed to reflect the changes to the kernel.

Last edited by twelveeighty (2012-10-17 03:09:55)

Offline

#33 2012-10-17 04:28:38

twelveeighty
Member
From: Alberta, Canada
Registered: 2011-09-04
Posts: 309

Re: [SOLVED] Drivers for Broadcom 4365 WiFi module (Dell Vostro 3560)

Okay - last minute update.

I have made a couple of patches and uploaded a new version to AUR (rel 3)... Now, I have NOT been able to test this AT ALL, but please try and see if that one works. Until I upgrade this laptop to 3.6, I can't test it, but please let me know if this fixes the problem.

I did the same thing as the guys did for the other broadcom driver, this latest version will ONLY work on kernel 3.6 and higher, no longer on 3.5....

Offline

#34 2012-10-17 06:10:29

tuxuls
Member
Registered: 2012-09-29
Posts: 15

Re: [SOLVED] Drivers for Broadcom 4365 WiFi module (Dell Vostro 3560)

Ok, i'm try it. Thanks!

Offline

#35 2012-10-17 06:18:56

tuxuls
Member
Registered: 2012-09-29
Posts: 15

Re: [SOLVED] Drivers for Broadcom 4365 WiFi module (Dell Vostro 3560)

$ export LANG=en_US && sudo dkms install broadcom-wl/6.20.55.19 

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area....
make KERNELRELEASE=3.6.2-1-ARCH....(bad exit status: 2)
Error! Bad return status for module build on kernel: 3.6.2-1-ARCH (x86_64)
Consult /var/lib/dkms/broadcom-wl/6.20.55.19/build/make.log for more information.

$ cat /var/lib/dkms/broadcom-wl/6.20.55.19/build/make.log

DKMS make.log for broadcom-wl-6.20.55.19 for kernel 3.6.2-1-ARCH (x86_64)
Wed Oct 17 09:17:55 EEST 2012
CFG80211 API is prefered for this kernel version
Makefile:73: Neither CFG80211 nor Wireless Extension is enabled in kernel
KBUILD_NOPEDANTIC=1 make -C /lib/modules/`uname -r`/build M=`pwd`
make[1]: Entering directory `/usr/src/linux-3.6.2-1-ARCH'
CFG80211 API is prefered for this kernel version
Using CFG80211 API
  LD      /var/lib/dkms/broadcom-wl/6.20.55.19/build/built-in.o
  CC [M]  /var/lib/dkms/broadcom-wl/6.20.55.19/build/src/shared/linux_osl.o
  CC [M]  /var/lib/dkms/broadcom-wl/6.20.55.19/build/src/wl/sys/wl_linux.o
  CC [M]  /var/lib/dkms/broadcom-wl/6.20.55.19/build/src/wl/sys/wl_iw.o
  CC [M]  /var/lib/dkms/broadcom-wl/6.20.55.19/build/src/wl/sys/wl_cfg80211.o
/var/lib/dkms/broadcom-wl/6.20.55.19/build/src/wl/sys/wl_cfg80211.c: In function 'wl_cfg80211_scan':
/var/lib/dkms/broadcom-wl/6.20.55.19/build/src/wl/sys/wl_cfg80211.c:489:21: error: 'ndev' redeclared as different kind of symbol
/var/lib/dkms/broadcom-wl/6.20.55.19/build/src/wl/sys/wl_cfg80211.c:485:58: note: previous definition of 'ndev' was here
/var/lib/dkms/broadcom-wl/6.20.55.19/build/src/wl/sys/wl_cfg80211.c: At top level:
/var/lib/dkms/broadcom-wl/6.20.55.19/build/src/wl/sys/wl_cfg80211.c:1561:2: warning: initialization from incompatible pointer type [enabled by default]
/var/lib/dkms/broadcom-wl/6.20.55.19/build/src/wl/sys/wl_cfg80211.c:1561:2: warning: (near initialization for 'wl_cfg80211_ops.scan') [enabled by default]
make[2]: *** [/var/lib/dkms/broadcom-wl/6.20.55.19/build/src/wl/sys/wl_cfg80211.o] Error 1
make[1]: *** [_module_/var/lib/dkms/broadcom-wl/6.20.55.19/build] Error 2
make[1]: Leaving directory `/usr/src/linux-3.6.2-1-ARCH'
make: *** [all] Error 2

can't build module

Offline

#36 2012-10-17 13:49:35

twelveeighty
Member
From: Alberta, Canada
Registered: 2011-09-04
Posts: 309

Re: [SOLVED] Drivers for Broadcom 4365 WiFi module (Dell Vostro 3560)

Yes, I realized last night I forgot to change the important part: the parameter change. I missed changing the parameters to the wl_cfg80211_scan function. The latest rel posted to AUR should fix this. I don't have a 3.6 kernel yet to test, so please post back with results.

Offline

#37 2012-10-17 16:10:38

tuxuls
Member
Registered: 2012-09-29
Posts: 15

Re: [SOLVED] Drivers for Broadcom 4365 WiFi module (Dell Vostro 3560)

Yeah, man! It's works! I am writing connected with WiFi. Thank you!

Last edited by tuxuls (2012-10-17 19:01:07)

Offline

#38 2012-10-20 18:48:52

HeshamSL65
Member
From: Cairo, Egypt
Registered: 2012-10-20
Posts: 1

Re: [SOLVED] Drivers for Broadcom 4365 WiFi module (Dell Vostro 3560)

Well I am not (yet ?) in the ArchLinux territory, but nevertheless thanks to your patch I could as well successfully put this card to work in a kernel 3.6.2 Debian-based system (Linux Mint Maya 13, only a matter of packaging). This is more than great for today, but worrying for tomorrow as long as Broadcom kept getting late behind kernel progressing and kept the source closed.

Anyway, for any one who stumbles upon this page in searching for a working driver to his Debian system (Ubuntu/Mint/etc) with 3.6.2 kernel, I have prepared a Debian package which you can try here if it works for you.

Thank you very much again for your wonderful work guys

Last edited by HeshamSL65 (2012-10-20 18:50:39)

Offline

#39 2012-10-21 02:04:48

twelveeighty
Member
From: Alberta, Canada
Registered: 2011-09-04
Posts: 309

Re: [SOLVED] Drivers for Broadcom 4365 WiFi module (Dell Vostro 3560)

No problem. This is how open source is supposed to work!

Broadcom sucks. For those reading this thread before they bough their hardware: don't buy Dell, or see if you can change the card as an option. Don't be fooled like us :-) Or better yet: be vocal about it, call Dell, Broadcom and complain about their terrible support for Linux. Dell is alright, but putting a card like this in it, that should have never happened in this day and age.
/rant

Offline

#40 2012-10-25 15:44:17

patseb
Member
Registered: 2012-10-23
Posts: 6

Re: [SOLVED] Drivers for Broadcom 4365 WiFi module (Dell Vostro 3560)

Hello all,
Unfortunately I also have Dell Vostro 3460 with BCM 4365 WiFi module.
I've installed these drivers successfully (on Linux 3.5.4) and it's working somehow fine, except that WiFi sometimes won't start.
Sometime I have to reboot 3 times notebook to force WiFi working, before that I've got errors:
[   20.760931] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
or some ioctl unsupported functions...
Anybody has the same problems?

Offline

#41 2012-10-26 21:10:22

twelveeighty
Member
From: Alberta, Canada
Registered: 2011-09-04
Posts: 309

Re: [SOLVED] Drivers for Broadcom 4365 WiFi module (Dell Vostro 3560)

patseb wrote:

Hello all,
I've installed these drivers successfully (on Linux 3.5.4) and it's working somehow fine, except that WiFi sometimes won't start.

Do you mean you're running the one from the AUR? How is that possible, it's dependent on Linux >= 3.6? If you somehow forced it to install on 3.5, I would not be surprised that you have issues with scanning for networks, since that was changed for Linux 3.6...

Offline

#42 2012-10-27 07:18:21

patseb
Member
Registered: 2012-10-23
Posts: 6

Re: [SOLVED] Drivers for Broadcom 4365 WiFi module (Dell Vostro 3560)

No. I've installed package from AUR when it was for Linux 3.5. I didn't upgrade kernel and I'm using netcfg
Everything works fine, except that sometimes (after cold start) I cannot connect at all.
Today I've dumped one of outputs which I get when I cannot connect (other one is with scanning):

nl80211: Could not configure driver to use managed mode
ioctl[SIOCSIWMODE]: Operation not supported
ioctl[SIOCGIWRANGE]: Operation not supported
ioctl[SIOCGIWMODE]: Operation not supported
ioctl[SIOCSIWAP]: Operation not supported
ioctl[SIOCSIWESSID]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODE]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODE]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODE]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODE]: Operation not supported

Last edited by patseb (2012-10-27 07:19:04)

Offline

#43 2013-01-08 03:06:33

WindPower
Member
Registered: 2012-09-06
Posts: 12

Re: [SOLVED] Drivers for Broadcom 4365 WiFi module (Dell Vostro 3560)

Sorry to bump this but I'm having the same problem as patseb:

- Dell Vostro 2520 BTX. I do not recommend this laptop to anyone ever. I only bought it because there was a one-day deal that made it really really cheap and I needed a laptop for a small amount of time. I didn't research Linux compatibility because it was a one-day offer and it came preloaded with Ubuntu so I assumed it'd all "just work". Oh how wrong I was.
- Kernel: 3.6.11-1 x86_64 running, linux and linux-headers packages having the same version
- Broadcom Corporation BCM43142 802.11b/g/n [14e4:4365]
- PKGBUILD from today (which looks like this by the way, for future folks stumbling upon this topic)
- No build errors

Module loads fine, wireless device gets detected and shows up in NetworkManager, but whenever it tries to scan, the following appears in dmesg:

ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)

And no network show up in the network list.

Last edited by WindPower (2013-01-08 04:51:20)

Offline

#44 2013-01-08 04:43:29

twelveeighty
Member
From: Alberta, Canada
Registered: 2011-09-04
Posts: 309

Re: [SOLVED] Drivers for Broadcom 4365 WiFi module (Dell Vostro 3560)

Sorry all - I wasn't aware the AUR package was flagged out-of-date. I'll need to look at the suggested changes. I actually had obtained a more reliable upstream source a while ago but got too busy with work to change this package; even though he/she is not Broadcom, this upstream maintainer takes this driver seriously so that would be a much better solution.

@WindPower: you seem to have the same card as the rest of us, although I think most of us have the Dell Vostro, not the 2520. I have the exact same kernel and wireless works fine here. Can you show the output of "dmesg | grep wl". Mine says:

[    6.124850] wl: module license 'Mixed/Proprietary' taints kernel.
[    6.155179] INFO @wl_cfg80211_attach : Registered CFG80211 phy

Offline

#45 2013-01-08 04:55:28

WindPower
Member
Registered: 2012-09-06
Posts: 12

Re: [SOLVED] Drivers for Broadcom 4365 WiFi module (Dell Vostro 3560)

twelveeighty wrote:

Sorry all - I wasn't aware the AUR package was flagged out-of-date. I'll need to look at the suggested changes. I actually had obtained a more reliable upstream source a while ago but got too busy with work to change this package; even though he/she is not Broadcom, this upstream maintainer takes this driver seriously so that would be a much better solution.

@WindPower: you seem to have the same card as the rest of us, although I think most of us have the Dell Vostro, not the 2520. I have the exact same kernel and wireless works fine here. Can you show the output of "dmesg | grep wl". Mine says:

[    6.124850] wl: module license 'Mixed/Proprietary' taints kernel.
[    6.155179] INFO @wl_cfg80211_attach : Registered CFG80211 phy

I get the same output (plus the "ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)" lines)

Edit: Also, I never connected to the Internet using the preloaded copy of Ubuntu that came on it, but I did see that it successfully listed the wireless access points around me, so I know that whatever driver the (now-wiped) preloaded Ubuntu was using works fine for scanning.

Last edited by WindPower (2013-01-08 05:00:09)

Offline

#46 2013-01-08 05:13:19

twelveeighty
Member
From: Alberta, Canada
Registered: 2011-09-04
Posts: 309

Re: [SOLVED] Drivers for Broadcom 4365 WiFi module (Dell Vostro 3560)

I did some Googling and I wonder if you are having problems related to the infamous eth0 - eth1 issues where udev and the driver are fighting (see https://wiki.archlinux.org/index.php/Re … nterfaces). On my machine, I have set up a /etc/udev/rules.d/10-network.rules as described in the Wiki.

Check your /var/log/messages.log. First look for the kernel / systemd-udevd messages and then the NetworkManager initialization entries. On my machine, with the udev rules file in place, it looks like this with a Ethernet cable connected at boot time:

...
Jan  7 18:10:05 localhost kernel: [    6.124850] wl: module license 'Mixed/Proprietary' taints kernel.
Jan  7 18:10:05 localhost kernel: [    6.124856] Disabling lock debugging due to kernel taint
Jan  7 18:10:05 localhost kernel: [    6.142797] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
Jan  7 18:10:05 localhost kernel: [    6.144030] r8169 0000:01:00.0: eth0: RTL8168evl/8111evl at 0xffffc90000c6a000, d4:be:d9:55:4e:2a, XID 0c900800 IRQ 44
Jan  7 18:10:05 localhost kernel: [    6.144032] r8169 0000:01:00.0: eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
Jan  7 18:10:05 localhost [    6.155162] systemd-udevd[156]: renamed network interface eth0 to net0
Jan  7 18:10:05 localhost kernel: [    6.195023] eth0: Broadcom BCM4365 802.11 Hybrid Wireless Controller 6.20.55.19 (r300276)
Jan  7 18:10:05 localhost [    6.198442] systemd-udevd[160]: renamed network interface eth0 to wifi0
...
Jan  7 18:10:12 localhost systemd[1]: Started Authorization Manager.
Jan  7 18:10:12 localhost NetworkManager[418]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
...
Jan  7 18:10:13 localhost NetworkManager[418]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.1/0000:02:00.0/ieee80211/phy0/rfkill0) (driver wl)
Jan  7 18:10:13 localhost systemd[1]: Started Network Manager.
Jan  7 18:10:13 localhost systemd[1]: Starting Network.
...
Jan  7 18:10:13 localhost NetworkManager[418]: <info> WiFi enabled by radio killswitch; enabled by state file
...
Jan  7 18:10:13 localhost NetworkManager[418]: <info> (net0): new Ethernet device (driver: 'r8169' ifindex: 2)
Jan  7 18:10:13 localhost NetworkManager[418]: <info> (net0): exported as /org/freedesktop/NetworkManager/Devices/0
Jan  7 18:10:13 localhost NetworkManager[418]: <info> (net0): now managed
...
Jan  7 18:10:13 localhost NetworkManager[418]: <info> (wifi0): using nl80211 for WiFi device control
Jan  7 18:10:13 localhost NetworkManager[418]: <info> (wifi0): new 802.11 WiFi device (driver: 'wl' ifindex: 3)
Jan  7 18:10:13 localhost NetworkManager[418]: <info> (wifi0): exported as /org/freedesktop/NetworkManager/Devices/1
Jan  7 18:10:13 localhost NetworkManager[418]: <info> (wifi0): now managed
Jan  7 18:10:13 localhost NetworkManager[418]: <info> (wifi0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Jan  7 18:10:13 localhost NetworkManager[418]: <info> (wifi0): bringing up device.
Jan  7 18:10:13 localhost NetworkManager[418]: <info> (wifi0): preparing device.
Jan  7 18:10:13 localhost NetworkManager[418]: <info> (wifi0): deactivating device (reason 'managed') [2]
Jan  7 18:10:13 localhost dbus[422]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service'
...
Jan  7 18:10:13 localhost NetworkManager[418]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
Jan  7 18:10:13 localhost NetworkManager[418]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
Jan  7 18:10:13 localhost dbus-daemon[422]: dbus[422]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service'
Jan  7 18:10:13 localhost systemd[1]: Starting WPA supplicant...
Jan  7 18:10:13 localhost dbus-daemon[422]: dbus[422]: [system] Successfully activated service 'fi.w1.wpa_supplicant1'
Jan  7 18:10:13 localhost dbus[422]: [system] Successfully activated service 'fi.w1.wpa_supplicant1'
Jan  7 18:10:13 localhost NetworkManager[418]: <info> wpa_supplicant started
Jan  7 18:10:13 localhost systemd[1]: Started WPA supplicant.
Jan  7 18:10:13 localhost NetworkManager[418]: <info> (wifi0) supports 1 scan SSIDs
Jan  7 18:10:13 localhost NetworkManager[418]: <info> (wifi0): supplicant interface state: starting -> ready
Jan  7 18:10:13 localhost NetworkManager[418]: <info> (wifi0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Jan  7 18:10:13 localhost NetworkManager[418]: <warn> Trying to remove a non-existant call id.
Jan  7 18:10:13 localhost NetworkManager[418]: <info> (wifi0): supplicant interface state: ready -> inactive
Jan  7 18:10:13 localhost NetworkManager[418]: <info> (wifi0) supports 1 scan SSIDs
...

Offline

#47 2013-01-08 05:51:35

WindPower
Member
Registered: 2012-09-06
Posts: 12

Re: [SOLVED] Drivers for Broadcom 4365 WiFi module (Dell Vostro 3560)

I added a file at /etc/udev/rules.d/10-network.rules that renames the wireless interface to wifi0 and the Ethernet interface to wired0. It matches by MAC address, not by interface name. NetworkManager picks up the change and still sees both interfaces, and successfully connects over Ethernet.

Here's a log from a boot after this change has been made. Interestingly, there are some other errors in there (Ctrl+F "nl80211_wiphy_info_handler" or "real_update_permanent_hw_address"). I searched logs from old boots (prior to having the udev rules) and those show up there as well.

...
Jan 07 18:31:30 crapola kernel: Linux version 3.6.11-1-ARCH (tobias@T-POWA-LX) (gcc version 4.7.2 (GCC) ) #1 SMP PREEMPT Tue Dec 18 08:57:15 CET 2012
Jan 07 18:31:30 crapola kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=18edfadc-a486-47bb-a0b2-06074b9d9c5f ro cryptdevice=/dev/sda3:root quiet
...
Jan 07 18:31:32 crapola kernel: wl: module license 'Mixed/Proprietary' taints kernel.
Jan 07 18:31:32 crapola kernel: Disabling lock debugging due to kernel taint
Jan 07 18:31:32 crapola kernel: INFO @wl_cfg80211_attach : Registered CFG80211 phy
Jan 07 18:31:32 crapola kernel: scsi6 : usb-storage 2-1.6:1.0
Jan 07 18:31:32 crapola kernel: usbcore: registered new interface driver ums-realtek
Jan 07 18:31:32 crapola kernel: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
Jan 07 18:31:32 crapola kernel: r8169 0000:09:00.0: irq 43 for MSI/MSI-X
Jan 07 18:31:32 crapola kernel: r8169 0000:09:00.0: eth1: RTL8168evl/8111evl at 0xffffc90000664000, e0:db:55:8e:e3:2d, XID 0c900800 IRQ 43
Jan 07 18:31:32 crapola kernel: r8169 0000:09:00.0: eth1: jumbo features [frames: 9200 bytes, tx checksumming: ko]
Jan 07 18:31:32 crapola systemd-udevd[207]: renamed network interface eth1 to wired0
Jan 07 18:31:32 crapola kernel: lib80211_crypt: registered algorithm 'TKIP'
Jan 07 18:31:32 crapola kernel: eth0: Broadcom BCM4365 802.11 Hybrid Wireless Controller 6.20.55.19 (r300276)
Jan 07 18:31:32 crapola kernel: usb 2-1.6: USB disconnect, device number 3
Jan 07 18:31:32 crapola systemd-udevd[205]: renamed network interface eth0 to wifi0
...
Jan 07 18:31:38 crapola NetworkManager[704]: <info> NetworkManager (version 0.9.6.4) is starting...
Jan 07 18:31:38 crapola NetworkManager[704]: <info> Read config file /etc/NetworkManager/NetworkManager.conf
Jan 07 18:31:38 crapola NetworkManager[704]: <info> WEXT support is enabled
Jan 07 18:31:38 crapola NetworkManager[704]: <info> VPN: loaded org.freedesktop.NetworkManager.openvpn
...
Jan 07 18:31:38 crapola systemd[1]: Started Authorization Manager.
Jan 07 18:31:38 crapola NetworkManager[704]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
Jan 07 18:31:38 crapola NetworkManager[704]: keyfile: parsing Home ...
Jan 07 18:31:38 crapola NetworkManager[704]: keyfile:     read connection 'Home' # (Note: I added this one manually by copying it from another laptop where this profile works, just to see if I could get it to connect anyway without having to scan)
Jan 07 18:31:38 crapola NetworkManager[704]: <info> trying to start the modem manager...
Jan 07 18:31:38 crapola NetworkManager[704]: <info> monitoring kernel firmware directory '/lib/firmware'.
Jan 07 18:31:38 crapola NetworkManager[704]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.3/0000:07:00.0/ieee80211/phy0/rfkill0) (driver wl)
Jan 07 18:31:38 crapola NetworkManager[704]: <info> WiFi enabled by radio killswitch; enabled by state file
Jan 07 18:31:38 crapola NetworkManager[704]: <info> WWAN enabled by radio killswitch; enabled by state file
Jan 07 18:31:38 crapola NetworkManager[704]: <info> WiMAX enabled by radio killswitch; enabled by state file
Jan 07 18:31:38 crapola NetworkManager[704]: <info> Networking is enabled by state file
Jan 07 18:31:38 crapola NetworkManager[704]: <error> [1357601498.935480] [wifi-utils-nl80211.c:669] nl80211_wiphy_info_handler(): Don't know the meaning of NL80211_ATTR_CIPHER_SUITES 0x000fac06.
Jan 07 18:31:38 crapola NetworkManager[704]: <info> (wifi0): using nl80211 for WiFi device control
Jan 07 18:31:38 crapola NetworkManager[704]: <error> [1357601498.935569] [nm-device-wifi.c:2734] real_update_permanent_hw_address(): (wifi0): unable to read permanent MAC address (error 0)
Jan 07 18:31:38 crapola NetworkManager[704]: <info> (wifi0): new 802.11 WiFi device (driver: 'wl' ifindex: 2)
Jan 07 18:31:38 crapola NetworkManager[704]: <info> (wifi0): exported as /org/freedesktop/NetworkManager/Devices/0
Jan 07 18:31:38 crapola NetworkManager[704]: <info> (wifi0): now managed
Jan 07 18:31:38 crapola NetworkManager[704]: <info> (wifi0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Jan 07 18:31:38 crapola NetworkManager[704]: <info> (wifi0): bringing up device.
Jan 07 18:31:38 crapola NetworkManager[704]: <info> (wifi0): preparing device.
Jan 07 18:31:38 crapola NetworkManager[704]: <info> (wifi0): deactivating device (reason 'managed') [2]
Jan 07 18:31:38 crapola dbus[706]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service'
Jan 07 18:31:39 crapola NetworkManager[704]: <warn> failed to allocate link cache: (-10) Operation not supported
Jan 07 18:31:39 crapola NetworkManager[704]: <info> (wired0): carrier is OFF
Jan 07 18:31:39 crapola NetworkManager[704]: <info> (wired0): new Ethernet device (driver: 'r8169' ifindex: 3)
Jan 07 18:31:39 crapola NetworkManager[704]: <info> (wired0): exported as /org/freedesktop/NetworkManager/Devices/1
Jan 07 18:31:39 crapola NetworkManager[704]: <info> (wired0): now managed
Jan 07 18:31:39 crapola NetworkManager[704]: <info> (wired0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Jan 07 18:31:39 crapola NetworkManager[704]: <info> (wired0): bringing up device.
Jan 07 18:31:38 crapola systemd[1]: Started Network Manager.
...
Jan 07 18:31:38 crapola systemd[1]: Starting Network.
Jan 07 18:31:38 crapola systemd[1]: Reached target Network.
Jan 07 18:31:38 crapola systemd[1]: Starting WPA supplicant...
Jan 07 18:31:39 crapola systemd[1]: Started Update UTMP about System Runlevel Changes.
Jan 07 18:31:39 crapola dbus-daemon[706]: dbus[706]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service'
Jan 07 18:31:39 crapola dbus-daemon[706]: dbus[706]: [system] Successfully activated service 'fi.w1.wpa_supplicant1'
Jan 07 18:31:39 crapola dbus[706]: [system] Successfully activated service 'fi.w1.wpa_supplicant1'
Jan 07 18:31:39 crapola systemd[1]: Started WPA supplicant.
Jan 07 18:31:39 crapola systemd[1]: Startup finished in 9s 667ms 381us (kernel) + 10s 89ms 718us (userspace) = 19s 757ms 99us.
Jan 07 18:31:39 crapola NetworkManager[704]: <info> (wired0): preparing device.
Jan 07 18:31:39 crapola NetworkManager[704]: <info> (wired0): deactivating device (reason 'managed') [2]
Jan 07 18:31:39 crapola NetworkManager[704]: <info> Added default wired connection 'Wired connection 1' for /sys/devices/pci0000:00/0000:00:1c.5/0000:09:00.0/net/wired0
Jan 07 18:31:39 crapola NetworkManager[704]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
Jan 07 18:31:39 crapola kernel: r8169 0000:09:00.0: wired0: link down
Jan 07 18:31:39 crapola kernel: IPv6: ADDRCONF(NETDEV_UP): wired0: link is not ready
Jan 07 18:31:39 crapola kernel: r8169 0000:09:00.0: wired0: link down
Jan 07 18:31:39 crapola NetworkManager[704]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
Jan 07 18:31:39 crapola NetworkManager[704]: <info> wpa_supplicant started
Jan 07 18:31:39 crapola NetworkManager[704]: <info> (wifi0) supports 1 scan SSIDs
Jan 07 18:31:39 crapola NetworkManager[704]: <info> (wifi0): supplicant interface state: starting -> ready
Jan 07 18:31:39 crapola NetworkManager[704]: <info> (wifi0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Jan 07 18:31:39 crapola NetworkManager[704]: <warn> Trying to remove a non-existant call id.
Jan 07 18:31:39 crapola NetworkManager[704]: <info> (wifi0): supplicant interface state: ready -> inactive
Jan 07 18:31:39 crapola NetworkManager[704]: <info> (wifi0) supports 1 scan SSIDs
Jan 07 18:31:39 crapola kernel: ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
Jan 07 18:31:41 crapola NetworkManager[704]: <info> (wired0): carrier now ON (device state 20)
Jan 07 18:31:41 crapola NetworkManager[704]: <info> (wired0): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
Jan 07 18:31:41 crapola NetworkManager[704]: <info> Auto-activating connection 'Wired connection 1'.
Jan 07 18:31:41 crapola NetworkManager[704]: <info> Activation (wired0) starting connection 'Wired connection 1'
Jan 07 18:31:41 crapola NetworkManager[704]: <info> (wired0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Jan 07 18:31:41 crapola NetworkManager[704]: <info> Activation (wired0) Stage 1 of 5 (Device Prepare) scheduled...
Jan 07 18:31:41 crapola NetworkManager[704]: <info> Activation (wired0) Stage 1 of 5 (Device Prepare) started...
Jan 07 18:31:41 crapola NetworkManager[704]: <info> Activation (wired0) Stage 2 of 5 (Device Configure) scheduled...
Jan 07 18:31:41 crapola NetworkManager[704]: <info> Activation (wired0) Stage 1 of 5 (Device Prepare) complete.
Jan 07 18:31:41 crapola NetworkManager[704]: <info> Activation (wired0) Stage 2 of 5 (Device Configure) starting...
Jan 07 18:31:41 crapola NetworkManager[704]: <info> (wired0): device state change: prepare -> config (reason 'none') [40 50 0]
Jan 07 18:31:41 crapola NetworkManager[704]: <info> Activation (wired0) Stage 2 of 5 (Device Configure) successful.
Jan 07 18:31:41 crapola NetworkManager[704]: <info> Activation (wired0) Stage 3 of 5 (IP Configure Start) scheduled.
Jan 07 18:31:41 crapola NetworkManager[704]: <info> Activation (wired0) Stage 2 of 5 (Device Configure) complete.
Jan 07 18:31:41 crapola NetworkManager[704]: <info> Activation (wired0) Stage 3 of 5 (IP Configure Start) started...
Jan 07 18:31:41 crapola NetworkManager[704]: <info> (wired0): device state change: config -> ip-config (reason 'none') [50 70 0]
Jan 07 18:31:41 crapola NetworkManager[704]: <info> Activation (wired0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Jan 07 18:31:41 crapola kernel: r8169 0000:09:00.0: wired0: link up
Jan 07 18:31:41 crapola kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wired0: link becomes ready
Jan 07 18:31:41 crapola NetworkManager[704]: <info> dhclient started with pid 1264
Jan 07 18:31:41 crapola NetworkManager[704]: <info> Activation (wired0) Beginning IP6 addrconf.
Jan 07 18:31:41 crapola NetworkManager[704]: <info> Activation (wired0) Stage 3 of 5 (IP Configure Start) complete.
Jan 07 18:31:41 crapola dhclient[1264]: Internet Systems Consortium DHCP Client 4.2.4-P2
Jan 07 18:31:41 crapola dhclient[1264]: Copyright 2004-2012 Internet Systems Consortium.
Jan 07 18:31:41 crapola dhclient[1264]: All rights reserved.
Jan 07 18:31:41 crapola dhclient[1264]: For info, please visit https://www.isc.org/software/dhcp/
Jan 07 18:31:41 crapola dhclient[1264]: 
Jan 07 18:31:41 crapola NetworkManager[704]: <info> (wired0): DHCPv4 state changed nbi -> preinit
Jan 07 18:31:41 crapola dhclient[1264]: Listening on LPF/wired0/e0:db:55:8e:e3:2d
Jan 07 18:31:41 crapola dhclient[1264]: Sending on   LPF/wired0/e0:db:55:8e:e3:2d
Jan 07 18:31:41 crapola dhclient[1264]: Sending on   Socket/fallback
Jan 07 18:31:41 crapola dhclient[1264]: DHCPDISCOVER on wired0 to 255.255.255.255 port 67 interval 8
Jan 07 18:31:41 crapola dhclient[1264]: DHCPREQUEST on wired0 to 255.255.255.255 port 67
Jan 07 18:31:41 crapola dhclient[1264]: DHCPOFFER from 192.168.1.1
Jan 07 18:31:42 crapola dhclient[1264]: DHCPACK from 192.168.1.1
Jan 07 18:31:42 crapola dhclient[1264]: bound to 192.168.1.54 -- renewal in 36749 seconds.
Jan 07 18:31:42 crapola NetworkManager[704]: <info> (wired0): DHCPv4 state changed preinit -> bound
Jan 07 18:31:42 crapola NetworkManager[704]: <info>   address 192.168.1.54
Jan 07 18:31:42 crapola NetworkManager[704]: <info>   prefix 24 (255.255.255.0)
Jan 07 18:31:42 crapola NetworkManager[704]: <info>   gateway 192.168.1.1
Jan 07 18:31:42 crapola NetworkManager[704]: <info>   nameserver '192.168.1.1'
Jan 07 18:31:42 crapola NetworkManager[704]: <info> Activation (wired0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Jan 07 18:31:42 crapola NetworkManager[704]: <info> Activation (wired0) Stage 5 of 5 (IPv4 Commit) started...
Jan 07 18:31:43 crapola NetworkManager[704]: <info> (wired0): device state change: ip-config -> activated (reason 'none') [70 100 0]
Jan 07 18:31:43 crapola NetworkManager[704]: <info> Policy set 'Wired connection 1' (wired0) as default for IPv4 routing and DNS.
Jan 07 18:31:43 crapola NetworkManager[704]: <info> Activation (wired0) successful, device activated.
Jan 07 18:31:43 crapola NetworkManager[704]: <info> Activation (wired0) Stage 5 of 5 (IPv4 Commit) complete.
Jan 07 18:31:43 crapola dbus[706]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Jan 07 18:31:43 crapola dbus-daemon[706]: dbus[706]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Jan 07 18:31:43 crapola kernel: ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
Jan 07 18:31:43 crapola dbus-daemon[706]: dbus[706]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jan 07 18:31:43 crapola dbus[706]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
...
Jan 07 18:32:01 crapola NetworkManager[704]: <info> (wired0): IP6 addrconf timed out or failed.
Jan 07 18:32:01 crapola NetworkManager[704]: <info> Activation (wired0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Jan 07 18:32:01 crapola NetworkManager[704]: <info> Activation (wired0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Jan 07 18:32:01 crapola NetworkManager[704]: <info> Activation (wired0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
...
Jan 07 18:32:06 crapola kernel: ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
Jan 07 18:32:24 crapola polkitd[1246]: Registered Authentication Agent for unix-session:1 (system bus name :1.26 [/usr/lib/kde4/libexec/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Jan 07 18:32:39 crapola kernel: ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
...
# The rest is just NetworkManager periodically trying to scan things
Jan 07 18:33:22 crapola kernel: ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
Jan 07 18:34:15 crapola kernel: ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
Jan 07 18:35:18 crapola kernel: ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
Jan 07 18:36:21 crapola kernel: ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
Jan 07 18:37:24 crapola kernel: ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
Jan 07 18:38:27 crapola kernel: ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
Jan 07 18:39:30 crapola kernel: ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
Jan 07 18:40:33 crapola kernel: ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)

You'll notice that the machine is affectionately named "crapola" because it really is a crappy laptop.

Last edited by WindPower (2013-01-08 05:56:10)

Offline

#48 2013-01-09 03:06:06

twelveeighty
Member
From: Alberta, Canada
Registered: 2011-09-04
Posts: 309

Re: [SOLVED] Drivers for Broadcom 4365 WiFi module (Dell Vostro 3560)

I'm getting in lost territory here, but I'd be willing to bet those two "nl80211_wiphy_info_handler" or "real_update_permanent_hw_address" errors are causing your problems. Google showed that the hex code 0x000FAC06 corresponds to the following:

#define WLAN_CIPHER_SUITE_AES_CMAC    0x000FAC06

I'm out of my league here, but I do know AES is an encryption method, could this perhaps just be the specific wireless router that you have set up near this laptop? Have you tried scanning wireless networks against a different wireless router, a public one, perhaps? I think that is worth a shot to test.

Offline

#49 2013-01-09 04:02:55

twelveeighty
Member
From: Alberta, Canada
Registered: 2011-09-04
Posts: 309

Re: [SOLVED] Drivers for Broadcom 4365 WiFi module (Dell Vostro 3560)

Not related to the problems @WindPower is having, there was some commotion on the AUR regarding the driver being "out of date", but here are my findings, as posted in the comment there (for those not monitoring the AUR comments):
---

Okay all, we have a problem. I downloaded the source from the link provided by @ryley (https://launchpad.net/ubuntu/raring/+source/bcmwl), and, yes, the version number of that driver is higher (6.20.155 vs the current AUR 6.20.55) BUT the source code is IDENTICAL to what we have now.
The only diffs between the source posted on launchpad and this AUR build are the ones that we need to patch out again (wl_linux.c: ndo_set_multicast_list replaced by ndo_set_rx_mode as of kernel 3.2).

So, unless you all enjoy updating this terrible driver for no reason, I would much rather not touch it. Otherwise, please post back here and I'll go through the effort of updating it if we get some votes. If not, I'll remove the "out-of-date" flag in a couple of days, deal?

I hate Broadcom so much.

Offline

#50 2013-01-09 21:22:27

WindPower
Member
Registered: 2012-09-06
Posts: 12

Re: [SOLVED] Drivers for Broadcom 4365 WiFi module (Dell Vostro 3560)

twelveeighty wrote:

I'm getting in lost territory here, but I'd be willing to bet those two "nl80211_wiphy_info_handler" or "real_update_permanent_hw_address" errors are causing your problems. Google showed that the hex code 0x000FAC06 corresponds to the following:

#define WLAN_CIPHER_SUITE_AES_CMAC    0x000FAC06

I'm out of my league here, but I do know AES is an encryption method, could this perhaps just be the specific wireless router that you have set up near this laptop? Have you tried scanning wireless networks against a different wireless router, a public one, perhaps? I think that is worth a shot to test.

I don't think that's the problem; they look like regular issues with NetworkManager specifically. So I tried removing NetworkManager which made these two errors go away, and instead I tried to use netcfg to connect. Unfortunately, the original error ("ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)") shows up again in the log as soon as netcfg tries connecting to the wireless network. I also tried setting HIDDEN='yes' in an attempt to make it not scan for networks, but unfortunately it tries to scan anyway and the error shows up again in the logs.

Last edited by WindPower (2013-01-09 22:26:10)

Offline

Board footer

Powered by FluxBB