<DigitalKiwi> samueldr: how do i get something that wants /dev/vcio
<DigitalKiwi> to work
<samueldr> I don't know what's /dev/vcio
<samueldr> so I don't know
<DigitalKiwi> :<
<clever> DigitalKiwi: one min
<clever> drivers/char/broadcom/vcio.c: ret = alloc_chrdev_region(&vcio.devt, 0, 1, "vcio");
<clever> its in this file of the kernel source
<samueldr> I'm not all that hip in the raspberry pi specific ecosystem
<clever> 2 obj-$(CONFIG_BCM_VCIO) += vcio.o
<samueldr> in fact I kinda dislike the specificity, rather than being standard stuff
<clever> you must compile the kernel with BCM_VCIO=y or BCM_VCIO=m
<clever> and then modprobe vcio?
<DigitalKiwi> oh
<DigitalKiwi> do we have a kernel with that
<clever> DigitalKiwi: what does `modprobe vcio` say?
<DigitalKiwi> not found
<DigitalKiwi> Linux rpi-nixos 4.19.86 #1-NixOS SMP Sun Nov 24 07:21:09 UTC 2019 aarch64 GNU/Linux
<clever> DigitalKiwi: mainline or rpi kernel?
<DigitalKiwi> mainline i think
<DigitalKiwi> idk :(
<clever> DigitalKiwi: thats set by your boot.kernelPackages config
<DigitalKiwi> i don't set it
<clever> then your on mainline
<clever> try changing it to the rpi kernel
<DigitalKiwi> ok
<clever> 2020-01-25 15:25:28 < m15k> Do I need `boot.kernelPackages = pkgs.linuxPackages_rpi3;` in my `configuration.nix` for RPI3?
<clever> 2020-01-25 15:26:45 < samueldr> if you want to use the raspberry pi foundation's kernel
<DigitalKiwi> thanks
<DigitalKiwi> hope this works
<clever> the option may also exist in mainline, and just needs to be flipped on
<DigitalKiwi> how would i do that
<DigitalKiwi> do you know if there's somewhere the hwver would be https://github.com/jgarff/rpi_ws281x/blob/master/rpihw.c#L338
<DigitalKiwi> with this kernel it has /proc/device-tree which it didn't before but not /proc/device-tree/system/
rajivr___ has joined #nixos-aarch64
<DigitalKiwi> ...
<DigitalKiwi> it didn't switch kernel??? but that wasn't there last time
<clever> DigitalKiwi: what about `modprobe vcio`?
<DigitalKiwi> it didn't work
<DigitalKiwi> but my uname is the same as before
<DigitalKiwi> it shouldn't be the same
<clever> DigitalKiwi: not sure then
<DigitalKiwi> ...
<DigitalKiwi> it didn't reboot
<clever> nixos-rebuild wont reboot on its own
<DigitalKiwi> or i can't tell the difference between the time and uptime
h0m1 has quit [Ping timeout: 248 seconds]
<DigitalKiwi> love that nix search takes a gig of ram on my computer with a gig of ram
<DigitalKiwi> I ThOuGhT C++ WaS SuPpOsEd To Be FaSt
h0m1 has joined #nixos-aarch64
<samueldr> look at how quickly it fills your ram
<DigitalKiwi> ;_;
<DigitalKiwi> (it filled it slowly)
<DigitalKiwi> lol hnix
<DigitalKiwi> i got it up to using ~55GB of ram the other day
<DigitalKiwi> and then i killed it
<DigitalKiwi> about every 10 minutes it went up by 1-1.5 on average GB
<DigitalKiwi> oh no, i think i forgot to save the stats i collected ;_;
<DigitalKiwi> it took something like 3 hours to get there
orivej has joined #nixos-aarch64
wavirc22_ has quit [Ping timeout: 268 seconds]
wavirc22 has joined #nixos-aarch64
wavirc22 has quit [Ping timeout: 268 seconds]
wavirc22 has joined #nixos-aarch64
wavirc22 has quit [Ping timeout: 265 seconds]
wavirc22 has joined #nixos-aarch64
wavirc22 has quit [Read error: Connection reset by peer]
wavirc22 has joined #nixos-aarch64
wavirc22 has quit [Read error: Connection reset by peer]
wavirc22 has joined #nixos-aarch64
wavirc22 has quit [Ping timeout: 268 seconds]
orivej has quit [Ping timeout: 268 seconds]
wavirc22 has joined #nixos-aarch64
wavirc22 has quit [Read error: Connection reset by peer]
wavirc22 has joined #nixos-aarch64
wavirc22 has quit [Ping timeout: 265 seconds]
wavirc22 has joined #nixos-aarch64
wavirc22 has quit [Read error: Connection reset by peer]
wavirc22 has joined #nixos-aarch64
m15k has joined #nixos-aarch64
<m15k> Is it normal that the raspberry pi 3 is blinking 2 times (https://elinux.org/R-Pi_Troubleshooting#Green_LED_blinks_in_a_specific_pattern) is indicating that the sd card cannot be read. But nixos is booting from it.
<lopsided98> m15k: The green LED should not be flashing, but the blink patterns in your link will only occur due to failures very early in the boot process. On the other hand, the red LED will blink continuously because the mainline kernel configures it as a heartbeat LED by default.
<m15k> lopsided98: Red LED is constantly on. Green light is blinking twice. Stops. And blink twice again.
<lopsided98> Yeah, actually that is correct. I mixed up the colors. The one that blinks should be labelled ACT
<m15k> Can the heartbeart rate be adjusted?
<m15k> And/Or be disabled
<lopsided98> The heartbeat rate is proportional to the CPU load. On my RPi 2 you can temporarily change the LED trigger by writing to /sys/class/leds/ACT/trigger
<lopsided98> I'm not sure if the LED name is the same on the RPi 3
<lopsided98> cat that file to see the available options
t184256 has left #nixos-aarch64 [#nixos-aarch64]
t184256 has joined #nixos-aarch64
m15k has quit [Ping timeout: 260 seconds]
orivej has joined #nixos-aarch64
bdesham has joined #nixos-aarch64
ryantrinkle has quit [Ping timeout: 265 seconds]
rajivr___ has quit [Quit: Connection closed for inactivity]
t184256 has left #nixos-aarch64 ["Error from remote client"]
t184256 has joined #nixos-aarch64
ryantrinkle has joined #nixos-aarch64
orivej has quit [Ping timeout: 268 seconds]