| 18 Aug 2024 |
 K900 | Yeah that seems normal | 20:52:04 |
| K900 | Though I wonder why the sh thing is back | 20:52:20 |
| K900 | And you are using latest nixos-wsl, correct? | 20:52:34 |
 Whovian9369 | I believe so yeah, I even updated nixos-wsl's flake input recently while I was updating the rest of my config | 20:53:27 |
| K900 | Oh wait no this is fine | 20:53:31 |
| K900 | Because you didn't have a /bin/sh presumably | 20:53:46 |
| K900 | So it just lost the race once | 20:53:59 |
| K900 | Which is fine probably | 20:54:02 |
| K900 | Check journalctl on the NixOS side, are there any errors | 20:54:20 |
| K900 | Check journalctl on the NixOS side, are there any errors? | 20:54:22 |
| Whovian9369 | [ 3.088622] misc dxg: dxgk: dxgkio_is_feature_enabled: Ioctl failed: -22
[ 3.094189] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
[ 3.095047] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
[ 3.095696] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
[ 3.096450] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
[ 3.180922] Failed to connect to bus: No such file or directory
[ 3.437537] Failed to connect to bus: No such file or directory
[ 3.694745] Failed to connect to bus: No such file or directory
[ 3.950524] Failed to connect to bus: No such file or directory
[ 3.993589] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
[ 4.122778] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
[ 4.123407] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
This is right after what I posted above -- Lots of Failed to connect to bus: No such file or directory or misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2 after that though
| 20:54:41 |
| K900 | Those are fine | 20:54:56 |
| K900 | That's just WSLg being weird | 20:55:08 |
| K900 | "Failed to connect to bus" is presumably because your user session is still not starting correctly | 20:55:24 |
| Whovian9369 | In reply to @k900:0upti.me
Check journalctl on the NixOS side, are there any errors? Aug 18 16:50:18 nixos-wsl kernel: FS-Cache: Duplicate cookie detected then its information
Aug 18 16:50:18 nixos-wsl unknown: /usr/lib/wsl/lib/libcuda.so.1 is not a symbolic link
Aug 18 16:50:18 nixos-wsl unknown: WSL (2) ERROR: WaitForBootProcess:3352: /sbin/init failed to start within 10000ms
Aug 18 16:50:18 nixos-wsl systemd-journald[79]: Received client request to flush runtime journal.
Aug 18 16:50:18 nixos-wsl systemd-journald[79]: File /var/log/journal/3f0405037402365e4122e654618a2843/system.journal corrupted or uncleanly shut down, renaming and replacing.
...
Aug 18 16:50:18 nixos-wsl systemd-sysctl[263]: Couldn't write '16' to 'kernel/sysrq', ignoring: No such file or directory
These are what stood out to me, and mostly repeat a few times
| 20:56:28 |
| K900 | Yeah that's fine | 20:56:41 |
| Whovian9369 | In reply to @k900:0upti.me
Check journalctl on the NixOS side, are there any errors? * Aug 18 16:50:18 nixos-wsl kernel: FS-Cache: Duplicate cookie detected then its information
Aug 18 16:50:18 nixos-wsl unknown: /usr/lib/wsl/lib/libcuda.so.1 is not a symbolic link
Aug 18 16:50:18 nixos-wsl unknown: WSL (2) ERROR: WaitForBootProcess:3352: /sbin/init failed to start within 10000ms
...
Aug 18 16:50:18 nixos-wsl systemd-journald[79]: Received client request to flush runtime journal.
Aug 18 16:50:18 nixos-wsl systemd-journald[79]: File /var/log/journal/3f0405037402365e4122e654618a2843/system.journal corrupted or uncleanly shut down, renaming and replacing.
...
Aug 18 16:50:18 nixos-wsl systemd-sysctl[263]: Couldn't write '16' to 'kernel/sysrq', ignoring: No such file or directory
These are what stood out to me, and mostly repeat a few times
| 20:56:41 |
| K900 | As in none of that is fatal | 20:56:51 |
| K900 | Though init not starting is weird | 20:56:55 |
| K900 | Is this NixOS 24.05 or unstable? | 20:57:02 |
| Whovian9369 | Should be Unstable | 20:57:10 |
| K900 | Oh | 20:57:19 |
| K900 | And did you update in between restarting the VMs? | 20:57:28 |
| Whovian9369 | You mean while we were experimenting? No, not to my knowledge | 20:57:50 |
| K900 | Do you have
[wsl2]
kernelCommandLine = cgroup_no_v1=all
in your .wslconfig? | 20:58:02 |
| Whovian9369 | I don't have anything in my C:\Users\Whovian\.wslconfig (Everything is commented out.) | 20:59:05 |
| K900 | Yeah, you need to set that | 20:59:33 |
| K900 | For systemd 256 to start correctly | 20:59:36 |
| K900 | Otherwise things get Funny | 20:59:40 |
| Whovian9369 | Ah damn it, thanks 😅
I'll try that in a moment | 20:59:49 |
