<samueldr> now that y'all have had your issues with it
<samueldr> I can maybe start getting mine together
<angerman> samueldr: if you happen to have some spare silent 80mm pwm fans lying around, substitute those that come with the package. They can be loud.
<samueldr> spare fans? maybe I should get on onlyfans first
<sphalerite> hahahaha
<samueldr> hm, are they really annoying to get to once built-up?
<sphalerite> no
monk has left #nixos-aarch64 ["Error from remote client"]
<sphalerite> amongst the least annoying things
<angerman> Only under load.
<sphalerite> undo 4 screws to get the back of the case off, then 4 screws per fan
<samueldr> great, then I'll ignore this for now and put something on order somehow somewhen if I ever order stuff where noctua (or other recommentations) are sold
<angerman> But then, I have it sitti next to me on my desk.
monk has joined #nixos-aarch64
<samueldr> it'll be close to where my desk is
<samueldr> but there's other things that are annoying around, so maybe it won't be the worst
<sphalerite> though actually the wires are annoying because they're tied to some other stuff with cable ties
<sphalerite> if you follow the instructions
<sphalerite> it's really quiet when there's no load on it
<samueldr> haha, cable ties... I haven't looked at the instructions yet, but I would have substituted for hook-and-loops straps
<sphalerite> (and it's not just shutting down)
<angerman> It’s pretty annoying to swap the pwm connectors with just the back plate removed. Quite fiddly and you need to remove the power plugs as well
<sphalerite> oh yeah, forgot about that…
<sphalerite> one thing I learned from getting the helios64 is that if I ever have the choice between a kit and a pre-assembled device, I should generally take the pre-assembled device.
<samueldr> I actually didn't realise when I ordered that it was a kit
<samueldr> I thought it was pre-assembled, with a tray for the mobo
<angerman> It looks like mine has leveled out.
<angerman> Initially it wasn’t level on the desk.
<sphalerite> ah nice
<angerman> Either it has dented the desk sufficiently or the metal has adjusted a bit.
<sphalerite> or the feet have compressed a bit?
<angerman> It was almost a full feet up.
<angerman> As in 2mm or so. Not imperial feet.
<sphalerite> hah
<sphalerite> I haven't attached the feet to mine yet, since I'm not sure which orientation I want it in
<sphalerite> or which orientation the future owner will want it in
<angerman> Smart
<sphalerite> (I won't be keeping it for long after my honeycomb arrives, if all goes well)
<samueldr> and if I had an honeycomb it would be to use as a workstation, not as a glorified NAS ;)
<sphalerite> my honeycomb will be a NAS/build server/router/everything basically :p
<sphalerite> everything except a workstation
<angerman> I’ve got a Mac mini for that ;)
<sphalerite> ok I'm really confused now…
<sphalerite> I'm setting CPU_LITTLE_ENDIAN = yes and CPU_BIG_ENDIAN = no in extraStructuredConfig, yet the config script answers 1 for the big-endian/little-endian question
<sphalerite> well, time for digging through perl.
<sphalerite> what? 1:25am? I don't know what you're talking about
<samueldr> sounds like a friday to me
<sphalerite> ah-ha! It's a bug in generate-config.pl!
Darkmatter66_ has quit [Ping timeout: 272 seconds]
<sphalerite> fix: #107181
<{^_^}> https://github.com/NixOS/nixpkgs/pull/107181 (by lheckemann, 12 seconds ago, open): linux: fix generate-config's handling of "no-choice" options
lovesegfault has quit [Quit: WeeChat 3.0]
<samueldr> welp, even though it's in the kernel, kexec doesn't work on the mediatek device
<samueldr> not really surprised, since the build didn't even work out of the box
lovesegfault has joined #nixos-aarch64
h0m1 has quit [Ping timeout: 260 seconds]
Ultrasauce_ has quit [Read error: Connection reset by peer]
Ultrasauce has joined #nixos-aarch64
jdnixx-M1 has quit [Ping timeout: 260 seconds]
lopsided98_ has quit [Ping timeout: 260 seconds]
lopsided98 has joined #nixos-aarch64
h0m1 has joined #nixos-aarch64
jdnixx-M1 has joined #nixos-aarch64
<samueldr> though looking at the ramoops... it might not be that kexec isn't working, but that the kernel implementation of drivers is terrible
<samueldr> there is a bug with the display driver, where it won't suspend or shutdown, but rather will panic because of *something*
<samueldr> which my guesstimate is that it assumes there is a userspace component part of Android that does things
<samueldr> and no checks
<samueldr> though the good news is that for _that_ particular crash I have confirmed what was a suspicion
h0m1 has quit [Ping timeout: 260 seconds]
h0m1 has joined #nixos-aarch64
orivej has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 264 seconds]
evils has quit [Quit: Lost terminal]
evils has joined #nixos-aarch64
veleiro has quit [Read error: Connection reset by peer]
veleiro has joined #nixos-aarch64
<sphalerite> gah. Having similar problems with the helios64's eMMC as on the chromebook.
veleiro has quit [Read error: Connection reset by peer]
veleiro has joined #nixos-aarch64
<Ke> what problems?
<Ke> clocks too high on u-boot and fail?
<sphalerite> [ 4.658218] mmc1: mmc_select_hs200 failed, error -110 // [ 4.663912] mmc1: error -110 whilst initialising MMC card
<sphalerite> is that u-boot's fault?
<Ke> probably not, I guess
<sphalerite> aw, and there I was getting my hopes up :p
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
veleiro has quit [Read error: Connection reset by peer]
veleiro has joined #nixos-aarch64
rajivr has joined #nixos-aarch64
zupo has joined #nixos-aarch64
veleiro has quit [Read error: Connection reset by peer]
veleiro has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
FRidh has joined #nixos-aarch64
veleiro has quit [Read error: Connection reset by peer]
veleiro has joined #nixos-aarch64
Darkmatter66 has joined #nixos-aarch64
veleiro has quit [Read error: Connection reset by peer]
veleiro has joined #nixos-aarch64
veleiro has quit [Read error: Connection reset by peer]
veleiro has joined #nixos-aarch64
<angerman> sphalerite: I’m running off of the emmc ...
veleiro has quit [Read error: Connection reset by peer]
veleiro has joined #nixos-aarch64
veleiro has quit [Read error: Connection reset by peer]
veleiro has joined #nixos-aarch64
veleiro has quit [Read error: Connection reset by peer]
veleiro has joined #nixos-aarch64
veleiro has quit [Read error: Connection reset by peer]
veleiro has joined #nixos-aarch64
<sphalerite> angerman: maybe I'm just cursed.
veleiro has quit [Read error: Connection reset by peer]
veleiro has joined #nixos-aarch64
<sphalerite> angerman: I'm playing with the fans a bit now, funny thing is they don't even have much of an effect on the CPU temperature (which of course they _are_ controlled by
Darkmatter66 has quit [Ping timeout: 260 seconds]
veleiro has quit [Read error: Connection reset by peer]
<sphalerite> it would make a lot more sense to base the fan speed on HDD temperature.
veleiro has joined #nixos-aarch64
<Ke> how come firefox-unwrapped is not in the cache?
<sphalerite> I think it was removed from the channel blockers because it frequently held the channel up. Not sure if that was because it took long to build or because it was failing
<clever> sphalerite: and once again, i'm reminded of how much apt sucks, lol
<clever> ffmpeg shows that it was built with --enable-rpi
<clever> `apt-get source ffmpeg` gives me source that lacks an --enable-rpi option
<clever> fail :P
<clever> now how am i supposed to port this to nixpkgs...
<sphalerite> clever: maybe there are patches in debian/ ?
veleiro has quit [Read error: Connection reset by peer]
<clever> lots of junk there, but no patch file
<sphalerite> Ke: hm, the job seems to have timed out on hydra.
<clever> there is a rules file, which contains the configure args
veleiro has joined #nixos-aarch64
<clever> but it doesnt match what ffmpeg itself was claiming it was built with
<Ke> does nixos need more hydra for aarch64
<sphalerite> I've kicked the job, so it'll try building it again
<sphalerite> Ke: I _think_ we're okay for capacity now that the thunderx machines are operational again. Not sure though, gchristensen would be the one to know.
<clever> hmmm, but maybe h264_v4l2m2m works out of the box already....
<sphalerite> oh and the 2a5 machines which are new
<clever> now, how did i install nix before...
orivej has joined #nixos-aarch64
<sphalerite> Ke: well right now lots of the hydra aarch64 machines are running idle, so if there are capacity problems at least they're not leading to a massive backlog of queued builds.
<Ke> how would one get that timeout then?
<Ke> is the timeout just unreasonably short for a single package
lgcl has joined #nixos-aarch64
<clever> pi@raspberrypi:~ $ nix-env -iA nixpkgs.ffmpeg
<clever> now, how lucky will i be? ...
<clever> hydra's got me covered :D
<clever> pi@raspberrypi:~ $ ffmpeg -decoders | grep h264
<clever> V..... h264_v4l2m2m V4L2 mem2mem H.264 decoder wrapper (codec h264)
<clever> bingo!
veleiro has quit [Read error: Connection reset by peer]
veleiro has joined #nixos-aarch64
veleiro has quit [Read error: Connection reset by peer]
veleiro has joined #nixos-aarch64
alpernebbi has joined #nixos-aarch64
<sphalerite> angerman: have you had issues with the helios64 becoming unreachable via gigabit ethernet too?
<sphalerite> I think this is the same old checksum offloading issue I have with the nanopi m4 as well
veleiro has quit [Read error: Connection reset by peer]
veleiro has joined #nixos-aarch64
<sphalerite> FWIW: the fix is ethtool --offload eth0 tx off
<angerman> sphalerite: i did run that on a hunch from the rock pi4. But is that persistent?
<angerman> I’ve certainly rebooted it since and done quite a bit of iperf tests. Never became unresponsive unless it panicked.
<sphalerite> it's not persistent
<sphalerite> how does iperf test? iirc the problems usually only occur when there's lots of TCP load
veleiro has quit [Read error: Connection reset by peer]
veleiro has joined #nixos-aarch64
<angerman> Idk to be honest, I just tried to ensure that the 1Gb link worked. Got 995Mbit
<angerman> sphalerite: supposedly recent kernels have this fixed though. I think I saw patches for it. So 🤷
veleiro has quit [Read error: Connection reset by peer]
veleiro has joined #nixos-aarch64
veleiro has quit [Read error: Connection reset by peer]
veleiro has joined #nixos-aarch64
cole-h has joined #nixos-aarch64
veleiro has quit [Read error: Connection reset by peer]
veleiro has joined #nixos-aarch64
lgcl has quit [Quit: ERC (IRC client for Emacs 27.1)]
veleiro has quit [Read error: Connection reset by peer]
veleiro has joined #nixos-aarch64
veleiro has quit [Read error: Connection reset by peer]
veleiro has joined #nixos-aarch64
cole-h has quit [Ping timeout: 272 seconds]
veleiro has quit [Read error: Connection reset by peer]
veleiro has joined #nixos-aarch64
lgcl has joined #nixos-aarch64
lgcl has quit [Client Quit]
lgcl has joined #nixos-aarch64
lgcl has quit [Client Quit]
lgcl has joined #nixos-aarch64
lgcl has quit [Quit: ERC (IRC client for Emacs 27.1)]
lgcl has joined #nixos-aarch64
lgcl has quit [Client Quit]
lgcl has joined #nixos-aarch64
lgcl has quit [Client Quit]
lgcl has joined #nixos-aarch64
lgcl has quit [Client Quit]
lgcl has joined #nixos-aarch64
lgcl has quit [Quit: ERC (IRC client for Emacs 27.1)]
Darkmatter66 has joined #nixos-aarch64
lgcl has joined #nixos-aarch64
<Ke> wonder if compiling firefox on nixos is more than it was on gentoo
<Ke> that would translate to maybe 90 mins on this device
<sphalerite> I recently compiled firefox on my laptop in something like that amount of time
<sphalerite> oh, looks like it errored out this time rather than timing out
rajivr has quit [Quit: Connection closed for inactivity]
<Ke> still building
<Ke> I guess longer than linux
veleiro has quit [Ping timeout: 260 seconds]
luigy has joined #nixos-aarch64
veleiro has joined #nixos-aarch64
lgcl has quit [Quit: ERC (IRC client for Emacs 27.1)]
veleiro has quit [Ping timeout: 264 seconds]
lgcl has joined #nixos-aarch64
lgcl has quit [Client Quit]
<samueldr> sphalerite: emmc brand and size please :)
<samueldr> sounds like the kernel driver really has a marginal behaviour
lgcl has joined #nixos-aarch64
lgcl has quit [Remote host closed the connection]
lgcl has joined #nixos-aarch64
veleiro has joined #nixos-aarch64
lgcl has quit [Remote host closed the connection]
lgcl has joined #nixos-aarch64
lgcl has quit [Remote host closed the connection]
dstzd has quit [Quit: ZNC - https://znc.in]
veleiro has quit [Ping timeout: 260 seconds]
dstzd has joined #nixos-aarch64
Darkmatter66 has quit [Ping timeout: 260 seconds]
dstzd has quit [Client Quit]
lgcl has joined #nixos-aarch64
lgcl has quit [Client Quit]
FRidh has quit [Quit: Konversation terminated!]
lgcl has joined #nixos-aarch64
<Ke> yes, indeed build fails with error message somewhere
<Ke> I guess no migration to nixos for gui
veleiro has joined #nixos-aarch64
dstzd has joined #nixos-aarch64
dstzd has quit [Remote host closed the connection]
dstzd has joined #nixos-aarch64
alpernebbi has quit [Quit: alpernebbi]
Darkmatter66 has joined #nixos-aarch64
lgcl has quit [Ping timeout: 260 seconds]
veleiro has quit [Read error: Connection reset by peer]
Darkmatter66 has quit [Quit: ZNC 1.7.5 - https://znc.in]
fooker has quit [Ping timeout: 272 seconds]
fooker has joined #nixos-aarch64
kcalvinalvin has quit [Ping timeout: 240 seconds]
kcalvinalvin has joined #nixos-aarch64
rajivr has joined #nixos-aarch64
AmandaC has quit [Quit: Toodles]
AmandaC has joined #nixos-aarch64