BIOS' Days Are Numbered 513
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."
No more? (Score:2, Funny)
No more bios? Might as well cancel my cable, Biography was one of the only good shoes on A&E.
great... (Score:2)
because (Score:5, Informative)
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. [openfirmware.org]
Re:because (Score:4, Informative)
But yeah, it's cool.
Re:because (Score:2)
And yeah, I agree OpenFirmware kicks butt. Netbooting never was easier :)
Re:because (Score:2)
Yes, they do, and have done so ever since they invented Open Boot, which was the basis for OpenFirmware.
Re:because (Score:3, Interesting)
-lee
Re:because (Score:5, Insightful)
Re:because (Score:4, Informative)
You can diagnose hardware errors with it, you can boot off the network with it, you can specify which device you want to boot from, (on multi proc systems, you can specify which CPU will be the 'boot strap' cpu), and you can tell it if you want it to boot at all (if you want it to come up to just the eeprom after a power cycle.)
It's all sorts of goodness. I can't tell you how many times it's saved the day on our sun boxen. And for the hyper masochistic, there's a full blown forth interpreter.
And get this: It doesn't suck. (though it does generally mean something is sucking wind when you are working at that level).
Text mode start up screens (Score:3, Interesting)
Why do we need to glorify the start-up screen when text can do just fine... If I wanted glorified startup screens I'd boot up my AIX RS/6000 thank you very much.
Re:Text mode start up screens (Score:3, Insightful)
The problem with PCs is that they are generally consumer-servicable and are designed so that you can plug all kinds of hardware into it. This calls for an extensive and reliable startup code that can tell you something more than you could deduct from the fact your OS is not booting. I know my computer is Compaq/HP/IBM, I'd appreciate something else than a purrty BIOS logo.
Re:Text mode start up screens - Alien! (Score:4, Interesting)
And another thing - what's to stop MS "embracing" a few MB makers and converting the boards to boot only one OS - say, for example, Windows? It would be trivial to add proprietary code to this, which prevented anything else booting - obviously then anyone adding the required code to boot, say, anything else would be violating our favourite law...
Re:Text mode start up screens (Score:3, Funny)
ah? why? rs/6000 plays Thus Speak Zarathustra at startup?
Re:Text mode start up screens (Score:3, Funny)
*I used to think ppl that got giddy on ascii pr0n back in the bbs days were *WEIRD*
Re:Text mode start up screens (Score:5, Interesting)
Who needs text OR graphics? My brother got a new Asus A7N8X Deluxe [asus.com] 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?
Re:Text mode start up screens (Score:2, Informative)
I have that board... nixed the voice after only a day or two. It's very annoying (and really bad sound quality). And they did it wrong... it shouldn't say anything if the post went fine... it should only talk if there was a problem, saying what the problem was.
Oh, and one major beef I have with this board already: it doesn't have SMART monitoring for the harddrives!!! At least I haven't been able to find any sign of it and my email to tech support went ignored.
Re:Text mode start up screens (Score:4, Interesting)
This turned out to be BAD magic. See, my dad got into the BIOS by accident one day (they left lots of papers and other junk on the keyboard) and thought it was some kind of new Windows screen he hadn't seen before. Well, he knew he had to enter a password to get to the Internet, so he clicked that little "password" icon and entered a password... and that didn't work, so he did it again with a different password. He repeated that several times (not remembering the LAST password he typed), then gave up by selecting "quit". Computer rebooted and asked him for a password, which he didn't remember.
I was never able to get that board to boot again. Couldn't find the password recovery, it didn't have a jumper to clear the settings and pulling the battery for a day didn't help.
My opinion since then is that BIOS level setup screens SHOULD look scary to novice users!
Re:Text mode start up screens (Score:3, Informative)
Re:Text mode start up screens (Score:5, Insightful)
By the way, ever seen the blank stare on an average computer user's face when you tell them "Oh, you can fix that in the BIOS, just hit the F2 key once you hear the POST beep, use the tab and +/- keys to navigate around and set the AGP aperature setting to 64MB, then hit F10 to Save and Exit." - yea, we can do better than this.
We can't (Score:2, Funny)
Yeah get rid of BIOS (Score:4, Insightful)
Re:Yeah get rid of BIOS (Score:2, Interesting)
Another function of BIOS was (and still is) to give the chance to configure some hardware CMOS parameters. Again, DOS was not able to do that. With Linux kernel you have NVRAM driver, which can change most of such parameters right from OS. I don't know any parameters, which either today or in near future would be unable to be set from a NVRAM driver of the OS kernel.
The main reason of changing those parameters was inflexibility. But today nonody will set IDE disk parameters - instead they used AUTO. Same for many other things. Although, some of CMOS might not be automatically tuned up, I am not sure.
The last (from what I can recall right now) reason to still use BIOS is to point to the boot device. Perhaps that the function that will survive longer than other. At least that's the on;y function I still use in Apple's firmware :)
Re:Yeah get rid of BIOS (Score:2, Informative)
Re:Yeah get rid of BIOS (Score:5, Informative)
Billy boy didn't write the original DOS code, so it was not an issue of him "not being smart enough".
Those days it was done for performance.
No, the high performance calls skipped the bios. Back then the bios was mainly useful because many of the clones could be BIOS compatable with the PC thereby making getting a version of DOS to work properly on it was much easier. However, if you wanted performance, you'd call the
Another function of BIOS was (and still is) to give the chance to configure some hardware CMOS parameters.
Not back then. There were no cmos parameters back in the DOS days. Heck, pc's didn't even have battery backed clocks until much later. Hard disks were an expensive luxury and you had to run utility apps straight from the controller's ROM to do things like low level formatting.
Re:Yeah get rid of BIOS (Score:4, Informative)
Regardless of what you want to call it, something has to handle the hardware until the OS can get enough information to intelligently start itself up. That means rudimentary disk I/O (int 13h), video I/O (int 10h), and so on.
Re:Yeah get rid of BIOS (Score:3, Interesting)
BIOS provides an important feature: hardware abstraction.
Originally, the BIOS provided the same functionality that is now provided by the manufacturers on a floppy disk/CD. The BIOS contained the drivers for the hardware.
How many times do we see questions about the timeframe for Linux drivers for new hardware, or complaints about the inability to write a driver because a manufacturer won't release detailed specs?
If we returned to a BIOS like arrangement, then we would be able to install the OS's of our choice without having to write hardware drivers specific to those OS's.
I say we need more BIOS, not less. We need to come up with a new spec that brings the BIOS up to date, and takes the new kinds of devices into account (sound cards, superduper video cards, etc.).
And just to take it one step further, devices that connect via the various new bus structures (USB, Firewire, etc.) should be able to yield a driver on demand by the host. That driver should be in some virtual machine format that can be JIT compiled/interpreted by the host.
Re:Yeah get rid of BIOS (Score:4, Informative)
Hardware OS's ? (Score:5, Interesting)
Re:Hardware OS's ? (Score:3, Informative)
I remember reading about some people who were doing 3 second Linux-rom boots on PCs by replacing the BIOS ROM within the last couple years. I can't seem to find them via google, though...
It is an intriguing idea. Linux NetPCs are already done. I want a fast ROM boot.
Linux BIOS (Score:4, Funny)
3 second Linux-rom boots on PCs by replacing the BIOS ROM ... I can't seem to find them via google, though
Have you tried just putting Linux and BIOS into a Google query [google.com]? First two results: The LinuxBIOS Home Page [lanl.gov] and Slashdot | Linux BIOS [slashdot.org].
OpenFirmware pls (Score:5, Insightful)
Re:OpenFirmware pls (Score:3, Interesting)
Or they might get it right the first time. Or they might use something that already works. I'm not optimistic though.
Goodbye BIOS as well as.. (Score:3, Funny)
Goodbye floppy drive.
Re:Goodbye BIOS as well as.. (Score:3, Insightful)
Several devices will battle it out. (Score:3, Interesting)
The point is that the only reason floppies are still around is that so many of us "old folk" are comfortable with them. There is better technology available! You can boot from CD, or even from USB dongles if you need to. (Maybe we could market a l33t h@x0r pw reset USB dongle...)
Let it go.. We let go of the 8-track (most of us any way), we let go of our Commodore 64s, our Apple IIs, the 5.25" Drive. It's time to let go of the venerable 3.5" and make room for new and better solutions.
If there's something that you can do with a floppy that you can't do with SD/MMC, CDR/RW, or a USB dongle, speak up, I'd love to hear it!
Re:Goodbye BIOS as well as.. (Score:2)
um...
boycott them. Or something.
Anandtech has coverage as well (Score:5, Informative)
Stricter Enforcement for DRM (Score:3, Insightful)
Re:Stricter Enforcement for DRM (Score:2)
> BIOS'. In fact right now bios' can block/permit
> writting to the boot sector of a hard disk.
Care to explain how?
Just another thing to blame... (Score:2)
Gets rid of text-mode startup? (Score:4, 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.
If you're a geek, you definitely want the boot information. If you're not, 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...
Re:Gets rid of text-mode startup? (Score:2)
You can really tell the difference between a piece of junk HP, and a generic MoBo when you fire a machine up. With an HP, they don't even trust a user to not press F10 to enter setup, so they don't tell the user how to access it. GRRRR!
The new feature of giving the system's vital statistics is cool too. You can see if your fans are running, and your system temperature after rebooting, just before the OS starts to load.
Re:Gets rid of text-mode startup? (Score:4, Insightful)
Re:Gets rid of text-mode startup? (Score:2, Insightful)
And, just like replacing a line printer with an inkjet printer, it's a much slower, lower quality, harder to read, and more expensive way to do exactly the same thing.
GO INTeL!
Re:Gets rid of text-mode startup? (Score:2)
And I don't know what you're booting up with, but nothing about my bios or hardware information reminds me in the LEAST of the Matrix. Do you drive through canyons with your folks on vacations and pretend you're flying in the canyons of the death star?
Re:Gets rid of text-mode startup? (Score:4, Funny)
Yeah, and I wear my Darth Vader helmet over my acne-pocked face, and rasp out threats in an impossibly high-pitched "James Earl Jones" voice.
Re:Gets rid of text-mode startup? (Score:2)
Re:Gets rid of text-mode startup? (Score:2)
Re:Gets rid of text-mode startup? (Score:5, Insightful)
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.
Re:Gets rid of text-mode startup? (Score:3, Informative)
If you see "boot-command 0 bootr", then 'sudo nvram boot-command=0 bootr -v"' should work for you.
Re:Gets rid of text-mode startup? (Score:2, Insightful)
Now I'm only assuming that this new standard they're inventing will have some sort of debugging mode, or else it really won't fly. Quick, Eye-candy laden startups would be nice too.
The thing about it is, I totally expected a post like this. Sure, mod me down as a troll, but this is what happens when the slashdot crowd gets whiff of a new standard in the PC market. Below I have exampled this effect of "reverse luddite-ism".
Dell shipping with no more floppy discs? Oh no! whatever will we do? How about a bootable cd? Seriously. I haven't used my floppy in ages. They're unreliable, slow, and have a tendency to destroy an important term paper that's on it. Good riddance.
Whaaaaaaat?!! Office XP is going to FORCE me to register?!! Why I never! Yes, they ask you what country you live in. If you're not pirating your copy of Office, this ain't no big deal.
Poo-poo to this EFI. I'll never use it! I need diagnostic info! I like text! Besides, Microsoft will hijack it somehow! Like I said before, it won't become a standard unless you CAN use it for diagnostic information. AND, since we're talking about a new standard here, maybe it will cure a lot of the problems that you might need BIOS to debug!
PS - half of my post was funny. The other half is true. Mod accordingly.
Re:Gets rid of text-mode startup? (Score:2)
I'd like to see a BIOS-replacement that actually provided some information and used good resolution (my monitor has the resolution to display everything the BIOS and Linux during startup produce in a readable font, all on the screen at once; but not in text mode) and could use pictures (memory bank 3 is dead-- here's a photo of the motherboard showing which one that is...).
Re:Gets rid of text-mode startup? (Score:3, Interesting)
I *hope* that's what the LAN access will achieve, and that we won't be left with a shitty, sit-in-the-machine-room experience with more colours.
Also, the LAN stuff, while potentially cool, could also be a pain in the arse from a security point of view. WOL has cause conniptions for come people in the past, and that's very simple indeed.
Why not (Score:5, Interesting)
Re:Why not (Score:2)
#s/PC/box/g
#less beer
Re:Why not (Score:3, Interesting)
Re:Why not (Score:4, Interesting)
Heck, it's even possible to 'mount' a file system, and use a line editor to fix things (granted, it's easier to boot single user, and go from there, but again, if things are really FUBAR'ed...)
SGI uses an ARCS PROM (Score:2)
Open Firmware URL (Score:2, Informative)
Startup Screens (Score:3, Funny)
EFI? (Score:2)
It's about time. (Score:5, Funny)
I've never understood boot-ups. (Score:2)
Either way, Instant ON is way overdue.
Yo Grark
Canadian Bred with American Buttering.
Uh Oh! (Score:5, Interesting)
I'm guessing Microsoft is already adding code to windows to wipe out that last part from machines, as it might "confuse people"...
Honestly, this sounds very much like they're replacing the BIOS with something that works very much like a BIOS, but prettier...
Re:Uh Oh! (Score:2)
So, if EFI lives on the hard disk, how does the boot code get from the hard drive to the memory and into the CPU? Sounds like Intel needs to invent a bootloader for EFI. Since it deals with such basic tasks, they could call it the Basic Input Output System.
oh, wait...
Re:Uh Oh! (Score:4, Interesting)
EFI is firmware; from the moment you switch on your machine EFI is in control of it. You can quite optionally have EFI Applications that are stored on a non-volatile storage area (probably a hard disk) in a modified FAT partition. Seeing as you wanted to know, these are in Microsoft Portable Executable format, which is a form of COFF. But you can easily develop them under (ELF based) linux with gnu-efi. It's just like a normal C program, you can allocate memory etc etc. Elilo is the EFI boot loader and it works pretty much like lilo.
You can even have EFI drivers that extended EFI to do other cool things.
In essence, it's like having DOS built right in.
Re:Uh Oh! (Score:3, Insightful)
A better BIOS would solve this by getting a much clearer idea of what sort of hardware is in the system and what can be done with it. Got a USB hard drive you want to boot from? No problem: EFI knows how to read USB disks, so it grabs the files it needs and boots from it. Want to boot from your second CD drive instead of your first? Just pick "cdrom1" instead of "cdrom0" and you're all set. Want to boot over the network, but don't have DHCP? Set your NIC's IP address in EFI and tell it where to grab the boot image from using TFTP.
And then there's the nifty trick Suns have of being able to interrupt the operating system, no matter what, and drop you back into the "BIOS." I'm told there's even a debugger in there that you can use to debug the same system you're using (in case of kernel traps and such).
A more flexible, versatile, and powerful BIOS is a very cool thing, and even everyday desktop users will be aware of its benefits (though they may not know the source of them). People who use PCs for serious work have lusted after this sort of thing for a long time.
Don't get me started (Score:2)
I still don't pretend to understand all of it, but what bothered me was that I used to go to these Toronto computer shows and there would be these little books for sale on the BIOS, 4 of them, consisting of 5 pages of 8 x 10 photocopies folded over and stapled in the middle with a cheap colour cover on them. In other words, cheapest possible production values.
They went into detail on the BIOS and were EXACTLY what I needed, but the guy wanted twenty five bucks EACH for them.
I wouldn't have bought them even if I could, but I swore one day I would and publish them for free all over the BBS world (This was pre-Internet)
Now it looks like I won't have to, but I'm still pissed off. Charging a fortune for stuff people really needed is wrong.
no, wrong direction (Score:5, Insightful)
"Normal" home users, the kinds of people who might benefit from a GUI, probably don't want to talk to anything other than their main, mainstream OS. And power users and network administrators want the hardware to come with a system that can be scripted, extended, and remotely controlled. And almost everything that needs to be done with the BIOS-replacement should be done from the regular OS, which can leave little scripts in non-volatile areas for what the BIOS-replacement should do when it reboots (as opposed to putting those instructions into the user's brain).
Yes, the BIOS needs a serious overhaul, and, yes, it needs to change a bit in the direction of becoming a better OS. But it should become a better OS that normal users never have to talk to directly. It should become a 32bit/64bit OS that much more than previously accomplishes its magic behind the scenes. If it needs a GUI at all, the GUI should probably consist of a web server (so that the BIOS can be configured over the net) and a built-in, simple web browser, not some Microsoft-wannabe-lookalike.
Re:no, wrong direction (Score:2)
You want it easy for Joe-Six-Pack? Fine. Don't lock out the sysadmins and techs that have to support 18K+ desktops. The single most fustrating thing about Microfsck products is their inabillity to scale to large enviroments. That, and they are so bad they don't even suck.
And that's really bad.
It's about time (Score:2)
It's kind of annoying still seeing things like standard x86 startup screens.
It seems like intel has been on a rampage of reform lately. With the Intanium2 (in hopes of getting rid of the ancient x86 chipset architecture), the Centrino (to give laptops better battery life), and now this bios change.
Good ol' Intel (Score:5, Informative)
Hi-res splash screen! (Score:2, Funny)
This indicates just how desperate the industry is to keep the market from saturating.
Why? (Score:2, Interesting)
If it can actually help when having system problems...but aside from that, would there really be any reason to switch to EFI? Wouldn't it be creating more overhead? I mean, it seems like it would be doing more than a BIOS normally would,a nd run it next to an OS will there be any performance hits?
SGI did this with PCs in 1998... (Score:2)
Re:SGI did this with PCs in 1998... (Score:2)
No, I think it's best to leave the OS' on the disk, and only the code that's motherboard specific on the motherboard - it just doesn't make sense to mix the two in a PC.
What if the hard drive fails? (Score:2, Interesting)
EFI? (Score:3, Funny)
.
It just not the same. (Score:2)
Grammar (Score:2)
Complexity (Score:2, Insightful)
More specifically... (Score:3, Funny)
All days are numbered, but bios is done in binary.
(It's a vague attempt a humour... laugh.)
Whither OpenFirmware? (Score:5, Interesting)
Like a lot of people here, I've been wondering why Intel is trying to reinvent the wheel when OpenBoot is both flexible and reliable. It's a little intimidating for Forth newbies (like myself), but I've never had a problem with any of the Sun or Apple boxen that use OF.
The motivation behind EFI is probably simple economics. Intel has effectively maximized their revenue from CPUs. This forces them to branch into other markets to keep the profits growing and the stockholders happy. By improving on the BIOS they make a more compelling case for Intel chipsets, especially in the highly profitable server arena.
OpenFirmware is an open standard, so other chipset vendors could implement their own OF solutions without ever paying a dime to Intel. EFI is probably patent encumbered and represents a nice opportunity to collect fat license checks from companies like VIA and ServerWorks. Also, MS has demonstrated how profitable controlling a platform can be. Intel's probably trying to extend their strong processor position so that they have more control over your computer. OF is, well, open. That makes it kind of suck as a monopoly extension tool.
That's what I've come up with, anyways. If anyone's got a better theory please share.
here's a solution... (Score:2)
2) Make it post so damn fast that nobody even notices
Avast Matey. Prepare to be boarded! (Score:2)
So basically what we have here is combined BIOS/Boot track that Turbo Tax has explicit *permission* to write to, but perhaps you don't?
Oh, gee, goody. Just what I had asked Santa for.
KFG
From what I read, this is NOT the answer (Score:5, Interesting)
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.
VGA text mode is a waste of circuitry (Score:3, Interesting)
Re:VGA text mode is a waste of circuitry (Score:3, Interesting)
Legacy is a bitch, isn't it?
Seriously, unless there is a sane and universally accepted standard out there that can replace VGA/VESA it has to stay. Too much use it for it to be removed - like the BIOS, boot-loaders, MS-DOS and Linux in text mode. I do not want to wait for the OS to load the correct video driver before the machine is able to display something. There are way too many SNAFUs that can happen before a video driver can be loaded, and if that happens the PC is toast unless the BIOS has proper support for a serial console or boot control over the network.
Does the VGA requirement hold back the development of new graphics chips? I would assume that it is a well understood problem that can be implemented in a small separate space and doesn't impact the design of the rest of the chip. If that is an incorrect assumption, please explain.
Yes, it is a legacy annoyance. Yes, it would be great if we could replace it with something better.
The BIOS is the device driver for the motherboard (Score:3, Interesting)
The reason why BIOS exists as it does today is because motherboard manufacturers wanted to add features that the major OS's were not supporting. For example, system sleep on laptops running Windows NT. NT doesn't support that, so the BIOS was updated to do the work "under the covers". Another example is USB keyboard support. In order to have your USB keyboard work in DOS or any other legacy OS, the BIOS has a USB driver built-in that translates USB keyboard events to PS/2 keyboard commands. The OS has no idea what's going on.
All of this could have been avoided if BIOS developers weren't so goddamn lazy. I used to be one, and my co-workers were experts at hacking up the BIOS code so that it would just barely work for whatever new feature they needed to add. The last thing they were going to do is redesign anything so that it made sense. Half of the code hadn't been touched in 10 years, and there was no one left who understand it anyway.
I hear Dell is planning on laying off all their BIOS developers and moving everything to China. I can't wait until some huge customer calls because they have some obscure hardware from the 90's that won't work in their Itanium box, and the problem won't get fixed because they don't have anyone left who knows what they're doing.
Who are they kidding? (Score:4, Interesting)
How long did it take to put the ISA bus to bed after PCI came out? Ten years?
I'd love to see the BIOS go away as much as anyone, but I just don't see this happening in a reasonable amount of time. It's just too firmly entrenched in every PC, add-in card, and software doo-dad to easily do away with. And I don't care how good the "legacy" support is, I'm sure it will not work more frequently than it does work.
Then again, I am a cynic, although you'd never know it.
About time (Score:3, Insightful)
SGI has been doing this right for years. Their PROM is network aware, can run basic diagnostics, uses a gui and just looks damn cool.
Much better to see "Welcome to Octane" than Beep Chuga Chuga.... Post complete Memtest and other garbage.
Lets just hope the process remains open enough to allow Open Code.
Misleading statement about no text-only (Score:5, Informative)
I beleive the statement about getting rid of text-mode-only startup is incorrect. I've used EFI extensively in systems that don't even have a graphics card installed, and it works just fine over a serial console.
EFI is like a little mini-OS that serves mainly as a boot loader environment, but can also be used for running simple batch scripts and executables. System configuration utilities, OS installers, and diagnostic programs are all good candidates to build as EFI executables. For example, "elilo" is a Linux boot loader built as an EFI executable. To me, EFI seems more like MS-DOS than anything else.
EFI has modular drivers, so you can support different boot devices, network stacks, etc., and use them for pre-OS-boot tasks such as installation, configuration, etc.
Since EFI can mount (some) filesystems, and the booted OS can subsequently mount the same filesystem, an EFI partition is a useful place. For example, when you build a new linux kernel, you just copy it into the mounted EFI partition, modify the elilo.conf file (also in this partition), and the next boot will boot from the new file. No more scribbling to boot records.
Same thing, different names (Score:5, Informative)
OpenBoot/OpenFirmware has had similar abilities for some time. Your CPU boots up a Forth interpreter, which then goes looking for programs to run. Expansion cards are one place to look, so that video and network adaptors can be used before the OS loads.
This is important, so pay close attention. The interpreter will run Forth code found on an expansion card. This means that you can use the same card in a computer whose CPU is from Intel, MIPS, Alpha, etc. The initial code will define Forth subroutines that allow the bootstrap loader to use the card. For example, a video card will define subroutines for CURSES-like functions, the boot loader will then call those routines to interact with the user. It's written in an interpreted language, so it'll be slow, but the OS won't have to use those routines, it will use drivers loaded from disk. On the other hand, the OS can use the Forth routines if it can't find a driver, allowing cards to be useful before you install the correct drivers.
It's a great idea whose time came over a decade ago. Too bad Intel and Phoenix never got on the bandwagon.
Re:bios? (Score:2, Insightful)
Re:bios? (Score:2, Funny)
Re:bios? (Score:3, Informative)
Re:making room for linux? (Score:2)
Re:Paladium (Score:5, Funny)
I tried to make sense of this sentence but my internal parser core dumped. Luckily my newly installed Phoenix Core Management Environment diagnosed the problem as a gramatically challenged sentence.
Re:Paladium (Score:2, Funny)
Does Phoenix will have (forced to?) have the paladium's required functions?
I see from this sentence that you're an avid follower of Douglas Adams' verb conjugations based on time travel. However, I believe that you should replace "will have" with "willen on-haven." That should make things much clearer for all of us.
kthxbye.
Re:Paladium (Score:4, Insightful)
In btw: nothing new here. This is the way all big Iron works. It starts enforcing licensing from firmware level so no way you can circumvent it.
So watch the words EFI. They are the words that will have to precede the words Palladium. Also do not even think about replacing the OS on such machine if the manufacturer has decided to disallow you to do so. And they very well can do this.