*** OhYash1 is now known as ohyash | 08:56 | |
Nebrassy[m] | tried to build in Pie again, same issue I had on oreo, device instantly reboots, console ramoops are of the previous twrp session (I know for a fact this kernel supports ramoops) | 11:10 |
---|---|---|
Nebrassy[m] | I noticed the kernel doesn't include any dtbs so no early mounts | 11:10 |
Nebrassy[m] | also what's DATA_PARTITION= in the ramdisk supposed to point towards?, I might have wrong mountpoints | 11:10 |
T42 | <elros34> it's should points directly to your data partition so /dev/mmcblk0px or /dev/sdx but unlikley device wil reboot straightaway if it's wrong. What device? Did you revert skip_initramfs support in kernel. | 11:15 |
Nebrassy[m] | ok I definitely have wrong mountpoints, device is jasmine_sprout, here's all https://github.com/nebrassy?tab=repositories | 11:16 |
Nebrassy[m] | I also don't see where it mounts system or vendor anywhere | 11:17 |
Nebrassy[m] | I usually use this to build twrp, don't know if I need the revert for sailfish https://github.com/nebrassy/kernel_xiaomi_sdm660-sailfish/commit/ff66eb6e9aeb792b46bcf74b5642bca7a545ccaa | 11:17 |
Nebrassy[m] | (also tried adding audit=0 to cmdline) | 11:19 |
Nebrassy[m] | and, isn't it supposed to be /dev/block/mmcblkXX instead of /dev/mmcblkXX? | 11:19 |
T42 | <elros34> @Nebrassy which branch in kernel is the one you use now? | 11:32 |
Nebrassy[m] | hybris-16.0 | 11:32 |
T42 | <elros34> disable CONFIG_VT in kernel, flash it and try again | 11:36 |
Nebrassy[m] | ok | 11:43 |
T42 | <elros34> not very important right now but your droid-hal-device.conf is wrong read again comment you put there "WRITE | 11:51 |
T42 | <elros34> ˓→ALL IN ONE LINE(:" | 11:51 |
*** OhYash1 is now known as ohyash | 12:12 | |
Nebrassy[m] | ah didn't notice, thanks | 12:13 |
T42 | <elros34> just to be sure: you know that you can just flash hybris-boot, you dont need to build whole new image | 12:21 |
Nebrassy[m] | yup, just building hybris-hal | 12:22 |
Nebrassy[m] | I need to flash manually anyway, my twrp doesn't have busybox/bunzip | 12:23 |
Nebrassy[m] | it stays live for a bit longer after disabling CONFIG_VT, and got ramoops http://haste.aicp-rom.com/ujuweroger.coffeescript | 12:33 |
T42 | <elros34> ok so enable CONFIG_VT back and revert: 6c8294064937459a6a0e79b57e01fde0efd554d0 dd96daf41e0ab5c87171b3a55cab2d3ae9e5ee0e https://github.com/nebrassy/kernel_xiaomi_sdm660-sailfish/commits/hybris-16.0?after=78f898d91b579b63d462d507533cdaa0c20bb4f7+34&path%5B%5D=drivers&path%5B%5D=tty. Do you have /data/.stowaways/.sailfishos/init.log n | 12:38 |
T42 | ow? How long it stays on now? | 12:38 |
Nebrassy[m] | used to be like a second, now more like 8 | 12:39 |
Nebrassy[m] | and nah no logs in data, pretty sure it isn't reaching mount yet | 12:40 |
Nebrassy[m] | what exactly should I revert? | 12:42 |
Nebrassy[m] | nvm didn't see | 12:42 |
Nebrassy[m] | building | 12:44 |
Nebrassy[m] | kernel/xiaomi/sdm660/drivers/tty/tty_port.c:607:34: error: no member named 'worker_thread' in 'struct tty_port' | 12:59 |
Nebrassy[m] | return sched_setscheduler(port->worker_thread, policy, ¶m); | 12:59 |
Nebrassy[m] | also revert https://github.com/nebrassy/kernel_xiaomi_sdm660-sailfish/commit/b4356652a823d2d90ea1771aae65f44640f056e1 | 12:59 |
Nebrassy[m] | ? | 12:59 |
T42 | <elros34> probably. The faulty commit is "tty: move tty_port workqueue to be a kthread" but other depends on these changes | 13:01 |
Nebrassy[m] | it's the same merge so yeah, trying | 13:02 |
Nebrassy[m] | had to rever https://github.com/nebrassy/kernel_xiaomi_sdm660-sailfish/commit/7da5dcecd964bbb6c25337420ae7adc768981aa4 too | 13:25 |
Nebrassy[m] | http://haste.aicp-rom.com/axejuvapef.coffeescript | 13:25 |
Nebrassy[m] | also unable to open an initial console | 13:25 |
T42 | <elros34> that shouldn't be an issue. So now you have enabled VT? | 13:27 |
Nebrassy[m] | Yup | 13:27 |
T42 | <elros34> pfk initialize for you but I remember other with similar issue to your have to disable CONFIG_PFK so it's worth to try. Also enable CONFIG_FW_LOADER_USER_HELPER back | 13:30 |
Nebrassy[m] | hm idk why I thought I didn't disable it, I'll try | 13:32 |
Nebrassy[m] | same http://haste.aicp-rom.com/iwaxeroraq.coffeescript | 13:47 |
T42 | <elros34> looks like it crash somewhere in init script when mdev is used | 13:49 |
T42 | <elros34> https://github.com/nebrassy/kernel_xiaomi_sdm660-sailfish/commits/7a1d81a954182461348b8c6b5ae85008b984c761/lib/kobject_uevent.c | 13:51 |
Nebrassy[m] | revert latest one? | 13:52 |
T42 | <elros34> I would try, you can also compare with some other working kernel (same version) | 13:53 |
Nebrassy[m] | worked, got telnet http://haste.aicp-rom.com/ahorifepop.md | 14:23 |
Nebrassy[m] | should I keep CONFIG_PFK disabled? | 14:23 |
T42 | <elros34> you can keep it disabled it shouldn't matter | 14:24 |
Nebrassy[m] | what's the root password for devel-su | 14:25 |
T42 | <elros34> in telnet you are already root user | 14:25 |
Nebrassy[m] | right, thanks for the help | 14:27 |
Nebrassy[m] | so what's next? | 14:45 |
T42 | <elros34> grab full journalctl --no-page | 14:46 |
Nebrassy[m] | http://haste.aicp-rom.com/ojozocoqed.pl | 14:50 |
T42 | <elros34> looks like wrong fixup-mountpoints: compare your changes with your fstab | 14:53 |
Nebrassy[m] | ah yup, guessing it's time to rebuild everything | 14:56 |
Nebrassy[m] | already fixed mountpoints just only build hybris-boot after it | 14:56 |
T42 | <elros34> before creating new image you can unpack droid-hal*rpm and check whether /lib/systemd/system/*.mount contains correct partitions (without by-name) | 14:59 |
Nebrassy[m] | http://haste.aicp-rom.com/inidaqagay.sql | 18:08 |
Nebrassy[m] | I don't have vendor in fstab, since it's early mounted, should I add it? | 18:08 |
T42 | <elros34> or just create vendor.mount and symlink to enable it and put it to sparse | 18:19 |
T42 | <elros34> by default mount units are enabled by symlink in /etc/systemd/system/local-fs.target.wants/ by droid-hal rpm post install script | 18:25 |
Nebrassy[m] | that saved me a rebuild but I still rather just add to fstab | 18:39 |
mal | some new devices need a custom vendor mount service because those have also other things mounted under /vendor | 18:44 |
mal | so the mount order has to be correct | 18:44 |
T42 | <elros34> mal: If I understand systemd manual correctly custom vendor shoudn't be needed: "If a mount unit is beneath another mount unit in the file system hierarchy, both a requirement dependency and an ordering dependency between both units are created automatically." | 18:46 |
Nebrassy[m] | that'd be me then as dsp, bluetooth, persist and modem are mounted in vendor | 18:46 |
mal | @elros34 hmm, is there some mention about which version has such support | 18:49 |
T42 | <elros34> no, I found it here https://www.freedesktop.org/software/systemd/man/systemd.mount.html | 18:49 |
Nebrassy[m] | https://paste.ubuntu.com/p/sQxCHBymWB/ | 18:54 |
mal | @elros34 looking at git blame of systemd that should be a very old feature, probably even an original feature | 18:54 |
Nebrassy[m] | looks like it mounted persist first | 18:54 |
T42 | <elros34> it's about /vendor/dsp and /vendor/bt_firmware not /persist | 18:56 |
Nebrassy[m] | wait that's /mnt/vendor/persist, why | 18:58 |
Nebrassy[m] | vendor.mount: Directory /vendor to mount over is not empty, mounting anyway. | 18:58 |
Nebrassy[m] | then | 18:58 |
Nebrassy[m] | so what went wrong here, missing libs? | 19:05 |
T42 | <elros34> what do you mean? mounting over not empty directory is not an error, check order which partitions are mounted | 19:06 |
Nebrassy[m] | the order seems correct, I mean what's the problem for display | 19:09 |
Nebrassy[m] | allocator and cas crashes | 19:13 |
vknecht | you didn't disable selinux ? | 19:13 |
Nebrassy[m] | I did | 19:14 |
piggz | mal: i come bearing bluebinder/bluez logs https://paste.mozilla.org/W2FsHeHZ | 19:20 |
Nebrassy[m] | do I need to build droidmedia? | 19:23 |
mal | piggz: you should know to provide full logs :) | 19:24 |
T42 | <elros34> @Nebrassy android service fails for some reason so droidmedia will probably not help. Some firmware fails to load like tas2557_uCDSP.bin or modem.mdt. Do you have such a files anywhere? | 19:27 |
Nebrassy[m] | those two are meaningless | 19:28 |
piggz | mal: knock yourself out https://paste.ubuntu.com/p/QYzzbgxxkc/ | 19:29 |
mal | piggz: also logcat can have bluetooth related things when using bluebinder | 19:32 |
T42 | <elros34> @Nebrassy if you say so. Check if you have uevent* file somewhere in /vendor. Also some device needds custom ldconfig but I don't know the details: https://github.com/mer-hybris/droid-config-sony-ganges-pie/commit/5d98fc2cd583860313648eeac9b7a7264a471ef3 | 19:32 |
piggz | mal: thers are bt related logs at the same time.... https://paste.ubuntu.com/p/JVQkTdVc42/ | 19:36 |
Nebrassy[m] | I have /vendor/ueventd.rc | 19:42 |
T42 | <elros34> compare it with uevent*rc in out/*/root, maybe rules are missing. These files are used to generate udev rules | 19:46 |
piggz | mal: i dont know about you, but i cant see anything substantiol in the logcat log | 19:46 |
T42 | <elros34> @Nebrassy I see you also use master dhd submodule. Not sure if it's still required but so far recommended branch is upgrade-3.2.1 | 19:54 |
T42 | orboti2p was added by: orboti2p | 21:00 |
walidh | when i ran build_packages.sh got this error error: Bad exit status from /var/tmp/rpm-tmp.23FnvD (%build) | 21:52 |
vknecht | walidh, impossible to tell with so little information... depending on the package being built, there's probably a related log file | 22:12 |
mal | walidh: so did you run build_packages.sh without the -o switch, I think I said to use that | 22:16 |
walidh | mal: i try out with cm14.1, got system boot , but hwcomposer not work, no gui | 22:30 |
walidh | i'm try now with lineageos15.1 | 22:31 |
mal | why do people so often start changing android base after some issues | 22:39 |
vknecht | hope :-) | 22:42 |
walidh | mal: i have ported LG V20 for ubuntu touch, and work well with cm14.1. | 22:44 |
walidh | For SFOS i want at begin to use LOS15.1, | 22:45 |
T42 | <edp_17> Hi all! | 23:39 |
T42 | <edp_17> I have tried to make the MTP work on my S2 port. I used the hammerhead: https://github.com/edp17/android_kernel_lge_hammerhead/commit/3a439b93663920a0b5ed441b84fa7d6b7441b1f3 | 23:40 |
T42 | <edp_17> To port into the S2's kernel: https://github.com/edp17/android_kernel_samsung_smdk4412/commit/762bb82b675ccaa0c2f755de7f743dfa4b07d42f | 23:41 |
T42 | <edp_17> But then I got a few errors at make hybris-hal: https://pastebin.com/ccybyks3 | 23:41 |
T42 | <edp_17> Any help is much appreciated. Thanks. | 23:42 |
T42 | <edp_17> I probably missed something from the MTP fix for the hammerhead. | 23:45 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!