colemickens_irc has joined #nixos-aarch64
rajivr has joined #nixos-aarch64
h0m1 has quit [Ping timeout: 244 seconds]
h0m1 has joined #nixos-aarch64
Thra11_ has quit [Ping timeout: 240 seconds]
Thra11_ has joined #nixos-aarch64
<colemickens> clever: idk if you care btw, but I did boot the efi firmware over netboot the other night. next up will be booting something more fun from there (maybe burning an http url into the EFI payload in the nix module? might be neat)
<samueldr> https://retrage.github.io/2020/08/01/9pfspkg-en.html may be a fun thing to try too
<colemickens> was just reading that :)
* colemickens isn't quite sure there's a point if you're not really on board with 9p?
* colemickens is now reading about bitvisor
<colemickens> how does fs1: get created and linked to proxy-boot though?
<colemickens> "map -u" and then fs1: appears? (/me might not know enough about plan9 stuffs)
<samueldr> hmm, good question
<samueldr> set as UEFI variables
<samueldr> to my inexperienced eyes with network boot, what is interesting is there is no tftp contortion or HTTP server to deal with
<samueldr> it's basically already a filesystem
<samueldr> so at that point it works just like a filesystem
<samueldr> so you prepare that 9p share just like you would another ESP
<samueldr> and yeah, bitvisor looked interesting
<samueldr> and somewhat unknown I think considering what it promises
<colemickens> please correct me if I'm wrong, but if I squint it looks the same, but they hid the networking in 9p.
<samueldr> the same than?
<colemickens> functionally, at the end of the day, it's a netboot...
<samueldr> oh, sure
<colemickens> but over 9p instead of http
<samueldr> can a grub booted from http just use the files out of the http server?
<samueldr> (I am really inexperienced)
<colemickens> I don't know that's what I'm about to find out!
<samueldr> because that may be the big differentiator
<colemickens> Or, well, find out if rpi4 running some flavor of tianocore (I think) will boot something over a plain http server
<samueldr> it's really a filesystem as far as the UEFI firmware is concerned with 9p
<samueldr> so grub just does the usual filesystem things
<samueldr> and the uefi firmware transitively does it through 9p
<colemickens> Cool. Thank you. I understood that from reading but didn't appreciate it.
<samueldr> now, does netboot through other means do that too? maybe!
<colemickens> can linux keep doing file i/o through the efi interface?
<samueldr> I don't think it does :(
<samueldr> otherwise I can see shenanigans happening that could be nice
<colemickens> so uh, boot windows over 9p?
<samueldr> oh, I already assumed so
<samueldr> ;)
<samueldr> hmm
<samueldr> though I guess a full linux system running on 9p would be more trivial that way
<samueldr> or, more coherently booted?
<samueldr> at some point I really want to take some time and play with network boots
<colemickens> any particular angle on it?
<samueldr> nah, just knowing more
<samueldr> though every time I think about it I end up thinking that a thin or thick client is always better since it can deal with transient network failure
<angerman> theotherjimmy[m] so... and it turns out it *is* ttyAML0 m(
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 260 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
<ArtemVorotnikov[> samueldr: my Nokia 8 is unlocked already 🙂 , and I'm Russian myself so I do know of 4pda
<ArtemVorotnikov[> For one, there's this kernel: https://github.com/resident-nokia/umbrella
<samueldr> oh, lucky you
<samueldr> I had so much trouble to register, hoping it would reveal download links in a thread, where I still don't understand where to download :)
<samueldr> for other people: the captcha on 4pda.ru is cyrillic spelled-out numbers
<samueldr> so, from that point on you're in the less documented, more nebulous parts
<samueldr> while not identical, some of the steps are similar to the postmarketos ones https://wiki.postmarketos.org/wiki/Porting_to_a_new_device#Kernel_package
<samueldr> mainly the kernel configuration
<samueldr> what I often end up doing is extracting the kernel config from a running kernel's /proc/config.gz on the device
orivej has quit [Remote host closed the connection]
<samueldr> (or using binwalk on the extracted kernel, which often ends up giving a kernel config file)
orivej has joined #nixos-aarch64
orivej has quit [Remote host closed the connection]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-aarch64
orivej_ has joined #nixos-aarch64
orivej has quit [Ping timeout: 240 seconds]
orivej_ has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 256 seconds]
Thra11_ has quit [Ping timeout: 264 seconds]
Thra11_ has joined #nixos-aarch64
<sphalerite> samueldr: "ntfs2btrfs" wow x)
<Ke> samueldr we run nixos with 9p sharing store from host
<Ke> a limited system only though, but probably full system would work
Thra11_ has quit [Ping timeout: 256 seconds]
FRidh has joined #nixos-aarch64
Thra11_ has joined #nixos-aarch64
<clever> colemickens: nice
<kahiru> is nixos-generate-config able to deal with 9p mounts?
<clever> kahiru: i'm guessing it just pulls 3 fields from /proc/mounts (device, type, mountpoint) and spits it out in nix
<kahiru> could be
<clever> and for most filesystems, you dont need anything that complex, just find the uuid
Thra11_ has quit [Ping timeout: 240 seconds]
<kahiru> Ke: what do you use as 9p server?
alp has joined #nixos-aarch64
zupo has joined #nixos-aarch64
tilpner has joined #nixos-aarch64
orivej has joined #nixos-aarch64
Thra11_ has joined #nixos-aarch64
Thra11_ has quit [Ping timeout: 240 seconds]
Thra11_ has joined #nixos-aarch64
orivej has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-aarch64
Thra11_ has quit [Ping timeout: 240 seconds]
Thra11_ has joined #nixos-aarch64
orivej has quit [Ping timeout: 260 seconds]
alp has quit [Ping timeout: 246 seconds]
Thra11_ has quit [Ping timeout: 240 seconds]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
Thra11_ has joined #nixos-aarch64
FRidh has quit [Ping timeout: 240 seconds]
FRidh has joined #nixos-aarch64
orivej has joined #nixos-aarch64
Thra11_ has quit [Ping timeout: 260 seconds]
orivej has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
orivej has quit [Ping timeout: 240 seconds]
Thra11_ has joined #nixos-aarch64
alp has joined #nixos-aarch64
zupo has joined #nixos-aarch64
quinn has quit [Quit: ZNC 1.8.1 - https://znc.in]
Thra11_ has quit [Ping timeout: 256 seconds]
alp has quit [Ping timeout: 256 seconds]
alp has joined #nixos-aarch64
Darkmatter66_ has joined #nixos-aarch64
Darkmatter66 has quit [Ping timeout: 240 seconds]
zupo has quit [Remote host closed the connection]
zupo has joined #nixos-aarch64
alp has quit [Ping timeout: 264 seconds]
alp has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
samrose has joined #nixos-aarch64
Acou_Bass has quit [Ping timeout: 244 seconds]
alp has quit [Remote host closed the connection]
Acou_Bass has joined #nixos-aarch64
flip[m] has joined #nixos-aarch64
<flip[m]> Hello, does anybody use nixos on Raspberry Pi 4 8GB? I have an issue where the board gets stuck in a reboot loop, but where it eventually manages to boot. I'm new to Nixos so maybe I've screwed something up, but I don't think so... Any help troubleshooting this is greatly appreciated.
<clever> flip[m]: what power supply are you using?
<flip[m]> clever: not an official raspberry pi 4 USB C, but it was 3+ Ampere iirc. Can't actually check the rating without unplugging...
<flip[m]> I built NixOS from some fork with support for RasPi 4 8GB, i'm wondering if that could be the issue?
<flip[m]> last printed message on the console is "Finished Address configuration of wlan0" and "Starting Networing Setup..." and then it just reboots
<clever> flip[m]: ive heard that the 8gig ram needs more power, and i can see how the PSU may not be able to keep up
<clever> flip[m]: is the red led blinking any?
<flip[m]> during boot? It's stable now that it's running/idling
<clever> yeah, when its looping
<flip[m]> let me reboot and check
<flip[m]> no, the green activity LED is blinking, but the Red LED does not
<flip[m]> except for maybe a split second as the system resets
<clever> sounds normal
<clever> i would try turning on the serial logs, and watch those
<flip[m]> I followed this guide to build the install image: https://gist.github.com/chrisanthropic/2e6d3645f20da8fd4c1f122113f89c06
<flip[m]> So i think i'm using the unstable tree, if that could be causing issues
<flip[m]> Don't think i have any way to get UART attached unfortunately
<flip[m]> The instructions seems to have been updated to use stable nixos since i built? I'll try rebuilding the installer image and see if it changes things
<flip[m]> unless there's a prebuilt installer image I can use?
* clever looks
<clever> 2020-01-22 13:53:12< clever> Tenkawa: `nix-build '<nixpkgs/nixos/release.nix>' -A sd_image_raspberrypi4.aarch64-linux` for an rpi4 i believe
<clever> thats what ive got in my logs, for creating a pi4 image
<flip[m]> not sure if those will work on Pi 4 8GB though
<clever> try it and see what happens?
<flip[m]> yeah will do
orivej has joined #nixos-aarch64
<flip[m]> heh, it's still stuck in the boot loop since the reboot more than an hour ago
<clever> definitely sounds like something is wrong
<flip[m]> looks like the prebuilt arm64 images don't work either, complains about start4.elf compat
<clever> you can try copying the new start4.elf and fixup4.dat onto the fat32 fs
<clever> to upgrade it
<flip[m]> yeah trying it
<clever> i have seen that check in the decompiler binary, and was wondering what it was
<clever> sounds like start4.elf needs 8gig support, and the eeprom firmware is specially checking for it
<clever> so it wont even try to boot something that fails
<flip[m]> got stuck on the colorful screen now
<flip[m]> I'll just try rebuilding the installer image with the updated guide...
orivej has quit [Remote host closed the connection]
orivej has joined #nixos-aarch64
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
orivej has quit [Remote host closed the connection]
orivej has joined #nixos-aarch64
orivej has quit [Remote host closed the connection]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 246 seconds]
lordcirth_ has quit [Ping timeout: 260 seconds]
FRidh has quit [Ping timeout: 256 seconds]
FRidh has joined #nixos-aarch64
cole-h has joined #nixos-aarch64
lordcirth has joined #nixos-aarch64
lordcirth_ has joined #nixos-aarch64
lordcirth has quit [Ping timeout: 264 seconds]
alp has joined #nixos-aarch64
lordcirth_ has quit [Quit: Leaving]
* colemickens is considering unlocking his day-to-day phone to keep tinkering.
* colemickens is really accustomed to NFC payment now though
<samueldr> I'm a bit sad that host card emulation didn't catch on
<samueldr> AFAIUI HCE would allow the end-user to control this, and it's just acting as the card
<samueldr> *and*, at the time of its introduction with Android 4.4, wouldn't have required the payment terminal to care about it not being a card
<WRMilling> I am guessing then current implementations require the terminal to knwow its an NFC capable phone?
<samueldr> maybe not that it's an NFC capable phone, but using another protocol than the credit card, as I understand it
<samueldr> (I could be wrong about that bit, but otherwise it makes no sense how paypass/paywave was possible but google pay not on the same terminal in its early days here)
<samueldr> hard information on the topic is not trivial to gather :/
alp has quit [Ping timeout: 264 seconds]
alp has joined #nixos-aarch64
FRidh has quit [Quit: Konversation terminated!]
Darkmatter66_ has quit [Ping timeout: 264 seconds]
alp has quit [Ping timeout: 240 seconds]
alp has joined #nixos-aarch64
Darkmatter66 has joined #nixos-aarch64
alp has quit [Client Quit]
zupo has joined #nixos-aarch64
rajivr has quit [Quit: Connection closed for inactivity]
zupo_ has joined #nixos-aarch64
zupo has quit [Ping timeout: 256 seconds]
Mic92 has joined #nixos-aarch64
Thra11 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…]