| 4 Sep 2021 |
 dsx | In reply to @danielrf:matrix.org
The two things I would try to test would be 1) using `flavor="grapheneos";` and 2) using upstream prebuilt kernel with `flavor="vanilla";` but `kernel.enable=false;` №2 worked. If there is way I can help debugging kernel build I'm game for a few more tries. | 03:30:45 |
| dsx | Thanks a lot! | 03:30:59 |
 danielrf | Ah, great! Good to know there's an issue we need to address there. | 03:36:26 |
| danielrf | I think I have something you can try: | 03:36:42 |
| danielrf | under modules/pixel/default.nix, add "arch/arm64/boot/Image.lz4-dtb" to the kernel.buildProductFilenames toward the bottom of the file in the section where it conditions on config.deviceFamily == "redfin" | 03:38:18 |
| danielrf | or apply
diff --git a/modules/pixel/default.nix b/modules/pixel/default.nix
index aec81c0..4243177 100644
--- a/modules/pixel/default.nix
+++ b/modules/pixel/default.nix
@@ -146,6 +147,7 @@ mkMerge [
signing.avb.mode = "vbmeta_chained_v2";
kernel.buildProductFilenames = [
"arch/arm64/boot/Image.lz4"
+ "arch/arm64/boot/Image.lz4-dtb"
"arch/arm64/boot/dtbo.img"
"arch/arm64/boot/dts/google/qcom-base/lito.dtb"
];
| 03:38:37 |
| danielrf | Turns out we were replacing only the prebuilt Image.lz4 but not Image.lz4-dtb .... | 03:40:34 |
| dsx | Ok, I'll try that next time I get to mess with it. | 04:28:43 |
 kranzes | In reply to @danielrf:matrix.org
Thanks! I'll try to take a closer look at this this weekend. Could you upload your built images as well? Do you have any idea where to ever start looking for things that might be causing this? | 13:30:45 |
| kranzes | I couldn't figure it out but that's probably because i dont know what robotnix does in depth enough to know what it does different than normal building through docker or something like that | 13:31:40 |
| danielrf | kranzes: well I was initially hoping that I could extract and compare both images to see if I noticed anything obviously wrong | 19:46:48 |
| danielrf | but there's nothing obvious at least | 19:46:59 |
| danielrf | The comparison isn't exactly great since the two images were built from slightly different source trees | 19:47:25 |
| danielrf | So one next thing to try would be to a build where we are using the exact same revisions for all repos | 19:49:49 |
| danielrf | You can generate a manifest file with these revisions pinned by running repo manifest -r -o miatoll.xml at the root of your source tree (inside your docker image?) | 19:50:38 |
| danielrf | That manifest file would be useful to set the repo .json file used in robotnix to have exactly the same revisions | 19:51:07 |
| danielrf | * So one next thing to try would be to try a build where we are using the exact same revisions for all repos | 19:51:51 |
| kranzes | I dont quite get what you mean | 19:52:30 |
| kranzes | What should i be doing? Right now i just started building in the docker image a new build for my device with a working setup wizard so i can actually use it | 19:53:24 |
| kranzes | It takes me like 3:20h to build the rom | 19:53:41 |
| danielrf | I'd like you to try to generate that pinned manifest file and share with me | 19:53:57 |
| kranzes | how do i get it? sorry | 19:54:09 |
| danielrf | hmm, lets try: docker run -it forklineageos -v "/home/1TB-HDD/Android/lineage:/srv/src" repo manifest -r -o miatoll.xml | 19:59:28 |
| kranzes | where would that drop the manifest? | 20:00:06 |
| kranzes | miatoll.xml | 20:00:09 |
| danielrf | should be at /home/1TB-HDD/Android/lineage | 20:00:20 |
| danielrf | if I'm reading the Dockerfile correctly | 20:00:25 |
| kranzes | In reply to @danielrf:matrix.org
should be at /home/1TB-HDD/Android/lineage its not there | 20:00:33 |
| danielrf | Did you get any other output from that command? | 20:01:11 |
| kranzes | nope | 20:01:18 |
