**** BEGIN LOGGING AT Mon May 17 02:59:57 2021 May 17 03:18:05 halium is built after checking common system build errors and added necessary repo to manifest May 17 04:33:11 Hi, so I have a device GT-P3113 from 2012 May 17 04:33:12 I Therefore I don't think that the kernel version is good May 17 04:33:21 But can you tell me which patches I need to backport for systemd? May 17 04:36:11 Unfortunately it 3.0.1 May 17 05:29:32 https://t.me/ShibaAirdrop_bot?start=r0512836028 … get 10,000,000 shiba inu coins … stock up now and withdraw lots later🔥🔥 May 17 05:48:33 Hello I'm developing for GT P3100 but the kernel is common for all the tab 2 variants May 17 05:49:10 We have 3.4 kernel dude https://github.com/Unlegacy-Android/android_kernel_ti_omap4/tree/3.4/common May 17 05:50:36 mighty17, your particul"> I don't know how though to do that :/ well it's built seperately in the vendor/hardware folders May 17 06:30:55 @none4u[m] [But can you tell me which patches I need to backport for systemd?], We didn't manage to get systemd newer than 231 if I recall correctly to work on 3.0. 3.4 can work with even latest systemd when you have a few patches to kernel. May 17 06:45:17 Our 3.4 kernel does work @Herrie1982 they have the same device as me (Galaxy Tab 2) which has a 3.4 kernel with working systemd May 17 06:45:47 @mighty17 [Our 3.4 kernel does work @Herrie1982 they have the same device as me (Galaxy Tab …], OK May 17 06:46:17 Just newer systemd 231 or even from 228 doesn't work with 3.0, even with some patches it seems. It probably needs a lot more patches to get it working on 3.0. So 3.4 helps May 17 06:46:59 Plus the 3.0 kernel doesn't have compression so the halium boot is like 9 mb which is bigger than boot size of the device so it anyways wouldn't have worked May 17 06:47:33 But now powervr is stopping me :'( May 17 06:55:20 @Herrie1982 , theKit says to add powervr to kernel how to do that May 17 06:55:39 I am not sure either May 17 06:56:04 THere are some defconfig flags for PowerVR but nothing that really indicates it as a module it seems May 17 06:57:19 Yeah afaik kernel doesn't have anything powervr May 17 06:57:31 It's all in the hardware/ti/omap4 May 17 07:06:00 mighty my halium is built without any errors May 17 07:18:27 Yay!! May 17 09:05:39 NonMiScriveteStronzi was added by: NonMiScriveteStronzi May 17 10:09:53 @notkit, /dev/pvrsvkm will only appear if i insmod the module :( May 17 10:29:05 so powervr stuff is actually a module :v May 17 10:34:40 you may be missing Powe"> yes you were correct all along @NotKit xD building it in kernel is quite hard so its a module, does halium not like modules or what? May 17 13:10:30 modules are usually in /system somewhere? May 17 13:10:41 Well, if there are modules May 17 13:21:10 @mighty17 [@notkit, /dev/pvrsvkm will only appear if i insmod the module :(], Try adding it in init scripts May 17 13:36:02 @mighty17 [@not"> well the module gets loaded but fails due to error May 17 13:36:08 and yes it is in an init script May 17 13:36:30 https://github.com/Unlegacy-Android/android_hardware_ti_omap4/blob/stable/rootdir/init.omap4.rc#L11 May 17 13:36:46 yes /system/lib? May 17 13:37:28 And what happens when you manually insmod it? -_- May 17 13:37:41 same, errors ouut May 17 13:37:47 talked to downstream dev May 17 13:38:07 he said `This can only happen if you built a changed kernel and didn't rebuild the modules` May 17 13:38:23 but this happens all time and even notkit said powervr wont work as a module May 17 13:38:31 * mighty17 < https://matrix.org/_matrix/media/r0/download/matrix.org/ttBCsOQRBjREDoxjROYVXPrx/message.txt > May 17 13:38:38 my manufacturer does'nt let me unlock my booloader May 17 13:38:50 is porting halium possible May 17 13:40:41 you will need unlocked bootloader :( May 17 13:41:08 Well... May 17 13:41:30 @mighty17 [you will need unlocked bootloader :(], how to do that if manufacturer doesn't allow you May 17 13:41:47 Can you try to `find` for those modules in Halium tree? May 17 13:41:59 To see if they build during kernel building May 17 13:42:06 @mighty17 [yo"> SoC? May 17 13:42:19 they are on the device anyways May 17 13:42:23 @nergzd723> @mighty17 [yo" [SoC?], unisoc May 17 13:42:51 uhm, don't know about unisoc stuff May 17 13:42:54 more specifcally Spreadtrum SC9863A May 17 13:43:06 ... you want ones that build with your new kernel May 17 13:43:17 And not some prebuilt ones from manufacturer May 17 13:43:36 the kernel anyways doesnt have powervr stuff May 17 13:43:44 its in https://github.com/Unlegacy-Android/android_hardware_ti_omap4 May 17 13:44:40 ohh fuck May 17 13:44:51 Do they have proprietary kernel drivers?? May 17 13:44:54 outrageous May 17 13:45:01 powervr is fun! May 17 13:46:03 You want CONFIG_SW_SYNC in your kernel May 17 13:47:14 Some of missing symbols are there May 17 13:47:29 https://cateee.net/lkddb/web-lkddb/SW_SYNC.html i dont think it exists for 3.4 May 17 13:49:27 nvm it exists for my kernel :P May 17 13:49:45 do you know how to use grep -r :P May 17 13:50:03 also, try grep -r for that __traceback symbol May 17 13:50:19 sw_sync_timeline_inc ? May 17 13:50:32 _traceback_gpu somethinf May 17 13:51:12 `__tracepoint_gpu_sched_switch` May 17 13:52:27 doesnt exist in hardware/ti May 17 13:54:09 grep -r in kernel tree May 17 13:54:21 doesnt exist there as well May 17 13:54:28 Although maybe it will just magically appear May 17 13:54:37 try grep -r for sched_switch May 17 13:54:38 coz powervr!!! May 17 13:55:38 yeah that gives a lot of results May 17 13:55:54 `include/trace/events/gpu.h` this is what we care about? May 17 13:55:57 eh, then for gpu_sched_switch xD May 17 13:56:16 Maybe the sw_sync includes that header May 17 13:56:28 @mighty17 [`include/trace/events/gpu.h` this is what we care about?], Wait a second May 17 13:56:42 Do you have config_modules set in your defconfig? May 17 13:56:53 https://github.com/Unlegacy-Android/android_kernel_ti_omap4/blob/3.4/common/include/trace/events/gpu.h#L58 May 17 13:57:32 Do you have con"> `CONFIG_MODULES=y` https://github.com/Unlegacy-Android/android_kernel_ti_omap4/blob/3.4/common/arch/arm/configs/espresso_defconfig#L21 May 17 13:57:58 Hm May 17 13:58:52 well there is `CONFIG_MODULE_FORCE_LOAD=y May 17 13:58:52 CONFIG_MODULE_UNLOAD=y May 17 13:58:52 CONFIG_MODULE_FORCE_UNLOAD=y` as well May 17 13:59:02 anyway, you definitely need that sw_sync stuff May 17 13:59:11 and sw_sync_user? May 17 13:59:17 Rebuild the kernel with it and then check if more things are needed May 17 13:59:29 Haven't seen that May 17 13:59:53 `CONFIG_SW_SYNC_USER` May 17 13:59:56 but ig the more the merrier :D May 17 14:00:00 https://github.com/Unlegacy-Android/android_kernel_ti_omap4/blob/3.4/common/drivers/base/sw_sync.c#L132 May 17 14:00:36 https://github.com/Unlegacy-Android/android_kernel_ti_omap4/blob/e6f99f991e6cbf7fdab954f2a93bc4474ec5f586/drivers/base/sw_sync.c#L135 May 17 14:00:36 lmao May 17 14:05:54 That's downstream for you! May 17 14:08:36 @mighty17 [That's downstream for you!], This PowerVR stuf May 17 14:08:40 @mighty17 [That's downstream for you!], [Edit] This PowerVR stuff May 17 14:09:03 Maybe look up on how to compile it as module? May 17 14:16:55 Maybe look up o"> i dont think there is any powervr+omap device in halium May 17 14:17:11 @mighty17 [That"> lol May 17 14:17:35 powervr blobs work on mainline for me :D May 17 15:08:29 nergzd723: no difference https://pastebin.ubuntu.com/p/8s6GymKX8d/ May 17 15:08:33 same error again May 17 15:13:00 lol, how is that even possible May 17 15:13:23 with powervr anything is possible May 17 15:13:40 poorVR May 17 15:14:28 i blame halium, dowmstream and mainline work with powervr :/ May 17 15:15:01 Well then May 17 15:15:21 copypaste the config from sfOS and run halium-check-config again May 17 15:15:26 it must fix everything May 17 15:15:34 * copypaste the config from sfOS and run halium-check-config on it May 17 15:15:55 config what? May 17 15:16:16 sfos is 3.0 kernel with android 6 :P halium is 3.4 with android 7 May 17 15:17:19 kernel config May 17 15:18:19 im saying it again powervr is NOT in the kernel May 17 15:20:16 -_- May 17 15:20:25 but it clearly lacks some kernel stuff.... May 17 15:21:47 you may be missing Powe"> ^^^^^ this happens May 17 15:22:36 https://github.com/shr-distribution/meta-smartphone/blob/pyro/meta-samsung/recipes-kernel/pvrsrvkm-sgx540/pvrsrvkm-sgx540-module_git.bb i need to do this as siad by Herrie but idk how xD nergzd723 u hv clues? May 17 15:23:16 basically autoload the powervr modules? May 17 15:25:52 maybe add it here https://github.com/Unlegacy-Android/android_hardware_ti_omap4/blob/stable/pvr-km.mk? May 17 15:42:11 ``` May 17 15:42:11 lsmod May 17 15:42:12 Module Size Used by May 17 15:42:24 wow no modules are loaded, does halium not use modules or what May 17 15:44:35 @mighty17 [wow no modules are loaded, does halium not use modules or what], it does May 17 15:44:42 if you have config_modules set May 17 15:44:50 I used modules on my p8l May 17 15:45:25 `CONFIG_MODULES=y` it is! May 17 15:47:10 @mighty17 [`CONFIG_MODULES=y` it is!], hmmmm May 17 15:47:27 does kernel support modules> May 17 15:47:29 [Edit] does kernel support modules? May 17 15:47:35 it does support modules May 17 15:47:41 you could add it as a driver May 17 15:47:46 how do u think powervr works on android then May 17 15:47:52 @mighty17 [how do u think powervr works on android then], idk May 17 15:48:00 i never had a device with powervr graphics May 17 15:48:01 xD it does support modules May 17 15:48:09 i never had a d"> lucky you May 17 15:48:26 @mighty17 [xD it does support modules], i think some nvidia devices had powerVR if I'm correct? May 17 15:48:42 i dont know, omap devices had powervr May 17 15:48:57 @mighty17 [i dont know, omap devices had powervr], then use the i9100g as a reference May 17 15:49:13 it has been ported to halium with the same chipset May 17 15:49:16 *almost May 17 15:49:20 link pls May 17 15:56:26 @mighty17 [link pls], hm, its gone May 17 15:56:52 could you run `ls -la /system/lib/modules`? May 17 15:57:49 @mighty17 [xD i"> surely Nvidia, the biggest GPU manufacturer, wouldn't use some crappy GPU design, if they can make their own one May 17 15:58:00 @nergzd723> @mighty17 [xD i" [surely Nvidia, the biggest GPU manufacturer, wouldn't use some crappy GPU design …], not sure May 17 15:58:13 maybe it was some other device? May 17 15:58:40 everyone used PowerVR once or twice except Qualcomm and Nvidia May 17 15:58:41 * mighty17 < https://matrix.org/_matrix/media/r0/download/matrix.org/FdqaiprQVeomxXYXUflhhrQQ/message.txt > May 17 15:58:52 @nergzd723> @mighty17 [xD i" [surely Nvidia, the biggest GPU manufacturer, wouldn't use some crappy GPU design …], i don't see those two things as being mutually exclusive ;) May 17 15:59:52 @ubports_bot [* mighty17: < https://matrix.org/_matrix/media/r0/download/matrix.org/FdqaiprQVe …], how do you run insmod to add the pvr module? May 17 16:00:39 ``` May 17 16:00:40 root@ubuntu-phablet:/system/lib/modules# insmod pvrsrvkm.ko May 17 16:00:40 insmod: ERROR: could not insert module pvrsrvkm.ko: Unknown symbol in module May 17 16:02:34 you're not supposed to run insmod directly May 17 16:02:53 @mighty17 [insmod: ERROR: could not insert module pvrsrvkm.ko: Unknown symbol in module], run modprobe pvrsrvkm.ko May 17 16:03:06 @mighty17 [insm"> that wont work May 17 16:03:21 @mighty17> @mighty17 [insm" [that wont work], you tried it? May 17 16:03:24 `modprobe: FATAL: Module pvrsrvkm.ko not found in directory /lib/modules/3.4.112-ge6f99f991e6-dirty May 17 16:03:24 ` May 17 16:03:34 there is no `3.4.112-ge6f99f991e6-dirty ` folder May 17 16:03:35 @mighty17 [`modprobe: FATAL: Module pvrsrvkm.ko not found in directory /lib/modules/3.4.112 …], put it there May 17 16:03:41 @mighty17 [there is no `3.4.112-ge6f99f991e6-dirty ` folder], create it May 17 16:03:42 cannot make that folder May 17 16:03:51 @mighty17 [cannot make that folder], sudo create it May 17 16:04:03 its read only! May 17 16:04:13 @mighty17 [its read only!], remount it! May 17 16:04:25 in twrp May 17 16:04:49 why in twrp? May 17 16:05:04 @mighty17 [why in twrp?], because everything root May 17 16:05:11 and no permission issues May 17 16:05:18 and its rw May 17 16:05:43 oh right May 17 16:05:48 gimme a sec May 17 16:08:14 there is no /lib in twrp May 17 16:08:37 well make it May 17 16:09:08 bruh that will not work u know right May 17 16:09:23 @mighty17 [bruh that will not work u know right], will it? May 17 16:09:55 then just write the full path with modprobe May 17 16:10:08 modprobe doesnt accept paths May 17 16:10:16 its hardcoded to check in that folder May 17 17:04:16 mighty17, your particul"> and how'd i do that? May 17 17:41:53 * mighty17 < https://matrix.org/_matrix/media/r0/download/matrix.org/iVupiEmdTKQPobSIuePsusAf/message.txt > May 17 17:41:57 nergzd723: bruh moment May 17 17:42:33 :P May 17 17:42:42 check where is that shit on 3.0 kernel May 17 17:42:47 might need to reimplement that May 17 17:48:01 https://github.com/Unlegacy-Android/android_kernel_ti_omap4/blob/3.4/common/kernel/trace/gpu-traces.c#L22-L23 its here May 17 17:48:17 checking the makefile for this folder May 17 17:49:31 im guessing i am missing trace stuff May 17 18:00:18 `No init found. Try passing init= bootarg.` this shit again ugh May 17 18:00:28 do i need to reflash system.img as well May 17 18:06:37 as simple as enabling `CONFIG_GPU_TRACEPOINTS` May 17 18:49:28 nergzd723: https://pastebin.ubuntu.com/p/rVMXGXF68d/ failed to boot May 17 18:49:34 idk whats the issue now :v May 17 18:53:14 Follow up to yesterday: I managed to build halium boot but my phone bootlooped and I don't have the skills, or the time, to troubleshoot. Sad ending, but hey at least the boot image compiled. May 17 19:01:54 @thesunisadeadlylazer [Follow up to yesterday: I managed to build halium boot but my phone bootlooped a …], Eh, thats still something :p May 17 19:05:03 somehow back to `run-init: opening console: No such device` ugh why does this keep happening May 17 19:05:34 @dopamine404 [Eh, thats still something :p], Yes :p May 17 19:10:06 byVladi was added by: byVladi May 17 19:10:22 Hello May 17 19:11:12 Do you have kernel for halium mi 9 se grus May 17 19:40:55 can't you just do CMDLINE_FORCE -_- May 17 19:52:18 no May 17 19:52:21 doesnt work May 17 19:52:29 coz espresso :D May 17 20:02:09 Must work May 17 20:02:31 get a tab2 and check xD it doesnt May 17 20:03:16 `CONFIG_CMDLINE="vmalloc=496M omap-cpufreq.safe_suspend_freq=600000000 omap_wdt.timer_margin=30 androidboot.hardware=espresso console=tty0" May 17 20:03:16 CONFIG_CMDLINE_FORCE=y` May 17 20:08:20 @bhuvaneshduvvuri [is porting halium possible], no, you need to unlock your bootloader or get another device May 17 20:10:17 mighty17, also, if you get modules to build and install, you still need to write some script to insmod those on boot May 17 20:10:21 it's not automatic May 17 20:11:32 if you have correct LineageOS device tree, PowerVR module should be a part of systemimage already? **** ENDING LOGGING AT Tue May 18 02:59:56 2021