<samueldr>
I may have clues as to what is going on with the framebuffer
<samueldr>
I have had a wee look at a new phone I got and it's using DRM (Direct Rendering Manager)
<samueldr>
if you have a running pixel 3 you could dmesg | grep -i drm out of a terminal app or adb shell
<samueldr>
pretty sure dmesg should work without any kind of rooting
<danielrf[m]>
samueldr: I have a pixel 3 xl as well btw
<samueldr>
anyway, what I meant with "out of whole cloth" was "new and from nothing"
<samueldr>
danielrf[m] I figure it's your daily driver so you're not about to get it working :)
<danielrf[m]>
yup...
<danielrf[m]>
and it turns out that running dmesg in a shell just says "Permission denied"
<samueldr>
hmm
<samueldr>
oh well
<danielrf[m]>
since i'm running a "user" build with a re-locked bootloader
<samueldr>
do you have the normal recovery?
<samueldr>
maybe a TWRP or something would allow you to look
<samueldr>
(through adb shell)
<samueldr>
maybe even the default one?
<samueldr>
or even that new userspace fastboot thing
<samueldr>
the phone in question where I spotted DRM is my daily driver, so no fun there for now
<danielrf[m]>
no luck unfortunately.... "fastboot boot" requires unlocking bootloader (which would erase userdata)
<danielrf[m]>
and the recovery doesn't seem to have accessible adb shell
<craige>
IIRC, the phone has TWRP but I've not picked it up since a few weeks after NixCon, been too busy.
<samueldr>
danielrf[m]: I see, no worries then :)
<craige>
oh, wrong message :-D
<craige>
I've give that ADB effort a run later, samueldr
<samueldr>
that's not critical, only clues for a later port
<craige>
I'd like to turn some serious attention to it but life's not allwing it right now. Additionally my PinPhone should be here soon too, it will probably get priority over the Pixel 3 for attention..
<craige>
s/PinPhone/PinePhone/ :-D
h0m1 has quit [Ping timeout: 252 seconds]
h0m1 has joined #nixos-aarch64
<rajivr___>
Thanks samueldr I just finished cross-building nixpkgs stable 19.09.
<samueldr>
great
t184256 has left #nixos-aarch64 ["Error from remote client"]
orivej has quit [Ping timeout: 240 seconds]
zupo has joined #nixos-aarch64
t184256 has joined #nixos-aarch64
chiefgoat has quit [Ping timeout: 240 seconds]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
chiefgoat has joined #nixos-aarch64
chiefgoat has quit [Read error: Connection reset by peer]
zarel has joined #nixos-aarch64
zupo has joined #nixos-aarch64
wavirc22 has joined #nixos-aarch64
Acou_Bass has quit [Ping timeout: 272 seconds]
Acou_Bass has joined #nixos-aarch64
Acou_Bass has quit [Ping timeout: 268 seconds]
Acou_Bass has joined #nixos-aarch64
ryantrinkle has quit [Ping timeout: 265 seconds]
orivej has joined #nixos-aarch64
Acou_Bass has quit [Ping timeout: 272 seconds]
Acou_Bass has joined #nixos-aarch64
ryantrinkle has joined #nixos-aarch64
jakobrs has joined #nixos-aarch64
<jakobrs>
I tried using the image on the wiki with the Raspberry Pi 4, but it's stuck at the splash screen.
<jakobrs>
Do I need to build the image myself?
ryantrinkle has quit [Ping timeout: 265 seconds]
wavirc22 has quit [Ping timeout: 258 seconds]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
wavirc22 has joined #nixos-aarch64
<jakobrs>
All right, I tried to build the image myself, but it's failing because I'm on x86_64 and I'm trying to compile for aarch64.
<jakobrs>
What command do I use to build the image?
ryantrinkle has joined #nixos-aarch64
wavirc22 has quit [Ping timeout: 258 seconds]
wavirc22 has joined #nixos-aarch64
<jakobrs>
Progress update: "Can't find default configuration arch/x86/configs/bcm2711_defconfig" using
<jakobrs>
Apparently this is because make is missing 'ARCH=arm'
jakobrs has left #nixos-aarch64 [#nixos-aarch64]
<thefloweringash>
The “raspberryPi” system is for old 32 bit arm (armv6l), you probably want “aarch64-multiplatform”
<thefloweringash>
and I was too slow
<thefloweringash>
Something in the rpi4 boot has a splash screen?
<clever>
thefloweringash: what does it look like?
<thefloweringash>
I have no idea, I was trying to understand “I tried using the image on the wiki with the Raspberry Pi 4, but it's stuck at the splash screen.”
<clever>
thefloweringash: it could be the standard rainbow that all rpi firmware shows
<thefloweringash>
If you put in a blank sd card does it just hang there?
<clever>
thefloweringash: the rpi4, with no sd card, will blink the status led a certain number of times, in a loop
<thefloweringash>
I’m not an rpi owner, so I can’t really help with diagnosing failures
<thefloweringash>
The rpi4 image should JustWork, right?
<clever>
yeah
Thra11 has joined #nixos-aarch64
laduke-13 has quit [Quit: WeeChat 2.7]
jakobrs has joined #nixos-aarch64
<samueldr>
sounds like the rainbow, and sounds like they used the generic image which doesn't support the 3
<samueldr>
oops, the 4
<jakobrs>
I did use the raspberry pi image; I suspect the Pi image on the wiki is for the Pi 3, not the Pi 4
<jakobrs>
setting crossSystem to aarch64-multiplatform doesn't change anything, however I noticed something:
<jakobrs>
The derivations that are being build very clearly have kernelArch set to x86_64 instead of arm64
lovesegfault has quit [Ping timeout: 260 seconds]
<jakobrs>
Which is probably because nixos/default.nix doesn't actually have a crossSystem argument
<samueldr>
we don't have a "pi image" AFAIK, if downloaded from the nixos hydra, it's the generic image (which by default has the raspberry pi u-boot setup)
<jakobrs>
Yeah,
<jakobrs>
and I'm trying (and failing) to build the rpi4 image (from modules/installer/cd-dvd/sd-image-raspberrypi4.nix)
<samueldr>
when mainline starts supporting the 4, the same image will be made to work for it too
<samueldr>
nixos systems assume you can do native compilation
<samueldr>
(true) cross-compilation is still a WIP
<samueldr>
though we do have that image building for unstable
<samueldr>
it's not built with the expected generic image layout and may have some sharp edges still
<samueldr>
it's using the raspberry pi foundation's kernel fork
<jakobrs>
Oh, thanks
<samueldr>
note that I planned for this image to never make it into a stable release, since mainline support for the pi 4 is still a WIP, it will be deleted from the coming 20.03 release, but still be present in unstable up until mainline linux works
<jakobrs>
I'll try using that image
<jakobrs>
How am I *supposed* to set crossSystem for nixos?
<bennofs>
lopsided98: do you have emmc working with your 5.4 ayufan rock64 kernel?
<lopsided98>
bennofs: yes
<bennofs>
lopsided98: are you using mainline uboot? (from nixpkgs unstable)
<lopsided98>
yes
<bennofs>
somehow, I always get boot failures (blk_update_request for the emmc) on cold boots
<bennofs>
but it does work if I reboot after booting 4.4 successfully first
<lopsided98>
I have never had any issues with the eMMC on the Rock64 (although it is unreliable on my RockPro64)
<bennofs>
do you know what mmc chip you have?
<lopsided98>
Foresee, purchased from Pine64 store
<bennofs>
hmm ok, that seems exactly the same chip as mine (foresee NCEMAM8B)
<bennofs>
weird. it also works fine with unpatched mainline, which I find surprising. I just noticed that mainline is 5.4.1 (and not 5.4.0), so maybe I'll just try rebasing the ayufan on latest mainline and see if anything got fixed
<samueldr>
I'm having thoughts that operating temperature could affect the issue
<bennofs>
it also fails after reset
<samueldr>
I don't remember which way around, but I think on my dumo it has more issues either from cold boot, or from warm boot
<bennofs>
the only difference I could spot in uboot debug logs was that the SD card initialization (not MMC) wasn't performed after reboot (no long CMD55/CMD41 loop).
<sphalerite>
samueldr: you should have appropriate weather conditions for testing that nicely in Canada now, shouldn't you? :D
<samueldr>
it takes a long time to test the range!