chiefgoat has quit [Ping timeout: 265 seconds]
chiefgoat has joined #nixos-aarch64
lovesegfault has joined #nixos-aarch64
<lovesegfault> samueldr: does the rpi4 not use the same bootloader as the rpi3?
<lovesegfault> I'm unsure where `FIRMWARE` should be mounter
<lovesegfault> *mounted
<lovesegfault> For my rpi3 I mount it to `/boot/firmware` but it seems like it should be `/boot` for the rpi4?
<samueldr> lovesegfault: yes and no
<lovesegfault> uh oh
<samueldr> lovesegfault: they both use the raspberry pi foundation's bootloader, but we boot different programs
<samueldr> the 3 family boots u-boot
<samueldr> the 4 currently directly boots the kernel
<samueldr> that's why for the 4 we currently have to mount "FIRMWARE" under /boot
<samueldr> since that image is basically a hack over top our u-boot centric image
<lovesegfault> Aha
<samueldr> does that make sense?
<lovesegfault> this is wrong then
<lovesegfault> Yep, makes perfect sense
<samueldr> oh, I thought this was nixpkgs
<lovesegfault> Why does the rpi4 not boot uboot?
<samueldr> and I was getting confused
<lovesegfault> samueldr: lol
<lovesegfault> sorry
<samueldr> no worries :)
<lovesegfault> Just my own configs
<samueldr> hmmm
<samueldr> it was because when I got that initial image config in nixpkgs u-boot didn't support the 4
<samueldr> currently it's because mainline doesn't support the 4
<samueldr> (mainline linux)
<samueldr> but since u-boot now supports the 4, we could meet halfway
<lovesegfault> 5.5 should support, right?
<samueldr> no idea
<lovesegfault> or is it 5.6?
* lovesegfault checks
<samueldr> I haven't seen much info
<samueldr> but what I've seen is it's still wildly an open issue
<lovesegfault> apparently 5.5 has RPi4 support
<samueldr> oh, exciting
<lovesegfault> :)
<{^_^}> #70796 (by samueldr, 16 weeks ago, open): u-boot: Add Raspberry Pi 4 build
<samueldr> we need to re-review this, check if 2020.01 added the right device tree, if not somehow patch it into our build
<samueldr> that would be a good goal to achieve for 20.03, and entirely plausible
<lovesegfault> I have an rpi4 now, so I can help test
<samueldr> [as long as the end-user uses the "new_kernel" variant)
<lovesegfault> Sweet, I'll play with it when 5.5 lands (there's an open PR)
mDuff has quit [Ping timeout: 268 seconds]
h0m1 has quit [Ping timeout: 246 seconds]
h0m1 has joined #nixos-aarch64
ToxicFrog has left #nixos-aarch64 ["WeeChat 2.6"]
lovesegfault has quit [Ping timeout: 268 seconds]
lovesegfault has joined #nixos-aarch64
lovesegfault has quit [Ping timeout: 260 seconds]
lovesegfault has joined #nixos-aarch64
lovesegfault has quit [Quit: WeeChat 2.7]
jaen has joined #nixos-aarch64
<jaen> Hello, I'm trying to build a raspi4 image using the qemu binfmt method and after some wrangling I got to the point where it tries to assemble the image, but then I get a lot of messages like `error while reading directory .: Cannot allocate memory` and the resulting image does not work. Any ideas what to do about it?
FRidh2 has joined #nixos-aarch64
<makefu> jaen: which guide where you following?
<jaen> @makefu: there's really no one complete guide as far as I could see, but I'm basically doing this — https://nixos.wiki/wiki/NixOS_on_ARM#Build_your_own_image — using QEMU links provided
<jaen> I just add openssh and networking on top of the defaults, so I can configure it without having to buy a micro-hdmi cable
<jaen> Here's the config if that helps – https://gist.github.com/jaen/babb55f20f7232ff3f1c903b09cbb6e9
<makefu> i am unsure if rpi4 is completely supported already. i see a number of open issues just by scrolling through the backlog in this channel. maybe someone here can support
<jaen> This happens both on my nixos machine and with nix on arch linux, I'm on the unstable channel, I think it's required for it to work
<jaen> Well, I wouldn't be surprised if it didn't work when built, but I can't even build it, while people seem to do it, so I'm probably just doing something wrong?
<jaen> I'll probably just bite the bullet and buy the cable, but would appreciate help figuring it out none the less, even if only for posterity
<makefu> qemu-user build for the full system i do not even know if it works already. however we have an aarch64 community builder which is aarch64 https://github.com/nix-community/aarch64-build-box.
t184256 has left #nixos-aarch64 ["Disconnected: Replaced by new connection"]
t184256 has joined #nixos-aarch64
<srk> thefloweringash: now it tries to pull llvm \o/ but fails /o\
<srk> copying path '/nix/store/6csgw9w4hsri738ppf6lh1lr15680p46-llvm-9.0.1' from 'https://thefloweringash-armv7.cachix.org'...
<srk> file 'nar/6fc455aaec12362451eb40d25fe68f6fd1ddd43d926fa685b968efe503156de9.nar.xz' does not exist in binary cache 'https://thefloweringash-armv7.cachix.org'
<clever> srk: they garbage collected the cache, you need to clear your cache cache now
<clever> [root@system76:~]# ls ~/.cache/nix/binary-cache-v6.sqlite*
<clever> srk: delete these files, and nix will re-query all caches, and discover that llvm isnt there anymore
<clever> and that reminds me, i forgot to test the initrd i left building overnight
<srk> even if I delete them it still tries to download it. llvm build failed again at something like 90%, hell
<clever> srk: did you check as root?
<srk> yeah, I'm using root account
<clever> its possible the narinfo is still present, so the cache is bork?
<srk> possibly
<clever> URL: nar/6fc455aaec12362451eb40d25fe68f6fd1ddd43d926fa685b968efe503156de9.nar.xz
<clever> HTTP/1.1 404
<clever> yep, the cache is bork
<thefloweringash> uhoh, something went wrong in the cachix migration today?
<thefloweringash> it's only at ~3gb/20gb, shouldn't have GCd
<clever> thefloweringash: definitely not a gc, the narinfo is still present
<jaen> @clever: is it you who has theirs qemu binfmt overlay linked in the wiki?
<clever> jaen: probably
<thefloweringash> does cachix allow uploading to fail non-atomically ?
<clever> thefloweringash: unknown, youd have to ask domen
<jaen> @clever: I'm trying to use it to build a raspi4 SD card image and I get a cascade of `error while reading directory XXX: Cannot allocate memory` when it tries to copy the results into the image. Have you encountered something like that?
<clever> [ 6.852433] Run /init as init process
<clever> [ 6.861777] CPU: 0 PID: 1 Comm: init Tainted: G W 4.19.89-v7+ #166
<clever> [ 6.856863] potentially unexpected fatal signal 11.
<{^_^}> https://github.com/NixOS/nixpkgs/pull/166 (by jcumming, 7 years ago, merged): - libarchive-3.0.4
<clever> jaen: nope, i havent seen that error
<jaen> Oh well, thanks. I'll just do a graphical install then.
<jaen> Not even sure how to tackle debugging this
<clever> looks like its not an armv7 problem i'm having
<clever> v6 fails the same way
<srk> init segfauls? oO
<clever> srk: yes
<clever> srk: previously, init wasnt segfaulting, but udevd was
<clever> not sure what i did to upset init
<srk> is that with some recent nixpkgs?
<samueldr> I think the problem is that clever is doing unspeakable things to the poor thing
<samueldr> and I want him to succeed!
<clever> srk: currently using a recent rev from staging
<clever> srk: cross armv6, cross armv7, and native armv7 all fail the same way
<samueldr> clever: just checking, that's still with your firmware, right? works on the foundation's?
<clever> samueldr: i think so, need to double-check that in a bit
<clever> samueldr: also, the stock kernel from pkgs.linux_rpi2 hangs, but if i compile a kernel by hand from the same .config it works
<thefloweringash> I tried manually repushing that llvm with the cachix cli, it says "All done" but curl is still 404-ing.
<clever> thefloweringash: you might need to delete it from the server first, then re-push
<samueldr> thefloweringash: might be a good idea to get in touch with domen (he's on irc) just in case *something* happened during the migration
orivej has quit [Ping timeout: 268 seconds]
jaen has quit [Remote host closed the connection]
FRidh2 has quit [Quit: Konversation terminated!]
orivej has joined #nixos-aarch64
<thefloweringash> I'm not sure of the details, but apparently I'm "one of the lucky 2k :)", so the cache is still migrating, "should be available by tomorrow"
wavirc22 has joined #nixos-aarch64
<srk> cool!
wavirc22 has quit [Ping timeout: 260 seconds]
wavirc22 has joined #nixos-aarch64
<srk> uuuh, udisks
<srk> udisks -> libblockdev -> libndctl -> asciidoctor -> asciidoctor-mathematical -> pango -> gl/cairo/mesa/llvm
wavirc22 has quit [Ping timeout: 272 seconds]
wavirc22 has joined #nixos-aarch64
wavirc22 has quit [Ping timeout: 268 seconds]
pbb_ has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
<thefloweringash> srk: https://hydra.barbara.cons.org.nz/eval/2191 (requires ipv6)
wavirc22 has joined #nixos-aarch64
* gchristensen wishes he could access it
<srk> cool
<srk> it's weird that udisks is pulling all that but I don't see a quick way to fix that, asciidoctor is required to build 'man' of the libndctl
<srk> maybe with some overrides
<thefloweringash> Do you need udisks?
<thefloweringash> I’ve previously tried Cloudflare as a protocol converting proxy. Something didn’t work, but I don’t recall what. I’ll give it another go.
wavirc22 has quit [Ping timeout: 265 seconds]
<srk> of course not, but it's quite a suprise that it's pulling all the graphical stack
<srk> when you don't have anything graphical related enabled
<thefloweringash> I’ve seen a few comments in the profiles about how heavy it’s become. IIRC it even requires gtk
wavirc22 has joined #nixos-aarch64
pbb has joined #nixos-aarch64
<srk> grows easily if you don't periodically check the size/deps of the toplevel closure
<srk> huh, now your hydra returns Error code: SSL_ERROR_NO_CYPHER_OVERLAP
<srk> gchristensen: my provider gives native ipv6 but only half duplex :) you can't ping their v6 network or anything in it
<srk> windows security measures
wavirc22 has quit [Ping timeout: 248 seconds]
wavirc22 has joined #nixos-aarch64
<thefloweringash> well, looks like cloudflare isn't working this time either. reverted back to plain connectivity
<srk> btw what's the machine you're using for the builds?
<srk> big ugly aarch64 thingie :D
<thefloweringash> it's medium ugly, a honeycomb lx2k with a kvm vm for the armv7l sytem
wavirc22 has quit [Ping timeout: 268 seconds]
<srk> 4 x 10GbE SFP+
<srk> uu:D
<thefloweringash> if my ISP rolls out 10gb I might use it as my router. the competition have 10gb but I'm stuck on 1gb
<gchristensen> srk: wat lol
wavirc22 has joined #nixos-aarch64
<srk> I've only played with LS1046A, didn't make it boot nixos tho
<srk> gchristensen: either that or incompentence or 'who would pay for public v4 then'
<srk> I want to use wireguard to route ipv6 traffic to VPS at some point for full duplex connectivity :)
<thefloweringash> my internet is neat: ipv6 native, with tunneled ipv4 to a shared public ip address. the port is divided into 8-bits customer id, 8-bits port
<srk> hm, maybe headless profile could turn off udisks?
<srk> or minimal
wavirc22 has quit [Read error: Connection reset by peer]
<sphalerite> thefloweringash: I've played on and off with the idea of getting an lx2k, would you recommend it?
<sphalerite> thefloweringash: does it work with normal kernels and u-boot?
<thefloweringash> honestly I didn't put any effort into trying normal kernels and normal u-boot, I just ported the vendor stuff to nix (https://github.com/thefloweringash/lx2k-nix)
wavirc22 has joined #nixos-aarch64
<sphalerite> aaah okay. Well thanks for packaging it nicely!
<sphalerite> and documenting
<sphalerite> also, what do you work on, if I may ask?
<thefloweringash> it's really nice not being io and ram starved, ie, I put 32gb of ram and a 1tb nvme drive in it. it's also really nice to have a standard form factor. I went on aliexpress and got a picopsu clone and a little mini-itx case
<thefloweringash> the list of errata on the preproduction version is a bit rought, with notable entries like: "no fan controller" and "microsd slot is read only", but the final version should have those fixed
<thefloweringash> Not sure how to answer the question about what i work on: my day job is webshit
<sphalerite> yeah I guess that was my question :) is the aforementioned competition in the webshite domain as well?
<thefloweringash> a while ago I thought I might enjoy having a low end linux laptop to sit on the couch and tinker with things: just enough to run a terminal and maybe a web browser. so I got a chromebook (a kevin, rk3399), and it's all just spiraled out of control since then...
<sphalerite> hah
<sphalerite> oh yeah, did you see my coreboot-for-gru-built-with-nix thing?
<thefloweringash> oh, no I mean the competition for my isp. there are two major fiber networks. Mine does 1gb, the other does 10gb
<sphalerite> aaaah
<thefloweringash> s/mine/the one I get my residential connection from/
<thefloweringash> I've been avoiding alternate bootloaders since I'm hesitant to remove chromeos or make booting it harder. I haven't found a good linux replacement for squid =\
<sphalerite> squid?
<thefloweringash> the android drawing app
<thefloweringash> in the same class as xournal / xournalpp
<sphalerite> ah okay, so you actively use chromeos? Yeah then I guess you don't want that
<thefloweringash> ooh now that staging is merged maybe they won't crash when I use the stylus, has that hit the channels yet?
<sphalerite> it also has some rough edges like no working suspend-to-ram or wifi currently :/
<sphalerite> (and I've only used it for bob, but the changes for kevin should be minor AFAIK)
wavirc22 has quit [Ping timeout: 268 seconds]
<thefloweringash> I feel the temptation to get a pinebook pro, just for that nvme slot, even if it's not quite as fancy as a kevin
wavirc22 has joined #nixos-aarch64
wavirc22 has quit [Ping timeout: 240 seconds]
wavirc22 has joined #nixos-aarch64
wavirc22 has quit [Ping timeout: 265 seconds]
wavirc22 has joined #nixos-aarch64
wavirc22 has quit [Ping timeout: 268 seconds]
wavirc22 has joined #nixos-aarch64
wavirc22 has quit [Ping timeout: 260 seconds]
wavirc22 has joined #nixos-aarch64
orivej has quit [Ping timeout: 260 seconds]
wavirc22 has quit [Ping timeout: 268 seconds]
wavirc22 has joined #nixos-aarch64
wavirc22 has quit [Ping timeout: 268 seconds]
wavirc22 has joined #nixos-aarch64
wavirc22 has quit [Ping timeout: 265 seconds]
wavirc22 has joined #nixos-aarch64
<samueldr> just know that NVME slot may not work with all drives due to power usage
<samueldr> otherwise I really like the machine
<samueldr> and in chromebook-related news... something fresh
<samueldr> I've been working on that using-linux-as-a-bootloader approach a bit, hopefully by the end of next month it's ready
wavirc22 has quit [Ping timeout: 268 seconds]
wavirc22 has joined #nixos-aarch64
wavirc22 has quit [Ping timeout: 240 seconds]
wavirc22 has joined #nixos-aarch64
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 272 seconds]
wavirc22 has quit [Ping timeout: 260 seconds]
wavirc22 has joined #nixos-aarch64
wavirc22 has quit [Ping timeout: 268 seconds]
wavirc22 has joined #nixos-aarch64
wavirc22 has quit [Ping timeout: 265 seconds]
wavirc22 has joined #nixos-aarch64
wavirc22 has quit [Ping timeout: 268 seconds]
wavirc22 has joined #nixos-aarch64
wavirc22 has quit [Ping timeout: 260 seconds]
wavirc22 has joined #nixos-aarch64
orivej has joined #nixos-aarch64
wavirc22 has quit [Ping timeout: 265 seconds]
wavirc22 has joined #nixos-aarch64
wavirc22 has quit [Ping timeout: 240 seconds]
wavirc22 has joined #nixos-aarch64
wavirc22 has quit [Ping timeout: 268 seconds]
wavirc22 has joined #nixos-aarch64
wavirc22 has quit [Ping timeout: 268 seconds]
wavirc22 has joined #nixos-aarch64
wavirc22 has quit [Ping timeout: 268 seconds]
wavirc22 has joined #nixos-aarch64
wavirc22 has quit [Ping timeout: 268 seconds]
wavirc22 has joined #nixos-aarch64
orivej has quit [Ping timeout: 265 seconds]
wavirc22 has quit [Ping timeout: 272 seconds]
wavirc22 has joined #nixos-aarch64
wavirc22 has quit [Ping timeout: 265 seconds]
wavirc22 has joined #nixos-aarch64
wavirc22 has quit [Ping timeout: 265 seconds]
wavirc22 has joined #nixos-aarch64
wavirc22 has quit [Ping timeout: 268 seconds]
wavirc22 has joined #nixos-aarch64
wavirc22 has quit [Ping timeout: 260 seconds]
wavirc22 has joined #nixos-aarch64
wavirc22 has quit [Ping timeout: 268 seconds]
wavirc22 has joined #nixos-aarch64
mDuff has joined #nixos-aarch64
lovesegfault has joined #nixos-aarch64
aminechikhaoui has quit [Quit: The Lounge - https://thelounge.github.io]
aminechikhaoui has joined #nixos-aarch64
aminechikhaoui has quit [Client Quit]
aminechikhaoui has joined #nixos-aarch64
<mDuff> Hmm. Smells like we're a single-digit number of hours from linuxPackages_5_5 being available in the nixos-unstable channel; might see if dwc2.dtbo can be applied to the .dtb shipped in the upstream kernel tree when that happens.
jtojnar_ has joined #nixos-aarch64
bennofs has quit [Remote host closed the connection]
bennofs has joined #nixos-aarch64
jtojnar_ has quit [Quit: jtojnar_]