alp has quit [Ping timeout: 272 seconds]
<juliosueiras> serial cable still not shipped
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-aarch64
<veleiro> samueldr: my firmware is installed to SPI for sure
<samueldr> great!
<veleiro> its great like that
<samueldr> what platform?
orivej has quit [Remote host closed the connection]
<samueldr> it's kind of annoying that distributions are assumed to provide the firmware for "cheapo" arm platforms
<samueldr> would you like buying a dell laptop and having to have your distribution deal with the firmware
<samueldr> well... yes. kind of... but that's not what I mean
orivej has joined #nixos-aarch64
<veleiro> platform? PBP and nixos :)
<samueldr> I didn't know what ARM machine you had
<samueldr> (or forgot)
<veleiro> i also have an x200 with libreboot flashed to the spi, been collecting dust
<veleiro> since 2015
<samueldr> it's way too much responsibilities on the shoulders of distros to manage a device's firmware
<samueldr> but at the same time device integrators have shown multiple time they can't provide firmwares :<
<samueldr> it'd be best if instead distros got together with U-Boot into providing golden firmware images
<samueldr> for when a manufacturer doesn't
knerten has joined #nixos-aarch64
jasom has quit [Ping timeout: 244 seconds]
<veleiro> yeah that would be cool
<samueldr> add some fwupd magic behind that
<samueldr> I guess an FDT overlay could give tips for firmware update flows, e.g. goldenfw,booted-from = "spi";
<samueldr> so fwupd knows to update the spi
<veleiro> EULA in fwupd coming soon
<veleiro> thats a more realistic direction, just like the web =()
rajivr has joined #nixos-aarch64
h0m1 has quit [Ping timeout: 272 seconds]
h0m1 has joined #nixos-aarch64
pinkieval has quit [Ping timeout: 256 seconds]
pinkieval has joined #nixos-aarch64
jasom has joined #nixos-aarch64
knerten1 has joined #nixos-aarch64
knerten has quit [Ping timeout: 240 seconds]
orivej has quit [Ping timeout: 265 seconds]
veleiro has quit [Ping timeout: 260 seconds]
orivej has joined #nixos-aarch64
zupo has joined #nixos-aarch64
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 240 seconds]
veleiro has joined #nixos-aarch64
justanotheruser has quit [Quit: WeeChat 2.7.1]
justanotheruser has joined #nixos-aarch64
jasom has quit [Ping timeout: 272 seconds]
jasom has joined #nixos-aarch64
orivej has joined #nixos-aarch64
justanotheruser has quit [Quit: WeeChat 2.7.1]
justanotheruser has joined #nixos-aarch64
orivej has quit [Quit: orivej]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-aarch64
<srk> ,cross
orivej has quit [Ping timeout: 260 seconds]
cole-h has quit [Quit: Goodbye]
justanotheruser has quit [Ping timeout: 265 seconds]
alp has joined #nixos-aarch64
juliosueiras has quit [Ping timeout: 258 seconds]
alp has quit [Ping timeout: 272 seconds]
knerten2 has joined #nixos-aarch64
<Mic92> samueldr: I know have this PR open to fix headless installations: https://github.com/NixOS/nixpkgs/pull/96991
<{^_^}> #96991 (by Mic92, 3 hours ago, open): nixos/installer: enable sshd by default
knerten1 has quit [Ping timeout: 256 seconds]
alp has joined #nixos-aarch64
<Mic92> thefloweringash: do you also have some nixos configuration for rock64 that updates bootloader afterwards? Right now dd'ing the bootloader just bricks the firmware partition.
<srk> it's not that difficult to build custom images with ssh keys but there seem to be a lot of confusion about cross compiling vs native (with qemu-user)
<srk> people doesn't seem to be aware that you can cross compile complete image with just nixpkgs.crossSystem.system and go straight for qemu
<srk> looks like it "just" needs a section in the manual, both for sdImage and for nixpkgs.crossSystem option
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
alp has quit [Ping timeout: 244 seconds]
alp has joined #nixos-aarch64
Darkmatter66 has quit [Max SendQ exceeded]
Darkmatter66 has joined #nixos-aarch64
Darkmatter66 has quit [Client Quit]
Darkmatter66 has joined #nixos-aarch64
veleiro` has joined #nixos-aarch64
Darkmatter66 has quit [Max SendQ exceeded]
Darkmatter66 has joined #nixos-aarch64
Darkmatter66 has quit [Max SendQ exceeded]
veleiro has quit [Ping timeout: 265 seconds]
Darkmatter66 has joined #nixos-aarch64
Darkmatter66 has quit [Max SendQ exceeded]
Darkmatter66 has joined #nixos-aarch64
zupo has joined #nixos-aarch64
zupo has quit [Client Quit]
zupo has joined #nixos-aarch64
dguibert has joined #nixos-aarch64
juliosueiras has joined #nixos-aarch64
alp has quit [Remote host closed the connection]
alp has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo has quit [Ping timeout: 240 seconds]
<sphalerite> samueldr: are there any reasons in particular that mobile-nixos doesn't use pkgs.buildLinux? I've been fiddling with embedded kernels and have found buildLinux very comfortable to use for defining config, with one small change (https://github.com/mayflower/nixpkgs/commit/c8c509269ae1f799897d830b3fea8875f90c9c21)
<sphalerite> oh, just saw the comments at the top of builder.nix :)
<sphalerite> that said, I really like the way that buildLinux views a kernel config as "some defconfig + options specified"
orivej has joined #nixos-aarch64
Darkmatter66_ has joined #nixos-aarch64
Darkmatter66 has quit [Ping timeout: 258 seconds]
orivej has quit [Ping timeout: 258 seconds]
zupo has joined #nixos-aarch64
zupo has quit [Ping timeout: 260 seconds]
jumper149 has joined #nixos-aarch64
veleiro`` has joined #nixos-aarch64
veleiro` has quit [Ping timeout: 258 seconds]
justanotheruser has joined #nixos-aarch64
orivej has joined #nixos-aarch64
bennofs_ has joined #nixos-aarch64
bennofs__ has quit [Ping timeout: 240 seconds]
cole-h has joined #nixos-aarch64
<samueldr> sphalerite: I want to come back on the subject later
<samueldr> at the very least support the validation that NixOS does for the options
justanotheruser has quit [Ping timeout: 256 seconds]
cole-h has quit [Quit: Goodbye]
cole-h has joined #nixos-aarch64
<sphalerite> samueldr: sweet
alp has quit [Ping timeout: 260 seconds]
disasm has quit [Ping timeout: 264 seconds]
t184256 has left #nixos-aarch64 ["Error from remote client"]
alp has joined #nixos-aarch64
disasm has joined #nixos-aarch64
justanotheruser has joined #nixos-aarch64
rajivr has quit [Quit: Connection closed for inactivity]
sphalerite has quit [Quit: WeeChat 2.6]
sphalerite has joined #nixos-aarch64
t184256 has joined #nixos-aarch64
zupo has joined #nixos-aarch64
Darkmatter66 has joined #nixos-aarch64
Darkmatter66_ has quit [Ping timeout: 260 seconds]
<samueldr> colemickens: (moving discussion)
<samueldr> AFAICT nadia here does good work
<samueldr> (another source)
<samueldr> not sure what other sources you've seen linked out of my things
<colemickens> nice, okay!
<samueldr> the manjaro bits are... not exactly clean... they generally lack proper attribution
<samueldr> like the kernel patches, they have been stripped of most useful metadata
<samueldr> which other repos have I referenced?
<samueldr> right
t184256 has left #nixos-aarch64 ["Error from remote client"]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
t184256 has joined #nixos-aarch64
cole-h has quit [Quit: Goodbye]
cole-h has joined #nixos-aarch64
superherointj has joined #nixos-aarch64
superherointj has quit [Quit: Leaving]
cript0nauta has joined #nixos-aarch64
criptonauta_ has quit [Read error: Connection reset by peer]
cript0nauta has quit [Remote host closed the connection]
cript0nauta has joined #nixos-aarch64
cript0nauta has quit [Remote host closed the connection]
cript0nauta has joined #nixos-aarch64
cript0nauta has quit [Remote host closed the connection]
cript0nauta has joined #nixos-aarch64
<sphalerite> wtffff… prometheus-node-exporter builds for x86_64 even on aarch64!?
<sphalerite> oh no, I'm just doing overlay stuff wrong.
dguibert has quit [Ping timeout: 245 seconds]
juliosueiras has quit [Ping timeout: 265 seconds]
noonien has quit [Quit: Connection closed for inactivity]
* colemickens is afraid to jinx it but...
<colemickens> I love the Nix ecosystem and peeps!
* sphalerite too
<sphalerite> everyone++
<colemickens> looks like robotnix is on its way to building glodroid already https://github.com/danielfullmer/robotnix/issues/32#issuecomment-686731592
<colemickens> and it looks like THEY made an issue, referencing back to robotnix's works for future work in their repo. :) :)
<samueldr> haha oh boy
<samueldr> it's as if working in the open, as open source, can lead to better collaboration
<gchristensen> +1
<samueldr> (they might be surprised by robotnix's setup though)
<sphalerite> whoooooaa
<samueldr> I might try and launch the build overnight to see how it fares
alp has quit [Remote host closed the connection]
alp has joined #nixos-aarch64
juliosueiras has joined #nixos-aarch64
juliosueiras has quit [Ping timeout: 256 seconds]
alp has quit [Ping timeout: 272 seconds]
alp has joined #nixos-aarch64
juliosueiras has joined #nixos-aarch64
<juliosueiras> still not shipped, the serial cable is going take a while =(
<juliosueiras> at the meantime, what is a good portable keyboard for pinephone(for terminal)
t184256 has left #nixos-aarch64 ["Error from remote client"]
<jumper149> Is NixOS Mobile usable as a daily driver for the pinephone yet? When looking through the online docs I didn't find how to select a graphical environment with the configuration.nix.
<samueldr> nope
<samueldr> in practice it should end up being the same way you would on NixOS
<samueldr> but NixOS doesn't (yet) have phone-first environment
julm has quit [Ping timeout: 260 seconds]
t184256 has joined #nixos-aarch64
disasm has quit [Ping timeout: 264 seconds]
disasm has joined #nixos-aarch64
<colemickens> samueldr: do you know how these strings are listed/found/etc? evdev:input:b0003v258Ap001Ee0110-e0,1,2,4,k110,111,112,r0,1,am4,lsfw
<samueldr> some arcane command on udevadm I think
<colemickens> I got the trackpad quirk working, but the "Keyboard Mouse" still appears in sway's devices meaning libinput is not disabling it.
<colemickens> hm ok
<samueldr> poke under /sys/class and look at uevent files
<samueldr> though all of this can be easily explained, each field has a value for a reason
<samueldr> which is IIRC documented somewhere around systemd/udev
<clever> samueldr: after ~2 weeks, i have the arm mmu configured, with dcache, and flushing the dcache before i switch to linux, lol
julm has joined #nixos-aarch64
<thefloweringash> Mic92: I'm not quite following sorry. I don't have any magic config here, I manually dd uboot to the two fixed locations.
<thefloweringash> I wrote something a little more concrete about how I would try to make a rock64 image out of the nixos image: https://gist.github.com/thefloweringash/d22d7e1b0aedf7bb32dd9280da45f900
<thefloweringash> there's no need for the firmware partition on a rock64, destroying it isn't a problem. does it boot after you do so?
jumper149 has quit [Quit: WeeChat 2.9]