| T42 | <elros34> if fpr some reason you choose to build lvm image then command is wrong. Look at build_packages.sh script | 00:50 |
|---|---|---|
| sharks | mal asked me to build an lvm image | 00:51 |
| sharks | Okay, thanks @elros34, I think I've spotted what you meant. There are two possible mic commands and the one for an lvm image is `mic create loop`, not `mic create fs` | 00:58 |
| sharks | Okay that got me further but I'm still doing something wrong, "cannot access flash.*': No such file or directory" | 01:13 |
| T42 | <elros34> search for flash.* in droid repos for some lvm based device. Maybe it expect flashing script in some place | 01:17 |
| sharks | not in mer-hybris/droid-config-sony-murray, but maybe I can extract them from the official 10 IV zip from Jolla's website. Just don't know where to put them - are they supposed to be in droid-config somewhere? | 01:20 |
| T42 | <elros34> https://github.com/search?q=org%3Amer-hybris%20flash.sh&type=code | 01:29 |
| sharks | Yep, I believe it's all the stuff in the `boot` directory, I just don't know where I'm supposed to get it from | 01:30 |
| T42 | <elros34> what do you mean it's first search result, its in submodule | 01:31 |
| sharks | Well then that exists in my source tree at $ANDROID_ROOT/hybris/droid-configs/droid-configs-device/sparse/boot/flash.sh | 01:33 |
| sharks | So why can't `mic` find it? What's it want me to do that I haven't done? | 01:34 |
| T42 | <elros34> second search entry shows it's supposed to be in out-of-image-files.files (https://github.com/mer-hybris/droid-config-sony-seine/blob/e47c164db8cdf08f69bae34f0145204265fbe5c8/out-of-image-files.files#L3). I ahve never se reason to try lvm build so take it with grain of salt | 01:35 |
| sharks | To be honest I'm not sure why an LVM build is a good idea either, you'll just end up with the problem everyone had when upgrading to 5.1 that there wasn't enough space on the partition, but anyway I was asked to do it by those smarter than me so I am trying to do as I was asked | 01:37 |
| sharks | You are right I don't have the out-of-image-files.files, but that lists eg. flash-on-windows.bat which doesn't exist in my sources locally, only adding to my confusion | 01:37 |
| T42 | <elros34> search for flash-on-windows.bat in mer-hybris repo | 01:39 |
| T42 | <elros34> you can see it's in sparse | 01:40 |
| sharks | Yep, just spotted that | 01:40 |
| sharks | Okay, thanks elros, I'll add the boot directory to sparse and see if that helps. | 01:40 |
| *** n2klb_ is now known as n2klb | 01:57 | |
| sharks | Nope, that didn't fix it | 02:02 |
| sharks | Screw it, until someone who knows more about LVM images can tell me what I'm doing wrong, I'll just comment out the bits about the flash files in the .ks file. | 02:04 |
| mal | you should just remove the flash file stuff from the pack kickstart https://github.com/mlehtima/droid-config-fp5/blob/master/kickstart/pack/fp5/hybris#L109 | 02:16 |
| mal | if that was the issue | 02:16 |
| mal | and you can define the size of the root partition, I use 10 GB on fairphones | 02:17 |
| sharks | Sorry, I had to step out for half an hour | 02:43 |
| sharks | I have removed the flash file stuff from the kickstart, I'll rerun the mic command and see if I can get an image to pop out the other end | 02:44 |
| mal | did you rebuild config packages first with build_packages.sh -c? | 02:52 |
| mal | I mean if you do the change I mentioned | 02:53 |
| sharks | Umm | 02:53 |
| sharks | no because I just changed the *.ks file I'm feeding into `mic` | 02:54 |
| sharks | Maybe that's the wrong thing to do but I don't even know if this LVM image is going to successfully go together and boot yet. If it works I'll go back and update droid-configs - but then if I trigger services on OBS, it should rebuild that, right? I don't have to run `build_packages.sh -c` locally anymore? | 02:55 |
| sharks | Nevermind, mic failed again so I'm doing something wrong. | 02:57 |
| sharks | I wish there was a way to just test these last 15 lines of the *.ks script without having to wait for mic to organise all the packages and build the rootfs and everything first | 02:58 |
| sharks | Maybe I can run them manually in the output directory | 02:59 |
| mal | did you setup boot-img package already? | 03:15 |
| sharks | This one? https://build.sailfishos.org/package/show/nemo:devel:hw:sony:murray/droid-hal-img-boot-sony-xqcc72 | 03:16 |
| mal | yes | 03:17 |
| sharks | And I also ran build-packages -b /path/to/droid-hal-img-boot-sony-xqcc72 though as I say my understanding is that this *.ks file is supposed to pull packages from OBS not from local repo | 03:17 |
| sharks | Okay, removing the line `chmod 755 flash.*` and removing "flash.*" from the FILES variable gave me an image. But I'm not getting gui anymore, can only telnet | 03:24 |
| sharks | On port 23 | 03:25 |
| sharks | So I flashed boot with `fastboot flash boot hybris-boot.img` and rootfs with `fastboot flash userdata sailfish.img001`, but I've got "exFAT-fs (sda74): invalid boot record signature", "exFAT-fs (sda74): failed to read boot sector", "exFAT-fs (sda74): failed to recognize exfat type", "F2FS-fs (sda74): Magic Mismatch, valid(0xf2f52010) - read(0x0)", "F2FS-fs (sda74): Can't find valid F2FS filesystem in 1th superblock" in dmesg on device. | 03:37 |
| sharks | So userdata (sda74) is not mounting. It sounds to me like it's still trying to boot with a community-style userdata partition not an LVM one, but I don't know why or how | 03:39 |
| sharks | @mal you said I didn't have to `make hybris-boot` again after switching to LVM? There was nothing I had to do in the HABUILD environment? | 03:42 |
| sharks | I don't fully understand how droid-hal-img-boot works | 03:42 |
| sharks | I mean it makes a boot image but where does it put it? How can I be sure that's what made it onto my device? | 03:43 |
| sharks | @mal where do the flash.* files get pulled into the archive from? | 05:13 |
| sharks | Cripes I'm so confused. The hybris-boot.img that made it into my LVM archive was from ./out/target/product/pdx225/hybris-boot.img (confirmed by checking md5 hash). The boot-img package output is at ./hybris/droid-hal-img-boot-sony-xqcc72/hybris-boot.img because there is no documentation as to where to put it, so I took a guess that would do. Either I put it in the wrong place and `mic` didn't pick it up, or something else is wrong. | 05:24 |
| sharks | At any rate, flashing with the hybris-boot from droid-hal-img-boot gets me to the first setup screen, but my touchscreen no longer works | 05:24 |
| sharks | And the phone will not connect over USB so I'm completely locked out, just stuck looking at a language selection screen | 05:25 |
| sharks | But at least I suppose that means I've got the filesystem up | 05:25 |
| sharks | Any idea where to go from here? | 05:25 |
| rinigus | sharks: its been a while since I used LVM in a port. but some notes are at https://github.com/sailfishos-sony-tama/main/blob/hybris-10/hadk-sony-xz2.md . not all has to be followed (you don't package android itself, for example), but maybe there are some bits that can help | 06:33 |
| rinigus | @b100dian: here are the notes | 06:37 |
| rinigus | please update local_manifests - that will fix newest kernel check repo while allowing you to pull all the latest updates from the rest | 06:37 |
| rinigus | I have used /main/scripts/sync-sources.sh to update all my sources. note that before it, I added snapshot to .repo/manifests as explained in HADK. that way I could keep LOS codes as they were in my base and sync-sources did not pull in some later changes in LOS which we don't have in our base anyway. | 06:37 |
| rinigus | in my case, I fixed few revisions in local_manifests/nagara.xml too - just to avoid changes from LOS. but those are probably different between 1iv and 5iv as we did the base at different times. so, those fixed commitIDs live in my local copy and were not committed | 06:38 |
| rinigus | after sync, I checked with /main/scripts/create-manifest-snapshot.py what were the changes to verify that I am on correct commit IDs. my manifest snapshot is uploaded to our snapshot repo - so you can check it against your local one | 06:38 |
| rinigus | I have tagged droid-config but didn't trigger rebuild for 5IV. that has to be done after you pull in latest dhd | 06:38 |
| rinigus | in my mind we are good to go. just need to add docs on OTA (I will deal with that) and test a bit. | 06:38 |
| rinigus | and will test your eSIM check as well | 06:46 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!