rajivr has joined #nixos-aarch64
ky0ko has joined #nixos-aarch64
veleiro has joined #nixos-aarch64
tilpner_ has joined #nixos-aarch64
tilpner has quit [Ping timeout: 240 seconds]
tilpner_ is now known as tilpner
jb55 has quit [Remote host closed the connection]
jb55 has joined #nixos-aarch64
h0m1 has quit [Ping timeout: 260 seconds]
h0m1 has joined #nixos-aarch64
cript0nauta has joined #nixos-aarch64
quinn has joined #nixos-aarch64
ajs124 has quit [Quit: killed]
ajs124 has joined #nixos-aarch64
srk has quit [Ping timeout: 240 seconds]
srk has joined #nixos-aarch64
jb55 has quit [Remote host closed the connection]
jb55 has joined #nixos-aarch64
jb55 has quit [Remote host closed the connection]
jb55 has joined #nixos-aarch64
jb55 has quit [Remote host closed the connection]
jb55 has joined #nixos-aarch64
jb55 has quit [Remote host closed the connection]
jb55 has joined #nixos-aarch64
ky0ko has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
ky0ko has joined #nixos-aarch64
jb55 has quit [Remote host closed the connection]
jb55 has joined #nixos-aarch64
cript0nauta has quit [Remote host closed the connection]
cole-h has quit [Ping timeout: 240 seconds]
Darkmatter66 has quit [Ping timeout: 260 seconds]
<pbb> What is the difference between cma= kernel parameter and gpu_mem= firmware setting?
<samueldr> cma= can be used for anything
<pbb> but it achieves the same?
<samueldr> not sure what gpu_mem is though
<pbb> I found it in the Pi 4 wiki entry
<samueldr> not really
<samueldr> gpu_mem is a config.txt thing, no?
<pbb> yes
<pbb> "firmware setting"
<samueldr> right
<samueldr> cma= is a kernel setting
<samueldr> we were previously setting it on the kernel command-line
<pbb> so you would need both to actually do something?
<pbb> or is one of them enough?
<samueldr> but it's not great because of reasons that we've seen in the PR you rebased
* samueldr re-opens the PR to remember what failed
<pbb> let me rephrase the question: what would be the best way to set the gpu memory size / cma (assuming that's essentially the same thing) when using u-boot?
<pbb> I would like to update the wiki with a new example using dtmerge and u-boot
<pbb> (for enabling gpur
<pbb> *gpu)
<samueldr> I'm pretty sure you don't set it at all on Linux's side
<samueldr> I'm not sure if gpu_mem from the firmware ends up used though
<samueldr> that's a raspberry pi specific that I don't know
<samueldr> clever maybe knows, depending on whether earlier raspberry pis did the same
<samueldr> (though clever might not be around)
<pbb> okay, thanks. let's see if someone else knows
<samueldr> though, now that cma= is not set on the command-line, it will use the defaults from the platforms
<samueldr> which the device trees can set
<samueldr> AFAIUI we now shouldn't touch nor recommend touching the cma parameter by default
<samueldr> I guess if the user needs it for *reasons* they can
<pbb> okay
<samueldr> the latter is the cma reservation for the pi 4... when set by the kernel command-line, the cma reservation happens too high in-memory
<samueldr> I assume the "best" way to set it up would be through a dtb overlay, for what it's worth
<samueldr> though I really only know as much as I learned for #97883
<{^_^}> https://github.com/NixOS/nixpkgs/pull/97883 (by samueldr, 15 weeks ago, merged): Use U-Boot for the Raspberry Pi 4-specific image
<samueldr> I'd really like to see good notes about this, too
<samueldr> it seems there's a lot of cargo-culting about that
<samueldr> reading around, it seems the CMA is often conflated with gpu mem because the pi may be able to request gpu memory if needed from the CMA https://elinux.org/RPiconfig#CMA_-_dynamic_memory_split
orivej has joined #nixos-aarch64
Asmadeus has quit [Ping timeout: 272 seconds]
veleiro has quit [Remote host closed the connection]
Asmadeus has joined #nixos-aarch64
wavirc22_ has joined #nixos-aarch64
wavirc22 has quit [Ping timeout: 256 seconds]
<gchristensen> guh this machine won't boot b/c its clock is skewed and my cert is "expired" or not yet valid
lgcl has joined #nixos-aarch64
<simpson> Hm, a curious puzzle.
cole-h has joined #nixos-aarch64
<gchristensen> ah ha, I can ask ipxe to ntp before chaining to https
alpernebbi has joined #nixos-aarch64
cole-h has quit [Ping timeout: 256 seconds]
Cadey is now known as Guest57365
Guest57365 has quit [Killed (egan.freenode.net (Nickname regained by services))]
<DigitalKiwi> i have a laptop that keeps resetting the time to the distant future :/
<DigitalKiwi> Wed Jan 1 12:08:32 AM UTC 2098
<DigitalKiwi> think it maybe needs a new bios battery? lol
<simpson> Possibly.
<DigitalKiwi> why's it go to the future though shouldn't it got to 1970? maybe it's too powerful
<FireFly> huh, good question
<FireFly> weird timestamp
alpernebbi has quit [Quit: alpernebbi]
<lgcl> i am trying to boot get a rockpro64 setup with an encrypted root fs. i have an unencrypted fat /boot and see the boot menu and u-boot retrieving the kernel/initrd, but after starting the kernel, the attached screen just turns off. does anyone has an idea what i might be doing wrong?
<flokli> gchristensen: ipxe doesn't write to hwclock, only to ipxes clock.
<flokli> so you might still want to disable resolved, so timesyncd can resolve the NTP server address :-P
<Ke> lgcl: you have video in the u-boot?
<{^_^}> systemd/systemd#5873 (by sjoerd-ccu, 3 years ago, open): Can't sync time when time is incorrect due to dnssec
rajivr has quit [Quit: Connection closed for inactivity]
<hexa-> this seems a bit more sensible
<flokli> yeah, saw that
<flokli> it's linked from the issue
<flokli> I mean, I asked if that part could land in 247 :-P https://github.com/systemd/systemd/pull/17535#issuecomment-731345709
<flokli> but 248 it is.
<lgcl> Ke: yes, i see a u-boot version number, boot menu and messages that kernel/initrd are being retrieved. the last message is "Starting kernel ..." and then the screen turns off
Darkmatter66 has joined #nixos-aarch64
<clever> pbb: the firmware bootloader will use gpu_mem to heavily patch start.elf and determine where to load it into ram
<clever> pbb: so gpu_mem has major effects on the system, before it even looks for uboot
orivej has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-aarch64
<Ke> heh, just heard a nice idea of using trustzone to isolate spi-nor from Linux and use that for secure boot write protect
<clever> Ke: in the case of the rpi, the dram controller doesnt have the right features to implement trustzone correctly
<Ke> heh, what about rk3399?
<clever> not famaliar with that one
Darkmatter66 has quit [Ping timeout: 272 seconds]
andi- has quit [Quit: WeeChat 2.8]
andi- has joined #nixos-aarch64
lgcl has quit [Quit: ERC (IRC client for Emacs 27.1)]
cole-h has joined #nixos-aarch64
yorick has quit [Quit: reboot]
yorick has joined #nixos-aarch64
v0|d has joined #nixos-aarch64
orivej has quit [Ping timeout: 260 seconds]