search

PJ-Singh-001 / Cubic

The Official Web Site for Cubic (Custom Ubuntu ISO Creator) (https://github.com/PJ-Singh-001/Cubic)
825 stars 47 forks source link

Unable to start in uefi mode（legacy mode is normal）, stuck in the grub> interface #335

Open lisymail opened 3 months ago

lisymail commented 3 months ago

Describe the bug I changed the value of ID in /etc/os-release to test，After successfully generating the iso。 After the installation of the OS is completed，Unable to start OS in uefi mode（gegacy mode is normal）, stuck in the grub> interface 6

in grub> interface, Execute command ：configfile /efi/test/grub.cfg can enter os，but i don't want to do this。What problem caused this?

To Reproduce

Steps to reproduce the behavior.

Expected behavior

A clear and concise description of what you expected to happen.

OS Information (please complete the following information):

Cubic Information (please complete the following information):

Cubic Log:

Cut and paste the log after running cubic --verbose from the command line

Screenshots

If applicable, add screenshots to help explain your problem.

lisymail commented 3 months ago

@PJ-Singh-001

PJ-Singh-001 commented 3 months ago

@lisymail,

Take a look your grub files and make sure they are OK.

/etc/default
/etc/grub.d

However, I think your issue is GDM or GNOME on Ubuntu may rely on this value in /etc/os-release to run properly.

ID=ubuntu

If you change this back to ID=ubuntu does it start working again?

Perhaps the ":ubuntu" in the gschemas comes from /etc/os-release?...

grep ":ubuntu" /usr/share/glib-2.0/schemas/*
lisymail commented 3 months ago

Not a problem with GDM or GNOME。。。。。

You can use cubic to test it. During this process, you only change the ID in os-release , then generate the iso, and finally use the generated iso to install it in the uefi environment. After the installation is completed, the system will start again. Go to the grub interface This way, we can reproduce the problem I @PJ-Singh-001

PJ-Singh-001 commented 3 months ago

I'll try it out, but it will take me some time to get to it, since I am preparing the next release right now.

You may already know this, but there are three places where distributor information is stored.

cat /etc/lsb-release 
cat /etc/os-release 
cat /usr/lib/os-release

Ubuntu uses /etc/lsb-release. But if you are changing this, you may want to be consistent.

ChaoJiLiChen commented 3 months ago

Is this problem solved? I also encountered this problem. I looked at /etc/lsb-release and got the information from the os-release file.

PJ-Singh-001 commented 3 months ago

@ChaoJiLiChen,

What changes did you make?

PJ-Singh-001 commented 3 months ago

@lisymail, @ChaoJiLiChen,

If you had added a variable to the os-release file, note that variables are not supported by this file and will not be parsed.

ChaoJiLiChen commented 3 months ago

I just changed the ID in the os-release file, and left everything else unchanged.