| T42 | <Mister_Magister> Failed to access management interface | 00:35 |
|---|---|---|
| Mister_Magister | was meant to search that oops | 00:35 |
| *** n2klb_ is now known as n2klb | 01:58 | |
| rinigus | @b100dian: I have this patch pulled in https://github.com/mer-hybris/hybris-patches/commit/00c92c4c2dc5ffb52756b246017c7f7536195c00 . however, there is no linkerconfig in requested spot on my build | 06:33 |
| rinigus | in logs - linkerconfig: executing /usr/libexec/droid-hybris/system/bin/linkerconfig failed: No such file or directory | 06:33 |
| rinigus | you don't seem to have this patch applied | 06:33 |
| T42 | <b100dian> No, I dont have it | 07:47 |
| T42 | <b100dian> So you do have it applied? | 07:48 |
| rinigus | @b100dian: yes. and in the logs it looks for /usr/libexec/droid-hybris/system/bin/linkerconfig which I don't have on device. probably something that comes in future SFOS versions? | 07:50 |
| rinigus | was rather simple to find and confirm by comparing manifest snapshots :). hopefully, will fix my boot too | 07:52 |
| rinigus | will see tonight | 07:52 |
| T42 | <b100dian> Hmm so it paches an executable that it is not packaged, in droid hal? | 07:53 |
| T42 | <b100dian> Or something didnt build | 07:53 |
| T42 | <b100dian> What if you copy on devixe your system linkerconfig there?:D | 07:53 |
| rinigus | @b100dian: looks like it. we probably have to build it separately, as we do with i18n | 07:55 |
| rinigus | @b100dian: copy would be simplest way to get it booting and later update from full sfos. will test when back home | 07:55 |
| sharks | Can someone idiot-check why my OBS packages are failing to build with `nothing provides pkconfig(android-headers)`, `nothing provides pkconfig(libgbinder)` etc.? Reading irc logs people say wrong arch etc. but I can't see where I've got anything but aarch64 in there. | 08:04 |
| rinigus | sharks: look into droid-hal config of nagara. you need to "build" it - use similar approach as used there | 08:06 |
| rinigus | sharks: add build.script to it | 08:07 |
| sharks | Ohh - I am indeed missing build.script. Thankyou! | 08:08 |
| sharks | Hmm, droid-hal-$device now has build.script in it but OBS says it's "excluded" - am I missing any other step? Sorry to be a pain, I'm new to this. | 08:12 |
| rinigus | sharks: this one too - https://build.sailfishos.org/package/view_file/nemo:devel:hw:sony:nagara/droid-hal-nagara/droid-hal.spec | 08:17 |
| sharks | Oh God, sorry. I think I need more sleep, didn't realise there was two pages and that file was on the second page!! Thanks rinigus. | 08:19 |
| sharks | Okay, stuck again - does anyone know why I've got this one now? Not sure what I've done differently to droid-hal-img-boot-fp5 that would cause this... | 09:27 |
| sharks | RPM build errors: | 09:27 |
| sharks | Could not canonicalize hostname: phost18 | 09:27 |
| sharks | Bad exit status from /var/tmp/rpm-tmp.WMIfot (%build) | 09:27 |
| sharks | phost18 failed "build droid-hal-pdx225-img-boot.spec" at Fri Jul 17 09:25:13 UTC 2026. | 09:27 |
| rinigus | sharks: error is a bit above it - /usr/bin/env: 'python3' | 09:30 |
| rinigus | looks like python dependency is missing in spec | 09:30 |
| sharks | Hmm, in fp5 the python dependency is in droid-hal-device-img-boot.inc, but by the time I cloned that submodule two years later it was taken out. | 09:33 |
| sharks | Not sure why that would be the case, but thanks anyway rinigus - I'll work around it... | 09:34 |
| sharks | Perhaps another silly question - where do the repo URLs in droid-config-xqcc72-ssu-kickstarts.aarch64.rpm come from? They're assuming my repo is at nemo:testing:hw:sony:xqcc72 not nemo:devel:hw:sony:murray | 10:15 |
| sharks | I'm completely stumped as to how to fix that, I can't see at all how it's supposed to be configured. | 10:48 |
| rinigus | sharks: that is not that silly question. if I remember correctly you need to add https://build.sailfishos.org/package/show/nemo:devel:hw:sony:nagara/community-adaptation-devel . notice where does it point to and make similar github repo for your port. which SPEC is used from rpm/ , in case of several SPEC files, is determined by OBS repo name. so, if name is community-adaptation-devel then corresponding spec is used. that way you | 10:53 |
| rinigus | will be able to define urls based on whether you build devel (for you) or testing (for users) version | 10:53 |
| sharks | rinigus - thanks! That's exactly what I was missing. Can I ask a follow-up? In some ports the developer has used `latest` repos, and in others they use `releasemajorminor`. In nagara you're using a bit of both. What is the rationale behind this? Is there one or the other that I should be using? | 10:58 |
| rinigus | sharks: obviously, nagara is using the best and the only correct approach. latest is used for devel. for user's facing testing, we define subproject https://build.sailfishos.org/project/subprojects/nemo:testing:hw:sony:nagara for each release. that allows you to add or drop packages between releases. has been battle tested in sony tama and some other ports | 11:06 |
| sharks | Right, cool. I noticed nagara has subprojects like that. Are they something I can create myself or do I need to ask for it from keto etc.? Right now I'm just focusing on getting the devel one going, so I'll use latest for that, and then once I've decided I know what I'm doing I want to retrace my steps and use devel as a guide to put the testing one together. | 11:08 |
| sharks | Oh - it looks like I can make my own subprojects. Cool! Thanks again rinigus, you're a handy bloke to have around. | 11:10 |
| rinigus | good luck! | 11:10 |
| sharks | Thanks, I might need it :) | 11:11 |
| mal | Mister_Magister: you might find a commit for CMAC in fp2 kernel, branch hybris-21.08.1-rel, check also other thing next to it | 12:22 |
| mal | rinigus: which android base was that? | 12:23 |
| mal | the linkerconfig issue | 12:23 |
| rinigus | mal: its lineage21/android14 | 12:26 |
| mal | rinigus: which droid-hal-device submodule revision? | 12:27 |
| rinigus | let me check | 12:27 |
| mal | rinigus: which location do you have linkerconfig in out/ | 12:29 |
| Mister_Magister | mal: is cmac ABSOLUTELY needed? | 12:29 |
| mal | not sure | 12:29 |
| Mister_Magister | want to spend some fun friday afternoon with me trying to figure out why am i getting "Failed to access management interface"? I built the backports | 12:29 |
| rinigus | mal: in one of the apex ones, runtime | 12:30 |
| mal | ok then it should get copied if you have correct submodule version | 12:31 |
| mal | did it get copied to droid-hal rpm? | 12:31 |
| mal | or maybe you have symlink issue | 12:31 |
| rinigus | mal: we have our own dhd as this one is still pending https://github.com/mer-hybris/droid-hal-device/pull/345 | 12:31 |
| rinigus | which means I have relatively old dhd base and this is not there - https://github.com/mer-hybris/droid-hal-device/commit/21cc677be30b4adb152843d51265ae4bb0641a39 | 12:32 |
| rinigus | will rebase, thanks! | 12:32 |
| mal | rinigus: don't rebase to latest | 12:33 |
| mal | for now rebase on top of be67bbcdcfb9f1e392dbac699928fa29c5c103cd | 12:33 |
| rinigus | thank you very much! (was going to check in release notes and see which one to use) | 12:33 |
| mal | thinking if I should revert that last change until I fix it properly | 12:34 |
| Mister_Magister | so mal, if you could, any ideas about fm radio and/or bluetooth? :P | 12:42 |
| mal | I htink management inteface tries to suggest it's using new enough driver, you are sure backports are in use? | 12:44 |
| Mister_Magister | I'm not | 12:45 |
| Mister_Magister | how do i verify | 12:45 |
| mal | you built it after building kernel? | 12:45 |
| Mister_Magister | yes | 12:45 |
| Mister_Magister | in backlog you said that managment interface error is when you didn't build backports but are using bluez5 | 12:45 |
| mal | and kernel has bt stuff as modules? | 12:45 |
| Mister_Magister | yes | 12:45 |
| Mister_Magister | yeah i'm as stumped as you are xd | 12:47 |
| Mister_Magister | the only difference is lack of CMAC but that doesn't seem like it would invoke this issue | 12:48 |
| Mister_Magister | https://paste.opensuse.org/pastes/ba469c6e39c0 modules loaded | 12:50 |
| Mister_Magister | https://paste.opensuse.org/pastes/878424f90032 here's me building kernel then backports | 12:50 |
| Mister_Magister | the backports are tiny bit outdated but nothing important | 12:51 |
| Mister_Magister | literally just my commit which shut up warnings lol | 12:51 |
| Mister_Magister | compat module is not loaded idk if thats needed but loading it doesn't help either | 12:53 |
| Mister_Magister | oh, I added CMAC to the old kernel | 12:56 |
| Mister_Magister | well then maybe it's needed | 12:56 |
| mal | there is the commit about hid backport also if you want to support that | 13:01 |
| Mister_Magister | mal: with CMAC the backports asked me to regenerate config and this time ti touched hci_smd | 13:03 |
| Mister_Magister | so i think CMAC was needed | 13:03 |
| Mister_Magister | mal: hid backport? what's that for? | 13:03 |
| Mister_Magister | yeah and this time backports also touched bt module so i think that was it | 13:04 |
| mal | bluetooth hid, so keyboards etc | 13:05 |
| Mister_Magister | oh, that doesn't work? | 13:05 |
| mal | fp2 kernel has "hid: Backport hid-generic driver" | 13:06 |
| sharks | Sorry to interrupt, quick question - What is out-of-image-files.files for? | 13:06 |
| Mister_Magister | oki will look into it | 13:06 |
| Mister_Magister | but first i want to get bt working | 13:06 |
| mal | sharks: that lists what files will kept out side the installation zip | 13:07 |
| sharks | Thanks mal, in other words it's not mission critical | 13:07 |
| Mister_Magister | great, now it's just bootlooping | 13:11 |
| sharks | I've just tried to build my first image since all the LVM & OBS changes, and ended up with a new error trying to manually run `mic` per the hadk-hot | 13:11 |
| sharks | Info[07/17 13:03:45] : Running pack scripts ... | 13:11 |
| sharks | $ANDROID_ROOT/sfe-xqcc72-5.1.0.11devel1 $ANDROID_ROOT | 13:11 |
| sharks | Resize root and home | 13:11 |
| sharks | losetup: /dev/loop0: failed to set up loop device: No such file or directory | 13:11 |
| sharks | Info[07/17 13:03:45] : Script returned with non zero status, failing. | 13:11 |
| sharks | Error <creator>[07/17 13:03:46] : Failed to execute %pack script with /bin/bash | 13:11 |
| sharks | Seems like everything made it into the `sfe-xqcc72-5.1.0.11devel1` directory, but for whatever reason it couldn't jam it all into a *.zip | 13:12 |
| sharks | https://paste.opensuse.org/pastes/112e3a16e93a | 13:14 |
| Mister_Magister | hmm now it's just bootlooping without even booting :/ | 13:24 |
| Mister_Magister | dang it | 13:34 |
| Mister_Magister | got it to booting again but it just bootloops | 13:34 |
| Mister_Magister | [ 54.318445,0] kernel BUG at /home/foidbgen/hadk-titan/kernel/motorola/msm8226/fs/sysfs/dir.c:534! | 13:35 |
| Mister_Magister | kernel did an oopsie | 13:36 |
| Mister_Magister | why now though? | 13:36 |
| Mister_Magister | So i'm looking into conttrack because thats where panic is from and there's comment "Mishearing the voices in his head, our hero wonders how he's supposed to kill the mall." | 13:46 |
| Mister_Magister | don't you just love easter eggs | 13:46 |
| sharks | When you manually run `sudo mic create fs`, the *.ks file you pass in from the ssu-kickstarts rpm is essentially the bash script that runs to do the work of creating the flashable image? If so, how come if I modify that file in order to try and debug this /dev/loop error, I don't see my modifications the next time I run the mic command? | 13:53 |
| Mister_Magister | mal: if i don't build your backports it doesn't segfault :( | 15:00 |
| rinigus | @b100dian: cp /apex/com.android.runtime/bin/linkerconfig /usr/libexec/droid-hybris/system/bin/linkerconfig helped me out. I have nagara booting again | 15:05 |
| rinigus | will fix dhd (as instructed above) and regenerate all packages. | 15:06 |
| rinigus | "all" hybris packages. I expect that this new linkerconfig would work better than older solution | 15:06 |
| mal | sharks: wait, how are you building the image? | 15:25 |
| T42 | <kbtpo> FLX1 | 16:23 |
| rinigus | mal: this https://github.com/mer-hybris/droid-hal-device/commit/9f96bd1473e3631d62eefb7fd2275f367d581ddd interferes with nagara suspend implementation. namely, we patch android suspend service for SFOS to use wakelocks | 18:06 |
| rinigus | patch is at https://github.com/sailfishos-sony-nagara/main/blob/main/patches/system/hardware/interfaces/0001-Add-kernel-wakelock-to-reflect-Android-wakelock-requ.patch | 18:06 |
| rinigus | and have our own android suspend service init. | 18:06 |
| rinigus | which is now in conflict with the one added by dhd. :( | 18:07 |
| rinigus | I guess I will make separate branch for nagara's dhd and we will be merging it with the main in future by pulling there new commits | 18:08 |
| rinigus | @b100dian: see above | 18:08 |
| mal | rinigus: why do you need to custom .rc if you can do it like this https://github.com/mer-hybris/hybris-patches/blob/hybris-22.2/system/hardware/interfaces/0001-hybris-Add-kernel-wakelock-to-reflect-Android-wakelo.patch and that dhd change? | 18:11 |
| mal | it seems 23.2 patch of that missing the last part, need to fix it | 18:11 |
| mal | also I could add the patch to 21.0 branch also | 18:11 |
| rinigus | mal: I need to call /usr/libexec/droid-hybris/system/bin/hw/android.system.suspend-service | 18:12 |
| rinigus | not from /system | 18:12 |
| mal | see the last part of the patch I linked | 18:12 |
| mal | or is the path wrong | 18:12 |
| T42 | <b100dian> rinigus: you were ahead of your time again?:) | 18:14 |
| rinigus | mal: NICE! | 18:17 |
| rinigus | let's add it to 21.0 as well | 18:18 |
| rinigus | @b100dian: no, I think it was figured out with nagara or in parallel :) | 18:19 |
| mal | we have similar in apexd.rc where we change the path | 18:20 |
| mal | hmm, why is that installed to system/etc/init/android.system.suspend-service.rc in my builds | 18:22 |
| mal | I'm confusing things a bit again | 18:25 |
| rinigus | OK, looks for now I just need to extend suspend patch by nicking it from hybris-patches los-23 branch. later it could be added to los-21 branch too. then we can use almost mer-hybris dhd | 18:30 |
| rinigus | @b100dian ^ | 18:30 |
| T42 | <b100dian> ringus: not sure I understand the conclusion. Is mal's patch replacing ours entirely and we can update dhd & add one more hybris-patch (other than the linkerconfig one) manuall? | 18:42 |
| T42 | <b100dian> *manually | 18:42 |
| T42 | <b100dian> or we keep dhd changes | 18:43 |
| rinigus | @b100dian: I have changed my patch for now as in https://github.com/sailfishos-sony-nagara/main/commit/840083798f8eb5df3d5fb0896d0fdf3f5b88968b | 18:47 |
| rinigus | this applies for our LOS version | 18:47 |
| rinigus | then I will drop our service file from config | 18:47 |
| rinigus | this will allow to use dhd from mer. | 18:48 |
| rinigus | @b100dian: I will probably finish whole test tomorrow and then can document it. wouldn't make it tonight with all rebuilds. so, just refrain from updating meanwhile your device from our OBS repos :) | 18:49 |
| rinigus | but seems like all is rather cleanly solvable... | 18:49 |
| T42 | <b100dian> I will make time to rebuild droid hal tomorrow, deal. With All the things^H^H patches. | 18:51 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!