1 |
On 05/24/2017 11:46 AM, allan gottlieb wrote: |
2 |
> On Wed, May 24 2017, Daniel Frey wrote: |
3 |
> |
4 |
>> On 05/24/2017 11:10 AM, allan gottlieb wrote: |
5 |
>>> My older laptop needs broadcom-sta. Back when I bought and setup the |
6 |
>>> laptop (kernel 3.18.12), I emerged broadcom-sta and wireless worked. |
7 |
>>> |
8 |
>>> Now I am upgrading to kernel 4.9.16. The kernel boots but no wireless. |
9 |
>>> In /lib/modules/3.18.12-gentoo-3 I have net/wireless/wl.ko. |
10 |
>>> In /lib/modules/4.9.16-gentoo-3 there is no net. |
11 |
>>> |
12 |
>>> Am I supposed to remerge broadcom-sta? If so how do I indicate the |
13 |
>>> kernel version for /lib/modules? |
14 |
>>> Do I set the the /usr/src/linux symlink? |
15 |
>>> Do I run 4.9.16 during the emerge? |
16 |
>>> Something else? |
17 |
>>> |
18 |
>>> thanks, |
19 |
>>> allan |
20 |
>>> |
21 |
>> |
22 |
>> Sounds like it installs kernel modules, so yes, after a new kernel build |
23 |
>> you need to re-emerge all packages that install modules. Easiest way to |
24 |
>> emerge all packages that install kernel modules is: |
25 |
>> |
26 |
>> `emerge -a @module-rebuild` |
27 |
>> |
28 |
>> Dan |
29 |
> |
30 |
> Thank you dan, but how do I tell the build which /lib/modules/* to use. |
31 |
> I gave two guesses above. |
32 |
> |
33 |
> allan |
34 |
> |
35 |
|
36 |
Use `eselect kernel list` : it will show which /lib/modules it will go |
37 |
to (as an example here's mine): |
38 |
|
39 |
$ eselect kernel list |
40 |
Available kernel symlink targets: |
41 |
[1] linux-4.1.37-gentoo * |
42 |
[2] linux-4.9.16-gentoo |
43 |
|
44 |
If I merge a package with kernel modules, it will currently go to |
45 |
lib/modules/4.1.37-gentoo, which is what my kernel symlink is set to. |
46 |
You can use `eselect kernel set` to change this symlink. In my case, |
47 |
using `eselect kernel set 2` will change it to 4.9.16. In your case, |
48 |
list the installed kernels and set it to the new kernel and `emerge -a |
49 |
@module-rebuild` and you'll be good to go. |
50 |
|
51 |
Dan |