Tuesday, 2023-05-16

CarbontatedCaffeine"# NOTE: /vendor partition is now early-mounted and the fstab entry is specified in device tree: #       /proc/device-tree/firmware/android/fstab/vendor"00:08
CarbontatedCaffeineIs this why my vendor partition isn't being mounted00:08
CarbontatedCaffeineIs anyone able to assist me with the vendor partition01:15
malso add vendor patition to fstab01:22
maluse the other entries in fstab as example01:23
malthen run make hybris-hal and then repackage droid-hal01:23
CarbontatedCaffeine"/dev/sda31                                              /vendor             ext4    ro,barrier=1     wait,slotselect,avb=vbmeta,logical,first_stage_mount"01:39
CarbontatedCaffeineDo I need vbmeta01:40
CarbontatedCaffeineI'm using the fstab reference from the android website01:40
CarbontatedCaffeineIt's still not showing up02:12
CarbontatedCaffeinealso system doesn't mount automatically still02:13
CarbontatedCaffeineI have tried to fix it, but it still doesn't seem to work02:13
CarbontatedCaffeineSo when I go to /dev/block/platform/soc/624000.ufshc/by-name/ I still see system_a and system_b rather than "system" that I defined in fixup-mountpoints02:32
CarbontatedCaffeineSo it never mounts, since it can't found /dev/block/platform/soc/624000.ufshc/by-name/system02:33
CarbontatedCaffeineWould it have been better if I had used an older version of android for my port closer to the stock firmware04:37
T42<elros34> fixup-mountpoints is for systemd mount units,  it doesn't change by-name symlinks, they will be there and you do not care about them because you should have /dev/sdaX in mount units as we already tried05:58
CarbontatedCaffeineWell it doesn't seem to be working out07:49
CarbontatedCaffeineI added "/dev/sda33" to fstab with the same results07:50
CarbontatedCaffeine(fstab.common from the device repo)07:50
CarbontatedCaffeineHow do I get the .mount file to automatically have /dev/sda33 in it instead07:52
CarbontatedCaffeineThat's what I don't understand07:52
T42<stard0x> Is there sailfish os available for k20 pro ?07:54
T42<Mister_Magister> google it (re @stard0x: Is there sailfish os...)07:57
T42<b100dian> There is at least a droid-config-raphael on github but it doesnt have more than a couple of commits, so maybe it did not advance very well08:00
T42<elros34> @CarbonatedCaffeine but what results? You are not giving details. Have you check that vendor.mount in droid-hal-.rpm exist and use correct block device? If not then did you check fstab in out have yout entries?08:01
CarbontatedCaffeinevendor.mount doesn't even exist, I have said that08:03
CarbontatedCaffeine"# NOTE: /vendor partition is now early-mounted and the fstab entry is specified in device tree: #       /proc/device-tree/firmware/android/fstab/vendor"08:03
T42<elros34> so what about my other question then?08:04
CarbontatedCaffeineIt doesn't have vendor in fstab08:05
T42<elros34> so you have the answer08:05
CarbontatedCaffeineI'm STUCK08:06
CarbontatedCaffeineI have no idea why08:06
CarbontatedCaffeinethis answer is not helping08:06
T42<elros34> cmon, mal told you to add vendor entry to fstab. Did you add it?08:06
CarbontatedCaffeineNothing is working08:06
T42<elros34> where did you add it?08:07
T42<elros34> to which file08:07
T42<elros34> did you copy that fstab to out?08:07
CarbontatedCaffeineI recompiled *sigh*08:07
CarbontatedCaffeineI don't know that I can just do that08:10
CarbontatedCaffeineI just compile everything because, well08:10
CarbontatedCaffeineI can't be too sure08:10
T42<TheVancedGamer> CarbonatedCaffeine: ranting won't help, upload your trees with your modifications and send the link here so we can help08:13
T42<TheVancedGamer> and by the looks of it you're apparently adding direct /dev entries to fstab, which is not recommended08:13
CarbontatedCaffeineBut that's what everyone has been telling me!?08:14
T42<TheVancedGamer> so do it? I don't see what's the issue here08:14
CarbontatedCaffeine"adding direct /dev entries to fstab, which is not recommended"08:14
CarbontatedCaffeineI mean this08:14
T42<TheVancedGamer> unless we can't see your working environment and trees we can't suggest answers08:14
T42<TheVancedGamer> quite the opposite, Elros and mal have been telling you to add it to fixup-mountpoints and not touch your fstab at all08:15
T42<TheVancedGamer> the fixup-mountpoints script is supposed to handle all that08:15
T42<TheVancedGamer> quoted from Elros:08:16
T42<TheVancedGamer> "it doesn't matter, like I said it just find first string in whole fstab and replace it with second (see your fixup-mountpoint entry you pasted)"08:16
T42<TheVancedGamer> "in human language: replaces  'block/platform/soc/624000.ufshc/by-name/system_a'  with 'sda33' in fstab"08:16
T42<TheVancedGamer> what he said was the sed command executed by the fixup-mountpoints script does all this08:16
CarbontatedCaffeineThat makes no sense to me08:17
CarbontatedCaffeinenone of it08:17
T42<TheVancedGamer> have you read the fixup-mountpoints script and seen what it does?08:17
T42<TheVancedGamer> I recommend you learn what `sed` does and how bash scripts work in general08:17
CarbontatedCaffeineI'm not trying to learn how to use commands, I'm porting a device08:18
T42<TheVancedGamer> https://github.com/mer-hybris/hybris-boot/blob/master/fixup-mountpoints#L608:18
T42<TheVancedGamer> you'll need to learn how to work around your way in linux to get anything fruitful08:19
CarbontatedCaffeineI'm literally so close08:19
CarbontatedCaffeineit's just this file system garbage08:19
CarbontatedCaffeineIt's getting confused because of the A/B partitions08:19
T42<TheVancedGamer> see, if you're not going to do it the way all porters have been doing it, you're bound to get issues08:19
T42<TheVancedGamer> FP4 is A/B for example, you can check that for hints08:20
CarbontatedCaffeineI have been08:20
CarbontatedCaffeineit's not working08:20
CarbontatedCaffeineI'm doing the same stuff08:20
T42<TheVancedGamer> ok, then you say you added `/dev/sda11` or whatever to your fstab08:20
T42<TheVancedGamer> while you're not supposed to modify the paths08:20
CarbontatedCaffeineI did that ages ago08:20
T42<TheVancedGamer> the fixup-mountpoints script is there to do it08:20
T42<TheVancedGamer> as well as add it for dhd08:21
CarbontatedCaffeineYou're just making this more confusing08:21
T42<TheVancedGamer> I think the HADK very clearly explains that you need to add partitions to fixup-mountpoints script located in hybris-boot/fixup-mountpoints in your hadk source root08:21
CarbontatedCaffeineI did?08:22
CarbontatedCaffeineI HAVE DONE ALL THAT08:22
CarbontatedCaffeineI have told you08:22
T42<TheVancedGamer> then push your changes and let us see08:22
CarbontatedCaffeineI have08:22
T42<TheVancedGamer> links?08:22
T42<TheVancedGamer> where is your device tree?08:23
T42<TheVancedGamer> device/google/marlin or whatever08:23
CarbontatedCaffeineAll I've ever needed to do is change fstab so I don't bother08:24
T42<TheVancedGamer> see that's the problem, you DON'T change the fstab08:24
CarbontatedCaffeineI DO08:24
T42<TheVancedGamer> the trees will always stay untouched08:24
T42<TheVancedGamer> explain then why you need to change fstab?08:24
CarbontatedCaffeineYou're telling me, I don't change it, but then explain why I do08:25
CarbontatedCaffeinewhat are you talking about08:25
T42<TheVancedGamer> let's try this again, I gather that you are changing fstab located in device/google/marlin08:25
T42<TheVancedGamer> correct?08:25
T42<TheVancedGamer> why do you feel the need to change it?08:25
T42<TheVancedGamer> when we have just established that fixup-mountpoints will change it during compilation08:26
CarbontatedCaffeineI'm trying to mount vendor08:26
CarbontatedCaffeineIt's not showing up at all08:26
CarbontatedCaffeinethere's no mount for it08:26
T42<TheVancedGamer> then it is early-mounted by the dtb08:26
CarbontatedCaffeineI tried using fixup-mountpoints08:26
T42<TheVancedGamer> you don't need to worry about it08:27
CarbontatedCaffeineIt's not showing up08:27
CarbontatedCaffeineat all08:27
T42<TheVancedGamer> have you tried manually mounting in shell?08:27
CarbontatedCaffeineit says wrong fs or something when I make a dir for vendor in / and I run "mount /dev/sda31 /vendor"08:28
T42<TheVancedGamer> `dmesg` and see what fs errors08:28
T42<TheVancedGamer> was the device booting lineageOS prior to flashing hybris-boot?08:28
CarbontatedCaffeineHere's dmesg08:37
CarbontatedCaffeinevendor is only ever mentioned twice08:38
CarbontatedCaffeineThis is what I mean, like I have no idea why vendor isn't mounting, or is even mentioned in the rootfs anywhere08:41
T42<elros34> then focus little. I asked you about fstab, did you make now needed modifications? Did you check droid-hal*rpm?08:42
T42<elros34> I you don't want to learn anything then this is not going anywere. Did you bother to read all hadk-hot at least once?08:43
CarbontatedCaffeineI did08:43
CarbontatedCaffeineI believe that part isn't documented well enough08:45
T42<elros34> can you elaborate, do you see vendor.mount in droid-hal*rpm or not now?08:45
CarbontatedCaffeine"If you don't want to learn anything then this is not going anywere" why you telling me to give up08:45
CarbontatedCaffeinewhat even is that08:46
CarbontatedCaffeineI don't even know how to check if it's in there08:46
T42<elros34> I didn't you just said that you want  porting not learning commands08:46
T42<elros34> then ask how to do something instead ignoring my questions08:47
CarbontatedCaffeineI didn't like that question08:47
T42<elros34> ? got to $ANDROID_ROOT/droid-local-repo and find droid-hal-device*rpm, unpack it with some graphical archive manager you use and check in sparse whether vendor.mount exists08:49
T42<elros34> actually not in sparse, after unpacking/opening it will by same path as in device09:00
CarbontatedCaffeineWell I have learned how to use grep properly now actually09:03
CarbontatedCaffeineI've needed to find references of stuff09:03
CarbontatedCaffeinefine I'll learn more stuff09:04
CarbontatedCaffeineI'm just frustrated because I've been stuck on the filesystem stuff for 3 days now09:05
CarbontatedCaffeineI can't even build my thing anymore10:14
CarbontatedCaffeineI give up for the day10:14
CarbontatedCaffeinenevermind I made another mistake10:18
CarbontatedCaffeineit's fine10:18
CarbontatedCaffeineelros34: no vendor.mount found12:15
T42<Teo> Hello everyone ! I'm currently trying to port to a Moto Z Play (addison), and I finally built the image zip file. Unfortunately, when I try to install it through TWRP (via sdcard or adb sideload), I have an error "Signal 11", and that's all. I don't have any relevant log. Do you have an idea of what could cause that, or what can I check on my image ? Thank you !16:38
T42<b100dian> It might be bz2 format not supported. Does uploading the bz2 and tar -xjf ing over adb shell work?16:42
T42<Teo> Oh you're right, I got "tar: exec bunzip2: No such file or directory" error16:45
T42<b100dian> You can either manually unpack just by sending the tar file and flash hybris-boot independently (search numeric-owner in logs here) or apply changes to hybris-boot and build mic with another command like https://piggz.co.uk/sailfishos-porters-archive/index.php?log=2023-04-13.txt#line29316:55
T42<Teo> Thank you ! I'll give it a try17:06
T42<b100dian> You should also set an username in telegram so that people across the IRC bridge can ping/reply to you Teo17:57
T42<Papoucifle> Done ! Sorry, I thought I already had one18:30
T42<elros34> You know there is some old port for addison?19:39
T42<elros34> CarbonatedCaffeine so again the same question... did you ammend fstab in out/ and rebuild droid-hal?19:41
T42<Papoucifle> Yes I know there's one already. I tried it but it's way too outdated, nothing works reliably on it.20:21
CarbontatedCaffeine"did you ammend fstab in out/ and rebuild droid-hal?" No I didn't.21:35
malcan you show your fstab from device repo, the modified one21:36
CarbontatedCaffeine Android fstab file. # The filesystem that contains the filesystem e2fsck binary (typically /system) cannot # specify 'check', and must come before any filesystems that do specify 'check'  # NOTE: /vendor partition is now early-mounted and the fstab entry is specified in device tree: #       /proc/device-tree/firmware/android/fstab/vendor  #<src>                                                  <mnt_point>         <type>  <mnt_fla21:39
CarbontatedCaffeineWrong paste21:39
CarbontatedCaffeineLet me get this clear, I had to add /boot otherwise it wouldn't build21:40
CarbontatedCaffeinethat's the only thing I've done to it21:40
CarbontatedCaffeineIt's also the same on in /out21:44
CarbontatedCaffeineDo I have to specifically call for system_a21:52
CarbontatedCaffeineas someone has mentioned that I cannot just change the symlink of that21:54
malyou select which slot you use and in fixup-mountpoints you define the partitions nodes of that slot to replace the system etc21:57
CarbontatedCaffeineThat's the thing, it doesn't replace it21:58
CarbontatedCaffeinefor me21:58
CarbontatedCaffeineit's still system_a and system_b21:58
malshow your fixup-mountpoint part21:58
malI think misunderstand what fixup-mountpoints does21:58
maldroid-hal build creates systemd mount services based on your fstab and replaces the device nodes in fstab entries with the ones defined in fixup21:59
malwhat problem are you trying to solve?21:59
CarbontatedCaffeineOkay so basically the fstab has this "/dev/block/platform/soc/624000.ufshc/by-name/system     /"22:00
CarbontatedCaffeineand when I boot the system on my phone22:00
CarbontatedCaffeineit obviously can't find it22:00
malfstab is not used in sailfish22:01
CarbontatedCaffeinebecause my phone has two partitions for system22:01
malmounts are handled by systemd not fstab22:01
CarbontatedCaffeinethen why does adding /boot to my fstab fix something?22:01
malbecause build needs to know boot partition to create the installation script which also flashes kernel22:02
CarbontatedCaffeinealright, so why can't I change system to "/dev/block/platform/soc/624000.ufshc/by-name/system _a    /"22:03
CarbontatedCaffeinedoes that not work22:03
malso you didn't understand what I just said about systemd mount service and fixup-mountpoints22:03
CarbontatedCaffeineYou're not making any sense to me either22:04
CarbontatedCaffeineI'm sorry but22:04
CarbontatedCaffeineI don't understand why my fixup-mountpoints is not working22:04
malas you see in your fixup you have "-e 's block/platform/soc/624000.ufshc/by-name/system sda33 ' \" which replaces the system with the actual device node (when creating systemd mount services) and that node (sda33) in fixup matches system_a22:05
malwhy do you say it's not working?22:05
CarbontatedCaffeineWhat do you mean why22:05
CarbontatedCaffeineI have told the people here multiple times22:05
malhave you checked on device if the /usr/lib/systemd/system/system.mount contains correct node i.e. /dev/sda33 or something22:06
CarbontatedCaffeineit doesn't22:06
CarbontatedCaffeineit contains what is found in fstab.common22:06
CarbontatedCaffeineand system_a/_b still exists22:06
CarbontatedCaffeinethat's what I've been trying to telling you22:07
malwell you were talking about fstab all the time22:07
malnot about systemd mount services22:07
CarbontatedCaffeineAlright, are we on the same page now22:08
malof course system_a and system_b exist22:08
CarbontatedCaffeinedo you want me to show you the system.mount file22:08
malso do you see any error in droid-hal build log?22:09
CarbontatedCaffeinechecking now22:10
CarbontatedCaffeineit doesn't have any22:11
CarbontatedCaffeine*would you like to see the system.mount file*22:11
malsure but also the whole droid-hal build log22:12
CarbontatedCaffeineof course22:12
CarbontatedCaffeineHere's the droid-hal log22:13
CarbontatedCaffeinehttps://pastebin.com/Y5fzjKYE (system.mount)22:14
CarbontatedCaffeinethis is from the latest rpm22:14
CarbontatedCaffeineI made yesterday22:14
malyou should be looking at system_root.mount22:15
malas you can see that system.mount is doind a bind mount which is special thing when device has system as root22:16
CarbontatedCaffeineso it binds it to the node?22:16
malI mean system_root.mount mounts the actual device and that system.mount bind mounts /system_root/system to /system22:17
CarbontatedCaffeineThanks for that, I was a bit confused about which did what22:18
CarbontatedCaffeineOh wait it has the right thing now?22:19
CarbontatedCaffeinebut when I boot it, it'll have no system/system_root22:19
CarbontatedCaffeinewait a minute22:20
maldoes command "mount" show system and some other stuff that was in your fstab22:20
malthat looks ok22:21
CarbontatedCaffeineand when I boot it, it's not the same22:22
CarbontatedCaffeineI'll do it now22:22
malwhat do you mean?22:22
malyou still haven't said what you see in output of "mount"22:23
CarbontatedCaffeineon the phone?22:23
malyes, of course22:24
CarbontatedCaffeineI need to reflash it then, because I edited a lot of stuff on it22:24
CarbontatedCaffeineJust so we have what it builds22:25
CarbontatedCaffeineDoes that make sense22:26
*** rdr_ is now known as rdr22:26
CarbontatedCaffeineOk, I built droid-hal just to make sure22:30
CarbontatedCaffeinelooks good22:30
CarbontatedCaffeineI'm going to copy new rootfs22:35
CarbontatedCaffeineand boot.img22:35
CarbontatedCaffeineand we'll see22:36
CarbontatedCaffeineWhy does it take so long the first time I run "mic" to build the rootfs22:40
CarbontatedCaffeineI'm always wondering if it doesn't pack my new rpms into the new roofts archive22:41
CarbontatedCaffeine(file system)22:43
CarbontatedCaffeinelooks good, no vendor though22:43
malyou can see the versions it used in the .packages file in the folder where it creates the zip22:43
malif you really need vendor I would just add it to fstab and rebuild22:44
CarbontatedCaffeineOkay *shrug*22:45
CarbontatedCaffeineWell, I don't know if I need it22:45
CarbontatedCaffeineelros said I should22:45
malwell how about you manually mount it and check what it contains22:45
CarbontatedCaffeineI don't have a path of /vendor22:46
CarbontatedCaffeinewhere should I mount it22:46
T42<elros34> well you don't need vendor, we just repeat to add several times  just for fun, ignore more22:46
CarbontatedCaffeineAlso I just realized, it's packing old rpms22:47
CarbontatedCaffeinewhat can I do about that?22:47
mal@elros34 are you sure?22:47
malI'm still confused what the actual issue it that is being fixed22:48
CarbontatedCaffeineme too22:48
CarbontatedCaffeineGraphics isn't working22:48
malhow does it fail22:48
CarbontatedCaffeinedunno *shrug* lets see22:48
CarbontatedCaffeineor dmesg22:48
T42<elros34> there was no real issue, he was supposed to add vendor to fstab ant that is all hard task22:48
CarbontatedCaffeine"Also I just realized, it's packing old rpms"22:50
CarbontatedCaffeinehttps://pastebin.com/E5ceQuRh (journal log)22:51
malwell first of all you have too new droid-config submodule22:52
malwhich is causing this: dummy_compositor[3588]: /usr/sbin/dummy_compositor: unrecognized option '--hwc-restart'22:53
CarbontatedCaffeineI thought I fixed that?22:54
CarbontatedCaffeineI checked hadk hot22:55
maland you have config package rebuilt and correct version installed to the image?22:55
CarbontatedCaffeineit's installing old rpms22:56
CarbontatedCaffeinenot new ones22:56
CarbontatedCaffeineWait nah22:56
CarbontatedCaffeineI just forgot to run build_packages.sh --version22:56
CarbontatedCaffeineall good22:56
CarbontatedCaffeineActually, my bad22:57
CarbontatedCaffeineI think I forgot to do droid-config22:57
CarbontatedCaffeineI did droid-hal-device22:57
CarbontatedCaffeineI'll fix that up22:57
malremember build_packages.sh -c after that22:59
CarbontatedCaffeinewill do23:03
CarbontatedCaffeineVersions of packages still don't line up23:17
CarbontatedCaffeineI'm doing23:21
CarbontatedCaffeinerpm/dhd/helpers/build_packages.sh --droid-hal23:21
CarbontatedCaffeinerpm/dhd/helpers/build_packages.sh --droid-hal rpm/dhd/helpers/build_packages.sh --configs23:21
CarbontatedCaffeinealong with rpm/dhd/helpers/build_packages.sh --version23:22
CarbontatedCaffeineat the end23:22
CarbontatedCaffeineWhen I build my rootfs, should it say I have new packages to install?23:23
malit should23:25
malor something that it gets some new versions of some packages23:25
CarbontatedCaffeineI wonder what I'm doing wrong then23:25
malI had a bit similar issues a while ago23:27
CarbontatedCaffeineThe .package file says "droid-config-marlin.aarch64 1-202305161113"23:28
CarbontatedCaffeineThe rpm says "droid-config-marlin-1-202305162321.aarch64.rpm"23:28
CarbontatedCaffeineShould I do this? "# EXTRA_NAME adds your custom tag. It doesn't support '.' dots in it! export EXTRA_NAME=-my1"23:30
CarbontatedCaffeineUse extra_name=my123:30
CarbontatedCaffeinefor different versions?23:31
malnot sure if that matters, afaik it overwrites the previous one23:31
CarbontatedCaffeineThis is really weird then :/23:32
CarbontatedCaffeineIs it because I'm running sudo mic create fs --arch=$PORT_ARCH --tokenmap=ARCH:$PORT_ARCH,RELEASE:$RELEASE,EXTRA_NAME:$EXTRA_NAME --record-pkgs=name,url --outdir=SailfishOScommunity-release- --pack-to=sfe-$DEVICE-$RELEASE$EXTRA_NAME.tar.gz ./Jolla-\@RELEASE\@-marlin-\@ARCH\@.ks23:33
CarbontatedCaffeineThis is to pack it into a tar.gz23:33
CarbontatedCaffeineand I'm ONLY running this23:33
CarbontatedCaffeineI'm trying just using "rpm/dhd/helpers/build_packages.sh --mic"23:34
CarbontatedCaffeineAh look, now it works23:34
CarbontatedCaffeine"773 packages to be installed, 756 packages gotten from cache, 17 packages to be downloaded"23:35
CarbontatedCaffeineI'm adding that to my notes23:35
CarbontatedCaffeineI'm still skeptical, so I'm going to check the files *just in case*23:37
malwait, maybe you need to run: createrepo_c --outputdir=droid-local-repo/$DEVICE/repo --location-prefix=../ droid-local-repo/$DEVICE23:37
malif you use that manual mic command23:37
CarbontatedCaffeineOh I see23:39
CarbontatedCaffeineso what does this do?23:39
CarbontatedCaffeinesince I already see a repo folder there23:39
malit recreates the local repo metadata with latest packages23:39
CarbontatedCaffeineOh nice23:40
CarbontatedCaffeinePackages line up again!23:40
CarbontatedCaffeineTime to try again23:40
malso if you run mic manually you should always run that command before mic if you have built any new rpms23:42
malthat is what the build script does https://github.com/mer-hybris/droid-hal-device/blob/master/helpers/build_packages.sh#L36423:43
CarbontatedCaffeineI understand now23:44
CarbontatedCaffeinehere's journalctl23:56
CarbontatedCaffeineWell, just the lipstick failing part23:56

Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!