zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Darkmatter66 has joined #nixos-aarch64
ib07 has joined #nixos-aarch64
knerten1 has joined #nixos-aarch64
knerten2 has quit [Ping timeout: 265 seconds]
alp has joined #nixos-aarch64
orivej has joined #nixos-aarch64
zupo has joined #nixos-aarch64
cole-h has quit [Ping timeout: 258 seconds]
orivej has quit [Ping timeout: 240 seconds]
knerten2 has joined #nixos-aarch64
knerten1 has quit [Read error: Connection reset by peer]
knerten1 has joined #nixos-aarch64
knerten2 has quit [Ping timeout: 240 seconds]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
orivej has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
ib07 has quit [Ping timeout: 240 seconds]
alp has quit [Ping timeout: 272 seconds]
alp has joined #nixos-aarch64
zupo has joined #nixos-aarch64
knerten2 has joined #nixos-aarch64
knerten1 has quit [Ping timeout: 240 seconds]
colemickens has quit [Quit: killed]
Dandellion has quit [Quit: killed]
pinage404[m] has quit [Quit: killed]
fgaz has quit [Quit: killed]
cornu has quit [Quit: killed]
bbigras has quit [Quit: killed]
thefloweringash has quit [Quit: killed]
bennofs[m] has quit [Quit: killed]
yangm has quit [Quit: killed]
JJJollyjim has quit [Quit: killed]
Ox4A6F has quit [Quit: killed]
danielrf[m] has quit [Quit: killed]
codyopel has quit [Quit: killed]
Smith[m] has quit [Quit: killed]
tnias[m] has quit [Quit: killed]
puzzlewolf has quit [Quit: killed]
hsngrmpf[m] has quit [Quit: killed]
Ke has quit [Quit: killed]
Jake[m] has quit [Quit: killed]
leonardp has quit [Quit: killed]
hpfr has quit [Quit: killed]
Danct12[m] has quit [Quit: killed]
Ericson2314 has quit [Quit: killed]
alexarice[m] has quit [Quit: killed]
flo[m] has quit [Quit: killed]
ArtemVorotnikov[ has quit [Quit: killed]
betrion[m] has quit [Quit: killed]
tilcreator has quit [Quit: killed]
blitzclone[m] has quit [Quit: killed]
kyren has quit [Quit: killed]
smrtak[m] has quit [Quit: killed]
lopsided98 has quit [Ping timeout: 260 seconds]
lopsided98 has joined #nixos-aarch64
leonardp has joined #nixos-aarch64
ib07 has joined #nixos-aarch64
alp has quit [Ping timeout: 272 seconds]
knerten1 has joined #nixos-aarch64
rtjure__ has joined #nixos-aarch64
knerten2 has quit [Ping timeout: 246 seconds]
rtjure_ has quit [Ping timeout: 260 seconds]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
rajivr has quit [*.net *.split]
julm has quit [*.net *.split]
taktoa[c] has quit [*.net *.split]
dsal has quit [*.net *.split]
taktoa[c] has joined #nixos-aarch64
rajivr has joined #nixos-aarch64
dsal has joined #nixos-aarch64
julm has joined #nixos-aarch64
Ox4A6F has joined #nixos-aarch64
bbigras has joined #nixos-aarch64
alexarice[m] has joined #nixos-aarch64
Danct12[m] has joined #nixos-aarch64
yangm has joined #nixos-aarch64
codyopel has joined #nixos-aarch64
Jake[m] has joined #nixos-aarch64
Dandellion has joined #nixos-aarch64
bennofs[m] has joined #nixos-aarch64
fgaz has joined #nixos-aarch64
smrtak[m] has joined #nixos-aarch64
bqy has joined #nixos-aarch64
ArtemVorotnikov[ has joined #nixos-aarch64
cornu has joined #nixos-aarch64
betrion[m] has joined #nixos-aarch64
puzzlewolf has joined #nixos-aarch64
hsngrmpf[m] has joined #nixos-aarch64
thefloweringash has joined #nixos-aarch64
colemickens has joined #nixos-aarch64
Ericson2314 has joined #nixos-aarch64
pinage404[m] has joined #nixos-aarch64
blitzclone[m] has joined #nixos-aarch64
danielrf[m] has joined #nixos-aarch64
flo[m] has joined #nixos-aarch64
Smith[m]1 has joined #nixos-aarch64
JJJollyjim has joined #nixos-aarch64
hpfr has joined #nixos-aarch64
tnias[m] has joined #nixos-aarch64
Ke has joined #nixos-aarch64
tilcreator has joined #nixos-aarch64
kyren has joined #nixos-aarch64
rtjure_ has joined #nixos-aarch64
rtjure__ has quit [Ping timeout: 246 seconds]
zupo has joined #nixos-aarch64
alp has joined #nixos-aarch64
<betaboon>
can anyone suggest which nixpkgs-channel to work off of for aarch64 in order to have to compile the least amount of packages ?
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo has quit [Ping timeout: 256 seconds]
zupo has joined #nixos-aarch64
zupo has quit [Client Quit]
orivej has quit [Ping timeout: 256 seconds]
alp has quit [Remote host closed the connection]
rtjure_ has quit [Ping timeout: 246 seconds]
rtjure has joined #nixos-aarch64
alp has joined #nixos-aarch64
tilpner has joined #nixos-aarch64
zupo has joined #nixos-aarch64
bqy has quit [Quit: Idle for 30+ days]
alp has quit [Read error: Connection reset by peer]
alp has joined #nixos-aarch64
alp_ has joined #nixos-aarch64
alp has quit [Ping timeout: 272 seconds]
alp_ has quit [Remote host closed the connection]
alp_ has joined #nixos-aarch64
knerten2 has joined #nixos-aarch64
knerten1 has quit [Ping timeout: 244 seconds]
knerten1 has joined #nixos-aarch64
knerten2 has quit [Ping timeout: 258 seconds]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
ninjin_ has quit [Ping timeout: 240 seconds]
ninjin_ has joined #nixos-aarch64
<betaboon>
when i cross-compile an image for aarch64, boot that on the device, apply the same configuration.nix and run a nixos-rebuild it seems like it wants to rebuild everything, is there a way around that?
<nbp>
nvm, there is a comment above: "Don't enable this on AArch64"
<betaboon>
thanks anyway :D
<nbp>
Looking at both arm64 devices I have, I do not see anything special about the binary caches, and last time I rebuilt, it did download from nixos.org cache.
<nbp>
If there are too many rebuilds, you might try commenting lines and see which one might cause these issue. For example, do you have these issues with a minimal configuration.nix ?
<betaboon>
i just built an image from nixos-unstable, cross-compiled on my x86-system. now running rebuild on the aarch64 device, it is indeed fetching alot of things from cache, tho seems to be building some things as well. i was wondering why it has to rebuild somethings even tho there is no real change
<betaboon>
what's especially annoying: i have built a custom kernel, that got cross-compiled, but the aarch64 system goes on and recompiles it on first rebuild
<nbp>
a few things are always rebuild, such as simple files, such as config files. If you have bigger compile times, it might not be in the things pre-build by the cache, or a configuration caused your evaluation to compute a different hash.
<nbp>
Which is why I asked about commenting out things which are making your configuration unique, to bisect which settings cause this massive rebuild.
<betaboon>
i was wondering if the hash changes because it was first cross-compiled and then compiled on aarch64
alp_ has quit [Ping timeout: 272 seconds]
cole-h has joined #nixos-aarch64
ryantrinkle has joined #nixos-aarch64
alp_ has joined #nixos-aarch64
<nbp>
betaboon: this is certainly true.
<nbp>
betaboon: but in such case it should still be able to pull these from the nixos.org cache.
<nbp>
I recall having at one point installed qemu to ""natively"" build some of the packages instead of cross compiling.
das_j has joined #nixos-aarch64
<das_j>
hey, has anyone had problems with a pi 4 (both 4GB and 8GB) and keyboard in initrd? I can't get it to work for some reason
<clever>
are the usb drivers included in the initrd?
<das_j>
I should also mention that this pi boots with PXE and has no sd card
<das_j>
so maybe I assembled the dtb directories wrong, but that's really hard to know. I can see it requesting the proper files via TFTP and the TFTP server responding
<das_j>
oh nice, is dtparam=sd_poll_once to prevent these timeout warnings for mmc0?
<betaboon>
das_j: iirc that was what i was trying to acchieve with that. dont remember if that worked tho
<das_j>
what do you have in cmdline-raspberrypi-4.txt?
ajs124 has joined #nixos-aarch64
<betaboon>
das_j: i added it to the gist.
<das_j>
oh, thanks
<betaboon>
das_j: that `nfsnixstore` thing is something custom.
<ajs124>
our initrd is just supposed to iscsi at that point (and it does in a test), so that part shouldn't matter
<das_j>
hmm, the configs sadly look pretty similar. I added the last changes from yours
<das_j>
btw, I don't think you need bootcode.bin ;)
<das_j>
(or do you? :O)
<das_j>
It works \o/
<das_j>
what
<betaboon>
das_j: i think you're right for the pi4. i had pi3s and pi4s netbooted in my setup. i think thats why it is still in
<das_j>
I think I was missing the dtparam stuff
<ajs124>
that's just supposed to enable spi, i2c and some sd stuff though, right?
<das_j>
betaboon: If you come to nixcon 2021, be sure to contact me anytime you want free beer ;) (in case you are coming)
<das_j>
probably the spi stuff is needed
<betaboon>
maybe i can make it to nixcon next year :D
<das_j>
imma be right back, time for some celebratory drinks
<betaboon>
das_j: i dont even remember what was completly required for it to work. the whole raspberrypi netboot stuff (dont even call it PXE) is just weird. i had to fiddle around with it for several days to get it working. but that was a couple months ago
<das_j>
yep, ajs124 already spent about half a day just to make the pi do anything with tftp
<das_j>
turns out nobody ever tested non-dnsmasq setups
<betaboon>
I'm running a dnsmasq setup with proxy-dhcp. works quite well atm.
<betaboon>
I'm fine with dnsmasq :D using it as dnsproxy as well to forward the clusters consul-domain etc
rtjure has quit [Ping timeout: 264 seconds]
<ajs124>
it's totally PXE. it even sends an architecture code of 0, so you know its x86/BIOS. very helpful of them.
<das_j>
okay I tried around. `enable_uart=1` is required for USB to work
<das_j>
obviously
<ajs124>
obviously
<betaboon>
ajs124: i wouldn't cosider it being PXE as the whole mechanism of providing `filename` in the dhcp-lease doesnt apply to what the rpi netboot does
<betaboon>
rpi netboot just takes the server-address and assumes it is offering tftp, and that all the files it needs are just in the root-directory of that tftp-server, as if the tftp-server is just a replacement for the sd-card
<ajs124>
nono, it tries to use its own serial number as a folder, before trying the root directory
<ajs124>
and it doesn't just try to boot, you need to send an arbitraty vendor dhcp option which isn't correctly documented (sort of), for it to do anything
<betaboon>
yeah it uses its macaddress for a subdirectory, or you can add a tftp-directory-prefix in the bootloader-config
<betaboon>
yep.
<clever>
betaboon: it can also be a subdir based on the serial#
<ajs124>
because… idk, implementing PXE properly would have been too easy and convenient for users?
<betaboon>
clever: ah ok. never knew.
<clever>
ajs124: PXE typically involves loading x86 based plugins into an existing network stack
<betaboon>
ajs124: i just not seem to get that "It's totally PXE" was sarcastic ? XD
<clever>
ajs124: how would you do that from a VC4 based binary?
<ajs124>
PXE is standardized for EFI, even on AArch64
<ajs124>
but the Pi doesn't do EFI, sure
<clever>
ajs124: and for pre-pi4 models, the dram is not even online yet, so you need to put all of that logic into a 128kb binary
<betaboon>
i think the pi is a weird machine, with weird quirks and still it is hella impressive how capable it is even considering the pricepoint and how it allows a broader audience of people to make experiences
<clever>
the problem is more that to even get efi working, you need a bunch of other files
<clever>
you basically need an SD card, to make it able to efi netboot
Darkmatter66 has quit [Ping timeout: 240 seconds]
zupo has quit [Remote host closed the connection]
Darkmatter66 has joined #nixos-aarch64
zupo has joined #nixos-aarch64
<das_j>
well… while the keyboard works pretty great on the 4GB variant, it does not work on the 8GB variant. any ideas?
<clever>
das_j: does the keyboard work after it has booted fully?
<das_j>
not sure, it does not boot fully yet ;)
<clever>
das_j: this sounds like the vl805 eeprom
<das_j>
I'll tell you once I get there
<clever>
das_j: do you see a chip missing near the headphone jack?
<das_j>
clever: Do I need to flash that manually with the eeprom tool?
<clever>
compare the 2 boards
<das_j>
they look pretty much the same
<clever>
das_j: near the headphone jack, there should be 2 tiny chips, no leads, and more rectangular then square, do you see them?
<ajs124>
we're using linux_rpi4 from nixpkgs-20.03. which is 4.19 with bcm2711_defconfig
<ajs124>
which appears to have this set to Y
<clever>
does the 4gig board have the chip present or missing?
<das_j>
it's present
<clever>
thats likely the key difference then
<clever>
got a serial adapter for the pi?
<das_j>
sadly no
<clever>
but you do have a 2nd pi
<das_j>
but I can use the other one once it's running, right? that's my plan
<clever>
cross-wire the tx->rx tx->rx and gnd->gnd between the 2, and enable the serial port on the 4gig, but dont run a console on it
<clever>
then you can minicom your way into the 8gig pi
<clever>
enable serial again, and console=serial0
<clever>
drivers/usb/host/pci-quirks.c: ret = rpi_firmware_init_vl805(pdev);
<clever>
obj-$(CONFIG_USB_PCI) += pci-quirks.o
<clever>
das_j: oh, interesting, what about that config flag?
<das_j>
cc ajs124
<das_j>
btw, the reason for the second pi is to have something IPMI-like where both pis are able to access each others uart in case something fails ;) so I was going to do that anyway
<clever>
1263 "Failed to load VL805's firmware: %d. Will continue to attempt to work, but bad things might happen. You should fix this...\n",
<das_j>
probably using UART 4 as "client"
<clever>
it may show this message
<das_j>
dmesg?
<clever>
yeah
<das_j>
nope
<das_j>
ah wait wrong pi
<clever>
oh, and dropbear
<clever>
you might be able to ssh into the 8gig, before usb works
<clever>
then you dont need uart
knerten2 has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
knerten1 has quit [Ping timeout: 256 seconds]
rajivr has quit [Quit: Connection closed for inactivity]
knerten has joined #nixos-aarch64
knerten2 has quit [Ping timeout: 256 seconds]
zupo has joined #nixos-aarch64
zupo has quit [Client Quit]
zupo has joined #nixos-aarch64
orivej has joined #nixos-aarch64
alp_ has quit [Remote host closed the connection]
alp_ has joined #nixos-aarch64
zupo has quit [Ping timeout: 256 seconds]
rtjure has quit [Ping timeout: 256 seconds]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
CyberManifest has joined #nixos-aarch64
orivej has quit [Ping timeout: 240 seconds]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
CyberManifest has quit [Quit: Leaving...]
CyberManifest has joined #nixos-aarch64
cole-h has quit [Quit: Goodbye]
CyberManifest has quit [Quit: Leaving...]
orivej has joined #nixos-aarch64
CyberManifest has joined #nixos-aarch64
CyberManifest has quit [Quit: Leaving...]
zupo has joined #nixos-aarch64
knerten1 has joined #nixos-aarch64
knerten has quit [Ping timeout: 240 seconds]
knerten1 has quit [Quit: knerten1]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
ryantrinkle has quit [Ping timeout: 256 seconds]
zupo has joined #nixos-aarch64
zupo has quit [Ping timeout: 272 seconds]
orivej has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-aarch64
v0|d has quit [Ping timeout: 240 seconds]
ryantrinkle has joined #nixos-aarch64
alp_ has quit [Ping timeout: 272 seconds]
alp_ has joined #nixos-aarch64
<craige>
I'm a bit confused this morning - my x86 machine is configured for distributed builds for aarch64 yet when building an SD image for a Pi3 I get: error: a 'aarch64-linux' with features {} is required to build...X11-fonts.drv
<craige>
Has anyone seen that before?
orivej has quit [Ping timeout: 272 seconds]
<samueldr>
yes, maybe colemickens who maybe solved his issue
<samueldr>
but otherwise DigitalKiwi seems to sometimes hit that issue
<samueldr>
craige: ^
<craige>
Thanks samueldr - it's an odd one for me as the build did work, no doesn't. Don't recall making any changes but I _may_ have :-)
<samueldr>
(as for I, I still have never used remote builds that way lol)