Apart from factory reset in BIOS, you may try to disconnect power source and dismantle CMOS battery for a period of time, say 10mins (though it should be good enough for 30sec in most cases). Meanwhile, press and hold the power button several times in order to clear all possible recorded settings in BIOS. Then install CMOS battery, connect power source and power on your 5810 to see if any miracle happens. It once bring my T5600 back to life. Worth to try!
The bios does not have the drivers to display for some reason. Stick in a pre-made linux distro or windows disk then it will display after the OS loads up. For the time being you have to load windows or linux on another computer, then take it out and put it in the T5810. Still working on trying to solve the root issue, but for now I am loading linux mint without looking at a BIOS splash screen. I am blind as a bat until the OS loads up.
Hello, I had the same problem, my solution: Use an old low-resolution monitor 1366x768 I managed to view the Bios and Settings there I enabled the Legacy Room with which I was able to install Windows 10 21H2 LTSC since until that version of windows I had support my AMD GPU I could not install any new version of windows or it generated conflicts from Video Driver. I hope it will help you.
I had the exact same problem. I could get the DELL logo and Bios on the display (after bios reset).
BUT, after enabling the "Secure Boot" all went black.
I even changed the mainboard 2x.
I finally figured out that the issue came from the GPU card, that was incompatible with the "secure boot" option. If you wait long enough, windows will prompt.
me.myself.i
2 Intern
•
135 Posts
0
November 20th, 2020 18:00
Did you check in the BIOS that the PCIe slot that your GPU is in is selected as the Primary Video Slot? (this can be any onboard 16x slot)
It may have been reset to Auto, or some other non-matching slot.
bmcowboy
3 Apprentice
•
573 Posts
0
November 24th, 2020 10:00
"I was having problems entering the BIOS..."
"Did you check in the BIOS that... "
Interesting. How can one checking on BIOS settings without entering BIOS?
bmcowboy
3 Apprentice
•
573 Posts
0
November 24th, 2020 10:00
Hi @zheryt ,
Apart from factory reset in BIOS, you may try to disconnect power source and dismantle CMOS battery for a period of time, say 10mins (though it should be good enough for 30sec in most cases). Meanwhile, press and hold the power button several times in order to clear all possible recorded settings in BIOS. Then install CMOS battery, connect power source and power on your 5810 to see if any miracle happens. It once bring my T5600 back to life. Worth to try!
smorfnimda
1 Rookie
•
1 Message
0
September 14th, 2024 01:53
The bios does not have the drivers to display for some reason. Stick in a pre-made linux distro or windows disk then it will display after the OS loads up. For the time being you have to load windows or linux on another computer, then take it out and put it in the T5810. Still working on trying to solve the root issue, but for now I am loading linux mint without looking at a BIOS splash screen. I am blind as a bat until the OS loads up.
Mark86HN
1 Rookie
•
2 Posts
0
June 18th, 2025 12:48
Hello, I had the same problem, my solution: Use an old low-resolution monitor 1366x768 I managed to view the Bios and Settings there I enabled the Legacy Room with which I was able to install Windows 10 21H2 LTSC since until that version of windows I had support my AMD GPU I could not install any new version of windows or it generated conflicts from Video Driver. I hope it will help you.
Rockyenco
1 Rookie
•
7 Posts
0
February 11th, 2026 07:16
I had the exact same problem. I could get the DELL logo and Bios on the display (after bios reset).
BUT, after enabling the "Secure Boot" all went black.
I even changed the mainboard 2x.
I finally figured out that the issue came from the GPU card, that was incompatible with the "secure boot" option.
If you wait long enough, windows will prompt.
Rockyenco
1 Rookie
•
7 Posts
0
February 11th, 2026 07:55
Correction, it was in fact the "Enable Legacy Option ROMs" option that was causing it, but needed to be disabled to use secure boot....