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."
In that case, how will be Paladium be implanted? Does Phoenix will have (forced to?) have the paladium's required functions?
by giving it some other fancy name! U need to have something between hardware and the OS. Call it whatever you want to call
Umm. Just because you don't see it doesn't mean it isn't there. OEMs like to have startup screens that disguise the text mode stuff going on invisibly...
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!
If BIOS isn't broken, one wonders why there needs to be a fix. One can pretty confidently assume that such a change would usher in stricter enforcement for DRM. And I'm sure it simply solidifies the work MS largely completed through its XP registration scheme. Perhaps I'm paranoid, but can any of you blame me?
Part of the hardcore faithful who believed in Apple long before it was cool again to do so
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...
Real Daleks don't climb stairs - they level the building.
The problem with graphics bootup is that if there is a hardware problem, you will see nothing. Displaying a text message like 'bus barfed' is trivial, handling a terrible, terrible problem in gfx mode, not so.
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.
What will replace the floppy drive? Granted, it's antique, and @#$ing slow, but what other method do you have to transfer small files easily between two computers, without the net? Granted, everything should just be net based, but what happens if your net connection goes down? Floppy drives are simple, easy to use, and widely available in PCs. Also, you can't monitor a floppy drive like you can emails ;)
" whats a bios? in all the newer computers ive seen that havent been built by the users, there is no bios."
Clearly you have no idea what you are talking about because all computers have a BIOS.
You ask "what's a bios" which indicates you don't know what it is and then you claim to know that there are computers without it ? How can you know that acomputer doesn't have a BIOS in it if you don't even know what a BIOS is to begin with?
"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.
I don't think it is smart to add complexity to a damn near hardwired system. If there is one of the "cool" bugs found in the bios replacement how would you ever be able to fix it? This sounds somewhat dangerous to me.
...And when they came for me, there was no one left to speak out for me." - Martin Niemoeller (1892-1984)
Sounds like Intel wants to reinvent the wheel. I hope they realize that Open Firmware exists. Or is it their version of embrace and extend?
Yes. This is to Open Firmware as USB 2.0 is to Firewire.
OpenFirmware does NOT live on the Hard Drive, it lives in Flash ROM so it's semi-permanent. Compaq tried putting a BIOS Setup program on a 'secret' partition on the old Deskpro 2/4/6XXX machines and it was a total hassle to fix them if the drive died or somrthing happened to the partition, you had to load the BIOS Setup from _DISKETTES_. It was cool to have a GUI Setup with full diagnostics, but when the drive died so did the convenience. Don't even get me started on upgrading hard disks on those things.
"Sometimes, I think Trent just needs a cup of hot chocolate and a blankie." -Tori Amos on Nine Inch Nails
It all sounds like a good idea, but "non-volatile" is the last thing I'd call anything that's stored on a hard disk. My BIOS is ugly, but scripties aren't playing around in my firmware. Right now the worst a virus can do is force you to blitz your drive and reinstall an OS. How'd you like the next Code Red to render machines completely unbootable, or perhaps even damage hardware? It sounds great, really, but don't put it on a hard disk. Also, It's been done, to a degree. Some laptops store BIOS settings on a hard disk, and it's a bitch when an OS upgrade braindeads it, or keeps it from suspending, etc...
SGI has its prom that is graphical, the machine boots to a menu: Start system, Install OS, Diagnostics, Restore System and Maintance mode. The first time I saw it a was shocker, 24bit color BIOS! and a nice chime, it is a graphics workstation. When you select Maintance mode, by clicking on it or pressing 5 it takes you to a console window that works verymuch like openfirmware. It boots to the same menu over serial just it is a text menu:
System Maintenance Menu
1) Start System
2) Install System Software
3) Run Diagnostics
4) Recover System
5) Enter Command Monitor
Option? 5
Command Monitor. Type "exit" to return to the menu.
>> hinv
System: IP22
Processor: 175 Mhz R4400, with FPU
Primary I-cache size: 16 Kbytes
Primary D-cache size: 16 Kbytes
Secondary cache size: 1024 Kbytes
Memory size: 32 Mbytes
Audio: Iris Audio Processor: version A2 revision 4.1.0
>> version
PROM Monitor SGI Version 5.3 Rev B10 R4X00/R5000 IP24 Feb 12, 1996 (BE)
>>
If PC's booted in 32bit mode it would sure make life easier. Nix the BIOS and replace it with a 32 or 64 bit interface like OpenFirmware or the SGI PROM.
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.
I'm Rick James with mod points biatch!
The current boot process sucks.
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.
Blogging because I can...
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.
EFI does allow you to format a partition of the hard drive in vfat (linuxspeak for fat32) so that it can recognize the files stored on it. Those files can be anything you want, and the partition may be mounted by the OS and treated as a regular partition. For example, the /boot partition of a Itanium II node that has SuSe SLES 8.1 installed on it looks like this:
drwxr--r-- 3 root root 4096 Dec 31 1969 . ..
drwxr-xr-x 23 root root 528 Feb 11 11:26
-rwxr--r-- 1 root root 503248 Jan 27 06:55 System.map-2.4.19-SMP
drwxr--r-- 4 root root 4096 Jan 27 07:51 efi
-rwxr--r-- 1 root root 1160383 Feb 10 21:00 initrd
-rwxr--r-- 1 root root 1156850 Feb 10 21:00 initrd.shipped
-rwxr--r-- 1 root root 2381696 Jan 27 12:55 vmlinuz
-rwxr--r-- 1 root root 72173 Jan 27 14:37 vmlinuz.autoconf.h
-rwxr--r-- 1 root root 39332 Jan 27 14:37 vmlinuz.config
-rwxr--r-- 1 root root 2381696 Feb 10 19:12 vmlinuz.shipped
-rwxr--r-- 1 root root 130 Jan 27 12:33 vmlinuz.version.h
When EFI boots up, it will look for fat32 or fat16(why bother?) partitions on any harddrives, cdroms, ls240's or any other local devices the MB manufacturer supports. It then offers you the opportunity to access these mounts just like you had good old dos onboard. Instead of assigning drive letters, you get FS0:, FS1:, etc.
Caveats:
The OEM who provides the MB and its EFI implementation has to provide the driver for the devices that EFI supports. So the manufacturer of an Intel Tiger 4 Chassis with built-in SCSI from MPT needs to obtain the EFI driver for the device from the manufacturer. Same thing for the IDE chips on board or the integrated NIC. If the EFI has the built-in driver in the rom, it can then use that device during boot. I don't know if a hardware driver for EFI can be loaded manually.
To live on the harddrive, EFI uses a new type of partition table, EFI GPT, to store partition information. fdisk doesn't like this, but parted works just fine for linux. I'm not sure how Windows deals with this.
Hope this helps. If you need to know how I know this, well let's just say that I have over 256 Tiger 4's in my linux cluster. :)
The Internet has no garbage collection