!RjBlCIbsLDzHBIzmaA:nixos.org

NixOS on ARM

990 Members
NixOS on ARM: now with more ARM! — Support: AArch64; armv6 and armv7 are best effort, without any official cache. — Documentation: https://nixos.wiki/wiki/NixOS_on_ARM — Community build box: https://github.com/nix-community/aarch64-build-box → build box status: https://status.nixos.org/grafana/d/5LANB9pZk/per-instance-metrics?orgId=1&refresh=30s&var-instance=147.75.77.190 —244 Servers

Load older messages


SenderMessageTime
23 May 2021
@hoverbear:matrix.orghoverbear I need to make a pr for that to Linux Hackerman 's repo but I've been trying to find some optimal gcc flags which include ftree-vectorize etc 22:28:13
@hoverbear:matrix.orghoverbear* I need to make a pr for that to Linux Hackerman 's repo but I've been trying to find some optimal gcc flags which include ftree-vectorize etc... Currently waiting on Firefox to build.22:29:56
@artemist:artem.istartemist 🏳️‍⚧️Okay, spi flashed The main issue with my old uboot was that any keyboard or serial input took several seconds to register22:56:32
@samueldr:matrix.orgsamueldrright, yeah, fixed upstream22:56:51
@samueldr:matrix.orgsamueldrif you had tried UEFI and had a "console" UEFI program running like GRUB, it would also be extremely slow22:57:17
@samueldr:matrix.orgsamueldrthis is because U-Boot (still does) sync the display every chars written22:57:38
@artemist:artem.istartemist 🏳️‍⚧️I erased the spi flash from the serial console then booted off your installer sd card image22:58:01
@samueldr:matrix.orgsamueldrperfectly cromulent way to install22:58:21
@samueldr:matrix.orgsamueldralso a good validation check that the builds does boot on the target hardware22:58:36
@samueldr:matrix.orgsamueldr(though in practice there's enough difference in the SPI build that it could boot fine from SD but not on SPI)22:58:53
@artemist:artem.istartemist 🏳️‍⚧️Do EFI variables work in Tow-boot on the pinebook pro?23:10:29
@artemist:artem.istartemist 🏳️‍⚧️Or should I just rely on boota64.efi being in the right place?23:10:52
@samueldr:matrix.orgsamueldrhttps://nixos.wiki/wiki/NixOS_on_ARM/UEFI23:15:31
@samueldr:matrix.orgsamueldrfor the time being, boota64.efi23:15:36
@samueldr:matrix.orgsamueldrthough you might want to use rEFInd instead23:15:44
@samueldr:matrix.orgsamueldrsuch that rEFInd scans for EFI programs23:15:56
@samueldr:matrix.orgsamueldrdepending on what you prefer :)23:16:01
@artemist:artem.istartemist 🏳️‍⚧️Makes sense. TIL that you can use rEFInd on ARM23:16:08
@artemist:artem.istartemist 🏳️‍⚧️I last used it on an ancient macbook before I corebooted it23:16:22
@samueldr:matrix.orgsamueldr but yeah, since it's U-Boot with a coat of varnish, just like U-Boot there's no efivars support just yet 23:16:38
@samueldr:matrix.orgsamueldrI use rEFInd on my few computers where the UEFI implementation is bad23:16:56
@samueldr:matrix.orgsamueldrplop it at the fallback location, so when they decide to lose their efi vars, I'm not left with absolutely nothing to boot23:17:19
@artemist:artem.istartemist 🏳️‍⚧️Unfortunately on the computers I've had with a bad UEFI implementation if the boot order got changed too much the system was bricked. You couldn't even get into the firmware interface or the boot menu23:18:14
@artemist:artem.istartemist 🏳️‍⚧️Or boot the images you had configured23:18:41
@samueldr:matrix.orgsamueldrthose I have just decide to reset themselves :)23:18:45
@artemist:artem.istartemist 🏳️‍⚧️That's nice. This was a thinkpad and ended up returning it because of this issue23:19:03
@samueldr:matrix.orgsamueldrunderstandably :(23:19:25
@samueldr:matrix.orgsamueldrwhy aren't they all just using coreboot letting the user control that?23:19:39
@samueldr:matrix.orgsamueldrthey can leave the security bits to be blown by enterprise users!23:19:59
@samueldr:matrix.orgsamueldr(yeah, I know why, because they can use the "enterprisey" EFI implementors service level agreements and such nonsense)23:20:28

Show newer messages


Back to Room ListRoom Version: 6