| 18 Aug 2024 |
 Whovian9369 | Happen to have any ideas, or am I just stuck with this issue for the time being? | 20:46:26 |
 K900 | Can you check dmesg from the Ubuntu instance and see if there's any errors there? | 20:47:17 |
| Whovian9369 | Skimming to the end quickly, the output at the bottom exactly matches the one when run from nixpkgs | 20:48:28 |
| Whovian9369 | * Skimming to the end quickly, the output at the bottom exactly matches the one when run from Nix | 20:48:32 |
| Whovian9369 | And a couple quick "Page Up"s seems to show that they still match | 20:49:38 |
| K900 | Yes, it is the same kernel | 20:50:10 |
| K900 | But it should also have messages from NixOS activatoin | 20:50:18 |
| K900 | * But it should also have messages from NixOS activation | 20:50:20 |
| K900 | Actually, can you just try to wsl --shutdown and restart the VM first? | 20:50:29 |
| Whovian9369 | Just did that actually, and started both NixOS and Ubuntu | 20:50:42 |
| Whovian9369 | [ 2.041577] WSL (2) WARNING: hostname set to nixos-wsl in /etc/wsl.conf
[ 2.050661] WSL (2) WARNING: /usr/share/zoneinfo/America/New_York not found. Is the tzdata package installed?
[ 2.068520] systemd_shim[1]: /dev/shm is not a symlink, leaving as-is...
[ 2.069205] systemd_shim[1]: Remounting / shared...
[ 2.069637] systemd_shim[1]: Remounting /nix/store read-only...
[ 2.070372] systemd_shim[1]: Running activation script...
[ 2.172772] Can't ignore signal CHLD, forcing to default.
[ 2.314321] Can't ignore signal CHLD, forcing to default.
[ 2.410033] setting up /run/booted-system...
[ 2.411011] sh: line 1: grep: command not found
[ 2.411305] sh: line 1: systemctl: command not found
[ 2.413893] setting up /etc...
[ 2.588282] setting up /bin...
[ 2.595867] setting up /bin/login...
[ 2.599100] setting up /sbin/init shim...
[ 2.608438] systemd_shim[1]: Spawning real systemd...
[ 2.666790] Failed to connect to bus: No such file or directory
[ 2.922972] Failed to connect to bus: No such file or directory
Skimming dmesg made these jump out at me
| 20:51:48 |
| 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 |
