c0ns0le c0ns0le

Setup Hyper-V enhanced session for Ubuntu 20

I couldn't find instructions that were 100% complete, so I put this together.

These instructions worked fine for me. Follow each step carefully.

Download Ubuntu 20 desktop

DO NOT create the VM by choosing Quick Create in Hyper-V Manager. Follow these instructions exactly.

Creality CR-6 issue list

This is an initiative to create an overview of the issues found with the Creality CR-6 SE.

As of this writing (2020-09-19) the large number of the motherboard issues have not been publicly acknowledged. Hopefully this overview forces Creality to acknowledge the issues with the Creality CR-6 SE leveling free 3d printer.

Update 2021-07-17 from Creality

According to Creality all issues should be resolved in the newer models:

Here are the improvements we did as below:

Error

$ sudo apt-get update
Err:1 http://archive.ubuntu.com/ubuntu focal InRelease
Temporary failure in name rerolution

$ host google.com
;; connection timed out; no servers could be reached

Display whether you have WSL1 or WSL2 by typing wsl --list --verbose into a PowerShell prompt, like this:
```
PS C:\Users\mslin> wsl --list --verbose
  NAME      STATE           VERSION
* Ubuntu    Running         1
```
The above shows that a machine has WSL1 installed.
Ignore this step if you have WSL2.

The default Ubuntu sleep command does not work on WSL1. sleep must work properly in order for the upgrade to succeed.

Install and configure WSL2 on windows 10

Install WSL2

Using the following link here install the WSL 2 on your windows 10.

Install X-Server

VcXsrv seems to the best choice for X-Server in Windows

Enable `systemd` in WSL 2

**NOTE: If you have Windows 11 there is now an official way to do this in WSL 2, use it if possible - see MS post here (WINDOWS 11 ONLY)**

This guide will enable systemd to run as normal under WSL 2. This will enable services like microk8s, docker and many more to just work during a WSL session. Note: this was tested on Windows 10 Build 2004, running Ubuntu 20.04 LTS in WSL 2.

To enable systemd under WSL we require a tool called systemd-genie
Copy the contents of install-sg.sh to a new file /tmp/install-sg.sh:

	# Change to name of TARGET-VM.
	$vm='CHANGE_ME'
	# Change to PCI device location (💡 Location).
	$Location = 'CHANGE_ME'

	# Enable CPU features.
	Set-VM -GuestControlledCacheTypes $true -VMName $vm
	# Host-Shutdown rule must be changed for the VM.
	Set-VM -Name $vm -AutomaticStopAction TurnOff

	#C:\Users\<yourUserName>\.wslconfig
	# https://blog.cloud-eng.nl/2021/02/03/wsl2-limits-vmmem/
	[wsl2]
	memory=6GB # How much memory to assign to the WSL 2 VM.
	processors=4 # How many processors to assign to the WSL 2 VM.
	swap=1GB # How much swap space to add to the WSL 2 VM, 0 for no swap file.
	localhostForwarding=true # ports bound to wildcard or localhost in the WSL 2 VM should be connectable from the host via localhost:port.

	[wsl2]
	kernel=<path> # An absolute Windows path to a custom Linux kernel.
	memory=<size> # How much memory to assign to the WSL2 VM.
	processors=<number> # How many processors to assign to the WSL2 VM.
	swap=<size> # How much swap space to add to the WSL2 VM. 0 for no swap file.
	swapFile=<path> # An absolute Windows path to the swap vhd.
	localhostForwarding=<bool> # Boolean specifying if ports bound to wildcard or localhost in the WSL2 VM should be connectable from the host via localhost:port (default true).

	# <path> entries must be absolute Windows paths with escaped backslashes, for example C:\\Users\\Ben\\kernel
	# <size> entries must be size followed by unit, for example 8GB or 512MB

	mkdir -pv /etc/sudoers.d/
	echo "$USER ALL=(ALL:ALL) NOPASSWD: ALL" \| sudo tee /etc/sudoers.d/dont-prompt-$USER-for-sudo-password
	mkdir -pv /usr/local/etc/sudoers.d/
	echo "$USER ALL=(ALL:ALL) NOPASSWD: ALL" \|sudo tee /usr/local/etc/sudoers.d/dont-prompt-$USER-for-sudo-password