[SOLVED] trying to access boot order to read from a USB asked for administrator psswrd ...not accepted?
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
trying to access boot order to read from a USB asked for administrator psswrd ...not accepted?
Greetings from Portugal @10:37hrs,
Hardware: Hp Pavilion desktop 590-poxxx, 8Gib DDR4, i5-8400 CPU @2.8GHz x6, UHD Graphics 630 (CFL GT2)
I'm running with Pop!_OS 22.04 LTS, 64-bit, Gnome 42.9
Windowing x11
To open Pop OS my psswrd is still being accepted
However, when trying to access boot menu (F9 @start up) I'm asked to enter administrator psswrd?
I use the same psswrd resulting in a symbol I assume to mean You are locked out/cannot access the boot menu
Surfing tinternet over the weekend I encountered someone with a similar problem. However, I didn't take to much heed at the time... duh The gist of said conversation was 'groups' in the terminal had been changed... which means nada to me! I'm a GUI dude the terminal is where a train arrives at :-)
The F9/F12 boot menu has nothing to do with Linux; it's provided by your firmware. Can you remember setting a password for accessing it? Or did you carry out a BIOS update recently?
re. The F9/F12 boot menu has nothing to do with Linux; it's provided by your firmware. Can you remember setting a password for accessing it? Or did you carry out a BIOS update recently?
Hullo Hazel, As far as I'm aware i did not set a psswrd for accessing the boot menu & did not do a BIOS update recently
ps
I just had a look at system firmware in settings and found... UEFI dbx 77 with an update 'signal
changelog
371 Insecure versions of the Microsoft Windows boot manager affected by Black Locus were added to the list of forbidden...
Distribution: Cinnamon Mint 20.1 (Laptop) and 20.2 (Desktop)
Posts: 1,672
Rep:
Hi!
You don't say what sort of HP Pavilion you have, a model No. would help. Normally there is a small shorting link (Called a shunt) on the motherboard which needs to be removed to reset the BIOS Admin password. The link may be marked "PWD" if you're lucky. Check this link to see how to reset a Pavilion All-in-One BIOS.
I just had a look at system firmware in settings and found... UEFI dbx 77 with an update 'signal
changelog
371 Insecure versions of the Microsoft Windows boot manager affected by Black Locus were added to the list of forbidden...
So should I update?
I'm not familiar with recent versions of Windows. Does that signal indicate that the firmware has actually been updated or simply that there's an update waiting? If the former, that might have something to do with your problem. Can you even stop a Windows update from running these days?
On a point of forum protocol: If you want to quote from someone else's post, use Quote rather than Reply. It gives a more legible result.
I'm not familiar with recent versions of Windows. Does that signal indicate that the firmware has actually been updated or simply that there's an update waiting? If the former, that might have something to do with your problem. Can you even stop a Windows update from running these days?
On a point of forum protocol: If you want to quote from someone else's post, use Quote rather than Reply. It gives a more legible result.
Thx Hazel,
forum protocol noted re the firmware update I figure it's a press this button to update & not it has been updated
On the subject of groups: this obviously isn't your problem currently but you might as well know about them since you seem to have stumbled across the concept.
In Unix systems like Linux, every file, directory or resource belongs to some user and also to a user group. In early Unix systems, the groups corresponded to real-life departments like R&D or Finance or a university department. This system allowed people to give close colleagues limited access to some of their files while screening out the rest of the world. Nowadays groups aren't used that way any more but they are still allowed to control access to hardware resources. For example, to get seamless access to plug-in storage devices, you need to be a member of the plugdev group.
Modern Linux distros use a login program that automatically adds personal users to certain groups at login time and that is probably what the posts you found were talking about. If you are curious to know which groups you belong to, open a terminal and type groups.
On the subject of groups: this obviously isn't your problem currently but you might as well know about them since you seem to have stumbled across the concept.
In Unix systems like Linux, every file, directory or resource belongs to some user and also to a user group. In early Unix systems, the groups corresponded to real-life departments like R&D or Finance or a university department. This system allowed people to give close colleagues limited access to some of their files while screening out the rest of the world. Nowadays groups aren't used that way any more but they are still allowed to control access to hardware resources. For example, to get seamless access to plug-in storage devices, you need to be a member of the plugdev group.
Modern Linux distros use a login program that automatically adds personal users to certain groups at login time and that is probably what the posts you found were talking about. If you are curious to know which groups you belong to, open a terminal and type groups.
Groups explanation appreciated & will explore in terminal after I sort out the lunch and then sort out my boot into BIOS problem
I tried repeating the instructions... However, as soon as I type in the psswrd the third time I'm shown a code A {447247A4} {this is not the actual code displayed it's the one from the aforementioned YaChoob vid] because it disappears (faster than the blink of an eye} & I'm taken to the pop! os log in screen
I figured that I could simply power off and repeat the process trying to copy down the code a digit at a time... LOL too simple! The code changes each time Grrr
So, can you, or anyone else reading this, suggest a way of freezing the screen so as I can write it down & proceed to https://bios-pw.org/
thx pal, I am wary of doing the update till prompted! I will now have a look at the links you gave
OK I've had a look at the ubuntu links
Unfortunately, being a linux noobie with no terminal know-how it's a bit like telling a blind man to look further off in the distance
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
