| T42_ | <A_T_R> How? | 00:43 |
|---|---|---|
| T42_ | <A_T_R> what is this means "need to tag repo for every obs rebuild" | 04:08 |
| voidanix[m] | I do not have touch at the encryption screen... Could I have missed something? | 08:53 |
| voidanix[m] | Maybe this is a panel bug, no idea | 08:53 |
| mal | does persistent journal show anything useful? | 09:14 |
| voidanix[m] | Absolutely nothing IIRC | 09:28 |
| voidanix[m] | I can send logs this afternoon since i don't have the device at hand rn | 09:29 |
| T42_ | <elros34> @A_T_R git tag | 11:34 |
| T42_ | <elros34> voidanix[m] what framework encryption screen use? If it's qt then IIRC there are some env flags which enables more verbose qt qpa input system | 11:40 |
| voidanix[m] | @elros34 I assume the builtin device/disk decryption screen uses Qt | 12:12 |
| T42_ | <elros34> then try QT_QPA_EVDEV_DEBUG=1 QT_LOGGING_RULES="qt.qpa.input=true" | 12:25 |
| voidanix[m] | tried putting that in /etc/sysconfig but wouldn't work, any other place to do it? | 13:27 |
| T42_ | <elros34> I would use droid-hal-device.conf | 13:32 |
| T42_ | <elros34> if not then check what systemd service starts that screen and see from where it reads env or add one | 13:33 |
| voidanix[m] | no output... hmm... | 17:02 |
| T42_ | <Connor> Kia ora everybody! I've been working on a port for surya (Poco X3 NFC) and am kinda struggling with dynamic partitions. I've got my vendor partition mounting but can't seem to get the system one to work which I think is breaking some things. I've got telnet 2323 access and have popped the output of systemctl status for both vendor.mount and system.mount (along with the contents of the actual files) here: https://pastebin.com/NP4kUfb9 | 19:13 |
| T42_ | <Connor> I've tried about a dozen different variations on my system.mount at this point so any help would be greatly appreciated! | 19:13 |
| T42_ | <elros34> show findmnt and ls -al /system/ | 19:40 |
| T42_ | <elros34> do you have system in /dev/mapper/? | 19:44 |
| T42_ | <Connor> https://pastebin.com/A6kKPByS is the output of findmnt; ls -al /system/ returns /system/: No such file or directory ; the only things in /dev/mapper are a file called "control" and the dynpart-vendor folder | 19:47 |
| T42_ | <elros34> so dynpart failed, check journal to see why | 19:48 |
| T42_ | <elros34> parse-android-dynparts* | 19:49 |
| T42_ | <elros34> well I think you can safely run 'parse-android-dynparts <path to super partition>' now | 19:51 |
| T42_ | <Connor> I tried "parse-android-dynparts /dev/block/bootdevice/by-name/super" and got https://pastebin.com/urGcs61w but I'm not quite sure what to do with it (or if I've got the correct path to my super partition) | 20:01 |
| T42_ | <elros34> at least you can se it should have system and product, run whole command from dmsetup.sh and see (check dmesg) | 20:05 |
| T42_ | <elros34> product partition looks suspicious | 20:06 |
| T42_ | <elros34> can you show also android_device repository? | 20:14 |
| T42_ | <Connor> Is the android_device repository just the LineageOS one I used in my local manifest? If so, it's https://github.com/LineageOS/android_device_xiaomi_surya | 20:31 |
| T42_ | <elros34> that one, lineage20? | 20:32 |
| T42_ | <Connor> Woops no sorry, I'm using the lineage-18.1 branch | 20:33 |
| T42_ | <Connor> https://github.com/LineageOS/android_device_xiaomi_surya/tree/lineage-18.1 | 20:33 |
| T42_ | <elros34> so did you run whole dmsetup command? | 20:34 |
| T42_ | <Connor> I tried but I can't find dmsetup.sh, tried /usr/bin/droid/dmsetup.sh but it isn't there | 20:39 |
| T42_ | <elros34> so how is you /dev/mapper/vendor created then? rpm -ql droid-config-surya | grep dmsetup | 20:40 |
| T42_ | <Connor> That gives me "/usr/lib/systemd/system/dmsetup.service" | 20:41 |
| T42_ | <elros34> so it should executes some script. anyway you don't need script just run command: dmsetup create --concise "$(/usr/bin/parse-android-dynparts /dev/<super block>)" | 20:42 |
| T42_ | <Connor> That gives me syntax error: unexpected ")" ; I tried changing it to /dev/super but that gives me open failed: /dev/super | 20:48 |
| T42_ | <elros34> /dev/<super> is path to your super partition so /dev/sda1 or /dev/sdc70, you should know which one is yors | 20:51 |
| T42_ | <elros34> didn't you create fixup-mountpoints or amend dmsetup.sh to match your device? | 20:52 |
| T42_ | <Connor> My bad, just grabbed it from my fixup-mountpoints, it's sda15 | 20:53 |
| T42_ | <Connor> dmsetup create returned: A non-block device file at '/dev/mapper/dynpart-vendor' is already present | 20:53 |
| T42_ | <Connor> I'll reboot and try again? | 20:54 |
| T42_ | <elros34> no, any other error in dmesg? what about /dev/mapper now | 20:54 |
| T42_ | <Connor> Ooh dynpart-system and dynpart-product are there in /dev/mapper now! | 20:55 |
| T42_ | <elros34> so you mess up something in scripts. You must have dmsetup executed somewhere otherwise you wouldn't have dynpart-vendor | 20:56 |
| T42_ | <Connor> I do have a dmsetup.service which runs "/bin/bash /usr/bin/droid/dmsetup.sh" , do you think that could be the problem? | 20:59 |
| T42_ | <elros34> but you don't have that scripts so. I don't see your changes so I don't know | 21:00 |
| *** rdr_ is now known as rdr | 22:13 | |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!