Thursday, 2020-11-05

T42<Zero %lastname%> (Photo, 734x572) 币圈电报微信群炸群、电报群指定群私聊、Twitter/Facebook点赞加粉等,需要的咨询       @he20150103:11
T42Ines Etter %lastname% was added by: Ines Etter %lastname%08:25
szopinwould anyone know what changes need to be made in gitlab CI from 3.2.1 to 3.4 to get a working image? (specifically for cosmocom-ci, as just changing @RELEASE@ results in a non-working image, would newer docker image be needed? it's using coderus'
szopinI'm guessing 'user --name nemo --groups audio,input,video --password nemo' in .ks file needs changing to 'defaultuser'?09:17
T42<elros34> iirc this line was removed at some point. Compare ks with some more up to date device09:25
szopinlatest is enchilada but it only has 3.309:27
szopinoh wait... that's created date09:28
szopinnope... last update is vince-ci but also on 3.309:29
szopindoesn't seem to be any ci setup for 3.4 build09:29
szopinsadly the cosmo port doesn't update to either 3.3 or 3.4, ends up rebooting around 70% and no longer boots09:30
T42<elros34> yeah we don't have 3.4.0.x on obs so probbable many are still at 3.3.0.x. For sure you need to remove replace first su -c "/usr/bin/oneshot --mic" with /usr/bin/oneshot --mic09:31
T42<elros34> ah but did anybody update adaptation repos?09:31
kalubewhat's the status with OBS? I got put off building 3.4 when they announced they were killing it09:40
szopinelros34: thx, will try with that change09:48
szopinor does the above mean trying to build 3.4 right away will not work and 3.3 is where it's at?09:57
szopinoh one more thing, as all sensors seem dead on the 3.2.1 image no gyro/accel etc, all giving 0s in csd, is that something that can be troubleshot from within the port or does it need rebuilding the community-adaptation packages?10:06
szopin(I was trying to follow hadk guide, but there is no android base for cosmo available, only kernel, so got stuck pretty early on on local manifests and repo setup, though most of it seems taken care of by NotKit)10:08
szopin(even then, the guide says it should work out of the box :/)10:08
szopin89btw who is working on Volla Phone port? NotKit said it has very similar SoC, so could maybe reuse its android base to get the proper setup for things outside of the CI10:19
T42<edp_17> szopin: To make sensors working on 3.4 I have to downgrade sensorfw to
szopinIt was not working on 3.2.1... the initial NotKit release, about to try the 3.4 artifact with the su -c removed, will try to downgrade if it boots10:29
T42<elros34> I am afraid you need to upgrade adaptation repos to get it fully working with 3.4.0 otherwise some thinks might not work even if it boots like camera, videoplayback. Removing "su -c" is required to avoid some issues but will not help for not booting image. You would need to telnet to device and grab journalctl to see what fails10:32
szopincan I grab journalctl from gemian?10:32
szopinyeah must be... everything is in /.stowaways/sfos/ (except everything that's written to /data as it's also gemian rootfs)10:34
T42<elros34> I guess if you chroot to sailfish then it should be possible. But first you would need to enable persistent logging in sfos
szopinok, will update that before the boot then10:35
szopinalright, here goes nothing10:37
*** szopin89 is now known as szopin10:37
szopinat least keyboard in gemian still works :)10:39
szopinhmm... var/log/journal is empty10:40
szopinnope... it's there10:41
szopinwrong dir10:41
szopin4 .journal files, but some binary format...10:43
T42<elros34> yes you need to use journalctl to read them10:43
szopinok... I can just chroot into /.stowaways, great stuff10:44
szopin100probably related to not working sensors: Nov 05 10:38:06 localhost kernel:  (6)[1:swapper/0]i2c i2c-1: of_i2c: modalias failure on /i2c@11011000/gsensor@6aNov 05 10:38:06 localhost kernel:  (6)[1:swapper/0]i2c i2c-1: of_i2c: modalias failure on /i2c@11011000/gyro@6911:01
szopin100I think this is where it fails: ov 05 10:38:08 localhost (5)[1072:droid-hal-init]droid-hal-init: /init.rc: 1: Could not import file 'vendor.mediatek.hardware.power@2.0-init.rc': No such file or directoryNov 05 10:38:08 localhost (5)[1072:droid-hal-init]droid-hal-init: Parsing file /vendor/etc/init/vendor.mediatek.hardware.pq@2.2-service.rc...Nov 0511:17
szopin10010:38:08 localhost (5)[1072:droid-hal-init]droid-hal-init: Parsing file /vendor/etc/init/vndservicemanager.rc...Nov 05 10:38:08 localhost systemd[1]: dsme.service: Unit entered failed state.11:17
malshow full log11:22
szopin100where best to upload it?11:22
szopin100too big for pastebin, but this works
malso are sensors the only issue or something else also?11:40
szopin100sensors and BT, but with the 3.4 it's just not booting11:40
malalso get output of journalctl -b --no-pager11:41
szopin100updating from terminal also results in unbootable state whether to 3.3 or 3.4, and same with artifact from gitlab11:41
szopin100one sec11:41
szopin100Failed to get boot id: No such file or directory(I'm chrooting into /.stowaways/sfos as no recovery/telnet option on cosmo)11:43
T42<elros34> just for future use journalctl -b-1  to get logs only from previous boot not all11:43
malgood point11:43
szopin100this is -b-1:
szopin100and --no-pager from last boot
szopin100seems identical11:48
szopin100I guess > file does the nopager11:48
T42<elros34> systemd-* and dsme fails with: "Failed at step NETWORK spawning". THis si probably the first issue to solve11:49
riniguskalube: I saw by accident last night 3.4... target at OBS. cannot comment on whether it is ready or not. maybe someone from Jolla can provide bg11:55
kaluberinigus: cheers, hopefully I can get proper A/B support in sailfish and make some headway :D11:56
T42<elros34> @szopin100: what "zcat /proc/config.gz | grep CONFIG_NET_NS" shows?12:02
malwhich device and kernel is that?12:03
malah, 4.4 kernel12:03
szopin100no such file or directory12:04
szopin100on gemian it's set to y12:05
T42<elros34> you need to telnet to device get it from there or read it from defconfig from kernel sources if they are up to date12:06
szopincan't telnet to it as it has no recovery mode12:06
szopinor at least unaware how to access it12:06
szopintried volume up/down on booting into sfos but got nowhere12:07
szopincould try restoring the working 3.2.1 should populate /proc then12:07
T42<elros34> you don't need recovery or any buttons for telnet, when it's booting you should see in dmesg  that usb interface is setup, then "telnet 2323"12:07
malwhat kind of build is that?12:08
szopinno idea, I need to boot into gemian to setup directory /.stowaways/sailfishos/ with all the rootfs of sfos, then boot from a different partition into it12:09
szopinmaybe there is some way to trigger recovery menu, haven't found it yet12:09
szopinyeah... would need to dd the hybris-recovery img12:10
T42<elros34> like I said you don't need recovery /init-debug script in sfos rootfs setup telnet for you when you boot regular sailfish.12:10
szopinI don't think there is one in the artifacts from CI12:10
szopinit reboots in seconds when booting 3.412:11
szopincan try to get it from the wroking 3.2.112:11
T42<elros34> ok so for now maybe try as a workaround to remove PrivateNetwork=true from all services which fails with "Failed at step NETWORK spawning" to see if that helps12:12
T42<elros34> I have check and it has /init-debug like it should12:14
szopin# it or set to false?12:15
T42<elros34> probably it doesn't matter12:15
szopinwifi connects but no connectivity, but build shows
szopinmaybe will change them one at a time12:22
szopinhmmm orientation is also locked, components app doesn't seem to change it12:23
malis sensorfw running?12:27
szopinhmm two of the PrivateNetwork settings resetted themselves back to true, leaving dsme.service with it commented for now12:36
szopinI think I broke the Page.qml when trying to change it landscape inverted :/12:37
szopinthat was weird, display was just a line, then it seemed like a bootloop as got chinese 'Goodbye(or welcome?)' black screen and only vibra when pressing power key... but it's all fine lol12:39
szopinweird, the Page.qml seems fine, maybe it's the second boot issue12:42
szopincouldn't save developer password in settings with all the PrivateNetwork commented out12:43
malfirst thing to fix is that dsme12:43
szopinyeah, with it commented out and Orentation.All back in getting the tutorial again12:43
szopinthis time developer password got saved and sensorfwd is running12:46
szopinfixing landscape from within worked, network still not working12:51
szopin(connects to wifi but nothing opens in either browser or setting up account)12:51
szopinshould I try to edit the PrivateNetwork back in and restart dsme?12:54
szopinthat causes a restart13:02
spiiroinszopin: does the dsme process start at all? or does it fail already when systemd is settings up things?13:05
szopinhard to tell, tried systemctl after uncommenting the PrivateNetwork bit, it told me to daemon-reload(?)... 10-15 seconds later it showed lockscreen and then blackscreen/reboot13:06
szopincan try to have top open in another window and see13:07
szopinsystemctl restart dsme*13:07
spiiroinszopin: until things stablize, you might want comment out "StartLimitAction=reboot" from dsme.service13:11
szopinOk, with that commented it just goes into blackscreen and need to power off13:15
spiirointop is probably not that useful if the process dies immediately/is not started at all..13:17
szopinseen only dsme-server process running13:17
spiirointhere ought to be two: dsme-wdd and dsme-server. former is watchdog kicking parent process, and latter the outwards visible actual service13:19
spiiroinabout the first thing that should happen on dsme startup: parent writes that "DSME 0.81.4 starting up" to stderr. journald should get it, but that was not in that paste13:20
szopinI can access now the journal from within 3.4, one sec13:21
szopinStarting DSME/Failed to start/Stopped/Failed to start/Stopped/Starting DSME/Failed/Stopped/Starting/Failed in this order (grep on DSME)13:24
szopinIf you want full logs will be easier to get from gemian as fingerterm is sideways and select/copy will be a pain if not impossible13:25
szopinLet me pull the full log13:26
spiiroinszopin: I think all of those are progress reports logged from systemd.. so nothing from dsme process itself?13:26
szopinin journal no, there was no DMSE 0.8...13:26
spiiroinbut but but... there were other units that were failing with that PrivateNetwork? was there some unit that has it and works? i.e. might this be some sort of systemd vs kernel version issue or stte?13:27
szopinthere is 5 or six .service files with PrivateNetwork, 2 or 3 of them reset themselves to uncommented after booting into sfos, commenting dsme.service is enough to boot in without reboot, let me check that log again13:29
spiiroinreset to uncommented? as in, your manual edits disappear on reboot?13:35
* spiiroin wonders if fs sync happens ...13:35
szopinyes, for bluebinder and that obexdservice I think, the # before PrivateNetwork was gone13:36
szopineven though originally I commented them all out13:36
T42<elros34> @szopin so if it doesn't reboot now then check that /proc/config.gz13:43
szopinno such setting13:45
T42<elros34> no CONFIG_NET_NS=y? then this needs to be enabled in defconfig13:47
szopinhmm... that's not something I can do on device?13:47
T42<elros34> no, you need to build kernel13:48
szopinis this needed on 3.4? can check if the 3.2.1 has it, but don't think the CI rebuilds the kernel13:49
T42<elros34> not sure as I have it enabled for a long time13:50
szopinwould this be the android kernel or the cosmo-linux kernel? is it built on obs with the community-adaptation part?13:50
T42<elros34> ci only create image, it doesn't build anything13:51
szopinwill have to reach out to NotKit to see if he has that setup for sfos still to just add one option13:51
T42<elros34> usually we build kernel in pc then package it and upload rpm to obs13:52
szopinbtw what options are needed for flatpaks? if notkit agrees to rebuild it would be good to include those to for angelfish14:04
szopinonly PR_SET_NO_NEW_PRIVS/14:06
szopinok kernel is in droid-hal and there is also droid-hal-cosmocom-img-recovery-0.0.6-202002102318.armv7hl.rpm I guess this would be needed for recovery mode?14:11
szopinI need to get that whole setup myself, but NotKit supposedly used some private planet mediatek BSP, the HAL guide supports only lineageOS now, but halfway through goes to CyanogenMod as it's on nexus14:14
szopinand there is neither lineage nor Cm for cosmo (maybe pure AOSP Pie will work?)14:14
T42<Simon %lastname%> Does anybody know where I can find xulrunner-qt5-dev? I'm trying to compile qtmozembed but it doesn't have this dependency14:25
szopinpiggz: are you using public android base for yggdrasil or some private mediatek bsp like cosmo? Volla is using the same Helio p23 so ws wondering if maybe the same base would work to setup hadk properly?14:27
szopinwouldn't have to bother NotKit all the time as it seems BT also needs another defconfig change :/14:28
T42<NotKit> I have public tree based on yggdrasil. Need some time to clean up and upload14:29
szopinOh wow you're here too?14:29
szopinI guess T42 is telegram bridge?14:30
T42<NotKit> yes14:30
ThaodanT42 because 42 is the answer to everything14:32
szopinfrom the HADK daq CONFIG_BT_HCIVHCI=y is supposedly needed for BT on 8.1, though cosmo is 9 so not sure14:32
szopinI guess IRC is old fashioned and telegram has all the answers now14:33
szopinwait for discourse bridge14:33
Thaodandiscord? For discord there is bitlbee discord. I just needed a name for the telegram bridge and thught 42 would fit.14:34
szopin6cord too14:35
szopinI think the only client on sfos14:35
szopinThaodan: there should be one XMPP like bridge that covers telegram, matrix, discord, qq and AOL and whatsapp14:37
szopininstead of one protocol covers all, one bridge to rule them all14:38
ThaodanThere is you can use xmpp transports for that14:38
Thaodanbitlbee is like that just for IRC14:38
szopincosmo guys are fighting with matrix bridge alone for the last 72hrs and it's not looking good14:38
szopin(that's telegram <-> matrix, two newish and popular and supported frameworks, add all that legacy support to that)14:40
samsep10lhello people. i am not sure if i can get answer here. but do anyone know what to do with this?14:46
samsep10lhalium/out/soong/host/linux-x86/bin/d8', needed by 'halium/out/soong/.intermediates/frameworks/base/packages/EasterEgg/EasterEgg/android_common/dex/EasterEgg.jar'14:47
samsep10li looked at halium page, but it didn't give me solution14:48
szopinnot sure if halium is used in any sfos distro, ubports uses it afaik14:50
samsep10li tried before, failed. might be a bug.14:52
szopinI mean there are people here who port all kinds of stuff, so not a bad place to ask, just that sfos doesn't use halium14:54
szopin(then again ubports documentation is supposedly non-existant, so might as well get better answers elsewhere)14:55
szopintry /join #halium 364 people there, here out of a 100 only a percentage will have experience15:02
szopinthat 364 is weird though as they don't have a bridge, but instead NickTelegram, so could be doubles15:02
szopinyeah the bridging solutions seem to be non-standardised15:03
riniguskalube: what do you expect from A/B support? for me it mainly looks as an option to expand LVM into those "unused" volumes16:26
rinigusjolla devs: any update on OBS 3.4. target?16:26
kaluberinigus currently you have to hard code partitions, meaning in order to dual boot with android you are forced to install sailfish on a particular slot which is kinda a pain. ubports and postmarketos can both be installed to either slot making it way easier to dual boot16:29
pketorinigus: sorry, no other news about 3.4 target than it was tried but there was weird issues, and then other stuff came up and nobody has had time yet to look at it again16:37
riniguspketo: thank you very much for update! and there is nothing to be sorry about - it is all understandable.16:38
riniguskalube: I see. haven't considered dual boot myself.16:39
T42<elros34> kalube so do not hardcode partitions. Amend mount units before systemd start. I use such a hack in init script to support 2 similar devices with different system partition number16:42
kalube@elros seems to be the right approach16:50
szopinpketo: does it mean trying to build 3.4 images is doomed to fail?17:01
szopinas in: there no ported device that starts as 3.4 and you can only get there through OTA17:04
szopindon't want to waste NotKit's time if that's so17:04
malbuilding 3.4.0 is possible locally, just OBS is the problem18:16
T42<Simon %lastname%> Where can I find "nemo-test-tools"?20:34
malwhere do you need those? not even sure what those are20:34
T42<Simon %lastname%> it's a dependency of qtmozembed-tests21:24
T42<Simon %lastname%> I thought maybe one of those tests helps narrowing down why the browser stays white on pinephone21:25
malprobably now21:27
mal*probably not21:28
malwe know roughly where the issue is happening but not why21:28
T42<Simon %lastname%> is that documented anywhere accessible?21:31
T42<Simon %lastname%> or how can I help debugging this? It's the last big missing piece as far as I can see21:33
maljust some discussion I had with piggz about the issue some time ago21:37
ThaodanYou can use the channel logs to search for that21:38
malI think it was in a private chat21:39
malmaybe I should try to find the links from my own irc logs21:40
T42<Simon %lastname%> this might not be the most appropriate place but I put an issue here some while ago:
ThaodanPlease set a user name and attach some logs to the issue21:46
T42<Simon %lastname%> How do I set a user name?21:50
ThaodanJust search for telegram username22:06
T42<simonschmeisser> thanks, done, I also added some minimal logs to the issue but I can add more if you guide me22:14
ThaodanI'm not sure what the problem is but you can look in to the documenation of the package for more debug output22:51
malthe issue is not very simple23:01
Thaodanhm ok23:23
ThaodanIs it related to not having gmp-droid?23:24
malgmp-droid is optional but nice to have23:33

Generated by 2.17.1 by Marius Gedminas - find it at!