• Pop!_Planet is still very much under development. Data for the wiki is being sourced from the Arch Linux and Ubuntu wikis, along with a bunch of completely unique content specific to Pop!_OS, and sourcing, converting and updating that content takes time; please be patient. If you can't find what you're looking for here, check the Arch Linux and Ubuntu wikis.
  • Welcome!

    I'll get straight to the point.

    When I started Pop!_Planet, I launched it because I saw a need for a centralized community for Pop!_OS. To be frank, I never expected the level of popularity it has achieved. Over the last year, we have gone from under 50 users, to almost 400 users. That's awesome! However... it also comes with a downside. We are rapidly running out of disk space on our server, and the bandwidth costs go up every month.

    Pop!_Planet is not affiliated with System76 in any way, and is funded completely out of pocket. From day one, I said that I'd never use on-site ads (I hate them as much as you do), so the only monetization we get is through donations. Right now, the donations we receive don't even cover our overhead.

    I know that most users will ignore this message, and that's ok. However, if even a few of our users are willing and able to donate a few dollars to help offset our expenses, it would be greatly appreciated.

    Support Pop!_Planet

    Thank you for your time,

    Dan Griffiths
    Pop!_Planet Founder

Rename label of Pop_OS! in UEFI boot Lemur Pro

papp

New member
Oct 21, 2020
7
0
4
34
Hi,

I have a Lemur Pro with 2 SSD ( one for POP_Os and another for Windows ). After a firmware update, the "Pop_OS!" label inside UEFI boot to chooes Pop_OS! changed to "Samsung SSD 970 EVO Plus 500Gb". How I can rename this label to just "Pop_OS!"
 

Attachments

derpOmattic

Pop!_Muse
Trusted User
Founding Member
Nov 23, 2018
1,548
254
30
www.patreon.com
The name is contained within an EFI variable in the motherboard, so to update that you would need to recreate it with a new name.

You will need to install efibootmgr if it isn't already. apt policy efibootmgr will tell you. Once installed, or if it's already there, just run sudo efibootmgr in a terminal. To see all your options look at the man page man efibootmgr.

Here is an example of one I changed a long time ago.
Code:
sudo efibootmgr
BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0000,0006,0008,000A,0002
Boot0000* Pop!_OS 18.10
Boot0002* Hard Drive
Boot0006* CD/DVD Drive
Boot0008* USB
Boot000A* Removable Drive
"To recreate it with a new name";

So the entry I wanted to change is Boot0000* Pop!_OS 18.10.

