Friday, 2026-07-17

T42<Mister_Magister> Failed to access management interface00:35
Mister_Magisterwas meant to search that oops00:35
*** n2klb_ is now known as n2klb01: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 build06:33
rinigusin logs - linkerconfig: executing /usr/libexec/droid-hybris/system/bin/linkerconfig failed: No such file or directory06:33
rinigusyou don't seem to have this patch applied06:33
T42<b100dian> No, I dont have it07: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
riniguswas rather simple to find and confirm by comparing manifest snapshots :). hopefully, will fix my boot too07:52
riniguswill see tonight07:52
T42<b100dian> Hmm so it paches an executable that it is not packaged, in droid hal?07:53
T42<b100dian> Or something didnt build07:53
T42<b100dian> What if you copy on devixe your system linkerconfig there?:D07:53
rinigus@b100dian: looks like it. we probably have to build it separately, as we do with i18n07:55
rinigus@b100dian: copy would be simplest way to get it booting and later update from full sfos. will test when back home07:55
sharksCan 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
rinigussharks: look into droid-hal config of nagara. you need to "build" it - use similar approach as used there08:06
rinigussharks: add build.script to it08:07
sharksOhh - I am indeed missing build.script. Thankyou!08:08
sharksHmm, 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
rinigussharks: this one too - https://build.sailfishos.org/package/view_file/nemo:devel:hw:sony:nagara/droid-hal-nagara/droid-hal.spec08:17
sharksOh 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
sharksOkay, 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
sharksRPM build errors:09:27
sharks    Could not canonicalize hostname: phost1809:27
sharks    Bad exit status from /var/tmp/rpm-tmp.WMIfot (%build)09:27
sharksphost18 failed "build droid-hal-pdx225-img-boot.spec" at Fri Jul 17 09:25:13 UTC 2026.09:27
rinigussharks: error is a bit above it - /usr/bin/env: 'python3'09:30
riniguslooks like python dependency is missing in spec09:30
sharksHmm, 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
sharksNot sure why that would be the case, but thanks anyway rinigus - I'll work around it...09:34
sharksPerhaps 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:murray10:15
sharksI'm completely stumped as to how to fix that, I can't see at all how it's supposed to be configured.10:48
rinigussharks: 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 you10:53
riniguswill be able to define urls based on whether you build devel (for you) or testing (for users) version10:53
sharksrinigus - 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
rinigussharks: 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 ports11:06
sharksRight, 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
sharksOh - it looks like I can make my own subprojects. Cool! Thanks again rinigus, you're a handy bloke to have around.11:10
rinigusgood luck!11:10
sharksThanks, I might need it :)11:11
malMister_Magister: you might find a commit for CMAC in fp2 kernel, branch hybris-21.08.1-rel, check also other thing next to it12:22
malrinigus: which android base was that?12:23
malthe linkerconfig issue12:23
rinigusmal: its lineage21/android1412:26
malrinigus: which droid-hal-device submodule revision?12:27
riniguslet me check12:27
malrinigus: which location do you have linkerconfig in out/12:29
Mister_Magistermal: is cmac ABSOLUTELY needed?12:29
malnot sure12:29
Mister_Magisterwant to spend some fun friday afternoon with me trying to figure out why am i getting "Failed to access management interface"? I built the backports12:29
rinigusmal: in one of the apex ones, runtime12:30
malok then it should get copied if you have correct submodule version12:31
maldid it get copied to droid-hal rpm?12:31
malor maybe you have symlink issue12:31
rinigusmal: we have our own dhd as this one is still pending https://github.com/mer-hybris/droid-hal-device/pull/34512:31
riniguswhich means I have relatively old dhd base and this is not there - https://github.com/mer-hybris/droid-hal-device/commit/21cc677be30b4adb152843d51265ae4bb0641a3912:32
riniguswill rebase, thanks!12:32
malrinigus: don't rebase to latest12:33
malfor now rebase on top of be67bbcdcfb9f1e392dbac699928fa29c5c103cd12:33
rinigusthank you very much! (was going to  check in release notes and see which one to use)12:33
malthinking if I should revert that last change until I fix it properly12:34
Mister_Magisterso mal, if you could, any ideas about fm radio and/or bluetooth? :P12:42
malI htink management inteface tries to suggest it's using new enough driver, you are sure backports are in use?12:44
Mister_MagisterI'm not12:45
Mister_Magisterhow do i verify12:45
malyou built it after building kernel?12:45
Mister_Magisteryes12:45
Mister_Magisterin backlog you said that managment interface error is when you didn't build backports but are using bluez512:45
maland kernel has bt stuff as modules?12:45
Mister_Magisteryes12:45
Mister_Magisteryeah i'm as stumped as you are xd12:47
Mister_Magisterthe only difference is lack of CMAC but that doesn't seem like it would invoke this issue12:48
Mister_Magisterhttps://paste.opensuse.org/pastes/ba469c6e39c0 modules loaded12:50
Mister_Magisterhttps://paste.opensuse.org/pastes/878424f90032 here's me building kernel then backports12:50
Mister_Magisterthe backports are tiny bit outdated but nothing important12:51
Mister_Magisterliterally just my commit which shut up warnings lol12:51
Mister_Magistercompat module is not loaded idk if thats needed but loading it doesn't help either12:53
Mister_Magisteroh, I added CMAC to the old kernel12:56
Mister_Magisterwell then maybe it's needed12:56
malthere is the commit about hid backport also if you want to support that13:01
Mister_Magistermal: with CMAC the backports asked me to regenerate config and this time ti touched hci_smd13:03
Mister_Magisterso i think CMAC was needed13:03
Mister_Magistermal: hid backport? what's that for?13:03
Mister_Magisteryeah and this time backports also touched bt module so i think that was it13:04
malbluetooth hid, so keyboards etc13:05
Mister_Magisteroh, that doesn't work?13:05
malfp2 kernel has "hid: Backport hid-generic driver"13:06
sharksSorry to interrupt, quick question - What is out-of-image-files.files for?13:06
Mister_Magisteroki will look into it13:06
Mister_Magisterbut first i want to get bt working13:06
malsharks: that lists what files will kept out side the installation zip13:07
sharksThanks mal, in other words it's not mission critical13:07
Mister_Magistergreat, now it's just bootlooping13:11
sharksI'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-hot13:11
sharksInfo[07/17 13:03:45] : Running pack scripts ...13:11
sharks$ANDROID_ROOT/sfe-xqcc72-5.1.0.11devel1 $ANDROID_ROOT13:11
sharksResize root and home13:11
sharkslosetup: /dev/loop0: failed to set up loop device: No such file or directory13:11
sharksInfo[07/17 13:03:45] : Script returned with non zero status, failing.13:11
sharksError <creator>[07/17 13:03:46] : Failed to execute %pack script with /bin/bash13:11
sharksSeems 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 *.zip13:12
sharkshttps://paste.opensuse.org/pastes/112e3a16e93a13:14
Mister_Magisterhmm now it's just bootlooping without even booting :/13:24
Mister_Magisterdang it13:34
Mister_Magistergot it to booting again but it just bootloops13:34
Mister_Magister[   54.318445,0] kernel BUG at /home/foidbgen/hadk-titan/kernel/motorola/msm8226/fs/sysfs/dir.c:534!13:35
Mister_Magisterkernel did an oopsie13:36
Mister_Magisterwhy now though?13:36
Mister_MagisterSo 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_Magisterdon't you just love easter eggs13:46
sharksWhen 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_Magistermal: 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 again15:05
riniguswill 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 solution15:06
malsharks: wait, how are you building the image?15:25
T42<kbtpo> FLX116:23
rinigusmal: 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 wakelocks18:06
riniguspatch is at https://github.com/sailfishos-sony-nagara/main/blob/main/patches/system/hardware/interfaces/0001-Add-kernel-wakelock-to-reflect-Android-wakelock-requ.patch18:06
rinigusand have our own android suspend service init.18:06
riniguswhich is now in conflict with the one added by dhd. :(18:07
rinigusI 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 commits18:08
rinigus@b100dian: see above18:08
malrinigus: 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
malit seems 23.2 patch of that missing the last part, need to fix it18:11
malalso I could add the patch to 21.0 branch also18:11
rinigusmal: I need to call /usr/libexec/droid-hybris/system/bin/hw/android.system.suspend-service18:12
rinigusnot from /system18:12
malsee the last part of the patch I linked18:12
malor is the path wrong18:12
T42<b100dian> rinigus: you were ahead of your time again?:)18:14
rinigusmal: NICE!18:17
riniguslet's add it to 21.0 as well18:18
rinigus@b100dian: no, I think it was figured out with nagara or in parallel :)18:19
malwe have similar in apexd.rc where we change the path18:20
malhmm, why is that installed to system/etc/init/android.system.suspend-service.rc in my builds18:22
malI'm confusing things a bit again18:25
rinigusOK, 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 dhd18: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> *manually18:42
T42<b100dian> or we keep dhd changes18:43
rinigus@b100dian: I have changed my patch for now as in https://github.com/sailfishos-sony-nagara/main/commit/840083798f8eb5df3d5fb0896d0fdf3f5b88968b18:47
rinigusthis applies for our LOS version18:47
rinigusthen I will drop our service file from config18:47
rinigusthis 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
rinigusbut 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/!