Wednesday, 2021-07-28

T42<edp_17> Ops, In this case I am sorry for the false info and thanks for correction. (re @elros34: --mw usage is  total...)06:03
T42<supirlelik96> <project path="external/libhybris" name="libhybris/libhybris" revision="master" />           in manifest right? (re @elros34: either play with git...)08:28
T42<supirlelik96> <project path="external/libhybris" name="libhybris/libhybris" revision="master" />           in08:28
T42<supirlelik96> manifest right? (edited) (re @elros34: either play with git...)08:28
T42<supirlelik96> <project path="external/libhybris" name="libhybris/libhybris" revision="master" />08:28
T42<supirlelik96> in manifest right? (edited) (re @elros34: either play with git...)08:28
T42<supirlelik96> I tried deleting external/libhybris and cloned the sources again. The error remained anyway. How can I fix it? (re @elros34: either play with git...)08:53
T42<elros34> git clone it instead using repo09:13
T42<elros34> why libhybris/libhybris? that is upstream without packaging, sailfish use mer-hybris/libhybris09:14
T42<supirlelik96> How to fix problem? (re @elros34: git clone it instead...)09:14
T42<supirlelik96> ok (re @elros34: why libhybris/libhyb...)09:14
T42<elros34> what kind of instructions do you follow?09:15
T42<supirlelik96> hadk (re @elros34: what kind of instruc...)09:15
T42<supirlelik96> latest09:15
T42<elros34> that is not enough, follow also mer-hybris/hadk-faq and for latest issues09:16
T42<edp_17> This last one was new to me. I'll include this into my notes. Thanks for the heads up!10:03
T42<edp_17> @elros34 : I was about to ask how to include gnu-bash into the build but I found it in that instruction.10:09
T42<edp_17> When I added the Requires: gnu-bash into the patterns I spotted the Requires: busybox-static in there. Should I remove that?10:10
T42<elros34> no, busybox-static is used by /init-debug script10:23
T42<edp_17> Cheers!10:27
T42<supirlelik96> (re @edp_17: This last one was ne...)10:35
T42<supirlelik96> Error how to fix building droid-hal10:36
T42<edp_17> @supirlelik96 : solution: (in Platform) sb2 -t $VENDOR-$DEVICE-$PORT_ARCH -m sdk-install -R zypper install droid-config10:37
T42<supirlelik96> ok10:38
T42<edp_17> Then rebuild droid-hal-version-$DEVICE or whatever was building when you got this error.10:39
T42<supirlelik96> (re @edp_17: @supirlelik96 : solu...)10:39
T42<supirlelik96> What should I do next? (re @supirlelik96: https://paste.ubuntu...)10:39
T42<edp_17> I would do option 1.10:45
T42<elros34> based on your droid-hal-device.log, you are missing /system mount unit. Have you added something to makefstab_skip_entries?10:51
T42<supirlelik96> + /bin/rm -rf /home/alex/mer/android/droid/hybris/mw/yamuisplash/installroot11:12
T42<supirlelik96> + exit 011:12
T42<supirlelik96> Directory walk started11:12
T42<supirlelik96> Directory walk done - 91 packages11:12
T42<supirlelik96> Temporary output repo path: /home/alex/mer/android/droid/droid-local-repo/onclite/.repodata/11:12
T42<supirlelik96> Preparing sqlite DBs11:12
T42<supirlelik96> Pool started (with 5 workers)11:12
T42<supirlelik96> Pool finished11:12
T42<supirlelik96> DBus unavailable, falling back to libssu11:12
T42<supirlelik96> Loading repository data...11:12
T42<supirlelik96> Reading installed packages...11:13
T42<supirlelik96> Forcing installation of 'yamuisplash-1.0.0-1.aarch64' from repository 'Plain RPM files cache'.11:13
T42<supirlelik96> Resolving package dependencies...11:13
T42<supirlelik96> Problem: nothing provides yamui needed by yamuisplash-1.0.0-1.aarch6411:13
T42<supirlelik96>  Solution 1: do not install yamuisplash-1.0.0-1.aarch6411:13
T42<supirlelik96>  Solution 2: break yamuisplash-1.0.0-1.aarch64 by ignoring some of its dependencies11:13
T42<supirlelik96> Choose from above solutions by number or cancel [1/2/c/d/?] (c): c11:13
T42<supirlelik96> * Check /home/alex/mer/android/droid/hybris/mw/yamuisplash.log for full log.11:13
T42<supirlelik96> !! can't install the package (re @edp_17: I would do option 1.)11:13
T42<supirlelik96> how to fix&11:13
T42<supirlelik96> ?11:13
T42<supirlelik96> (re @edp_17: I would do option 1.)11:13
T42<supirlelik96> error building droid-hal11:18
T42<supirlelik96> i fixed problem (re @edp_17: I would do option 1.)11:23
mal@edp_17 on which sfos version do you have that camera issue?11:24
T42<edp_17> mal: On the latest: 4.1.02411:50
T42<supirlelik96> I building droid-hal  and I get an error that I couldn't fix (re @supirlelik96: https://paste.ubuntu...)11:52
T42<supirlelik96> please help (re @edp_17: mal: On the latest: ...)11:52
T42<edp_17> @supirlelik96 : What's in this log? /home/alex/mer/android/droid/hybris/mw/yamuisplash.log11:53
T42<supirlelik96> ok11:54
T42<edp_17> paste.ubuntu please11:54
T42<supirlelik96> ok11:54
T42<supirlelik96> (re @edp_17: paste.ubuntu please)11:55
T42<edp_17> It looks like you also need to build/install yamui if you want to install yamuisplash.11:58
T42<edp_17> What is this yamuisplash?11:58
T42<edp_17> I found it:
T42<supirlelik96> this is a component when building droid-hal (re @edp_17: What is this yamuisp...)11:59
T42<supirlelik96> libhbybris components11:59
T42<supirlelik96> libhybybris components (edited)11:59
T42<supirlelik96> libhybris components (edited)11:59
T42<edp_17> You need to build yamui. Do this12:00
T42<edp_17> rpm/dhd/helpers/ --mw= -s rpm/yamui.spec12:00
T42<supirlelik96> ok (re @edp_17: You need to build ya...)12:01
T42<supirlelik96> yamui is building12:02
T42<edp_17> Is it for displaying custom logo/loading screen when the device is starting?12:03
T42<supirlelik96> Yse (re @edp_17: Is it for displaying...)12:10
T42<supirlelik96> Yes (edited) (re @edp_17: Is it for displaying...)12:10
T42<supirlelik96> this is necessary so that the loading screen is not the redmi logo or black, but the sailfish os logo (re @edp_17: Is it for displaying...)12:13
T42<edp_17> How does is it work? So I just need to build them and install the packages into the final build? Or is there some additional trick?12:18
T42<supirlelik96> Yes (re @edp_17: How does is it work?...)12:23
T42<edp_17> Is there any additional trick?12:32
T42<supirlelik96> (re @edp_17: Is there any additio...)12:51
T42<supirlelik96> error building rootfs with mic12:51
T42<supirlelik96> ­čśČ12:51
T42<supirlelik96> patterns  generated (re @edp_17: Is there any additio...)13:10
T42<supirlelik96> please help (re @edp_17: Is it for displaying...)13:17
T42<supirlelik96> droid config, droid-hal-version :
T42<edp_17> hybris/droid-configs/droid-configs-device/helpers/ No such file or directory13:26
T42<supirlelik96> yes13:27
T42<supirlelik96> how to fix"?13:27
T42<supirlelik96> yeah (re @edp_17: hybris/droid-configs...)13:27
T42<edp_17> Have you updated all submodules including13:27
T42<edp_17> that one?13:28
T42<supirlelik96> no, but how to do it? (re @edp_17: Have you updated all...)13:28
T42<supirlelik96> in habuild-sdk  repo sync -fetch submobules?13:29
T42<edp_17> No. As Elros said, you need to follow not only the HADK but the hadk-faq too. Plus that third link.13:29
T42<supirlelik96> ok13:30
T42<edp_17> If you didn't update all submodules, you'll get other problems too.13:30
mal@adampigg I managed to get sailjail working with the patch13:32
T42<edp_17> @supirlelik96 : I recommend you to make notes of these errors and about their solution. So next time you just need to check your notes and will know what and how to fix.13:33
T42<supirlelik96> ok (re @edp_17: @supirlelik96 : I re...)13:33
T42<supirlelik96> (re @edp_17: If you didn't update...)13:47
T42<supirlelik96> ­čÖĆ13:48
T42<edp_17> What are you trying to do?13:49
T42<supirlelik96> iam rebuilding droid-hal13:50
T42<supirlelik96> so that there are rpm patterns packages13:50
T42<shouaccount> Bump (re @shouaccount: I built sfos with hy...)13:51
T42<edp_17> In the log you linked it looks like you were trying to run that
T42<supirlelik96> already with the .yml file13:51
T42<supirlelik96> yess.. (re @edp_17: In the log you linke...)13:51
T42<edp_17> Then that is wrong!13:52
T42<edp_17> Don't run that. Have you updated the submodules like the hadk-faq says?13:52
T42<supirlelik96> How to do this I can't understand? (re @edp_17: Don't run that. Have...)13:53
T42<shouaccount> Update your submdoules (re @supirlelik96: How to do this I can...)13:56
T42<shouaccount> Search on web how to do that13:56
T42<supirlelik96> ok13:56
T42<shouaccount> @edp_17 can you please suggest me something as well? :p (re @shouaccount: I built sfos with hy...)13:57
T42<shouaccount> @edp_17 can you please suggest me something as well? :P (edited) (re @shouaccount: I built sfos with hy...)13:57
T42<edp_17> Okay. Do this:13:59
T42<edp_17> 1. cd ~/mer/android/droid/rpm/dhd13:59
T42<edp_17> 2. git fetch
T42<edp_17> 3. git pull master13:59
T42<edp_17> 4. cd ~/mer/android/droid/hybris/droid-configs/droid-configs-device13:59
T42<edp_17> 5. git fetch
T42<edp_17> 6. git pull master13:59
T42<edp_17> 7. cd ~/mer/android/droid/hybris/droid-hal-version-$DEVICE/droid-hal-version13:59
T42<edp_17> 8. git fetch
T42<edp_17> 9. git pull master13:59
T42<edp_17> 10. rebuild packages (re @supirlelik96: How to do this I can...)13:59
T42<edp_17> Trying. ­čśŐ (re @shouaccount: @edp_17 can you plea...)13:59
T42<supirlelik96> Thank you (re @edp_17: Okay. Do this:13:59
T42<supirlelik96> 1. cd...)13:59
T42<elros34> I will repeat again, you have something wrong with fstab or makefstab_skip_entries because system mount unit is not created so it will be good to fix that before creating image14:04
T42<supirlelik96> (re @edp_17: Okay. Do this:14:06
T42<supirlelik96> 1. cd...)14:06
T42<supirlelik96> error rebuild droid-config14:06
T42<supirlelik96> please help :) (re @edp_17: Trying. ­čśŐ)14:08
T42<supirlelik96>      full log (edited)14:09
T42<adampigg> Mal: gr8, was going to ask. Should you add to faq?14:13
T42<edp_17> @supirlelik96 : looks like the update of submodules was not enough. I'd remove them and clone from github.14:14
T42<supirlelik96> ok (re @edp_17: @supirlelik96 : look...)14:14
T42<batuhannay> Forwarded from batuhannay: Bir├žok yat─▒r─▒mc─▒ ve broker, ger├žekli─če inanmad─▒klar─▒ i├žin t├╝m yat─▒r─▒m karlar─▒n─▒ kaybederken, baz─▒lar─▒ b├╝y├╝k para ├žekme i┼člemlerini sahte ┼čirketlere kapt─▒rd─▒ ve bir├žo─ču hala kaybetmeye devam ediyor.14:18
T42<batuhannay>  Hepinizi zaman─▒m─▒z─▒n en b├╝y├╝k ├Âdeme yapan ve yasal yat─▒r─▒m ┼čirketiyle tan─▒┼čt─▒rmak i├žin buraday─▒m..Para ├žekmelerimi otomatik olarak al─▒yorum ve Option jeton de─či┼čimi ile g├╝nl├╝k yat─▒r─▒m─▒m─▒n y├╝kseli┼čine tan─▒k olmaktan ├žok mutluyum.14:18
T42<batuhannay>  ─░nan─▒n bana ┼ču anda yat─▒r─▒m yapmak i├žin en iyi platform bu.14:18
T42<batuhannay>  Hemen ├╝ye ol ve benim gibi strat kazan, linki buradan takip edebilirsin14:18
T42<supirlelik96> please help (re @edp_17: @supirlelik96 : look...)17:44
T42<supirlelik96> (re @edp_17: @supirlelik96 : look...)17:44
T42<supirlelik96>   buidling rootfs with mic 1.0.2  ERROR (edited) (re @edp_17: @supirlelik96 : look...)17:45
T42<elros34> do not upload photos, if you expect help then upload your droid-config, droid-hal kernel with all your changes to github18:05
T42<supirlelik96> ok (re @elros34: do not upload photos...)18:11
T42<supirlelik96> ­čÖĆ please help (re @elros34: do not upload photos...)18:13
T42<elros34> to github means to or similar site not to telegram18:14
T42<supirlelik96> ok18:15
T42<supirlelik96> it is temporarily impossible to use an archive instead of a github for the time being (re @elros34: to github means to g...)18:15
T42<supirlelik96> it is temporarily impossible to use an git instead of archve for the time being (edited) (re @elros34: to github means to g...)18:16
T42<edp_17> mal: Do you have idea the root cause and/or solution of that camera error?20:26
mal@Herrie1982 are you still in this channel?21:03
T42<Herrie1982> Yes (re @SailfishFreenodeIRCBridgeBot: <mal>@Herrie1982 are...)21:03
malyou linked quite a long time ago some kernel patches to use new systemd with 3.4 kernel and after some debugging it seems one of those causes a kernel panic (null pointer error) when running some processes in gdb, like journalctl21:05
malafter reverting this and using this instead I don't get the crash21:06
malalso do you happen to see anything like this in logs "undefined instruction: pc=af936966" the address is different each time21:08
mal@Herrie1982 have you seen anything like that ^21:14
T42<Herrie1982> It doesn't ring a bell really, but from our side it was Tofe/Christophe who was looking into it21:17
T42<Herrie1982> I know it somehow depends on which 3.4.x kernel you have21:17
T42<Herrie1982> We had different versions of the patches for different 3.4 kernels21:17
T42<Herrie1982> All of the different 3.4.x kernels had a different level of NS implementations somehow21:17
malyeah, I use the 3.4 kernel fairphone uses for aosp9 releases, and some backports on top21:18
T42<Herrie1982> 3.4 ones are a pain, but we got them to work, but then again we probably have less requirements in LuneOS vs SFOS21:19
malI tried the kernel updated to latest stable 3.4 release from fp2 lineage repos but that failed to boot to UI for some reason, even after quite much debugging, starting UI caused a reboot21:19
malnow with that revert and patch I have latest sailfish running on fp2 with 3.4 kernel21:20
maljust need to see if I could get rid of that "undefined instruction" messages, I get quite a lot of those, based on some debugging those might be caused by openssl21:21
T42<Herrie1982> 3.4 are really trial and error based on my experience21:21
T42<Herrie1982> Had some 3.4.0 and some 3.4.1xx and there's quite a difference between them21:22
T42<Herrie1982> You might want to check instead21:24
T42<Herrie1982> We used that for Halium/LOS 16 based for Hammerhead and used some different patches there21:24
malI'll have a look21:25
T42<Herrie1982> Tenderloin is another one we recently upgraded to Android 9.0 base with 3.4 kernel:
T42<Herrie1982> Though Hammerhead is probably more useful21:28
T42<Herrie1982> For Mako we used this:
mallooks like hammerhead had different approach for the pidns, it implemented it properly and had some extra backports21:30
T42<Herrie1982> It's trial and error really with these old kernels and various levels of patches21:31
T42<Herrie1982> Tenderloin is a franken kernel anyway, borrowed from HTC because it was stuck on 2.6 initially21:31
T42<Herrie1982> Already a miracle we're on 3.421:31
malthat sounds quite terrible21:31
T42<Herrie1982> There's a mainline kernel, but has issues (as usual)21:32
T42<Herrie1982> So I would recommend to use Tenderloin as a reference, but Mako or Hammerhead should be a better guess21:32
malI have managed to boot sailfish to UI with mainline kernel also21:32
malI mean on fp221:32
T42<Herrie1982> Since it uses same msm8974 as Hammerhead it should be possible yes21:33
T42<Herrie1982> We have a mainline build on LuneOS side ready too in general, toyed with it in the past21:34
T42<Herrie1982> Build infra is flexible enough to switch easily between mainline/Halium :)21:34
malI have some iommu patches for msm8974 which I really should cleanup and push somewhere, with those I can use gpu in mainline21:34
T42<Herrie1982> Those would be nice indeed!21:35
malI also should test my camera patches for msm8974, I made some clean versions based on some hints of the old hacks21:36
T42<supirlelik96> journalctl telent
T42<supirlelik96> I'm going to launch sfos4 the last port on hibris16 and the device is stuck on the redmi logo (edited)23:34
T42<supirlelik96> journalctl telent
T42<supirlelik96> I'm going to launch sfos4 the last port on hibris16 and the device is stuck on the redmi logo23:38
T42<supirlelik96> port arch=aarch64 (edited)23:38
T42<supirlelik96> journalctl telent
T42<supirlelik96> console ramoops-0:
T42<supirlelik96> I'm going to launch sfos4 the last port on hibris16 and the device is stuck on the redmi logo23:39
T42<supirlelik96> port arch=aarch64 (edited)23:39
T42<supirlelik96> journalctl telent
T42<supirlelik96> console ramoops-0:
T42<supirlelik96> I'm going to launch sfos4 the last port on hybris16 and the device is stuck on the redmi logo23:39
T42<supirlelik96> port arch=aarch64 (edited)23:39
T42<supirlelik96> Please help­čÖĆ23:57

Generated by 2.17.1 by Marius Gedminas - find it at!