Ubuntu login issues via Grub
I have two operating systems. After fixing the errors, I can’t enter Ubuntu normally, it only works through the kernel. How can I fix it?
Question information
- Language:
- English Edit question
- Status:
- Solved
- For:
- Ubuntu linux Edit question
- Assignee:
- No assignee Edit question
- Solved by:
- Manfred Hampl
- Solved:
- Last query:
- Last reply:
Revision history for this message
|
#1 |
Please describe, what there is happening when you switch on the system and try starting Ubuntu.
Revision history for this message
|
#2 |
/boot/grub/
is a lot of information on the screen, then a black screen and a blinking
cursor. When I enter through the kernel, the bootloader panel opens and OK
on the first line I enter the system. I do not understand why the Ubuntu
menu does not work?
ср, 30 нояб. 2022 г. в 14:20, Manfred Hampl <
<email address hidden>>:
> Your question #703981 on linux in Ubuntu changed:
> https:/
>
> Status: Open => Needs information
>
> Manfred Hampl requested more information:
> Please describe, what there is happening when you start the system and
> try starting Ubuntu.
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https:/
>
> You received this question notification because you asked the question.
>
--
С уважением
Владимир Бегун
www.begun.ks.ua
Revision history for this message
|
#3 |
"/boot/
What kind of error?
"When I enter through the kernel"
What do you mean by "enter through the kernel"?
When you boot the system, how do you choose to start Windows or Ubuntu?
Do you see the grub menu when you start the system?
Revision history for this message
|
#4 |
Yes, I see the standard menu, but the login through Ubuntu fails (shows a
lot of information, then a blinking cursor and that's it.
When I press enter through the specified kernel, I go through the
bootloader menu by function normally
ср, 30 нояб. 2022 г. в 15:11, Manfred Hampl <
<email address hidden>>:
> Your question #703981 on linux in Ubuntu changed:
> https:/
>
> Status: Open => Needs information
>
> Manfred Hampl requested more information:
> "/boot/
> What kind of error?
>
> "When I enter through the kernel"
> What do you mean by "enter through the kernel"?
>
> When you boot the system, how do you choose to start Windows or Ubuntu?
>
> Do you see the grub menu when you start the system?
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https:/
>
> You received this question notification because you asked the question.
>
--
С уважением
Владимир Бегун
www.begun.ks.ua
Revision history for this message
|
#5 |
Ubuntu, with Linux 5.15.0-53-generic (recovery mode) I go through this
kernel to the menu through the bootloader
ср, 30 нояб. 2022 г. в 15:11, Manfred Hampl <
<email address hidden>>:
> Your question #703981 on linux in Ubuntu changed:
> https:/
>
> Status: Open => Needs information
>
> Manfred Hampl requested more information:
> "/boot/
> What kind of error?
>
> "When I enter through the kernel"
> What do you mean by "enter through the kernel"?
>
> When you boot the system, how do you choose to start Windows or Ubuntu?
>
> Do you see the grub menu when you start the system?
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https:/
>
> You received this question notification because you asked the question.
>
--
С уважением
Владимир Бегун
www.begun.ks.ua
Revision history for this message
|
#6 |
In your other question https:/
Why did you add nomodeset?
Revision history for this message
|
#7 |
I had it by default, I did not change anything
ср, 30 нояб. 2022 г. в 16:11, Manfred Hampl <
<email address hidden>>:
> Your question #703981 on linux in Ubuntu changed:
> https:/
>
> Status: Open => Answered
>
> Manfred Hampl proposed the following answer:
> In your other question
> https:/
> see that you tried adding "nomodeset" to the grub parameters. There are
> some reports of people who tell that their system does not correctly
> boot with the "nomodeset" parameter (especially systems with NVidia
> graphic cards).
>
> Why did you add nomodeset?
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
> https:/
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https:/
>
> You received this question notification because you asked the question.
>
--
С уважением
Владимир Бегун
www.begun.ks.ua
Revision history for this message
|
#8 |
Why did you add nomodeset?
"I had it by default, I did not change anything"
That cannot be true. The whole problem in the other question has been caused by an incomplete addition.
Revision history for this message
|
#9 |
and what to replace this nomodeset with?
ср, 30 нояб. 2022 г. в 17:11, Manfred Hampl <
<email address hidden>>:
> Your question #703981 on linux in Ubuntu changed:
> https:/
>
> Status: Open => Answered
>
> Manfred Hampl proposed the following answer:
> Why did you add nomodeset?
> "I had it by default, I did not change anything"
>
> That cannot be true. The whole problem in the other question has been
> caused by an incomplete addition.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
> https:/
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https:/
>
> You received this question notification because you asked the question.
>
--
С уважением
Владимир Бегун
www.begun.ks.ua
Revision history for this message
|
#10 |
GRUB_CMDLINE_
We have only corrected the quotes in the file of the above operations to
fix the kernel bug
ср, 30 нояб. 2022 г. в 17:11, Manfred Hampl <
<email address hidden>>:
> Your question #703981 on linux in Ubuntu changed:
> https:/
>
> Status: Open => Answered
>
> Manfred Hampl proposed the following answer:
> Why did you add nomodeset?
> "I had it by default, I did not change anything"
>
> That cannot be true. The whole problem in the other question has been
> caused by an incomplete addition.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
> https:/
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https:/
>
> You received this question notification because you asked the question.
>
--
С уважением
Владимир Бегун
www.begun.ks.ua
Revision history for this message
|
#11 |
The default value delivered by Ubuntu before any modification is
GRUB_CMDLINE_
Revision history for this message
|
#12 |
should I replace monodesept with quiet splash in the grub bootloader
itself? Now grub shows an error in the DEVICEMAP-FILE:
/boot/grub/
Ubuntu-File-Edit , change monodesept to quiet splash and save, right or not?
ср, 30 нояб. 2022 г. в 17:50, Manfred Hampl <
<email address hidden>>:
> Your question #703981 on linux in Ubuntu changed:
> https:/
>
> Status: Open => Answered
>
> Manfred Hampl proposed the following answer:
> The default value delivered by Ubuntu before any modification is
>
> GRUB_CMDLINE_
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
> https:/
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https:/
>
> You received this question notification because you asked the question.
>
--
С уважением
Владимир Бегун
www.begun.ks.ua
Revision history for this message
|
#13 |
linux /boot/vmlinuz-
root=UUID=
initrd /boot/initrd.
here you can change it in the bootloader?
ср, 30 нояб. 2022 г. в 17:50, Manfred Hampl <
<email address hidden>>:
> Your question #703981 on linux in Ubuntu changed:
> https:/
>
> Status: Open => Answered
>
> Manfred Hampl proposed the following answer:
> The default value delivered by Ubuntu before any modification is
>
> GRUB_CMDLINE_
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
> https:/
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https:/
>
> You received this question notification because you asked the question.
>
--
С уважением
Владимир Бегун
www.begun.ks.ua
Revision history for this message
|
#14 |
"Now grub shows an error in the DEVICEMAP-FILE: /boot/grub/
Repeating: Which "error" does it show?
And yes, I recommend that you update the contents of /etc/default/grub again, giving "quiet splash" (with quotes!) after the equal sign of GRUB_CMDLINE_
After changing the contents of /etc/default/grub you have to run the command
sudo update-grub
to apply the changes, and then reboot to verify what the effect is.
Revision history for this message
|
#15 |
** (gedit:19707): WARNING **: 20:24:29.704: Failed to set document
metadata: Setting metadata attribute:
displayed in the terminal after changing file line 10 ..quiet splash I have
not yet updated grub - what to do next?
ср, 30 нояб. 2022 г. в 18:51, Manfred Hampl <
<email address hidden>>:
> Your question #703981 on linux in Ubuntu changed:
> https:/
>
> Status: Open => Answered
>
> Manfred Hampl proposed the following answer:
> "Now grub shows an error in the DEVICEMAP-FILE: /boot/grub/
> Repeating: Which "error" does it show?
>
> And yes, I recommend that you update the contents of /etc/default/grub
> again, giving "quiet splash" (with quotes!) after the equal sign of
> GRUB_CMDLINE_
>
> After changing the contents of /etc/default/grub you have to run the
> command
> sudo update-grub
> to apply the changes, and then reboot to verify what the effect is.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
> https:/
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https:/
>
> You received this question notification because you asked the question.
>
--
С уважением
Владимир Бегун
www.begun.ks.ua
Revision history for this message
|
#16 |
You can safely ignore that "set document metadata" warning from gedit. It does not matter.
When you have done a change in the /etc/default/grub file, you must run
sudo update-grub
that the changes are applied to the files used during the boot process.
Revision history for this message
|
#17 |
Super! Everything turned out, the problem is solved, the highest praise for
the recommendations
ср, 30 нояб. 2022 г. в 20:51, Manfred Hampl <
<email address hidden>>:
> Your question #703981 on linux in Ubuntu changed:
> https:/
>
> Status: Open => Answered
>
> Manfred Hampl proposed the following answer:
> You can safely ignore that "set document metadata" warning from gedit.
> It does not matter.
>
> When you have done a change in the /etc/default/grub file, you must run
> sudo update-grub
> that the changes are applied to the files used during the boot process.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
> https:/
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https:/
>
> You received this question notification because you asked the question.
>
--
С уважением
Владимир Бегун
www.begun.ks.ua
Revision history for this message
|
#18 |
Thanks Manfred Hampl, that solved my question.