| 10 Nov 2024 |
|  sbc64 left the room. | 20:02:04 |
| sbc64 joined the room. | 20:02:54 |
| 12 Nov 2024 |
|  Luke removed their profile picture. | 17:33:14 |
| Luke set a profile picture. | 17:33:55 |
| Luke removed their profile picture. | 17:34:45 |
| Luke set a profile picture. | 17:35:21 |
| 13 Nov 2024 |
|  Inayet joined the room. | 22:14:57 |
| 20 Nov 2024 |
| Inayet removed their profile picture. | 00:59:26 |
|  Kamilla 'ova joined the room. | 12:53:27 |
| 22 Nov 2024 |
|  Zach joined the room. | 16:59:30 |
|  Morgan (@numinit) joined the room. | 17:49:52 |
|  @tanvir:hackliberty.org joined the room. | 20:15:00 |
|  👉@crystallinefire:chat.solarpunk.moe changed their profile picture. | 20:26:39 |
| 24 Nov 2024 |
 matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | chuang: I got pretty far trying to get to mainline kernel with https://github.com/chuangzhu/nixos-sun20iw1p1, I've gotten everything working on the current nixos-unstable, and got systemd-boot/efi working, and an image generator with systemd-repart, but the kernel doesn't boot (probably a panic) | 15:15:56 |
| matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | I'm currently attempting to try your kernel, but is there any chance you know of what kernel config is supposed to boot, and which option causes the kernel panics? | 15:16:24 |
| matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | there is no stdout for me to observe the kernel panic so it's not obvious to me | 15:16:35 |
| 25 Nov 2024 |
|  @nullcube:matrix.org joined the room. | 09:57:46 |
| 26 Nov 2024 |
| matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | chuang: I got the d1 booting with 6.11 using a kernel from someone who's maintaining it on 6.11 with only 30~ patches away from mainline | 23:06:43 |
| matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | https://github.com/esmil/linux/commits/d1-6.11.y/ | 23:07:13 |
| matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | 
Download image.png | 23:07:36 |
| matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | we need to figure out what is causing those lockups on riscv in our common-config | 23:08:11 |
| matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | Also, we unnecessarily disable zboot/efi on riscv64 in nixpkgs for some reason, any ideas on why we do that? https://github.com/NixOS/nixpkgs/blob/master/pkgs/os-specific/linux/kernel/common-config.nix#L978-L981 | 23:09:14 |
| matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | Oh, and the image was made with systemd-repart, which was pretty cool! | 23:10:33 |
| matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | systemd-analyze
Startup finished in 5.176s (kernel) + 39.477s (initrd) + 1min 36.092s (userspace) = 2min 20.746s
multi-user.target reached after 1min 36.090s in userspace.
| 23:11:48 |
| matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | pretty slow, of course@ | 23:11:53 |
| matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | * pretty slow, of course | 23:11:59 |
| 27 Nov 2024 |
|  jopejoe1 (4094@39c3) changed their display name from jopejoe1 to jopejoe1 [4094]. | 18:18:07 |
| 28 Nov 2024 |
| Morgan (@numinit) | http://github.com/NixOS/nixpkgs/issues/354261
hmmm... never tackled these errors before. adding one of the deps to allowedReferences fixed it but 4 more popped up... | 20:49:02 |
| Morgan (@numinit) | I suspect the solution is something like "figure out which target files contain host build paths" right? | 20:49:38 |
| 30 Nov 2024 |
|  doomhammer joined the room. | 05:16:01 |
