<colemickens>
Anyone want to hack on rpi4 netboot stuff? Someone emailed me about it, I still want to get it working. Im thinking of dedicating tomorrow to it
<samueldr>
step 1, buy a net, step 2, buy a boot
alp_ has quit [Ping timeout: 272 seconds]
rajivr has joined #nixos-aarch64
Ericson2314 has quit [Ping timeout: 244 seconds]
Ericson2314 has joined #nixos-aarch64
<NickHu>
Anyone know how to get mic working on PBP?
<NickHu>
There's like a billion devices in alsamixer
h0m1 has quit [Ping timeout: 264 seconds]
<NickHu>
Speakers work fine
<NickHu>
(After running the reset-audio ruby script)
h0m1 has joined #nixos-aarch64
justanotheruser has quit [Ping timeout: 264 seconds]
justanotheruser has joined #nixos-aarch64
orivej has quit [Ping timeout: 264 seconds]
orivej has joined #nixos-aarch64
alp_ has joined #nixos-aarch64
orivej has quit [Ping timeout: 272 seconds]
<LinuxHackerman>
Nick Hu: if the PBP is anything like the chromebooks, be very careful with those controls. They can fry your speakers.
<patagonicus>
Ke: Just a few days ago I finally put NixOS on my (x86) laptop and then made the switch to sway, mostly because you can actually have different scaling for HiDPI on different screens and it just works. That also fixed tearing and some Chrome bug I had.
<patagonicus>
But I haven't figured out yet how to do autologin. Currently I manually log in on tty1 and run exec sway.
heywoodlh has quit [Ping timeout: 246 seconds]
<LinuxHackerman>
patagonicus: put `[[ $(tty) = "/dev/tty1" ]] && exec sway` in your shell init, and enable tty autologin?
<patagonicus>
Ah, tty autologin was the thing I wasn't sure about.
FRidh has joined #nixos-aarch64
red[evilred] has joined #nixos-aarch64
<red[evilred]>
my God
<red[evilred]>
is the Raspberry Pi foundation ever going to keep 8G RAM Pi 4s in stock?
<simpson>
Ooh, that reminds me that I wanted to order hardware before the Christmas rush. Probably too late for that to really be rush-avoiding.
<red[evilred]>
no stock until February if you can believe that
<simpson>
Curse my inability to actually get stuff done. I could have ordered it a month ago but I was indecisive and worried about the laughably modest capex.
<red[evilred]>
what kinda hardware do you have in mind?
<simpson>
Ooh, nice. I see we're thinking along the same lines of how to run these at relatively high load and get that extra heat off.
adamzivcak has joined #nixos-aarch64
<red[evilred]>
Can ship immediately:
<red[evilred]>
11339
<red[evilred]>
Foujnd them all
<red[evilred]>
apparently Allied has 11,000 of them in stock
<red[evilred]>
not sure I believe them
<red[evilred]>
the question is - can I retire my 500Mhz ARM NAS cluster
<simpson>
Sounds like when Chinese chemical companies claim to have $CORROSIVE_NUISANCE by the gallon.
<red[evilred]>
if I can find a suitable USB <-> SATA bridge
<simpson>
Like, as soon as you place the order, suddenly nope, they've never had any stock ever, and they don't know why you would be asking~
<simpson>
Why would you retire that? That sounds rad.
<simpson>
I guess maybe it's a pain to maintain.
<red[evilred]>
nah, its performance is sub par
adamzivcak is now known as adamZivcak
adamZivcak is now known as adamzivcak
<red[evilred]>
which isn't surprising at 500Mhz CPU really
adamzivcak25 has joined #nixos-aarch64
adamzivcak25 has quit [Remote host closed the connection]
adamzivcak has quit [Remote host closed the connection]
FRidh has quit [Ping timeout: 272 seconds]
FRidh has joined #nixos-aarch64
cole-h has quit [Ping timeout: 256 seconds]
FRidh has quit [Ping timeout: 246 seconds]
FRidh has joined #nixos-aarch64
cole-h has joined #nixos-aarch64
cole-h has quit [Ping timeout: 256 seconds]
adamzivcak has joined #nixos-aarch64
heywoodlh has joined #nixos-aarch64
adamzivcak has quit [Remote host closed the connection]
adamzivcak has joined #nixos-aarch64
adamzivcak has left #nixos-aarch64 [#nixos-aarch64]
sds2 has joined #nixos-aarch64
evalexpr has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
<sds2>
patagonicus: Sorry, I couldn't answer earlier. I tried again with a different approach but it didn't build the system either. Coreutils seems not to be involved in my case. I attached a picture of the error I got. Any ideas I could try? https://ibb.co/Jc85VG9
<patagonicus>
sds2: I'd check dmesg - segfault sounds like you ran out of RAM and the oomkiller killed it.
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
<patagonicus>
Otherwise, if you give me the version of your nixpkgs I can try building it to see if it works. That's somewhere in /nix/var, but I have to check where exactly.
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
<sds2>
patagonicus: I rebooted already and can't access dmesg for this build anymore. Could you have a look at my config.nix and tell me if I'm doing something totally wrong in there? I took the example from the NixOS on ARM wiki page and adapted it. I'm not sure if that's the right approach at this step... https://pastebin.pl/view/fa20f4ac
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
<patagonicus>
Looks reasonable (don't know about the kernel args, but I doubt they'd cause segfaults in any case). My guess is that the 1 GB of swap is not enough.
<patagonicus>
I don't know how much RAM your chip has, but it's probably not a lot. :)
<sds2>
patagonicus: Yes, not much. The device has 2GB DDR3 in total. Do you think it's pointless to try something else?
<patagonicus>
You could see if it does parallel compilation and dial that back, but that would also make it slower. I'd recommend adding some kind of SATA disk (it has SATA, right?) and using 10 or 20 GB of that for swap.
<sds2>
patagonicus: Yes, it has SATA. Okay, then I will try this approach next. :)
alp_ has joined #nixos-aarch64
<patagonicus>
You should check the channel logs for coreutils, it's a known problem, at least upstream. There's a patch for it, but it's also needed for a few other packages that fail the same way. Basically, if your coreutils fails to install because of a couple of failed tests, it's that bug. :)
<{^_^}>
#103925 (by lopsided98, 2 weeks ago, open): coreutils, findutils, gnutls: fix build on 32-bit ARM
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
<patagonicus>
Oh, nice. I was too lazy to file a report for it and I have the patch in my local nixpkgs repo.
<patagonicus>
Unfortunately I'll still need the patch for updating the Hardkernel kernel version since my PR doesn't seem to get merged.
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
<patagonicus>
Hmm. How difficult is it to take an existing nixpkgs derivation and make it compile to a static binary? I'm wondering if I could use my ARM machine to compile stuff like tmux for my LaMetric while I poke around.
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
<patagonicus>
Oh, ok, tmux has a --enable-static flag, that shouldn't be difficult then. :)
red[evilred] has quit [Quit: Idle timeout reached: 10800s]
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
v0|d has quit [Ping timeout: 240 seconds]
<tilpner>
patagonicus: There's also pkgsStatic.tmux
<patagonicus>
Even better. I should work right now, but I'll take a look later. I want to play with the framebuffer and it's weird encoding.
<patagonicus>
Ah, I haven't tried querying the device for info, was just going off a very sparse Reddit post.
<patagonicus>
It's not regular RGB encoding, it uses two bytes, but also has special values for whites. And the screen is weird - 36x8, but only the left 8 columns can do colors.
<LinuxHackerman>
yeah, the fbdev ioctls should let you get info about it.
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
<patagonicus>
Is there an existing tool for that or do I need to write my own? ^^
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
<LinuxHackerman>
patagonicus: well… you can run an X server with the fbdev driver
<patagonicus>
Hah. Yeah. Don't think that'll be easier than writing my own C code for it.
<sphalerite>
patagonicus: are you sure?
<sphalerite>
that lets you forget all about the pixel-format specifics.
<patagonicus>
Can X run on less than 300 pixels? And I'd have to compile it first.
<patagonicus>
Plus, showing regular X apps doesn't really work, I'd have to write something custom anyway, adding a bit that moves an image to fb0 shouldn't be much more work.
<patagonicus>
But, I've finally put in the "work" of connecting my laptop to my switch via ethernet so I can connect to the internet at the same time I'm connected to the LaMetric. Let's build the static tmux and see if that works.
<patagonicus>
Yeah, it doesn't like something. It tries to build bash, but its configure claims the C compiler doesn't produce executables.
<LinuxHackerman>
yeah X on small screens should work no problem
<LinuxHackerman>
and it'll let you run e.g. an SDL application with a lot less hassle than fiddling around with the fb directly
<LinuxHackerman>
and yeah pkgsStatic doesn't work that well, it's probably best if you can make dynamic stuff work on there
adamzivcak1 has joined #nixos-aarch64
adamzivcak1 has left #nixos-aarch64 [#nixos-aarch64]
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
FRidh has quit [Ping timeout: 256 seconds]
FRidh has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
<patagonicus>
I probably can. I want to try to see if I can put nix on it. But until then a statically compiled Go program sounds like the easiest way to use it. The main problem is figuring out what API I should use for a screen that doesn't have color for all pixels. Will probably just use the blue channel or something for those pixels.
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
FRidh has quit [Ping timeout: 260 seconds]
FRidh has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
zupo has quit [Ping timeout: 260 seconds]
zupo has joined #nixos-aarch64
adamzivcak has joined #nixos-aarch64
<patagonicus>
Oh, wow, it has ffmpeg preinstalled. mpd I can understand, since it has a speaker, but ffmpeg?
adamzivcak has left #nixos-aarch64 [#nixos-aarch64]
adamzivcak has joined #nixos-aarch64
adamzivcak has left #nixos-aarch64 [#nixos-aarch64]
monk has left #nixos-aarch64 ["Error from remote client"]
monk has joined #nixos-aarch64
<clever>
patagonicus: ffmpeg has been patched to support the h265 hw decode on the pi4
<patagonicus>
I'm guessing they might use it for audio transcoding, but I'm reasonably confident they're not showing videos. Maybe transcoding some GIFs, but I'd use imagemagick for that.
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
<patagonicus>
Has anyone seen a "crypt_luks" binary before. --help says "partitions crypt utility" and also "Report bugs to ." without any address.
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo has quit [Ping timeout: 264 seconds]
FRidh has quit [Ping timeout: 240 seconds]
zupo has joined #nixos-aarch64
<patagonicus>
So, kernel info says 5 bits blue, six bits green and then five bits red. But most values give black for the non-color pixels, so dunno.
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
alp_ has quit [Ping timeout: 264 seconds]
sds2 has quit [Client Quit]
sds2 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
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
rajivr has quit [Quit: Connection closed for inactivity]
<patagonicus>
Ok, there's definitely some truth to that, but also some values have the same brightness. Red and blue don't turn on until you get to 0xb for them, for green it's 0x16, which makes sense since it has one more bit and that's double of 0xb.
<patagonicus>
White LEDs turn on if red == blue and green == red << 1 and the brightness is based on the value. That's also ok.
<patagonicus>
But for higher values there's a difference for each bit. For red 0xa to 0xe are the same color, for 0xf to 0x14 it's always two values with the same color, but weirdly 0x18 and 0x19 also have the same color, which I don't understand.
<patagonicus>
Maybe it's related to the brightness adjustment based on the light sensor. That either seems to be handled in hardware or in the kernel.
alp_ has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
<sphalerite>
patagonicus: do red and blue stay on if you set them to 0xb, then reduce them?
<patagonicus>
Nope
<patagonicus>
Haven't found anything where the previous value matters.
<patagonicus>
I do now have a Go-Server that gives me a website with three sliders for red green and blue and if I move them it updates the color of the whole screen, though. :)
Lordcirth has joined #nixos-aarch64
<Lordcirth>
samueldr, qtwebengine 5.14 fails to compile on my pinebook pro, any ideas?
<Lordcirth>
Oh, logs say it was OOM, nvrm. Guess I'll increase swap and build overnight again
monk has left #nixos-aarch64 ["Error from remote client"]
h0m1 has quit [Quit: WeeChat 3.0]
h0m1 has joined #nixos-aarch64
monk has joined #nixos-aarch64
veleiro has joined #nixos-aarch64
andi- has quit [Ping timeout: 244 seconds]
andi- has joined #nixos-aarch64
AmandaC has quit [Quit: Toodles]
AmandaC has joined #nixos-aarch64
orivej has quit [Ping timeout: 260 seconds]
Dezgeg has quit [Ping timeout: 260 seconds]
zupo has joined #nixos-aarch64
pinkieval has quit [Quit: We're here, we're queer, connection reset by peer.]
pinkieval has joined #nixos-aarch64
adamzivcak1 has joined #nixos-aarch64
adamzivcak1 has left #nixos-aarch64 [#nixos-aarch64]
sds2 has quit [Ping timeout: 240 seconds]
Dezgeg has joined #nixos-aarch64
orivej has joined #nixos-aarch64
<sphalerite>
Can I get the kernel to do software PWM on a GPIO to expose it as a hwmon fan?
<sphalerite>
I mean, I'm fairly sure that's possible somehow. Just hoping I can do it at runtime and don't have to mess with device trees.
<sphalerite>
clever: this seems like something you would know about.
<sphalerite>
I mean, I can do it from userspace using `while gpioset -u 100000 -m time 1 0=0 ; do gpioset -u 100000 -m time 1 0=1 || break ; done` or an equivalent C program that uses a lot less system calls… but I'm pretty sure this is a function that should be available in the kernel, which would save even more context switching :)
monk has left #nixos-aarch64 ["Error from remote client"]