[Porting] Call for Testers

flohack

@preflex Strange. I did only one commit on the kernel config lately:

Maybe those SELinux changes are doing that? It seems to work for UT.

hy

@flohack Can you come to a detailed installation tutorial?

flohack

@hy I will try on the weekend, to refresh it once more, yes.

hy

@flohack Thanks!

khimaros

@flohack i am referencing https://pad.ubports.com/p/HaliumHowToTestInstall which mentions a system.img, however i don't see a system.img in Jenkins. am i missing something? i'd love to try this out on my sailfish device.

flohack

@khimaros the problem is that on Jenkins there is only an integrated .tar.gz which cannot be used for the Halium install method. I will create an updated one an post here again where to get it.

flohack

So I mader a new round of images here: https://twoot.bin.org.in/nextcloud/index.php/s/iAZDDkRYYAiN6Kk - tell me if that works better

khimaros

for those seeing a bunch of garbage in the instructions, this link seems to show @Flohack's original version of the document https://pad.ubports.com/p/HaliumHowToTestInstall/timeslider#419

khimaros

@flohack thank you! it boots, touchscreen good, WiFi working, front and back camera are functional w/ reasonable white balance, screen off/on fine, loudspeaker playing youtube with no stutter, volume rockers working. overall really solid experience! let me know if there's anything specific you would like feedback on.

khimaros

@flohack does the halium-boot.img have debugging enabled? i'm trying to use the same boot image to test out droidian and need to troubleshoot some early stage init issues. not seeing any iSerial results with lsusb.

flohack

@khimaros you mean to have access via RNDIS or telnet?

khimaros

@flohack whatever would let me instrument very early stage boot. do you have the instructions you are using to build halium-boot for sailfish handy? anything beyond the standard halium-9.0 build process?

flohack

@khimaros if you only want to test halium-boot first the instructions are actually quite okayish for Halium 9. You basically sync the tree, add the device manifest and then just let it build - if you flash it without rootfs.img and system.img you can boot it, and it will drop into emergency telnet mode
If you add rootfs but no system.img it will normally boot into rootfs and you should get RNDIS ssh

khimaros

@flohack -- thank you. are the device manifests you merged in https://github.com/Halium/halium-devices/pull/282 sufficient? i ran into some build errors and wondered if there were some additional steps/patches i was missing.

flohack

@khimaros yes should be enough, you need to:

repo sync the Halium 9 tree
run halium/devices/setup sailfish (or marlin)
run hybris-patches/apply-patches --mb
then run breakfast sailfish (or marlin) and mka all parts

khimaros

@flohack -- thank you. i was able to build successfully. however, i'm noticing that the documented hybris-recovery target does not exist, which is making it a bit tricky to troubleshoot init issues. was this renamed or is there another way to force an existing boot image into recovery mode?

flohack

@khimaros this target is new to me, we only have:

halium-boot for non a/b devices, and bootimage for a/b
recovery
system
vendor

mostly what you need

khimaros

@flohack -- i'm referring to the documentation at https://docs.halium.org/en/latest/porting/debug-build/early-init.html#forcing-debug-mode:

If the device simply reboots when trying to boot and does not bring up telnet, you may build and use the hybris-recovery.img file to attempt to force a shell to come up.

this is the circumstance I'm bumping up against. maybe there is a new way to troubleshoot this?

flohack

@khimaros Well here is the problem: While we claim to be a Halium distro, we are only sharing some of the codebase, and you need to know when to break off from the Halium docs and return to UBports

If you have reboot issues best bet is to wipe data, then flash halium-boot and see if it still crashing. If yes, your kernel is screwed, if not it should give you telnet. Also adding break=bottom to kernel cmdline will stop before the real init to inspect the device and mounts etc.

woodenLion

Help please, as I am getting "chroot: failed to run command ‘chpasswd’: No such file or directory" and don't know what to do.