Why is this assigned to bcmwl?
OP problem seems to be the kernel thinking that no RAM is available
(making OOM Killer kill everything).
Even if 32GB RAM are present the kernel command line has all these weird
options:
irqpoll maxcpus=1 nousb memmap=exactmap memmap=577K@4K
memmap=130476K@737280K
*** This bug is a duplicate of bug 1307744 ***
https://bugs.launchpad.net/bugs/1307744
** This bug has been marked a duplicate of bug 1307744
bcmwl-kernel-source 6.30.223.141+bdcom-0ubuntu2: bcmwl kernel module failed
to build [error: too few arguments to function ‘cfg80211_ibss_joined’]
Just a quick note that this is caused by some change between kernel 3.14
(i.e. bcmwl compiled fine on 3.14) and 3.15 (here it fails to compile).
The bcmwl regularly needs patches to keep up to date with the kernel.
This has nothing to do with trusty (I run precise).
--
You received this bug
@gurjeet,
I'd recommend you just download the saucy .deb and install it
(http://packages.ubuntu.com/saucy/amd64/bcmwl-kernel-source/download for
64-bit).
It solves basically every problem the bcmwl driver had (ever) had.
AFAIK.
--
You received this bug notification because you are a member of
@Brian,
Sorry that after all your efforts you ended up going to the easy
(though questionable) solution. Since there is no reason to expect
Broadcom to fully GPL the driver, I guess the only solution (besides
using the in-kernel driver, which to me -- bcm4313 -- is still a no-go)
would be
Weird. Note: I'm on 12.04, not 13.04, but it shouldn't matter.
I have bcmwl-kernel-source 6.30.223.30+bdcom-0ubuntu3, downloaded from here:
https://launchpad.net/ubuntu/+source/bcmwl/6.30.223.30+bdcom-0ubuntu3/+build/4761504
That one includes in /patches:
0001, 0002, 0003, 0004 (kernel 3.2),
Interesting :)
If the module builds OK but doesn't load, you could try loading it
manually modprobe wl and see if any errors show up on the
console/syslog/dmesg.
AFAIK the patch you've applied adds support for 3.8 as well as for
lowlatency. If this works OK you could try isolating the lowlatency
@Tommy,
I am using 64-bit, and actually am using kernel 3.10 with precise.
Now in the very same page you posted if you look at linux-generic you
see it points to linux-image-generic which points to linux-
image-3.2.0-51-generic.
I cannot say 100% but an average LTS user (doing only security
Bug expired because somebody decides this is probably irrelevant,
based on the false assumption that kernel 3.8 is in precise now.
Last time I looked (http://packages.ubuntu.com/precise/linux-image-
generic), the precise kernel is 3.2.0-51, in both precise and precise-
updates.
People using a
Add. Confirmed means Verified by somebody else than the reporter. I
have, among others, verified this bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1130037
Title:
Hi all,
IANAL but I think it should be no problem to link non-GPL with GPL
symbols. For some reason kernel's modpost checks for this and aborts.
Modifying the license of a module would certainly be illegal. Modifying
modpost.c to remove that check (s/fatal/warn/) would just produce a
warning but
Christopher,
that's not how linux (Ubuntu) bug reporting works.
I know. Ubuntu, and unfortunately most open-source, bug reporting works
like this:
1. try to find irrelevant formal problems with the report itself.
2. if OP still there, ask user to update kernel.
2.5 do this 4 or 5 times to
12 matches
Mail list logo
