kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #02791
[Bug 1097519] Re: Wrong driver used for older Broadcom chipsets
So, after a bit of hacking around, I was able to get my BCM4313 working
with the latest bcmwl-6.30.223.30 and the latest kernel 3.10.0.
I think the main problem that I originally had, and that others
( https://mail.gnome.org/archives/networkmanager-list/2013-February/msg00125.html )
started having was due to the bcmwl driver changing to use API=CFG80211 (the current make default) instead of API=WEXT, which I assume it was using before? Well, switching back to WEXT made things work for me.
Getting it to compile with 3.10.0 was an additional tangential hurdle --
the function "create_proc_entry" no longer exists. Perhaps something
like this should do the trick:
--- wl_linux.c 2013-07-31 21:28:10.000000000 -0400
+++ /sloppyhacked/wl_linux.c 2013-07-31 23:18:22.000000000 -0400
@@ -3461,19 +3461,27 @@
return length;
}
+static const struct file_operations wlp_fops = {
+ .owner = THIS_MODULE,
+ .read = wl_proc_read,
+ .write = wl_proc_write
+};
+
static int
wl_reg_proc_entry(wl_info_t *wl)
{
char tmp[32];
sprintf(tmp, "%s%d", HYBRID_PROC, wl->pub->unit);
- if ((wl->proc_entry = create_proc_entry(tmp, 0644, NULL)) == NULL) {
+ if ((wl->proc_entry = proc_create(tmp, 0644, NULL, &wlp_fops)) == NULL) {
WL_ERROR(("%s: create_proc_entry %s failed\n", __FUNCTION__, tmp));
ASSERT(0);
return -1;
}
+/*
wl->proc_entry->read_proc = wl_proc_read;
wl->proc_entry->write_proc = wl_proc_write;
wl->proc_entry->data = wl;
+*/
return 0;
}
#ifdef WLOFFLD
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1097519
Title:
Wrong driver used for older Broadcom chipsets
Status in “bcmwl” package in Ubuntu:
Confirmed
Status in “ubuntu-drivers-common” package in Ubuntu:
Confirmed
Bug description:
On upgrade to 13.04, the wl.ko, package bcmwl-kernel-source drier is
selected.
This driver does not allow the computer to boot and causes great pain in recovery for users, most of which will not be able to get the Ubuntu installation functional
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1097509
Instead use the driver brcmsmac, that actually works with BCM4313
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.7.0-7-generic 3.7.0-7.15
ProcVersionSignature: Ubuntu 3.7.0-7.15-generic 3.7.0
Uname: Linux 3.7.0-7-generic i686
ApportVersion: 2.7-0ubuntu2
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: foxyboy 1904 F.... pulseaudio
Date: Tue Jan 8 15:36:51 2013
HibernationDevice: RESUME=UUID=695c8efa-91da-424d-983e-cc08dd01eba3
MachineType: LENOVO 20040M18
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-7-generic root=UUID=8b809c57-f15a-464f-a7a9-fafb8abaa715 ro quiet
RelatedPackageVersions:
linux-restricted-modules-3.7.0-7-generic N/A
linux-backports-modules-3.7.0-7-generic N/A
linux-firmware 1.99
SourcePackage: linux
UpgradeStatus: Upgraded to raring on 2013-01-08 (0 days ago)
dmi.bios.date: 08/30/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 24CN62WW
dmi.board.name: Caucasus2
dmi.board.vendor: LENOVO
dmi.board.version: Rev 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Lenovo
dmi.chassis.version: Rev 1.0
dmi.modalias: dmi:bvnLENOVO:bvr24CN62WW:bd08/30/2010:svnLENOVO:pn20040M18:pvrLenovoIdeapadS10-3t:rvnLENOVO:rnCaucasus2:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0:
dmi.product.name: 20040M18
dmi.product.version: Lenovo Ideapad S10-3t
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1097519/+subscriptions