justanotheruser has quit [Read error: Connection reset by peer]
justanotheruser has joined #nixos-aarch64
justanotheruser has quit [Read error: Connection reset by peer]
orivej has quit [Ping timeout: 264 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 240 seconds]
justanotheruser has joined #nixos-aarch64
rajivr has joined #nixos-aarch64
h0m2 has quit [Ping timeout: 244 seconds]
h0m2 has joined #nixos-aarch64
zupo has joined #nixos-aarch64
dramforever has joined #nixos-aarch64
juliosueiras has quit [Ping timeout: 264 seconds]
orivej has joined #nixos-aarch64
<clever>
samueldr: reading the docs more, i think the A53 might always have ECC on the L1/L2, the doc doesnt mention it as being optional, and it has error injection as well, so i can try to cause a fault on my pi3, and then detect it
aminechikhaoui3 has joined #nixos-aarch64
wavirc22 has quit [Ping timeout: 258 seconds]
aminechikhaoui has quit [Read error: Connection reset by peer]
aminechikhaoui3 is now known as aminechikhaoui
wavirc22 has joined #nixos-aarch64
orivej has quit [Ping timeout: 264 seconds]
W1lkins has quit [Quit: Ping timeout (120 seconds)]
W1lkins has joined #nixos-aarch64
orivej has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
alp has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
knerten has joined #nixos-aarch64
orivej has quit [Ping timeout: 258 seconds]
dramforever has quit [Quit: Leaving]
cole-h has quit [Quit: Goodbye]
rajivr has quit [Quit: Connection closed for inactivity]
cdknight[m] has quit [Quit: Idle for 30+ days]
kai_w has quit [Quit: Idle for 30+ days]
<Mic92>
26
alp has quit [Remote host closed the connection]
alp has joined #nixos-aarch64
rajivr has joined #nixos-aarch64
alp has quit [Ping timeout: 246 seconds]
alp has joined #nixos-aarch64
zupo has joined #nixos-aarch64
superherointj has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<superherointj>
samueldr, I've been talking in #Pine64 about the issue, it seems the issue can be deeper than I was expecting, can I open an issue in NixOS for tracking the problem? I plan using the issue to relay information upstream. So it can reach people that can actually fix the problem.
zupo has joined #nixos-aarch64
orivej has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<{^_^}>
#97544 (by superherointj, 7 minutes ago, open): Libvirtd: In RockPro64 enabling Libvirtd triggers kernel panic on boot
juliosueiras has quit [Ping timeout: 240 seconds]
juliosueiras has joined #nixos-aarch64
juliosueiras has quit [Ping timeout: 265 seconds]
<superherointj>
It seems the problem is NixOS is using an old version of dmidecode (3.2 does not have a recent patch).
<Mic92>
superherointj: bumping that should not be too hard.
orivej has quit [Ping timeout: 258 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 260 seconds]
orivej has joined #nixos-aarch64
orivej_ has joined #nixos-aarch64
orivej has quit [Ping timeout: 265 seconds]
juliosueiras has joined #nixos-aarch64
alp has quit [Ping timeout: 264 seconds]
orivej_ has quit [Ping timeout: 264 seconds]
orivej has joined #nixos-aarch64
alp has joined #nixos-aarch64
alp has quit [Remote host closed the connection]
alp has joined #nixos-aarch64
alp_ has joined #nixos-aarch64
alp has quit [Ping timeout: 244 seconds]
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
alp_ has quit [Remote host closed the connection]
alp_ has joined #nixos-aarch64
cole-h has joined #nixos-aarch64
jumper149 has joined #nixos-aarch64
bennofs_ has joined #nixos-aarch64
bennofs__ has quit [Ping timeout: 256 seconds]
orivej has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-aarch64
alp_ has quit [Ping timeout: 264 seconds]
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-aarch64
alp_ has joined #nixos-aarch64
Darkmatter66_ has joined #nixos-aarch64
Darkmatter66 has quit [Ping timeout: 240 seconds]
rajivr has quit [Quit: Connection closed for inactivity]
h0m1 has joined #nixos-aarch64
h0m2 has quit [Ping timeout: 272 seconds]
h0m1 has quit [Client Quit]
h0m1 has joined #nixos-aarch64
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<superherointj>
I'm attempting to update the dmidecode package, but as I am new to NixOS world, I'm not sure how the mirroring service works. So I was unsure how to set the URL. Please give me some feedback. Thanks. \n https://gist.github.com/superherointj/f2f120222ab730238d89599159da8f2b
<superherointj>
Can I just set the URL straight without using the "mirror://" or should I use mirror?
<samueldr>
you should use mirror for releases, as it does some automatic stuff to ensure the data can be found
<superherointj>
The problem is 3.2 is latest release and 3.2 is broken for me. But from git master is fine.
<samueldr>
yeah
<samueldr>
looking quickly
<simpson>
In this case, I don't know if the mirror will have git snapshots. I'd consider `fetchgit` on git://git.savannah.gnu.org/dmidecode.git
<samueldr>
I think we should simply fetchpatch those recommended patches
<samueldr>
since it's the recommended
<samueldr>
so keep the "old" release as it is, and add patches = []; with appropriate fetchpatch calls
<simpson>
samueldr++ will also make it easier to merge upstream, which I gather is the plan.
<{^_^}>
samueldr's karma got increased to 264
<samueldr>
I would also add a comment on top of the patches list stating that these are recommended, to look at the project's page to see if there are additional recommended patches
<samueldr>
I feel this is kind of 3.2.${number of recommended patches}
<samueldr>
but in a haphazard way :/
<samueldr>
as if it was 3.2.8
<samueldr>
does that make sense, superherointj?
<superherointj>
Right.
<samueldr>
don't hesitate to ask for clarifications, I'm making a lot of assumptions about general comfort around Nixpkgs :)
<superherointj>
Thanks :)
alp_ has quit [Ping timeout: 246 seconds]
tilpner has quit [Remote host closed the connection]
tilpner has joined #nixos-aarch64
CyberManifest has joined #nixos-aarch64
<CyberManifest>
hi, is there an armhf 32 bit version of NixOS available ?
<samueldr>
not reall
<samueldr>
not really*
<simpson>
Hi, *which board*? It matters quite a bit. If you literally just need an unmarked embedded compiler, then `pkgsCross.armhf-embedded` can work.
<samueldr>
simpson: I assumed NixOS was the distro :)
<samueldr>
CyberManifest: assuming armv6l (e.g. raspberry pi 0, 1) or armv7l (many), 32 bit ARM, "not really"
<superherointj>
I need to compute sha256sum for a git patch 'normalized' the Nix way. Which tool is used for normalizing it?
<samueldr>
,tofu superherointj
<{^_^}>
superherointj: To get a sha256 hash of a new source, you can use the Trust On First Use model: use probably-wrong hash (for example: 0000000000000000000000000000000000000000000000000000), then replace it with the correct hash Nix expected. For inserting 52 0's in vim: <esc>52i0<esc>
<samueldr>
CyberManifest: you can cross-compile the minimal installer image, mostly, but it's not that useful since you're still faced with not having a binary cache for anything
<samueldr>
the main issue (as far as the foundation si concerned) is that there is no real server-class hardware to throw at the problem to compile for 32 bit ARM
<samueldr>
I was just now reading the backlog in #nixos
<CyberManifest>
samueldr: again, not a programmer
<CyberManifest>
samueldr: would nixpackager on debian be a better solution ?
<samueldr>
depends what you intend to do
<simpson>
What's the goal, exactly? You have to keep in mind that *somebody* has to compile everything.
<samueldr>
but the you're likely to face the same issue: needing to compile evertyhing
<samueldr>
(gosh, I can't type properly right now it seems :/)
<CyberManifest>
samueldr: use nix on reaspbbery pi
<CyberManifest>
samueldr: sorry about before, I was getting you mixed up with another channel/room
<superherointj>
samueldr, regarding the name of package. Instead of making up a number, would be more precise adding a label describing what it actually is, recommended patches, like "dmidecode-3.2-rp" (Recommended Patches). What do you think?
<samueldr>
no new package
<samueldr>
they're the recommended updates to dmidecode AFAICT
<superherointj>
So, just repeat old name? -3.2
<samueldr>
yeah, that's the version number they use
<samueldr>
kind of annyoing
<samueldr>
annoying*
<samueldr>
it's not that cold in the room, but my fingers are freezing somehow :/
* superherointj
has never seen snow.
* superherointj
has seen ice from the refrigerator.
<samueldr>
it's 12°C out, 87% humidity, quite good weather for making it feel cold in the room I guess... especially since the window next room is opened
Thra11 has quit [Ping timeout: 264 seconds]
Darkmatter66_ has quit [Quit: ZNC 1.7.5 - https://znc.in]
Darkmatter66 has joined #nixos-aarch64
justanotheruser has quit [Ping timeout: 244 seconds]