<samueldr>
now to get the device, copy the file, fastboot it
<danielrf[m]>
awesome!
<samueldr>
and it doesn't boot!
<samueldr>
but that's most likely the device tree that's somehow wrong
<samueldr>
fun thing is that it looks like the kernel's not even starting
<samueldr>
btw, I don't really need help debugging the issue, just reporting
<samueldr>
I kind of know my way around booting a Linux on phones :)
<danielrf[m]>
Haha, no worries. I'm sure you have more expertise here than I do anyway :)
<samueldr>
yeah, also I'm starting from an unknown condition
<samueldr>
I don't know if it's supposed to work!
<danielrf[m]>
that does complicate things!
<danielrf[m]>
which phone / device is this for btw?
<samueldr>
motorola-surfna
<samueldr>
which doesn't have any trustable TWRP
<samueldr>
since I saw that twrp device tree generator, I wanted to try it
<danielrf[m]>
literally the first page on google when I searched for "motorola-surfna" is your mobile nixos doc page.
<samueldr>
I know!
<samueldr>
caught me again earlier today
<samueldr>
moto e6
<samueldr>
last year when I did the port there were no TWRPs, at all, and no custom ROMs
<samueldr>
if the device tree it generate works, the next thing I wanted to try was add a kernel build to it, then maybe it'd give me an insight into making a LineageOS port from scratch :)
<samueldr>
interesting, first it seems the initial recovery.img I was using as a source would't boot on the device
<samueldr>
so I tracked another official one
<samueldr>
which this one does boot
<samueldr>
but a twrp from that tooling won't boot... what's interesting is that the kernel binary is the same
<samueldr>
so I must assume something's not right with the init!
<samueldr>
annoyingly enough it looks like console pstore doesn't work
<samueldr>
maybe you're joking, but that's actually seriously what it is
<samueldr>
looks like there's also sailfish activity on their jenkins
<danielrf[m]>
I've actively repressed my memories of jenkins so I don't know if it's possible to see the build configurations without higher permissions
<samueldr>
I was about to say that jenkins looks totally unhelpful
<samueldr>
where's the data!
<samueldr>
but we do have a git commit ID
<samueldr>
and marlin/sailfish share the same ID
<danielrf[m]>
seeing some env vars and logs as well
<samueldr>
yeah, logs
<samueldr>
no env vars in sailfish/marlin
<samueldr>
logs, surprisingly, show commands being run
<danielrf[m]>
Wonder if this is public: `/builds/jenkins/scripts/buildtwrp.py`
<samueldr>
you know I was just looking that up
<danielrf[m]>
I'm working on a configuration for marlin right now, and it needs a couple extra repos: `hardware/qcom/{bootctrl,msm8998}`
<danielrf[m]>
so I'd wonder where exactly those repos are being included in the jenkins config
<samueldr>
exactly as my last reading material link documents
<danielrf[m]>
(or maybe they're only needed for me since we're using the minimal manifest)
<samueldr>
you might also end up needing some binaries from a rom
<samueldr>
plausible too
<danielrf[m]>
while using a minimal manifest would be nice, I'd hate to have to track down all these extra dependencies / kernel sources / etc manually for each device
<samueldr>
huh!
<samueldr>
it's only the twrp.me site that's wrong
<samueldr>
the actual files listing for sailfish is the same as for marlin (with different names)