Show me your UEFI settings page - looking for functions

Dark Rider

New Member
Member
Messages
187
Can people please show me their UEFI settings page? I'm looking to prove or disprove something that the HP people are now telling me.

First off, they do not give tech support for UEFI - UEFI is advanced they say with advanced Issues. This is why you will find no mention of UEFI in an HP service manual. They say contact Microsoft which is silly because MS only requires the use of these features - they are not the OEM responsible for the bios/UEFI functionality.

According to the Windows Hardware Certification Requirements for Client and Server Systems, Sections 14 through 18 under the heading: System.Fundamentals.Firmware.UEFISecureBoot ( Windows Hardware Certification Requirements for Client and Server Systems) Users, not OEM's are supposed to have the ability to delete Secure Boot keys ( even Microsoft's key if they wanted, of course this would cause Windows 8 not to boot in UEFI mode with Secure Boot enabled) or add your own Secure Boot keys assuming you have one that's needed for an OS you created or some other system running at boot time.

I think either the tech support at HP are either lackeys reading from a script and even the Supervisors have no clue whats going on or HP is doing this on purpose to pull a fast one. I think it's possible HP may be in breech of agreement with Microsoft - that, or something else is going on that's not clear to anyone.

I want to know, does Anyone have a UEFI firmware settings section that allows this functionality of being able to delete (not disable) the Secure Boot Keys (PK) or add your own keys as is Required by Microsoft?
 

My Computer

System One

  • OS
    Windows 8 64 bit
    System Manufacturer/Model
    HP Pavillion G7-2251dx
    CPU
    AMD A-8 4500M
    Memory
    8 Gigabytes DDR3 sdram
    Graphics Card(s)
    Discrete ATI Radeon HD 7640G with 2 Gigs
    Sound Card
    IDT Audio
    Monitor(s) Displays
    17.3
    Screen Resolution
    1600x900
    Hard Drives
    500 gig
    Internet Speed
    3.5 mb/sec
It depends on how UEFI is implemented in the system. For most HP systems, you still have the option for legacy booting, which makes UEFI secure boot not nearly as effective. If you've built a system using such legacy modes, there's nothing to disable. I have yet to see an HP system that is pure UEFI. If that time comes, then yes, there will be a setting to turn of Secure Boot... it will read something like "Secure Boot: Enabled/Disabled or Yes/No."

I can't go into detail about systems I've seen that aren't ready for prime-time or speculate whether it will show up sooner rather than later.

-J

(Disclaimer: I work for Microsoft. My opinions are my own. I do not speculate on un-released products nor will I divulge any information relating to such)
 

My Computer

System One

  • OS
    Windows 8, Windows 7
    System Manufacturer/Model
    HP Z210
    Internet Speed
    25mbps
While that's interesting that's really outside of the scope of this discussion. Disabling Secure Boot and or switching between UEFI and Legacy Bios mode are two issues that have nothing to do with the above issue. HP tech support told me the same thing - as if they could not understand the question. They kept repeating instructions for disabling Secure Boot and or switching to Legacy Mode. We already have a way to disable Secure Boot as mentioned here: http://www.eightforums.com/tutorials/17058-secure-boot-enable-disable-uefi.html#post185128

HP tech support did not understand that disabling Secure Boot and the ability to remove or add Secure Boot keys (PK) are two totally different things. When I patiently explained to them the issue and actually read from the Windows Hardware Certification for Client and Server Systems document they told me they don't give support for UEFI and I would have to ask Microsoft about this.

Let me ask you this. If I create a Secure Boot Key for a operating system I create, How do I implement this in UEFI so that it can check against the information in my boot loader (in my distro disks) to KNOW it's o.k. to let it install? There Has to be a way to add this key to UEFI so it can use verify my system as good to install.

Whats the normal procedure for doing this?
 

My Computer

System One

  • OS
    Windows 8 64 bit
    System Manufacturer/Model
    HP Pavillion G7-2251dx
    CPU
    AMD A-8 4500M
    Memory
    8 Gigabytes DDR3 sdram
    Graphics Card(s)
    Discrete ATI Radeon HD 7640G with 2 Gigs
    Sound Card
    IDT Audio
    Monitor(s) Displays
    17.3
    Screen Resolution
    1600x900
    Hard Drives
    500 gig
    Internet Speed
    3.5 mb/sec
