<elvishjerricco>
Anyone have any tips for debugging my android kernel not working with the rpi's hdmi? I can ssh in and check out journalctl but nothing stands out to me. Would it be in stage 1 or stage 2?
<samueldr>
elvishjerricco: does uboot show up?
<elvishjerricco>
samueldr: Yea the thing boots; I'm SSH'd in right now
<samueldr>
I mean, does uboot work on the HDMI display?
<elvishjerricco>
OH
<elvishjerricco>
yea
<elvishjerricco>
it does
<elvishjerricco>
It say "Starting kernel" or whatever then the whole screen goes black
<samueldr>
ah, then it's probably not something obvious with config.txt disabling the output :)
<elvishjerricco>
heh, no probably not
<samueldr>
though, do you have any differences with the aarch64 default image's config.txt?
<elvishjerricco>
Don't think so
<elvishjerricco>
I think the main source of difference is going to be my kernel config file
<samueldr>
(I'm downloading the aarch64 image to at least verify it should work with the mainline kernel shipping with it)
<samueldr>
are you building with modules?
<elvishjerricco>
samueldr: I have the 3 b +, which required 4.18 at least
<elvishjerricco>
I am, I think?
<samueldr>
oh, I don't have the 3b+, won't try then :/
<samueldr>
(in case it's an issue with a peculiarity of it)
<elvishjerricco>
Regular mainline linux 4.18 does work fine; screen and all
<elvishjerricco>
but android-mainline-tracking from 4.18 does not show the screen
<samueldr>
ah, that's good, would it be hard to do a lsmod on both and diff?
<elvishjerricco>
Good idea
<samueldr>
I'm kinda thinking something like not building its modesetting driver or vc4
<samueldr>
(though unlikely)
<elvishjerricco>
Gotta rebuild my kernel now; brb :P
<elvishjerricco>
Huh. All of a sudden my nix expression stack overflows....
<elvishjerricco>
samueldr: And here it is from the mainline linux build: Module Size Used by btsdio 16384 0 brcmfmac 278528 0 brcmutil 16384 1 brcmfmac hci_uart 73728 0 btbcm 16384 1 hci_uart cfg80211 733184 1 brcmfmac vc4 167936 3 bluetooth 516096 5 btsdio,hci_uart,btbcm cec
<samueldr>
maybe doing the same on the mainline kernel that work could reveal differences, though I don't see anything outright wrong, not sure if it would show up in there...
<samueldr>
(I'm mostly throwing things I would try around)
<elvishjerricco>
samueldr: Is the `ASoC: no DMI vendor name!` not worrisome?
<elvishjerricco>
(And your throwing things around is better than my no idea of what to do :P)
<samueldr>
that warning (in a not too old checkout) seems to come from "sound/soc/soc-core.c"
<elvishjerricco>
< is the mainline config and > is the android config
<samueldr>
kinda and kinda not :) updating a PR
* samueldr
wonders about seline
<samueldr>
selinux*
<samueldr>
maybe even the other hardened things
<elvishjerricco>
Yea I dunno what selinux is :P
<samueldr>
and then the binder config options, no idea what they do, but if it's about binding to hardware, maybe it grabs the framebuffer before anything else does?
<Dezgeg>
are you expecting to see the virtual console or X11? CONFIG_VT being disabled will drop the virtual console
<samueldr>
selinux does *waves hands* access control management stuff
<samueldr>
haha, good catch there!
<elvishjerricco>
Dezgeg: Oh crap I missed that
<elvishjerricco>
darn android configs disabling that
<samueldr>
darn downstream OEMs breaking it :(
<elvishjerricco>
This is just the android-mainline-tracking branch without any device specific changes or anything
<samueldr>
(I'm talking about my devices, sorry for the confusion)
<samueldr>
either asus or qualcomm broke that on two kernel revisions
<samueldr>
for two different devices
<elvishjerricco>
Alright, building with a few of the lines from that diff included. Here's hoping...
<Dezgeg>
surely there's a rpi3-with-mainline android port somewhere with the things figured out?
<elvishjerricco>
Dezgeg: Yea the lineage stuff was going to be my fallback if I couldn't get the mainline tracking branch working
<Dezgeg>
I would think 4.14 already has good enough vc4 support to get GPU acceleration
<elvishjerricco>
Dezgeg: There's some specific hardware things about the 3b+ that are only in 4.18. Something about the lan and something else I can't remember... Plus a different dtb
<Dezgeg>
backporting those bits sounds way less work
<elvishjerricco>
Nah. The only work involved here so far has been these 15 lines of kernel config, and I expect that to be enough for now
<Dezgeg>
maybe some distro like fedora has it already sorted out
<elvishjerricco>
I mean mainline already works perfectly
<elvishjerricco>
4.18 actually
<elvishjerricco>
It's really just that android disabled these things I wanted
<elvishjerricco>
Which would have been the case either way
<Dezgeg>
well yes but I presume lineage has the userspace bits sorted out
<elvishjerricco>
userspace bits?
<Dezgeg>
to actually run android
<elvishjerricco>
Ah
<elvishjerricco>
Yea but I'm intending on redoing a ton of that kind of stuff anyway just to get it build with nix stuff
<elvishjerricco>
It worked!
<elvishjerricco>
NixOS running on android on an rpi 3 b +, all cross compiled :)
Ericson2314 has quit [Ping timeout: 240 seconds]
Ericson2314 has joined #nixos-aarch64
jtojnar has quit [Quit: jtojnar]
Ericson2314 has quit [Ping timeout: 265 seconds]
FRidh has joined #nixos-aarch64
orivej has joined #nixos-aarch64
ZoomZoomZoom has joined #nixos-aarch64
orivej has quit [Ping timeout: 240 seconds]
globin has quit [Ping timeout: 260 seconds]
ZoomZoomZoom has quit [Quit: Leaving]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Remote host closed the connection]