rajivr has quit [Quit: Connection closed for inactivity]
ib07 has quit [Ping timeout: 240 seconds]
red[evilred] has quit [Quit: Idle timeout reached: 10800s]
ib07 has joined #nixos-aarch64
red[evilred] has joined #nixos-aarch64
<red[evilred]>
I guess
<red[evilred]>
I should at least lookup what else I need
rajivr has joined #nixos-aarch64
<red[evilred]>
sphalerite (IRC): also - have to find out if NixOS on this thing needs SD / SATA / M2 / eMMC to run
<red[evilred]>
oh wow - that RAM is spendy
tilpner_ has joined #nixos-aarch64
tilpner has quit [Ping timeout: 260 seconds]
tilpner_ is now known as tilpner
<red[evilred]>
sphalerite (IRC): how much RAM you thinking of putting in it?
<pbb>
colemickens, samueldr: you talked about an issue with booting mainline kernel using u-boot on a raspberry pi a few weeks ago. something with "RD image overlaps OS image". did you find a solution to that?
<pbb>
using sd-image-aarch64.nix as basis works with lts kernel but not with latest kernel
<samueldr>
uh, I don't think I personally experienced it, I must have been only tangentially involved in the discussions
<samueldr>
in the u-boot env there are vars that can be tweaked
<samueldr>
those are seeded by platform-specific defaults IIRC
<samueldr>
`and IIRC those vars include "addr" as part of their names
<pbb>
is this in the generic-extlinux-compatible module or in the u-boot defconfig file or where?
<samueldr>
the env I assumed you'd checked using the u-boot command-line on the device
<samueldr>
otherwise it may be part of the defconfig for some platforms
<samueldr>
IIRC it isn't for some other
<samueldr>
(the command to check the env on-device is "env")
<pbb>
okay. different question: is it possible to boot a mainline kernel using the raspberry pi bootloader?
<samueldr>
AFAIK yes
<pbb>
Thanks. I have no idea what exactly I could try with the u-boot env addr stuff. So I'll try the rpi bootloader first.
h0m1 has quit [Ping timeout: 260 seconds]
h0m1 has joined #nixos-aarch64
Darkmatter66 has quit [Ping timeout: 256 seconds]
<samueldr>
the one that's bigger, you would set it bigger still
<pbb>
there's kernel_addr_r=0x00080000
<pbb>
and loadaddr=0x00200000
justanotheruser has quit [Ping timeout: 268 seconds]
srk has quit [Ping timeout: 240 seconds]
jb55 has quit [Ping timeout: 240 seconds]
srk has joined #nixos-aarch64
<samueldr>
I think it's ramdisk_addr_r
jb55 has joined #nixos-aarch64
<samueldr>
in u-boot, for the raspberry pi it seems to be defined by include/configs/rpi.h
<samueldr>
(for the defaults)
<samueldr>
ramdisk_addr_r=0x02700000
<samueldr>
though I'm less confident in what I'm saying now
<Ke>
sphalerite: I'd guess they produced a big batch now and ship all
orivej has joined #nixos-aarch64
<Ke>
mine was ordered like a month after you guys did
red[evilred] has quit [Quit: Idle timeout reached: 10800s]
orivej has quit [Ping timeout: 246 seconds]
Darkmatter66 has joined #nixos-aarch64
Darkmatter66 has quit [Read error: Connection reset by peer]
Darkmatter66 has joined #nixos-aarch64
srk has quit [Ping timeout: 240 seconds]
srk has joined #nixos-aarch64
Darkmatter66 has quit [Ping timeout: 264 seconds]
veleiro has quit [Ping timeout: 260 seconds]
red[evilred] has joined #nixos-aarch64
<red[evilred]>
Ke, you got a shipping notification?
rajivr has quit [Quit: Connection closed for inactivity]
Darkmatter66 has joined #nixos-aarch64
veleiro has joined #nixos-aarch64
v0|d has joined #nixos-aarch64
cole-h has joined #nixos-aarch64
Darkmatter66_ has joined #nixos-aarch64
Darkmatter66 has quit [Ping timeout: 246 seconds]
s1ng0c has joined #nixos-aarch64
Thra11 has quit [Quit: WeeChat 3.0]
s1ng0c has quit [Remote host closed the connection]
v0|d has quit [Remote host closed the connection]
tilpner_ has joined #nixos-aarch64
tilpner has quit [Remote host closed the connection]
tilpner_ is now known as tilpner
s1ng0c has joined #nixos-aarch64
<s1ng0c>
@samueldr I tried to build example/demo for pinephone but seem build broken due to mobile-nixos/modules/cross-workarounds.nix, could you check
<samueldr>
it's broken *because* of it, but it's not expected to build with cross-compilation because of upstream Nixpkgs
<s1ng0c>
security.polkit.enable and services.udisks2.enable are conclicted with X11 selections
<samueldr>
s1ng0c: assuming you're not building natively on aarch64
<s1ng0c>
no, I have x86_64
<s1ng0c>
cross compiling
<samueldr>
the demo image won't cross-compile, known issue, it's bringing in a *boat load* of stuff that has multiple distinct issues with cross
<s1ng0c>
I tried to add Wayland + Weston to local.nix, it was also not worked :(
<samueldr>
for the time being you can assemble an image by `dd`ing the prebuilt rootfs from an Hydra build on top of the partition from a normal build