I want to know, does Anyone have a UEFI firmware settings section that allows this functionality of being able to delete (not disable) the Secure Boot Keys (PK) or add your own keys as is Required by Microsoft?

It's a plain simple page based on the Insyde BIOS used in all HP's. You have the ability to enable lagacy mode (CMS) for MBR boot.
You can also disable SecureBoot BUT that's all... most advanced options are hidden from the user.

Where does it states that your own keys are required?
They are possible but not required.

I have a HP UEFI here but I don't see any advanced options anytime soon.
There will be BIOS mods possible in the future but as long as all works nicely with default settings, I'm not gonna manually tweak the settings.

This is for laptops in my case. I don't have any idea about the possible additions a HP desktop pc can have in the UEFI settings.
 

My Computer

System One

  • OS
    Windows 10 x64
    Computer type
    Laptop
    System Manufacturer/Model
    HP Envy DV6 7250
    CPU
    Intel i7-3630QM
    Motherboard
    HP, Intel HM77 Express Chipset
    Memory
    16GB
    Graphics Card(s)
    Intel HD4000 + Nvidia Geforce 630M
    Sound Card
    IDT HD Audio
    Monitor(s) Displays
    15.6' built-in + Samsung S22D300 + 17.3' LG Phillips
    Screen Resolution
    multiple resolutions
    Hard Drives
    Samsung SSD 250GB + Hitachi HDD 750GB
    PSU
    120W adapter
    Case
    small
    Cooling
    laptop cooling pad
    Keyboard
    Backlit built-in + big one in USB
    Mouse
    SteelSeries Sensei
    Internet Speed
    slow and steady
    Browser
    Chromium, Pale Moon, Firefox Developer Edition
    Antivirus
    Windows Defender
    Other Info
    That's basically it.
Let me ask you this. If I create a Secure Boot Key for a operating system I create, How do I implement this in UEFI so that it can check against the information in my boot loader (in my distro disks) to KNOW it's o.k. to let it install? There Has to be a way to add this key to UEFI so it can use verify my system as good to install.

Whats the normal procedure for doing this?

They don't give support for this because it is not something they've built so the end user can mess with. I say mess with and not re-configure because there's very little need to do so. If you install a legit OS, UEFI will take it just fine because it is signed and certified and the UEFI boot files will reflect that. There is nothing on your part that you realistically will need to do.

I want to know, does Anyone have a UEFI firmware settings section that allows this functionality of being able to delete (not disable) the Secure Boot Keys (PK) or add your own keys as is Required by Microsoft?

This is for laptops in my case. I don't have any idea about the possible additions a HP desktop pc can have in the UEFI settings.

This is the same for desktops. It is not a necessary setting to change so it is left out of the locked down, non-engineering version of the board.
 

My Computer

System One

  • OS
    Windows 8, Windows 7
    System Manufacturer/Model
    HP Z210
    Internet Speed
    25mbps
Hopachi says, " Where does it states that your own keys are required?
They are possible but not required."

JLyman says, "They don't give support for this because it is not something they've built so the end user can mess with"

It Is required and they Do have to provide the user support for it because section 17 says:

Mandatory. On non-ARM systems, the platform MUST implement the ability for a physically present user to select between two Secure Boot modes in firmware setup: "Custom" and "Standard". Custom Mode allows for more flexibility as specified in the following:

It shall be possible for a physically present user to use the Custom Mode firmware setup option to modify the contents of the Secure Boot signature databases and the PK. This may be implemented by simply providing the option to clear all Secure Boot databases (PK, KEK, db, dbx), which puts the system into setup mode.

If the user ends up deleting the PK then, upon exiting the Custom Mode firmware setup, the system is operating in Setup Mode with SecureBoot turned off.

The firmware setup shall indicate if Secure Boot is turned on, and if it is operated in Standard or Custom Mode. The firmware setup must provide an option to return from Custom to Standard Mode which restores the factory defaults. On an ARM system, it is forbidden to enable Custom Mode. Only Standard Mode may be enabled.

This is the agreement HP has with Microsoft. HP's UEFI must provide the ability to access and use this Custom mode.

Hopachi, the using your own keys comes into play if you make a system (New os or system tool) that needs to boot with UEFI's Secure Boot enabled. You have to create a key for your firmware so it can check this key against the key in your boot loader. However it's implemented. you the User must have the ability to do this if you need to. It is this Custom mode with it's deleting or adding keys functionality that should be present in your UEFI Firmware settings according to this. It even says in this document you have the ability to delete ( not disable) Microsoft's own key.

