ajs124 has quit [Quit: Bridge terminating on SIGTERM]
ajs124 has joined #nixos-aarch64
apache8080 has quit [Ping timeout: 276 seconds]
srk has joined #nixos-aarch64
<clever> [root@pikiosk:~]# grep local-cmds /run/current-system/init
<clever> /nix/store/nqwkvgs0c6g35kk0zq9szwmh52w44vxx-bash-4.4-p23/bin/bash /nix/store/s0h61jiych1b13rjfz74ikr4r3nn20r1-local-cmds
<clever> # Figure out device names for the boot device and root filesystem.
<clever> samueldr: i dont know exactly why, but this script was failing on my pi4, when i booted the fresh disk image over usb
justanotheruser has joined #nixos-aarch64
<clever> as a result, the rootfs wasnt expanded, and db.sqlite wasnt initialized
apache8080 has joined #nixos-aarch64
<clever> i only realized it was broken, when all of that magically worked from an SD card
<samueldr> there were a few regressions last month about all that
Asmadeus has quit [Quit: brb... hopefully]
<samueldr> haven't had the time to look more, or even test in depth
<clever> u-boot also had other problems, if a usb keyboard dongle is inserted, it cant usb-boot at all
<clever> and attempting to resize the rootfs manually (either before boot, or live), breaks uboot as well
<samueldr> uh
<samueldr> that's odd
<samueldr> ah, did you add back the "bootable" flag to the partition?
<clever> very
<clever> oh, thats needed, on the ext4??
<samueldr> on the partition where the ext4 fs lives, yes
<clever> that would explain it
<samueldr> u-boot looks for it to know whether it can boot from it or not
<clever> i'm used to the rpi firmware completely ignoring the bootable flag
<samueldr> that's why "fdisk delete recreate" for partitions are terrible
<clever> so i didnt bother preserving it
<samueldr> loses so much info!
<clever> i knew what info i had to preserve (under the closed firmware), and didnt copy anything extra
<samueldr> yeah, that is a u-boot thing
<samueldr> it scans only filesystems for which their partition have the "bootable" flag, OR are GPT EF00
Asmadeus has joined #nixos-aarch64
<clever> i'm also unable to produce a non-uboot disk image with the release.nix stuff
<samueldr> we're not producing raspberry pi images, at all
<samueldr> as supported images
<samueldr> the pi4 image will probably be removed entirely by the next release
<samueldr> I was told that mainline was enough to get you started
<clever> i'm trying to get the kms overlay to work
<clever> which needs very recent changes, from the rpi fork of linux, and a dt overlay
<samueldr> oh, yeah, not sure how the dt overlay will happen with u-boot
<samueldr> you'll probably have to use the things in nixos to pre-bake it
<samueldr> which I don't know much about
monk has left #nixos-aarch64 ["Error from remote client"]
monk has joined #nixos-aarch64
rajivr has joined #nixos-aarch64
apache8080 has quit [Ping timeout: 264 seconds]
patagonicus2 has joined #nixos-aarch64
patagonicus has quit [Ping timeout: 272 seconds]
patagonicus2 is now known as patagonicus
h0m1 has quit [Ping timeout: 240 seconds]
h0m1 has joined #nixos-aarch64
pinkieval has quit [Ping timeout: 240 seconds]
pinkieval has joined #nixos-aarch64
apache8080 has joined #nixos-aarch64
orivej has quit [Ping timeout: 272 seconds]
jumper149 has joined #nixos-aarch64
justanotheruser has quit [Ping timeout: 264 seconds]
apache8080 has quit [Ping timeout: 272 seconds]
apache8080 has joined #nixos-aarch64
awmv has quit [Quit: Connection closed for inactivity]
justanotheruser has joined #nixos-aarch64
<clever> samueldr: i'm having trouble getting hardware.deviceTree.overlays to actually do anything, the dtb coming out of it lacks the overlay...
<samueldr> I don't know much about, never dealt with it
<samueldr> but I've heard of similar experiences here
<samueldr> not sure there was any clear resolution, or at least I don't remember of one
<clever> the overlay also fails to apply until you add `filter = "*rpi*.dtb";`
<samueldr> mainline dtbs IIRC won't work by default as they are compiled without symbols
<samueldr> or something along the line
<clever> i decompiled the mainline blob, and the __symbols__ is present
<clever> i also confirmed the symbols have the right names for the overlay
<clever> samueldr: what about specifying a custom u-boot script?
<samueldr> I haven't had to deal with overlays yet, so I couldn't say
* clever digs
<clever> fdt addr ${fdt_addr}
<clever> fdt resize 1024
<clever> samueldr: if you add this to the u-boot script, and DONT load a dtb file, then you can run on the DTB the firmware passed in
<clever> so you will respect whatever dtoverlay= was present in config.txt
<samueldr> yeah
<clever> but then how do i set such a u-boot script on nixos...
<samueldr> but then there's the issue where mainline really assumes you're using _their_ view of the hardware :(
<clever> i plan to use the rpi fork of linux
<clever> since it has newer drivers for the hw i want to drive
<samueldr> yeah, then in that case it should work fine
<clever> but which file is u-boot going to expect that script in?
<clever> [root@pikiosk:~]# cat /boot/extlinux/extlinux.conf
<clever> TIMEOUT 50
<clever> because this doesnt look like a u-boot script
<samueldr> a boot "script" is compiled
jumper149 has quit [Quit: WeeChat 3.0.1]
<clever> and can that still interface with the extlinux.conf style stuff, or will i need to write a new bootloader for nixos?
<samueldr> and following the generic distro boot rules for looking at partitions, it will look for {,/boot}/boot.scr
<samueldr> I think you can
<samueldr> but you have to drop the DTB lins
<samueldr> lines*
<samueldr> (or FDT?)
<samueldr> FDTDIR I think
<clever> FDTDIR ../nixos/vw8c6pmm21rqyi78zmrb9r00x493n6a2-linux-5.4.79-1.20201201-dtbs
<samueldr> yeah that
<samueldr> u-boot will load (and fail if dtb file is missing from the dir) if FDTDIR is given
<clever> the overlays are already in that dir!!
<samueldr> but yeah, your script won't interface well with generations :/
<clever> what if i just wanted to ditch u-boot entirely?
<samueldr> left as an exercise to the reader
* clever jumps on the hamster wheel
<samueldr> you could look at the raspberry pi 4 sd image generator from before u-boot was introduced
<samueldr> or you could conjure something better that re-uses the existing nixos modules for raspberry pi boot
<clever> > linux_rpi4.src.urls
<clever> yep, thats the one i want
<clever> that may also explain why i wasnt seeing the mainline issues in the dtb
<clever> now, will it still boot? ...
<clever> yep, stage-2!
<clever> ah, /boot/overlays is missing
mvnetbiz_ has joined #nixos-aarch64
mvnetbiz_ has quit [Changing host]
Asmadeus has quit [Read error: error:1408F10B:SSL routines:ssl3_get_record:wrong version number]
<clever> nixos/modules/system/boot/loader/raspberrypi/raspberrypi-builder.sh
<clever> this script is copying everything except the overlays dir
Asmadeus has joined #nixos-aarch64
<clever> samueldr: and i now have overlays working once more!
justan0theruser has joined #nixos-aarch64
justanotheruser has quit [Ping timeout: 272 seconds]
apache8080 has quit [Ping timeout: 276 seconds]
apache8080 has joined #nixos-aarch64
apache8080 has quit [Ping timeout: 265 seconds]
Darkmatter66 has joined #nixos-aarch64
quinn has quit [Quit: ZNC 1.8.1 - https://znc.in]
quinn has joined #nixos-aarch64
JJJollyjim has joined #nixos-aarch64
JJJollyjim is now known as Guest67960
<thefloweringash> pleased to report that the nixos aarch64 iso image JustWorks™ on the utm app for macos
Guest67960 has quit [Quit: authenticating]
Guest67960 has joined #nixos-aarch64
Guest67960 has quit [Client Quit]
Guest67960 has joined #nixos-aarch64
<Guest67960> if only hardware could be as simple as qemu haha
<Ke> utm?
<Ke> virtualization
<Ke> ?
<Guest67960> utm is qemu frontend
<Guest67960> *is a
cole-h has quit [Ping timeout: 272 seconds]
sphalerite_ is now known as sphalerite
zupo has joined #nixos-aarch64
adamzivcak has joined #nixos-aarch64
adamzivcak has left #nixos-aarch64 [#nixos-aarch64]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
adamzivcak1 has joined #nixos-aarch64
adamzivcak1 has left #nixos-aarch64 [#nixos-aarch64]
Guest67960 has quit [Quit: authenticating]
Guest67960 has joined #nixos-aarch64
Guest67960 is now known as JJJollyjim
JJJollyjim has quit [Client Quit]
Guest26650 has joined #nixos-aarch64
Guest26650 has quit [Client Quit]
Guest26650 has joined #nixos-aarch64
Guest26650 has quit [Client Quit]
Guest26650 has joined #nixos-aarch64
Guest26650 has quit [Client Quit]
alpernebbi has joined #nixos-aarch64
adamzivcak has joined #nixos-aarch64
adamzivcak has left #nixos-aarch64 [#nixos-aarch64]
adamzivcak1 has joined #nixos-aarch64
adamzivcak1 has left #nixos-aarch64 [#nixos-aarch64]
luxemboye has quit [Ping timeout: 268 seconds]
adamzivcak has joined #nixos-aarch64
luxemboye has joined #nixos-aarch64
adamzivcak has left #nixos-aarch64 [#nixos-aarch64]
orivej has joined #nixos-aarch64
dev_mohe has joined #nixos-aarch64
dev_mohe has quit [Quit: dev_mohe]
Asmadeus has quit [Quit: boo]
adamzivcak1 has joined #nixos-aarch64
adamzivcak1 has left #nixos-aarch64 [#nixos-aarch64]
adamzivcak1 has joined #nixos-aarch64
<adamzivcak1> Hello, has anyone experience with tmpfs as root on Raspberry Pi 4?
dev_mohe has joined #nixos-aarch64
adamzivcak1 has left #nixos-aarch64 [#nixos-aarch64]
orivej has quit [Ping timeout: 276 seconds]
zupo has joined #nixos-aarch64
dev_mohe has quit [Quit: dev_mohe]
bdju has quit [Read error: Connection reset by peer]
bdju has joined #nixos-aarch64
<Ke> adamzivcak1: I imagine it's absolutely the same as on x86
<Ke> is there something that does not wprk for you?
<Ke> * is there something that does not work for you?
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
adamzivcak has joined #nixos-aarch64
luxemboye has quit [Remote host closed the connection]
luxemboye has joined #nixos-aarch64
zupo has joined #nixos-aarch64
adamzivcak has left #nixos-aarch64 [#nixos-aarch64]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo has quit [Client Quit]
monk has left #nixos-aarch64 ["Error from remote client"]
monk has joined #nixos-aarch64
monk has left #nixos-aarch64 ["Error from remote client"]
monk has joined #nixos-aarch64
Asmadeus has joined #nixos-aarch64
dev_mohe has joined #nixos-aarch64
zupo has joined #nixos-aarch64
awmv has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
dev_mohe has quit [Quit: dev_mohe]
bennofs_ has joined #nixos-aarch64
srk has quit [Remote host closed the connection]
srk has joined #nixos-aarch64
AmandaC_ has quit [Ping timeout: 260 seconds]
AmandaC_ has joined #nixos-aarch64
alpernebbi has quit [Quit: alpernebbi]
AmandaC_ has quit [Ping timeout: 264 seconds]
cole-h has joined #nixos-aarch64
AmandaC_ has joined #nixos-aarch64
orivej has joined #nixos-aarch64
justanotheruser has joined #nixos-aarch64
justan0theruser has quit [Ping timeout: 272 seconds]
rajivr has quit [Quit: Connection closed for inactivity]
dev_mohe has joined #nixos-aarch64
dev_mohe has quit [Quit: dev_mohe]
apache8080 has joined #nixos-aarch64
zupo has joined #nixos-aarch64
apache8080 has quit [Ping timeout: 272 seconds]
jumper149 has joined #nixos-aarch64
<samueldr> artturin: here so I can answer your question more directly?
justan0theruser has joined #nixos-aarch64
<samueldr> (answering on github)
justanotheruser has quit [Ping timeout: 260 seconds]
<artturin> samueldr: okay
<samueldr> haha
<samueldr> well, I already answered
<samueldr> I also invite you to directly open new issues if there are issues like those, or even PRs
<samueldr> but yes, you're most likely right that configs are missing
<artturin> i'll open pr's after testing
<artturin> rn im just trying to get the dock to work so that i can use the tty
<artturin> dock + a keyboard
<samueldr> would be nice to have confirmation it works :)
<samueldr> I think USB OTG doens't work as it is configured right now
<samueldr> I'll have to build a test system on my pine a64-lts to figure out what is wrong maybe
<samueldr> I'm assuming because it didn't seem to work on the pinebook a64
<samueldr> but I'm not even sure it should work that way on the pinebook a64
adamzivcak has joined #nixos-aarch64
adamzivcak has left #nixos-aarch64 [#nixos-aarch64]
<artturin> should i set mobile.quirks.supportsStage-0 to false for now since i want to compile the kernels on my computer since its faster
<samueldr> maybe yeah
<samueldr> that's what I do on the pinephone when hacking on kernel features
monk has left #nixos-aarch64 ["Error from remote client"]
monk has joined #nixos-aarch64
aleph- has quit [Quit: WeeChat info:version]
<artturin> which kernel config is the demo image using
<samueldr> the same kernel config
justanotheruser has joined #nixos-aarch64
<samueldr> yes
<samueldr> let me rephrase
<samueldr> there is no kernel in it
justan0theruser has quit [Ping timeout: 272 seconds]
<samueldr> so there is no "kernel config the demo image is using", so if you were building the full demo system, it'd use the same kernel config as your device does
adamzivcak1 has joined #nixos-aarch64
adamzivcak1 has left #nixos-aarch64 [#nixos-aarch64]
aleph- has joined #nixos-aarch64
apache8080 has joined #nixos-aarch64
cole-h has quit [Ping timeout: 265 seconds]
monk has left #nixos-aarch64 ["Error from remote client"]
monk has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Darkmatter66 has quit [Ping timeout: 240 seconds]
Darkmatter66 has joined #nixos-aarch64