<k0ral>
the Nixos image for SD card has a 30MB /boot partition, but as a matter of fact this is insufficient to do a nixos-rebuild
<k0ral>
when I run nixos-rebuild, a linux-4.19.67-Image file is created in /boot/nixos and fills up /boot partition entirely, leaving no space left for any other file to be created
<k0ral>
did I do something wrong ?
orivej has quit [Ping timeout: 245 seconds]
<vika_nezrimaya>
k0ral: the /boot partition isn't a partition anymore, you may be using an old image
<vika_nezrimaya>
newer NixOS SD cards mount FAT32 partition to /boot/firmware (actually they don't even do that! it's noauto in fstab) and use it only for U-Boot
<vika_nezrimaya>
Kernels in /boot/nixos reside on / partition
jtojnar has quit [Read error: Connection reset by peer]
<samueldr>
drop the "/boot" entry from fileSystems
<samueldr>
we're in a rough situation at the moment, where we have two images, the stable 19.03 one where /boot is expected to be NIXOS_BOOT, and the unstable where /boot is on the main partition
<samueldr>
(and the documentation not being updated)
wildtrees has joined #nixos-aarch64
t184256 has left #nixos-aarch64 ["Disconnected: Replaced by new connection"]
t184256 has joined #nixos-aarch64
<k0ral>
ah, looks more consistent with what I observe :)
<k0ral>
btw, this is not named NIXOS_BOOT, but FIRMWARE in my case
<k0ral>
for some reason
<k0ral>
well I guess that's precisely because of this paradigm change :)
<samueldr>
exactly
<samueldr>
(I had forgotten) I made that change so it would willfully be incompatible with the previous naming scheme
<samueldr>
btw, the main reason to switching that around is so that /boot is not limited in size, like it was previously
<k0ral>
and my problem is one good reason for going that direction :)
<DigitalKiwi>
samueldr: would this change make it easier for me to try again to get f2fs working
<samueldr>
I don't think it would
<samueldr>
not saying "it's not possible", just saying it's likely it doesn't matter
<samueldr>
except if, and a big IF, u-boot doesn't support f2fs
<samueldr>
if it doesn't then it actively makes it _harder_
<DigitalKiwi>
oh
<samueldr>
what would make it easier is a likely next step: UEFI-based sd images
<samueldr>
wherein u-boot chainloads to a bootloader that knows abouf f2s
<samueldr>
f2fs*
<samueldr>
so the system, in the end, works more like your run of the mill computer at boot
<DigitalKiwi>
i doubt it's changed but last we checked u-boot doesn't support f2fs
<DigitalKiwi>
how hard is uefi sd images?
<samueldr>
dunno
<samueldr>
maybe trivial, maybe harder
<samueldr>
part of the work I need to do for Mobile NixOS is work on image generation and filesystem generation; work I intend to put back into NixOS for all images
<samueldr>
so I guess that after this is figured out, I would know
t184256 has left #nixos-aarch64 ["Error from remote client"]
t184256 has joined #nixos-aarch64
ryantrinkle has quit [Ping timeout: 258 seconds]
vika_nezrimaya has quit [Remote host closed the connection]
vika_nezrimaya has joined #nixos-aarch64
vika_nezrimaya has quit [Remote host closed the connection]
ryantrinkle has joined #nixos-aarch64
jtojnar has joined #nixos-aarch64
ris has joined #nixos-aarch64
<Thra11>
Got panfrost graphics driver working on NixOS on the RockPro64 :)
<samueldr>
yay!
<samueldr>
Thra11++ for the wiki notes earlier
<{^_^}>
Thra11's karma got increased to 1
<samueldr>
will be useful for the next rockpro64 user with the issue :)
<Thra11>
Indeed.
<Thra11>
Might add a section about panfrost now.
<samueldr>
that would be amazing
<samueldr>
do you know how much of that is generic?
<samueldr>
if you know, or think it is, prefer adding a page under the NixOS on ARM namespace for panfrost :)
<Thra11>
Basically it consists of 1. Build the ayufan mainline kernel sources 2. Build libdrm, mesa and optionally kmscube from git instead of the current releases.
<Thra11>
So hopefully it won't be too long before it just works without any modifications
wildtrees has quit [Quit: Leaving]
ryantrinkle has quit [Ping timeout: 245 seconds]
<Thra11>
Well I've added a short paragraph to the RockPro64 wiki page. Maybe someone will find it useful.
<Thra11>
I look forward to deleting it again when it becomes unnecessary :)
ryantrinkle has joined #nixos-aarch64
ryantrinkle has quit [Remote host closed the connection]
ryantrinkle has joined #nixos-aarch64
wildtrees has joined #nixos-aarch64
wildtrees has quit [Remote host closed the connection]
wildtrees has joined #nixos-aarch64
vika_nezrimaya has joined #nixos-aarch64
vika_nezrimaya has quit [Remote host closed the connection]
<samueldr>
<3 Thra11
<{^_^}>
Thra11's karma got increased to 2
<adisbladis>
What's the state of rpi4 on nixos?
<adisbladis>
Or the other way around ^_^
<samueldr>
(1) waiting on the rpi foundation or mainline kernel to fix the aarch64 issues
<samueldr>
(2) waiting on u-boot to support the rpi4 mainline~ish
<samueldr>
(2.1) they are waiting on the mainline kernel device trees to be finalized
<samueldr>
once (1) is tackled, it'll work fine without the u-boot niceties like selecting generations
<samueldr>
ugh, my irc client is confused
<samueldr>
brb
samueldr has left #nixos-aarch64 [#nixos-aarch64]
samueldr has joined #nixos-aarch64
<samueldr>
adisbladis: #63720 is the tracking issue