Saturday, 2024-01-27

genericv2purged 'out/' and trying again.00:00
genericv2Same error again on a fully clean build.00:26
genericv2But i'll continue tomorrow. I am logging out now, thanks for helping T42_  mal00:27
genericv2hi again, i'll continue now. Any idea to previous initramfs generation error?11:07
genericv2Anything to check on trees etc.11:08
T42_<elros34> best way would be if you show whole make output from yesterday after cleaning build output but if you don't have it anymore then just what you have.11:11
genericv2No problem i can build again.11:12
genericv2I'll redirect the entire output to a file11:12
T42_<elros34> show what you have now first11:12
genericv2Not the entire output but must be enough.11:18
maljust to be sure, which branch of hybris-boot are you using?11:25
genericv2and i am using lineage-20 trees for my phone.11:27
malI meant the repo in hybris/hybris-boot11:30
genericv2I don't know if i missed a part, hybris/hybris-boot doesn't have a branch but repo command is clones android13 branch i think.11:33
genericv2<project path="hybris/hybris-boot" name="mer-hybris/hybris-boot" revision="android13" />11:33
genericv2HABUILD_SDK [sagit] twoxa@suse:~/android/hybris/hybris-boot$ git branch => * (no branch)11:34
T42_<elros34> git branch -a?11:35
genericv2  remotes/github/android1311:36
genericv2  remotes/m/hybris-20.0 -> github/android1311:36
T42_<elros34> so there is no out/target/product/sagit/obj/ROOT/hybris-boot_intermediates/boot-initramfs.gz?11:38
malcould cpio be missing somehow?11:39
genericv2T42_ yeah, it does not exist.11:40
T42_<elros34> in HABUILD not in platform sdk11:40
genericv2cpio is installed, checked again now.11:40
genericv2In habuild.11:40
genericv2HABUILD_SDK [sagit] twoxa@suse:~/android$ cpio => cpio: You must specify one of -oipt options. Try 'cpio --help' or 'cpio --usage' for more information.11:41
T42_<elros34> please show git diff in hybris-boot11:43
malwondering which compression format that uses11:45
genericv2did 'git diff | tee gitdiff'11:46
genericv2And this is the full log of a clean build:
genericv2mal, where can i check the compression format11:51
T42_<elros34> you could search for BOARD_RAMDISK_USE in device/11:52
genericv2Nope, nothing related to it on my trees. It using the default probably.11:54
malI'll test a bit, just a moment11:55
genericv2Okay i am waiting. Thank you.11:56
malit's possible that lz4 support patch could be broken, you could try to revert that in hybris-boot11:57
malthe last commit in that repo11:57
malmake sure you don't lose your fixup changes when doing that11:58
genericv2Reverted that lz4 patch, trying again now.12:01
malI can reproduce that issue, trying to fix, it's the lz4 support patch causing the issues12:02
genericv2Yeah reverting that commit fixed the issue12:03
genericv2HABUILD_SDK [sagit] twoxa@suse:~$ ls android/out/target/product/sagit/obj/ROOT/hybris-recovery_intermediates/12:03
genericv2initramfs  recovery-initramfs.gz12:03
genericv2Thank you very much for helping me :)12:03
genericv2#### build completed successfully (07:05 (mm:ss)) ####12:08
malsomething else to note, when using the android13 branch of droid-configs-device submodule it has issues unless you make some changes to it or build new version of mce12:17
malI think I found a fix to the lz4 support issue, testing with both kind of setups now13:02
genericv2Hi again, now i'll work on the kernel but i have a question. Android App Support is paid in official Sony devices. Is my unofficial build going to have Android app support? Or i need pay for it?16:11
T42_<elros34> neither you can try to use free alternative waydroid
genericv2So i can't use sailfishos's android app implemention :( Thats bad. Actually i only use telegram as a messaging app and no other special android apps but that android api thingy was cool. I'll use waydroid then.16:21
T42_<elros34> there are many native telegram apps abandoned and maintained16:22
genericv2Yeah i saw one of them. And i liked it, i love sfos design. I'll use one of the telegram clients and waydroid for banking apps etc, if i succeed porting it of course­čśů I'll continue now.16:28
genericv2Stuck again :( Kernel complication gives an error about this file:
genericv2I can fix the complication error by editing lines 118, 119 and 120 but it can't boot recovery. When CONFIG_VT is enabled, phone reboots immediately. And when it's disabled, the phone waits 30~ seconds and reboots.18:32
genericv2Here is the console output with original dummycon.c + Enabled CONFIG_VT: I asked so many questions, sorry if i am annoying.18:32
T42_<elros34> you are supposed to have config_cummy disabled then I think you shouldnt have any errors in kernel about that18:42
deathmistgenericv2: qcom kernels (specifically older ones) are known to be broken with VT=y, you'll have to revert some commits in your kernel source similar to
T42_<elros34> lineage 15 or something like that but not 2018:44
T42_<elros34> oh looks like it really might have this commit
genericv2Got it, i'll try older kernels.18:45
deathmistyou need to revert some commits18:46
deathmistwhich break the VT driver18:46
genericv2Also CONFIG_DUMMY is set to 'n'18:46
genericv2ah saw it now, okay18:46
deathmistor are you porting on an older hybris version? I've not been following the discussion really18:46
genericv2Nope i am porteeing on hybris 2018:46
T42_<elros34> so to be clear do you have any kernel compilation issues with config_vt=y config_dummy=n?18:47
genericv2Yes, i have. I am these ( errors with vt=y and dummy=n18:48
genericv2What did i just wrote18:49
T42_<elros34> ok so lets not mix different issues for now18:49
genericv2Yeah, now reverting commits. Need a moment.18:50
T42_<elros34> no18:50
T42_<elros34> these commits have nothing to your issue18:50
genericv2what i need to do then now.18:54
T42_<elros34> can you show your git diff of your defconfig18:55
T42_<elros34> these lines are from 2.6 kernel so looks like somebody forget to update something:
genericv2Please wait a minute, i'll send it19:00
T42_<elros34> I think it should be safe to modify these 3 functions like here:
genericv2lets try19:07
T42_<elros34> did you really only make these few changes? mer-kernel-check doesn't complain about anything else? Do you have CONFIG_AUTOFS4_FS set in .config?19:09
T42_<elros34> I do not like this minimized defconfigs, you never really know what is really set19:11
genericv2I normally checked all warning too, started clean after seeing it not booting. But these are the only errors i get19:11
T42_<elros34> not all warnings are important and some are useless19:12
genericv2Yeah i know. Lot of them are just about NFS19:12
genericv2Build completed with no errors after dummycon.c modification19:14
T42_<elros34> if kernel builds fine then reenable config_vt temporary, build and flash hybris-boot19:14
T42_<elros34> sorry disable not reenable19:14
T42_<elros34> It is so old issue I didn't expect it in lineage 2019:14
T42_<elros34> this kernel is probably not in line with common lineage changes19:15
genericv2Built again with VT=n (and DUMMY=n). Will flash now19:20
genericv2Didint able to boot to recovery again, but it didin't crash.19:21
genericv2VT=y makes it crash immediately19:22
T42_<elros34> follow host dmesg, see whether it reboots or stays on, you will not see anything on screen yet19:22
genericv2It's not reconnecting to usb while it's stuck at mi logo19:26
T42_<elros34> what about all usb stuff explained in hadk? did you check for common boat loader messages and telnet?19:28
genericv2Just asking to be sure, hybris recovery must boot when there is nothing else installed about sfos/hybris right?19:30
T42_<elros34> hybris-boot/recover both will boot without sfos rootfs and both with show absolutely nothing on screen19:31
genericv2Okay i am not doing something wrong then.19:32
genericv2Can't telnet as there is no usb connection19:33
genericv2Not sure where to check for bootloader messages. I'll read documention.19:33
genericv2may /proc/last_kmsg help?19:34
T42_<elros34> it may but focus on basics so hadk 9.2 then you run dmesg -w, flash hybris-boot.img and power on /connect device19:35
malcheck which usb config options you have enabled in defconfig19:35
T42_<elros34> so far we don't even know whether you have any hybris-boot messages in dmesg or not and this is always first step19:36
malyeah, good point19:36
genericv2I always tried recovery. I'll backup my current boot partiton and work with hybris-boot.img now.19:37
genericv2mal: i'll check now19:37
genericv2 here is everything about usb in defconfig19:39
genericv2Yeah, there simply no sign of life in dmesg19:42
T42_<elros34> device reboots or stays on?19:43
genericv2It stays up for 30-60 seconds and reboots19:44
genericv2(VT=y makes it reboot instantly as i said)19:44
genericv2there is some interesting logs on lsusb -v by the way19:44
T42_<elros34> so 30 or 60s? Have you checkedd for /data/.stowaways/sailfishos/init.log in recovery19:45
genericv2from 30 to 60, changes time by time19:45
T42_<elros34> what about first boot after flashing hybris-boot.img because this is most important19:45
T42_<elros34> What about CONFIG_AUTOFS4_FS I asked previously?19:46
genericv2I am not sure if it can write files to /data because the storage is encrypted right now.19:48
genericv2i'll flash hybris-boot and count how many seconds it takes to reboot nowe19:48
T42_<elros34> didn't you read hadk-hot, you must remove data encryption19:49
genericv2CONFIG_AUTOFS4_FS is set to 'y'19:49
malalso userdata has to be ext4, afaik19:49
T42_<elros34> no, I do not think so this was ever an issue19:50
genericv2Oops, i missed that probably. This is my dailydriver so didin't wiped userdata before starting to port. I'll backup everything and wipe data.19:50
T42_<elros34> you may take care of this config_vt and kernel changes now too to ease debugging or make small change in hybris-boot script instead19:51
genericv2so no need to wipe data for now? Would be great because i was planning to wipe it after making some progress19:53
T42_<elros34> it can ease debugging but its not necessary to get initramfs working, you may try to see if you have usb configs mal was talking about
malyeah, if device uses gsi usb then it needs those for sure19:55
genericv2Oh okay then. If we are unable to make initramfs work, i'll wipe it.19:55
genericv2Added those lines to kernel. Complication gave a lot of errors. This kernel is a mess19:58
genericv2kernel/xiaomi/msm8998/drivers/usb/gadget/function/rndis.c file is broken. Another linux 2.x code probably. oof20:11
T42_<elros34> you can you show full error?20:12
T42_<elros34> yeah this common misleading error, I think disabling gsi should help :
genericv2Yeah disabling GSI helped with that error. Now another one came:
T42_<elros34> trey without that CONFIG_USB_CONFIGFS_RMNET_BAM?20:29
genericv2[11708.566594] usb 1-12: USB disconnect, device number 3520:34
genericv2[11717.547838] usb 1-12: new high-speed USB device number 36 using xhci_hcd20:34
genericv2[11717.694793] usb 1-12: New USB device found, idVendor=18d1, idProduct=d001, bcdDevice= 4.0420:34
genericv2[11717.694798] usb 1-12: New USB device strings: Mfr=1, Product=2, SerialNumber=320:34
genericv2[11717.694799] usb 1-12: Product: Refusing20:34
genericv2[11717.694800] usb 1-12: Manufacturer: Mer Boat Loader20:34
genericv2[11717.694801] usb 1-12: SerialNumber: Mer20:34
genericv2It's alive :)20:34
genericv2i'll try to telnet to it, seems like its not rebooting20:34
genericv2Yeah it's not rebooting. We made progress20:36
genericv2SerialNumber: Mer Debug telnet on port 23 on usb0 - also running udhcpd20:38
T42_<elros34> so did you managed to telnet?20:39
genericv2Telnet is getting stuck at "Trying" I am trying to fix it.20:39
T42_<elros34> do you use correct 23 port?20:40
genericv2Yeah i am using port 23.20:40
genericv2same at both my host suse and build env ubuntu20:42
T42_<elros34> follow hadk-hot tips for telnet issues20:43
genericv2i hope i don't need to force reboot the phone somehow, my power button is broken20:45
T42_<elros34> ehh20:46
genericv2Command ip link is not detecting my phone20:49
genericv2this is the problem20:49
T42_<elros34> whats the output of ifconfig -a20:50
malis the ip set for the usb interface20:50
genericv2Nope, no 'usb0' in ifconfig aswell20:51
genericv2It sees the thing as a "Portable media player", my favorite bootloader20:51
malsometimes the interface is not usb020:51
T42_<elros34> then device is not powered anymore20:51
T42_<elros34> connect/disconnnect phone and see what interface appears if ifconfig20:52
genericv2It must be alive. Disconnecting and reconnecting updates dmesg. And nothing on ifconfig20:52
T42_<elros34> even with -a argument, really nothing?20:53
genericv2Yeah, a big nothing except my network adapter20:54
T42_<elros34> do you still get  New USB device found on every connection?20:54
genericv2My laptop found it20:54
genericv2The phone is connected as a network interface now20:54
genericv2okay i am in20:55
genericv2i can telnet to phone with my laptop20:55
genericv2KDE or Suse is did something probably20:56
T42_<elros34> check if you can mount data partition manually without removing encryption20:57
genericv2Data is already mounted21:01
genericv2'/dev/sda17 on /data type ext4'21:01
genericv2i'll can continue porting now, right?21:03
T42_<elros34> you need to fix config_vt issue21:04
genericv2ah true, just forget about that21:05
genericv2What i need to do now, i forget everything while trying to boot into mer21:06
genericv2Applied  patches in ubports documention21:30
genericv2Still crashes with VT=y21:30
genericv2One of the patched failed tho21:30
genericv2Applied failing patch by-hand. Everything must be okay this time. Starting build again.21:44
genericv2Complication error. Time to give up. Thanks everyone21:48
T42_<b100dian> When you say complication instead of compiling you sound less than your potential:p21:52
genericv2haha xD, i just learnt english by myself. I am mixing words sometimes.21:54
genericv2i need to logoff now, Unfortunately i am delaying sfos for now. I want it so can't even give up.21:56

Generated by 2.17.1 by Marius Gedminas - find it at!