elvishjerricco has quit [Ping timeout: 272 seconds]
elvishjerricco has joined #nixos-aarch64
h0m1 has quit [Ping timeout: 272 seconds]
h0m1 has joined #nixos-aarch64
lovesegfault has quit [Ping timeout: 260 seconds]
lovesegfault has joined #nixos-aarch64
lovesegfault has quit [Ping timeout: 272 seconds]
lovesegfault has joined #nixos-aarch64
<ashkitten> ooo
<{^_^}> mobile-nixos#120 (by samueldr, 38 minutes ago, open): doc: Add per-device pages
<samueldr> it's been annoying me for a while that I didn't have per-device pages
lovesegfault has quit [Quit: WeeChat 2.8]
FRidh has joined #nixos-aarch64
leonardp[m] has joined #nixos-aarch64
<leonardp[m]> samueldr: i tested with a rpi3 non plus, so ignore the part regarding #82455, my bad :( i am downloading the image right now and will test it on a B+
<{^_^}> https://github.com/NixOS/nixpkgs/issues/82455 (by ertw, 3 weeks ago, open): Raspberry Pi 3 B+ doesn't boot on kernel 5.4.23
leonardp[m] is now known as leonardp
leonardp has quit [Quit: authenticating]
leonardp has joined #nixos-aarch64
orivej has quit [Ping timeout: 260 seconds]
<evils> apparently leonardp beat me to reporting that functional, feel free to let me know if there's anything else i could test on this hardware
<leonardp> it appears to be setup specific so the more the better i think
<leonardp> evils: can check if you get serial output?
<evils> i could try to dig up a serial adapter, got to go AFK for a few hours now though
<evils> the issue with it showing its boot after connecting HDMI is really odd though, i think i had it on 4.19 too, but there it may actually have waited to boot until you connected HDMI
<leonardp> i'm just curious :)
<leonardp> `
<evils> i'll have to check my usual config, today has been all from the hydra image
<leonardp> you can mount the sd card and add the lines to config.txt manually (firmware partition) for a quick test
<evils> well, no time now :(
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Darkmatter66 has quit [Ping timeout: 256 seconds]
Darkmatter66 has joined #nixos-aarch64
tilpner_ has joined #nixos-aarch64
tilpner has quit [Ping timeout: 256 seconds]
tilpner_ is now known as tilpner
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Darkmatter66_ has joined #nixos-aarch64
Darkmatter66 has quit [Ping timeout: 256 seconds]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
FRidh has quit [Quit: Konversation terminated!]
zupo has joined #nixos-aarch64
orivej has joined #nixos-aarch64
FRidh has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
ALLES_bennofs is now known as bennofs
zupo has joined #nixos-aarch64
lovesegfault has joined #nixos-aarch64
<Valodim> samueldr: soo I tried the image on two "Raspberry Pi 3 Model B V1.2"
<samueldr> and?
<Valodim> one of them hangs at "Starting kernel..."
<samueldr> :)
<Valodim> the other shows that, but then nothing anymore
<Valodim> I'll double-check to confirm
<samueldr> what's the display hardware connected like?
<Valodim> HDMI to my projector. No adapter
<Valodim> both of the Pis work as expected with a known working sd card otherwise
<Valodim> (with a kernel version of.. lemme check)
<samueldr> can you try the same image, on different displays?
<Valodim> the working sd card image is a 5.4.28, and I assume has hdmi_force_hotplug=1 set
<samueldr> this sounds like a kernel-side regression with some display configurations, to me
<Valodim> can do
<Valodim> tested on an LG projector now, will check on a monitor
<samueldr> especially if/since we're testing with the same imag
<samueldr> image*
<Valodim> so it works with a Pi 3B on your end?\
<Valodim> ah yes, you said
<samueldr> yes, though tested only one display configuration
<samueldr> I could maybe try and hook it to different displays using different kind of adapters
<Valodim> also weird that my two pis behave differently
<samueldr> now that I know there's at least one confirmed failure with the same image on a 3B (non-plus)
<samueldr> yes, very weird
<samueldr> with the same exact SD card burned from that fresh .img?
<Valodim> I didn't burn it anew inbetween. doing that right now
<samueldr> oh, it should be fine to re-use the same sd card without re-burning, as long as it's the image I asked to test
<samueldr> and that it wasn't edited
<Valodim> oh, ok
<samueldr> the boot process does rehydrate the system, but it shouldn't affect the test for this use case, and if it does, rebooting once should make it a non-issue
<Valodim> unless power is cut off at a bad time :)
<samueldr> yeah :)
<Valodim> results: both pis work correctly on a samsung monitor
<Valodim> one of them also on an lg monitor
<Valodim> I'm now going to try the lg projector with the hdmi cable I used on the monitors
<Valodim> because the hdmi wire that doesn't work is preeetty long. other devices don't seem to have issues with that, but I've had hdmi wires exhibit all kinds of funky behavior, so gonna test that
<samueldr> good call
<samueldr> and it does confirm that it's setup-dependent
<samueldr> sadly, not something we can directly fix, the fix would be kernel-side
<Valodim> haha, it does work
<Valodim> wtf :D
<samueldr> can you write your observations on the issue?
<Valodim> so I unplugged the working hdmi on the projector, and plugged it in the other cable that didn't work before - also on the projector. it still shows an image
<samueldr> that's plausible, I guesss
<Valodim> turned it off and on again - still works
<Valodim> wtf
<samueldr> baseless guess: imagine if the EDID could not be read because of the length of the cable at initialization time by the vc4 kernel driver
<samueldr> it wouldn't be able to set some thing (or anything), but if it did read it, and you simply switch cables, it's business as usual?
<samueldr> oh, the latter is more surprising
<samueldr> maybe a case of "did you try unplugging and plugging back again?"
<Valodim> put it in the other pi, also works now
<Valodim> I'm gonna reflash the image again
FRidh has quit [Quit: Konversation terminated!]
<Valodim> fresh image. still works.
<Valodim> there is one variable: we flashed the working versions with dd conv=fdatasync
<samueldr> :/
<Valodim> that *could* make a difference? but we installed nixos a couple times before without ever using the conv=fdatasync option
<Valodim> (it was only by chance because it came up unrelatedly that we used it now)
<samueldr> I wouldn't think syncing would make that much of a difference
<samueldr> but I don't *know*
<Valodim> works consistently now
<samueldr> o.O what an annoying issue!
<Valodim> ok I wrote *another* sd card, without conv=fdatasync, and put it in a pi on the same hdmi cable that didn't work before
<Valodim> and it works
<Valodim> turned the beamer off and on to make super extra sure. still works.
<Valodim> I dunno man :) I guess the good news is that it works
<samueldr> "fun"
<samueldr> danielrf[m]++
<{^_^}> danielrf[m]'s karma got increased to 2
<Valodim> fwiw, I put the observations in the issue
<samueldr> thank you Valodim++
<{^_^}> Valodim's karma got increased to 2
<Valodim> thank you for looking after this! samueldr++
<{^_^}> samueldr's karma got increased to 197
yvan has quit [Quit: WeeChat 2.7.1]
yvan has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Darkmatter66 has joined #nixos-aarch64
Darkmatter66_ has quit [Ping timeout: 250 seconds]