New: wf111 package removes all kernel module dependencies

https://bugs.busybox.net/show_bug.cgi?id=8346

Summary: wf111 package removes all kernel module dependencies
Product: buildroot
Version: 2015.05
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: mstarr at hedonline.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0

Created attachment 6161
--> https://bugs.busybox.net/attachment.cgi?id=6161
Patch to fix wf111 overwriting module files during install

If the wf111 package is selected and the source is given, the package builds and runs depmod in its output directory. Then in the install target the contents of the output directory are copied to the target/lib/modules/<VERSION> directory. When the install step occurs the module.* files are overwritten with the wf111 files resulting in only the wf111 driver kernel module showing up on the target.

This is detected by running "modprobe -l" on the target hardware and it will only show the extra/unifi_sdio.ko kernel module. This prevents loading of any other kernel modules enabled in the kernel configuration.

As a solution the WF111_INSTALL_CMDS is removed and under the WF111_BUILD_CMDS,
the following can be added to the make command:
OUTPUT=$(TARGET_DIR).

This points the build to install to the target directory and not the local output directory. This in turn catches all the other kernel modules when depmod is run. The only issue with this is that under the build target of wf111, it will also be installing the software too which is usually handled under the install target.

Attached is a patch that makes the changes suggested above.

Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=8346

--- Comment #1 from Martin <[email protected]> 2015-12-01 21:41:51 UTC --- I have managed to reproduce this issue using qemu_x86_64_defconfig in the 2015.11 release. My initial tests seem to show it's related to using uclibc.

To reproduce the npm crash do the following:

1) start with qemu_x86_64_defconfig
2) add the C++ compiler
3) enable node.js version 0.12.7
4) enable npm for the target
5) build and run in qemu as per the instructions in board/qemu/x86_64/readme.txt
6) login and type npm -v, it will crash.

Changing the toolchain from uclibc to glibc causes npm to start working. So as a work around use glibc. I'll try and narrow down the issue further.

Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=8346

--- Comment #2 from Martin <[email protected]> 2015-12-01 21:45:31 UTC --- (In reply to comment #1)

Oops, this is meant for bug #8296 not this bug. Sorry.

Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=8346

Thomas Petazzoni <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #3 from Thomas Petazzoni <[email protected]> --- Fixed by
https://git.buildroot.net/buildroot/commit/?id=eee68714a85b159050caecc2628fa349c4d9489e.

You are receiving this mail because:
You are on the CC list for the bug.