Monday, 2019-07-01

T42<adampigg> Mal, so, options? R u happy i have everything mounted?06:44
Mister_Magistermal: just friendly reminder :P06:45
T42<adampigg> Mister_magister: we appreciate your patience, you are now no2 in the queue and will get to you shortly06:47
Mister_Magister@adampigg staph it i'm just reminding06:47
T42<DSstill01> Can one of you post the output of 'ls /etc/pulse'?09:58
malhow about you provide what you have?10:14
T42<DSstill01> Nothing10:22
T42<DSstill01> I deleted it10:22
T42<DSstill01> After fm changes i had no incall audio, so i deleted the whole dir. Now i have to restore it by reinstalling packages10:23
T42<birdzhang> lipstick crash random on 15.1 base with dmesg log  binder_alloc: 14183: binder_alloc_buf, no vma10:26
T42<birdzhang> full dmesg log https://pastebin.com/jvjJmxd510:27
T42<birdzhang> i'm stuck on this issue10:28
KALUBEHi, I'm porting to a Samsung Galaxy J3 (2016). I have telnet and the system is up, but systemctl hangs on some commands and masking/manually starting droid-hal-init causes a reboot to recovery (confirmed by strace)12:14
KALUBEsystemctl status: https://pastebin.com/3nGQwkEW and journal log https://pastebin.com/NvK3psdH12:14
KALUBEI've removed a lot of spam from power_supply in the journal log.12:15
malwhich android base?12:26
KALUBEcm-14.112:28
malI assume you have added the 14.1 specific things from faq?12:34
KALUBEOh shoot, missed them12:36
KALUBEMal: Still the same issue, running systemctl mask droid-hal-init still hangs13:10
malbut does droid-hal-init fail?13:11
KALUBEyes13:16
malwith what error?13:17
malthe changes I mentioned from faq help with droid-hal-init, but there are various things that can be wrong13:18
maldid you need straggler files define in droid-hal spec?13:18
KALUBEI don't have a message about unpackaged files found when running build_packages so I assume not? This is the output of strace droid-hal-init https://pastebin.com/92DwNhPU13:19
KALUBEI'm not sure that is wasn't called by systemd before that, will make sure it's disabled and see if the output is different13:21
KALUBENo it was masked with that output. I've noticed in systemctl that init-done.service is hanging on wait-for-file /run/user-sessions/user-init-debug.flag, is this set by droid-hal-init? Or could it be relates13:25
malKALUBE: looks like you didn't disable selinux correctly13:25
malso enable selinux bootparam kernel config (keep audit enabled), then add selinux=0 to kernel commandline13:26
malthere should instructions to that somewhere13:26
KALUBEFrom the earlier log? I noticed that and patched the boot image.13:26
KALUBEI currently have CONFIG_AUDIT disabled, SELINUX enabled and both disabled with cmdline. I'll set them both enabled in kernel config and disable them with cmdline?13:26
malshow your kernel config13:31
KALUBEI've just adjusted it... https://pastebin.com/WGk0FD2413:32
KALUBEChanges: CONFIG_SECURITY_SELINUX_BOOTPARAM=y CONFIG_AUDIT=y SELINUX_BOOTPARAM=y13:32
KALUBEAnd selinux=0 audit=0 is in cmdline13:33
malno need to put audit=0, I never use that13:35
KALUBEAh ok13:35
malalso line 3668 is wrong in defconfig13:35
KALUBEShould be unset?13:36
malremove the line13:36
malthat value is already set on line 346013:36
KALUBEOh, they do the same thing?13:36
malthere is no such thing as SELINUX_BOOTPARAM, it's CONFIG_SECURITY_SELINUX_BOOTPARAM13:37
KALUBEInteresting, the mer_verify_kernel_config script references it13:37
KALUBEGuessing it's shorthand13:37
malyes13:37
malsame that it says AUDIT=y which is of course CONFIG_AUDIT=y13:38
KALUBEMakes sense.13:41
KALUBEOk, it boots, droid-hal-init is masked13:42
KALUBERunning strace droid-hal-init still causes a reboot to recovery13:42
maldoes it still complain about selinux in strace?13:44
KALUBEThis is the strace https://pastebin.com/MF6RDyJW it mentions selinux but I'm not sure exactly what to look for13:45
KALUBEstatfs64("/sys/fs/selinux", 88, 0xbe8278f0) = -1 ENOENT (No such file or directory)this line perhaps13:45
maldroid-hal-init: Security fail13:46
malwhich means selinux afaik13:46
malcheck the kernel commandline from /proc/cmdline13:47
malalso check selinux in kernel config using : "zcat /proc/config.gz | grep SELLINUX"13:48
mal*"zcat /proc/config.gz | grep SELINUX"13:48
KALUBENo mention of selinux=0 in the cmdline, or in config.gz https://pastebin.com/eDpdQZsJ13:49
KALUBEWhen I unpack hybris-boot.img it has selinux=0 in the cmdline so this is really weird13:49
maland you are sure you correctly flashed the kernel?13:50
KALUBEI boot TWRP and flash hybris-boot.img to the "boot" partition13:50
KALUBEI haven't been able to use the standard sfe zip flash because tar runs out of memory13:51
KALUBEam I missing a step?13:51
malI have never used twrp to flash kernel like that, I flash kernel using fastboot13:51
KALUBEThe phone doesn't have fastboot, I will try flashing it using heimdall13:52
malanyway you need to make sure the kernel is correct before you can continue figuring out if things fail otherwise13:59
KALUBEYeah, I've just managed to flash with heimdall, it was having some... Difficulty. But the cmdline is the same14:00
KALUBEIt's like it's using some other cmdline entirely?#14:01
KALUBEI may have found the cause of the issue...14:01
KALUBEThere is a boot partition but also a kernel partition, I think the kernel partition is actually the boot partition, and it's been using the lineage boot image the whole time14:02
KALUBEIt seems this was not it. There also a boot2 partition?14:07
malno idea about that device, but since you did already boot to sfos it should have been the actual kernel14:09
malare you sure you copied the correct kernel to recovery for flashing?14:09
KALUBEI was right, I checked the updater script for lineage and it flashed it's boot.img to the KERNEL partition. So it is the correct one.14:09
KALUBEI did have the correct kernel, I was flashing it to the wrong partition though. But having just flashed it, /proc/cmdline didn't change?14:10
KALUBEflashed it to KERNEL that is14:10
KALUBENo luck, I'm going to go and come back to this later.14:17
malwondering what you did differently before14:18
piggzevening all18:01
justgerdhey piggz18:02
Mister_Magisterpiggz: no18:02
piggzMister_Magister: no what?18:03
Mister_Magisteryou know what18:03
justgerdMister_Magister: not evening yet in your timezone?18:05
Mister_Magisterjustgerd: it is18:05
justgerdMister_Magister: where did that no come from then18:05
Mister_Magisteryou will see18:06
justgerdokay i guess18:06
Mister_Magisterpiggz: got wifi?18:07
piggzMister_Magister: nope18:07
piggzu got sensors?18:07
Mister_Magisteri'm getting 5z first18:09
Mister_Magistertoday is the day i get gui18:10
Mister_Magisteri hope18:10
piggzMister_Magister: the mount units you sent .... they dont appear to be for this device!  im just cleaning it up now i have proper ones from dhd!18:10
Mister_Magisterthey are for this device18:11
Mister_Magisterat least according to TheKit mounts18:11
piggzthey look hand-balled to me, the mount commands didnt match the comments18:12
piggzanyway, i have proper ones now in dhd18:13
Mister_Magisterthey were totally hand made18:14
malare sensors really not working on that device?18:15
piggzmal: yes, but i havnt looked into why yet....18:16
malso maybe the mounts really are a problem is almost nothing works18:16
piggzmal: well, mounts _should_ be good now..... lets see18:16
piggzmal: what can i show you, output of mount?18:18
piggzit should hopefully make more sense...providing it boots18:19
piggzwhich ofc it doesnt18:20
Mister_Magistermal: nah there is missing lib mount and stuff18:21
piggzmal: ok, mounts now as clean as i think, with a single hand-balled mount unit for /vendor, which I think we discussed adding to fstab anyway....18:30
piggzhttps://paste.gnome.org/phlv9hfoo18:31
Mister_Magisterwtf i flashed new rootfs now i got bootloop18:32
piggzMister_Magister: oh fuck, mal was blooming right18:35
Mister_Magisterhm?18:35
Mister_Magistermal is a flower?18:35
Mister_Magistersince when?18:35
T42<adampigg> (Photo, 1920x2560) https://irc.thaodan.de/.imgstore/08Kq40JSDT.png18:36
Mister_Magisterit randomly stopped rebooting18:36
Mister_Magisterlol18:36
Mister_Magisterheh18:36
Mister_Magistergj18:36
Mister_Magisterwe have that now18:36
piggzmal: i bow again ;)18:36
Mister_Magisterafter 20 reboots18:36
Mister_Magisterit stopped rebooting18:36
Mister_Magistercause?18:36
Mister_Magisteri don't even have pstore lol18:37
Mister_Magisterdroid-hal-init ffs18:37
Mister_Magistermal: idea what patch i could be missing? https://paste.opensuse.org/view//2612451218:43
Mister_Magisteralso mal reminder18:45
malpiggz: nice, I thought the mounts and symlinks should be enough :)18:48
piggzmal: youre a goddamn smart arse :P18:48
piggzso....radio18:48
mal:D18:48
Mister_Magisterpiggz: radio?18:49
piggzi got a message saying 'incompatible handset' when searching for a network18:49
piggzMister_Magister: mobile net18:49
Mister_Magisterhm18:49
Mister_Magisterthough thekit would do that but k18:49
piggzi wonder if the pro1 isnt compatible with my network18:49
Mister_Magisterpiggz: volte/18:50
Mister_Magister?18:50
piggzno, its regular old 3/4g on ThreeUK18:50
Mister_Magisterhttps://paste.opensuse.org/view//85339088 lol test_egl18:51
Mister_Magisterpiggz: assume it should work18:51
malMister_Magister: where is that lib on device?18:51
Mister_Magistergod knows but that's not important18:52
Mister_Magisterwhy hwservicemanager and servicemanager fails is important18:53
Mister_Magisterwait i will replace linker maybe18:53
Mister_Magistermal: btw this is different device (sorry for confusing)18:54
Mister_Magisterpiggz: if adding fstab.qcom and the other thing to hybris modules to build is enough shouldn't we replace vendorimage with that?18:55
Mister_Magisterwell some devices will fail to build but…18:55
piggzMister_Magister: i dont want to change the hybris-boot process for all devices just yet....18:58
Mister_Magisterjust giving ideas eh18:58
Mister_Magisterhybris16 isn't really out18:58
piggzid like to think of a way to pass in a variable, so that each device could add to the list of things to buiild18:58
Mister_Magisterporting is hard19:00
Mister_Magisteri disabled droid-hal-init and now i don't get rndis19:01
Mister_Magisteris that reasonable at all? no19:01
piggzrats, wifi stopped working19:01
piggzafter reboot19:01
Mister_Magistersee19:03
Mister_Magisterit's hard19:03
Mister_Magisterit does totally unreasonable things19:03
Mister_Magisteri would really love to have mal's hybris1619:03
piggzgo figure, rebooted and wifi works19:05
Mister_Magistertiming19:05
Mister_Magistereasy19:05
*** justgerd is now known as JustGerd19:05
JustGerdwait mal is working on hybris16?19:07
Mister_Magisterno19:19
Mister_Magisterwe are19:19
malwell I have almost all on my computer but I haven't pushed those to public19:19
JustGerdmal: ah okay makese sense19:39
KALUBEI'm still having no luck with droid-hal-init. It seems that my cmdline get's ignored by samsung's bootloader, I have tried disabling SELINUX and AUDIT in the kernel config but it still fails and causes a reboot if I mask droid-hal-init and start it manually https://pastebin.com/7gqXwjF719:45
malKALUBE: you need to find some way to disable selinux in a way that it doesn't break anything20:19
malMister_Magister: droid-hal-init initializes configfs usb usually20:37
Mister_Magisterah20:37
Mister_Magister usually when i masked dhi i still had networking ;-;20:37
malit works if first telnet make it work20:38
malI think20:38
piggzi notice that the init script starts network, then, when dhi starts, the connection drops and comes up again20:43
malyes20:43
malthat way it should usually do it, assuming init script works for the device20:43
piggzmal: where does /dev/vhci come from?20:44
KALUBEmal: Any suggestions on disabling selinux? Sailfish doesn't have /etc/selinux, I'm not sure where to go from here to be honest20:45
maltry what happens if you set all of the selinux kernel configs to =n, I really don't know any other way except patching more of android init20:47
malpiggz: you need the vhci kernel config and then bluebinder, after those it should work20:47
piggzi have part 2 of that lot....20:48
malpiggz: did you make sure you have the bluetooth firmware symlink also20:48
piggzmal: unlikely....20:48
malpiggz: https://github.com/mer-hybris/android_kernel_sony_msm/blob/hybris-sony-aosp-8.1.0_r52_20190206/arch/arm64/configs/aosp_nile_pioneer_defconfig#L81220:48
malpiggz: I think it might need similar symlink you added for /firmware, check out/..../root again for the links it created there20:49
malprobably /bt_firmware or something like that20:49
piggzmal: i have something like that...20:50
vknechthello :-) been trying to get systemd logs on sdcard, does that look like an honest attempt ? any obvious flaw which would prevent that to work ? https://pastebin.com/GSzMTVgr21:53
malvknecht: why not just enable persistent journal log?21:55
vknechtbecause I'd then have to copy/dd partition back from fs to read it I think21:56
vknechttho it's possible, just a hassle21:56
vknechtother way would be to mod preinit, but would have to override/sparse a jolla package, which seems a hassle too21:58
vknechthere's where I'm at, logs gotten from preinit late.d plugin to sdcard, no telnet available : https://pastebin.com/2aiY4J1G22:03
vknechtnot in the setup to continue right now, but if you have ideas, I read logs :-)22:04
vknechtjust having a systemd unit to spit all logs on sdcard would help22:05
vknechtmy best guess atm is I miss a /vendor symlink to /system/vendor, but I'm somewhat blind (tried much of rndis config recommendations, even disabling configfs completely)22:08
vknechtsymptoms are : stays on vendor logo for ~10 seconds, then purple led for ~3 seconds (or indefinitely on previous attempts) and device stucks on logo indefinitely (4/5 minutes)22:15
vknechtbtw I tried the community-way extract-rootfs-manually but it fails/crashes twrp, so atm I'm doing mixed-way aka. lvm but keep /system partition (skipping fimage stuff)22:20
vknechtgood night and sweet dreams :-)22:26

Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!