Code:
efibootmgr -b 0000 -B
efibootmgr -c -L "Pop!_OS 19.10"
(Don't do this yet, read further down)

I've used the -b option, which is --bootnum XXXX, the bootnum and then -B to --delete-bootnum.


To recreate it with -c, --create and -L to --label the new entry, followed by the new name Pop!_OS 19.10

On advice from evertiro, I dropped the version number. So just Pop!_OS, which will persist through upgrades.

Some caveats.
In order to have the name Pop!_OS, you will have to escape the bang, because ! means something on the Linux command line. That is done with a back slash - it will look like this;

Code:
sudo efibootmgr -b 0000 -B
sudo efibootmgr -c -L Pop\!_OS
EDIT: Use quotes "Pop\!_OS"

This is an example only. You will have to fill in the relevant information for your set up.
 
Last edited:

papp

New member
Oct 21, 2020
7
0
4
34
The name is contained within an EFI variable in the motherboard, so to update that you would need to recreate it with a new name.

You will need to install efibootmgr if it isn't already. apt policy efibootmgr will tell you. Once installed, or if it's already there, just run sudo efibootmgr in a terminal. To see all your options look at the man page man efibootmgr.

Here is an example of one I changed a long time ago.
Code:
sudo efibootmgr
BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0000,0006,0008,000A,0002
Boot0000* Pop!_OS 18.10
Boot0002* Hard Drive
Boot0006* CD/DVD Drive
Boot0008* USB
Boot000A* Removable Drive
"To recreate it with a new name";

So the entry I wanted to change is Boot0000* Pop!_OS 18.10.

Code:
efibootmgr -b 0000 -B
efibootmgr -c -L "Pop!_OS 19.10"
(Don't do this yet, read further down)

I've used the -b option, which is --bootnum XXXX, the bootnum and then -B to --delete-bootnum.


To recreate it with -c, --create and -L to --label the new entry, followed by the new name Pop!_OS 19.10

On advice from evertiro, I dropped the version number. So just Pop!_OS, which will persist through upgrades.

Some caveats.
In order to have the name Pop!_OS, you will have to escape the bang, because ! means something on the Linux command line. That is done with a back slash. Now that you're escaping the bang, you can't use quotes, so it will look like this;

Code:
sudo efibootmgr -b 0000 -B
sudo efibootmgr -c -L Pop\!_OS
This is an example only. You will have to fill in the relevant information for your set up.
I have done what you recommend me and I have that:

xxxx@pop-os:~$ sudo efibootmgr -c -L Pop\!_OS
Could not prepare Boot variable: No such file or directory
 

Attachments

derpOmattic

Pop!_Muse
Trusted User
Founding Member
Nov 23, 2018
1,548
254
30
www.patreon.com
It worked for me, but that was a while ago as you can see. Maybe something changed. If you can wait, I'll try it on my test machine tonight after work.
 

derpOmattic

Pop!_Muse
Trusted User
Founding Member
Nov 23, 2018
1,548
254
30
www.patreon.com
We had a small error while working on the server: Papp said;
My problem persist:

root@pop-os:~# sudo efibootmgr -c -L "Pop\!_OS"

Could not prepare Boot variable: No such file or directory
 

derpOmattic

Pop!_Muse
Trusted User
Founding Member
Nov 23, 2018
1,548
254
30
www.patreon.com
My problem persist:
root@pop-os:~# sudo efibootmgr -c -L "Pop\!_OS"
Could not prepare Boot variable: No such file or directory
@papp, I checked with System76 and they're not aware of any specific reason for the Lemur to do that. I'm not sure why it hasn't worked for you while I literally just did that myself. I checked the error message and it seems to be a little vague.

One fix I saw was to try installing efivar. sudo apt install efivar && reboot

Code:
efivar/focal 37-2ubuntu2 amd64
  Tools to manage UEFI variables

However, I have never tried that and I don't know if it will work.
 

papp

New member
Oct 21, 2020
7
0
4
34
@papp, I checked with System76 and they're not aware of any specific reason for the Lemur to do that. I'm not sure why it hasn't worked for you while I literally just did that myself. I checked the error message and it seems to be a little vague.

One fix I saw was to try installing efivar. sudo apt install efivar && reboot

Code:
efivar/focal 37-2ubuntu2 amd64
  Tools to manage UEFI variables

However, I have never tried that and I don't know if it will work.
I have two drives in my lemur: one for windows and one for Pop_OS. That problem appeared after a firmware update...
I will really appreciate a solution as it is wierd to have 3 boot options and two of them pointing to Pop_OS with wrong labels...
 

papp

New member
Oct 21, 2020
7
0
4
34
@papp, I checked with System76 and they're not aware of any specific reason for the Lemur to do that. I'm not sure why it hasn't worked for you while I literally just did that myself. I checked the error message and it seems to be a little vague.

One fix I saw was to try installing efivar. sudo apt install efivar && reboot

Code:
efivar/focal 37-2ubuntu2 amd64
  Tools to manage UEFI variables

However, I have never tried that and I don't know if it will work.
Thank's for your help derpomatic. I don't know neither why it is not working... I just have two ssd ( one for Windows and One for Pop_OS ) and the problem appeared after a firmware actualisation from Pop_OS three months ago. Do you have any other idea or intuition of what may cause the problem ?
Best,
 

papp

New member
Oct 21, 2020
7
0
4
34
Thank's for your help derpomatic. I don't know neither why it is not working... I just have two ssd ( one for Windows and One for Pop_OS ) and the problem appeared after a firmware actualisation from Pop_OS three months ago. Do you have any other idea or intuition of what may cause the problem ?
Best,
System 76 is giving to me several ineffective solutions since last 3 months...nothing has solved the problem : _(
 

derpOmattic

Pop!_Muse
Trusted User
Founding Member
Nov 23, 2018
1,548
254
30
www.patreon.com
Oh, OK, that's not great, but I'm sure they'll sort it out. I know that doesn't help you now. Maybe you could've led with this piece of information though. :)
 

Members online

No members online now.

Latest projects

Forum statistics

Threads
1,199
Messages
5,520
Members
1,246
Latest member
Moonzenith