<gchristensen> anyone want to play with new arm hw with me? :)
<gchristensen> I have an new Ampere system and its cpu stalls on nixos-install
<samueldr> sure
<samueldr> which kernel is it booting? 4.14 or 4.19/20?
<samueldr> like, are you booting 18.09 or unstable?
<samueldr> 18.09
<gchristensen> 18.09
<makefu> that feeling when your raspi starts compiling some gui library after you tried to enable a service and run rebuild switch ....
<gchristensen> I'm in ubuntu now -- anything I should look at before I reboot to the nixos livecd?
<samueldr> which kernel version? dumping /proc/config.gz
<samueldr> maybe a dmesg dump too
<samueldr> though the dmesg is not something I'd think would be really useful
<samueldr> is the ubuntu release a standard one?
<samueldr> or an ampere flavoured one?
<gchristensen> mmm not 100% sure :)
<gchristensen> linaro
<samueldr> if it's ampere-flavoured, maybe the kernel is too, and then this might be something to look into
<makefu> gchristensen: it would be fantastic if you could document the steps from ubuntu to nixos. i have a somewhat similar case here. i tried to boot from sdcard before but it does not get detected by the kernel in stage 1 so the next thing i'd like to test is to install nixos via the ubuntu (which works and even detects the the memory card).
<gchristensen> I hard-core cheat :/
<gchristensen> I usually jump right to netbooting
<makefu> that is a far jump, however i think i can manage to get netboot running via uboot
<gchristensen> the hardware is in a datecenter, and someone else did the hard work of setting up tftp and ipxe and dhcp and I just say "boot this url" :X
<clever> i have that "hardwork" setup on my LAN, and even packaged into a nixos module that can basically turn a laptop into a plague upon a LAN :P
<gchristensen> samueldr: I'm not thinking of anything else I'm missing here
<gchristensen> you?
<samueldr> haven't taken a detailed look yet
<clever> makefu: yep
<samueldr> gchristensen: the linaro thing in the kernel version is the compiler
<clever> makefu: it includes justdoit, so a single shell command will wipe whatever computer you run it on
<clever> makefu: with a few more tweaks, it could pre-install netboot_server onto that machine, and then you just need to ensure netboot works when you have 200 conflicting dhcp servers, lol
<clever> then its just 1 tweak away from becoming a virus!
<makefu> haha
<clever> nixos for everybody!
<makefu> i am really wondering why there are not more cases of tftp boot viruses
<clever> weather they want it or not!
<makefu> they will have to want it
<samueldr> gchristensen: I guess it's annoying/hard to get a PXE with new_kernel?
<samueldr> thinking that since ubuntu is 4.15, it might help
<gchristensen> not so annoying / hard
<gchristensen> what is new_kernel?
<samueldr> nothing really, since I don't think anything PXE has it
<samueldr> but we have iso.new_kernel and sd_card.new_kernel (iirc for the name) which uses latest instead of the default
<gchristensen> huh
<samueldr> <nixos/release.nix> iso_minimal_new_kernel
<gchristensen> sure
<gchristensen> is that on unstable?
<samueldr> it's in 18.09
<gchristensen> nice
<samueldr> not the PXE variant, but the concept and such
<gchristensen> yeah
<gchristensen> I mean, all it is doing is doing the latest kernel
<gchristensen> I'll just select that in my existing infra
* samueldr nods
<gchristensen> any initrd.availableKernelModules we should throw in too
<samueldr> no idea
<samueldr> dang
<gchristensen> hm?
<samueldr> lsmod would have been nice
<samueldr> oh you did it :)
<samueldr> well, if it goes to stage-2, not sure there's any that's needed
<gchristensen> aye
<gchristensen> true
<gchristensen> it will
<gchristensen> ok while that runs I'll reboot the machine from ubuntu into nixos
<gchristensen> unless samueldr you had other questions for ubuntu
<samueldr> not that I can think of
<gchristensen> okay
<gchristensen> this is not in to the new nixos, but the old nixos
<gchristensen> decided against the reboot
<gchristensen> reboots are slow enough I'd rather not have to do it twice :P
<samueldr> lol
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<gchristensen> welp. I lost the timing race anyway.
<gchristensen> it is a good thing nix is good at making correct / complete images
<gchristensen> otherwise netboot would be hell
<samueldr> heh
<samueldr> it's kinda why I love nixos for the things like mobile-nixos
<samueldr> pretty good guarantees that once it worked, building it with updates it will work or easy~ish to figure out the issue (if something broke)
<gchristensen> yea
<clever> that reminds me
<clever> nix-env -p /nix/var/nix/profiles/per-user/root/rpi3-netboot -f not-os/release.nix -A rpi_image -I nixpkgs=./nixpkgs/ --set
<clever> this creates a custom nix-env profile, pointing to the result of a given attr in a given file
<clever> lrwxrwxrwx 1 root root 48 Dec 11 2016 /tftproot/9080d9b6 -> /nix/var/nix/profiles/per-user/root/rpi3-netboot
<clever> this then exposes that, at the path the rpi netboot looks for, in the tftp daemon
<clever> i now have full generations and rollback support, and can rollback even if the pi is "bricked", as long as i can remotely reset it
<samueldr> clever: use another pi's GPIO
<clever> thats always an option
<clever> but, this isnt limited to just rpi's
<samueldr> :)
<clever> you could use it on any server your netbooting
<gchristensen> <<< NixOS Stage 2 >>>
<samueldr> now do stage 3
<gchristensen> lol
<gchristensen> slowwww running activation script...
<gchristensen> setting up /etc...
<gchristensen> I shoulda set log level to like, 7
<gchristensen> Initializing machine ID from random generator.
<gchristensen> this is hilariously slow
<gchristensen> [ 2.265374] [Firmware Bug]: register x18 corrupted by EFI get_time
<gchristensen> unpacking the NixOS/Nixpkgs sources...
<samueldr> sounds "fine"
<gchristensen> https://gist.github.com/grahamc/0a8fa13fa8926a797385e7968f0de562 some info from the install environment
<samueldr> has it been installing?
<gchristensen> it is trying to install
<samueldr> further or not than the earlier attempt?
<gchristensen> its in building the configuration in /mnt/etc/nixos/configuration.nix...
<gchristensen> and everything iinstalling the boot loader...
<samueldr> h.y.p.e
<gchristensen> installation finished!
<samueldr> so, not much more exciting than the previous one, only needed a more recent kernel
<samueldr> sbbr seems to help :)
<gchristensen> <3 yes
<samueldr> hope ebbr will do the same
<gchristensen> packet-t2a6-ampere-1 login:
<samueldr> root
<clever> hunter2
<gchristensen> [root@packet-t2a6-ampere-1:~]#
<gchristensen> thanks for the help, samueldr!
<samueldr> lol
<gchristensen> is there a nice benchmarking program that I could run and compare results against another machine?
<samueldr> lately it feels like 90% of the "it doesn't work on $fancy" is "use the latest kernel"
<gchristensen> :)
<gchristensen> pretty nice ...
<samueldr> I'd like to know too, would be nice to also compare SBCs
<gchristensen> lol
<gchristensen> [nix-shell:~]# sysbench --test=cpu --num-threads=32 --cpu-max-prime=9999 run
<gchristensen> ...
<gchristensen> Initializing worker threads...
<gchristensen> Illegal instruction
<clever> lol
<gchristensen> to be fair, it is very fast to tell me that
<samueldr> same on the aarch64 community box gchristensen
<gchristensen> ah nice
<gchristensen> so they are equal in that regard
<samueldr> (for some values of nice)
<petersjt014> anyone know a way I can quickly-ish do a rebuild for armv6l (raspi-0) without having to tolerate 480MB ram/1 core?
<petersjt014> I have a few things I'm considering
<petersjt014> usinbg a vm is one: https://nixos.wiki/wiki/NixOS_on_ARM/QEMU
<samueldr> qemu-user-arm might be usable
<samueldr> and possibly the only useful solution other than cross
<petersjt014> I've tried it with the armv6l image, it stalls after 'initializing kernel'. not sure what flags need to be changed if any
<samueldr> (a full emulated machine is way slower than qemu-user, though probably still faster than the pi)
<petersjt014> 1 core/ .5GB vs 4core 8GB -- yup
<samueldr> emulation takes its toll on perfs
<petersjt014> but if I can specify remote cross compile stuff as flags I'd be willing to try that too
<samueldr> (sadly I have next to no useful recommendation for cross)
<petersjt014> VM voodo fun for now then
<petersjt014> oh, I should ask: will things compiled by the armv7l image be compatible with a physical armv6l device?
<gchristensen> samueldr: impurity in sysbench
<samueldr> oh, makes sense
<samueldr> built on the thunderx machine
<gchristensen> nix-store --delete /nix/store/87gl94flr69prk191f92d9fxxv7l34ak-sysbench-1.0.15/bin/sysbench; nix-build '<nixpkgs>' -A sysbench --check; ./result/bin/sysbench --test=cpu --num-threads=32 --cpu-max-prime=9999 run
<gchristensen> (replace your --delete path as needed)
<samueldr> on my pi3 it had to build, probably at a revision where it isn't in the cache (not so slow to build) and runs
<samueldr> gchristensen: what am I doing wrong if --check also downloads the cached build and just says it's non-deterministic (keeping the cached build)
<lopsided98> petersjt014: it is possible to build for armv6l on an armv7l machine, but you need a few changes to nixpkgs to prevent build systems from assuming you're trying to build for armv7l
<gchristensen> samueldr: oops
<gchristensen> delete the path and then
<gchristensen> --substituters '', instead of --check
<samueldr> right
<petersjt014> lopsided98: Is it specific flags by any chance?
<samueldr> lopsided98: isn't it failing on some critical things due to the impurely looking at the CPU?
<samueldr> IIRC there is nothing like on x86_64 to hide the armv7ness of an armv7 machine to the software
<gchristensen> right
<lopsided98> samueldr: I have a few patches that prevent that, mainly setting the "build_alias" env var to prevent autotools from guessing the platform
<clever> samueldr: i have a setup-hook that will fail the build if v7 opcodes make it into the output
<lopsided98> it is not perfect, but it works well enough that I use it for a number of armv6l systems
<samueldr> stop hoarding the good stuff :3
<clever> samueldr: let me see where i left it...
<petersjt014> would it be easier to make an armv6l vm instead?
<lopsided98> I don't really have enough RAM on my build system to dedicate to a VM
<petersjt014> I have more than enough--gotta pay by the hour tho :|
<clever> samueldr: to be fair, i wrote this 3 years ago :P
<samueldr> gchristensen: ran it on three systems https://gist.github.com/samueldr/7d9b564f8b453a6f3d914827dcc35eed
<gchristensen> faster than the xeon
<gchristensen> nice
<clever> samueldr: the basic idea, is to fill in line 4 with arch pairs, and then jam this into the stdenv, so all builds fail if v7 stuff leaks in
<samueldr> gchristensen: many more cores, 2012-era xeon
<gchristensen> aye
<samueldr> still nice
<samueldr> oh, even one core is faster on that kind of test
<gchristensen> :)
<samueldr> the community box seems faster
<samueldr> (I think they're not in the same price range though?)
<gchristensen> the ampere system is $3-5k
<samueldr> while the community box is "if you need to ask..."
<gchristensen> literally no idea
<samueldr> that's the joke :)
<samueldr> no pricing information, probably means pricey
<gchristensen> :)
<gchristensen> sooo many coressss
<samueldr> that's two thunderx, and the new centriq, right?
<samueldr> ah, the last graph didn't show the ampere
<gchristensen> yeah, the last graph won't show the ampere until it has built ~1hr of jobs :)
<gchristensen> 30min*
* samueldr looked at the queue summary
<gchristensen> we have about 3 jobs per available core ;)
<samueldr> nice
alex_giusi_tiri has left #nixos-aarch64 [#nixos-aarch64]
<sphalerite> KemoNine: gchristensen: No, sorry, I never got that far with armv7 stuff
<timokau[m]> If I want a simple, no fuss, nixos "mini-home-server", the rpi 3B+ is probably my best option right? I'm currently running some light services (taskd, wallabag, syncthing) on my rpi2 and would really like to migrate from arch. I'm not happy about the shared ethernet & USB connector on the RPI, but that is probably the only board known to work with upstream nixpkgs and without any tinkering right?
<timokau[m]> Sorry to abuse this channel a bit, but I'm assuming the people here have probably tried every board under the sun :D
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
orivej has quit [Ping timeout: 240 seconds]
tilpner has joined #nixos-aarch64
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 268 seconds]
nbp_ is now known as nbp
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 240 seconds]
petersjt014_ has joined #nixos-aarch64
petersjt014 has quit [Ping timeout: 240 seconds]
petersjt014 has joined #nixos-aarch64
petersjt014_ has quit [Ping timeout: 250 seconds]
worldofpeace has joined #nixos-aarch64
duncan^ has left #nixos-aarch64 [#nixos-aarch64]
orivej has joined #nixos-aarch64
orivej has quit [Remote host closed the connection]
orivej has joined #nixos-aarch64
orivej has quit [Remote host closed the connection]
orivej has joined #nixos-aarch64
orivej has quit [Read error: Connection reset by peer]