Cannot select OS options on dual boot machine [on hold]
up vote
-1
down vote
favorite
When I boot up my laptop I get the
Minimal BASH like line editing is supported. For the first word, TAB lists possible command completions. anywhere else TAB lists possible device or file completions.
error and can no longer select which OS I want to use, as I could in the past.
I had no issue yesterday and have been dual booting for the past three years on this laptop.
Link for when I tried to boot-repair: http://paste.ubuntu.com/p/T42v2C8PQG/
Edit:
Able to get into my Windows 10 OS, but can no longer dual-boot.
paste-bin results : paste.ubuntu.com/p/32yZpxFG68/
Issue: Would like to be able to access both Fedora and Windows.
fedora dual-boot grub
edited 2 days ago
justinnoor.io
340218
asked 2 days ago
Thomas
62
New contributor
Thomas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
put on hold as too broad by Rui F Ribeiro, G-Man, nwildner, Christopher, GAD3R yesterday
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
up vote
-1
down vote
favorite
When I boot up my laptop I get the
Minimal BASH like line editing is supported. For the first word, TAB lists possible command completions. anywhere else TAB lists possible device or file completions.
error and can no longer select which OS I want to use, as I could in the past.
I had no issue yesterday and have been dual booting for the past three years on this laptop.
Link for when I tried to boot-repair: http://paste.ubuntu.com/p/T42v2C8PQG/
Edit:
Able to get into my Windows 10 OS, but can no longer dual-boot.
paste-bin results : paste.ubuntu.com/p/32yZpxFG68/
Issue: Would like to be able to access both Fedora and Windows.
fedora dual-boot grub
edited 2 days ago
justinnoor.io
340218
asked 2 days ago
Thomas
62
New contributor
Thomas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
put on hold as too broad by Rui F Ribeiro, G-Man, nwildner, Christopher, GAD3R yesterday
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
2
I advise disabling EFI and using legacy boot.
– Rui F Ribeiro
2 days ago
1
@RuiFRibeiro doing that and then switching back to EFI let me access my Windows10 OS but not the Fedora OS (no giving me the option to select). It automatically going to Windows10
– Thomas
2 days ago
1
@RuiFRibeiro That's not good advice. He would have to reinstall both Windows and Linux; not a pleasant day's work!
– Michael Hampton
2 days ago
If your system is now booting directly into Windows rather than GRUB, you can go into your BIOS setup and choose a different boot option, i.e. "UEFI: Fedora"
– Michael Hampton
2 days ago
add a comment |
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
When I boot up my laptop I get the
Minimal BASH like line editing is supported. For the first word, TAB lists possible command completions. anywhere else TAB lists possible device or file completions.
error and can no longer select which OS I want to use, as I could in the past.
I had no issue yesterday and have been dual booting for the past three years on this laptop.
Link for when I tried to boot-repair: http://paste.ubuntu.com/p/T42v2C8PQG/
Edit:
Able to get into my Windows 10 OS, but can no longer dual-boot.
paste-bin results : paste.ubuntu.com/p/32yZpxFG68/
Issue: Would like to be able to access both Fedora and Windows.
fedora dual-boot grub
edited 2 days ago
justinnoor.io
340218
asked 2 days ago
Thomas
62
New contributor
Thomas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
When I boot up my laptop I get the
Minimal BASH like line editing is supported. For the first word, TAB lists possible command completions. anywhere else TAB lists possible device or file completions.
error and can no longer select which OS I want to use, as I could in the past.
I had no issue yesterday and have been dual booting for the past three years on this laptop.
Link for when I tried to boot-repair: http://paste.ubuntu.com/p/T42v2C8PQG/
Edit:
Able to get into my Windows 10 OS, but can no longer dual-boot.
paste-bin results : paste.ubuntu.com/p/32yZpxFG68/
Issue: Would like to be able to access both Fedora and Windows.
fedora dual-boot grub
fedora dual-boot grub
edited 2 days ago
justinnoor.io
340218
asked 2 days ago
Thomas
62
New contributor
Thomas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 2 days ago
justinnoor.io
340218
asked 2 days ago
Thomas
62
New contributor
Thomas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 2 days ago
justinnoor.io
340218
edited 2 days ago
justinnoor.io
340218
edited 2 days ago
justinnoor.io
340218
340218
asked 2 days ago
Thomas
62
New contributor
Thomas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 2 days ago
Thomas
62
asked 2 days ago
Thomas
62
62
New contributor
Thomas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Thomas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Thomas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
put on hold as too broad by Rui F Ribeiro, G-Man, nwildner, Christopher, GAD3R yesterday
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
put on hold as too broad by Rui F Ribeiro, G-Man, nwildner, Christopher, GAD3R yesterday
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
2
I advise disabling EFI and using legacy boot.
– Rui F Ribeiro
2 days ago
1
@RuiFRibeiro doing that and then switching back to EFI let me access my Windows10 OS but not the Fedora OS (no giving me the option to select). It automatically going to Windows10
– Thomas
2 days ago
1
@RuiFRibeiro That's not good advice. He would have to reinstall both Windows and Linux; not a pleasant day's work!
– Michael Hampton
2 days ago
If your system is now booting directly into Windows rather than GRUB, you can go into your BIOS setup and choose a different boot option, i.e. "UEFI: Fedora"
– Michael Hampton
2 days ago
add a comment |
2
I advise disabling EFI and using legacy boot.
– Rui F Ribeiro
2 days ago
1
@RuiFRibeiro doing that and then switching back to EFI let me access my Windows10 OS but not the Fedora OS (no giving me the option to select). It automatically going to Windows10
– Thomas
2 days ago
1
@RuiFRibeiro That's not good advice. He would have to reinstall both Windows and Linux; not a pleasant day's work!
– Michael Hampton
2 days ago
If your system is now booting directly into Windows rather than GRUB, you can go into your BIOS setup and choose a different boot option, i.e. "UEFI: Fedora"
– Michael Hampton
2 days ago
2
2
I advise disabling EFI and using legacy boot.
– Rui F Ribeiro
2 days ago
I advise disabling EFI and using legacy boot.
– Rui F Ribeiro
2 days ago
1
1
@RuiFRibeiro doing that and then switching back to EFI let me access my Windows10 OS but not the Fedora OS (no giving me the option to select). It automatically going to Windows10
– Thomas
2 days ago
@RuiFRibeiro doing that and then switching back to EFI let me access my Windows10 OS but not the Fedora OS (no giving me the option to select). It automatically going to Windows10
– Thomas
2 days ago
1
1
@RuiFRibeiro That's not good advice. He would have to reinstall both Windows and Linux; not a pleasant day's work!
– Michael Hampton
2 days ago
@RuiFRibeiro That's not good advice. He would have to reinstall both Windows and Linux; not a pleasant day's work!
– Michael Hampton
2 days ago
If your system is now booting directly into Windows rather than GRUB, you can go into your BIOS setup and choose a different boot option, i.e. "UEFI: Fedora"
– Michael Hampton
2 days ago
If your system is now booting directly into Windows rather than GRUB, you can go into your BIOS setup and choose a different boot option, i.e. "UEFI: Fedora"
– Michael Hampton
2 days ago
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
It looks like someone or something removed a whole lot of important stuff from your grub configuration defaults in /etc/default/grub. Particularly this line:
GRUB_CMDLINE_LINUX="rd.driver.blacklist=nouveau rhgb quiet"
This line originally contained a lot more information, to help grub locate and boot your Linux installation.
The actual grub configuration is built in part from this configuration file.
You should try editing the kernel command line at the grub menu by pressing e while the menu is on display. Then afer rhgb quiet add in root=/dev/sda5 rd.auto to the end. Then press F10 to boot. That should get you in.
After determining that this works and boots your system, to fix the problem permanently, add the same to the line indicated in /etc/default/grub and run grub2-mkconfig -o /etc/grub2-efi.cfg to fix the persistent grub configuration file. (It may happen that you need slightly different options to get the system to boot. In that case, use those options instead.)
answered 2 days ago
Michael Hampton
5,55911740
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
It looks like someone or something removed a whole lot of important stuff from your grub configuration defaults in /etc/default/grub. Particularly this line:
GRUB_CMDLINE_LINUX="rd.driver.blacklist=nouveau rhgb quiet"
This line originally contained a lot more information, to help grub locate and boot your Linux installation.
The actual grub configuration is built in part from this configuration file.
You should try editing the kernel command line at the grub menu by pressing e while the menu is on display. Then afer rhgb quiet add in root=/dev/sda5 rd.auto to the end. Then press F10 to boot. That should get you in.
After determining that this works and boots your system, to fix the problem permanently, add the same to the line indicated in /etc/default/grub and run grub2-mkconfig -o /etc/grub2-efi.cfg to fix the persistent grub configuration file. (It may happen that you need slightly different options to get the system to boot. In that case, use those options instead.)
answered 2 days ago
Michael Hampton
5,55911740
add a comment |
up vote
0
down vote
It looks like someone or something removed a whole lot of important stuff from your grub configuration defaults in /etc/default/grub. Particularly this line:
GRUB_CMDLINE_LINUX="rd.driver.blacklist=nouveau rhgb quiet"
This line originally contained a lot more information, to help grub locate and boot your Linux installation.
The actual grub configuration is built in part from this configuration file.
You should try editing the kernel command line at the grub menu by pressing e while the menu is on display. Then afer rhgb quiet add in root=/dev/sda5 rd.auto to the end. Then press F10 to boot. That should get you in.
After determining that this works and boots your system, to fix the problem permanently, add the same to the line indicated in /etc/default/grub and run grub2-mkconfig -o /etc/grub2-efi.cfg to fix the persistent grub configuration file. (It may happen that you need slightly different options to get the system to boot. In that case, use those options instead.)
answered 2 days ago
Michael Hampton
5,55911740
add a comment |
up vote
0
down vote
up vote
0
down vote
It looks like someone or something removed a whole lot of important stuff from your grub configuration defaults in /etc/default/grub. Particularly this line:
GRUB_CMDLINE_LINUX="rd.driver.blacklist=nouveau rhgb quiet"
This line originally contained a lot more information, to help grub locate and boot your Linux installation.
The actual grub configuration is built in part from this configuration file.
You should try editing the kernel command line at the grub menu by pressing e while the menu is on display. Then afer rhgb quiet add in root=/dev/sda5 rd.auto to the end. Then press F10 to boot. That should get you in.
After determining that this works and boots your system, to fix the problem permanently, add the same to the line indicated in /etc/default/grub and run grub2-mkconfig -o /etc/grub2-efi.cfg to fix the persistent grub configuration file. (It may happen that you need slightly different options to get the system to boot. In that case, use those options instead.)
answered 2 days ago
Michael Hampton
5,55911740
It looks like someone or something removed a whole lot of important stuff from your grub configuration defaults in /etc/default/grub. Particularly this line:
GRUB_CMDLINE_LINUX="rd.driver.blacklist=nouveau rhgb quiet"
This line originally contained a lot more information, to help grub locate and boot your Linux installation.
The actual grub configuration is built in part from this configuration file.
You should try editing the kernel command line at the grub menu by pressing e while the menu is on display. Then afer rhgb quiet add in root=/dev/sda5 rd.auto to the end. Then press F10 to boot. That should get you in.
After determining that this works and boots your system, to fix the problem permanently, add the same to the line indicated in /etc/default/grub and run grub2-mkconfig -o /etc/grub2-efi.cfg to fix the persistent grub configuration file. (It may happen that you need slightly different options to get the system to boot. In that case, use those options instead.)
answered 2 days ago
Michael Hampton
5,55911740
answered 2 days ago
Michael Hampton
5,55911740
answered 2 days ago
Michael Hampton
5,55911740
answered 2 days ago
Michael Hampton
5,55911740
5,55911740
add a comment |
add a comment |
2
I advise disabling EFI and using legacy boot.
– Rui F Ribeiro
2 days ago
1
@RuiFRibeiro doing that and then switching back to EFI let me access my Windows10 OS but not the Fedora OS (no giving me the option to select). It automatically going to Windows10
– Thomas
2 days ago
1
@RuiFRibeiro That's not good advice. He would have to reinstall both Windows and Linux; not a pleasant day's work!
– Michael Hampton
2 days ago
If your system is now booting directly into Windows rather than GRUB, you can go into your BIOS setup and choose a different boot option, i.e. "UEFI: Fedora"
– Michael Hampton
2 days ago