| 1 Jun 2026 |
 lorne | For my G5 I've been assembling a symlink tree of: grub image, kernel, vmlinux, squashfs, and just scp-ing it directly to an Apple Partition Map / HFS+ volume on a usb stick and booting over usb with the regular probe-usb boot usb3/disk:3,\grub\grub.img. I was going to try that again once everything builds (libressl is sad). | 15:04:37 |
| lorne | * For my G5 I've been assembling a symlink tree of: grub image, kernel, initrd, squashfs, and just scp-ing it directly to an Apple Partition Map / HFS+ volume on a usb stick and booting over usb with the regular probe-usb boot usb3/disk:3,\grub\grub.img. I was going to try that again once everything builds (libressl is sad). | 15:29:29 |
 Puna | https://github.com/NixOS/nixpkgs/pull/486572 and https://github.com/NixOS/nixpkgs/pull/488831 should allow you to build an ISO via nixos module stuff, write it to a USB / burn to a disc, and either boot it from the mac's multiboot menu thingy or via the tbxi entry point in openfirmware | 15:56:41 |
| Puna | https://github.com/OPNA2608/nixpkgs/tree/wip/ppc64-installer is a nixpkgs tree where i collect all such fixes/additions that i have submitted, and rebase them on nixos-unstable every once in awhile (after checking that everything still builds and boots). the newworldmac-nixos-installer.nix file in the repo root can be used as the config for the iso. example command (run on the hardware itself):
puna@Yubel ~/D/nixpkgs (wip/ppc64-installer-testing)> env \
"NIX_PATH=nixpkgs=$PWD:nixos-config=$PWD/newworldmac-nixos-installer.nix" \
nom-build \
--option allow-import-from-derivation false \
--no-out-link \
--max-jobs 1 --cores 2 \
./nixos -A config.system.build.images.iso
YMMV when doing cross
| 16:01:39 |
| Puna | (this mac stuff has come up in #exotic:nixos.org every once in awhile, if you'd like to take a look) | 16:04:17 |
| 2 Jun 2026 |
|  kiffeuse4life67 changed their display name from missbehaves to kiffeuse4life67. | 07:45:26 |
| lorne | I have grub and the kernel and initrd loading from a usb stick, but no usb so it's not booting and not responding to the keyboard. I guess I'm missing the usb driver. | 14:20:25 |
| 3 Jun 2026 |
| lorne | upon closer inspection, udevd and journald are segfaulting | 11:17:12 |
| lorne | turning off systemd in init was enough to boot to all the way to a shell, but I'm no further ahead. keyboard input produces squares, and networking isn't up so I can't ssh in either. | 16:26:30 |
|  Charles left the room. | 20:04:00 |
| 4 Jun 2026 |
|  Echo changed their profile picture. | 04:23:45 |
|  guillaume changed their display name from Guillaume to flashonfire. | 16:40:47 |
| 5 Jun 2026 |
| guillaume changed their display name from flashonfire to guillaume. | 12:07:11 |
| kiffeuse4life67 changed their profile picture. | 14:17:36 |
|  9lore changed their display name from 9lore to 9lore | call LORE. | 14:35:05 |
|  zimward changed their display name from zimward to zimward @GPN24. | 19:37:40 |
| 7 Jun 2026 |
|  @fgrsnau:matrix.org left the room. | 13:42:38 |
|  richarddodd joined the room. | 14:19:10 |
| richarddodd | Hey - I'm trying to do some cross x64 -> aarch64 and am finding some packages aren't building (RN it's tree-sitter). Is there a guide somewhere for how to go about debugging packages in the nixpkgs repo? | 14:20:24 |
 K900 | There's really no simple answer here | 14:20:51 |
| K900 | Very few upstreams actually test cross compilation | 14:20:59 |
| K900 | So the process is usually "look at the build error really hard and try to figure out what's going wrong" | 14:21:17 |
| richarddodd | I'm happy to debug the build - I just need to figure out how to go from nixpkgs to a shell.nix or similar. | 14:21:35 |
| richarddodd | * I'm happy to debug the build - I just need to figure out how to go from nixpkgs/../package.nix to a shell.nix or similar. | 14:21:51 |
| richarddodd | In my case the error is unknown type name '__SVFloat32_t', so I suspect fixing it will involve providing some SVE symbols or perhaps turning SVE usage off when cross-compiling | 14:24:29 |
| K900 | nix-shell -A <foo> | 14:25:00 |
| K900 | Or rather, in your specific case, probably nix-shell -A pkgsCross.aarch64-multiplatform.foo | 14:25:14 |
| richarddodd | Would that use my own local copy of nixpkgs, so I can start debug/run cycling? | 14:26:21 |
| richarddodd | oh - I think I understand - I go to the root of nixpkgs and then run that to use a particular attribute rather than the root attribute? | 14:28:20 |
| K900 | Yes | 14:28:50 |
