-
-
Notifications
You must be signed in to change notification settings - Fork 93
Add procedure for Windows dual-boot #710
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.
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
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,49 @@ | ||
| --- | ||
| title: Solus does not appear in the startup menu | ||
| summary: Restoring the Solus entry in the startup menu | ||
| --- | ||
|
|
||
| import BootAndChroot from "./snippets/_mount_partitions.mdx"; | ||
| import UnmountAll from "./snippets/_unmount_partitions.mdx"; | ||
| import WhatToDoNext from "./snippets/_contact_team.mdx"; | ||
|
|
||
| This is usually caused by a conflict with another OS on a dual-boot system. | ||
|
|
||
| ## Cause | ||
|
|
||
| There are two common causes: | ||
| 1. After a software update within Solus on systems using a legacy startup method (non-UEFI systems, like GRUB) where another Linux distribution owns the startup manager. | ||
| 1. After Windows updates, Windows may overwrite the MBR (Master Boot Record). This leaves only the Windows Boot Loader in the startup menu. | ||
|
|
||
| ## Procedures to restore access to Solus | ||
|
|
||
| ### If another Linux distribution owns the startup manager on a dual-boot system | ||
|
|
||
| Boot into the other operating system and update the startup manager. | ||
|
|
||
| For more information, check the documentation of your distribution. | ||
|
|
||
| ### If this is a Windows dual-boot system | ||
|
|
||
| 1. Shut down your system. | ||
| 1. Boot from a Solus live USB. | ||
| 1. Mount the partitions of your Solus system. | ||
|
|
||
| <details> | ||
| <BootAndChroot /> | ||
| </details> | ||
|
Comment on lines
+30
to
+34
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Also extra space, I think? |
||
|
|
||
| 1. Run this to update the boot menu. | ||
|
|
||
| ``` | ||
| clr-boot-manager update | ||
| ``` | ||
|
Comment on lines
+38
to
+40
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This should have just three spaces, I think. |
||
|
|
||
| 1. Unmount all the Solus partitions. | ||
| <details> | ||
| <UnmountAll /> | ||
| </details> | ||
|
Comment on lines
+42
to
+45
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. And here. |
||
|
|
||
| ## What to do next | ||
|
|
||
| <WhatToDoNext /> | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Extra space at the start of the line