I contend, HP only ships with Standard mode UEFI Firmware Settings functionality. Or else, I should be able to access the Custom option. Lets say I want to "modify the contents of the Secure Boot signature databases and the PK." Remember, this is a Secure Boot option, not what you can pass to the system by disabling Secure Boot. My system does not seem to have the ability to do this. The only Secure Boot options I do have is either on or off. Lets say i want to completely delete Microsoft's own key. I would need to access this Custom mode and it's functionality to do that. it's missing from HP's UEFI Firmware Settings.

JLyman, My take on this is you may be right but they Have to rebuild the bios/UEFI to enable this functionality. The User ( not the OEM) has to be able to use Custom mode and all the things listed above it's supposed to be able to do.

Perhaps the problem I'm having with it is not in the UEFI firmware but Microsoft's writing of the document. This statement, "If the user ends up deleting the PK then, upon exiting the Custom Mode firmware setup, the system is operating in Setup Mode with SecureBoot turned off." suggests that you can first delete the PK and then on exiting the firmware Secure Boot will be started in Off Mode - when they really mean, By turning Secure Boot off, you effectively delete the PK - But this really sounds like to me whats happening is " This may be implemented by simply providing the option to clear all Secure Boot databases (PK, KEK, db, dbx), which puts the system into setup mode." And which can then be " return from Custom to Standard Mode which restores the factory defaults." but it doesn't read that way at all as written. It actually sounds like you should have more ability from Firmware settings to control PK.

UEFI specifies (section 27.5) a Platform Key (PK), which is designed to be controlled by the Platform Owner (whoever owns the hardware) and a set of Key-Exchange Keys (KEKs), which are designed to be controlled by the OEM and OS vendors. “Controlled” in this sense means that these keys are public/private key pairs; whoever knows the private key is the key controller, but to install the
key, you only need the public piece, which means KEKs may be installed by anybody without controlling them. This separation is vital because it allows the platform owner to decide which keys they trust without compromising the ability of the KEK controllers to assure themselves that the OS booted securely.
Making UEFI Secure Boot Work With Open Platforms | The Linux Foundation
 
Last edited:

My Computer

System One

  • OS
    Windows 8 64 bit
    System Manufacturer/Model
    HP Pavillion G7-2251dx
    CPU
    AMD A-8 4500M
    Memory
    8 Gigabytes DDR3 sdram
    Graphics Card(s)
    Discrete ATI Radeon HD 7640G with 2 Gigs
    Sound Card
    IDT Audio
    Monitor(s) Displays
    17.3
    Screen Resolution
    1600x900
    Hard Drives
    500 gig
    Internet Speed
    3.5 mb/sec
Hopachi says, " Where does it states that your own keys are required?
They are possible but not required."

JLyman says, "They don't give support for this because it is not something they've built so the end user can mess with"

It Is required and they Do have to provide the user support for it because section 17 says:

Mandatory. On non-ARM systems, the platform MUST implement the ability for a physically present user to select between two Secure Boot modes in firmware setup: "Custom" and "Standard". Custom Mode allows for more flexibility as specified in the following:

It shall be possible for a physically present user to use the Custom Mode firmware setup option to modify the contents of the Secure Boot signature databases and the PK. This may be implemented by simply providing the option to clear all Secure Boot databases (PK, KEK, db, dbx), which puts the system into setup mode.

If the user ends up deleting the PK then, upon exiting the Custom Mode firmware setup, the system is operating in Setup Mode with SecureBoot turned off.

The firmware setup shall indicate if Secure Boot is turned on, and if it is operated in Standard or Custom Mode. The firmware setup must provide an option to return from Custom to Standard Mode which restores the factory defaults. On an ARM system, it is forbidden to enable Custom Mode. Only Standard Mode may be enabled.

This is the agreement HP has with Microsoft. HP's UEFI must provide the ability to access and use this Custom mode.

Hopachi, the using your own keys comes into play if you make a system (New os or system tool) that needs to boot with UEFI's Secure Boot enabled. You have to create a key for your firmware so it can check this key against the key in your boot loader. However it's implemented. you the User must have the ability to do this if you need to. It is this Custom mode with it's deleting or adding keys functionality that should be present in your UEFI Firmware settings according to this. It even says in this document you have the ability to delete ( not disable) Microsoft's own key.

