insmod: failed to load /sdcard/.../my_driver.ko: Required key not available
As far as I know, when loading a module using the "insmod" command from the ENG(or userdebug) binary, it is not necessary to verify the signature of the module.
--
--
You received this message because you are subscribed to the "Android Building" mailing list.
To post to this group, send email to android-...@googlegroups.com
To unsubscribe from this group, send email to
android-buildi...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-buildi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/efbcb066-7ef7-4cb7-a5b6-55e39bfedfe2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
As far as I know, when loading a module using the "insmod" command from the ENG(or userdebug) binary, it is not necessary to verify the signature of the module.The kernel configuration / image doesn't change between eng/userdebug and user, so this would surprise me. I suspect you'd have to rebuild the kernel, but I don't know for sure. The android-kernel google group may be able to help you more -- we generally only deal with prebuilt kernels when building the rest of the platform.- Dan
On Thu, Jul 18, 2019 at 7:37 AM Lucas. B <bsbi...@gmail.com> wrote:
@Dear All,--I've been wondering about some of the android functions for some time now, so I made a device driver.And I downloaded the AOSP source code and built it into ENG(or userdebug), then flash it into my Pixel 3 XL.But as I tried to load the module with the "insmod" command, I could find the following:insmod: failed to load /sdcard/.../my_driver.ko: Required key not availableAs far as I know, when loading a module using the "insmod" command from the ENG(or userdebug) binary, it is not necessary to verify the signature of the module.Anyway, I have the above signature problem, and I wonder how to solve it.How build own drive into the kernel, whether modify the .config in the AOSP source to build a new binary, or whatever can try to build a device driver, etc. I welcome everyone.I want to make sure my driver is working normally on the my Pixel 3 XL.with best regard,Thanks =)Lucas. B.
--
You received this message because you are subscribed to the "Android Building" mailing list.
To post to this group, send email to android-...@googlegroups.com
To unsubscribe from this group, send email to
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/CALQgHd%3DrTs%2B0SEYs%3DXdqZ_r23P7mnD0s8YGUfBU67vsbN0Rqtg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/CA%2BFjb8M%2BccfcPuoEjXo8VRk4PC%2BRFSMgV_5Ugu8MeZTgAZYpsQ%40mail.gmail.com.