Friday, 2022-04-15

T42<leha155> Los (re @SailfishFreenodeIRCBridgeBot: <Thaodan>Are you por...)04:44
T42<Bedjo> halo, is there anyone porting sailfish 4.X into Oneplus X device ? thanks07:22
riniguspiggz: I just fixed fpd-test GUI for 4.4 - we had to disable sailjail there as well12:54
rinigusas it is trivial change, it was committed directly and I tagged it accordingly as well12:55
T42<nephros> backtracing minimer gives me this (and lipstick looks the same). It this useful?
voidanix[m]do you have and somewhere on your system?14:12
T42<elros34> @nephros did stop lipstick before doing the test? check logcat15:39
deathmistmal: I just tested SMS as fully working afaik via ModemManager on 5.18 kernel MSM8998, previously I could only send but not receive, appears that situation has changed now :)16:07
maldeathmist: interesting, I still have the same issue that modem won't go online16:15
deathmistmal: have you made any upstream issues with verbose logs? someone especialy on libqmi front could have an idea what the problem is or know further troubleshooting steps16:29
T42<Amit34> Redmond note 4 ke little sailfish os  do16:40
maldeathmist: I think there is no issue reported anywhere for that17:16
maldeathmist: seems there is an issue about that not much help there17:56
voidanix[m]Thaodan: holy sh*t we got GUI on kumano+A1118:36
Thaodanvoidanix[m]:what made the difference?18:41
voidanix[m]overall selinux was broken, i have a todo list of things done18:45
voidanix[m]last thing done was setting up (`Unknown class service_manager`)18:45
T42<nephros> Definitely, it coredumps all the time! (re @elros34: @nephros did stop li...)18:59
Thaodan"last thing done was setting up (`Unknown class service_manager`)" Ignore the unknown class warnings. What is your do to list?19:03
voidanix[m] - things i've tried/done19:35
voidanix[m]that unknown class wouldn't let keymaster load though, that message came from strace-ing wait_for_keymaster19:35
ThaodanHm I stil wonder why it was needed. So keymaster appeared like it was loading but it didn't?19:40
voidanix[m]pretty much, yes19:48
T42<edp_17> Hi all! I need a little help. As usual, device boots but stucks on logo. After a minute or so, it reboots. The /system is not mounted.
T42<edp_17> I've set persistent journal and seen droid-hal-init has failed to start. Any suggestions?
T42<nephros> During that minute where it's up can you telnet to the device ( via USB/rndis)?21:23
T42<nephros> Did a correct system.mount unit get created when building hal?21:24
T42<edp_17> Yes, I can. That's how I set persistent journal and was able to collect logs that I posted.21:24
T42<edp_17> How can I check whether a correct system.mount unit get created when building hal?21:25
T42<Spidey24Z> cat /usr/lib/systemd/system/system.mount (re @edp_17: Hi all! I need a lit...)21:26
T42<Spidey24Z> also check if it linked to
T42<Spidey24Z> ls -la /etc/systemd/system/
T42<nephros> Oh, it doesn't find droid-hal-init at all.21:28
T42<edp_17> Yeh, but droid-hal-init is in /sbin:21:28
T42<edp_17> -rwxrwxr-x    1 root     root        521932 Apr 12 11:02 /sbin/droid-hal-init21:28
T42<edp_17> this is what 'ls -al /sbin/droid-hal-init' gives me on device.21:29
T42<edp_17> Interesting as I don't have '/usr/lib/systemd/system/system.mount':
T42<edp_17> These are I have in ''/usr/lib/systemd/system/':
T42<Spidey24Z> what's /system mmcblk number21:36
T42<elros34> it's normal that droid-hal-init (modified android init) fail without /system (android linker and whatsnot) mounted with: no suchh file or directory error21:40
T42<nephros> Thought so. It's the message a binary gives if it can't find its linker.21:43
T42<nephros> Miklos: inspect the phase when building the mount units, they are generated from Android /*init* files and fstab. There needs so be a correct mount for /system.21:46
T42<nephros> If you know the partition you van also mount it manually during the one minute window on the device.21:46
T42<edp_17> mmcblk0p16 (re @Spidey24Z: what's /system mmcbl...)21:46
T42<edp_17> I probably added the mount points wrong. This is what I used:
T42<edp_17> And this is what I collected from los17.1 on device:
T42<elros34> grep for fstab in, it's all explained what you need to do to have mount units generated21:49
T42<edp_17> @elros34 : I will do that. Thanks! :)21:50
T42<Spidey24Z> @edp_17 copy it to  /usr/lib/systemd/system and link to ln -s  /usr/lib/systemd/system/system.mount  /etc/systemd/system/ :
T42<Spidey24Z> @edp_17 copy it to  /usr/lib/systemd/system and link to ln -s  /usr/lib/systemd/system/system.mount  /etc/systemd/system/ :
T42<elros34> bad idea if all other partitions are also missing unless one wants to create all manually21:56
T42<b100dian> Hi, I've added yamui and yamuisplash (forked with correct res png) but the screen turns black from the sfos logo when booting. systemctl-user restart lipstick makes it turn on again.22:51
T42<b100dian> I've yet to find the error in journal, does this seem familiar to anyone?22:51
T42<b100dian> maybe it's this? lipstick[6385]: [W] unknown:0 - EGLFS: Failed to open /dev/fb022:53
T42<elros34> is yamui stoped before lipstick starts? Maybe you need something like that:
T42<b100dian> yes, yamui is stopped before lipstick. I should definitely try that, thanks!23:00
T42<b100dian> well glad I asked. This was definitely something I would have [reverted/struggled with]. Thank you @elros3423:08
T42<b100dian> so the problem is that I have >5s time to lipstick? hmm maybe I have systemd-analyze to do:)23:18
T42<b100dian> Mine's on the forty-five23:30

Generated by 2.17.1 by Marius Gedminas - find it at!