I contend, HP only ships with Standard mode UEFI Firmware Settings functionality. Or else, I should be able to access the Custom option. Lets say I want to "modify the contents of the Secure Boot signature databases and the PK." Remember, this is a Secure Boot option, not what you can pass to the system by disabling Secure Boot. My system does not seem to have the ability to do this. The only Secure Boot options I do have is either on or off. Lets say i want to completly delete Microsoft's own key. I would need to access this Custom mode and it's functionality to do that. it's missing from HP's UEFI Firmware Settings.

JLyman, My take on this is you may be right but they Have to rebuild the bios/UEFI to enable this functionality. The User ( not the OEM) has to be able to use Custom mode and all the things listed above it's supposed to be able to do.

That's if the machine is using a purebred UEFI system. I have yet to see an HP system that used UEFI over BIOS. Every system I've seen was a BIOS based system that ONLY used UEFI as an optional boot manager. If the system is still BIOS-based, the above requirements do not apply.

I'm going to state this once and only once as this is ending up to be nothing but beating around the bush: Microsoft knows what HP's hardware is like and whether it has passed this certification or not. This stuff is apparent very early on in the build and engineering process. They communicate regularly during testing so any issues regarding this would have come up, already.

Please reference the attached image.

Notice the information. Nowhere is UEFI mentioned. This is an HP system that uses UEFI as an interpreter for booting to UEFI-based OSes like Windows 8. That is all it does. If the system was 100% UEFI, then all of the requirements you're fishing for would exist. End of story.
 

Attachments

  • Capture.PNG
    Capture.PNG
    99.8 KB · Views: 171

My Computer

System One

  • OS
    Windows 8, Windows 7
    System Manufacturer/Model
    HP Z210
    Internet Speed
    25mbps
This is an HP system that uses UEFI as an interpreter for booting to UEFI-based OSes like Windows 8. That is all it does. If the system was 100% UEFI, then all of the requirements you're fishing for would exist. End of story.

Why didn't you say this to begin with? So, I'm not crazy. I'm 100% Right. I do have a HP bios/UEFI that has scaled down functionality. But Only because it's not designed as a full UEFI system but Only an interpreter. I suppose for a few years most will be hybrid systems ( and hybrid is really the wrong term) because the code for UEFI is so buggy and hardware manufacturers are still figuring out the best ways to create drivers that work well. Interesting info on that here: EFI and Linux: the future is here, and it's awful - Matthew Garrett - YouTube

You know people read those documents and get the wrong impression when little details like that is left out. Just search the Linux and other non MS system blogs who talk about these systems that are required to use UEFI and Secure Boot. You say, "If the system is still BIOS-based, the above requirements do not apply." Where can I find that in the documentation - or anywhere so I can use it as a reference ?

So these systems are Legacy Bios based only with a UEFI interpreter. They are Not hybrid Bios/Uefi systems like most people say.
 

My Computer

System One

  • OS
    Windows 8 64 bit
    System Manufacturer/Model
    HP Pavillion G7-2251dx
    CPU
    AMD A-8 4500M
    Memory
    8 Gigabytes DDR3 sdram
    Graphics Card(s)
    Discrete ATI Radeon HD 7640G with 2 Gigs
    Sound Card
    IDT Audio
    Monitor(s) Displays
    17.3
    Screen Resolution
    1600x900
    Hard Drives
    500 gig
    Internet Speed
    3.5 mb/sec
This is an HP system that uses UEFI as an interpreter for booting to UEFI-based OSes like Windows 8. That is all it does. If the system was 100% UEFI, then all of the requirements you're fishing for would exist. End of story.

Why didn't you say this to begin with? So, I'm not crazy. I'm 100% Right. I do have a HP bios/UEFI that has scaled down functionality. But Only because it's not designed as a full UEFI system but Only an interpreter. I suppose for a few years most will be hybrid systems ( and hybrid is really the wrong term) because the code for UEFI is so buggy and hardware manufacturers are still figuring out the best ways to create drivers that work well. Interesting info on that here: EFI and Linux: the future is here, and it's awful - Matthew Garrett - YouTube

