| mighty17 | <mal "when does that happen"> When I run make -j4 command to make the images | 04:02 |
|---|---|---|
| mighty17 | mal | 04:02 |
| mighty17 | <deathmist "mighty17: I mean it probably hel"> It just says error6 and then unable to install zip :( | 04:03 |
| mighty17 | Also hi deathmist! I didn't know u were here :D | 04:03 |
| mighty17 | > <@freenode_mal:matrix.org> when does that happen | 04:25 |
| mighty17 | * When I run make -j$(nproc --all) hybris-hal droidmedia command to make the images | 04:25 |
| mighty17 | <deathmist "mighty17: I mean it probably hel"> command? lol i flashed from twrp :/ | 04:37 |
| mighty17 | <mighty17 "command? lol i flashed from twrp"> even adb sideload gives error6 :/ | 05:42 |
| mighty17 | idk what i did wrong it used to work before i got as far to able to telnet | 05:43 |
| mighty17 | https://forum.xda-developers.com/t/sfos-dev-only-sailfish-os-for-galaxy-tab-2-3g.3429786 we also have working sfos although old but i dont know what im doing wrong 😭 | 05:46 |
| mal | mighty17: can you show more output when that failure happens | 09:40 |
| mighty17 | <mighty17 "now any idea for this https://pa"> mal: | 09:48 |
| mighty17 | see the pastbin has the log | 09:49 |
| mal | mighty17: run "sudo zypper in grep -busybox-symlinks-grep" | 10:02 |
| mighty17 | mal: i fixed it by putting that script manually (edited to remove line 36) | 10:04 |
| mighty17 | is that not correct? | 10:04 |
| mighty17 | <mighty17 "https://forum.xda-developers.com"> another question can i update sfos from here? (it is ancient and has many issues though) | 10:06 |
| mal | probably easier to use the repos used in that only as an example and start for the beginning | 10:07 |
| mighty17 | I did everything from scratch like 2 times, firstly I got error of Mount so I redid everything with changed fstab and fixup-mount points now I get error 6 🙁 | 10:12 |
| mighty17 | okay guys... i have a new problem | 10:45 |
| mighty17 | it seems to have booted and tapping on screen shows backlight on but there is no ui or anything | 10:45 |
| mighty17 | but i cant get into ssh or telnet or anything https://pastebin.com/PUTbASCL | 10:47 |
| T42 | <edp_17> mighty17: Try to pull up the network manually. Use this: https://docs.halium.org/en/latest/porting/debug-build/early-init.html | 11:02 |
| mighty17 | okay any idea what can be wrong? | 11:03 |
| mighty17 | i used old fstab (of cm12.1) | 11:03 |
| T42 | <edp_17> Probably there is a problem with the mount points, I guess /system is not mounted. But without seeing the device, this is just a guess. | 11:05 |
| T42 | <edp_17> That's why I suggested to bring up the network manually and then you can check what's on the device. | 11:05 |
| mighty17 | okay im just doing that | 11:06 |
| mighty17 | i rebooted to twrp which seems to have removed los/sailfishos | 11:06 |
| T42 | <edp_17> Have you tried telnet? | 11:06 |
| mighty17 | nope i dont know what ip to put | 11:06 |
| T42 | <edp_17> telnet 192.168.2.15 2323 | 11:07 |
| mighty17 | 2323? or just 23? | 11:07 |
| T42 | <edp_17> 2323 | 11:07 |
| mighty17 | okay | 11:08 |
| mighty17 | gimme sometime as installing sfos takes some minutes | 11:09 |
| T42 | <edp_17> mighty17: a little extract from that site I gave you: https://paste.ubuntu.com/p/C5S6sRt2Gc/ | 11:10 |
| mighty17 | thanks a lot!! i will try telnet first | 11:11 |
| T42 | <edp_17> (This is how I brought up the network manually when the device wasn't reachable via ssh.) | 11:11 |
| mighty17 | edp_17 telnet worked | 11:19 |
| mighty17 | https://paste.ubuntu.com/p/cg5mr22G5p/ | 11:19 |
| T42 | <edp_17> What does the mount command say? | 11:23 |
| T42 | <edp_17> and what does this? cat /lib/systemd/system/system.mount | 11:24 |
| mighty17 | <T42 "<edp_17> What does the mount com"> nothing | 11:25 |
| T42 | <edp_17> and thsese: | 11:25 |
| T42 | <edp_17> cat /lib/systemd/system/efs.mount | 11:25 |
| T42 | <edp_17> cat /lib/systemd/system/preload.mount | 11:25 |
| mighty17 | okay let me try | 11:25 |
| mighty17 | https://paste.ubuntu.com/p/F4D3YYCKYb/ | 11:26 |
| mighty17 | @edp_17 | 11:26 |
| mighty17 | > <@freenode_T42:matrix.org> <edp_17> What does the mount command say? | 11:29 |
| mighty17 | * see this https://paste.ubuntu.com/p/RdwWg7Sn7m/ | 11:29 |
| T42 | <edp_17> Okay, so you have /system mounted. What's in here: cat /var/lib/environment/compositor/droid-hal-device.conf | 11:33 |
| * mighty17 sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/GsImQJOAmSrshvOFqIPlRJJp/message.txt > | 11:33 | |
| T42 | <edp_17> Change this: EGL_PLATFORM=hwcomposer to EGL_PLATFORM=fbdev | 11:35 |
| mighty17 | how do i change that? | 11:35 |
| mighty17 | i have to remake sfos then? | 11:35 |
| T42 | <edp_17> vi /var/lib/environment/compositor/droid-hal-device.conf | 11:36 |
| T42 | <edp_17> then press SHIFT+I | 11:36 |
| mighty17 | okk | 11:37 |
| T42 | <edp_17> Then with cursors navigate to that line and change, then press ESC, then press these thre characters :wq | 11:37 |
| T42 | <edp_17> *three | 11:37 |
| mighty17 | ohkk | 11:37 |
| T42 | <edp_17> But I think the problem is somewher else as the device doesn't get to the stage where it gets an IP address. | 11:37 |
| mighty17 | yes it changed and saved | 11:38 |
| T42 | <edp_17> Reboot. | 11:38 |
| mighty17 | power button right or is there some command | 11:38 |
| T42 | <edp_17> you can use the command reboot or the power button. :) | 11:38 |
| mighty17 | cool | 11:39 |
| T42 | <edp_17> How did you install the kernel? Did you used the hybris-boot.img or something else? | 11:40 |
| mighty17 | i followed the manual | 11:42 |
| mighty17 | <T42 "<edp_17> you can use the command"> still same thing | 11:43 |
| T42 | <edp_17> Did you applied the selinux=0 in BOARD_KERNEL_CMDLINE? | 11:43 |
| mighty17 | let me see | 11:43 |
| mighty17 | https://github.com/LineageOS/android_kernel_samsung_espresso10 this is my kernel | 11:43 |
| T42 | <edp_17> Plus you can check the following: | 11:43 |
| T42 | <edp_17> zcat /proc/config.gz | grep CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE | 11:43 |
| T42 | <edp_17> zcat /proc/config.gz | grep CONFIG_SECURITY_SELINUX_BOOTPARAM | 11:43 |
| mighty17 | <T42 "<edp_17> zcat /proc/config.gz | "> it is set to 0 | 11:43 |
| mighty17 | <T42 "<edp_17> zcat /proc/config.gz | "> it is =y | 11:44 |
| T42 | <edp_17> The BOARD_KERNEL_CMDLINE is in the device tree not in the kernel. | 11:44 |
| mighty17 | in boardconfig? | 11:44 |
| T42 | <edp_17> Okay, then those two flags are fine in the kernel. | 11:44 |
| mighty17 | <T42 "<edp_17> The BOARD_KERNEL_CMDLIN"> BOARD_KERNEL_CMDLINE := androidboot.hardware=espresso | 11:45 |
| mighty17 | <T42 "<edp_17> Did you applied the sel"> nothing like that is said in the manual | 11:46 |
| T42 | <edp_17> Double check that: Section 9.3.1 Bootloops | 11:49 |
| T42 | <edp_17> But that is not the case for you because your device is not bootlooping. | 11:49 |
| mighty17 | exactly | 11:49 |
| T42 | <edp_17> Okay what these do say: | 11:50 |
| T42 | <edp_17> cat /lib/systemd/system/efs.mount | 11:50 |
| T42 | <edp_17> cat /lib/systemd/system/preload.mount | 11:50 |
| T42 | <edp_17> cat /lib/systemd/system/system.mount | 11:50 |
| mighty17 | okay | 11:51 |
| mighty17 | https://pastebin.ubuntu.com/p/x9x2tDmYZ9/ | 11:52 |
| mighty17 | `cat: can't open '/lib/systemd/system/preload.mount': No such file or directory` | 11:53 |
| T42 | <edp_17> These also look fine. (I am not sure that preload.mount still exists.) | 11:54 |
| mighty17 | my guess would be that i used cm12.1 fstab but los14.1 as the base rom | 11:55 |
| mighty17 | as when i used los14.1's fstab the /system location was wrong | 11:55 |
| mighty17 | or the fixup-mount points was wrong | 11:56 |
| T42 | <edp_17> I see. Probably that's the problem. You need to fix /system location in the 14.1 base. | 11:57 |
| mighty17 | <T42 "<elros34> what? no you seems to "> should i try this | 11:57 |
| mighty17 | <T42 "<edp_17> I see. Probably that's "> or fix fixup-mountpoints? | 11:58 |
| T42 | <edp_17> Yes/ What is in the fuxup-mountpoints? | 11:58 |
| * mighty17 sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/wieIUYOPuibfLhiusOcohZQw/message.txt > | 11:59 | |
| mighty17 | https://github.com/LineageOS/android_device_samsung_espressowifi/blob/cm-14.1/rootdir/fstab.espresso this is the fstab | 12:01 |
| mighty17 | so i followed what elros34 said and used los14.1 fstab with the changes fixup-mountpoints | 12:08 |
| mighty17 | ``` | 12:08 |
| mighty17 | hybris/hybris-boot/Android.mk:71: ********************* /boot appears to live on /dev/block/mmcblk0p5 /dev/block/platform/omap_hsmmc.1/by-name/KERNEL | 12:08 |
| mighty17 | hybris/hybris-boot/Android.mk:72: ********************* /data appears to live on /dev/block/platform/omap_hsmmc.1/by-name/DATAFS | 12:08 |
| mighty17 | is this correct? | 12:08 |
| T42 | <edp_17> This is what I used for my i9100 (galaxy S2): https://pastebin.ubuntu.com/p/cjf4GSRhNb/ | 12:08 |
| T42 | <elros34> first one looks wrong and and is probably reason for sed failure later | 12:12 |
| T42 | <edp_17> Have you checked the mount points on android before you started the porting? (HADK Section 5.3 Configure Mountpoint Information) | 12:12 |
| T42 | <elros34> you need to remove extra /boot entry from fstan line 26 then it should be fine | 12:15 |
| T42 | <elros34> I guess that will also fix issue you opened in mer-hybris/hybris-boot | 12:15 |
| T42 | <elros34> Probable there should same safety check for boot as for data partition: ifneq ($(words $(HYBRIS_DATA_PART)),1) | 12:19 |
| mighty17 | <T42 "<elros34> first one looks wrong "> To me? | 12:21 |
| T42 | <elros34> yes | 12:22 |
| mighty17 | <T42 "<elros34> you need to remove ext"> Yes I did it and am making sfos again if it works I'll upstream it | 12:22 |
| mighty17 | <T42 "<elros34> yes"> I didn't understand, it just shows it when I run make | 12:22 |
| mighty17 | <T42 "<elros34> first one looks wrong "> Sed failure happens no matter what is there | 12:23 |
| mighty17 | <T42 "<elros34> you need to remove ext"> I removed from all of them 😲 | 12:24 |
| mighty17 | <T42 "<edp_17> Have you checked the mo"> Yes :) | 12:24 |
| T42 | <elros34> all? 1 line in 1 fstab. Can you show make hybris-hal output now, especially ********************* /boot appears to live on" part | 12:25 |
| mighty17 | It's same output and by all I mean I removed /omap from all the fixup mount points in espresso thing | 12:27 |
| T42 | <elros34> I am talking about this line: https://github.com/LineageOS/android_device_samsung_espressowifi/blob/cm-14.1/rootdir/fstab.espresso#L26 | 12:30 |
| mighty17 | <T42 "<elros34> I am talking about thi"> But u said to remove /omap from fixup-mount points | 12:30 |
| T42 | <elros34> that was yesterday, next issue is that entry: https://irclogs.sailfishos.org/logs/%23sailfishos-porters/latest.log.html#t2021-02-04T12:15:01 | 12:32 |
| mighty17 | <T42 "<elros34> that was yesterday, ne"> The sed issue? It can be fixed by putting hybris-updater-script without line 36 | 12:35 |
| T42 | <elros34> I don't know how it can be fixed that way but anyway you need to remove that line so make hybris-hal will finish without errors | 12:38 |
| mighty17 | I removed the line 36 😄 | 12:43 |
| mighty17 | And make runs successfully | 12:46 |
| mighty17 | should i try with sfos3.2.x as sfos3.4 dosent support kernel version 3.0 @elros34 | 12:50 |
| T42 | <elros34> no, now you should check journalctl and dmesg with your current build | 12:51 |
| mighty17 | ok i will check with build having lineageos 14.1 fstab and /omap removed from fixup-mount | 12:53 |
| T42 | <elros34> no, use that one you have on device already. | 12:54 |
| mighty17 | on device? | 12:56 |
| mighty17 | as in the cm12.1 fstab? | 12:56 |
| T42 | <elros34> there is no point wasting time and creating new image now because based on your answers to edp17 your mount units are correct | 12:57 |
| mighty17 | ohh thats dope | 12:58 |
| mighty17 | now what should i do | 12:58 |
| T42 | <elros34> just get journal | 13:00 |
| mighty17 | ?/ | 13:00 |
| mighty17 | * ?? whats that | 13:00 |
| T42 | <elros34> type journalctl --no-page | 13:00 |
| mighty17 | in telnet right | 13:01 |
| T42 | <elros34> in telnet max 1 min after reboot | 13:01 |
| mighty17 | ok | 13:02 |
| mighty17 | https://pastebin.ubuntu.com/p/rWvB3jz4VR/ elros34 | 13:04 |
| T42 | <elros34> that is all? let it boot for a while to get all logs or use journalctl --no-tail -f so you will see live logs. What about dmesg? | 13:07 |
| mighty17 | <T42 "<elros34> that is all? let it bo"> https://pastebin.ubuntu.com/p/hSGV7zXvC3/ | 13:08 |
| mighty17 | <T42 "<elros34> in telnet max 1 min af"> oh sorry didnt read this | 13:09 |
| mighty17 | <T42 "<elros34> that is all? let it bo"> https://pastebin.ubuntu.com/p/SYcxz59FPq/ now? | 13:10 |
| T42 | <elros34> ah so droid-hal-init is in dmesg. I wonder why is that for some samsung devices | 13:10 |
| mighty17 | oooh | 13:10 |
| mighty17 | any fixes? | 13:12 |
| T42 | <elros34> Have you added symlinks mentioned in hybris-14.1 chapter of hadk-faq? What about old cm12 based droid-configs? Check sparse/etc/mod* whether it loads some kernel modules | 13:15 |
| mighty17 | <T42 "<elros34> Have you added symlink"> there is no hadk-faq chapter atleast in the latest manual, and i didnt quite understand the 2nd part, check where? | 13:17 |
| mighty17 | /home/mighty/hadk/hybris/droid-configs/sparse dosent have a etc folder (this is on my pc) | 13:17 |
| T42 | <elros34> github.com/mer-hybris/hadk-faq | 13:17 |
| T42 | <elros34> about sparse/etc check it in old cm12 droid-configs repo | 13:18 |
| mighty17 | okay lemme see | 13:18 |
| mighty17 | <T42 "<elros34> about sparse/etc check"> https://github.com/yacuken/droid-config-espresso3g/tree/master/sparse/etc | 13:19 |
| mighty17 | <T42 "<elros34> github.com/mer-hybris/"> no i havent run `Run this script in $ANDROID_ROOT http://paste.opensuse.org/40869869` | 13:19 |
| T42 | <elros34> you can create those symlinks on device now so you don't have to create new image yet | 13:20 |
| mighty17 | oh thats great how do i do it? | 13:21 |
| T42 | <elros34> removing "hybris/droid-configs/sparse" in script should be fine I think. Also etc/modules.d | 13:24 |
| T42 | <elros34> modules-load.d and modprobe.d from old repo might be useful | 13:24 |
| mighty17 | oh | 13:24 |
| mighty17 | <T42 "<elros34> removing "hybris/droid"> which script? as in how is it possible to do in on the device itself? | 13:25 |
| T42 | <elros34> script mentioned in faq | 13:26 |
| mighty17 | <T42 "<elros34> modules-load.d and mod"> modprobe.d/droid-hal-espresso3g.conf seems to be about wifi | 13:26 |
| mighty17 | <T42 "<elros34> script mentioned in fa"> http://paste.opensuse.org/40869869 ??? but i never ran it in the first place | 13:27 |
| mighty17 | sorry i cant seem to understand | 13:27 |
| T42 | <elros34> so run it now on device just without that part in paths I mentioned | 13:28 |
| mighty17 | ooooh | 13:29 |
| mighty17 | <T42 "<elros34> so run it now on devic"> https://pastebin.ubuntu.com/p/f7kQn9Y8GR/ i think this is correct | 13:31 |
| mighty17 | @elros34 https://pastebin.ubuntu.com/p/NwV762Jsb3/ i ran it | 13:36 |
| mighty17 | now what? | 13:37 |
| T42 | <edp_17> reboot? | 13:39 |
| T42 | <elros34> so you already had the symlinks there or you run it twice? Check wheter they are correct | 13:40 |
| mighty17 | <T42 "<elros34> so you already had the"> i ran it twice my bad | 13:41 |
| mighty17 | <T42 "<edp_17> reboot?"> okay | 13:41 |
| T42 | <edp_17> @elros34 : Hi, I have a question for you. I've just seen that 4.0 EA is out. Do you know when can I start building 4.0? | 13:41 |
| mighty17 | <T42 "<edp_17> reboot?"> nope still the same | 13:43 |
| T42 | <elros34> oh good to know 4 is out! | 13:43 |
| T42 | <edp_17> https://forum.sailfishos.org/t/release-notes-koli-4-0-1/4542 | 13:44 |
| mighty17 | <mighty17 "nope still the same"> tapping the display shows backlight but nothing on the screen | 13:46 |
| mighty17 | any logs i should send? | 13:46 |
| T42 | <elros34> @edp_17 For local build you can probably upgrade target,tooling and try to build it now but for obs you will have to wait after official release and obs targets are ready | 13:46 |
| T42 | <elros34> 3.10 minimum kernel bump:( | 13:49 |
| T42 | <edp_17> Yeah, that device is not on OBS atm. | 13:50 |
| T42 | <edp_17> 3.10? So, doesn this mean that 4.0 cannot be built for my S2 (i9100)? (That's kernel is 3.0.) | 13:51 |
| mighty17 | edp_17 s2 has partial mainline support https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/arch/arm/boot/dts/exynos4210-i9100.dts?h=v5.8.3 | 13:52 |
| mighty17 | and what should i do now? | 13:53 |
| T42 | <elros34> @edp17 I don't know yet I need changelog to find reason for this min kernel change | 13:53 |
| T42 | <elros34> read* | 13:54 |
| T42 | <edp_17> @elros34 : Okay, thanks for looking into it anyway! | 13:54 |
| T42 | <elros34> Yeah I also use 3.0 kernel device.. | 13:54 |
| T42 | <edp_17> mighty17: I know there is partial mainline support for the S2 but not much is working on that unfortunately, so I stay with its original kernel. | 13:55 |
| mighty17 | you can mainline xD | 13:55 |
| mighty17 | even im trying to mainline my device (it has 3.0 kernel) | 13:55 |
| mighty17 | <mighty17 "and what should i do now? "> ??? rebuild sfos or what? this is confusing | 13:58 |
| T42 | <edp_17> No, at the moment you don't need to re-build neither the kernel nor the sfos image. Now you are fixing everything on the device. Once it works, then you can go back to PC and apply all the stuff in there you amended on the device and then re-build the image. This way, you'll get a working image with the less re-builditeration. | 14:01 |
| mighty17 | that is great but what should i do xD | 14:05 |
| mighty17 | it still dosent work on device | 14:05 |
| mighty17 | i cant understand what the problem is, is it fstab? is it sfos 3.4 dosent support kernel 3.0? what is it | 14:07 |
| T42 | <edp_17> SFOS 3.4 does support that kernel as I am using that on my galaxy s2 which also has kernel version 3.0 | 14:20 |
| mighty17 | thanks to patches from elros :) | 14:20 |
| mighty17 | also if u have any idea for my problem ping me i am shutting down the device for now | 14:20 |
| mighty17 | btw it does say charging ??/100 though | 14:21 |
| T42 | <edp_17> I just checked the targets and tooling url and both of them are available for 4.0.1.45. Great! I'll skip building 3.4 and will move on to 4.0. 😊 | 14:29 |
| mighty17 | <T42 "<edp_17> I just checked the targ"> But kernel patches? Aren't u on 3.0 | 14:41 |
| T42 | <edp_17> That device (Note 4 treltexx) I was referring to has 3.10.9 so looks like can get 4.0. 😊 | 14:43 |
| mighty17 | Ooh that's great!! | 15:04 |
| mighty17 | Btw @edp_17 should I try with 3.2.x version as it officially supports 3.0 kernel? I'm so tired of making this work | 15:04 |
| T42 | <elros34> how about you answer this: https://irclogs.sailfishos.org/logs/%23sailfishos-porters/latest.log.html#t2021-02-04T13:40:03 Building older sfos release will on create more issues | 15:11 |
| T42 | <edp_17> mighty17: I don't think SFOS 3.2.x does officially support kernel version 3.0. If it did support, I wouldn't needed Elros' glibc patch. | 15:29 |
| T42 | <edp_17> Although, with Elros' glibc patch you cna try building 3.4 because that works for sure. (At least it works on my S2, so potentially that could be built for other devices too.) | 15:29 |
| mighty17 | <T42 "<edp_17> mighty17: I don't think"> In his pr he.says sfos 3.3.0.x needs kernel ≥ 3.2 so 3.2 would support kernel 3.0 | 15:30 |
| T42 | <edp_17> @elros34 : So, are you suggesting to not sweat on and accept that on those old devices the latest SFOS version is 3.4? | 15:31 |
| mighty17 | <T42 "<edp_17> Although, with Elros' g"> Yup it does work I can see it show charging ??/100 but other than that we might need to fix some stuff | 15:31 |
| mighty17 | * In his pr he.says `sfos 3.3.0.x needs kernel ≥ 3.`2 so 3.2 would support kernel 3.0 | 15:31 |
| mighty17 | But I don't know how to fix it | 15:32 |
| T42 | <elros34> @edp_17 hm? I will try everything to get it working on 4.0.1. So far I did not find anything except big systemd upgrade which might be the culprit | 15:36 |
| T42 | <adampigg> warning, systemd breaks ports | 15:38 |
| T42 | <adampigg> https://github.com/sailfish-on-fxtecpro1/droid-hal-img-boot-fxtec-t5/commit/75cbf44353fdaf22322d5c6a60b5cbaa548597a2 | 15:39 |
| T42 | <adampigg> see ^^ for fix | 15:39 |
| T42 | <adampigg> basically, no user session starts | 15:39 |
| T42 | <edp_17> @elros34 : Don't missread me, I wasn't complaining. At all. 😊 I just stated that might be 3.4 is the last available version for that device. Don't waste time on that if something not obvious or very difficult. Thanks for you glibc work, what we already achieved with that device is incredible! | 15:41 |
| T42 | <elros34> I will spend time anyway because I want to have it on my ancient device | 15:43 |
| T42 | <edp_17> Then, your work for your own device will be the added bonus for all of us. 😃 | 15:45 |
| mighty17 | ya thanks 😃 | 17:14 |
| mighty17 | <mighty17 "Yup it does work I can see it sh"> anyone? | 17:16 |
| T42 | <godogabor> How can I do this? "However, if the user first directs the voice to the HF speaker and then back to the headset, the voice can be heard at the headset." | 17:40 |
| rinigus | @adampigg: why is that systemd fix needed? Wondering if it's needed for ports that follow official version closer... | 18:37 |
| T42 | <adampigg> rinigus: afaik its related to kernel version ... not needed on new kernels | 18:37 |
| rinigus | Good, which kernel do you have? | 18:41 |
| rinigus | @adampigg ^ | 18:42 |
| T42 | <adampigg> rinigus: 4.4.153 | 18:43 |
| rinigus | @adampigg: ok, we are on 4.9. but 4.4 is not the oldest one... | 18:53 |
| T42 | <adampigg> rinigus: cgroups v2 came in kernel 4.5, so i expect it will impact <= 4.4 | 18:58 |
| mighty17 | can u guys help me? see the chat above i just get backlight when i touch the screen (device - espresso3g base - LineageOS 14.1 SFOS 3.4.0.24 Kernel - 3.0.101) | 19:01 |
| rinigus | @adampigg: but in that case older official devices would have to use the same trick with systemd | 19:34 |
| T42 | <adampigg> rinigus: i think they do, im sure mal used it in an official repo somewhere | 19:35 |
| rinigus | @adampigg: ok, good to know it's about kernel version. Thanks! | 19:36 |
| T42 | <W %lastname%> sdk platform for 4.0.1.45 sfos where can I download it? | 19:46 |
| mal | rinigus: about that systemd fix piggz did https://github.com/mer-hybris/droid-hal-img-boot-sony-nile/commit/d19e9e81485eb13790a9cba5f27470e97ba3047c | 19:51 |
| mal | and yes, it's about kernel version | 19:52 |
| mal | @adampigg interestingly old enough kernel are fine without that fix | 19:53 |
| piggz | mal: its a shame systemd doesnt detect the required features | 19:54 |
| mal | piggz: for example 3.10 kernel of xperia x didn't need it based on git log | 19:54 |
| T42 | <Heng %lastname%> In ssu what does "Waiting" mean? | 21:05 |
| T42 | <Heng %lastname%> trying to update to 4 but seems hung | 21:06 |
| T42 | <elros34> @edp_17 false alarm so far everything works good on 4.0.1.45 and 3.0 kernel | 22:01 |
| T42 | <adampigg> cool .... hopefully be ok on latte then | 22:16 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!