dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
ehmry has joined #nixos-aarch64
orivej has quit [Ping timeout: 256 seconds]
comrandroxaos[m] has quit [Quit: Idle for 30+ days]
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
alp has quit [Remote host closed the connection]
alp has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
FRidh has joined #nixos-aarch64
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
rajivr has joined #nixos-aarch64
orivej has joined #nixos-aarch64
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
alp has quit [Ping timeout: 272 seconds]
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
zupo has joined #nixos-aarch64
orivej has quit [Ping timeout: 240 seconds]
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
alp has joined #nixos-aarch64
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
zupo has joined #nixos-aarch64
exarkun has left #nixos-aarch64 ["WeeChat 2.4"]
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
alp has quit [Ping timeout: 272 seconds]
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
aleph- is now known as Church-
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
orivej has joined #nixos-aarch64
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
<Thra11>
I wonder if there's a significant difference between having a host with 4G of RAM and a vm which has 4G RAM and 4G swap, versus the host having 4G RAM and 4G of swap and the vm having 8G of RAM.
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
<samueldr>
wow, what a conundrum
<samueldr>
since one of the OS knows best about the topology it must also know best how to allocate ressources
vika_nezrimaya has joined #nixos-aarch64
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
<Thra11>
I figure the guest OS knowing what's swap _should_ be better. But if a page in the vm's memory maps to a page in the host's memory, it might not make much difference.
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
<samueldr>
I wonder if it even makes sense, to somehow have a qemu ram driver that makes the guest system cooperate with the host system
<samueldr>
(assuming both know how to)
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
cole-h has joined #nixos-aarch64
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
t184256 has left #nixos-aarch64 ["Error from remote client"]
t184256 has joined #nixos-aarch64
zupo has joined #nixos-aarch64
<Ke>
it's called ballooning or automated ballooning
dongcarl has quit [Read error: Connection reset by peer]
<Ke>
and there have been ways to communicate memory pressure there, but not very mainliney way
dongcarl has joined #nixos-aarch64
<Ke>
swap might also have the issue that it would get cached on the host side, unless you make it writethrough
rajivr has quit [Quit: Connection closed for inactivity]
noonien has joined #nixos-aarch64
dongcarl has quit [Read error: Connection reset by peer]
FRidh has quit [Quit: Konversation terminated!]
cole-h_ has joined #nixos-aarch64
dongcarl has joined #nixos-aarch64
cole-h has quit [Ping timeout: 256 seconds]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo has quit [Client Quit]
zupo has joined #nixos-aarch64
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
Darkmatter66_ has joined #nixos-aarch64
bennofs has joined #nixos-aarch64
Darkmatter66 has quit [Ping timeout: 260 seconds]
bennofs has quit [Client Quit]
bennofs has joined #nixos-aarch64
dongcarl has quit [Read error: Connection reset by peer]
ninjin_ has quit [Remote host closed the connection]
ninjin_ has joined #nixos-aarch64
<nature>
Hi, I am having some trouble building an image for my rpi4, I have the following logs after nix-build: https://paste.rs/st6
<samueldr>
>> semop(1): encountered an error: Function not implemented
<samueldr>
are you building this using qemu-user?
<samueldr>
(through binfmt)
<nature>
I added the boot.binfmt.emulatedSystems = [ "aarch64-linux" ]; option to my configuration.nix
<nature>
so yes I am building through binfmt
<samueldr>
yeah, that's not a supported way to build for aarch64, due to issues like that one
<nature>
ah crap
<nature>
What are my options then ?
<samueldr>
the most trivial option is to use the rpi4 sd image as built by hydra and build it on real aarch64 hardware
<samueldr>
though sometimes it's not helpful for some users that don't have serial / usb / hdmi
<nature>
Yes I don't have hdmi
<nature>
that's exactly why I wanted to build it directly from my computer
<bennofs[m]>
you can hack the image to enable headless ssh i believe. that's how I always installed my pi's
<nature>
oh ok
<samueldr>
no need to hack, if you have usb
<nature>
lik mount the image and modify the configuration.nix inside ?
<samueldr>
you can assume you're on the command line and `sudo systemctl start sshd`
<samueldr>
that won't work since the configuration.nix needs to be rebuilt :)
<nature>
Ok, so I am not sure I am following, with you usb method
<samueldr>
if you're unsure whether the image booted successfully (it may take a hot minute or five for its first boot) you can use `reboot` as a way to make the board obviously react to your input
<samueldr>
OH, that also could work
<samueldr>
but its configuration.nix will not be one that can be rebuilt
<samueldr>
so you'd probably need to replace it with the config you were writing
<samueldr>
but yeah, I think that would work too
<samueldr>
I would highly recommend you get a relatively inexpensive UART (ideally from a known reseller) unless you plan to never ever use any other SBC or have fun exploratory work in computing
<nature>
ok, so mounting the prebuilt sd image and replacing the configuration.nix in there with the configuration I was writting ?
<samueldr>
for your *next* problem it's going to be worth its weight in gold :)
<bennofs[m]>
I can second that. If you ever want to debug something
<samueldr>
nature: I guess that would work
<samueldr>
and blindly type `sudo nixos-rebuild switch`
<nature>
yes, I'll definitely look into getting one then
<nature>
ok, thank you guys :) I'll try this for now and let you know if it worked
<samueldr>
and when you're like me, hacking on too many projects, I recommend having at least one known-good UART, well-identified, and buying additional, even dirt cheap ones, and leave the dirt cheap ones with the unfinished projects :)
<samueldr>
oh, and `sudo passwd nixos` and a password twice
<samueldr>
you then should be able to ssh into it
<samueldr>
(might need to figure out a strategy to discover the board)
ninjin_ has quit [Remote host closed the connection]
<samueldr>
this assumes wired networking
ninjin_ has joined #nixos-aarch64
<nature>
samueldr: oh good idea for the blind input, I'll do that if the first trick doesn't work
<nature>
and yes I am definitely like you hacking on many projects ^^'
<samueldr>
the well-known seller, known-good UART is important to double and triple-check when things go wrong with the cheap-o ones :)
bennofs has joined #nixos-aarch64
bennofs has quit [Client Quit]
bennofs has joined #nixos-aarch64
<sphalerite>
samueldr: it's a fairly common problem with braveheart — the battery isn't glued in, but it might as well be given how easy it is to take out x) you have to loosen all the screws in the case and then careflly pry it out
bennofs has quit [Client Quit]
<sphalerite>
samueldr: I put a post-it on the battery to be able to pull it out more easily in the future after that experience.
<samueldr>
sphalerite: weird, mine's easy enough to remove
<sphalerite>
samueldr: yes the repairability/replacement part availability would be very nice indeed.
<samueldr>
though there was the shipping sticker that was hard to remove IIRC
<sphalerite>
samueldr: the missing config option was the one introduced by the patch, which is why I missed it (generating the config from unpatched kernel sources), the one that ignores kernel options passed by the android bootloader.
<sphalerite>
maybe it's not on all bravehearts
<sphalerite>
any ideas on the wcnss_wlan stuff?
<samueldr>
oof, you got me confused by jumping back and forth between devices :)
<sphalerite>
hehe sorry :D
<samueldr>
yeah, I assume it must be the later batches of bravehearts, or maybe it's the battery itself that's out of spec?
<sphalerite>
fwiw I left my pinephone at home when I left the country to visit my parents, so I can only play with the tissot for the rest of this week :)
<samueldr>
heh, anyways there's not much "to fix" on pinephone
<samueldr>
sphalerite: I don't see any errors... does it end up showing up?
* samueldr
boots a wcnss-able device
<sphalerite>
no, it ends up getting watchdogged and rebooting the whole system
<sphalerite>
about a minute after echo 1 > /dev/wcnss_wlan (and getting "no such device or address" iirc)
<samueldr>
:|
<samueldr>
and you have the right firmwares?
<samueldr>
I figure nothing's pushed :)
<sphalerite>
I think so (grabbed it from lineageos running on the tissot with the working screen), though maybe it's in the wrong path?
<samueldr>
can you push your WIP stuff?
<sphalerite>
hm, not sure. I'm not sure the firmware is redistributable :')
<samueldr>
don't commit the firmware files
<samueldr>
I want to see the expressions
alp has joined #nixos-aarch64
<samueldr>
for the firmware files I figure we're going to end up figuring out how to pick them from the muppets repos at some point
<sphalerite>
I'll need to move the firmware bit from my system config to the device module (yeah, I probably should have put it there right away…) but yeah will do
<samueldr>
yeah, z00t has an expression for that already that you should/could have used as a starting point
<samueldr>
I should probably do wcnss for addison to see if it works
<samueldr>
right, my first roadblock was that it meant I would have to install lineageOS I think
greizgh has quit [Remote host closed the connection]
vika_nezrimaya has joined #nixos-aarch64
greizgh has joined #nixos-aarch64
<samueldr>
16GB is probably not enough for Mobile NixOS to be used "as NixOS"...
<samueldr>
I should even say "16GB", so 11GB for userdata
<samueldr>
I can't upgrade the demo system on asus-z00t :)
<samueldr>
this really shows that an "out of device" scheme is needed
<samueldr>
though *that* would be less NixOS-like, by miles
alp has quit [Ping timeout: 272 seconds]
colemickens_irc has joined #nixos-aarch64
quinn has joined #nixos-aarch64
cole-h_ is now known as cole-h
<colemickens>
samueldr: I realize that there's little risk of you making the same purchase/mistake, but the red pixels appear to be VZW devices. However, it ALSO didn't have a functioning SIM card reader, so its going back. I really wouldn't have minded swapping devices for a while, oh well. Funny enough, the good folks at USPS got the passthrough boards to me -_-.
<samueldr>
hah
<samueldr>
oh, I thought "red pixel 3" meant a red tint on the display