<samueldr>
colemickens: yeah, that the broadcom header is not part of a Free package I think
<samueldr>
not sure though
<colemickens>
almost seems like a gstreamer bug then, if I'm grasping the implications?
<colemickens>
anyway, doesn't matter, I'll send feedback on the patch, can't get distracted
ib07 has quit [Ping timeout: 240 seconds]
ib07 has joined #nixos-aarch64
ib07 has quit [Max SendQ exceeded]
ib07 has joined #nixos-aarch64
alp has quit [Ping timeout: 272 seconds]
cole-h has quit [Ping timeout: 240 seconds]
rajivr has joined #nixos-aarch64
s1ng0c has joined #nixos-aarch64
h0m1 has quit [Ping timeout: 244 seconds]
h0m1 has joined #nixos-aarch64
ib07 has quit [Ping timeout: 240 seconds]
<colemickens>
I would've expected this to be a cache hit, not a miss: nix build github:nixos/nixpkgs/nixos-unstable#legacyPackages.aarch64-linux.firefox
ib07 has joined #nixos-aarch64
<colemickens>
oh wait, never mind, I know this answer, aarch64 doesn't block the channel and think it might be broken on the channel right now,.
<samueldr>
or not broken, but timed out
sds2 has quit [Quit: sds2]
<veleiro`>
I've experienced the same thing colemickens, i think i last used the latest
<veleiro`>
build commit for mobile-nixos
<veleiro`>
for nixpkgs
sds2 has joined #nixos-aarch64
veleiro` is now known as veleiro
veleiro has joined #nixos-aarch64
veleiro has quit [Changing host]
<veleiro>
any of you use orgmode?
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
h0m1 has quit [Ping timeout: 260 seconds]
h0m1 has joined #nixos-aarch64
Acou_Bass has quit [Ping timeout: 256 seconds]
Acou_Bass has joined #nixos-aarch64
patagonicus4 has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
patagonicus has quit [Ping timeout: 260 seconds]
patagonicus4 is now known as patagonicus
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
s1ng0c has quit [Quit: Connection closed for inactivity]
red[evilred] has joined #nixos-aarch64
<red[evilred]>
emacs!
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
<angerman>
hmm... so if I connect a usb3-hdmi dongle to the helios64, maybe I get output? : D
<samueldr>
>> The M.2 SATA bus is shared with SATA Port 1. Therefore if you install an M.2 SATA SSD card, SATA Port 1 (J3) will automatically get disabled. But if you use the M.2 interface for USB modules, the SATA Port 1 (J3) is still enabled and accessible by the system.
sds2 has joined #nixos-aarch64
<samueldr>
there, I now know it's not going to cause some kind of damange
<samueldr>
and there, I know I can still use a USB M.2 module
<samueldr>
and now I'm curious as to what USB M.2 modules I can get
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
<angerman>
samueldr: well I'd be putting some nixos image on it anyway.
<samueldr>
hm?
<samueldr>
you still need a u-boot, and last I checked (a few months back) nothing was upstreamed
<samueldr>
but based off mainline at least
<samueldr>
that's why I said "their u-boot"
<angerman>
I wodner what happens with stock uboot
<samueldr>
there's no build for it
<angerman>
I should get an SD card ready.
<angerman>
samueldr: I have an image for the RockPi4 :D
<angerman>
it's "almost" stock.
<samueldr>
it may work enough, but the DP out is different from HDMI
<samueldr>
so depending on what the rockpi4 does with the DP lanes of the RK3399
<angerman>
Hmm. And I need more network cables. I'm out.
<samueldr>
though I wouldn't use a u-boot for the wrong board
<samueldr>
it's... like running the bios for another computer
<angerman>
guess I'll need to run to the electronics tower.
<samueldr>
and u-boot will load the wrong FDT
<samueldr>
since it'll think it's running on a RockPi4
<samueldr>
all of this *could* lead to damage in the worst conditions
<samueldr>
but unlikely I guess
sds2 has quit [Quit: sds2]
<angerman>
hmm... maybe I should just try their armbian image firs then.
<samueldr>
it's a good idea to check if your board works, if you haven't done that still
sds2 has joined #nixos-aarch64
<angerman>
yea, still lack a network cable. I thought I should have a few somewhere...
<samueldr>
now that I'm done with a few of the things I *needed* to do, I think I'll be looking in the Helio64 situation soon
<angerman>
maybe I need to look in the kdis room.
<red[evilred]>
every time you mention the helios64 my wallet winces
<samueldr>
h e l i o s 6 4
<samueldr>
unless you need a NAS, I wouldn't bother
<samueldr>
but if you need a NAS, it's likely to be quite the neat package
<angerman>
mine is going to eventually replace my QNAP
<red[evilred]>
Well, I currently have that cluster I told you about
<red[evilred]>
I just bought a whole bunch of Pi4 hardware to replace my current cluster
alp has joined #nixos-aarch64
<Ke>
really nice nas, but only 5 slots
<Ke>
now that I did the metadata on ssd, I can't really just stop
<red[evilred]>
I've been trying to replicate hydra's arm64 sdcard build with not much success
<red[evilred]>
the Pi4 image seems to work fine - my issue is working out which of the example configuration.nix files to use and how to get my nixos-rebuilds to be persistent
<red[evilred]>
I keep trying various combinations
<red[evilred]>
is there anything I can do to help with the Pi4 support/
<samueldr>
get mainline linux working
<samueldr>
then we can delete the special image
<samueldr>
u-boot is ready, even
<samueldr>
(I haven't verified the last few releases of the kernel)
alp has quit [Remote host closed the connection]
alp has joined #nixos-aarch64
justanotheruser has quit [Ping timeout: 244 seconds]
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
alp has quit [Remote host closed the connection]
alp has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
alp has quit [Ping timeout: 272 seconds]
justanotheruser has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
<red[evilred]>
okay - that's wierd
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
alp has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
orivej has joined #nixos-aarch64
Darkmatter66 has quit [Ping timeout: 246 seconds]
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
adamzivcak has joined #nixos-aarch64
<red[evilred]>
okay, so if I understand my basic proble
<red[evilred]>
m
<red[evilred]>
it's that /boot at 128M is too small to do a nixos-rebuild
<red[evilred]>
so when I unmount it
<red[evilred]>
and copy all the data into /boot on the root partition
<red[evilred]>
and have the root partition actually marked as bootable
monk has joined #nixos-aarch64
<red[evilred]>
it is still booting from the original /boot partition
<red[evilred]>
so my options are:
<samueldr>
the raspberry pi firmware is terrible, and will only look at FAT32 partitions
<samueldr>
the bootable bit is for u-boot
<red[evilred]>
1. Modify the build to make boot larger than 128M
<red[evilred]>
ahh
<red[evilred]>
Well, if it will only look at FAT32 partitions - there's no way to get it to boot off the root partition
<red[evilred]>
that's good to know
<samueldr>
exactly
<red[evilred]>
now I understand why we need uboot
<samueldr>
that's one reason the raspberry pi is annoying to deal with
<red[evilred]>
that was my missing piece
<samueldr>
u-boot for the raspberry pi help with that
<samueldr>
you might be interested in u-boot with the pi 4
<red[evilred]>
I certainly am
<red[evilred]>
first things first - I need to understand how it works
<red[evilred]>
then maybe I can dig in
<samueldr>
unless you need to deal with "shields" and other hardware nonsense made to interact with the raspberry pi "ecosystem"
<red[evilred]>
oh - and I probably need to get access to the community builder for aarch64 if it currently exists
<srk>
only difference is that I also set `nixpkgs.localSystem.system = "x86_64-linux";` to be able to nixos-rebuild --target-host or deploy via nixus
<Lordcirth>
Unfortunately my PBP always has to compile the kernel, as it has hardware-specific patches. Takes several hours and I can't use all cores without overheating
<srk>
lordcirth: you can save a lot of time by disabling some kernel modules / features
<Lordcirth>
ah
<Lordcirth>
I was thinking about that earlier
<srk>
which are typically not needed on arm hw
<Lordcirth>
Yeah, neoveau and radeon aren't going to matter
<Lordcirth>
Can I apply this on top of wip-pinebook-pro's patches?
<srk>
like nouveau is sort-of kernel in kernel that takes like half of the compilation time :D
<Lordcirth>
really??
<srk>
maybe not half but significant portion of time
<Lordcirth>
I will definitely try disabling it then
<Lordcirth>
I haven't done any package patching in Nix though
Adluc has joined #nixos-aarch64
alp has quit [Remote host closed the connection]
alp has joined #nixos-aarch64
alp has quit [Ping timeout: 264 seconds]
<patagonicus>
Ooh, that's great. I have to compile my kernels anyway since I'm using armv7. Not that the kernel is a significant part of the compile time of the whole system. :D
zupo has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
alp has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
cole-h has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<red[evilred]>
Who else has a aarch64 systems available?
<red[evilred]>
AWS? packet? who else?
<Lordcirth>
red[evilred], for rent, sale, or either?
alp has quit [Remote host closed the connection]
<red[evilred]>
rent
<red[evilred]>
I just need some compile resources today