| 20 Sep 2025 |
 @lotte:chir.rs | ah | 15:32:20 |
| @lotte:chir.rs | so the downstream kernel might be better? | 15:32:28 |
| @lotte:chir.rs | it’s not yet EOL :D barely | 15:34:13 |
 K900 | Better in some ways, likely significantly worse in others | 15:34:15 |
| @lotte:chir.rs | 5.4 lts | 15:34:16 |
| @lotte:chir.rs | yeah i tried running it on my older phone but there the kernel is so old most of the software doesn’t even run on it | 15:38:29 |
| @lotte:chir.rs | ah yeah display is specifically marked as borken eyah | 15:46:23 |
| @lotte:chir.rs | * | 15:46:36 |
| 23 Sep 2025 |
|  kenji changed their display name from a-kenji to kenji. | 10:43:39 |
| 30 Sep 2025 |
| @lotte:chir.rs changed their profile picture. | 10:58:29 |
|  17lifers (at mikuplushfarm) joined the room. | 16:05:09 |
| 17lifers (at mikuplushfarm) | 16:05:52 |
| 17lifers (at mikuplushfarm) | 16:05:52 |
|  NixOS Moderation Bot banned  joepie91 🏳️🌈 (divsive behavior). | 19:23:50 |
| 1 Oct 2025 |
|  Theodora The Absurdist Schizotisticoball joined the room. | 13:48:43 |
| 17lifers (at mikuplushfarm) left the room. | 18:06:01 |
| 2 Oct 2025 |
 Puna | r-burns: hi! i'm currently checking if i can get nixosTests running on my POWER machine. i see that you added the qemu entries for these back in https://github.com/NixOS/nixpkgs/pull/115175 , and you mentioned there that there'd be more changes down the line. did this change work for you, and did those other changes ever materialise into PRs? | 17:35:55 |
| Puna | as-is, qemu seems unable to launch a regular kernel with the powernv platform selected. i only managed to get something resembling a booting system out of that platform by passing petitboot files into -kernel and -initrd. since we also use those options to start VMs for tests though, that doesn't really work… | 17:38:33 |
| Puna | the pseries platform can definitely use -kernel and -initrd to boot a system, but on a big-endian POWER system any kernel I try just runs into invalid memory access almost immediately. so that also doesn't really work, at least not for natively running the tests | 17:40:06 |
| Puna | * the pseries platform can definitely use -kernel and -initrd to boot a regular linux kernel, but on a big-endian POWER system any kernel I try just runs into invalid memory access almost immediately. so that also doesn't really work, at least not for natively running the tests | 17:40:15 |
| Puna | * as-is, qemu seems unable to launch a regular kernel with the powernv platform selected. i only managed to get something resembling a booting system out of that platform by passing petitboot files into -kernel and -initrd, and adding a CD device with an installer ISO. since we also use those two options to start VMs for tests though, that doesn't really work - at least not without introducing some nix code to make a petitboot-recognised disk image to pass as a disc… | 17:42:22 |
| Puna | * as-is, qemu seems unable to launch a regular kernel with the powernv platform selected. i only managed to get something resembling a booting system out of that platform by passing petitboot files into -kernel and -initrd, and adding a CD device with an installer ISO. since we also use those two options to start VMs for tests though, that doesn't really work - at least not without introducing some nix code to make a petitboot-recognised dis(c/k) image to pass via a device… | 17:42:56 |
| Puna | just curious if you have any more insight into / ideas about that, was hoping to do installer tests for IEEE-1275 grub2 before committing to writing anything onto a real disk :) | 17:45:48 |
| Puna | * the pseries platform can definitely use -kernel and -initrd to boot a regular linux kernel, but on a big-endian POWER system any kernel I try to boot inside of the VM just runs into invalid memory access almost immediately. so that also doesn't really work, at least not for natively running the tests | 17:47:47 |
| Puna | * the pseries platform can definitely use -kernel and -initrd to boot a regular linux kernel, but on a big-endian POWER system any kernel I try to boot inside of the VM just runs into invalid memory access almost immediately. so that also doesn't really work, at least not for natively running the tests on the platform that I have access to | 17:48:07 |
 lzcunt | Heyy, it looks like bash introduced a sanity check for strchrnul that fails when cross compiling (just like getenv) and bash tries to replace the implementation | 20:16:54 |
| lzcunt | but for static builds with mlibc it fails because mlibc doesn't have them as weak symbols (which is similar behaviour to BSDs) | 20:17:53 |
| lzcunt | someone working with cross compilation to BSDs should check if they're affected | 20:18:23 |
| lzcunt | if they're affected, bash_cv_func_strchrnul_works=yes when cross compiling to BSDs just like we currently do for getenv_works should be enough to fix it | 20:19:51 |
 Alyssa Ross | In reply to @sananatheskenana:matrix.org
someone working with cross compilation to BSDs should check if they're affected BSD cross works well enough that it should be quite easy to check yourself if you're interested (and want to also fix it for mlibc) | 20:22:44 |
