Mukhamedgarif | r0kk3rz: dev board with msm8940/8937 family soc | 08:01 |
---|---|---|
r0kk3rz | Mukhamedgarif: so its not yet an actual device? | 08:06 |
r0kk3rz | i assume it has an android adaptation for it | 08:06 |
Mukhamedgarif | r0kk3rz: yes. It has android adaptation based on android N. | 08:14 |
r0kk3rz | which hybris tree did you use? | 08:16 |
Mukhamedgarif | r0kk3rz: hybris-14 | 08:19 |
r0kk3rz | do you have a working lineage os image for your board? | 08:19 |
Mukhamedgarif | r0kk3rz: no. it is like AOSP. | 08:21 |
r0kk3rz | yeah so the hybris tree needs to match the base image fairly precisely, so that might not work | 08:22 |
r0kk3rz | so i would suggest either patching the AOSP tree you have, or build a lineage os image first | 08:24 |
Mukhamedgarif | r0kk3rz: I'd cherry picked hybris commits into source tree. So after some time, droid-hal-init start well and ssh works. Surfaceflinger doesn't crashes as well as test_hwcomposer. But there is still no any image on the screen. | 08:26 |
r0kk3rz | what do the logs say? like logcat and journalctl | 08:28 |
kimmoli | https://m.youtube.com/watch?v=jofNR_WkoCE# | 08:29 |
T4 | <adampigg> wtf | 08:31 |
r0kk3rz | thanks kimmoli :) | 08:32 |
NeoChapay | @dampigg what does logs say tu-ru-ru | 08:34 |
Yardanico | can the reason of bootloop on my phone be that I removed "androidboot.selinux=permissive" from kernel commandline in BoardConfig.mk ? | 08:34 |
Yardanico | but I added selinux=0 into BoardConfig.mk as well | 08:34 |
NeoChapay | @adampigg what does logs say tu-ru-ru | 08:34 |
r0kk3rz | @adampigg looks niiice - https://arstechnica.com/gadgets/2018/08/galaxy-tab-s4-review-a-solid-android-tablet-a-too-quirky-android-desktop/ | 08:42 |
Yardanico | btw, for some reason, when building sailfish flashable .zip with "mic" russian keyboard layout gets removed from LXqt so I have to re-add it manually :D | 08:54 |
Yardanico | hmm I still have a bootloop after adding permissive back | 09:55 |
mal | Yardanico: how telling how soon the device reboots so we can guess what the reason is, there some possibilities | 10:13 |
mal | *how about telling | 10:13 |
Yardanico | mal, it reboots really fast, like 5-15 seconds after booting, I think it may be a kernel misconfiguration | 10:14 |
Yardanico | I was able to mask ofono once so that's not it | 10:14 |
Yardanico | well, not mask but ln -s it to /dev/null | 10:15 |
mal | that sounds line selinux issue | 10:16 |
Yardanico | mal, yeah I think so too | 10:16 |
Yardanico | I still don't understand should I add selinux=0 into defconfig or BoardConfg because last time I added it to BoardConfig device didn't bootloop but there wasn't "selinux=0" in /proc/cmdline | 10:17 |
Yardanico | also should I keep androidboot.selinux=permissive in BoardConfig? | 10:17 |
mal | you only do what is told | 10:19 |
*** Mikaela_ is now known as Mikaela | 11:12 | |
Yardanico | so it stillbootloops, probably I need to change CONFIG_SECURITY_SELINUX_BOOTPARAM to `y` BUT it's already set up like that in defconfig but for some reason it | 11:14 |
Yardanico | *it's not applied | 11:14 |
Yardanico | so I change CONFIG_SECURITY_SELINUX_BOOTPARAM to `y` in defconfig, recompile kernel, run kernel check and it still shows a warning about CONFIG_SECURITY_SELINUX_BOOTPARAM | 11:14 |
demonaxsh | Hi, everyone | 11:19 |
demonaxsh | Are there any special features of bluetooth configure? I built a kernel with bluez support, but for mtk bluetooth devices it works on a special firmware. Now bluetooth apparently does not even detected, and of course devices are not detected either. | 11:19 |
r0kk3rz | demonaxsh: do you know what bt chip you have? | 11:30 |
demonaxsh | not idea, in the kernel config for bluetooth (wifi etc) driver - CONFIG_MTK_COMBO=y, in the specification for the device I found only Bluetooth 4.0, BLE | 11:35 |
r0kk3rz | hmm ok | 11:35 |
r0kk3rz | looks like mtk does do soc integrated ones | 11:35 |
r0kk3rz | check the boardconfig.mk | 11:37 |
r0kk3rz | or look for some bluedroid configs | 11:37 |
demonaxsh | in kernel config also: | 11:39 |
demonaxsh | CONFIG_MTK_COMBO_CHIP_CONSYS_6735=y | 11:39 |
demonaxsh | CONFIG_MTK_COMBO_BT=y | 11:39 |
demonaxsh | MTK_BT_BLE_MANAGER_SUPPORT = no | 11:42 |
demonaxsh | MTK_BT_BLUEDROID_A2DP_APTX = no | 11:42 |
demonaxsh | MTK_BT_BLUEDROID_AVRCP_TG_15 = yes | 11:42 |
demonaxsh | MTK_BT_BLUEDROID_HFP_AG_17 = yes | 11:42 |
demonaxsh | MTK_BT_BLUEDROID_PLUS = yes | 11:42 |
demonaxsh | MTK_BT_CHIP = MTK_CONSYS_MT6735 | 11:42 |
demonaxsh | MTK_BT_SUPPORT = yes | 11:42 |
demonaxsh | it's from ProjectConfig.mk | 11:43 |
Mukhamedgarif | r0kk3rz: https://pastebin.com/FB5SFGek it is an attempt to run bootanimation. | 12:14 |
r0kk3rz | Mukhamedgarif: what am i looking at? | 12:25 |
Yardanico | ehhh, I don't know.. in the first day of porting sailfish os I managed to easily boot to telnet stage but not it bootloops | 12:29 |
Yardanico | *now | 12:29 |
r0kk3rz | Yardanico: obviously you've been dutifully commiting changes to git somewhere so you can track what you changed | 12:30 |
r0kk3rz | right? ;) | 12:30 |
Yardanico | r0kk3rz, not really :D I will probably just revert kernel defconfig and boardconfig changes | 12:31 |
Yardanico | so I have CONFIG_AUDIT=y in defconfig (also CONFIG_SECURITY_SELINUX_BOOTPARAM=y) and selinux=0 in BOARD_KERNEL_CMDLINE in boardconfig, that's right or not? | 12:32 |
Mukhamedgarif | r0kk3rz: I tried to run bootanimation. It is logcat. | 12:35 |
r0kk3rz | why are you running the boot animation? | 12:35 |
r0kk3rz | and not like, test_hwcomposer or something | 12:35 |
Mukhamedgarif | r0kk3rz: I tried both. No video output. | 12:37 |
Yardanico | so HADK says to do the same if bootloop happens but it seems it doesn't help | 12:37 |
r0kk3rz | Mukhamedgarif: yeah but logs :P | 12:39 |
mal | Yardanico: did you do any other selinux or audit related changes in defconfig? | 12:40 |
r0kk3rz | demonaxsh: got your kernel repo somewhere? | 12:42 |
Yardanico | mal, I think I didn't, I'll remove all defconfig changes, and manually fix ERRORs from kernel check and then push it to github so I can show you | 12:42 |
Mukhamedgarif | r0kk3rz: here is logcat for "EGL_PLATFORM=hwcomposer test_hwcomposer" https://pastebin.com/M7uacZ9L | 12:45 |
r0kk3rz | mmm that doesnt look very happy | 12:49 |
Yardanico | I think I would just remove all sailfish os HADK files (because I already have all repos) and re-do some steps from HADK | 12:57 |
demonaxsh | kernel repo I got from vendor device, but in my opinion it is also in public domain, alps-3.18 mediatek | 13:24 |
r0kk3rz | demonaxsh: link :P | 13:28 |
demonaxsh | i do not find, what you need? config or all in kernel repo? | 13:34 |
r0kk3rz | all of it | 13:37 |
demonaxsh | I hope I will not have problems with any licenses)) | 13:39 |
demonaxsh | I also found /system/etc/bluetooth and there is also /etc/bluetooth, maybe all of exists in /system/etc/blutooth should be in /etc/bluetooth? | 13:42 |
mal | probably no | 13:43 |
Yardanico | if I run `make hybris-hal`, compiled kernel will contain changes I've made in BoardConfig, right? | 13:45 |
mal | yes, and the you of course need to package it again with build_packages.sh -d so it will be included in the next image | 13:46 |
Yardanico | mal, well I want to experiment just with kernel (by using fastboot flash) without reassembling .zip every time | 13:46 |
mal | well then it's fine, just note that in case you test some features built as modules it will more complicated than that | 13:48 |
Yardanico | so it still bootloops, kernel commit for sfos changes - https://github.com/Yardanico/android_kernel_xiaomi_msm8953/commit/810ff13e95745cfd5921adddcc44dc239b59a96b , and on this line https://github.com/Yardanico/android_device_xiaomi_markw/blob/mkn-mr1/BoardConfig.mk#L57 I added "selinux=0" after "androidboot.selinux=permissive" | 13:49 |
demonaxsh | https://drive.google.com/open?id=1g3HUGPB5otpGpPtxCkeo27QjnJuMPuHS | 13:52 |
mal | was bootparam change taken into kernel, check the .config in out/ | 13:53 |
Yardanico | mal, oh, KERNEL_OBJ/.config contains "CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=1", that's bad? | 13:57 |
mal | the commandline should override that | 13:57 |
OhYash | mal : None of the sensors work in a newer build that worked on previous one. (Proximity, Gyro & accelerometer worked previously not now). What area should I check? | 14:17 |
mal | OhYash: faq, ctrl+f ->sensors | 14:19 |
OhYash | ah shit forgot. sorry to disturb. | 14:20 |
rydare | you dare disturb the great mal? | 15:15 |
rydare | oops i disturbed him with highlight | 15:16 |
rydare | sorry m*l | 15:16 |
Yardanico | so I re-installed all SDK tolling etc, so now my device boots to terminal and dmesg says that it booted in SELinux permissive mode | 16:44 |
Yardanico | that's bad, right? | 16:44 |
Yardanico | (i didn't add selinux=0 to cmdline yet) | 16:44 |
mal | not sure what you mean, did you do anything to the adaptation packages? | 16:48 |
mal | Yardanico: why are you only doing part of the instructions? it clearly says to add selinux=0 | 16:48 |
Yardanico | mal, ok, I'll add selinux=0 | 16:49 |
Yardanico | mal, ok, so now I added "selinux=0", and device still reboots (but I can connect through telnet for a couple of seconds), so dmesg now says "[ 0.005842] SELinux: Disabled at boot." | 17:02 |
Yardanico | complete dmesg - https://gist.github.com/Yardanico/8791aa54f85f12f2b9b3e6f3dcfffee2 | 17:04 |
mal | Yardanico: is that 14.1 based port? | 17:20 |
Yardanico | mal, yes | 17:21 |
mal | Yardanico: you didn't seem to run the symlink script mentioned in 14.1 porting section of faq (linked in channel topic) | 17:23 |
Yardanico | hmm, I think I did but I'll try again | 17:23 |
mal | oh, you did, sorry | 17:23 |
mal | missed that part of the log | 17:23 |
Yardanico | how can I dump all systemd logs to a file? journalctl > out.txt ? | 17:26 |
mal | Yardanico: maybe journalctl -n1000 or something and the output it to file, some people use also --no-pager as option | 17:29 |
Yardanico | mal, and what if I just copy /var/log/journal folder? can I access contents on a PC? | 17:30 |
Yardanico | ah nvm https://unix.stackexchange.com/questions/199988/howto-inspect-systemd-system-journal-from-another-system | 17:30 |
mal | I think the issue could be that some firmware files are not found due to missing symlinks or something, or some needed partitions are not mounted | 17:33 |
Yardanico | mal, hmm, I'll try to add some partitions to fixup-mountpoints | 17:34 |
mal | Yardanico: what partitions did you add before? | 17:35 |
Yardanico | mal, just same as mido (my device seem to have same partition table as mido because devices are pretty close hardware-wise) | 17:35 |
mal | make sure the partition table really is the same | 17:36 |
Yardanico | mal, yes I looked at all partition names | 17:36 |
mal | other option is that the udev rules are not working as they should, try to get output of ls -lR /dev/block/ and also journal log might tell something | 17:38 |
Yardanico | oh no journalctl is a bit broken because when the device loads it has incorrect clock but then it syncs (maybe with device's built-in RTC) time and journalctl is broken into two parts | 17:38 |
mal | doesn't matter | 17:38 |
Yardanico | it even tried to load libraries for "hwcomposer device" but all libs were not found | 17:39 |
mal | ? | 17:39 |
Yardanico | mal, this part of the log https://gist.github.com/Yardanico/02d0f9aacec1e0e36594e2bfad8bdf7d | 17:40 |
Yardanico | so it seems like the last part of the log is always a calltrace about unbalanced IRQ 55 or 73 | 17:45 |
Yardanico | *72 | 17:45 |
Yardanico | logs from 3 boots (or 4) without the first part (because it's separated) https://gist.github.com/Yardanico/61cf73e096ba15ae6cbbf5f2d044dba9 | 17:45 |
Yardanico | oh yeah I found some fixes for these IRQs in another kernel repo for my device | 17:47 |
Yardanico | I didn't try this repo yet, I just think it might not work (because it's currently used for 8.1 treblized ROM) | 17:47 |
Yardanico | but I'll try it now | 17:48 |
Yardanico | yay another kernel seems to have solved this issue! it doesn't reboot now. so splash logo was removed from the screen, it turned off, turned on, and turned off again. gonna see the logs | 18:16 |
mal | hmm, ok | 18:17 |
Yardanico | hmm, test_hwcomposer can't find libsdmextension.so (and some other libs), but they are located in /system/vendor/lib64 | 18:40 |
mal | wondering if those are needed or not | 18:42 |
Yardanico | btw, when I run test_hwcomposer backlight turns on for a second | 18:45 |
Yardanico | I'll capture strace | 18:45 |
mal | I assume you have set the correct env var before that? | 18:45 |
Yardanico | mal, you mean LD_LIBRARY_PATH or what? | 18:45 |
mal | EGL_PLATFORM | 18:45 |
Yardanico | ah, yeah, of course | 18:45 |
mal | wtth correct value | 18:45 |
Yardanico | correct value? | 18:45 |
Yardanico | faq-hadk says "EGL_PLATFORM=hwcomposer test_hwcomposer" | 18:46 |
mal | some device have had broken 32-bit hwcomposer and there is another way to get graphics working if that is the case, but logs would be useful | 18:46 |
Yardanico | I run strace like that? "EGL_PLATFORM=hwcomposer strace test_hwcomposer" | 18:47 |
Yardanico | here's the strace (it's big) https://gist.github.com/Yardanico/4d81ce6fbbb1a1dab33450b8a8d1070f | 18:48 |
mal | ok, but also get dmesg, journalctl and /usr/libexec/droid-hybris/system/bin/logcat | 18:48 |
Yardanico | ok | 18:48 |
Yardanico | also logcat is spammed by adsp | 18:48 |
Yardanico | oh well, no, I forgot to say that dmesg is spammed by something too :) | 18:49 |
Yardanico | mal, dmesg/journalctl/logcat - https://drive.google.com/open?id=1jodY2H3mbC9yO2-iIEfedjzKBeyd9ow0 | 18:59 |
mal | can you see any adsp firmware files anywhere on the device, some vendor partition or /system/etc/firmware or something | 19:14 |
Yardanico | mal, well there are some (some in other dirs and some files in /firmware/image) https://gist.github.com/Yardanico/7f4626b7de26bff7fbe20da671c930da | 19:17 |
mal | can you get the ls -lR /dev/block I asked earlier | 19:18 |
Yardanico | mal, https://gist.github.com/Yardanico/1a73eea5fa8a589c2841226c4e0e2320 | 19:19 |
mal | Yardanico: the kernel messages look terrible, are you sure that kernel is ok? | 19:19 |
Yardanico | mal, well it doesn't error like that on real system, I might try one another kernel too | 19:20 |
Yardanico | I mean on android | 19:20 |
mal | where do you get the kernels? | 19:21 |
mal | why are there many kernels available? | 19:21 |
Yardanico | mal, because there are several developers working on custom ROMs for my device, I can also try official kernel by xiaomi... but I think it would be worse | 19:21 |
wiktorek140 | Yardanico: have u correctly mounted fsg? | 19:29 |
r0kk3rz | hmm xiaomi or xda special, thats a tough choice | 19:29 |
r0kk3rz | id probably take xiaomi | 19:29 |
Yardanico | wiktorek140, what is fsg? :P | 19:29 |
Yardanico | to fixup-mountpoints you mean? i'll try. can I do that on the device without rebuilding whole .zip? | 19:30 |
wiktorek140 | Yardanico: partition, on some devices (for example surnia) it required to bootup gui | 19:30 |
Yardanico | and can I edit it on device without remaking whole zip? | 19:31 |
wiktorek140 | Yardanico: u can try but it require to rebuild kernel, and edit /lib/systemd/system/fsg.mount on device | 19:31 |
Yardanico | rebuild kernel? with what changes? | 19:32 |
wiktorek140 | add fsg partition to fixup-mountpoint and then rebuild kernel | 19:33 |
Yardanico | I thought that it wouldn't be very hard to port sfos to my device because santoni and mido are already ported :) | 19:33 |
Yardanico | ah, ok | 19:33 |
r0kk3rz | we have had reasonable success with xiaomi devices | 19:34 |
wiktorek140 | Yardanico: and consider adding "droid-hal-markw-detritus" to patterns | 19:36 |
Yardanico | wiktorek140, it's already here | 19:36 |
wiktorek140 | oh, sorry, i dont supose to find it on upper part of file ;) | 19:37 |
Yardanico | wiktorek140, so I just edit fixup-mountpoint and then `make hybris-boot`? | 19:39 |
wiktorek140 | Yardanico: yes, and then flash hybris-boot.img to device | 19:39 |
Yardanico | thanks, I'll try | 19:39 |
mal | wiktorek140: Yardanico after editing fixup flashing kernel is not enough | 19:42 |
Yardanico | I just think that it wouldn't help me because it's not required for santoni/mido | 19:42 |
Yardanico | (and btw, all custom kernel for my device were developed from a custom mido kernel) | 19:43 |
Yardanico | OHHH | 19:45 |
Yardanico | https://bitrvmpd.github.io/sailfish-santoni/Troubleshooting | 19:45 |
Yardanico | "This appears in dmesg, no GUI is displayed kgsl kgsl-3d0: |_load_firmware| request_firmware(a530_pm4.fw) failed: -2" i have same error! | 19:45 |
Yardanico | so I need to enable some flags | 19:46 |
Yardanico | GUI WORKS | 19:50 |
Yardanico | HOLY SH*T | 19:50 |
Yardanico | and touchscreen works! | 19:50 |
Yardanico | and audio works! | 19:52 |
Yardanico | and sms work (i received some right now)! | 19:53 |
r0kk3rz | Yardanico: see that wasnt hard :P | 20:11 |
Yardanico | r0kk3rz, yes it wasn't :) | 20:12 |
Yardanico | thank you all, I think I can probably fix almost all other issue via mido/santoni repos | 20:13 |
Yardanico | omg i'm so happy | 20:13 |
mal | Yardanico: so my guess of some firmware problem was correct, but the reason was in kernel not in userspace | 20:19 |
Yardanico | mal, yeah, thank you very much, I'm amazed how calm you are when people (like me) ask you a lot of stupid questions :) | 20:19 |
mal | Yardanico: I usually only get annoyed if people don't even try to find the solution themselves but instead assume we just tell everything that is needed | 20:21 |
r0kk3rz | and then dont follow instructions | 20:22 |
mal | yep | 20:22 |
mal | Yardanico: some things to look into are chapters 13.2 and 13.3 in hadk pdf | 20:33 |
Yardanico | mal, ok, thanks | 20:33 |
Yardanico | I probably wouldn't do anything more today :) | 20:33 |
mal | probably a good idea | 20:35 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!