You know people read those documents and get the wrong impression when little details like that is left out. Just search the Linux and other non MS system blogs who talk about these systems that are required to use UEFI and Secure Boot. You say, "If the system is still BIOS-based, the above requirements do not apply." Where can I find that in the documentation - or anywhere so I can use it as a reference ?

So these systems are Legacy Bios based only with a UEFI interpreter. They are Not hybrid Bios/Uefi systems like most people say.

Because the system is still 100% BIOS based. The only time UEFI is called upon is if you have it in the boot list... otherwise you're never handed off to it and the good ol' fashioned BOOTMGR takes over. I think the most accurate description would be "BIOS-based with a possible UEFI second-stage." If you disabled the UEFI boot options, UEFI would NEVER be called upon or interact with the boot process. I'm sorry if I confused you. I was running off of limited information until I could clear the sharing. I like my job, after all. ;)
 

My Computer

System One

  • OS
    Windows 8, Windows 7
    System Manufacturer/Model
    HP Z210
    Internet Speed
    25mbps
Thanks. I do appreciate the info. That's the first time I've heard anyone describe these systems like that.
 

My Computer

System One

  • OS
    Windows 8 64 bit
    System Manufacturer/Model
    HP Pavillion G7-2251dx
    CPU
    AMD A-8 4500M
    Memory
    8 Gigabytes DDR3 sdram
    Graphics Card(s)
    Discrete ATI Radeon HD 7640G with 2 Gigs
    Sound Card
    IDT Audio
    Monitor(s) Displays
    17.3
    Screen Resolution
    1600x900
    Hard Drives
    500 gig
    Internet Speed
    3.5 mb/sec
I agree with JLyman.
The BIOS interface is the SAME as on my older 100% BIOS and is also made by Insyde.

The UEFI is added on top: seems a good explanation. But legacy mode (classic BIOS boot) comes in second place so, yeah, UEFI is more important as default choice.

What we have here are between the first UEFI based BIOSes from HP and it's not excluded they'll modify and add extra options in the future. For stability alone I had already 2 firmware updates since September.

