let me guess, you have some stupid autistic issue with it?
UEFI
Falling into your wing while paragliding is called 'gift wrapping' and turns you into a dirt torpedo pic.twitter.com/oQFKsVISkI
— Mental Videos (@MentalVids) March 15, 2023
let me guess, you have some stupid autistic issue with it?
Falling into your wing while paragliding is called 'gift wrapping' and turns you into a dirt torpedo pic.twitter.com/oQFKsVISkI
— Mental Videos (@MentalVids) March 15, 2023
if by stupid autistic issue you mean it obsoleted my software making many things unable to boot then yes i occasionally have a problem with UEFI
>Filtered by a BIOS change
Yeah, peak LULZ
This boards gets more pathetic everytime you open it
>calls UEFI a "BIOS"
>doesnt realize that not every UEFI implementation can boot legacy bios shit
>boot legacy bios shit
New good
Old better
by a BIOS change
it's not a "BIOS change" you retardo
It's funny because booting my custom shit is easier with UEFI.
Tell me what you can't boot gramps, I've updated all my software since 98's and everything is uefi compatible now
Filtered
UEFI is gay, anon
UEFI isn't gay, it's israeli.
>UEFI isn't gay, it's israeli.
let's agree it's both
most uefi interfaces look ugly as shit
What in the fuck
what's wrong, you don't configure your boot options from inside the star cube?
sovl in ten years
When do you think z87 and haswell came out bucko
>let me guess, you have some stupid autistic issue with it?
Actually yeah
>pic
>P8P67 Deluxe
My P8P67 non-Deluxe constantly forgets I have Linux installed and I can't fix it with much short of reinstalling GRUB from a live USB. My B350-F would constantly forget I don't have Ubuntu installed anymore and shit would stay there until a BIOS reset. Whatever, replacing it with an ASRock B550 soon. If they haven't figured this shit out by now I'll be fucking pissed..
SOVL I had a board that had one like this, but it was orange. Indeed it ran at native resolution, first and last that I know does this.
>4770K
LGA1150 was the age of manufacturer UEFI ricing. ASRock had a fucking sparkling background.
It has been ten years.
Pic related
>>My P8P67 non-Deluxe constantly forgets I have Linux installed and I can't fix it with much short of reinstalling GRUB from a live USB.
A solution would be to bot in bios mode and to disable uefi boot
No.
yes
>I can't fix it with much short of reinstalling GRUB from a live USB
lmao can't even use efibootmgr
You got filtered by the lowest level on your computer.
Fucking lmao.
Retards inside: That's so cool!
SOVL
unironically sovl
could you please point me out to me the problem your experience in with our interface sirs
>DRAM Voltage 1.488V
horrible input lag when using a mouse
I mean sure, there's a good few ms of mouse latency with UEFI, but with BIOS the mouse latency of BIOS is the decades waiting for UEFI to be invented, so it's not bad.
Phoenix uefi looks like the traditional bios and does basically the same things
AMI uefi is the flashy themable shit that all gaymer boards use and it is easy to unlock hidden shit in it
Insydeh2o uefi is chinkshit and is buggy as fuck, it also looks like phoenix uefi. If your pc uses it you bought trash
microsoft also made their own uefi with zero customization options for their tablets
AMI UEFI comes stock on huananzhi and other chinese boards, it's great. I'm sold on Chinese motherboards at this point, they check off the whole list for me
decent io
sane board layout
decentish VRM but nothing too autistic
RAM slots
the older ones even lack intelME so no glowy backdoor! How ironic
Maybe it's time to throw your old HP Elitebook in the trash
>guys you don't get it!
>UEFI will save us all! No more rootkits! It will be super secure, sleek and modern!
Meanwhile in reality, it's buggy, bloated, shit, and insecure just like BIOS. lmao
That's valid for Intel macs up to 2012-2013 which had firmwares based on EFI 1.x. Later models until the ARM macs have a saner UEFI because they dropped CSM support which was the basis for Bootcamp and Windows relies on the spec being followed, altough it still has its quricks like support for HFS+ and APFS and booting from them(because fagOS is special the bootloader is stored in /System/Library/CoreServices/boot.efi instead of the ESP which is only used for Bootcamp and firmware updates). Also the OSDEV wiki has a lot of outdated information and nobody is really bothering to start their toy OSes on real hardware.
seabios is all you need
https://www.coreboot.org/ Coreboot, my nigga.
coreboot can run uefi you dumb fuck
I know.
ok then why do you act as if coreboot project developed any sort of bios or uefi?
its ok
waddup fellow coreboot niggas
SOVL vs SOVLLESS
UEFI, or Unified Extensible Firmware Interface, is a complete abomination of a firmware solution. It's nothing but a convoluted mess of unintuitive and overly-complex technologies that are not only difficult to understand, but are prone to errors and malfunctions.
The worst part of UEFI is the sheer amount of incompatibility between different vendors and hardware configurations. This is compounded by the fact that UEFI is essentially a closed system, meaning that any modifications to the firmware must be done through the vendor's own proprietary tools, making it even more difficult for users to customize their systems.
Furthermore, UEFI has been found to be riddled with numerous security flaws that have been exploited by malicious actors in order to compromise systems. This fact alone should be enough to steer any user away from UEFI and towards more secure alternatives.
The bottom line is, UEFI is an unreliable, insecure, and overly-complicated firmware solution that should be avoided at all costs. Stick with tried and true open source firmware solutions such as coreboot or Libreboot, and you'll be much better off in the long run.
Thanks, ChatGPT.
BIOS is better for multibooting.
It's not really UEFI's fault, but choosing a partition from a list of those flagged "bootable" is way better than the shit show of every OS trying to be the one in charge of the EFI partition and fucking all the others up.
>BIOS is better for multibooting.
Not really. Especially with Windows loving to change bootsectors whenever it updates.
>but choosing a partition from a list of those flagged "bootable"
You're not choosing a partition flagged as bootable, you're choosing the harddrive you want to boot from. The marked shit is only valid if you have a DOS/Windows MBR, if you install GRUB it will ignore the bootable flag and do its own thing.
>OS trying to be the one in charge of the EFI partition and fucking all the others up.
No OS does this in dual boot scenarios, not even Windows. They'll assert themselves as the default sure, but they don't format the ESP allowing you to use the firmware as the bootselector or a bootloader like GRUB or rEFInd. Or you can have multiple ESPs, the only thing stopping this is buggy firmware.
>BIOS is better for multibooting
Why do retards say this? It is literally the exact opposite of truth.
You can select which OS on the hard drive to boot from the UEFI menu. You can't do that on plain BIOS.
My notebook is UEFI, but the menu it's looks like the left one.
Am I doing something wrong?
No, having a gui is optional with uefi
Some dont have any settings at all
why doesn't ARM have a standard bootloader?
The same argument as "Linux is not an Operating System is a kernel". ARM is a CPU architecture not a full computer. But x86 got lucky due to everyone and their mother cloning the IBM PC and making the BIOS the de facto standard and then UEFI when the UEFI consortium was born. But there are x86 computers that do not have a BIOS nor UEFI.
Altough ARM does have some a standard built around UEFI and ACPI. And Windows on ARM computers use UEFI for the boot process.
What? CSM doesn't lock you in in 16/32 bit mode you can boot 64-bit OSes with it. Altough you're wrong on another count, the BIOS uses 16 bits so you actually lose the upper 3/4s of your registers plus 8 full registers and another 8 MMX/SSE registers
UEFI is bad and all but in CSM mode you lose the upper half of your registers so fuck you I'm using it.
HP *facepalm*
oh shit
oh fuck
SIR DO NOT REBOOT
DO NOT REBOOT
SIR
DO NOT REBOOT
Blue Screen
It isn't exactly the most secure.
It's better than BIOS. Ideally though, there'd be no distinction between firmware and kernel. You could literally use Linux as your UEFI if it had the right code added to it, the spec doesn't preclude much, and I wouldn't be surprised if Intel or Microsoft were to add that code one day because they got sick of dealing with Chinese shitware.
>let me guess, you have some stupid autistic issue with it?
Let me start from the beginning:
1. Code
2. How to run code
Code at its atomic level is all but a codex provided by 80x86 in terms of 80x86 compatibly machines
You cannot run 80x86 on plain device, you first need an (O)perating (S)ystem, more specifically you need a (P)ortable (E)xecutable like file format
The (PE) is made up of DATA and CODE
DATA consists of:
o Headers
o Fields Sizes Addresses and Ordinals
o Import and Export tables
o Other stuff I am too basic to be familiar with
CODE consists of
BINARIES mostly in functional format, where upon copying them and jumping at the beginning of them you can in a sense provide arguments and make them do stuff
Finally booting, unlike a (P)ortable (E)xecutable the booting process should rather be as easy a loading a custom binary onto the system as little as even fewer than 512 bytes
(UEFI) Unified Russian Firmware Interface is everything but simple
Steps to boot from UEFI include:
o Download EFI or EFI2 or UEFI github project for windows whose apparent author appears to be a tranny company by the name of Tianocore
o After the download run the SETUP
o After the the SETUP run the BUILD
o After the BUILD run something I forgot what it is
o If you do not get a single error, you're the luckiest individual in the entire fucking world
o Finally locate the .lib files
o Create C/C++ EFI/UEFI entry point which appears to have multiple variations
o Include the library in various C/C++ fields in your IDE
o After wasting whole bunch of percentages of your life, build
o If the build is successful, which it should be if you closely synchronized your actions with ChatGPT
o You should have an actual file from which you can boot from
o Your UEFI only BIOS still won't be able to process it cause it is not signed by an authority certificate
Welcome to 2023, enjoy the good times
>Unified Russian Firmware Interface
>Russian
wew lad
I understood how bios worked, I don't understand uefi. therefore it's bad.
based
Capital Based
>I understood how bios worked
No you didn't. Nobody ever did. BIOS were full of unspecified behaviors, bugs and discrepancies between implementations. UEFI is still shit but at least it's unified and we don't have to write shitty pre-bootloaders anymore.
>bugs and discrepancies between implementations.
As if UEFI doesn't have these. From firmwares reject bootentries not named Windows or RHEL to buggy or downright broken functionality.
Some examples:
1. When you allocate memory(malloc or pages) you have to tag it, all fine and dandy until you actually use the tags that are available for OS loaders which will cause a lockup on buggy firmware.
2. Sometimes UEFI just fails to remove itself from control when you call ExitBootServices(yes, UEFI is so convoluted you have to ask nicely to give you control over the hardware) and you have to guess if it still in control or you can start messing with the hardware and page tables
3. EDID doesn't work on Nvidia GPUs so unless you implement drivers you're stuck at 1024x768(granted it's on the GPU maker to implement the firmware support)
4. The memory map it gives you its just awful to the point linux actually translates it to the format the BIOS used because it actually makes sense.
Even Linus hates it which says a lot.
>exitbootservices is bad
the alternative is shit
>nvidia gpus
don't make me laugh
>memory
you shouldn't be using a low level language
>even Linus hates it
well he's a filthy nocoder who got filtered by the kernel linux. There's nothing quite like GOP on BIOS.
>the alternative is shit
The alternative is so shit people don't parade like wow I can do X in the BIOS. Everyone knows the BIOS is so shit they don't attempt anything except load their shit and then take control. UEFI should have provided the minimum amount as well, instead its a whole fucking operating system masquerading as firmware.
>you shouldn't be using a low level language
We're talking about UEFI here you retard, you're locked in the low level languages, even Rustrannies have to deal with this shit.
>There's nothing quite like GOP on BIOS.
Wow a framebuffer that can be works the same way as VGA with VESA extensions(int 10h). Except you can actually return to legacy mode to change resolutions(Windows actually does this if you don't have GPU drivers and ask for a resolution change), once you exitbootservices in UEFI you're locked in to whatever resolution GOP was set to.
ill stick with coreboot
I just wish it wasn't so toyish looking. I don't want a colorful theme or backgrounds images.
>posting bait about BIOS vs UEFI
Seems like you're the autistic one, OP.
>b450 boards dont have enough memory for 3000/5000 series cpus
>msi circumvents this by making a bare-bones UI and removing all the graphical garbage
>reddit retards complain about it
>meanwhile it's a functionally better BIOS
Why do people love UI bloat?
Makes it look like the terminal user interface boogeyman when there's no animations bouncing around.
>2034
>using terminal without a keyboard
truly, gui is for noobs
>msi circumvents this by making a bare-bones UI and removing all the graphical garbage
post it, I want to see it
I wish my uefi would output to 1080p. It's always stretched no matter what I do. I even set the monitor to aspect and it's still full screen stretched.
That's the before and after
I've always used the "advanced" mode, fucking zoomers need to fuck off for crying over a gui
right looks clean and I'm in love with it but I've seen in on other msi prebuilds before
it's for lower end motherboards old am4 300/400 series motherboards after a bios update to hold more cpu microcode to have newer processors run. msi had to remove the fancy ui to add in microcode becasuse their flash chips were too small to hold both.
>cuck bios
No, thank you.
Why does it say Cuck Bios?
>I wish my uefi would output to 1080p.
UEFI does support EDID but it's up to the GPU maker to actually implement it properly in their firmware driver, otherwise it falls back to 1024x768(the minimum requirement). Nvidia doesn't, Intel does, I'm not sure about AMD.
>Nvidia doesn't, Intel does
My GTX 650 absolutely did output 1080 with that Gigabyte UEFI, the one from
but it had some overscan bullshit like a fucking early Raspberry Pi, because Fermi and Kepler cards always did that without drivers installed.
>not sure about AMD
Tried on ASUS B350, logo and Windows boot was seemingly 1080 but BIOS was still shit res. But the card in question was an R9 295x2, a fucking antique, maybe my 6700 XT will do better, the B350 shit the bed in the meantime and the newest board I have is from early 2011.
Interesting. MSI also had pic related for the turbopoorfag H61 motherboards.
>there are people this retarded and dedicated to the retardation.
Not sure if I should laugh or be scared. Get help anon.
>My GTX 650 absolutely did output 1080 with that Gigabyte UEFI
My 2060 does not so probably they broke something when newer cards were made, neither on my Asus Z97-P(which absolutely does output 1080p on the iGPU), nor on my Gigabyte X570 AORUS ELITE(inb4 back to LULZ).
AMI UEFI is also on most desktop motherboards.
because they have no taste. They've been gatekept their whole lives and probably haven't read a book in years.
If then a conspiracy theory that you are being deprived of all freedom over your computer.
Which is why we build our own.
bios really had the right idea about guis
Post your configs/dotfiles pls.
SOVL vs soulless
If you want sovl, try CSM boot. You're guaranteed to have a couple lost sovls possessing your computer.
do zoomers really call it UEFI instead of BIOS?
not sure if trolling
not trolling, for me it will always be called BIOS
how do you distinguish UEFI from actual BIOS
nu-BIOS and legacy-BIOS
I don't. its all the same to me
why are you on g
nigga it's all the same
>press del to get into the bios/ uefi or f8 to get into the boot menu
>set boot device
>enable virtualization
>disable lgbt lights
>set xmp or docp
done, it's just a means to an end and nothing more
Uefi just works. I dont need bios
Yes.
>Let's make everything so complicated so retards get a nice GUI instead of their lame BIOS
Wtaf
.._____
./
| () () |
. ^ /
..|||||
..|||||
. ._____
/ — —
|() — ()|
—^—/
.|||||
.|||||
its bloated
its insecure
but enough about me
. ._____
./ — —
|() — ()|
.—^—/
. |||||
. |||||
. . _____
./. — — .
| .() — () |
. — ^ — /
. . .| | | |
. . .| | | |
I know how to pronounce and spell BIOS while I’ve already forgotten the other thing while typing this.
oooooooooooofee
No, but you do have to realize, UEFI does not necessarily need to look like your pic on the right. UEFI is just a standard, but there are UEFI compatible computers with interfaces like you see on the left.
I prefer the legacy BIOS, since it has a saner layout of the settings. Enabling virtialization on an older BIOS is easier than on UEFI, since while the setting was placed on a sane place on the BIOS, i had to look up the name of the setting for UEFI
UEFI computers aren't real IBM-compatible PC's because they cant boot DOS anymore and thats very sad 🙁
I just dislike the dogshit zoomer UI, I switch to the traditional one whenever possible
I hate how it's pronounced
I've never used uefi and I've used computers since having an Atari. There's no need to larp as a EFI anything. So much so though that I've never ever learnt it.
why did they have to introduce this spyware shit. whyyyyy
bios 4 the win
UEFI = more features and control = better user experience = BAD
I HATE things that work well. We NEED to go back to having shitty software with fewer features and worse UI because it's like muh childhood computers.
this, I'm not happy unless I'm miserable