Why if the modern replacement for BIOS is UEFI, we still call it BIOS?
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.
Older style computers which use boot code in the MBR are generally referred to as Legacy/CSM, the CSM meaning compatibility support module which is a component of the UEFI firmware that provides legacy BIOS compatibility by emulating a BIOS environment, allowing legacy operating systems. I have an HP laptop which doesn't have this option and I expect it will eventually disappear on new computers. Even with no Legacy option, my HP refers to it as "BIOS Setup Utility".
It makes me confuse with Legacy BIOS. Is any difference between BIOS and Legacy BIOS?
Thanks
The BIOS is a micro code program stored in read only memory. Typically software releases are given numbers. Every once in a while the marketing boys will give the next release a completely new name instead of an incremented number. They do this to make customers think that they are getting a radically new product. So instead of calling a new BIOS release BIOS-2.0 they called it UEFI. If UEFI hadn't been released until the summer of 2023 when Artificial Intelligence became a hot buzz word then the BIOS release name would have included Artificial Intelligence in its name.
Legacy BIOS refers to the BIOS release previous to the BIOS release called UEFI.
I have seen online resources which insist that a UEFI is not a BIOS (though it performs a similar task) and that terms like "UEFI BIOS" are oxymorons. On the other hand, the manual for my Lenovo Thinkcentre calls the UEFI the BIOS.
I suspect that a complicating factor is that a lot of non-technical users don't know the difference and think that BIOS just means "startup program". So they'd just be confused if the user manual called it something else.
The BIOS system has been around since 1975 when it was written by Kildall and first used on his CP/M systems and was developed to enable CP/M to be installed on different hardware without being modified. Several years later, IBM began using similar software on its personal computers. A major limitation of the BIOS is being unable to use drives larger than 2TB.
BIOS is bios, regardless of the type. Linux is still Linux and windows is still windows even though they both have been upgraded over time from 16 bit to 32 bit to 64 bit hardware the name did not change.
Just because legacy bios is no longer used (it had major limitations on the size of drives it supported, and architecture it supported) does not mean the newer UEFI bios (Unified Extensible Firmware Interface) is no longer bios. It is still bios (Basic Input Output System) (also known as the motherboard firmware) that performs the bootstrap functions to start the motherboard and attached devices, and to begin loading the kernel and OS.
Last edited by computersavvy; 11-24-2023 at 06:21 PM.
I thought that was a limitation in the partition table format fot MSDOS disks. If you used a GPT disk with a BIOS, wouldn't that get around it?
Yes, agreed. That has always been my understanding. Terms like BIOS, Legacy and even msdos are often used interchangeably and leads to confusion. Didn't bookmark the site where I read (misread?) that information and can't find it now to know which it was.
istr that in the very early days of PCs, DOS wasn't supposed to communicate with the disks directly. There would be this low level BIOS code to do it. And then, because BIOS existed, it was the obvious way to start up the machine by reading some kind of startup code from the drive before DOS was loaded.
Was that really so? I know Linux always accessed disks directly, but did DOS?
What we refer to as the BIOS was first created in 1975 and was designed to work on various hardware and was 5 years before DOS existed and was first used with CP/M. IBM used a modified version of it on its computers beginning in 1980/81.
DOS could not talk to the hardware when first powered on. Dos resided on the disk. The hardware had to be initialized by firmware (bios) on the board, including the drive, then dos could be loaded from the disk.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.