elvishjerricco has quit [Ping timeout: 272 seconds]
l-as has quit [Ping timeout: 240 seconds]
dtz has quit [Ping timeout: 240 seconds]
bennofs[m] has quit [Ping timeout: 240 seconds]
siraben has quit [Ping timeout: 240 seconds]
pachumicchu has quit [Ping timeout: 268 seconds]
cornu has quit [Ping timeout: 258 seconds]
noneucat has quit [Ping timeout: 268 seconds]
fgaz has quit [Ping timeout: 268 seconds]
craige[m]1 has quit [Ping timeout: 244 seconds]
kloenk has quit [Ping timeout: 244 seconds]
JJJollyjim has quit [Ping timeout: 244 seconds]
colemickens has quit [Ping timeout: 246 seconds]
puzzlewolf has quit [Ping timeout: 260 seconds]
manveru[m] has quit [Ping timeout: 268 seconds]
thefloweringash has quit [Ping timeout: 268 seconds]
mica[m] has quit [Ping timeout: 249 seconds]
pinage404[m] has quit [Ping timeout: 240 seconds]
chessai has quit [Ping timeout: 274 seconds]
angerman has quit [Ping timeout: 274 seconds]
LinuxHackerman has quit [Ping timeout: 244 seconds]
yangm has quit [Ping timeout: 246 seconds]
Danct12[m] has quit [Ping timeout: 268 seconds]
alunduil has quit [Ping timeout: 264 seconds]
bbigras has quit [Ping timeout: 258 seconds]
hpfr has quit [Ping timeout: 246 seconds]
chessai has joined #nixos-aarch64
angerman has joined #nixos-aarch64
alunduil has joined #nixos-aarch64
lopsided98 has quit [Ping timeout: 268 seconds]
elvishjerricco has joined #nixos-aarch64
lopsided98 has joined #nixos-aarch64
pachumicchu has joined #nixos-aarch64
flo[m] has joined #nixos-aarch64
zaynetro[m] has joined #nixos-aarch64
roberth has joined #nixos-aarch64
Ke has joined #nixos-aarch64
unclechu has joined #nixos-aarch64
Ox4A6F has joined #nixos-aarch64
Dandellion has joined #nixos-aarch64
submoo[m] has joined #nixos-aarch64
fgaz has joined #nixos-aarch64
craige[m]1 has joined #nixos-aarch64
rajivr has joined #nixos-aarch64
Dandellion has quit [Ping timeout: 240 seconds]
Ke has quit [Ping timeout: 246 seconds]
unclechu has quit [Ping timeout: 240 seconds]
craige[m]1 has quit [Ping timeout: 244 seconds]
roberth has quit [Ping timeout: 244 seconds]
Ox4A6F has quit [Ping timeout: 240 seconds]
flo[m] has quit [Ping timeout: 240 seconds]
fgaz has quit [Ping timeout: 240 seconds]
zaynetro[m] has quit [Ping timeout: 258 seconds]
submoo[m] has quit [Ping timeout: 268 seconds]
pachumicchu has quit [Ping timeout: 268 seconds]
veleiro has quit [Ping timeout: 256 seconds]
Danct12[m] has joined #nixos-aarch64
<DigitalKiwi>
gchristensen: it's your favorite feature!
<DigitalKiwi>
A definition for option `networking.hostName' is not of type `string matching the pattern ^$|^[[:alnum:]]([[:alnum:]_-]{0,61}[[:alnum:]])?$'. Definition values:
<DigitalKiwi>
- In `<unknown-file>': "aarch64.nixos.community"
<gchristensen>
great!
yangm has joined #nixos-aarch64
kloenk has joined #nixos-aarch64
cornu has joined #nixos-aarch64
dtz has joined #nixos-aarch64
thefloweringash has joined #nixos-aarch64
pinage404[m] has joined #nixos-aarch64
Ox4A6F has joined #nixos-aarch64
colemickens has joined #nixos-aarch64
leonardp has joined #nixos-aarch64
roberth has joined #nixos-aarch64
Ke has joined #nixos-aarch64
manveru[m] has joined #nixos-aarch64
unclechu has joined #nixos-aarch64
l-as has joined #nixos-aarch64
hpfr has joined #nixos-aarch64
bbigras has joined #nixos-aarch64
LinuxHackerman has joined #nixos-aarch64
siraben has joined #nixos-aarch64
submoo[m] has joined #nixos-aarch64
Dandellion has joined #nixos-aarch64
mica[m] has joined #nixos-aarch64
bennofs[m] has joined #nixos-aarch64
puzzlewolf has joined #nixos-aarch64
Ericson2314 has joined #nixos-aarch64
flo[m] has joined #nixos-aarch64
danielrf[m] has joined #nixos-aarch64
DavHau[m] has joined #nixos-aarch64
fgaz has joined #nixos-aarch64
noneucat has joined #nixos-aarch64
JJJollyjim has joined #nixos-aarch64
craige[m]1 has joined #nixos-aarch64
zaynetro[m] has joined #nixos-aarch64
pachumicchu has joined #nixos-aarch64
Acou_Bass has quit [Ping timeout: 246 seconds]
Acou_Bass has joined #nixos-aarch64
Acou_Bass has quit [Ping timeout: 246 seconds]
Acou_Bass has joined #nixos-aarch64
h0m1 has quit [Ping timeout: 272 seconds]
h0m1 has joined #nixos-aarch64
Acou_Bas- has joined #nixos-aarch64
Acou_Bass has quit [Ping timeout: 240 seconds]
<samueldr>
tmountain: are you sure you _need_ the binary blob TPL?
<samueldr>
AFAIUI all RK3399 boards should be supported by u-boot's own TPL
<samueldr>
(or SPL?)
<tmountain>
samueldr: not 100%, but I have not been able to get an upstream u-boot build to successfully boot up until now.
orivej has quit [Ping timeout: 264 seconds]
<samueldr>
do you have a serial cable to help look at issues?
<tmountain>
samueldr: I have it working
<tmountain>
samueldr: the issue was the disk label...
<tmountain>
samueldr: but I'm using a u-boot image I stole from Armbian
<samueldr>
yes, I mean for a mainline u-boot
<tmountain>
samueldr: ah.. no, but I can order one
<samueldr>
you probably should for your toolchest, always useful
<samueldr>
but that's probably not necessary :)
<tmountain>
samueldr: I'd love to get everything working with strictly upstream.
<samueldr>
tmountain: are you able to test a PR?
<tmountain>
samueldr: should be able to. I am a developer.
<samueldr>
just finishing up the commit to add ubootNanoPCT4 to Nixpkgs
<tmountain>
samueldr: awesome, would love to test that
<samueldr>
tmountain: @tmountain on github?
<tmountain>
samueldr: yes.
<tmountain>
samueldr: I'm signing off in just a few, but I can give it a shot tomorrow
<samueldr>
I'll be pinging you on the PR
<tmountain>
perfect, thank you!
<samueldr>
(I saw you were adding the board to the nixos wiki)
<samueldr>
adding a board already supported by u-boot mainline is extremely trivial
Acou_Bas- has quit [Ping timeout: 246 seconds]
Acou_Bass has joined #nixos-aarch64
veleiro` has joined #nixos-aarch64
veleiro` has quit [Ping timeout: 240 seconds]
<colemickens>
is it time to pull the pi configs into nixos-hardware?
<colemickens>
I still want them without the rest of hte ./sd-image.nix stuff along with it
<colemickens>
Or maybe just keep it in both. maybe it already is and I should've looked before thinking outloud
<samueldr>
what do you mean?
<samueldr>
colemickens: I'm confused by what you said
<samueldr>
but yeah, we probably want "nixos on arm" in nixos hardware at some level
<samueldr>
but be careful: adding the bootloader config (e.g. extlinux) is not a good idea!
<samueldr>
so you're left with not much to add
<samueldr>
what really is there to add to the config?
<colemickens>
why is adding the bootloader config a bad idea?
<colemickens>
that's the part I want, is the bits that drop the rpi config.txt and the right uboot bits, but I want my own partitioning and don't want the installer configs.
<samueldr>
that's because we cannot assume which bootloader config the user uses!
<samueldr>
just like you won't put grub in a thinkpad config
<samueldr>
they would probably want to use the hardware profile for the raspberry pi
<samueldr>
and end-up in a bad situation
<samueldr>
and now I see you're talking abount _image generation_
<samueldr>
which is another topic!
<colemickens>
hm I guess I have slightly different expectations
<colemickens>
and no, I didn't mean image generation :)
<colemickens>
you were right the first time
<samueldr>
uh, ah, mounts setup, rather than partitioning
<samueldr>
right?
<colemickens>
yes, yes, my bad
<samueldr>
no worries, partitioning can be overloaded that way too
<samueldr>
(though maybe with lib.mkDefault it'd be fine?)
<samueldr>
I don't really know how opinionated nixos hardware is and should be
<colemickens>
hm I do feel like there's enough to "extract" and share, though I understand the point about nixos-hardware bits being less invasive compared to what we're talking about.
<colemickens>
even just if they were composed differently in nixpkgs though, I could change my import line and not have to copy/paste. maybe I'm over optimizing for DRY
<colemickens>
don't mind me, I feel like I'm babbling.
<samueldr>
yeah, the images generation thing in Nixpkgs is really... single-minded
<samueldr>
it's really meant for one task only
<samueldr>
(btw, the raspberry pi 4 .nix expression should be deleted soon)
<samueldr>
(since mainline allegedly works)
<samueldr>
(so we're not really left with anything raspberry pi specific in nixpkgs)
<colemickens>
the pi4 one will be deleted, but the general rpi thing is still needed to manage config.txt and their bootloader though
<colemickens>
or am I brain-farting again
<samueldr>
the firmware partition is assumed to be an opaque blob
<samueldr>
like your bios on your computer
<samueldr>
that's the basic assumption
<samueldr>
since it's the basic assumptions on all u-boot supported boards
<samueldr>
we want to, at some point, have a user story to manage u-boot installations
<samueldr>
but only when it is thought about in a way that makes sense generally
<samueldr>
I see the raspberry pi config.txt as an equivalent to fiddle-farting in your computer's bios menus
<samueldr>
sure, it'd be better to have it handled by NixOS
<samueldr>
but it's crossing one line for the time being
<DigitalKiwi>
gchristensen: well now at least i've moved on to missing modules it can't find now :/
<samueldr>
and I really dislike the idea of further making a special place to one vendor in NixOS
blueblockbox has joined #nixos-aarch64
monk has joined #nixos-aarch64
<colemickens>
samueldr: have you thought about chaining bootloaders? I was starting to try to do something like that by adding a rpi4uefi builder that invoked another builder at the end to generate the systemd-boot stuff.
<colemickens>
maybe that could work with what you describe. I could have firmware, and then a totally normal uefi /boot partition and normal aarch64 root
<colemickens>
and I think u-boot could be used the same way based on what I understand
blueblockbox has quit [Ping timeout: 256 seconds]
blueblockbox has joined #nixos-aarch64
blueblockbox has quit [Client Quit]
blueblockbox has joined #nixos-aarch64
cole-h has quit [Ping timeout: 260 seconds]
blueblockbox has quit [Ping timeout: 246 seconds]
alpernebbi has joined #nixos-aarch64
blueblockbox has joined #nixos-aarch64
ib07 has quit [Ping timeout: 260 seconds]
<blueblockbox>
Hi, I am trying to boot on rockpro64 but from time to time I get stuck on `Booting using the fdt blob at 0x1f00000`. I managed to successfully boot using https://github.com/Mic92/nixos-aarch64-images but then after I rebuild nixos it always hangs.
<blueblockbox>
I have tried with both serial and HDMI with boot process hanging at the same time.
<blueblockbox>
I am using latest stable build and uboot 2021.01. I don't really know how to debug this apart from trying different images.
<samueldr>
colemickens: I don't follow about the bootloaders chaining
<colemickens>
samueldr: eh, I was hoping you'd ignored it.
<samueldr>
hah
<colemickens>
I was entirely too tired to be trying to converse last night, I'm sorry.
<samueldr>
no worries
<samueldr>
I like to explore ideas
<samueldr>
I guess the main hangup here is: u-boot is not (only) a bootloader
<samueldr>
its main purpose, first, is bios-like, bootloader is a nice thing tacked on at the end
<samueldr>
I was idly thinking the other day, u-boot could overlay the mainline kernel filename it intrinsically knows about into the FDT
<samueldr>
which in turn an EFI program could use to load the proper dtb file from a folder
<samueldr>
so instead of having grub load your kernel, you'd have it load that intermediary loader; that loader would load the dtb file from the generation's folder, and in turn, "exec" into the kernel
<samueldr>
I had thought of that scheme previously, but the main issue was "but how does grub [or another program] know about the mainline dtb filename??"
<samueldr>
IMO the filename should be a property part of the file
<samueldr>
so if you have socvendor/foobar-baz.dts, you have / { linux,dtbname = "socvendor/foobar-baz.dtb"; };
<samueldr>
this way u-boot could also stop hardcoding weird codepaths for many platforms, instead relying on the (imported from mainline) dtb intrinsics
<samueldr>
some, like pinephone variant detection, would probably still require things to be done
<samueldr>
but that would become the exception I guess
blueblockbox has quit [Ping timeout: 256 seconds]
justanotheruser has quit [Ping timeout: 264 seconds]
justanotheruser has joined #nixos-aarch64
zupo_ has quit [Ping timeout: 256 seconds]
zupo has joined #nixos-aarch64
<DigitalKiwi>
gchristensen: i get an error about modules
<DigitalKiwi>
modprobe: FATAL: Module pci_thunder_ecam not found in directory /nix/store/av96fjk7x7fz4qgm9vavml5488rjgzca-linux-5.4.89-modules/lib/modules/5.4.89
<DigitalKiwi>
that's not the kernel i'm on either :/
<DigitalKiwi>
which might be the cause of the error ? :D
cole-h has quit [Ping timeout: 240 seconds]
orivej has quit [Ping timeout: 240 seconds]
zarel_ has joined #nixos-aarch64
zarel has quit [Ping timeout: 265 seconds]
superherointj has joined #nixos-aarch64
alpernebbi has quit [Quit: alpernebbi]
tilpner_ has joined #nixos-aarch64
tilpner has quit [Ping timeout: 256 seconds]
tilpner_ is now known as tilpner
superherointj_ has joined #nixos-aarch64
<LinuxHackerman>
lol smart element, turning 7\x7 into 7×7
superherointj_ has quit [Quit: Leaving]
superherointj has quit [Quit: Leaving]
superherointj has joined #nixos-aarch64
superherointj has quit [Client Quit]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]