Repository navigation
Replies: 4 comments 36 replies
|
2026021200 is the version where they reenabled kernel module signing. The modules are signed with a per-build key, so if you're just replacing the kernel without also replacing the (I'm going to convert this issue to a discussion since this isn't an avbroot bug.) |
|
Im assuming the correctly signed kernel modules are in the out directory? How do I add these into the dlkm images, are they in the super partition |
|
Building the entire rom from source might be easier at this point |
|
Turns out replacing CONFIG_MODULE_SIG_REPLACE=y with CONFIG_MODULE_SIG_PROTECT=y fixed this after all. Not sure why it didnt work the first time but I tried again and it works. |
Uh oh!
There was an error while loading. Please reload this page.
Ive run into a problem rooting grapheneos (tegu 2026021200) recently that even building an unmodified kernel according to the build guide will not boot. Nobody else seems to have this problem and it persists across machines, I've ruled out pretty much anything but avbroot. I'm going to attach a log below but what causes the kernel panic is insmod being unable to load the zsmalloc kernel module due to it not being signed (grapheneOS kernel has module sig required and lockdown mode)
Ive had rooted grapheneos for a year now, but it suddenly doesnt work and I will get flogged if I ask in any of the official support channels about something related to root.
All reactions