Wednesday, 2019-04-17

osum4estim able to complete the first phase of the bootloader, but it fails before it reaches the second part. i've done touch /target/init_enter_debug2, but then when continuing init it gets stuck on a black screen/powers off. dmesg shows that the device disconnects. i've been able to fix all the kernel config errors besides CONFIG_VT and the selinux bootparam. if either of these are set to y then the init script isn't reached a01:38
osum4estah, looking at the log says it refused to boot since CONFIG_VT was not set. but setting it doesn't even get me to the init script? is there a reason why i wouldn't be able to set it?03:13
r0kk3rzbecause its broke03:15
r0kk3rzhappened to ghosalmartin03:15
r0kk3rzremove it from the check in the init script03:16
osum4estah, thanks. ill give that a go. still have the problem with selinux though, which has to be disabled somehow03:19
r0kk3rzim not sure that will be an issue yet, probably soon03:20
T4<Hound77> Why do I get "user 1000 does not exist" in mic create ?05:15
T4<austenite> its not the problem, does device bootloop?05:18
T4<Hound77> It just boots to bootloader. And I have to use different twrp for flashing lineage and sfos.05:24
T4<Hound77> I tried several twrp but none of them seems to flash either lineage or sfos.05:25
T4<austenite> most likely something is wrong in your defconfig05:45
T4<austenite> @Hound77 or just do 11.1 in hadk and flash hyrbis-boot image, you can dual boot lineage/sfos by changing the boot-image, sppeds up the process05:49
T4<Hound77> What 11.1 ? @austenite05:55
T4<austenite> section 11.1 in hadk pdf05:56
T4<Hound77> Seem like selinux is my problem given on 9.3.106:06
T4<Hound77> Then there is no necessary in doing 10.1 ?06:29
T4<austenite> wlan: version magic '3.18.31 SMP preempt mod_unload modversions aarch64' should be '3.18.31 SMP preempt mod_unload aarch64'  in dmesg .disabled module versions and signatures.06:44
T4<Hound77> … Is this okay when creating mic create ?07:34
r0kk3rzdid you get a zip at the end?07:35
T4<Hound77> Yes07:50
T4<Hound77> I added selinux=0 and did the .zip again now I am flashing the zip. If fails to boot I'll follow 11.107:51
r0kk3rzdont worry about the mic output so long as it completes08:10
T4<Hound77> Do I have to be in recovery to do 11.1 ?08:14
T4<Hound77> Because I get adb: error: connect failed: closed08:15
T4<elros34> Charlie if flashing zip ended without error you don't need to manually install it. Read 9.108:18
T4<Hound77> But the only error I get is this after flashing "Failed to mount /dev/block/bootdevice/by-name/userdata at /data : Device or resource busy", "failed to extract filesystem" and "Updater process ended with ERROR: 7"  … But flashing ends up successful.08:20
T4<Hound77> So I thought I should do it manually.08:20
T4<Hound77> After flashing it boots to bootloader.08:21
T4<elros34> I thought you found twrp which finish without "failed to extract.."08:24
T4<Hound77> The latest version It won't flash at all. But older ones finishes with the error above.08:42
pketoPSA: is going to have a maintenance break for about 30-60 minutes, starting around 12:00 EEST. This will affect all services using Jolla account login, like store, shop, TJC, blog, etc.08:52
masha11Hello! I get the following error: Sailfish droid-hal-init: Failed to initialize property area. How do i fix it? My device - Motorola Moto Z (griffin), LineageOS 14.1, SailfishOS
masha11From telnet 2323 ssh nemo: systemctl --no-pager:, journalctl -b:, dmesg:
T4<austenite> why should wlan driver be built as a module when prima wlan is working fine?11:39
T4<elros34> when it works good then leave it builtin11:40
malsome devices at least used to have issues if wlan driver was not reloaded after wlan hotspot11:41
malsome devices wouldn't even have wlan working without it being a module, so if both of those cases work reliably then builtin is fine11:41
malso enabling and disabling wlan hotspot many times is quite important test to do anyway11:42
T4<adampigg> mal, <cough>pr</cough>11:43
T4<adampigg> :D11:44
T4<adampigg> mal, there is a bunch of us doing pinephone porting now....11:45
T4<adampigg> native too11:45
T4<adampigg> just aswell i added native options to -config-!11:45
mal@adampigg what arch is that phone?11:56
T4<eugenio_g7> Cool, are pinephones shipping already?11:56
mal@adampigg I'll try to review the PR tonight11:58
T4<NotKit> mal, arm6412:09
T4<NotKit> @eugenio_g7 not yet, but they sent the devkits12:10
T4<adampigg> mal, arm with mali graphics12:12
T4<adampigg> mal, ta12:12
T4<eugenio_g7> @TheKit: cool!12:27
T4<adampigg> user:camera and media arnt working. me:what did you change12:47
T4<adampigg> user:nothing. me:you sure?12:47
T4<adampigg> user: well, i did a backup, installed android pie and a new recovery, then restored backup and loaded sailfish12:48
T4<adampigg> me: well........12:48
masha11mal: Hello, do you know what changes need to be made to successfully start droid-hal init? I get from journalctl: failed to start droid-hal-init .13:06
malsome people seem to have recent had issues that it fails to initialize property area, not sure what has changed for that to happen13:08
malafaik someone noticed that it was some permission issue13:10
malthat actually reminds me, I have one device (and others had other devices) that had problem that hybris-hal wasn't building all ueventd.rc files correctly so some permissions were not applied13:12
T4<austenite> @mal it happened to me when i ran rpm/dhd/helpers/build_packages.sh13:12
mal@austenite what happened?13:12
T4<austenite> so i stopped running the command and builds seem to work13:12
T4<austenite> @mal i ran rpm/dhd/helpers/ —configs when i changed pattern , then the os was not going past lockscreen, sometimes audio was not working13:13
T4<austenite> so after that i ran , built  a dummy image, changed pattern but never ran rpm/dhd/helpers/ --configs again13:16
malso you did something wrong13:18
T4<austenite> idk mal, i  unshallowed the repo , downloaded the repo again and started from scratch 5 times only not running rpm/dhd/helpers/ --configs for the second time fixed my problems13:19
T4<austenite> guess something is wrong with my pc13:20
malwithout seeing the changes you had in that repo it's impossible to tell what went wrong13:20
malbut since you said you changed patterns it's very possible you did something wrong there13:20
malmasha11: in $ANDROID_ROOT see what this command outputs: find out/ -name ueventd*.rc13:40
masha11@mal thanks, ok13:41
T4<elros34> masha11: not sure if that could be related but try to use older libhybris (iirc 0.0.25). With latest on cm11 base kmap2qmap crash for me. Also lipstick/minimer crash too but not sure if that was related. I cleaned everything and built with older libhybris. Then everything works14:14
masha11@elros34 thanks, I will try14:17
T4<MarcoDS_bit> little help? :D
mal@elros34 it would be nice to know why those fail and what error happens so it can be fixed14:52
T4<Hound77> @austenite @elros34 I'm quite stuck. Any suggestion to move foward ?15:15
T4<austenite> @Hound77 flashed zip?15:17
T4<Hound77> It wont boot.15:18
T4<austenite> @Hound77 su doesnt work in recovery , i did it with magisk on lineage and then through adb with root permissions15:19
T4<austenite> @Hound77 consider all warnings by mer-kernel check utility, run it again15:20
T4<Hound77> @austenite Do I need to make hybris-hal again ?15:27
T4<austenite> @Hound77 no15:27
T4<Hound77> @austenite So did you mean in the second part ?15:29
T4<Hound77> *What did you mean in the second part ?15:29
T4<austenite> @Hound77 i meant section 5.4.1 in hadk15:31
T4<Hound77> Didnt I already make that recommend changes to deconfig and make hybris-hal.15:32
T4<austenite> then its time for kernel logs15:33
T4<elros34> mal: sure I will provide more info soon but probably not today15:33
T4<elros34> Charlie: so you manually unpacked sfos and flashed kernel? Now connect it to pc and check host dmesg, HADK 9.215:35
T4<Hound77> Didnt do that yet.15:36
T4<austenite> @Hound77 it doesnt boot directly, youll have to finish whole hadk15:37
T4<austenite> i meant everthing thats in hadk15:38
T4<elros34> Marco: try to use latest release
T4<Hound77> @austenite But why did it mentioned on 8.5 to flash. What supposed to yield in this process ?15:41
T4<austenite> @Hound77 you deploy the image, and if it doesnt boot, check 9.4, telnet in, get logs and find out whats wrong15:43
T4<austenite> lxc-checkconfig: command not found , what are the other ways to find missing flags?15:54
T4<Hound77> @austenite So I should flash hybris boot and recovery through fastboot or use 11.1 section.15:57
T4<austenite> @Hound77 dont flash hybris-recovery, afaik its a bootimage to be used for debug when hybris-boot is continuously boot looping15:58
T4<austenite> @Hound77 just hybis-boot , through fastboot and zip16:00
erhoofHello everyone! Could it be that sfos suspend and basic linux distro suspend work differently? Currently i'm using i486 tablet without libhybris, everything is working great, except for sleep. On any linux distro sleep is working fine, but there systemctl suspend just gets my tablet frozen for 5-15 secs16:06
T4<adampigg> what tablet?16:08
erhoofacer w4 82016:10
T4<adampigg> Interesting, very much like our latte then16:11
erhoofAlso, please, can you someday upload your qtbase.spec and mesa.spec files? Want to compare16:12
erhoofgbm drm kms stuff16:12
T4<adampigg> Look on obs, xiaomi latte16:13
T4<adampigg> And github, sailfish-on-latte16:13
erhoofAlso, did you also have this SkiaGL problem with browser?16:15
erhoofTried to disable acceleration, but with no luck16:15
T4<Hound77> @austenite Just in case these are the kernel and recovery logs got from twrp flash, …
T4<austenite> @Hound77 these are twrp logs, do what elros said you need to start with 9.216:26
T4<adampigg> If you mean nkt rendering,  yes, we use webcat as we dont know the problem yet16:26
T4<adampigg> Whay kernel do u use!?16:26
T4<eugenio_g7> @erhoof: on latte we use the  android kernel16:39
erhoof@adampigg 4.20 from manjaro, it was by the hand so i've built image with it16:54
T4<meierrom> @adampigg [mal, there is a bunch of us doing pinephone po …], Bunch? How come? Did they distribute pine dev devices and forgot about mal? :)16:57
piggzerhoof: so, how do you boot the manjaro kernel? do you package it into an android boot.img?17:16
mal@meierrom maybe because I didn't even ask for a device, I have too many projects anyway17:20
piggzerhoof: so, your device also doesnt turn off screen after 15 or so seconds?17:24
piggz@eugenio_g7 have you had this?17:24
T4<Hound77> @austenite In 8.5 flash the zip, so what do I if it fails to flash. I'm confused at this point.17:50
T4<Hound77> I didnt get what 9.2 is all about and where to do it.17:51
T4<austenite> @Hound77 if zip doesnt flash then 11.117:52
T4<austenite> for bootimage, fastboot boot hybris-boot, for 1 boot, you can boot a fixed hybris-boot in next reboot17:53
T4<austenite> or fastboot flash boot , telnet and take logs17:54
T4<eugenio_g7> piggz: what? Non-working screen timeout? It worked fine here, but I have a pretty big timeout (set before I fixed the watchdog to avoid rage-reboot :P)18:16
T4<eugenio_g7> Will re-check18:16
piggz@eugenio_g7 yeah, i think i might have messed something, but not sure what, duting the lipstick upgrade18:31
piggz@eugenio_g7 libdrm updated to mer version, seems to work ok18:39
erhoof@piggz "how do you boot the manjaro kernel? " - its a UEFI tablet, so i just booted it like usual linux distro. prepared rootfs and usual initrd / vmlinuz21:51
erhoof"so, your device also doesnt turn off screen after 15 or so seconds?" it just freeze, like on power button or "systemctl suspend" command21:51
erhoofAnd it dont happend on any other linux21:52
T4<eugenio_g7> Not 100% sure, but SFOS relies on the android PM (wakelocks et al)22:35
T4<eugenio_g7> Under the hood, Sailfish OS uses the android wake locks. Typically there is no need to change anything in thekernel side (assuming it works fine with android) for the power management to work, as long as all the devicedrivers are working normally.22:39
T4<eugenio_g7> (from the HADK)22:39

Generated by 2.17.1 by Marius Gedminas - find it at!