osum4est | new log: https://pastebin.com/pF6LD36f | 00:00 |
---|---|---|
osum4est | what do i need to fix next? autologin, start-user-session, or user@10000.service? | 00:03 |
mal | a lot of android side services fail, which will prevent anything from working | 00:06 |
osum4est | i get [TP]: [ERR]:fwu_start_reflash: Firmware image synaptics_bl71.img not available so i think i need the proprietary vendor drivers | 00:08 |
osum4est | according to https://wiki.postmarketos.org/wiki/Google_Pixel | 00:09 |
mal | focus on the android side issue, that is preventing UI and everything | 00:10 |
osum4est | oh, i thought maybe the drivers were the cause of those issues. where in the log are they? and how do i fix them? | 00:11 |
mal | look for "killed by signal 9" in the logs | 00:11 |
mal | osum4est: didn't you say you had issues with selinux disabling? | 00:12 |
mal | maybe try it again | 00:12 |
osum4est | yes | 00:12 |
osum4est | try disabling it again? | 00:12 |
mal | yes | 00:12 |
mal | it won't work if selinux is enabled | 00:12 |
osum4est | right. just to double check: i don't have to rebuild the whole zip and reflash for that right? i can just "make hybris-boot" and boot the image? | 00:13 |
osum4est | mal, still nope... defconfig: https://pastebin.com/DPZxhqn4 device/google/marlin/marlin/BoardConfig.mk: https://pastebin.com/vMDYPY6w | 00:23 |
mal | so what does it do now? | 00:25 |
mal | flashing kernel should be enough | 00:25 |
osum4est | i made my led turn blue in my init script - which works when selinux is enabled. with selinux disabled the light never comes on, shows the vendors screen for about 15-20 seconds, then reboots | 00:27 |
mal | is it really possible that booloader would prevent disabling selinux? | 00:28 |
mal | *bootloader | 00:28 |
osum4est | if it helps at all my bootloader screen says: "Secure Boot: PRODUCTION" | 00:29 |
mal | no idea what that means | 00:31 |
r0kk3rz | i would've thought those two things are unrelated | 00:32 |
mal | it's way too late already here so I'll go offline now | 00:32 |
osum4est | alright, see ya. thanks for your help. hopefully i can get selinux disabled | 00:32 |
r0kk3rz | osum4est: do you know if you can disable secure boot? | 00:37 |
osum4est | r0kk3rz, haven't found a way, all web pages just talk about unlocking the bootloader, which i've already done of course. this seems like its some separate setting | 00:39 |
r0kk3rz | hmm ok, ive only heard about 'secureboot' with UEFI bootloaders | 00:40 |
r0kk3rz | i assume this is something else | 00:40 |
osum4est | yea. i have to turn that off on my desktop/laptop for booting linux, no idea what it means on an android device though | 00:40 |
r0kk3rz | in that case it means 'only boot signed images' | 00:41 |
r0kk3rz | but obviously it does boot sailfish, so who knows | 00:41 |
osum4est | right? is there a way to disable selinux later in the boot process instead? | 00:42 |
r0kk3rz | i dont think so | 00:42 |
osum4est | maybe it will only boot selinux disabled kernels if they're signed? but will boot any selinux enabled kernel? no idea how to sign it though | 00:43 |
r0kk3rz | this is too far into guesswork land | 00:44 |
r0kk3rz | its simpler to expect that something in the kernel doesnt like selinux being disabled | 00:45 |
osum4est | a few things metion a "ALLOW_DISABLE_SELINUX" flag, if you've heard of it | 00:46 |
r0kk3rz | https://github.com/ghosalmartin/android_device_google_marlin/commit/5828dbc7f584659fbfd7e1b97d502a84d1d0040d | 00:48 |
r0kk3rz | there is also this: https://github.com/ghosalmartin/android_kernel_google_marlin/commit/4b20763cbab4be73d1584086ae79c491f2d3b88f | 00:51 |
osum4est | i've had a few of those verity options a "n" but ill do the rest as well | 00:52 |
osum4est | that defconfig doesn't have the selinux bootparam enabled | 00:55 |
r0kk3rz | try that then | 00:55 |
r0kk3rz | !seen ghosalmartin | 00:55 |
merbot | r0kk3rz: ghosalmartin was last seen in #sailfishos-porters 4 weeks, 4 days, 13 hours, 3 minutes, and 18 seconds ago: <ghosalmartin> mal: hows yours holding up :) | 00:55 |
osum4est | change the kernel command line to his, commented out all the verity stuff and didin't enable the bootparam. i booted, but didn't seem to help https://pastebin.com/w0AjuGVk | 01:01 |
osum4est | enabling the bootparam causes the bootloop and doesnt reach init script | 01:01 |
r0kk3rz | im not sure how far martin got with this device | 01:07 |
r0kk3rz | looks like not far | 01:07 |
T4 | chuvilin was added by: chuvilin | 05:54 |
T4 | <MarcoDS_bit> Just to know, is there any form of encryption in sailfish? | 08:09 |
vknecht | hello... a bit OT since it's in LOS but... with a new(er) kernel I'm getting fence timeouts related to kgsl and mdss_fb https://pastebin.com/Xgmtn6tB | 08:10 |
vknecht | any tip/insight about what to look for ? | 08:11 |
r0kk3rz | @MarcoDS_bit: depends what you mean by encryption | 09:23 |
T4 | <MarcoDS_bit> r0kk3rz: user's data encryption | 09:41 |
r0kk3rz | you can do the sdcard... | 09:42 |
T4 | <MarcoDS_bit> Oh lol | 10:08 |
T4 | <adampigg> rinigus: is is possible to use the OpenCycleMap in offline mode in puremaps? Theyre _soooo_ much better for walking/biking than the OSM ones | 11:39 |
*** OhYash1 is now known as ohyash | 11:50 | |
vknecht | so, what's the dhd submodule revision to use ? 9398ac1 ? | 13:54 |
mal | vknecht: why not latest? | 13:55 |
vknecht | tried to mimic revs/versions as in fp2, still getting unresolvable dhv due to nothing providing libc++/libc/etc. for dhc | 13:56 |
mal | show whole build log of dhv | 13:56 |
vknecht | https://build.merproject.org/project/monitor/nemo:devel:hw:TCL:idol3?arch_armv8el=1&defaults=0&repo_sailfish_latest_armv7hl=1&unresolvable=1 | 13:57 |
mal | vknecht: fp2 uses latest, I just forgot to push it to git | 13:57 |
Its_Mike__ | Hey sailors :) | 14:00 |
mal | vknecht: for some reason that is depending on 64-bit lib | 14:01 |
Its_Mike__ | Tried to build sf 3.0.2.8 recently, but no gui at all. what's the problem? anything's changed with the new version? | 14:01 |
mal | Its_Mike__: it used to work? | 14:03 |
mal | you need to get some logs | 14:04 |
Its_Mike__ | Yes, everything was ok with the previous versions | 14:04 |
mal | can you telnet to the device | 14:04 |
mal | vknecht: there is no need to downgrade submodules | 14:04 |
Its_Mike__ | I guess so, should flash the broken zip file again... | 14:04 |
vknecht | I'll try again with latest dhv | 14:05 |
Its_Mike__ | Ok got telnet. let's grab some logs | 14:12 |
mal | first grab journalctl -b | 14:14 |
Its_Mike__ | Doesn't sounds good... | 14:18 |
mal | ? | 14:19 |
Its_Mike__ | Let me send them for you | 14:20 |
Its_Mike__ | https://paste.ubuntu.com/p/FqcT4mqGvz/ | 14:21 |
Its_Mike__ | and logcat: https://paste.ubuntu.com/p/8HmqPMmD2P/ | 14:21 |
Its_Mike__ | Can iptables and related things caused this problem? | 14:23 |
mal | Its_Mike__: did you make any other changes than building 3.0.2.8? | 14:23 |
mal | Its_Mike__: what was the previously working release? | 14:24 |
Its_Mike__ | Hmm... no? just updated submodules | 14:24 |
Its_Mike__ | It was 2.0.1.11 | 14:24 |
mal | oh, that old | 14:24 |
mal | do you mean 3.0.1.11? | 14:24 |
Its_Mike__ | Uh sorry | 14:24 |
Its_Mike__ | yes :D | 14:24 |
mal | Its_Mike__: you are sure hadn't done any local changes on the device in previous version? | 14:26 |
Its_Mike__ | Yes I'm sure. even re-sync everything with my github repo | 14:27 |
mal | what android base? | 14:28 |
Its_Mike__ | cm 12.1 , 5.1.1 | 14:28 |
Its_Mike__ | Do you remember the firewall problem, mal? | 14:28 |
mal | yes | 14:29 |
Its_Mike__ | Make some changes to kernel for fixing that | 14:29 |
Its_Mike__ | it works well on 3.0.1.11 | 14:29 |
mal | based on those logs the android side display service dies for some reason which causes graphics to fail | 14:29 |
mal | get dmesg also | 14:30 |
Its_Mike__ | Uh that sounds bad :(( | 14:30 |
Its_Mike__ | Sure! | 14:30 |
Its_Mike__ | https://paste.ubuntu.com/p/XgwTn7WgYM/ Here you are | 14:31 |
mal | Its_Mike__: can you pastabin you droid-hal spec file and also check in droid-local-repo what the droid-hal devel rpm has in android-config.h file (the rpm is just a compressed package so you and open it with some extraction tool) | 14:34 |
Its_Mike__ | Sure, let me start ubuntu.. | 14:35 |
mal | the android-config.h /usr/lib/droid-devel/droid-headers/ in the rpm | 14:36 |
mal | +is in | 14:36 |
mal | Its_Mike__: did you sync android source again or something? (don't if you didn't) | 14:37 |
Its_Mike__ | You mean repo sync? | 14:45 |
mal | yes | 14:45 |
mal | vknecht: I know the reason for your issue but not the fix yet | 14:45 |
Its_Mike__ | after second fail, yes :( | 14:45 |
mal | Its_Mike__: did it actually sync anything? | 14:46 |
vknecht | mal, ah, so I can take a break for now, thanks :-) | 14:46 |
Its_Mike__ | I don't think so, just revert some of my useless changes... | 14:47 |
vknecht | but it could be I forgot to commit the dhc submodule update | 14:48 |
vknecht | *dhd | 14:49 |
Its_Mike__ | https://paste.ubuntu.com/p/NcG8KWMrPw droid-hal-*.spec | 14:50 |
mal | vknecht: the issue is the libdiag.so you have in that repo, there did you get that, we need to somehow exclude the dependencies from that, or maybe just %define __provides_exclude something | 14:51 |
mal | *where | 14:52 |
Its_Mike__ | paste.ubuntu.com/p/D55y3NMh2Q android-config.h from rpm package | 14:53 |
Its_Mike__ | Uh sorry : https://paste.ubuntu.com/p/D55y3NMh2Q ^^ | 14:53 |
mal | vknecht: maybe https://github.com/mer-hybris/droid-hal-device/blob/master/droid-hal-device.inc#L92 ? | 14:54 |
mal | Its_Mike__: ok, that looks ok | 14:54 |
Its_Mike__ | The repo sync I've made you mean? | 14:55 |
mal | Its_Mike__: what changes did the sync revert? | 14:55 |
mal | Its_Mike__: I mean the android-config.h looks good | 14:55 |
Its_Mike__ | Uh Ok :) | 14:55 |
mal | if the defines were missing it could have explained the issue | 14:55 |
vknecht | got it from device iirc | 14:55 |
Its_Mike__ | Can't remember exactly! | 14:55 |
T4 | <MarcoDS_bit> Failed to initialize property area again :/ https://paste.ubuntu.com/p/rffhwgJhMX/ | 14:57 |
mal | Its_Mike__: one idea, downgrade libhybris to revision 20bcd5be11fcd82aa9e2e995c4bb37af9c94cbad | 14:57 |
Its_Mike__ | sure! let me try? | 14:57 |
mal | Its_Mike__: do you know how to do that? | 14:58 |
Its_Mike__ | Yes :) | 14:58 |
mal | good | 14:58 |
mal | it's just very common that some people have limited knowledge of git and how to build the a downgraded package with build_packages.sh | 14:59 |
mal | @MarcoDS_bit have you ever had a build that didn't have that error? | 15:01 |
T4 | <MarcoDS_bit> mal: nope actually, I have applied all the suggested fixes from the faq but I still have this | 15:05 |
mal | @MarcoDS_bit can you install strace on the device and try to run droid-hal-init with that | 15:06 |
T4 | <MarcoDS_bit> mal: mhh how to install/use it? | 15:07 |
Its_Mike__ | mal : I understand :) no problem | 15:07 |
mal | @MarcoDS_bit at least it's possible to include it in the image and just run strace droid-hal-init | 15:08 |
mal | and the env stuff that is done in the droid-hal-startup script | 15:08 |
T4 | <MarcoDS_bit> ok I'm trying it | 15:08 |
Its_Mike__ | Got some problems while installing that version of libhybris, try to solve them... | 15:10 |
mal | Its_Mike__: what? | 15:10 |
Its_Mike__ | Let me send the log | 15:11 |
Its_Mike__ | https://paste.ubuntu.com/p/rYNPtGYqjH/ | 15:11 |
vknecht | mal, adding "%define __provides_exclude_from ^%{_libexecdir}/droid-hybris/system/lib64/.*$" in droid-config-idol3.spec ? | 15:13 |
mal | Its_Mike__: sb2 -t $VENDOR-$DEVICE-$PORT_ARCH -m sdk-install -R zypper rm libhybris-tests-upstream-devel libhybris-libsf libhybris-libsf-devel | 15:14 |
mal | vknecht: something like that | 15:14 |
T4 | <MarcoDS_bit> mal: "strace droid-hal-init" makes my phone reboot to download/fastboot mode (?), and I get this https://paste.ubuntu.com/p/mvWtTpc9vj/ | 15:16 |
mal | did you run the stuff from the script before, also you have to mask droid-hal before trying to run droid-hal-init manually | 15:17 |
Its_Mike__ | Done :) | 15:20 |
mal | same behavior? | 15:20 |
Its_Mike__ | About to test it mal... will notice you | 15:21 |
T4 | <MarcoDS_bit> mal: what stuff from what script? I'm sorry for asking but could you guide me please? also droid-hal masked now | 15:25 |
mal | check droid-hal-init service for the script it runs and run everything in it | 15:30 |
T4 | <MarcoDS_bit> I ran everything, the result from "strace droid-hal-init" is the same, and that's strace /sbin/droid-hal-init https://paste.ubuntu.com/p/FXNZKcGh6M/ | 15:45 |
Its_Mike__ | Still have error while installation | 15:48 |
Its_Mike__ | The same log | 15:48 |
mal | Its_Mike__: really, exactly the same error? | 15:50 |
vknecht | hmm, dhv still unresolvable ; maybe rather use __requires_exclude ? | 15:53 |
mal | vknecht: that was my other idea | 15:54 |
mal | vknecht: some combination of those or something | 15:55 |
Its_Mike__ | Yep :( | 16:00 |
Its_Mike__ | Kind of annoying problem :D | 16:00 |
mal | so did the command I gave do anything? | 16:01 |
Its_Mike__ | Just removed those packages... | 16:02 |
Its_Mike__ | Let me try something... | 16:02 |
vknecht | dhv built with only the __require_exclude, tho I see this line in dcd build log: | 16:04 |
vknecht | [ 129s] Provides: bluetooth-rfkill-event-configs droid-config droid-config-idol3 = 0.0.37-1.43.1.jolla droid-config-idol3(armv7hl-32) = 0.0.37-1.43.1.jolla libdiag.so()(64bit) obexd-configs | 16:05 |
mal | Its_Mike__: how did you build the downgraded libhybris | 16:05 |
Its_Mike__ | cd into libhybris directory | 16:05 |
mal | so you didn't build_packages? | 16:05 |
Its_Mike__ | then do git --reset-hard ... | 16:05 |
mal | +use | 16:05 |
mal | only part I'm interesting in is the exact build_packages.sh command you used | 16:06 |
Its_Mike__ | and at the last used the libhybris spec with the build_package command to build it | 16:06 |
mal | exact command | 16:07 |
Its_Mike__ | build_packages.sh -b hybris/mw/libhybris -s rpm/libhybris.spec | 16:07 |
mal | not sure what you are doing wrong because removing the the conflicting packages should fix the issue | 16:07 |
mal | so you need to give whole libhybris.log | 16:08 |
Its_Mike__ | Sure! let me try again... | 16:08 |
Its_Mike__ | to build... | 16:08 |
mal | vknecht: just a comment, you will get a very ugly commit log if you always tag all test builds instead of manually triggering the builds on OBS until it works and then making just one clean commit, it's probably just me but I like to have a clean commit history | 16:09 |
vknecht | ah right will keep that in ming ; seemed to me that touching service file wasn't always sufficient | 16:12 |
Its_Mike__ | Here you are mal, it's the whole log : https://paste.ubuntu.com/p/33DmhZ7jgv | 16:12 |
vknecht | seems ok now libdiag doesn't appear in either log ; thanks a lot mal :-) | 16:13 |
mal | Its_Mike__: that claims you still have libhybris-tests-upstream-devel installed or it tries to install it, check droid-local-repo for that rpm | 16:17 |
mal | Its_Mike__: also check sb2 -t $VENDOR-$DEVICE-$PORT_ARCH -m sdk-install -R zypper if libhybris-tests-upstream-devel | 16:17 |
Its_Mike__ | On it mal, Thanks! | 16:17 |
Its_Mike__ | Removed it from local repo, rebuilding right now, hope it works | 16:21 |
Its_Mike__ | https://paste.ubuntu.com/p/qxhXdtxWnT/ | 16:26 |
Its_Mike__ | Same log I guess... | 16:26 |
Its_Mike__ | Got a random idea, maybe reinstalling platform sdk | 16:27 |
mal | no need | 16:27 |
Its_Mike__ | or installing libhybris manually | 16:28 |
Its_Mike__ | ? | 16:28 |
mal | so you now made sure it's not installed and not in local repo? | 16:28 |
T4 | <elros34> just install it manually via sb2 | 16:28 |
Its_Mike__ | if you mean libhybris-tests-upstream-devel package, yes :) removed from everywhere | 16:29 |
mal | the latest log has different error | 16:29 |
mal | I suggest you remove libhybris sources and reclone it and then checkout the correct revision and try again | 16:29 |
Its_Mike__ | @elros34 : maybe... | 16:30 |
mal | it really shouldn't be this difficult to build a simple package | 16:30 |
Its_Mike__ | :D Yep | 16:30 |
Its_Mike__ | Highly agreed | 16:30 |
T4 | <elros34> I just did the same yesterday, build_packages will not downgrade it for you do it manually | 16:30 |
mal | you might have some remnants from old build in your libhybris source tree | 16:31 |
T4 | <elros34> sb2 -t $VENDOR-$DEVICE-armv7hl -m sdk-install -R zypper rm libhybris-libsf libhybris-libsf-devel libhybris-tests-upstream-devel | 16:31 |
T4 | <elros34> and then something like sb2 -t $VENDOR-$DEVICE-armv7hl -m sdk-install -R rpm -U —force libhybris-0.0*rpm libhybris-devel*rpm libhybris-libEGL*rpm libhybris-libEGL-devel*rpm libhybris-libGLESv2*rpm libhybris-libGLESv2-devel*rpm libhybris-libhardware*rpm libhybris-libhardware-devel*rpm libhybris-libsync*rpm libhybris-libsync-devel*rpm libhy | 16:31 |
T4 | bris-libwayland-egl*rpm libhybris-libwayland-egl-devel*rpm | 16:31 |
mal | @elros34 looks at the latest log he gave, different error | 16:31 |
mal | *look | 16:31 |
Its_Mike__ | Confusing, let me do that | 16:32 |
Its_Mike__ | mal it actually builds the package, it only can't install it on platform target, I guess... | 16:33 |
Its_Mike__ | what package provides libgralloc.so.1 ? | 16:41 |
mal | Its_Mike__: did you do what I said? | 16:46 |
Its_Mike__ | recloning the source? | 16:47 |
mal | yes | 16:47 |
Its_Mike__ | Yeah? | 16:47 |
mal | note that you need to use --recurse-submodules when cloning | 16:47 |
mal | Its_Mike__: I really don't know anymore what you are doing, it's impossible to get the same error in that case | 16:48 |
Its_Mike__ | Just get a bit confused mal | 16:48 |
mal | did you remember to downgrade it after recloning? and also removing any stuff from droid-local-repo | 16:50 |
mal | *any libhybris stuff | 16:50 |
Its_Mike__ | May I ask a noob question? | 16:51 |
Its_Mike__ | Sure , I've removed libhybris packages from local repo | 16:52 |
Its_Mike__ | I should run something like this : git clone --recurse-submodules "url" libhybris ? | 16:53 |
mal | yes, I assumed you did that already | 16:53 |
Its_Mike__ | and then reset to the right reversion ? | 16:53 |
mal | at least you said you did | 16:53 |
Its_Mike__ | Done it without --recurse-submodules tag | 16:53 |
Its_Mike__ | ok reclone it like what I said | 16:55 |
Its_Mike__ | now I should just run git reset --hard "tag" under libhybris? | 16:56 |
Its_Mike__ | " Just want to be sure I'm doing everything right :D " | 16:56 |
mal | yes, I told you already | 16:57 |
Its_Mike__ | Sorry for noob questions :))) | 16:57 |
Its_Mike__ | Rebuilding ... I'll kill myself if it won't works this time xD | 17:00 |
Its_Mike__ | O_O still can't install packages | 17:02 |
mal | what error now | 17:06 |
Its_Mike__ | let me pastebin them | 17:08 |
Its_Mike__ | https://paste.ubuntu.com/p/6kcd38nCMN/ | 17:09 |
mal | are you sure the submodule was downgraded correctly? | 17:10 |
T4 | <elros34> Its_Mike: git checkout 0.0.5.25; git submodule update | 17:12 |
mal | wondering why the version of that package is not 0.0.5.25 but also has some git hash in it | 17:12 |
Its_Mike__ | Let me see guys | 17:21 |
Its_Mike__ | Finally :DD | 17:38 |
Its_Mike__ | Done | 17:38 |
Its_Mike__ | Reinstalled the platform sdk | 17:39 |
mal | that is almost never needed | 17:39 |
Its_Mike__ | I know... but todays adventure with sailfish was too odd for me | 17:42 |
Its_Mike__ | Ok let me build rootfs and see if it comes to gui | 17:43 |
osum4est | mal, still stuck on selinux... any other ideas? tried disabling audit, disabling selinux via bootparam, and disabling verity. also is it possible to use the halium kernel to boot sailfish (since halium supposedly supports marlin, maybe it will be able to disable selinux) | 17:56 |
mal | no idea if halium kernel is compatible | 17:59 |
mal | have a look at halium kernel to see what they have done | 17:59 |
osum4est | actually looks like halium doesnt support lineage 15.1, only 14.1. no idea how marlin is supposed to work since lineage 14.1 isn't available. yea i'll take a look at their boot params and kernel config | 18:00 |
Its_Mike__ | Thanks a lot mal, gui boots finally ! | 18:41 |
T4 | <austenite> hello, For anbox : Failed to mount Android data directory .Has anyone faced this? https://del.dog/sfos-garlic-anbox.sql | 18:51 |
osum4est | mal, is there a way to disable selinux later in the boot process? | 19:05 |
vknecht | @austenite, maybe give some context : which overlayfs patch (unless 3.18 which should have it already ?), which repo used to install anbox, lxc check result, ... | 19:07 |
vknecht | osum4est, maybe setenforce 0, if this command is available ? | 19:09 |
osum4est | after booting into rootfs? | 19:09 |
vknecht | on workstations and servers yes, not sure how that applies to these embedded pixies | 19:12 |
osum4est | yea just tried it, that command doesn't exist | 19:12 |
vknecht | hmm, lemme check something | 19:12 |
vknecht | maybe it's somewhere in there : http://repo.merproject.org/obs/home:/neochapay:/mer:/selinux/latest_armv7hl/armv7hl/ | 19:14 |
vknecht | in libselinux-utils, if you can get to install it | 19:17 |
mal | osum4est: afaik no | 19:17 |
osum4est | actually, how can i check if selinux is disabled? i may have gotten it to boot with the selinux bootparam set to yes | 19:17 |
vknecht | getenforce :-) but there's probably another way, maybe in sysfs or proc | 19:18 |
mal | osum4est: if droid-hal-init and android side services work then it's fine, check dmesg for failing things | 19:18 |
osum4est | mal, boot-hal, hwcomposer, configstore-hal, and gralloc are still getting killed by signal 9, and still have a bunch of "SELinux could not set context" messages. dont see any errors in dmesg | 19:21 |
mal | are servicemanagers running, there should be 3 hw, vnd and normal | 19:22 |
osum4est | looks like vnd and hw are getting killed by process 6. journal: https://pastebin.com/UdKWJAPM | 19:26 |
mal | that is very bad | 19:28 |
osum4est | is selinux still not disabled or is it something else? | 19:28 |
mal | probably not disabled | 19:29 |
mal | do you have selinux=0 in kernel commandline? | 19:29 |
osum4est | yes, the kernel parameters are also at the top of that journal log | 19:30 |
mal | osum4est: what did you change to make it boot now? | 19:30 |
osum4est | not sure really. i have verity disabled, bootparam=y and audit=y, and rebuild and reflash the whole image, rather than just the hybris-boot.img | 19:31 |
T4 | <elros34> make sure you check .config generated when you make kernel not your defconfig | 19:34 |
osum4est | elro34, yea that has the bootparam enabled. it also has "CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=1" but shouldn't that get overriden by the kernel param? | 20:05 |
mal | show the whole dmesg | 20:07 |
mal | preferrably after reboot so it has everything | 20:07 |
osum4est | sure, one sec | 20:07 |
T4 | <elros34> dont know, anyway you should really try to get logs from that failing kernel either via ramoops (flash working kernel and boot failing so it will reboot to working ?) or serial console (jack) | 20:09 |
osum4est | mal, dmesg: https://pastebin.com/BB8Uuu62 elros34: sure i could try that | 20:11 |
mal | osum4est: obviously from device, why would I want host dmesg | 20:11 |
osum4est | oh... didn't even think about that sorry :/ | 20:12 |
osum4est | device dmesg: https://pastebin.com/beceAGUX | 20:14 |
osum4est | see anything in there? for some reason if i boot hybris-boot.img directly it doesn't work, but flashing the whole zip does. i could just be doing something completely wrong though | 20:36 |
mal | well it looks like it's selinux issue but not sure why | 20:37 |
mal | check /proc/cmdline just in case | 20:37 |
mal | and zcat /proc/config.gz | grep SELINUX | 20:37 |
osum4est | huh, bootparam is not set for some reason | 20:38 |
osum4est | yeah for some reason the hybris-boot.img included in the zip has the selinux bootparam unset | 20:43 |
mal | osum4est: you do know that you have to run build_packages.sh -d to included new kernel | 20:46 |
osum4est | nope, that would explain why. still back at square one though. i'll grab the ramoops after the kernel reboots. would there be any point in disabling selinux in the base lineage install? | 20:53 |
mal | base android has no effect on that | 20:56 |
osum4est | mal, here's the ramoops: https://pastebin.com/HqrnGXbq i booted the broken kernel using fastboot and let it reboot into the working flashed boot | 20:58 |
mal | where are the kernel sources for that device? | 20:59 |
osum4est | this? https://github.com/LineageOS/android_kernel_google_marlin/tree/lineage-15.1 | 21:00 |
osum4est | it shows that selinux is disabled in there, but i have no idea why it's panicing | 21:27 |
mal | based on backtrace it could be here but no idea why https://github.com/LineageOS/android_kernel_google_marlin/blob/lineage-15.1/drivers/crypto/msm/ice.c#L1659 | 21:29 |
mal | osum4est: quite near the end Fatal Error: NON_SECURE_WDT | 21:30 |
osum4est | yea i saw that. there's literally only 5 wepages that mention it, and 4 of them are other logs haha | 21:31 |
osum4est | i can try turning off CONFIG_SCSI_UFS_QCOM_ICE=y | 21:38 |
mal | no idea what does, worth a try | 21:41 |
osum4est | build errors... ufs-qcom.c no longer has access to the ice functions | 21:48 |
T4 | <DSstill01> @sorbite thats because chinese guys like to change names of things | 21:53 |
T4 | <elros34> if pfk_kc_deinit is called anyway and it led to crash so maybe don't init it at all (pfk_kc_init) or just disable CONFIG_PFK : https://github.com/LineageOS/android_kernel_google_marlin/blob/lineage-15.1/security/pfe/pfk.c#L359 | 21:56 |
T4 | <NotKit> @MarcoDS_bit you need 64-bit Android strace | 21:57 |
steeeve | vknecht: did you manage to run anbox on your device or you have a crash in android rootfs or other (not specified)? | 22:01 |
osum4est | elros34: interesting. Disabled CONFIG_PFK and i can now reach the init script with selinux disabled. i cannot reach rootfs though, because it cannot mount /data. because /dev/sda33 doesn't exist? there are no /dev/sda* files? | 22:03 |
osum4est | there a bunch of other stuff /dev/ (fb*, msm*, ram*, etc.) but none of my sda partitions | 22:04 |
osum4est | init.log: https://pastebin.com/rFBZdKsE | 22:06 |
osum4est | nevermind, i had another setting disabled that shouldn't have been. i got into rootfs now!!! with selinux disabled!! thank you elros34!!! | 22:13 |
T4 | <elros34> awesome now try config_vt | 22:14 |
T4 | <elros34> also post what setting was disabled so others can benefits | 22:15 |
osum4est | CONFIG_PFK=n was the fix, we should add that to the faq | 22:15 |
osum4est | elros34, config_vt still does not work | 22:19 |
mal | osum4est: nice | 22:23 |
T4 | <elros34> afaik you will need it to get ui | 22:23 |
osum4est | oh, i thought it wasn't actually required? | 22:23 |
T4 | <elros34> I mean config_vt | 22:23 |
mal | osum4est: what do you mean sda33 doesn't exist, it did before | 22:23 |
osum4est | mal, ignore that part, i had another config setting disabled that i shouldn't have disabled. it works fine now with just CONFIG_PFK=n | 22:24 |
mal | ok | 22:25 |
osum4est | so i need CONFIG_VT=y for ui to work? | 22:25 |
T4 | <elros34> I think so, you can fix it :) | 22:27 |
mal | what is the problem with VT? | 22:27 |
osum4est | i can't reach the init script with CONFIG_VT=y also, hw&vndservicemanagers are still getting killed: https://pastebin.com/HijueyqW but no selinux stuff now | 22:29 |
mal | the killing of those is usually selinux related | 22:30 |
osum4est | what else could cause it? because selinux is definitely disabled now. | 22:32 |
mal | not sure right now | 22:33 |
osum4est | here's the ramoops with CONFIG_VT enabled. https://pastebin.com/3auscvVn this time i get "Fatal Error: RPM_ERR" | 22:39 |
*** Piece_Maker is now known as Acou_Bass | 22:40 | |
*** Piece_Maker is now known as Acou_Bass | 23:34 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!