ris has quit [Ping timeout: 276 seconds]
vika_nezrimaya has quit [Ping timeout: 245 seconds]
THFKA4 has joined #nixos-aarch64
THFKA4 has quit [Changing host]
orivej has quit [Ping timeout: 276 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 246 seconds]
alienpirate5 has joined #nixos-aarch64
alienpirate5 has joined #nixos-aarch64
alienpirate5 has quit [Changing host]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 276 seconds]
{^_^} has quit [*.net *.split]
lopsided98 has quit [*.net *.split]
craige has quit [*.net *.split]
lopsided98 has joined #nixos-aarch64
craige has joined #nixos-aarch64
{^_^} has joined #nixos-aarch64
vcunat has joined #nixos-aarch64
marek has quit [Ping timeout: 268 seconds]
marek has joined #nixos-aarch64
jtojnar has joined #nixos-aarch64
orivej has joined #nixos-aarch64
jtojnar has quit [Ping timeout: 276 seconds]
jtojnar has joined #nixos-aarch64
orivej has quit [Ping timeout: 248 seconds]
<exarkun> got all the way to libgcrypt
<exarkun> then its test suite failed
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 244 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 245 seconds]
chiefgoat has quit [Ping timeout: 244 seconds]
chiefgoat has joined #nixos-aarch64
<samueldr> :/
<samueldr> yeah, I hadn't been succesful in a full system build, ever, with qemu-user
<samueldr> only for supplementing an existing system
ryantrinkle has quit [Ping timeout: 272 seconds]
dispanser has quit [Ping timeout: 246 seconds]
<exarkun> maybe I should be carefully selecting nixpkgs version and using the armv6l binary cache instead of thinking I can build stuff
<exarkun> that binary cache is almost as slow as building w/ qemu but at least I don't have to debug build crud
<samueldr> oof, since it's armv6l it's going to be a pain to build natively
<samueldr> also, of note, is that I had issues with building for armv6l on qemu-user
<samueldr> since there are impurities in the build system
<samueldr> the same case as building for armv6l on armv6l
<samueldr> some builds detect features of the CPU
<samueldr> and qemu-user, unless tweaked, will default to armv7l for arm
<exarkun> I /assumed/ the overlay would take care of those kind of details since it seems to advertise armv6l as a feature
<exarkun> probably would more efficient for me to throw all of my armv6l hardware in the trash and replace it with at least armv7l but I /probably/ won't do that...
<samueldr> sadly, a bunch of stuff has impurities coming from cpu detection
<samueldr> on x86_64 and aarch64 too
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
ryantrinkle has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<sphalerite> exarkun: last I checked the arm binary cache was pretty out of date
<samueldr> I think it should be ~11 months out of date
<exarkun> Harsh :(
<exarkun> Sounds like armv6l is doomed
<exarkun> (for nix)
<sphalerite> https://www.cs.helsinki.fi/u/tmtynkky/nixos-arm/ shows that "channel" (the cache) was last updated last October
<samueldr> it'll never be a fun experience
<samueldr> sphalerite: ah, memory was off by one month I guess
<sphalerite> exarkun: the best you can do is probably cross-compile stuff
<samueldr> since with nix it "needs" to build on native to be a pleasant experience (for now)
<exarkun> sphalerite: Nope. Cross compilation doesn't work either.
<samueldr> though, cross-compilation has its issues :(
<sphalerite> well, depends on what you're targeting
<exarkun> I think I'll give up on nix for this piece of hardware and stick debian or something on it :/
<sphalerite> but yeah you almost definitely don't want to run nix _on_ it
<exarkun> sphalerite: I've never managed to get a cross-compile to armv6l to complete for a whole-system build, no matter how minimal
<exarkun> I did manage to get a whole-system build to complete _on_ the device one time
<samueldr> exarkun: I might not have shared that with you https://github.com/samueldr/cross-system
<exarkun> I think it took 5 days
<samueldr> though I assumed I did
<sphalerite> exarkun: yeah no, I wouldn't try to run nixos, since that includes running nix ;)
<sphalerite> exarkun: but something like clever's not-os, maybe
<samueldr> sphalerite: ^
<exarkun> samueldr: and that ... works?
<samueldr> that configuration.nix has all the toggly bits toggled so that cross-compilation works
<samueldr> for a minimal installer
<samueldr> it's kind of my WIP list of things to fix
<sphalerite> samueldr: yeah, but I'd think that cross-nixos isn't worth doing except maybe to booptstrap native nixos
<samueldr> sphalerite: I would say the same, but add "for now"
<sphalerite> and even that is probably silly compared to cross-nix on a different distro to bootstrap native nixos
<samueldr> I have hopes that it will always get better
<samueldr> in a way, it did!
<samueldr> though yeah, native builds will always be the supported use case
<samueldr> while cross-compilation is "as best we can"
<exarkun> arm hardware has come a long way recently and seems to continue to advance
<exarkun> so native compilation is getting more feasible
<samueldr> yeah, aarch64 is not an issue, armv7l is feasible with a bit of work
<exarkun> in principle it seems like it would be nice if nixpkgs _only_ cross compiled and never native compiled. but from what I've seen that's not realistic.
<samueldr> (for the whole hydra eval)
<sphalerite> #21471
<{^_^}> https://github.com/NixOS/nixpkgs/issues/21471 (by Ericson2314, 2 years ago, open): Always cross compile
<exarkun> yea, seen that :)
<samueldr> yeah, so much dependencies act badly
<sphalerite> exarkun: ^ :)
<samueldr> and it doesn't exactly work
<samueldr> since most times "always cross" is not enought cross
<samueldr> since you're still native-to-native
<samueldr> so hardware detection won't fail
<samueldr> and such things
<exarkun> right
<samueldr> but it's right, that always cross-compiling would likely give better results
<exarkun> maybe if you at least marked packages with those impurities somehow ... anyway, whatever
<exarkun> I need to fix my python env :)
<Ericson2314> Aarch32 from Aarch64?
<samueldr> here it's x86_64 compiling for armv6l
<samueldr> we might be able to get a native armv6l build infra going soon™
<samueldr> with a limited package set
<sphalerite> who's we?
<samueldr> the royal we
<samueldr> and another contributor, not sure how much they want to be implicated right now :)
<sphalerite> :D
<sphalerite> would that be using kvm on beefy aarch64 machines?
<samueldr> not likely to work
<samueldr> for armv6
<samueldr> it'll be on real deal slow armv6
<samueldr> the issue is AFAICT kvm on aarch64 gives armv7l, so the issues of building armv6l on armv7l happen
<samueldr> (e.g. misfeatures misdetection)
<sphalerite> ah so a replacement for dezgeg's basically?
<sphalerite> samueldr: isn't it even armv8, but 32-bit? i.e. more featureful than armv7
<samueldr> alng the lines, for armv6l
<sphalerite> I think dezgeg had both armv6 and armv7
<samueldr> sphalerite: I think it is, but I think for all intents and purposes it's pretty equivalent for armv7/armv8
<samueldr> at least in my limited testing
<samueldr> yeah, armv7l we® might try doing it with kvm
<samueldr> in my limited testing there were no issues of v8 specifics leaking into the build; the iso image booted on real non-aarch64 hardware
<gchristensen> speaking of which samueldr would you like a poison gift of 5 cm1s? :)
<gchristensen> I stopped trying to make them work and they've ended up in my physical bit bucket
<samueldr> ah
<samueldr> once I know I can make them work in a useful manner, I wouldn't mind
<gchristensen> cool
vcunat has quit [Ping timeout: 250 seconds]
wildtrees has joined #nixos-aarch64
wildtrees has quit [Max SendQ exceeded]
wildtrees has joined #nixos-aarch64
ris has joined #nixos-aarch64
orivej has joined #nixos-aarch64
worldofpeace has joined #nixos-aarch64
<worldofpeace> Hey, I need to test #66338 with the sd_image. Can I do this virtually?
<{^_^}> https://github.com/NixOS/nixpkgs/pull/66338 (by worldofpeace, 3 days ago, open): installer: Don't run as root
<samueldr> with emulation, and the right u-boot, the sd_image should be testable... but with _emulation_ (so slow)
<samueldr> last time I tried u-boot with qemu kvm didn't work
<worldofpeace> yeah that's what I was worried I'd get myself into
<samueldr> I wouldn't wish that on anyone :)
<samueldr> though it would be great if u-boot would work with kvm
<samueldr> (maybe it does now)
<samueldr> (I haven't verified)
<worldofpeace> yeah I don't think I'd be able to do this samueldr . Would it be fine to bypass that test given I've tested everything else?
<samueldr> I'll run that this evening after $work
<samueldr> it should still work fine, I'm like 99% sure
<samueldr> the main issue I think will be documentation-wise, for all installations
<samueldr> we might see a lot of support requests about that early in the 19.09 release cycle
<worldofpeace> indeed, and it's not like the manual is super searchable and I've seen people rely on like external guides even
zupo has joined #nixos-aarch64
<worldofpeace> thanks in advance, awaiting your findings 💖 samueldr
zupo has quit [Ping timeout: 248 seconds]
jtojnar has quit [Ping timeout: 245 seconds]
orivej has quit [Ping timeout: 268 seconds]
jtojnar has joined #nixos-aarch64
orivej has joined #nixos-aarch64
zupo has joined #nixos-aarch64
t184256 has left #nixos-aarch64 ["Disconnected: Replaced by new connection"]
t184256 has joined #nixos-aarch64
zupo has quit [Ping timeout: 268 seconds]
jtojnar has quit [Read error: Connection reset by peer]
jtojnar has joined #nixos-aarch64
ryantrinkle has quit [Ping timeout: 258 seconds]
<DigitalKiwi> what is a good touchscreen that works with raspberry pi and nixos?
<samueldr> [this space has been left blank intentionally]
<samueldr> :)
<samueldr> I still haven't managed to make the ones I got to learn about that work properly
<samueldr> but I'm working with the mainline kernel
<samueldr> instead of the rpi foundation's kernel
<DigitalKiwi> sad day
<samueldr> I think the answer to that is "any that works and is properly documented to work with the mainline kernel"
<samueldr> the documented part might be harder
<samueldr> OR, by using the foundation's bits
<gchristensen> DigitalKiwi: for this project, SSH might be just a better overall choice :)
<samueldr> when I next come around to that, I'll try with the rpi foundation kernel to sanity check the everything else
<DigitalKiwi> but i want pretty controls :(
<DigitalKiwi> 3 ft thermostat
<samueldr> one of the two I got wasn't expected; got it when locally sourcing a pi2+pi3 off craigslist-equivalent
<samueldr> but it sure would be nice to have the touch part working (it's hdmi based to the display)
<samueldr> then I could yak shave and bike shed a nice dashboard thing
orivej has quit [Ping timeout: 246 seconds]
vika_nezrimaya has joined #nixos-aarch64
wildtrees has quit [Quit: Leaving]
ris has quit [Ping timeout: 258 seconds]