However they still hide some functionality away. I've seen that by looking at extra options people unlocked at biosmods.com but that was by looking at classic BIOS options (will be available for newer version as well with increased demand). The new UEFI ones will also have advanced hidden menu's that are hidden for the sake of most users (ok, there are a few experts here and there but that's all). The normal users don't know what the settings do and can mess their configs pretty fast. UEFI has many options and most still evolve as newer functionality is added, it's still early for UEFI as intended to replace the BIOS for good BUT is pretty normal they don't apply all theory (specifications) into practice stating with the first versions you get.
 

My Computer

System One

  • OS
    Windows 10 x64
    Computer type
    Laptop
    System Manufacturer/Model
    HP Envy DV6 7250
    CPU
    Intel i7-3630QM
    Motherboard
    HP, Intel HM77 Express Chipset
    Memory
    16GB
    Graphics Card(s)
    Intel HD4000 + Nvidia Geforce 630M
    Sound Card
    IDT HD Audio
    Monitor(s) Displays
    15.6' built-in + Samsung S22D300 + 17.3' LG Phillips
    Screen Resolution
    multiple resolutions
    Hard Drives
    Samsung SSD 250GB + Hitachi HDD 750GB
    PSU
    120W adapter
    Case
    small
    Cooling
    laptop cooling pad
    Keyboard
    Backlit built-in + big one in USB
    Mouse
    SteelSeries Sensei
    Internet Speed
    slow and steady
    Browser
    Chromium, Pale Moon, Firefox Developer Edition
    Antivirus
    Windows Defender
    Other Info
    That's basically it.
In my opinion it seems someone at Microsoft thought it would be a great idea if all Windows 8 users became test subjects. Almost as if they said, " Lets get people to use this buggy unproven technology and see what happens". I know it didn't happen that way but that's what it seems like. I have browsed many Linux distro forums and am even on some trying to get the likes of Mint 14 or Ubuntu to install and work properly under UEFI with secure boot disabled and have run into tons of troubles even the Linux old time experts have a hard time figuring out. You'll notice on those forums the first thing people with Windows 8 does is disable UEFI and switch to Legacy Bios mode. They don't want to deal with UEFI. I am one of the crazy ones who have spend a week fighting with these systems - and Ubuntu and Mint do have compatibility build in for EFI. ( I like the idea of UEFI's faster hardware access coupled with a fast 64 bit system so I stuck it out trying to make this work) One would think that these forums would be full of people with Windows 8 trying to get a Linux distro to install under UEFI but that isn't happening this time around. These Linux old timers are folks that are used to getting into the code in the systems and configuring the system they way they want to - yet, they are leery of UEFI. On one hand it's said Uefi is more secure than Bios but Bios is written in assembly language which hardly anyone uses anymore. UEFI is written in C which tons of people use. I think it's possible hackers have a better chance of exploiting UEFI than they do Bios for these reasons. One things for sure, these new adventures into Uefi are going to be a wild ride.

Even if these UEFI's were fully functional versions with no Bios mode, it should not be possible for someone to mess up the system very badly (outside of using a hack/malware to attack the system) . There appear to be contingencies build in for this where the system would revert to factory default firmware and in the case of Secure Boot default PK's and datebase.
 

My Computer

System One

  • OS
    Windows 8 64 bit
    System Manufacturer/Model
    HP Pavillion G7-2251dx
    CPU
    AMD A-8 4500M
    Memory
    8 Gigabytes DDR3 sdram
    Graphics Card(s)
    Discrete ATI Radeon HD 7640G with 2 Gigs
    Sound Card
    IDT Audio
    Monitor(s) Displays
    17.3
    Screen Resolution
    1600x900
    Hard Drives
    500 gig
    Internet Speed
    3.5 mb/sec
On one hand it's said Uefi is more secure than Bios but Bios is written in assembly language which hardly anyone uses anymore. UEFI is written in C which tons of people use.

Who said that? Well... it's said... legends... but I programmed a thing or two and can tell you that the programming language of BIOSes is not assembler nowadays. The assembler is in portions not entire code because it's too hard to follow.
The used language is irrelevant and it's mostly C and C++ but watch out the slight differences.
SO They even, use C and C++ to make BIOSes, actually the same BIOS makers are the ones adapting the UEFI in newer models, or you thought just for UEFI new companies will rise?
The hackers will always be able to reverse-engineer in assembler no matter what the code is. Nobody programs in assembler anymore but that's a different story.

Even if these UEFI's were fully functional versions with no Bios mode, it should not be possible for someone to mess up the system very badly
No UEFI alone is pretty solid.
I was refering to a BIOS with all possible options available: I don't think you've seen one otherwise you will complain for other reasons like too many options. :)

I've seen HP BIOSes that expose the advanced menu and to be honest 70% of what's available there a normal, even more advanced user wouldn't understand. And there are options with "do not change" next to choice menu's: those are the ones you have to avoid because you'll mess things pretty badly if you touch them.

If they hide most of the options is good thing.
For your more choice-friendly UEFI you'll have to wait a bit more because it's just the beginning and you'll see other stuff coming along the way.

I agree that a more advanced choice menu should be available, I have HP too. We'll just have to see what updates or fixes will be available in future versions.

Cheers
Hopachi
 

My Computer

System One

  • OS
    Windows 10 x64
    Computer type
    Laptop
    System Manufacturer/Model
    HP Envy DV6 7250
    CPU
    Intel i7-3630QM
    Motherboard
    HP, Intel HM77 Express Chipset
    Memory
    16GB
    Graphics Card(s)
    Intel HD4000 + Nvidia Geforce 630M
    Sound Card
    IDT HD Audio
    Monitor(s) Displays
    15.6' built-in + Samsung S22D300 + 17.3' LG Phillips
    Screen Resolution
    multiple resolutions
    Hard Drives
    Samsung SSD 250GB + Hitachi HDD 750GB
    PSU
    120W adapter
    Case
    small
    Cooling
    laptop cooling pad
    Keyboard
    Backlit built-in + big one in USB
    Mouse
    SteelSeries Sensei
    Internet Speed
    slow and steady
    Browser
    Chromium, Pale Moon, Firefox Developer Edition
    Antivirus
    Windows Defender
    Other Info
    That's basically it.
I've seen HP BIOSes that expose the advanced menu and to be honest 70% of what's available there a normal, even more advanced user wouldn't understand. And there are options with "do not change" next to choice menu's: those are the ones you have to avoid because you'll mess things pretty badly if you touch them.

If they hide most of the options is good thing.
For your more choice-friendly UEFI you'll have to wait a bit more because it's just the beginning and you'll see other stuff coming along the way.

I agree that a more advanced choice menu should be available, I have HP too. We'll just have to see what updates or fixes will be available in future versions.

Cheers
Hopachi

Some pre-production boards with the full UEFI feature-set exposed can have upwards of two hundred different things to tweak, most of it even I don't understand.
 

My Computer

System One

  • OS
    Windows 8, Windows 7
    System Manufacturer/Model
    HP Z210
    Internet Speed
    25mbps
Thanks for the updated info Hopachi. I supposed I read that about Bios being written in assembly by people who were pushing UEFI. Actually I think it was a youtube video telling of the differences between the two.

Seems many Samsung models are bricking the systems when you try to run Ubuntu under UEFI with secure boot disabled. Booting Linux using UEFI can brick Samsung laptops - The H Open: News and Features Reading this it's not clear to me if this is an Ubuntu problem, a Samsung firmware problem or a hybrid with both.

Bricking for those who don't know means permanently crippling the system where they will boot nothing, even Win 8 with Secure Boot enabled. It effectively turns the system into a brick, a door stop.
 

My Computer

System One

  • OS
    Windows 8 64 bit
    System Manufacturer/Model
    HP Pavillion G7-2251dx
    CPU
    AMD A-8 4500M
    Memory
    8 Gigabytes DDR3 sdram
    Graphics Card(s)
    Discrete ATI Radeon HD 7640G with 2 Gigs
    Sound Card
    IDT Audio
    Monitor(s) Displays
    17.3
    Screen Resolution
    1600x900
    Hard Drives
    500 gig
    Internet Speed
    3.5 mb/sec
Thanks for the updated info Hopachi. I supposed I read that about Bios being written in assembly by people who were pushing UEFI. Actually I think it was a youtube video telling of the differences between the two.

Seems many Samsung models are bricking the systems when you try to run Ubuntu under UEFI with secure boot disabled. Booting Linux using UEFI can brick Samsung laptops - The H Open: News and Features Reading this it's not clear to me if this is an Ubuntu problem, a Samsung firmware problem or a hybrid with both.

Bricking for those who don't know means permanently crippling the system where they will boot nothing, even Win 8 with Secure Boot enabled. It effectively turns the system into a brick, a door stop.

You're welcome.

The bricking is troublesome, I saw the article.

For those Samsung laptops a fix has been found and probably the'll learn something about this and release a few updates on it:
http://www.eightforums.com/windows-...ed-booting-linux-using-uefi-2.html#post186430

Luckily those aren't entirely bricked. But Linux won't be recommended on them until they decide to do something about it.

Some pre-production boards with the full UEFI feature-set exposed can have upwards of two hundred different things to tweak, most of it even I don't understand.

Confirmed by a MS Windows Engineer. Thanks.
That explains even more why many options, irrelevant for the end-user, are hidden. :)
 

