-
Notifications
You must be signed in to change notification settings - Fork 150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Warnings since dkms-3.0.10 on Arch system #384
Comments
Did some digging today. First warnings are from pacman because in-tree kernel modules are Second warnings are because of #297. I think the easiest "fix" for me would be to force the installation. Any way to do this from dkms.conf? The warnings in EDIT: Did some more reading and found |
Moved where, by who? Can you run On the missing version part - where did you get the tbs_6904_se module from? Cannot see it in Arch or AUR. |
dkms is moving the original modules so they can be restored when the dkms module gets removed again. I can check the exact location later when I'm back at home.
I wrote that dkms module for my specific hardware because the complete TBS driver build is taking a very long time. I can update later with specific instructions if you want. |
Before:
After:
|
Reproducer: mkdir -p /usr/src/tbs_6904_se-6.6
cd /usr/src/tbs_6904_se-6.6
# create dkms.conf file
vi dkms.conf
# create .config file with modules to build
vi .config
git clone https://github.com/tbsdtv/media_build.git
git clone --depth=1 https://github.com/tbsdtv/linux_media.git -b latest ./media
dkms add tbs_6904_se/6.6
dkms build tbs_6904_se/6.6
dkms install tbs_6904_se/6.6 dkms.conf
.config
|
Thanks a bunch for the details. Off the top of my head, I think dkms should not be moving the original but instead rely on the depmod.d config/ordering to ensure that kmod picks the new/updated module over the pre-existing original. If the config does not allow for the correct ordering, then moving of modules may happen. Will try to look at this over the next week or so o/ |
any news on this @evelikov? |
I'm just churning through some dkms chores and this issue is next. It's been crazy month 😅 |
Glancing through, this has some overlap with #311. Since that one is a little more self-contained, I will address that and then we can see what's left here 🤞 |
Beginning with version 3.0.10 (and up to the current version 3.0.12) I get different warnings during kernel upgrades from dkms. Following is an example if I re-install the currently active kernel.
dkms status also returns some warnings:
dkms.conf
Do I need to update something in my dkms.conf file to get rid of these warnings? Thanks!
The text was updated successfully, but these errors were encountered: