| *** n2klb_ is now known as n2klb | 02:04 | |
| T42 | <elros34> @Mattia990 link doesn't work. Does evdev_trace show touchscreen node. Are you sure all needed partitions are mounted firmware loading doesn't fail? | 02:37 |
|---|---|---|
| sharks | Alright, I'm stuck again - I have attempted to get parse-android-dynparts working, have added it to patterns, built the rpm, added `/usr/bin/droid/dmsetup.sh`, and `dmsetup.service`, `vendor.mount`, etc. to `/usr/lib/systemd/system/`. Finally I put `%define makefstab_skip_entries / vendor` in `droid-hal-device.spec`. | 10:03 |
| sharks | But after rebuilding droid-hal and trying to recreate the rootfs with `build_packages.sh --mic`, I get "file /usr/lib/systemd/system/vendor.mount conflicts between attempted installs of droid-config-....aarch64 and droid-hal-....aarch64" | 10:03 |
| sharks | Clearly I have missed a step but I'm too much of a novice to work out what it is. Can anyone please point me in the right direction? | 10:03 |
| mal | sharks: you need to skip the mount point generation for the partitions that are handled with parse-android-dynparts, something like this in droid-hal spec https://github.com/mlehtima/droid-hal-fp5/blob/master/droid-hal-fp5.spec#L25 | 11:33 |
| T42 | <elros34> @sharks if you have added '/ vendor' then that is your issue, it's '/vendor' | 14:06 |
| T42 | <nikita_kraev> mal: Does it matter if the `%define makefstab_skip_entries / /odm /product /system /system_ext /vendor` should live in hal or in config? | 14:19 |
| mal | needs to be in droid-hal spec | 14:21 |
| T42 | <nikita_kraev> But we define mounting, parse-dynparts and systemd in droid-config, correct? | 14:22 |
| mal | yes but automatic mount point generation based on android fstab etc is done in droid-hal packaging stage | 14:28 |
| mal | so if we add any custom mount point service that replace the automatic ones then we need to prevent the automatic generation of those mount services in droid-hal | 14:28 |
| T42 | <nikita_kraev> that makes sense, thanks! | 14:29 |
| T42 | <Mattia990> Sorry, i didn't try the link. | 16:19 |
| T42 | <Mattia990> By the way i can't see the input of the touchscreen. Line 1530 scares me | 16:19 |
| T42 | <Mattia990> dmesg: https://paste.opensuse.org/pastes/17aa6a2a60b8 | 16:19 |
| T42 | <Mattia990> evdev: https://paste.opensuse.org/pastes/c21e37f911a4 (re @elros34: @Mattia990 link does...) | 16:19 |
| T42 | <elros34> so can't you simply use dtb from lineage? IIRC it's even in seperate partition so if you do not touch it then you should have right one from lineage test | 16:36 |
| T42 | <Mattia990> I tried different dtb, but in the lineage or the rom i'm using now as base there isn't included. Also i tried various dtbo with no success | 20:29 |
| T42 | <Mattia990> I tried hardcoding gpios values in fts touchscreen drivers or using the newest fts touchscreen drivers from lineage os 22.2 but i always have the same problem | 20:30 |
| mal | your build doesn't generate dtbo.img? | 20:30 |
| T42 | <Mattia990> Yes, but if i flash that the phone doesn't boot, it goes straight to fastboot | 20:31 |
| T42 | <Mattia990> I would like to unpack it and see what is going inside, but i can't find the part wheere the dtbo is created | 20:31 |
| T42 | <Mattia990> Or the tool i need to use to unpack it | 20:32 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!