Slashdot Mirror


BIOS' Days Are Numbered

Ninja Master Gara writes "While this article shows Phoenix expanding the uses of the bios, ZDNet UK reports Intel is looking to get rid of it altogether, to be replaced with the Extensible Firmware Interface (EFI) as announced at the Intel Developer Forum. EFI promises a considerable amount of flexibility to system control and startup, legacy support, and programability. And it gets rid of text mode only start up too."

9 of 502 comments (clear)

  1. Hardware OS's ? by vano2001 · · Score: 5, Interesting

    So will we finally be able to embed (part of) our favourite OS into the PC hardware? Remember the Amiga OS ... it had parts of its OS inside the ROM (intuition and other libraries (for graphics drawing and windowing)). A step forward... couple this with FlashCard RAM or otherwise.. and you can make some nice embedded systems. (Real NetPCs running linux with no CD/HD anyone?)

  2. OpenFirmware pls by jpt.d · · Score: 5, Insightful

    What else is there to say? OpenFirmware works nice

    --
    What we see depends on mainly what we look for. -- John Lubbock Now search for that bug slave!
  3. Anandtech has coverage as well by adpowers · · Score: 5, Informative

    Anandtech has a page about EFI as well. It also includes pictures of computers with EFI.

  4. Why not by bofkentucky · · Score: 5, Interesting

    OpenBoot, its an IEEE standard, Sun and Apple use it, its user programable, and cool as hell. Thankfully I rarely use it though, our (production) sun boxes have been nearly flawless since I started. Playing with it at Sun Sysadmin I class last week was one of the neatest things I've done in awhile on a PC. Do any of the other Unix (HPaq, SGI, IBM) vendors use OpenBoot?

    --
    09f911029d74e35bd84156c5635688c0
  5. Re:Gets rid of text-mode startup? by gwernol · · Score: 5, Insightful

    Machines that give you a graphical startup are annoying because you don't see the POST test etc, and if you're messing about with the hardware that's a real nuisance; you're never sure what's gone wrong.

    Of course there is absolutely no reason why a graphical startup can't (perhaps optionally) display all the usual POST test messages. A good example of this is Mac OS X: by default you don't see the Open Firmware messages during startup but you can turn them on and get all the information you would expect.

    If you're not [a geek], just watch it scroll by and think about how cool it is in a Matrix sort of way. But don't cover it over with a manufacturer's logo and a Microsoft ad...

    Some text-mode BIOSes already do this. The issue is not text vs. graphics, its what features and options does your particular EFI or BIOS vendor give you.

    --
    Sailing over the event horizon
  6. Good ol' Intel by LesPaul75 · · Score: 5, Informative

    They aren't getting rid of BIOS, they are just making it bigger (and more bloated). Claiming that they are "getting rid of" the BIOS is just their way of hyping their new, lucky-special BIOS. I write BIOS code for a living [shudder] and I've seen EFI. A better name for it would be "C-BIOS" or something like that, because that's what it is: a BIOS written in C. They've packed a lot of things into it, which may or may not be useful, like networking and a GUI. They've been pushing EFI for a long time, and I don't think they've had much success. I guess that they'll just force it down everyone's throat by putting it on all of their own chipsets and hope everyone else will follow suit. Personally, as a BIOS d00d, I hope that they have about as much success with this as they did with Rambus. :)

  7. because by SHEENmaster · · Score: 5, Informative

    openfirmware is usable rather than pretty?
    because it proves that a firmware can be cooler without ASCII art or pain-in-the-arse GUI?

    OpenFirmware, for those who don't know, is a solution adopted by Sun, Apple, and other big names. A partition on the hard disk contains the firmware which can be accessed through certain key combos. You can then give it commands to boot certain partitions and other such shit; stuff I'd like in my peecee's BIOS.

    Check it out.

    --
    You can't judge a book by the way it wears its hair.
  8. Re:Text mode start up screens by Jucius+Maximus · · Score: 5, Interesting
    "Text mode start up screen are cool! I don't need fancy graphics just so that my graphics card can get it's early morning POST exercise."

    Who needs text OR graphics? My brother got a new Asus A7N8X Deluxe board for his birthday (along with a new Athlon XP and DDR RAM) and I was shocked to hear the bootup sequence results being SPOKEN out of the onboard sound card!

    You'd hear in a sort of female type voice that the bootup was complete and the OS was loading. How about that for advanced boot?

  9. From what I read, this is NOT the answer by WhaDaYaKnow · · Score: 5, Interesting

    First of all, I'll link to my post two days ago.

    Intel however, doesn't seem to quite understand the issue. I mean, EFI is partially stored on the hardrive?! Sounds to me they are making things more complex, instead of less.

    The quote " In effect, it's a tiny operating system in its own right," scares the shit out of me.

    And all this hype about graphics, I mean, come on. I wrote a boot loader in 64K that booted straight into true color, 800x600 graphics mode, including a compressable image. It's not a big deal. And of course "With the BIOS, that's limited to VGA or worse" is horseshit, the BIOS can use the VESA BIOS to switch to any mode it desires. This is all a non-issue. It's been solved.

    Yes, network diagnostics is good. But I'd rather have a secure network boot, because then I can do anything, including loading a remote OS even though the harddrive shat on itself.

    The BIOS is the last place on the PC where people have to write in low-level assembler code, and we want to end that" he said. Instead, EFI is almost entirely written in C,

    Bullshit, there are BIOSs that are written in C. Actually, my bootloader is written in C++. There.

    so if your OS freezes you can go in and look at the state of the machine, change configuration, load a different driver, and do a sensible restart

    Yeah right, I can totally see my mom do that. I've spent hours trying to get Windows XP Embedded to NOT probe a secondary IDE channel because it was not terminated correctly and would hang the boot, using the kernel debugger and all. Never got it to work. And this is going to all work just like that?

    Finally, it can pretend to be a BIOS. "We're not expecting people to throw out the BIOS overnight, so EFI can support legacy systems by running on top of an existing BIOS and handing over control when appropriate."

    Ah! I was wondering where that backwards compatibility was. I'm so happy that we are moving one step forwards and two steps back.

    Yep, this probably sounds a flamebait, a silly rant, whatever. There's some good ideas there, but I don't think they are on the right track...

    At the end of the day, the BIOS (boot loader) should be in Flash (ROM) so that it still works even if there's no harddrive. It should get the hell done with all hardware initialization and boot the frigin OS. Putting more complexity in the BIOS means more bugs, means more updates, means more security risks.