126 Posts
0
9614
Optiplex 7010 graphics card doesn't work under UEFI
Very odd issue, after I switched a 7010 to UEFI and secure boot, it no longer will display anything over the graphics card in it, but the onboard graphics work fine. I don't even get the Dell logo on startup with the graphics card, it's that bad.
Any ideas on why this would happen? BIOS is A29, the graphics card has been in that system (but under legacy boot) for years, and worked fine up until the switch to UEFI/secure boot and reimaging.
speedstep
9 Legend
9 Legend
•
47K Posts
0
June 18th, 2019 07:00
The 7010 is not a Class 2.3.1 UEFI machine.
It can in fact run XP.
https://www.dell.com/support/article/us/en/04/how13914/optiplex-7010-xp-driver-cab?lang=en
The supported cards are
OptiPlex 9010/7010/3010/390
Discrete Video card Options:
https://www.amazon.com/Dell-DELL-51NCR/dp/B01N7CSNWK
SECURE BOOT IS NEVER EVER an option for a machine that will boot and run XP.
This is why the machine is NOT COMPATIBLE AT ALL with UEFI based Graphics cards.
Legacy Radeon HD Cards are all that are supported.
Legacy Nvidia cards up to Pascal aka GTX 1080 are fine.
RTX cards wont work for the same UEFI reason.
speedstep
9 Legend
9 Legend
•
47K Posts
0
July 18th, 2020 02:00
UEFI 2.3.1 specifications started with windows 8.0 OCTOBER 26, 2012
Thats also when they removed the COA sticker and started putting the key in bios.
As late as 2014 there is still an XP Driver cab for 3010 7010 9010
https://www.dell.com/support/article/en-us/how13914/optiplex-7010-xp-driver-cab?lang=en
UEFI 2.3.1 secure boot key in bios is never an option for a 3010 7010 9010
Not an issue with 3020 7020 9020
https://docs.microsoft.com/en-us/windows-hardware/design/compatibility/whcp-specifications-policies
Since Windows 10 and 64 bit only is the only path forward I absolutely dispute that a system that allows 32 bit XP is working perfectly.
Where are your 1650 1660 32 bit anything drivers?
Where are your 1650 1660 32 bit XP or Vista Drivers?
My Table clearly says approximate for model years.
It shows Green for models that are supported with Windows 10.
Not supported doesn't mean not working.
It does mean that there will never be WIN10 drivers for those models.
Snipping pictures from my posts years ago out of context in no way validates any of your claims. Dell has more recently decided that the 3010 7010 9010 models will be supported for 10. But not all versions of 10 and specifically there will be no WIN2004 DCH drivers. INTEL, AMD, NVIDIA etc reserves that for 6th Generation Core I3 I5 I7 and newer like the core I7 6800K. This too is never an option for 7010 aka broadwell processors or kaby lake or coffee lake etc.
https://www.dell.com/support/article/en-us/how13354/optiplex-7010-windows-10-driver-pack?lang=en
https://www.dell.com/support/article/en-us/sln297954/dell-computers-tested-for-windows-10-may-2020-update-and-previous-versions-of-windows-10?lang=en
speedstep
9 Legend
9 Legend
•
47K Posts
0
July 18th, 2020 03:00
UEFI v.2.3.1 BIOS requirement Windows 8 it’s optional with windows 10 it’s mandatory. This is not controlled or supported by DELL or any other OEM. Its MICROSOFT Secure Boot and COA keys are no longer a sticker but rather they are stored in UEFI BIOS along with the SECURE BOOT Certificates.
32 bit OS and drivers as well as Legacy MBR booting is no longer supported.
Secure boot requirements
In order to support Secure boot, you must provide the following.
YOU CANNOT RUN SECURE BOOT without UEFI Class 2.3.1 bios and hardware and certificates in BIOS. End users cannot install or update this from CLASS 1 Bios.
Variables must be set to SecureBoot=1 and SetupMode=0 with a signature database (EFI_IMAGE_SECURITY_DATABASE) necessary to boot the machine securely pre-provisioned, and including a PK that is set in a valid KEK database. For more information,
search for theSystem.Fundamentals.Firmware.
UEFISecureBoot system requirements in PDF download of the Windows Hardware Compatibility Program Specifications and Policies.
Signature Databases and Keys
Before the PC is deployed, you as the OEM store the Secure Boot databases on the PC. This includes the signature database (db), revoked signatures database (dbx), and Key Enrollment Key database (KEK). These databases are stored on the firmware nonvolatile RAM (NV-RAM) at manufacturing time.
The signature database (db) and the revoked signatures database (dbx) list the signers or image hashes of UEFI applications, operating system loaders (such as the Microsoft Operating System Loader, or Boot Manager), and UEFI drivers that can be loaded on the device. The revoked list contains items that are no longer trusted and may not be loaded. If an image hash is in both databases, the revoked signatures database (dbx) takes precedent.
The Key Enrollment Key database (KEK) is a separate database of signing keys that can be used to update the signature database and revoked signatures database. Microsoft requires a specified key to be included in the KEK database so that in the future Microsoft can add new operating systems to the signature database or add known bad images to the revoked signatures database.
After these databases have been added, and after final firmware validation and testing, the OEM locks the firmware from editing, except for updates that are signed with the correct key or updates by a physically present user who is using firmware menus, and then generates a platform key (PK).
The PK can be used to sign updates to the
KEK or to turn off Secure Boot.
savvy2
2.5K Posts
0
June 18th, 2019 06:00
what card is it? 12 makers and 100s of cards each, is card new, or used?
if the card has AuX power jacks did you connect them to the PCU cables 12v-PCI- marked?
what OS? W10-64bit? (if yes my guess was installed in legacy MBR mode) right? (yes moot point if BIOS screens dead sure)
7010 MT or other case? MT, DT, SFF, USFF ??????????? case size tells what MOBO is there,
Is BIOS newest.? (some DELLS even year 2011 made are UEFI sercure boot ready, for sure tuned up for w8 release,)
A29 is current, for sure.
For sure I can not speak for all version BIOS on ALL DELLS. ever.
all my dells have UEFI/LEGACY settings in F2 bios paged
yous said switched a 7010 to UEFI and secure boot, ( can guess that was done in F2 BIOS?)
many cards made back to 2014 are have bad BIOS, GOP mode or Dells zero support for GOP mode make the BIOS screens go dead. (back then they even had cards with a switch onto marked Legacy.. to get it to work on OEM PCs that do not support CSM or UEFI or do so and full of bugs. (history off)
if you card fails with F2 set to secure boot. that it was changed in F2 first. I can not see your a29 bios pages.
I have tested my GTX1650 card (new) on all my dells an it works, VOTAC model gaming tagged.
even on my old Dell 790MT
but we have seen on this forum MSI new cards failing just like this and is for bad GOP firmware in the dell.
again if card is w8 targeted card (years) make sure it has or does not have that Legacy switch (ask them)
power off pull AC plug from wall , push power button 3 times 1 sec, and PC is safe do not hot plug things inside)
Some folks (googling learn) you see the using HD iGPU to set bios then , put back the new GPU card.
yes clunky but does work. (or get 1 more GPU card, some do work
the UEFI is here and so is secureboot below there, for sure below. (watch the videos)
savvy2
2.5K Posts
0
June 18th, 2019 07:00
so you post this for vast Dells , (speedstep) over and over.
but not once do you disclose how you found the version of UEFI Class.
the only thing we see is the simbios , seen in msinfo32.exe screen. mine shows 2.6 there
why does dell keep all this UEFI stuff , like poker player,
even my old 790 boots UEFI secure boot, and all my GPU cards work in both Legacy and in UEFI mode.
the problem is some cards do fail we know that, all OEM websites report this, but not the top makers of mobo.
we all know that the old int15 video modes are gone now, but GOP address this issue.
the blame is hard, but if all cards fail in dells then the cards are not wrong it is DELLS bad GOP code.
we see some work though so.... (the cloud of blame is hard) if you read the specs and the makers of UEFI they beg OEMs to get this working, my guess it is not. Not so good.
speedstep
9 Legend
9 Legend
•
47K Posts
0
June 18th, 2019 09:00
INT 10 is MSDOS
UEFI CLASS 3 BIOS does not allow MBR or INT 10 or legacy booting of any kind.
7010 is NOT CLASS 2.3.1 UEFI BIOS and therefore SECURE BOOT IS NEVER AN OPTION.
savvy2
2.5K Posts
0
February 19th, 2020 04:00
why does your list contract this, non RED is 2.31
despite this old list, my 790MT UEFI secure boots and works with my brand new GTX1650 turing class GPU
same as my Dell 3020MT. works in real Secureboot, w10-64 mode and also works in legacy mode and both PCs (all are current version BIOS{UEFI} ))
both run BIOS F2 and F12 screens in ANY MODE.
But we do know some cards do not, but gee, vast cards made pre w8 to now, and many are buggy VBIOS and buggy , GOP code. we know that, the top 5 makers of cards say that, told to me.
Some top makers of cards like GIGaIBYTE even offer free VBIOS upgrades, so buy there cards?
we are not talking CLASS III UEFI PCs here why even go there (at zero legacy 2020 PC )
tigerwife
50 Posts
0
July 17th, 2020 13:00
so many fake information here.........
7010 can run UEFI with GTX1650 100% without problem.
SMBIOS 2.7 after latest bios upgrade.
3770, 32GB, GTX1650 on 250W TFX PSU, 100% without problem
Furmark test 100% loading 10 minutes NOT crash..
** When installation by USB.... DO NOT use the front pannel, then you will be a happy man.