-
Notifications
You must be signed in to change notification settings - Fork 28
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
Build started failing for OpenSUSE 15.5 #17
Comments
Hmm, maybe you're missing kernel headers?
|
Nope, already installed. There is something strange though, since I noticed the fix that was committed a few weeks ago, since I did get the
but the strange thing is that I sometimes STILL get the above "DMA_BUF" errors, despite the fact that I've got the fix in my code. |
I wouldn't mind an example of dkms.conf, since this will build two .ko modules not just one, so I am trying to make heads or tails out of how the dkms.conf should look. |
This is really strange. I just looked into your versions tag in the OpenSUSE kernel repo, the include fix should work flawlessly. Is this a fresh install or did you bumped your OS version by upgrade? |
I bumped, via I've got a VM with 15.5, that I'll try some similar things with, and see. Its freshly installed. |
But since I cant really understand how to use a dkms on opensuse to build the module, my attempts are going veeery slowly. I cant even find the original instructions I used on 15.4, where I simply copied the gasket-src into /usr/src/linux/drivers/staging/gasket, ran some Although I made a script of them, and its been working for years, every time I got a new kernel for 15.4. |
Well, isn't this annoying. I forgot, despite the fact that I've been banging my head against this earlier, opensuse 15.5, has GCC7.5 as default.
But anyway, I first tried just forcefully using MODULE_IMPORT_NS(DMA_BUF); and that worked as well. Updating my system to gcc12, made it much simpler. Some
in the gasket src directory, and now I have my .ko's! |
Yuck. That is seriously annoying, the fact I don't think it's a good idea to revert #16, because backports seem to be even more common than I thought. And we can't really make any reasonable correlation between whether the compiler supports cpp17 (GCC >= 8 || Clang >=5) and whether the kernel needs So what to do? Setting a minimum compiler version seems to be overkill but what else? |
Sorry, very late to the party... I'm the maintainer for this package on Tumbleweed, where installing it is as easy as using That said, the package builds just fine for Leap and therefore should run okay. This is the official 'development' repo: and this page shold allow you to install it: It's flagged as 'experimental' because it isn't in the official Leap repos, but it'll work just fine. |
Hi,
I've been using this driver/lkm and building a module for my Opensuse Leap 15.4 system for a year or two, so that I can run frigate in a docker container, using the
/dev/apex
device.I just now though, very stupidly, updated my host to Leap 15.5, and when I tried creating a new kernel module, I get:
WARNING: modpost: "module_layout" [drivers/staging/gasket/apex.ko] undefined!
WARNING: modpost: "system_wq" [drivers/staging/gasket/apex.ko] undefined!
WARNING: modpost: "kmalloc_caches" [drivers/staging/gasket/apex.ko] undefined!
WARNING: modpost: "param_ops_int" [drivers/staging/gasket/apex.ko] undefined!
WARNING: modpost: "pci_disable_device" [drivers/staging/gasket/apex.ko] undefined!
WARNING: modpost: "delayed_work_timer_fn" [drivers/staging/gasket/apex.ko] undefined!
WARNING: modpost: "param_ops_bool" [drivers/staging/gasket/apex.ko] undefined!
WARNING: modpost: "init_timer_key" [drivers/staging/gasket/apex.ko] undefined!
WARNING: modpost: "cancel_delayed_work_sync" [drivers/staging/gasket/apex.ko] undefined!
WARNING: modpost: "mutex_unlock" [drivers/staging/gasket/apex.ko] undefined!
WARNING: modpost: suppressed 125 unresolved symbol warnings because there were too many)
I think that maybe OpenSUSE simply isnt supported, but I would still kindly, and desperately, ask for any help or tips that might help solve this for me?
My suse system is running : Linux kernel
5.14.21-150500.55.19-default
The text was updated successfully, but these errors were encountered: