Skip to content

Code cleanup/adjustments for display fidelity. #13

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
AdrianTM merged 2 commits into from
Oct 19, 2026
Merged

Code cleanup/adjustments for display fidelity. #13

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5179675
Typo fixes, spell fix and many style adjustments.
FullScale4Me Oct 18, 2026
aa5b1a9
Formatting adjustments for MX-Viewer and Firefox.
FullScale4Me Oct 19, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 12 additions & 2 deletions help/custom.css
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,9 @@
body {
font-family: sans-serif;
line-height: 1.5;
margin: 2rem auto;
padding: 0 1.25rem 2rem;
color: #202124;
}

h1,
Expand All @@ -17,14 +21,20 @@ code {
padding: 0.1rem 0.3rem;
}

div {
pading: 5em;
img {
display: block;
margin: auto;
padding: 15px 0; /* Adds space between each */
}

p {
margin: .2em;
}

. center {
text-align:center;
}

.footer {
border-top: 1px solid #d0d7de;
color: #5f6368;
Expand Down
72 changes: 41 additions & 31 deletions help/mx-boot-repair.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,33 +2,32 @@
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>HELP: MX Boot Repair</title>
<link href="custom.css" rel="stylesheet" type="text/css">
</head>
<body>

<h1 align="center">HELP: MX Boot Repair</h1>
<h1 style="text-align:center;">HELP: MX Boot Repair</h1>

<p align="center">MX Boot Repair is a GUI app that can be used to recover from boot failure.</p>
<p style="text-align:center;">MX Boot Repair is a GUI app that can be used to recover from boot failure.</p>

<h3><strong>Some definitions:</strong></h3>
<h2><strong>Some definitions:</strong></h2>

<ul>
<li><strong>MBR</strong>: Installation in the hard drive’s Master Boot Record.<br></li>
<li><strong>PBR</strong>: Installation in the partition’s boot sector (partition level).<br></li>
<li><strong>ESP</strong>: Installation on the EFI system partition (UEFI only).<br></li>
<li><strong>MBR</strong>: Installation in the hard drive’s Master Boot Record.</li>
<li><strong>PBR</strong>: Installation in the partition’s boot sector (partition level).</li>
<li><strong>ESP</strong>: Installation on the EFI system partition (UEFI only).</li>
</ul>

<p>This app’s selection for “Install on” (see below) in the “Reinstall GRUB bootloader on ESP, MBR or PBR (root)” is not to be assumed as automatically correct at all times.</p>

<p>At times, with a very complex PC configuration there may need to be change(s) made to better match the PC under repair.</p>
<p>This application’s selection for “Install on” (see below) in the “Reinstall GRUB bootloader on ESP, MBR or PBR (root)” is not to be assumed as automatically correct at all times. With a very complex PC configuration there may need to be change(s) made to better match the PC under repair.</p>

<div align="center"><img src="Select-boot-method-ESP.png" width="582" height="190" alt="Select-boot-method-ESP.png"></div>
<img src="Select-boot-method-ESP.png" width="582" height="190" alt="Select boot method ESP">

<p>The best starting point is to live-boot from a recent USB, and select “Repair GRUB configuration file”.</p>


<h3><b>NOTES</b></h3>
<h3>NOTES</h3>

<p>Repair Grub configuration file is the most common use of this app. It should always be attempted <span style="text-decoration: underline;">first</span>. Running just the “Repair GRUB configuration file” assumes that Grub is fully and properly installed in the expected location. Sometimes running a “Reinstall Grub bootloader” is needed to be done <span style="text-decoration: underline;">first</span>, before Repair Grub configuration file.</p>

Expand All @@ -37,9 +36,9 @@ <h3><b>NOTES</b></h3>

<h3>Booting the PC</h3>

<p>Example at below of a One Time Boot Menu. Choose the option ▸UEFI Boot Sources or Legacy Boot Sources depending on how Linux was installed. If you know that the PC’s Linux installation was in Legacy mode then pick “Legacy Boot Sources”. Other PCs screens<i> may</i> vary.</p>
<p>Example at below of a One Time Boot Menu. Choose the option ▸UEFI Boot Sources or Legacy Boot Sources depending on how Linux was installed. If you know that the PC’s Linux installation was in Legacy mode then pick “Legacy Boot Sources”. Other PCs screens<em> may</em> vary.</p>

<div align="center"><img src="BootRepair02.jpg" width="321" height="212" alt="BootRepair02.jpg"></div>
<img src="BootRepair02.jpg" width="384" height="254" alt="BootRepair02">


<h3>Dual Boot with Windows 10 and Windows 11</h3>
Expand All @@ -51,6 +50,8 @@ <h4>Partition labels</h4>

<p>It is always good to have your partitions labeled. This allows better recognition for where the ESP (EFI System Partition) is located. Some Linux distro’s install do not label the ESP nor the /root.</p>

<br>

<p><b>TIP:</b> you can open GParted and right click on partitions in order to give them labels e,g like “EFI-SYSTEM” or just “ESP” (without ” “). Labeling partitions is best done from a Live USB, as these partitions needs to be unmounted for GParted to set a label on the partition(s).</p>


Expand All @@ -63,9 +64,10 @@ <h4>Windows partitions</h4>

<p>Below is a view of a Windows hard disk layout prior to any partitions being labeled.</p>

<div align="center"><img src="Before-Choose-Partitions.jpg" width="457" height="203" alt="Before-Choose-Partitions.jpg"><br>Typical GParted view of a Windows 11 hard disk layout.</div>
<img src="Before-Choose-Partitions.jpg" width="457" height="203" alt="Before Choose Partitions">
<div style="text-align:center;"><caption>Typical GParted view of a Windows 11 hard disk layout.</caption></div>

<p><strong>Partitions above explained</strong>:</p>
<h4><strong>Partitions above explained</strong>:</h4>

<p><strong>sda1</strong> – EFI aka ESP. Can be FAT32 or Vfat. Size ranges from 25-300 MiB. MX default is 256 MiB.</p>
<p><strong>sda2</strong> – “Windows Resources” Normally hidden in Windows File Manager. No format is normal.</p>
Expand All @@ -78,9 +80,9 @@ <h4 style="margin-top: 1.5em;">After running boot repair</h4>

<p>It is preferred to power OFF the PC, and then power on the PC back ON. This is because with a normal reboot will not clear all EFI stuff from RAM. Sometimes the MX Installer misses generating entries for other previously installed OS’s, so run in terminal:</p>

<div align="center" style="clear: both"><code>sudo update-grub</code></div>
<div style="text-align:center; clear: both"><code>sudo update-grub</code></div>

<p>This is a good check, to see anything was missed.</p>
<p>This is a good check, to see if anything was missed.</p>

<br><hr>

Expand All @@ -97,36 +99,44 @@ <h2>Repair GRUB configuration file</h2>
<p>2. Select: ◉ Repair GRUB configuration file. Click ‘→ Next’.</p>
<p> 3. On the ‘Select GRUB location‘ screen in ‘Select root location:’ choose the MX Linux / root partition.</p>

<div align="center"><img src="Select-Grub-Location01.png" width="580" height="129" alt="Select-Grub-Location01.png"></div>
<img src="Select-Grub-Location01.png" width="580" height="129" alt="Select-Grub-Location01">

<p>4. Click ‘✔Apply’.</p>
<p>5. In the ‘Authenticate‘ pop-up enter ‘demo’ for the ‘Password:’ prompt and click ‘Authenticate’.</p>
<p>6. A pop-up appears: ‘The GRUB configuration file (grub.cfg) is being rebuilt’.</p>
<p>7. When ‘Success‘ popup asks: ‘Do you want to exit MX Boot Repair?’ click ‘✔Yes’.</p>

<div style="clear:both; line-height: 0.5;">
<div style="text-align:center; clear:both; line-height: 0.5;"></div>

<br><hr>


<h2>UEFI PC boot repair</h2>


<p><b>You MUST be booted in UEFI mode to repair a UEFI installation with this app</b>.</p>

<h3 style="margin-top: 2em;">To reinstall GRUB bootloader:</h3>

<h3>To reinstall GRUB bootloader:</h3>

<p><b>Note</b>: in the image below “EFI-SYSTEM” and “MX25Xfce” are partition labels are displayed as hints for your choices.</p>

<div align="center"><img src="Select-boot-method-ESP.png" width="582" height="190" alt="Select-boot-method-ESP.png"></div>
<br>
<div style="text-align:center;"><img src="Select-boot-method-ESP.png" width="582" height="190" alt="Select-boot-method-ESP.png"></div>
<br>

<p>1. Boot MX Linux USB in UEFI mode. Run MX Boot Repair.</p>
<p> 2. Select: ‘◉ Reinstall GRUB bootloader on ESP, MBR or PBR (root)’. Click ‘→ Next’.</p>

<p> 2. Select: ‘<span style="font-family: OpenSymbol, Serif;">◉</span> Reinstall GRUB bootloader on ESP, MBR or PBR (root)’. Click ‘→ Next’.</p>

<p> 3. On the Select Boot Method:</p>

<ul>
<li>For ‘Install on:‘ choose ‘◉ ESP’.</li>
<li>For ‘Install on:‘ choose ‘<span style="font-family: OpenSymbol, Serif;">◉</span> ESP’.</li>
<li>Set ‘Location:’ to the ESP aka EFI partition.</li>
<li>Set ‘Select root location:’ to the partition where MX Linux is installed.</li>
</ul>
<p>4. Click ‘✔Apply’.</p>
<p>4. Click ‘<span style="font-family: OpenSymbol, Serif;">✔</span>Apply’.</p>
<p>5. In the Authenticate pop-up enter ‘demo’ for the ‘Password:’ prompt and click ‘Authenticate’.</p>
<p>6. A pop-up ‘Select /boot location:’ asks you to choose: If no encryption is in use, choose the ESP / EFI and then click ‘✔OK’.</p>
<p>7. Select the ESP aka EFI partition (if encryption is not in use) with the arrow and then click ‘✔OK’.</p>
Expand All @@ -138,15 +148,15 @@ <h3 style="margin-top: 2em;">To reinstall GRUB bootloader:</h3>
<h2>Legacy/MBR PC repairs</h2>

<p><b>You MUST be booted in Legacy/MBR mode to repair a Legacy installation with this app.</b></p>

<p>Repairing the bootloader by regenerating the GRUB configuration file is the most common use of this application and should be attempted <u>first</u>.</p>
<br>
<p>Repairing the bootloader by regenerating the GRUB configuration file is the most common use of this application and should be attempted <strong>first</strong>.</p>


<h3 style="margin-top: 2em;">Reinstall GRUB bootloader:</h3>

<p><b>Note</b>: in the image below “Lexar 126GB SSD” is the physical “sda” device and “MX25Xfce” is a partition label. The app displays these as hints for your choices.</p>

<div align="center"><img src="Select-boot-method-MBR.png" width="582" height="199" alt="Select-boot-method-MBR.png"></div>
<div style="text-align:center;"><img src="Select-boot-method-MBR.png" width="582" height="199" alt="Select-boot-method-MBR.png"></div>

<p>1. Boot MX Linux USB in Legacy mode. Run MX Boot Repair.</p>
<p>2. Leave selected: ‘◉ Reinstall GRUB bootloader’ on MBR. Click ‘→ Next’.</p>
Expand Down Expand Up @@ -175,15 +185,15 @@ <h2>Regenerate initramfs images</h2>
<p><b>The files will take some time to be regenerated, especially on a slower PC</b> .</p>

<p>From the man update-initramfs:</p>

<br>
<code>The update-initramfs script manages your initramfs images on your lo‐cal box. It keeps track of the existing initramfs archives in /boot. There are three modes of operation create, update or delete. You must at least specify one of those modes.
The initramfs is a gzipped cpio archive. At boot time, the kernel unpacks that archive into RAM disk, mounts and uses it as initial root file system. All finding of the root device happens in this early userspace.</code>

<br><br><hr>
<br>

<p><b>Development history</b>: Adrian</p>

<p><b>License</b>: <a href="https://mxlinux.org/wiki/licenses/license-mx-boot-repair">here</a>.</p>
<p><b>License</b>: <a href="https://mxlinux.org/wiki/licenses/license-mx-boot-repair">license</a>.</p>

</body>
</html>
Loading