| *** Bloop is now known as Guest8395 | 05:05 | |
| rinigus | mal: morning! ended up factoring audiopolicy into a separate service https://github.com/sailfishos-sony-tama/miniaudiopolicy. as a result, camera works as needed including shutter sounds. | 06:14 |
|---|---|---|
| rinigus | all required changes are in https://github.com/sailfishos-sony-tama/main/issues/115#issuecomment-787675508, if someone has the same issues | 06:14 |
| rinigus | mal ^ | 06:14 |
| T42 | <hacker12455> should selinux be disabled on 17.1 too? | 08:03 |
| mal | no 17.1 assumes selinux is enabled | 08:46 |
| T42 | <hacker12455> keep audit off or on | 09:19 |
| T42 | <Verevka86> <mal> https://paste.ubuntu.com/p/YXsbD4ysJh/ | 10:11 |
| T42 | <Verevka86> building hybris16.0 broken | 10:11 |
| mal | @Verevka86 when did you update submodule? | 10:13 |
| mal | update it now, just merged a fix I did yesterday | 10:14 |
| T42 | <Verevka86> @mal [update it now, just merged a fix I did yesterd …], Thanks, fix | 10:27 |
| piggz | mal: i kernel config check on the PP kernel doesnt show anything that might break sailfail, afaict | 10:29 |
| mal | piggz: time for some strace? | 10:53 |
| piggz | yeah, maybe | 11:02 |
| T42 | <zinstack625> pketo: could you please give me store access? | 11:09 |
| piggz | mal: ps aux shows jolla-mediaplayer with -prestart param ... but thats not in the .desktop file | 11:09 |
| piggz | mal: i dont think its started from the .desktop in usr/share/applications, it seems to be done via dbus???? | 11:13 |
| piggz | mal: yes, adding -v there helped, in dbus-1/services/com.jolla.mediaplayer.service | 11:15 |
| piggz | mal: https://paste.mozilla.org/aUC0Sj0X .... i wonder if it is all the dbus launched apps which fail | 11:17 |
| piggz | contacts loads, uses jail, but doesn use dbus | 11:18 |
| piggz | calendar uses dbus, doesnt open | 11:18 |
| piggz | galery works, and doesnt use dbus afaict | 11:19 |
| piggz | notes doesnt work, and uses dbus | 11:20 |
| T42 | <swanux> @mal: I kinda stuck with 16.0 base. So what do you recommend: try to go with 15.1, stick with the current situation or wait for stable 17.1? | 13:11 |
| mal | what is the problem with 16.0? | 13:11 |
| T42 | <swanux> I can get telnet (with some forced connect, and only if I hält the boot process before droid hal / systemd init), but I have no idea where to continue (tried some config modifications, manual continue, journalctl, etc, but no luck) | 13:13 |
| T42 | <swanux> *halt | 13:13 |
| mal | do you have the .rc files as mentioned in faq? | 13:14 |
| T42 | <swanux> In the init folder? Yes, I pushed them after flashing upon recommendation. | 13:16 |
| mal | how did you disable selinux? | 13:21 |
| mal | check what you have in /etc/selinux/ | 13:22 |
| T42 | <swanux> I disabled it on boot time if that's what you meant. Config says also that it's disabled (and dmesg) | 13:30 |
| T42 | <hacker12455> hm | 13:37 |
| T42 | <hacker12455> does 17.1 base boot to UI? | 13:37 |
| mal | @swanux ok, can you provide logs? have you tried starting droid-hal-init manually to see what it prints | 13:38 |
| mal | @hacker12455 it can boot to UI, I have a device which boots to UI with hybris-17.1 | 13:38 |
| T42 | <hacker12455> good | 13:38 |
| T42 | <hacker12455> was just checking cause I upped motorola-cedric to 17.1 base | 13:38 |
| swanux | mal: Yeah, sure. Which logs would you like (journals, live)? Tried droid-hal-init from telnet, no output (looks like it ran properly though as I didn't loose connecton) | 13:42 |
| mal | journal is useful | 13:45 |
| swanux | Ok | 13:45 |
| swanux | mal: Well it's interesting. Now I can't even get logging to work. (tried both persistent and automatic but nothing in var/log/journal). Is the output of journalctl --no-tail -f from telnet good instead? | 13:58 |
| mal | I usually use journalctl -b --no-pager | 14:01 |
| swanux | No journal files were found (as for some reason it doesn't work now despite my /etc/systemd/journald.conf storage setting) | 14:05 |
| mal | wait, how did you stop the boot? | 14:07 |
| mal | you should instead mask droid-hal-init service and not stop the boot to before systemd | 14:08 |
| swanux | I did touch /data/.stowaways/sailfishos/init_enter_debug2 | 14:12 |
| swanux | So should I mask now instead and delete that file? | 14:13 |
| mal | yes | 14:13 |
| pketo | @zinstack625 moto g7 added | 14:13 |
| swanux | Ok, ran systemctl mask droid-hal-init and now I don't need to force connection after reboot (great!) | 14:16 |
| swanux | mal: Here's the log https://pastebin.com/FkhF1tQR | 14:17 |
| T42 | <Verevka86> @hacker12455 [does 17.1 base boot to UI?], Yes | 14:29 |
| T42 | <zinstack625> pketo: awesome, thanks | 14:46 |
| rinigus | mal: not much is working on aosp10/aarch64 with sim card for me. mainly I can send/receive sms'es, but the rest is quite broken | 15:57 |
| rinigus | such as cell data does not connect; calls are muted; even ringing stops after a single ring tone. | 15:58 |
| rinigus | some I have seen mentioned for seine (mute calls), but the rest is not there | 15:58 |
| rinigus | mal: is that normal for aosp10/aarch64 or are there some extras found for tama? | 15:59 |
| rinigus | issues at https://github.com/sailfishos-sony-tama/main/issues?q=is%3Aissue+is%3Aopen+label%3Ahybris-10 | 15:59 |
| mal | rinigus: I seem to have same issue on my fp3 but works on seine | 16:06 |
| mal | about call audio | 16:06 |
| mal | I haven't tested that otherwise much | 16:06 |
| mal | rinigus: for me mobile data works | 16:09 |
| mal | rinigus: do you have the ohm fixes? | 16:09 |
| swanux | mal I may have found something, I just don't know how to use it. Here are the logs after manually running droid-hal-init (as I masked it): https://pastebin.com/dmbMSdWa (this was in a separate telnet terminal - in the terminal where I ran the command it produced this: nohup: appending output to nohup.out, and hanging there.) Also, I can't do | 16:19 |
| swanux | anything through telnet after this command, but I still have an active usb network connection. | 16:19 |
| mal | swanux: which device is that? | 16:25 |
| swanux | dipper. Xiaomi Mi 8. | 16:25 |
| mal | did you try 17.1 before? did you remove any changes to config repo before doing 16.0? | 16:28 |
| swanux | I use separate droid config repos for 16.0. I tried 17.1 before, that resulted in bootloop without telnet. you said something above about SELinux in 17.1 though (?), because I did 17.1 the same way as 16.0 (last time on Saturday I guess) | 16:33 |
| rinigus | mal: not sure about ohm fixes. (would have to pull logcat and journal still) | 16:43 |
| rinigus | mal: where do we get ohm fixes? | 16:44 |
| rinigus | mal: looks like I have ohm 1.2.6. | 16:45 |
| rinigus | I can see that ohm is updated to 1.3.0. any plugins I should look into as well? | 16:47 |
| T42 | <elros34> @swanux about that cgroup errors you have you can try adding systemd.legacy_systemd_cgroup_controller=yes to kernel boot arguments | 16:49 |
| swanux | @elros34 Thanks for the advice. Dumb question, but how can I add boot arguments? | 16:52 |
| T42 | <elros34> BOARD_KERNEL_CMDLINE in BoardConfig*.mk in your device repo | 16:55 |
| swanux | Thanks, (found it as BoardConfigCommon.mk under devices/xiaomi/sdm845-common) I'm building now. | 16:59 |
| swanux | mal: Thanks to @elros34 I've got a lot more promising log now : https://pastebin.com/cDYbphcC | 17:15 |
| mal | rinigus: I'll let you know about those a bit later today | 17:19 |
| T42 | <elros34> @swanux yeah not really:) android part fails same way | 17:23 |
| T42 | <elros34> you could try strace logcat to see why it fails to start | 17:24 |
| swanux | @elros34 Yeah, I see. I meant it's now shorter because it has one less error in it thanks to you. You know, small step for a senior a giant step for beginner. | 17:30 |
| swanux | Regarding logcat, I can't really use it... | 17:30 |
| swanux | logcat read failure | 17:30 |
| rinigus | mal: great! I have to look into FPD before anyway | 17:33 |
| T42 | <elros34> @swanux again do you start it after droid-hal-init appears in logs? Also strace should still shows something more than 1 line | 17:34 |
| swanux | So, if I understand correctly, I should run (strace) droid-hal-init and then try with logcat? | 17:36 |
| T42 | <elros34> I was talking about stracing logcat but you can strace droid-hal-init also. Be aware you can start droid-hal-init only once per boot | 17:37 |
| swanux | I see. Here's the strace of logcat before I run droid-hal-init (as I can't run anything after it since it breaks telnet) : https://pastebin.com/HAMsKZd9 | 17:46 |
| swanux | And here's the strace for droid-hal-init: https://paste.ee/p/dpjQl | 17:46 |
| swanux | And here's journal log for droid-hal-init (the same as before, just to have everything at one place): https://pastebin.com/cDYbphcC | 17:46 |
| T42 | <elros34> please: cat /usr/libexec/droid-hybris/system/etc/init/vndservicemanager.rc | 17:58 |
| swanux | @elros34 You, mean the output? (https://paste.ee/p/rtaF8) It's from the faq, so it's the same | 18:02 |
| T42 | <elros34> I want to be sure it's same because you refuse to upload your up to date repos so "cat /path/to/file" on device | 18:03 |
| T42 | <elros34> obviously that paste is wrong, if you have same on device then that is the reason why droid-hal-init fails | 18:04 |
| T42 | <elros34> If you want to download some file directly from github then you must first use RAW button | 18:10 |
| mal | yeah, easy to do it wrong otherwise | 18:10 |
| swanux | Thank you, I guess I'd have never thought about this stupid mistake... I'm gonna replace them now. | 18:24 |
| T42 | <elros34> I wonder why parsing error is visible in strace but not in your journal. | 18:28 |
| T42 | <elros34> Could be that you have some messages from droid-hal-init in dmesg? | 18:30 |
| mal | messages should show in journal also | 18:33 |
| swanux | Now I'm recreating journal (after running droid-hal-init), I'll post it, but this line looked familiar to me | 18:37 |
| swanux | droid-hal-init: couldn't write 7958 to /dev/cpuset/system-background/tasks: No space left on device | 18:37 |
| swanux | I'll post the whole log in a minute. Also dmesg. | 18:37 |
| swanux | Here's the journal (it's huge this time) : https://pastebin.ubuntu.com/p/MdPpS5Xdcs/ | 18:41 |
| swanux | And the whole dmesg -w output: https://pastebin.com/KYpzQMD7 | 18:43 |
| mal | swanux: did you fix all of the files you copied from github? | 18:46 |
| swanux | mal: Yes, I copied them from raw github and pushed after checking. Here's the raw output of disabled_services from cat: https://pastebin.com/bTqj27NP | 18:48 |
| T42 | <elros34> your journal is huge because you have persistent logging enabled. use -b0 switch to get journal only from current boot | 18:59 |
| swanux | Thanks for the tip! Here it is: https://pastebin.com/Em71XMeY | 19:01 |
| T42 | <elros34> droid-hal-init is still not very verbose. If you logcat still fails try again stracing droid-hal-init. At least that way it prints something | 19:09 |
| swanux | @elros34 logcat still the same, here's the new strace: https://paste.ee/p/SeytG | 19:15 |
| T42 | <elros34> it still can't read rc files.. | 19:17 |
| swanux | Interesting... | 19:18 |
| swanux | Are the permissions correct? https://pastebin.com/n9vCNKMt | 19:19 |
| swanux | I have no other idea, I checked them again, and their content is fine. I literally ctrl+a, ctrl+c, ctrl+v-d it from raw github then adb push-ed them. | 19:21 |
| T42 | <elros34> if they are readable the should be fine. Strace doesn't show any ermission issue on rc files.? I see you start whole script. Could you try just strace -f /sbin/droid-hal-init instead. Do you have any additional content in dmesg when you run strace that way? | 19:25 |
| mal | swanux: try changing the permissions to 444 | 19:26 |
| mal | @elros34 it seems it can read the files with 444 permissions based on log | 19:27 |
| swanux | mal: I changed the permissions. Now running droid-hal-init with strace as @elros34 suggested. | 19:29 |
| T42 | <elros34> mal: right 0644 are parsed but 0666 fails | 19:31 |
| swanux | Woah, now everything is different. I'll share the new data, just need a minute | 19:32 |
| swanux | This is the first part of strace -f (probably not so relevant as it continued, just in case): https://pastebin.com/3kbFeWhz | 19:35 |
| swanux | Then hundreds of lines of this: | 19:35 |
| swanux | [pid 6003] newfstatat(AT_FDCWD, "/dev/.coldboot_done", 0x7fdc6e40c8, 0) = -1 ENOENT (No such file or directory) | 19:35 |
| swanux | [pid 6003] nanosleep({tv_sec=0, tv_nsec=10000000}, 0x7fdc6e4088) = 0 | 19:35 |
| swanux | End the end is: https://pastebin.com/jBACAy4f | 19:35 |
| swanux | Here's the short journal : https://paste.ee/p/uOq8M | 19:36 |
| swanux | And the short as well dmesg: https://paste.ee/p/8hVd7 | 19:37 |
| swanux | And mal @elros34, huge difference: Now my telnet interface didn't die. | 19:38 |
| T42 | <elros34> you need to execute commands from droid-hal-startup.sh before stracing, you can see in logs it waits for /dev/.coldboot_done | 19:40 |
| piggz | rinigus: congrats | 19:49 |
| rinigus | :) | 19:49 |
| mal | @elros34 I think unmasking droid-hal-init might make sense already | 19:50 |
| swanux | @elros34 mal: I guess unmasking really makes sense, as it's been running for a couple of minutes now and still not dead | 19:51 |
| swanux | I'll wait for the end of this, and if no problems I'll unmask it | 19:51 |
| swanux | Ok, I guess I unmasked it and rebooted. Now it's not dead, but I can't see much difference (I mean visually, on the device's screen) | 19:57 |
| swanux | droid-hal seems to have inited successfully. Thank you for your help @elros34 and @mal | 20:02 |
| mal | any indication why UI fails? | 20:03 |
| T42 | <swanux> Well, I don't know what would be an indication.. (the journal you mean? Or dmesg?) | 20:20 |
| mal | journal of course, also logcat might tell something | 20:27 |
| T42 | <swanux> OK, thanks. I'll continue tomorrow I guess. | 20:32 |
| T42 | Sasank %lastname% was added by: Sasank %lastname% | 20:40 |
| T42 | <hacker12455> any idea why usb would not open during hybris-boot on 17.1 | 20:45 |
| T42 | <hacker12455> only thing we get is this | 20:46 |
| mal | did you set the environmental variable before building hybris-hal? | 20:46 |
| T42 | <hacker12455> https://bpa.st/QFHQ | 20:46 |
| T42 | <hacker12455> which one? | 20:47 |
| mal | "export TEMPORARY_DISABLE_PATH_RESTRICTIONS=true" | 20:47 |
| T42 | <hacker12455> nope | 20:47 |
| T42 | <hacker12455> what does that change? | 20:48 |
| mal | it makes kernel work | 20:48 |
| mal | otherwise the initrd doens't contain what it should contain and boot fails very early | 20:48 |
| T42 | <hacker12455> sure gonna try it | 20:48 |
| mal | you only need to run make hybris-boot and then flash the hybris-boot.img manually | 20:49 |
| T42 | <hacker12455> well that image does not create an interface too | 20:57 |
| T42 | <hacker12455> we have nothing on usb | 20:57 |
| T42 | <hacker12455> device stays on the oem logo | 21:00 |
| T42 | <hacker12455> it worked back when we were running a nougat base | 21:01 |
| mal | do you see anything in jost dmesg? does it even show up in there | 21:12 |
| T42 | <hacker12455> nope | 21:16 |
| mal | no sign of the device in dmesg? does the device remain on or reboot? | 21:29 |
| T42 | <hacker12455> remains on | 21:41 |
| T42 | <hacker12455> no sign of the device | 21:41 |
| T42 | <elros34> @hacker12455 by 'no sign' you mean there is no hybris-boot information in host dmesg or nothing at all from usb. Your paste suggest that you are not booting hybris-boot. | 22:36 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!