Saturday, 2021-12-11

T42<AntonlX> I am getting this "libminisf is incompatible or missing" error while starting UI. Can this mer instruction work for 18.1 port? (re @elros34: what about this: htt...)00:04
T42<elros34> unlikely00:07
T42<elros34> what errors you have in logcat?00:10
T42<AntonlX> logcat not working (re @elros34: what errors you have...)00:12
T42<elros34> then forget about ui errors, you need logcat working (droid-hal-init) first00:13
T42<AntonlX> logcat calls logcat in terminal?00:14
T42<elros34> no, /usr/libexec/droid-hybris/system/bin/logcat.  For future 'command not found' != 'logcat is not working'00:17
T42<AntonlX> nohup: can't execute '/sbin/droid-hal-init': No such file or directory (re @elros34: no, /usr/libexec/dro...)00:24
T42<AntonlX> After that failed to start droid-hal-init00:25
T42<elros34> so now you can say logcat is not working :) show whole journalctl --no-page00:25
T42<AntonlX> (re @elros34: so now you can say l...)00:27
T42<elros34> maybe your dynamic partitions are not mounted correctly? check with 'df' and 'ls /path/to/dynamic partitions mount points/'00:32
T42<elros34> with auto created mount units it's clear whether they are mounted or not but looks like you do not any debug messages so I can only guess00:34
T42<AntonlX> I've mount system_root to /system_root and mount —bind /system_root/system to /system00:38
T42<AntonlX> Everything right here
T42<elros34> this only output of what: /system_root? How do you handle /vendor/dsp and similar? Better show whole droid-config/hal repo and output of findmnt.00:47
T42<elros34> ah it's ls /, pleae include command prompt00:49
T42<AntonlX> Findmnt out (re @elros34: this only output of ...)00:51
T42<elros34> you can see that /system is missing00:52
T42<AntonlX> Super.img have 4 partitions - system_root, vendor, product, system_ext00:53
T42<AntonlX> system files located in system_root/system00:54
T42<elros34> look again at findmnt, your /system and /system_root is not mounted00:54
T42<elros34> vendor is probably also handled in wrong order00:59
T42<AntonlX> Now mounted, I forget to mount them. findmnt: (re @elros34: look again at findmn...)01:01
T42<AntonlX> But /sbin/droid-hal-init out with the same error01:01
T42<AntonlX> when i am executing /sbin/droid-hal-init phone rebooting and manually created mountpoints off (re @AntonlX: But /sbin/droid-hal-...)01:03
T42<elros34> but how do you start it? Do you mount partitions first, mask service or what? Statement about wrong vendor mount order is still valid01:04
T42<AntonlX> I've delete systemd super partitions .mount files and mounting them through and tool you shared before. (re @elros34: but how do you start...)01:07
T42<elros34> according to your logs: first  /vendor/*  are mounted by systemd then /vendor itself by your script, you need to fix it. Again how do you manaully start droid-hal-init? Do you mask it first or just start second time which is wrong?01:10
T42<AntonlX> If i simply trying to mount system_root to /system it outs Too many levels of symbolic links01:11
T42<AntonlX> But I've deleted systemd's vendor.mount (re @elros34: according to your lo...)01:13
T42<elros34> so how about you finally show me that script so I can see what you are doing? By /vendor/* I mean /vendor/dsp /vendor/mnt_fimware and so on01:15
T42<AntonlX> This is my script: (re @elros34: so how about you fin...)01:20
T42<AntonlX> System_root I am mounting manualy because theese commands at script cause bootloop01:21
T42<elros34> So 3th time I ask: Do you mask droid-hal-init, stop in init-script or how do you ensure /system is correct when droid-hal-init is started. I also wonder about /system/system_ext, is that symlink or maybe you need to bind mount it?01:23
T42<elros34> move all /vendor/* to that script also01:24
T42<AntonlX> I didn't mask droid-hal-init. It fails and I am restarting in with /sbin/droid-hal-init (re @elros34: So 3th time I ask: D...)01:27
T42<elros34> you can't, it can be only started once per boot so mask it, also user@100000.service, reboot, mount everything and then start droid-hal-init. If it fail same way, reboot repeat and strace -f droid-hal-init01:28
T42<rodsol90> .08:37
T42<Salvadorsr> Is posible sfos on f2fs filesystem08:38
T42<AntonlX> strace -f droid-hal-init output:
malwhich android base?12:36
T42<AntonlX> @mal yes (re @SailfishFreenodeIRCBridgeBot: <mal>18.1?)12:53
malthen that is the same issue I had, I have a fix for it locally but there is another issue I haven't yet fixed13:05
T42<adampigg> i always wondered that .. i wonder what makes a process special that it can only be started once (re @elros34: you can't, it can be...)13:31
mal@AntonlX this patch to system/core might or might not help in your situation
poetasteranyone look at porting for: ( fairphone style outta germany) That model ist still Android 814:16
piggzmal: so, according to that patch ... hybris changes are getting less?15:05
T42<AntonlX> @mal what I need to rebuild after this patches? (re @SailfishFreenodeIRCBridgeBot: <mal>@AntonlX this p...)15:12
T42<AntonlX> I need to fully recompile hybris-hal?15:21
T42<elros34> @adampigg I can only guess but I bet droid-hal-init can but started once comes from mal long time ago:) Frankly I am not sure this is still valid15:28
krnlyngit's still valid in the sense that there might be things that can't be initialized twice and cause confusion for driver blobs or outright fail or crash the device15:29
krnlyngbut you can start it multiple times if the previous attempts didn't do something that will cause problems15:30
krnlyngyou might need to delete /dev/__properties__ and files like that in order to avoid it from crashing immediately however15:31
T42<elros34> ^good to know. @AntonlX is this full log? I do not see place where it starts. Did you fix your mount points? What about /system/system_ext I asked, is it empty directory or symlink?15:38
mal@AntonlX hybris-hal needs to be rebuilt, but it should not take long since it will only build the changed parts15:44
T42<AntonlX> This is full log from start to end. I have to add pasrse-android-dynparts created mountpoints to fixup-mountpoints file? I mount system_root to /system_root, system_ext to /system_ext and mount —bind /system_ext /system_root/system_ext (re @elros34: ^good to know. @Anto...)15:47
T42<elros34> no do not add anything to fixup-mountpoints. Either create mount units for dynamic partitions manually and put them in droid-config  sparse (you will have to run parse-android-dynparts in some systemd service started before everything is mounted) or handle it just like you do in script15:52
T42<diablo765> question, fix cadi all the warnings, rebuilt the fixmountpoint, install the hybris-installer (of course I adapt it to my device), but when I install it in the first place it does not recognize me in f2fs, if not in ext4, lineage does not turn on in ext4 , another problem is that when I install the package, I get no system in twrp, and when it turns on it goes to fastboot mode17:12
T42<rodrisola> .19:45
T42<rodrisola> Is posible sailfish os on f2fs partition?21:35
malwhy can't you format the partition to ext4?21:36
T42<elros34> does it really matter whether it's ext4 or f2fs? After all init-script just use mount /dev/<data partition> /data21:49
malnot sure if anyone has tried to use f2fs21:58
Mister_Magistersomeone hasn't?22:00
Mister_Magisterisn't f2fs like default?22:00
Mister_Magisteri've been using f2fs on my g2 for like 6 years now22:01
ThaodanIt doesn't matter which fs as long as the kernel supports it22:01
Mister_Magisterbut don't do fat32 xd22:01
Thaodanfor rootfs you should just include the fsck of the rootfs in the initramfs22:01
Thaodanso you can repair the fs in case its needed22:02
ThaodanMister_Magister: Unless your into pain xD22:02
T42<adampigg> Is amiga fast filesystem ok? (re @SailfishFreenodeIRCBridgeBot: <Mister_Magister>but...)23:11
Mister_Magisterdoes it support permissions?23:12
Mister_Magisterand ownership23:12

Generated by 2.17.1 by Marius Gedminas - find it at!