Changes for page Ubuntu Linux

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -27,6 +27,7 @@
27	27	After the Windows installation has finished, we can boot back into Ubuntu using the Ubuntu 12.04 LTS Desktop CD. Again, we have to boot in UEFI mode.
28	28
29	29	We have to change to the target system by mounting all required partitions and chrooting to the target system. How to do this exactly depends on your system layout. In my case, I had the boot partition on /dev/sda4 and all other partitions in LVM. Therefore, I first installed the `lvm2` package, activated the volume group `vg0` with `vgchange -a y vg0` and mounted all required filesystems with the commands
	30	+
30	30	```bash
31	31	sudo mount /dev/vg0/root /mnt
32	32	sudo mount /dev/vg0/home /mnt/home
...	...	@@ -39,9 +39,11 @@
39	39	sudo mount -o bind /run /mnt/run
40	40	sudo mount -o bind /sys /mnt/sys
41	41	```
	43	+
42	42	In this example the system's ESP (this is the partition where the EFI boot-loaders are stored) has been created by the Windows setup as `/dev/sda1`.
43	43
44	44	Now we can change into the target system:
	47	+
45	45	```
46	46	sudo su -
47	47	chroot /mnt
...	...	@@ -56,9 +56,11 @@
56	56	After that you can install the EFI version of GRUB: `aptitude install grub-efi`.
57	57
58	58	In the target system, we have to edit `/etc/fstab` and add an entry for the ESP. You can find out the UUID of the partition by running `grub-probe --target=fs_uuid /boot/efi`. Then add a line like
	62	+
59	59	```
60	60	UUID=<UUID> /boot/efi vfat defaults 0 1
61	61	```
	66	+
62	62	to your /etc/fstab (of course you have to replace `<UUID>` by the UUID printed by `grub-probe`.
63	63
64	64	Now we install GRUB with `grub-install --boot-directory=/boot/efi/EFI --bootloader-id=grub --no-floppy --recheck` (I got this from [another guide](http://thinkpad-forum.de/threads/123262-EFI-Grub2-Multiboot-HowTo)).
...	...	@@ -68,6 +68,7 @@
68	68	Because memtest86+ was installed on the system, I had to copy the file `20_memtest86+` from the backup of the GRUB configuration files back to `/etc/grub.d`.
69	69
70	70	In order to be able to boot Windows 7 from GRUB (using the boot menu of the EFI BIOS is inconvenient), I added an extra entry to `/etc/grub.d/40_custom` (as describe in the [Ubuntu Community Wiki](https://help.ubuntu.com/community/UEFIBooting#Chainloading_Windows_x86_64_UEFI-GPT)):
	76	+
71	71	```
72	72	menuentry "Windows 7 (UEFI)" {
73	73	search -fs-uuid --no-floppy --set=root <UUID>
...	...	@@ -74,6 +74,7 @@
74	74	chainloader (${root})/EFI/Microsoft/Boot/bootmgfw.efi
75	75	}
76	76	```
	83	+
77	77	In this example `<UUID>` again has to be replaced by the UUID of the ESP.
78	78
79	79	In order to generate the GRUB configuration file, `update-grub` needs to be run.
...	...	@@ -105,3 +105,11 @@
105	105	```bash
106	106	aptitude search "?config-files"
107	107	```
	115	+
	116	+# Troubleshooting
	117	+
	118	+## Graphics server not starting after Upgrade to Ubuntu 22.04
	119	+
	120	+If the graphics server (X11 / Wayland) is not starting on a system with a NVIDIA graphics card (in particular an older one – in my case it was a GeForce 210), this might be caused by the switch from the proprietary NVIDIA driver to Nouveau, without some files of the proprietary NVIDIA driver having been removed correctly.
	121	+
	122	+Support for the old 340 version of the NVIDIA driver ended a while ago, so this version of the driver has been removed from Ubuntu 22.04. However, if this driver used to be install in Ubuntu 20.04 before the upgrade, it might still be installed after the upgrade and thus the configuration file `/etc/modprobe.d/nvidia-340_hybrid.conf` might still exist. This file will keep the open-source Nouveau driver from being loaded. This can typically be fixed by running `apt-get purge nvidia-340`.