| T42 | <b100dian> rinigus: how do you flash a new sailfishos kernel? Seems like something else is needed and if it is vendor_dlkm then we need fastbootd which requires lineage kernel / recovery etc? | 06:54 |
|---|---|---|
| T42 | <b100dian> I wish sony implemented `fastboot boot` wouldve been easier to grab logs | 06:54 |
| rinigus | @b100dian: you only need to flash hybris-boot and vendor-boot. vendor-dlkm has to be updated via regular packaging on SFOS side. its in vendor-dlkm rpm and contains the folder with modules. we just don't mount vendor_dlkm partition anymore on sfos boot and instead use that folder | 06:57 |
| rinigus | so, in the end, all 3 need to be updated: boot, vendor_boot and dlkm. just dlkm is not flashed. | 06:57 |
| rinigus | fastboot boot wasn't available on tama either. would be nice, indeed | 06:58 |
| rinigus | @b100dian: note its possible to get out of sync between kernel and dlkm. so, not super ideal situation | 06:59 |
| rinigus | but I think better than flashing dlkm as it is not possible to flash from fastboot directly. | 06:59 |
| T42 | <b100dian> Thanks, so at least I don't need to flash lineage again before flashing kernel update | 07:00 |
| T42 | <b100dian> Let's see if it boots with out-of-sync modules ;) | 07:01 |
| T42 | <b100dian> hopefully dwc3-msm.ko is not the one used for telnet | 07:04 |
| rinigus | @b100dian: note that to get to fastbootD, its sufficient to flash LOS boot and vendor_boot. so its not as full LOS needs to be reflashed. anyway, you already have LOS on device, just don't fully boot it :) | 07:04 |
| rinigus | fastbootD + recovery | 07:05 |
| T42 | <b100dian> yeah, but that was not changed | 07:05 |
| T42 | <b100dian> maybe we should change lineage to use the ext4 data without formatting ;) | 07:05 |
| rinigus | @b100dian: I suspect that LOS/android requires device encryption. but if there is a way around it, it would allow us to easily boot between sfos and los | 07:08 |
| T42 | <FarzinKazemzadeh> rinigus: It is possible to disable that encryption. | 07:25 |
| T42 | <FarzinKazemzadeh> https://github.com/Zackptg5/Disable_Dm-Verity_ForceEncrypt | 07:25 |
| rinigus | Thanks! | 07:35 |
| rinigus | Although, looks not supertrivial :) | 07:36 |
| T42 | <FarzinKazemzadeh> rinigus: Basically, that drops fileencryption flag from the fstab | 09:18 |
| T42 | <b100dian> What about filesystem type, can one change in fstab from (I guess) f2fs to ext4 ? | 09:42 |
| rinigus | @b100dian: I think you can change it. | 10:01 |
| rinigus | @FarzinKazemzadeh: thanks! | 10:02 |
| T42 | <FarzinKazemzadeh> @b100dian Fstab does specify filesystem type, and you can have multiples per partitions | 10:48 |
| T42 | <FarzinKazemzadeh> rinigus: You're welcome | 10:48 |
| T42 | <FarzinKazemzadeh> @b100dian Fstab does specify the filesystem type, and you can have multiples per partitions (edited) | 10:50 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!