My Computer

System One

  • OS
    Windows 10 x64
    Computer type
    Laptop
    System Manufacturer/Model
    HP Envy DV6 7250
    CPU
    Intel i7-3630QM
    Motherboard
    HP, Intel HM77 Express Chipset
    Memory
    16GB
    Graphics Card(s)
    Intel HD4000 + Nvidia Geforce 630M
    Sound Card
    IDT HD Audio
    Monitor(s) Displays
    15.6' built-in + Samsung S22D300 + 17.3' LG Phillips
    Screen Resolution
    multiple resolutions
    Hard Drives
    Samsung SSD 250GB + Hitachi HDD 750GB
    PSU
    120W adapter
    Case
    small
    Cooling
    laptop cooling pad
    Keyboard
    Backlit built-in + big one in USB
    Mouse
    SteelSeries Sensei
    Internet Speed
    slow and steady
    Browser
    Chromium, Pale Moon, Firefox Developer Edition
    Antivirus
    Windows Defender
    Other Info
    That's basically it.
Some pre-production boards with the full UEFI feature-set exposed can have upwards of two hundred different things to tweak, most of it even I don't understand.

Confirmed by a MS Windows Engineer. Thanks.
That explains even more why many options, irrelevant for the end-user, are hidden. :)

A lot of it is specific stuff for Intel or AMD to test their chipsets with and are really only there to forcibly create new scenarios.
 

My Computer

System One

  • OS
    Windows 8, Windows 7
    System Manufacturer/Model
    HP Z210
    Internet Speed
    25mbps
Back
Top