-
Notifications
You must be signed in to change notification settings - Fork 14
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
kernel modules ? #38
Comments
I eventually found https://docs.kernel.org/kbuild/modules.html which leads me to run
Yet when I run
Which of course doesn't run...
|
So after a |
nope... same error... what is 'enable CONFIG_MODULES' in menuconfig terms? |
I think the .config is what it is referencing, and |
So finally got a zram.ko compiled after inserting numerous
|
What I would do in this situation, after running "gbmake firmware" as you did, is to edit "O/.config" and find the line that mentioned ZRAM. It looked like "# CONFIG_ZRAM is not set" Next time I build a firmware, I'll include ZRAM in it. |
So, I guess this means that even if it build the correct zram.ko file, the current kernal cannot load it without a full rebuild and flashing it to SPI? |
That isn't true in general. If that doesn't work you could try: and then try the insmod again. That enables various debug messages in module loading. echo file kernel/module/main.c -p > /sys/kernel/debug/dynamic_debug/control to turn the debug messages back off. |
After checking
I think I messed something up so badly with all the previous edits that I'm restarting from scratch:
and will edit the |
I think I am still missing something, as I'm not able to get a zram.ko from this:
I didn't choose most of those options, they were auto-selected, such as |
It looks like you didn't delete the whole line - just the "#" ??? It seems to have had the desired effect. It looked like you only ran "gbmake oldconfig" - that just updates the config file. I said you should then run "gbmake firmware", though you could just run "gbmake ; gbmake modules". If BLK_DEV_RAM were needed for ZRAM, then it would have been automatically selected. BLK_DEV_RAM allows you to treat a section of RAM as a block device. You almost certainly don't need it. |
i re-ran
i'm trying |
it still seems like I a missing something...
|
Even by combining the gbmake with the modules_install command:
I was unable to compile a zram.ko file. I'm not sure what these warning/errors mean. zsmalloc.ko already exists:
Now that I look closely, it seems that the firmware uses '6.1.1+' where the code compiles into just '6.1.1' - is this a significant difference? Or maybe just a minor enough difference to cause the errors I'm seeing? |
Is there a compile guide to add modules? I'm specifically looking to compile the zram module as it doesn't seem to be included in your image.
So far I've run:
But
find / -type f -name zram.ko
returns nothing. I suppose there is something else needed to edit before it will compile the zram module?The text was updated successfully, but these errors were encountered: