Emerging app-laptop/tp_smapi doesn't fail but warns about unknown symbols causing the tp_smapi (and hdaps and thinkpad_ec) kernel module unusable.
Created attachment 446408 [details] emerge log Here is the full emerge trace.
Does this only occur on kernel 4.7? Also, please attach emerge --info
Created attachment 447026 [details] emerge --info
(In reply to NP-Hardass from comment #2) > Does this only occur on kernel 4.7? > > Also, please attach emerge --info I don't know, first time I'm trying to emerge tp_smapi.
That version of tp_smapi should work with 4.7 kernels. I guess the first thing I would check is that the kernel in /usr/src/linux is built, and actually corresponds to the config file at /usr/src/linux/.config. Double check that /usr/src/linux points to /usr/src/linux-4.7.2-gentoo, too. Most of those warnings (e.g. missing strncpy) aren't specific to tp_smapi so I'm thinking there's something wrong with the kernel source/build. You can also try to emerge some other out-of-tree kernel module, like net-fs/openafs-kernel or sys-fs/zfs-kmod. If every out-of-tree module throws the same warning, that gives us some useful information.
(In reply to Michael Orlitzky from comment #5) > That version of tp_smapi should work with 4.7 kernels. I guess the first > thing I would check is that the kernel in /usr/src/linux is built, and > actually corresponds to the config file at /usr/src/linux/.config. Double > check that /usr/src/linux points to /usr/src/linux-4.7.2-gentoo, too. I just upgraded to 4.7.5 and removed all older kernels. It persists. > Most of those warnings (e.g. missing strncpy) aren't specific to tp_smapi so > I'm thinking there's something wrong with the kernel source/build. You can > also try to emerge some other out-of-tree kernel module, like > net-fs/openafs-kernel or sys-fs/zfs-kmod. If every out-of-tree module throws > the same warning, that gives us some useful information. Is it possible these symbols get stripped somehow? CONFIG_STRIP_ASM_SYMS is not set.
Do you have CONFIG_TRIM_UNUSED_KSYMS=y? If so, can you try disabling it?
That's the right option I activated during a kernel upgrade. I thought it was CONFIG_STRIP_ASM_SYMS. Thank you.