Friday, 2023-07-07

T42<smatkovi> is the content of this system_root.mount right
T42<smatkovi> i don't know how to mount it in / and not in /system, i've checked in my known places and it says / there and not /system14:51
T42<smatkovi> can i somehow remount it in /, even if it is already mounted in /system?14:52
T42<smatkovi> that is also strange: / # cd system/bin15:00
T42<smatkovi> /bin/sh: cd: can't cd to system/bin: Too many levels of symbolic links15:00
T42<smatkovi> maybe the system.mount is wrong?
T42<smatkovi> i could maybe package the system partition, but i don't know how16:08
T42<elros34> I told you step by step what files to check, did you check all of them and last one in : droid-hal-device*rpm?16:11
T42<smatkovi> I  will say yes. But it wouldn't be the first time i thought i did something and then i didn't, so i will go through them again. So just to make sure i get everything, i should check the init.rc files for rootfs mounted in / instead of /system and then in the system_root.mount in the rpm if rootfs is mounted system_root?18:40
T42<elros34> start with the latest: so system_root.mount in the rpm should NOT have this 'mount rootfs rootfs.18:43
T42<elros34> If it has then go to init.rc files checking.18:43
T42<smatkovi> now it's not even in the rpm19:01
T42<smatkovi> maybe because i added %define makefstab_skip_entries / /system /vendor19:02
T42<smatkovi> to
T42<elros34> ... yeah19:02
T42<elros34> btw you shouldn't edit droid-hal-device.inc19:02
T42<smatkovi> that's what i understood from the hadk-hot19:03
T42<elros34> you always add something to droid-hal-device.spec, *.inc file is in submodule19:04
T42<smatkovi> here it says inc: - To prevent droid-hal creating incorrect systemd mount units add all dynamic partitions to makefstab_skip_entires similar to:
T42<smatkovi> maybe that should be updated then19:06
T42<smatkovi> oh it says common19:07
T42<elros34> it's no the best example but this is not droid-hal-device.inc19:07
T42<smatkovi> as i didn't have common i used device19:07
T42<smatkovi> so one could just create with that line?19:07
T42<smatkovi> in that directory?19:07
T42<elros34> you should not worry about it at all, remove what you added and move on with your simple issue to real porting19:08
T42<smatkovi> where is19:08
T42<smatkovi> ok thanks :)19:08
T42<smatkovi> that's very interesting, the system.mount and system_root.mount files look completely different and more right now19:12
T42<smatkovi> this is what the mount section for system_root.mount looks like: What=/dev/mmcblk0p25; Where=/system_root; Type=ext4; Options=ro,barrier=119:13
T42<smatkovi> in droid-hal-device.rpm19:14
T42<smatkovi> oh no What is wrong and should be /dev/block/bootdevice/by-name/system19:33
T42<smatkovi> init.rc has still mount rootfs rootfs / remount bind ro nodev19:36
T42<smatkovi> what should it have again?19:36
T42<smatkovi> oh it should be outcommented19:37
T42<smatkovi> i can't remember where i added that mmcblk0p2519:40
T42<smatkovi> omg i wrote it in two files in the tmp folder. maybe i should have deleted them anyway19:50
T42<smatkovi> very strange it gets recreated and then states it gets this line from out/target/product/j5xnlte/system/vendor/etc/fstab.qcom  but there clearly is something else19:53
T42<elros34> system_root.mount finally looks correct19:57
T42<smatkovi> i did make clean and have to wait an hour now for the kernel19:58
T42<smatkovi> before it still had the error at system_root.mount but maybe a cleaner start will give better results tomorrow19:59
T42<elros34> There is really no point to run make clean if youconly changed some files in droid repositories20:27
T42<elros34> copy droid-hal-device*.rpm to device, install and test20:28
T42<b100dian> piggz: abr: is expected to have a line for each sfos release? Wouldn't a move instead of a copy suffice? We could specify initial available version as a separate column20:55
T42<smatkovi> unfortunately i still get this in journalctl: Jun 23 03:00:00 localhost systemd[1]: system_root.mount: Mount process exited, c21:33
T42<smatkovi> ode=exited status=3221:33
T42<smatkovi> maybe this is also relevant: Jun 23 03:00:00 localhost systemd[1]: Failed to mount Droid mount for /system_ro21:35
T42<smatkovi> ot.21:35
T42<smatkovi> al/17a855b54e4047b2b3c800939bd7fd04) is 1.5M, max 1.0M, 0B free.21:35
T42<smatkovi> Jun 23 03:00:00 localhost mount[574]: mount: /system_root: mount point not mount21:35
T42<smatkovi> ed or bad option.21:35
malshow the system_root.mount file21:43
T42<smatkovi> you're right, it looks wrong again21:50
malyeah, that What= seems wrong21:51
malhow did you get that file? did you create it or was it generated automatically21:51
T42<smatkovi> it was generated21:51
T42<smatkovi> i mean the last one21:51
T42<smatkovi> the one that looked more right, i guess that one i created21:52
malso create a working one21:52
T42<smatkovi> this is the line in fstab /dev/block/bootdevice/by-name/system         /          ext4    ro,barrier=121:52
T42<smatkovi> what should be in the working one21:53
T42<smatkovi> What=/dev/block/bootdevice/by-name/system ?21:53
malthe actual device node instead21:53
T42<smatkovi> you mean /dev/mmcblk0p25?21:53
malsomething like that, if that is what your device has for the system partition21:54
T42<smatkovi> yes that is for the system partition21:54
T42<smatkovi> is that the only thing i should change in the system_root.mount?21:55
T42<smatkovi> it still can't mount correctly :/21:57
malhmm, that is wrong otherwise also21:58
malthe options part21:58
malthat part and also Type from some other service like vendor.mount21:58
T42<smatkovi> Options=remount,bind,ro,nodev21:59
T42<smatkovi> Type=rootfs21:59
T42<smatkovi> i have no vendor.mount, i have efs.mount for example22:00
T42<elros34> obviously if your droid-hal-device*rpm in local repo have correct mount unit and sfos on device not then either you are creating image using different rpms or installing wrong image22:01
T42<smatkovi> should options be Options=ro,barrier=1 ?22:02
T42<elros34> why do you ask, you have correct file in local repo, you even pasted it, same probably for other mount units22:03
T42<elros34> zypper info droid-hal-<device> should tell you rpm version which you can compare to good one in local repo22:04
T42<smatkovi> it wants to refresh repositories :/22:07
T42<elros34> so 'rpm -q <package name>'22:09
T42<smatkovi> it really installs another one22:09
T42<elros34> you should have list of packages in same directory as sfos image22:11
T42<smatkovi> maybe it has to do with the fact that i extract and repack the tar.gz and hybris-boot.img22:14
T42<smatkovi> maybe it is in update-binary?22:15
T42<elros34> what?22:16
T42<smatkovi> the list of packages22:16
T42<smatkovi> but it's very strange22:16
T42<elros34> no, list of packages used in image are in same directory as sfos image, you can't miss it22:17
T42<smatkovi> in the .packages file the most recent correct package version is listed22:20
T42<elros34> so obviously you recreated or installed wrong one22:21
T42<smatkovi> i see now that the .tar.gz in the .zip was modified two days ago22:23
T42<smatkovi> which should be in fact today22:23
T42<smatkovi> i found the correct packaged tarball22:27
T42<smatkovi> but it had sfe instead of sailfishos in its name22:27
T42<smatkovi> and it doesn't install because of error 7 :/22:33
T42<smatkovi> i'll try it as .tar and not .tar.gz22:36
T42<elros34> this is common error and very old issue still not fixed. There many ways to overcome it but nothing simple22:38
T42<smatkovi> i messed with the kikstarter and probably something else, but i didn't remember where22:41
T42<smatkovi> it worked when i extracted the .bz2 and just used the .tar, then i edited a file to get the .gz and now it creates a .gz and a .bz2 and doesn't work properly22:43
mal@elros34 I was thinking, would it be possible to include busybox in the install zip and use that to extract the rootfs?22:47
T42<Mister_Magister> everything is possible mal :)22:47
T42<Mister_Magister> especially that22:47
T42<Mister_Magister> like adding busybox to hybris-boot target and then copying binaries/libs should be piece of cake22:48
T42<elros34> mal: yes, I did that but why not using tar.gz which AFAIK works correctly22:48
malwe have the prebuilt busybox in external/ already22:48
mal@elros34 yeah, both are possible, just need to choose one22:49
T42<Mister_Magister> switching to gz would be better imo22:49
T42<Mister_Magister> no overcomplicating just to keep format22:49
malis there any significant difference in size?22:49
T42<Mister_Magister> I don't think anyone worries about size honestly22:50
T42<Mister_Magister> otherwise it would be lz422:50
T42<smatkovi> of course it was the build_packages.sh22:50
T42<smatkovi> it's about 10-30Mb difference in size22:51
T42<smatkovi> so neglectible i would say22:51
malyeah, that is quite small difference22:53
T42<smatkovi> maybe 40MB so less than 10% of the whole size of the .zip file22:55
T42<smatkovi> now i have error 6 :/22:59
T42<smatkovi> can i somehow only reset the building of sailfish os packages?23:05
malwhat do you mean?23:17
T42<smatkovi> when i build sailfish os the .zip file ends up with a .tar.gz and a tar.bz2 (which is the correct one) but when i bunzip2 that and also change the and remove the -z flag from the tar command and change the mentioned filenames accordingl also in updater-script i still get an error and two days ago this was working23:20
malif you remove some package from droid-local-repo and rebuild it then it should at least be latest23:22
T42<smatkovi> yes i have that, but i want to be able to install it again23:23
malso why doesn't the new image contain the new changes?23:24
malor are you missing some change?23:24
T42<smatkovi> now it works :)23:26
T42<smatkovi> i just cloned dhd again23:26
T42<smatkovi> i think now i got rid of the mount error, but still it doesn't boot into gui. this is the output of journalctl -b —no-pager:
T42<smatkovi> and this of dmesg after boot:
Mister_Magisterlmao the video problem in sake, that is "Dropping frame due to QoS", is funny because it's interleaved underflow and overflow23:43
Mister_Magisterso it seems like frame is not in time but then it arrives and there are two frames, but then next frame is also late23:43
Mister_Magisterso it just keeps dropping them23:44
Mister_Magisterfunnily what i don't think cause issue is audioless video stream, like camera viewfinder or microtube for that matter, files cause issue but streams don't23:44
Mister_Magistermaybe perhaps due to buffer?23:45
Mister_Magisterlike its getting couple qos messages but only at the beginning23:45
Mister_Magisterfor local files you wouldn't have large buffer23:45
T42<smatkovi> interesting23:46
Mister_Magisterit doesn't entirely explain anything but its clues23:47
Mister_Magisterdecoder frame list getting long: 52 frames,possible internal leaking?23:47
Mister_Magisterand then when it fills up, it crashes the playback entirely?23:47
Mister_Magisterneither gst-droid nor droidmedia has message "decoder frame list getting long" wtf23:51
Mister_Magisteroh its in gstreamer23:52
T42<elros34> @smatkovi don't tell me you still didn't apply all hybris patches?23:55
Mister_Magisterso jolla bothered to add av1 to droidmedia but not to gstdroid lol23:56
T42<smatkovi> maybe the patches get overwritten?23:56
T42<smatkovi> oh yes the make clean maybe23:56
T42<elros34> no make clean doesn't overwrite anything23:57
T42<elros34> I am just asking because logs looks suspicious23:57
T42<smatkovi> fatal: previous rebase directory .git/rebase-apply still exists but mbox given.23:58

Generated by 2.17.1 by Marius Gedminas - find it at!