| EleventhLast | https://pastebin.com/BNLTGTAv | 00:00 |
|---|---|---|
| T42 | <elros34> There not many devices with 3.4 kernel. Unlikely this will help but have you tried disabling audit (kernel cmdline audit=0) or searching for these 'undefined instruction' errors? | 06:14 |
| EleventhLast | in short, there is no such error if you only set up the OS, now I will compare 2 logs, but the difference is only in Wi-Fi | 06:27 |
| EleventhLast | did not try to disable auditing | 06:28 |
| EleventhLast | I looked at both logs, and the error itself begins precisely with starting the network and scanning the wifi, but for some reason, at the first start, an error about this instruction appeared, but it did not lead to a kernel bug | 06:39 |
| T42 | <elros34> then maybe it would be worth to compare commits related to sysfs/wifi 12vs15vs17 branch or even search for some custom kernel which might have some backported patches | 06:57 |
| EleventhLast | Yes, I will solve this problem myself, and I also found a compositing error, now I want to adjust the spec ratio | 07:01 |
| EleventhLast | but I have a 5.7-inch display, can I use the same formula? | 07:01 |
| T42 | <elros34> why not or find device with similar display/resolution | 07:04 |
| T42 | <elros34> maybe one of offcial devices | 07:04 |
| EleventhLast | remember I disabled the timer in init.target.rc ? How can I make it in the assembly itself? | 07:04 |
| T42 | <elros34> same file should be in $ANDROID_ROOT/device/*/*/rootdir/ or something like that | 07:05 |
| EleventhLast | I didn’t even understand how to calculate this pixel ratio, I get insanely huge numbers | 07:17 |
| EleventhLast | and yet, if it’s not difficult for you, tell me how to change the spec ratio, I don’t want to wait another hour to rebuild the image | 08:15 |
| EleventhLast | strange, the phone thinks it's charging, but nothing is connected to it | 10:28 |
| EleventhLast | sysfs/wifi there is no file, there is also no git, all I can say is that the firmware works after the initial setup, but if you reboot, everything dies | 12:04 |
| nncv | The only error I have left is this now: "Fetching: 81% (593/732) platform/packages/modules/DnsResolvererror.GitError: Cannot fetch device-sony-common update-ref: fatal: 137bf78caf8a464adcac102bdcb2d70c91c98509^0: not a valid SHA1 | 12:24 |
| nncv | " | 12:24 |
| T42 | <adampigg> r5555555555555555555ewuiiiiiiiiooooooooooooooooooooooooooooooooooooooooooooooooooooooo00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 | 13:23 |
| T42 | <adampigg> u]] | 13:23 |
| T42 | <adampigg> []-==7;;;8+;+i==oo****889;8;877;9 | 13:23 |
| T42 | <TheVancedGamer> uh | 13:23 |
| T42 | <Umeaman> Anyone here that wants to help out building a program based on the HADK instructions? I mean, there has to be an alternative way than through CLI to actually build Sailfish OS for a new device. | 13:46 |
| T42 | <Umeaman> | 13:46 |
| T42 | <Umeaman> Anyway, my project to join is here: https://gitlab.com/haddock1/haddock | 13:46 |
| T42 | <Umeaman> Don't get me wrong, all I'm asking is an alternative for noobs when it comes to CLI. | 13:47 |
| deathmist1 | @Umeaman looks similar to what I've made https://github.com/JamiKettunen/sfbootstrap I wanted to automate practically everything and integrate the workarounds/hacks one might have to do to build everything, though I think it broke right after I released it and I've not looked into SFOS things since due to being busy with other stuff | 13:54 |
| T42 | <Umeaman> To tell you the truth, I didn't know that it existed. (re @SailfishFreenodeIRCBridgeBot: <deathmist1>@Umeaman...) | 13:54 |
| deathmist1 | well I only started work on it sometime in 2021 and finally published initial version in 2022 :p | 13:56 |
| T42 | <Umeaman> Cool! What devices are ported thanks to this? | 13:57 |
| deathmist1 | it doesn't really guide you though / automate new port steps that much, but I've worked on a WIP module that would add this capability. I just need to look into more things and see if there's problems before pushing it (and first fix the scripts in general for latest versions) | 13:58 |
| mal | I don't really see how much porting of new devices could be automated, so many things change based on android base version and other things | 14:02 |
| deathmist1 | mal: in my case the "new port module" was mostly just a semi-interactive list of questions based on which it would create dhd/dcd/dvd repos for the device enough to build an initial flashable zip, no guarantees that it would boot or anything :p | 14:04 |
| mal | having a script to generate those repos would make sense, other than that not sure really | 14:06 |
| deathmist1 | like "is there a cellular modem", "at least 2 GB RAM or no" etc. and would tweak the patterns a bit | 14:06 |
| mal | yeah | 14:07 |
| EleventhLast | mal , have you removed anything from defconfig ? maybe there was some parameter with which the kernel did not work | 14:37 |
| piggz_ | seems like my kitten was typing | 14:42 |
| T42 | <TheVancedGamer> Yeah seemed like it :D | 14:50 |
| EleventhLast | in short, I don't know how to solve this problem | 15:04 |
| mal | did you try that one patch from yesterday? | 15:08 |
| EleventhLast | they were already installed in my files | 15:11 |
| mal | even this one https://github.com/aosp-mirror/kernel_common/commit/bb2b0051d7b0772ea9d0b4be900c2d965093f5d7 ? | 15:13 |
| EleventhLast | it looks like yesterday I had to sleep ..... damn, yesterday I had lines that didn’t seem to exist, and these seem to have also dreamed of .... | 15:16 |
| EleventhLast | there are no these patches, but yesterday I saw them in my config | 15:16 |
| EleventhLast | what happened yesterday, I seem to have removed these patches on purpose | 15:22 |
| EleventhLast | mal same error which refers to BUG_ON(sd->s_flags & SYSFS_FLAG_REMOVED); | 15:40 |
| EleventhLast | what should I do? I feel sorry for abandoning this device, considering how much time and effort I spent on it, and I also noticed that there are artifacts of the "wallpaper" image | 16:52 |
| T42 | <elros34> If you want to drop device after 1 day of bug fixing failure then you should choose official device and forget about porting. Some porters fix issues for months or never. What are even the steps to reproduce this bug? | 17:29 |
| T42 | <elros34> I wonder what would happen with BUG_ON -> WARN_ON but maybe it's not even safe to try it | 17:33 |
| EleventhLast | in general, all instruction errors start after this https://pastebin.com/rdT7860p | 18:20 |
| EleventhLast | but I have no idea why this is happening | 18:20 |
| T42 | <elros34> have you tried lineage18 branch from you kernel sources or some other kernel if there is any? | 18:39 |
| EleventhLast | I'm afraid I won't have enough internal memory on my hard drive, how much will it weigh in total? | 18:54 |
| T42 | <elros34> zero unless you cloned minimal sources with 1 branch and not commit history | 18:55 |
| EleventhLast | you can try lineage17 | 18:55 |
| EleventhLast | I don’t know, my lineage 15.1 takes 60 gigabytes | 18:56 |
| T42 | <elros34> check, git branch -a in kernel sources | 18:57 |
| EleventhLast | can i just replace the links with lineage 17 and repo sync? | 18:57 |
| EleventhLast | * (no branch) remotes/github/lineage-15.1 remotes/m/hybris-15.1 -> github/lineage-15.1 | 18:59 |
| T42 | <elros34> be careful with repo sync to not lost all your changes | 18:59 |
| EleventhLast | I save the changes, and then you can change the manifest and still sync again for lineage 17? | 19:00 |
| T42 | <elros34> I was only talking about kernel not whole sources so git should be enough | 19:02 |
| EleventhLast | only git clone to folder kernel? | 19:03 |
| mal | assuming the same kernel repo has different branches then just do git fetch there and the change to some newer branch and see if it works | 19:11 |
| voidanix[m] | Why not use 18.1 for the whole thing though? | 19:30 |
| deathmist1 | I don't know what the state of hybris-18.1 is still after a year, no changes in https://github.com/mer-hybris/android hybris-18.1(-update) branches since almost a year though | 19:45 |
| *** Daaanct12 is now known as Danct12 | 19:57 | |
| mal | 18.1 has issues on some older devices at least, I think the issue is related to whether the lineage build defines updatable apex or not | 20:33 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!