Wednesday, 2026-11-04

malyou could use chroot00:22
malthere is no bash in init ramdisk in sailfish00:23
T42<damnbruh2004> how come uname -a in early rootfs displays armv7l GNU/Linux?00:23
mal?00:23
T42<damnbruh2004> This is what i get when booted with wrong mounts via telnet00:24
T42<damnbruh2004> ~ # uname -a00:24
T42<damnbruh2004> Linux (none) 3.10.108-ZXKernel-3.0-Gabboxl #24 SMP PREEMPT Tue Nov 3 23:44:37 UTC 2026 armv7l GNU/Linux00:24
T42<damnbruh2004> did i forget somethhing and got a 32bit kernel + 64bit userspace somehow?00:24
T42<damnbruh2004> oh and the userspace is 64 bit yes00:25
T42<damnbruh2004> */unpacked**-rootfs/rootfs/usr/bin*$ file jolla-clock00:25
T42<damnbruh2004> jolla-clock: ELF 64-bit LSB shared object, ARM aarch64, version 1 (SYSV)00:25
T42<damnbruh2004> as well as the device is 64-bit capable00:25
malwait, what do you have in droid-hal*.spec file00:26
malin rpm folder under ANDROID_ROOT00:26
mallooking at that defconfig location it looks like you have 32-bit kernel indeed, so you accidentally made 64-bit rootfs, that is determined in couple of places00:27
T42<damnbruh2004> not much in the spec https://github.com/fortuna-for-smoothie/droid-hal-fortuna3g/blob/master/droid-hal-fortuna3g.spec00:28
malfirst of all the PORT_ARCH you defined when setting up the build environment00:28
maltry "echo $PORT_ARCH" in your build environment00:28
T42<damnbruh2004> i set 64 bit everywhere it asked00:28
malwhy? you have 32-bit kernel00:28
malpretty sure you can't use 64-bit userspace with 32-bit kernel?00:29
T42<damnbruh2004> i guess i was in a rush lol... i always remembered this phone to be not 32 bit for some reason00:30
malyou only need to redo the middleware build parts00:32
malso cleanup the build artifacts from the folders under hybris/mw/00:32
malso it doesn't have any leftovers from 64-bit build00:32
malno need to remove everything from there, only run "git clean -x -f -d" in the subfolders under there00:33
malmsm8916 is 64-bit soc, but it seems your device is still using 32-bit kernel00:34
Mister_Magister8916 i know this one00:36
Mister_Magisterah osprey, good times00:37
T42<damnbruh2004> i guess i'll have to clean all build intermediates and build from scratch, because packaging droid-hal fails with a linker error on a .o file01:16
malthere couple of those files under system/core I think01:21
malwhich are built during droid-hal packaging01:21
mal@damnbruh2004 a small hint for future, when adding hybris changes to defconfig it's easier to add those all to the end, then you don't have to care if the value is already defined in the file01:28
T42<damnbruh2004> ooo, thanks01:30
T42<damnbruh2004> reagrdless, this time i tried to checked for duplicates and dependent props01:30
T42<damnbruh2004> so now is this the consequence of me changing arch or an actual bug? when rpm/dhd/helpers/build_packages.sh --mw02:09
T42<damnbruh2004> 02:09
T42<damnbruh2004>  /bin/sh ../libtool   --mode=install /usr/bin/install -p   libandroid-properties.la '/home/smooth-e/hadk/external/libhybris/installroot/usr/lib'02:09
T42<damnbruh2004> libtool:   *error:* *error:* cannot install 'libandroid-properties.la' to a directory not ending in /usr/lib6402:09
*** n2klb_ is now known as n2klb02:35
malhow did you cleanup that libhybris source?02:35
malthe sources are in the submodule of it02:35
malso run git clean in the submodule02:35
T42<damnbruh2004> so i did make clean on the root dif, i rebuilt the kernel, i did git clean -fdx in external/libhybris and then i built —mw, however it still fails with the same thing03:05
T42<damnbruh2004> kinda confused of from where libtool gets the assumption to put files into lib6403:06
malyou need to do it int external/libhybris/libhybris03:09
T42<damnbruh2004> oh damn... just noticed03:10
T42<damnbruh2004> well... i recompiled everything for arm7 at this point and the same thing happens as before04:21
T42<elros34> are you sure. 'file /target/usr/bin/busybox-static' shows correct arch?04:34
T42<damnbruh2004> for some reason, the answer to this is no...04:44
T42<damnbruh2004> at this point i guess my build environment is all messed up04:45
T42<damnbruh2004> i will start from scratch tomorrow or someday later04:45
T42<damnbruh2004> because now it does not even boot when i provide broken mountpoints and ask for debug04:45
T42<damnbruh2004> thanks all for your support!04:46
T42<elros34> did you install correct target and remove aarch64 one?04:46
T42<damnbruh2004> yes04:46
T42<damnbruh2004> i changed the port arch env var, then removed and installed new target, then make clean for the android thing, then cleaned all submodules and repos i could think of and then did all the steps from building the kernel to packaging the rootfs04:47
T42<elros34> so echo $PORT_ARCH is correct?04:48
T42<damnbruh2004> armv7hl it is04:49
T42<elros34> what about droid-local-repo/ directory. Does it have aarch64 or arm packages?04:49
T42<damnbruh2004> i cleaned it before rebuilding. now it has only noarch and armv7hl packages04:50
T42<elros34> so it should be good. In same place when you have built sfos image there should be .packages file.IIRC it should have names of all installed packages. Does it have also armv704:52
T42<damnbruh2004> yes it does04:54
T42<elros34> so maybe you just mixed sfos images or nstallation failed. I see no reason for incorrect busybox-static04:54
T42<elros34> after all it's all about last step build_packages.sh --mic. This creates image using *.ks file from local repo and jolla repos04:57
T42<elros34> If ks file is correct and script set correct arch then should be fine04:57
T42<damnbruh2004> i re unpacked the image again to see it's content and it reports correct arch. Perhaps some kind of a wsl filesystem delay05:07
T42<damnbruh2004> idk at this point05:07
T42<damnbruh2004> reinstalling the image now, let's see05:08
T42<damnbruh2004> no05:22
T42<damnbruh2004> i installed and can confirm from twrp that userspace busybox is a 32 bit binary05:22
T42<damnbruh2004> however, correct mounts or not, hybris-recovery or standard hybris-boot, init_enter_debug2 or no such thing, the result is the same and it isn't a good one05:23
T42<damnbruh2004> a bootloop with no logs05:23
T42<damnbruh2004> im off to get some rest now, bye!05:25
abrMister_Magister: does 'doesn't show anything' mean it shows the browser bar with a blank white page, or less than that?06:57
abrand I guess this is esr115 on sfos 5.2?06:57
Mister_Magisterabr: yeap, and the browser page is black on my website and white on jolla's website08:22
Mister_Magisterabr: and its 5.2 yes08:38
abrhmm that's even weirder. can you get any other colours?08:49
abre.g. is wikipedia a sort of light grey?08:49
Mister_Magisterabr: wikipedia is black09:01
abrok so it's not the base colour09:01
Mister_Magisteri can dump you about:config or smth if that help09:02
Mister_Magisterlike saving to pdf works09:02
Mister_Magisterit is the oldeset supported sfos device so have that in mind09:03
abrwhich one is it? and which kernel? i made sure it worked on mesa, but it's possible that something really old just can't do the modern gfx09:04
Mister_Magistermotorola moto g2, 3.409:04
abrany errors in the journal or even dmesg would be nice09:04
Mister_Magisterno errors when launching it by hand or in dmesg or in journal09:04
Mister_Magisterthats why its interesting, no errors whatsoever nothing obvoius09:07
Mister_MagisterLike i can scroll the white page09:07
Mister_Magisterwhen i scroll commerce.jolla.com to the bottom there's black bar at the bottom09:07
Mister_Magisterso it like works but doesn't09:08
Mister_Magisteror more like everything on backend works but doesn't display properly09:08
Mister_MagisterI'd really appreciate help in fixing it because i'd love to keep this port going :)09:10
abri'll have a look to see if there's anything missing in 3.4 that gecko really needs. we've jumped a good couple of years or so between 91 and 115 and it's possible they just expect things. should check the min kernel req of gecko.09:16
abrdoes it have a usable /dev/shm?09:25
abrMister_Magister: see if MOZ_GL_DEBUG_VERBOSE=1 sailfish-browser gives more info09:51
abrif not then: env QSG_INFO=1 EMBED_CONSOLE=1 MOZ_LOG="timestamp,EmbedLite:5,EmbedLiteTrace:5,Layers:5" /usr/bin/sailfish-browser > "$HOME/browser-render.log" 2>&109:52
Mister_Magisterabr: sorry i'm eepy boi, /dev/shm does indeed exist10:25
Mister_Magisterabr: MOZ_GL_DEBUG_VERBOSE=1 sailfish-browser doesn't spit anything more useful10:27
Mister_Magisterhttps://paste.opensuse.org/pastes/a6ba8f72aacb10:27
Mister_Magisterabr: your log sir https://paste.opensuse.org/pastes/78a02a67923910:28
abrexactly which versions are you on? rpm -q xulrunner-qt5 qtmozembed-qt5 sailfish-components-webview-qt5 sailfish-browser10:33
Mister_Magister5.2.0.2210:35
Mister_Magisterah10:35
Mister_Magisterthe rpms10:35
Mister_Magisterxulrunner-qt5-115.40.0+git1-1.33.1.jolla.armv7hl qtmozembed-qt5-1.56.4-1.33.1.jolla.armv7hl sailfish-components-webview-qt5-1.7.4.1-1.24.1.jolla.armv7hl sailfish-browser-3.0.3-1.24.1.jolla.armv7hl10:36

Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!