Fix some missing code blocks inside lists

This commit is contained in:
parulin 2025-08-01 16:36:32 -04:00
parent 19cc43f286
commit 2e0d13592f
No known key found for this signature in database
GPG key ID: BC3830B42F4BF1F5
2 changed files with 44 additions and 34 deletions

View file

@ -99,9 +99,12 @@ Installation procedure:
- Install on first disk. - Install on first disk.
- Windows license may be read from flash via root in dom0: - Windows license may be read from flash via root in dom0::
``strings < /sys/firmware/acpi/tables/MSDM``
strings < /sys/firmware/acpi/tables/MSDM
Alternatively, you can also try a Windows 7 license key (as of 2018/11 they are still accepted for a free upgrade). Alternatively, you can also try a Windows 7 license key (as of 2018/11 they are still accepted for a free upgrade).
I first installed Windows and all updates, then entered the license key. I first installed Windows and all updates, then entered the license key.

View file

@ -2,11 +2,9 @@
UEFI troubleshooting UEFI troubleshooting
==================== ====================
Successfully installed in legacy mode, but had to change some xen parameters Successfully installed in legacy mode, but had to change some xen parameters
---------------------------------------------------------------------------- ----------------------------------------------------------------------------
**Note**: If you make changes, you must boot from “Partition 1” explicitly from UEFI boot menu. **Note**: If you make changes, you must boot from “Partition 1” explicitly from UEFI boot menu.
**Change the xen configuration on a USB media** **Change the xen configuration on a USB media**
@ -19,14 +17,10 @@ Successfully installed in legacy mode, but had to change some xen parameters
vi EFI/BOOT/grub.cfg vi EFI/BOOT/grub.cfg
3. Change the ``multiboot2 /images/pxeboot/xen.gz`` line to add your xen parameters on the boot entry of your choice 3. Change the ``multiboot2 /images/pxeboot/xen.gz`` line to add your xen parameters on the boot entry of your choice
4. Install using your modified boot entry 4. Install using your modified boot entry
**Change xen configuration directly in an iso image** **Change xen configuration directly in an iso image**
1. Set up a loop device (replacing ``X`` with your ISOs version name): ``losetup -P /dev/loop0 Qubes-RX-x86_64.iso`` 1. Set up a loop device (replacing ``X`` with your ISOs version name): ``losetup -P /dev/loop0 Qubes-RX-x86_64.iso``
@ -37,24 +31,19 @@ Successfully installed in legacy mode, but had to change some xen parameters
4. Save your changes, unmount and dd to usb device 4. Save your changes, unmount and dd to usb device
Installation freezes before displaying installer Installation freezes before displaying installer
------------------------------------------------ ------------------------------------------------
If you have an Nvidia card, see also `Nvidia Troubleshooting <https://forum.qubes-os.org/t/19021#disabling-nouveau>`__. If you have an Nvidia card, see also `Nvidia Troubleshooting <https://forum.qubes-os.org/t/19021#disabling-nouveau>`__.
Installation from USB stick hangs on black screen Installation from USB stick hangs on black screen
------------------------------------------------- -------------------------------------------------
Some laptops cannot read from an external boot device larger than 8GB. If you encounter a black screen when performing an installation from a USB stick, ensure you are using a USB drive less than 8GB, or a partition on that USB lesser than 8GB and of format FAT32. Some laptops cannot read from an external boot device larger than 8GB. If you encounter a black screen when performing an installation from a USB stick, ensure you are using a USB drive less than 8GB, or a partition on that USB lesser than 8GB and of format FAT32.
Installation completes successfully but then system crash/restarts on next boot Installation completes successfully but then system crash/restarts on next boot
------------------------------------------------------------------------------- -------------------------------------------------------------------------------
Some Dell systems and probably others have `another bug in UEFI firmware <https://web.archive.org/web/20170901231026/https://markmail.org/message/amw5336otwhdxi76>`__. These systems need ``efi=attr=uc`` enabled at all times. Although this is enabled by default in the installer, it is disabled after the first stage of a successful install. You can re-enable it either as part of the install process: Some Dell systems and probably others have `another bug in UEFI firmware <https://web.archive.org/web/20170901231026/https://markmail.org/message/amw5336otwhdxi76>`__. These systems need ``efi=attr=uc`` enabled at all times. Although this is enabled by default in the installer, it is disabled after the first stage of a successful install. You can re-enable it either as part of the install process:
1. Perform installation normally, but dont reboot the system at the end yet. 1. Perform installation normally, but dont reboot the system at the end yet.
@ -67,21 +56,36 @@ Some Dell systems and probably others have `another bug in UEFI firmware <https:
sed -i -e 's/ucode=scan/\0 efi=attr=uc/' /mnt/sysimage/boot/efi/EFI/qubes/grub.cfg sed -i -e 's/ucode=scan/\0 efi=attr=uc/' /mnt/sysimage/boot/efi/EFI/qubes/grub.cfg
4. Go back to ``tty6`` (Ctrl-Alt-F6) and click ``Reboot``. 4. Go back to ``tty6`` (Ctrl-Alt-F6) and click ``Reboot``.
5. Continue with setting up default templates and logging in to Qubes. 5. Continue with setting up default templates and logging in to Qubes.
Or if you have already rebooted after the first stage install and have encountered this issue, by: Or if you have already rebooted after the first stage install and have encountered this issue, by:
1. Boot Qubes OS install media into :ref:`rescue mode <user/troubleshooting/uefi-troubleshooting:accessing installer rescue mode on uefi>` 1. Boot Qubes OS install media into :ref:`rescue mode <user/troubleshooting/uefi-troubleshooting:accessing installer rescue mode on uefi>`
2. Press 3 to go to the shell 2. Press 3 to go to the shell
3. Find and mount the EFI system partition. (replace ``/dev/sda`` with your disk name. If unsure, use the ``lsblk`` command to display a list of disks): ``fdisk -l /dev/sda | grep EFI`` The output should look like this: ``/dev/sda1 2048 1230847 1228800 600M EFI System`` Then mount it: ``mkdir -p /mnt/sysimage/boot/efi mount /dev/sda1 /mnt/sysimage/boot/efi`` 3. Find and mount the EFI system partition. (replace ``/dev/sda`` with your disk
name. If unsure, use the ``lsblk`` command to display a list of disks):
.. code:: console
fdisk -l /dev/sda | grep EFI
The output should look like this:
.. code:: output
/dev/sda1 2048 1230847 1228800 600M EFI System
Then mount it:
.. code:: console
mkdir -p /mnt/sysimage/boot/efi mount /dev/sda1 /mnt/sysimage/boot/efi
4. Execute: 4. Execute:
@ -89,25 +93,38 @@ Or if you have already rebooted after the first stage install and have encounter
sed -i -e 's/ucode=scan/\0 efi=attr=uc/' /mnt/sysimage/boot/efi/EFI/qubes/grub.cfg sed -i -e 's/ucode=scan/\0 efi=attr=uc/' /mnt/sysimage/boot/efi/EFI/qubes/grub.cfg
5. Type ``reboot``. 5. Type ``reboot``.
6. Continue with setting up default templates and logging in to Qubes. 6. Continue with setting up default templates and logging in to Qubes.
Boot device not recognized after installing Boot device not recognized after installing
------------------------------------------- -------------------------------------------
Some firmware will not recognize the default Qubes EFI configuration. As such, it will have to be manually edited to be bootable. Some firmware will not recognize the default Qubes EFI configuration. As such, it will have to be manually edited to be bootable.
1. Boot Qubes OS install media into :ref:`rescue mode <user/troubleshooting/uefi-troubleshooting:accessing installer rescue mode on uefi>` 1. Boot Qubes OS install media into :ref:`rescue mode <user/troubleshooting/uefi-troubleshooting:accessing installer rescue mode on uefi>`
2. Press 3 to go to the shell 2. Press 3 to go to the shell
3. Find and mount the EFI system partition. (replace ``/dev/sda`` with your disk name. If unsure, use the ``lsblk`` command to display a list of disks): ``fdisk -l /dev/sda | grep EFI`` The output should look like this: ``/dev/sda1 2048 1230847 1228800 600M EFI System`` Then mount it: ``mkdir -p /mnt/sysimage/boot/efi mount /dev/sda1 /mnt/sysimage/boot/efi`` 3. Find and mount the EFI system partition. (replace ``/dev/sda`` with your disk name. If unsure, use the ``lsblk`` command to display a list of disks):
.. code:: console
fdisk -l /dev/sda | grep EFI
The output should look like this:
.. code:: output
/dev/sda1 2048 1230847 1228800 600M EFI System
Then mount it:
.. code:: console
mkdir -p /mnt/sysimage/boot/efi mount /dev/sda1 /mnt/sysimage/boot/efi
4. Copy ``grubx64.efi`` to the fallback path: 4. Copy ``grubx64.efi`` to the fallback path:
@ -115,16 +132,11 @@ Some firmware will not recognize the default Qubes EFI configuration. As such, i
cp /mnt/sysimage/boot/efi/EFI/qubes/grubx64.efi /mnt/sysimage/boot/efi/EFI/BOOT/bootx64.efi cp /mnt/sysimage/boot/efi/EFI/qubes/grubx64.efi /mnt/sysimage/boot/efi/EFI/BOOT/bootx64.efi
5. Type ``reboot`` 5. Type ``reboot``
"Qubes" boot option is missing after removing / attaching a disk or updating the BIOS "Qubes" boot option is missing after removing / attaching a disk or updating the BIOS
------------------------------------------------------------------------------------- -------------------------------------------------------------------------------------
1. Boot Qubes OS install media into :ref:`rescue mode <user/troubleshooting/uefi-troubleshooting:accessing installer rescue mode on uefi>` 1. Boot Qubes OS install media into :ref:`rescue mode <user/troubleshooting/uefi-troubleshooting:accessing installer rescue mode on uefi>`
2. Press 3 to go to the shell 2. Press 3 to go to the shell
@ -135,12 +147,7 @@ Some firmware will not recognize the default Qubes EFI configuration. As such, i
efibootmgr -v -c -u -L Qubes -l /EFI/qubes/grubx64.efi -d /dev/sda -p 1 efibootmgr -v -c -u -L Qubes -l /EFI/qubes/grubx64.efi -d /dev/sda -p 1
Accessing installer Rescue mode on UEFI Accessing installer Rescue mode on UEFI
--------------------------------------- ---------------------------------------
Choose “Rescue a Qubes OS system” from grub2 boot menu. Choose “Rescue a Qubes OS system” from grub2 boot menu.