OpenBIOS: Open Source Your POST Process
I’ve run across this a few times and I have to admit, it makes me a bit nervous. Mind you, I’m always nervous about anything that can completely prevent me from making my hardware ever work again if something goes wrong!
The OpenBIOS project:
“…provides you with most free and open
source Open Firmware implementations available. Here you find several
implementations of IEEE 1275-1994 (Referred to as Open Firmware)
compliant firmware.“Among its features, Open Firmware provides an instruction set
independent device interface. This can be used to boot the operating
system from expansion cards without native initialization code.“It is Open Firmware’s goal to work on all common platforms,
like x86, AMD64, PowerPC, ARM, Sparc and Mips. With its flexible and
modular design, Open Firmware targets servers, workstations and
embedded systems, where a sane and unified firmware is a crucial design
goal and reduces porting efforts noticably”
One of these days, I am going to get over my whimpyness and give this a try. I had the same reservation when I did my first BIOS flash, my first firmware upgrade, and my first OpenWRT implementation. Now, it’s just second nature and I don’t think twice about it. And I’m sure this will become the same.
Does anyone out there have any experiences or stories about OpenBIOS that they would like to share? Put them in the comments.
If you found this post useful, why don't you buy me a cup of coffee to show your gratitude?
2 Responses to “OpenBIOS: Open Source Your POST Process”
-
miT Says:
March 13th, 2009 at 9:19 amI’ve ran across openBIOS a couple times as well, and just like you, i am very hesitant on doing something like this. I would love to hear from others that have successfully done this without any issues. Success stories would make me feel better about taking this kind of step
-
Vince Says:
March 13th, 2009 at 12:53 pmSeen this program/site/project, several times over last few years.
Of major note:
This group has same problem, most developmental sites have. It writes all processes and procedures as if you had all technical skills not to have need of them.
If you wish to try, any of the software, inclusive of non-destructive ’see how it might work’ downloads…
Be the originator of the project, or major project leader. Otherwise, you will find much of the technoblabology highly discouraging.
Keeping in mind, my lame computer experience only dates back to the late ’60s’and I ran Windows XP with NO successful Virus Attacks (Only problems I had with Windows XP were the ones from Microsoft and the ‘nut behind the wheel’) (programmed in absolute machine (binary), machine (octal) BAL (assembler) yada-yada-yada…
I prided myself on being able to write instructions so humans (lower form of geek without the hornrims) could read and understand. I used to read (and translate) Mil-Specs to comprehensible vernacular. (Dumbspeak)
Gave up on any hopes of using the linux-bios for now.
Unfortunately, this inability of most Unix/Linux software (that ability to write instructions based on good and simple language) is Rife throughout the Unix/Linux software sources.
Take my specific problem:
AMD-64 bit computers.
I read many ‘how to do (install, set-up, fix) anything’ instructions.
99% never start off saying “These instructions only work for old 32 bit computes, and I have not the foggiest of what I’m talking about when it deals with anything newer than 1999″
Example: There is a problem With AMD64 systems in Ubuntu (and other distros) where memory after 1.5 megs may not be recognized. (I have 4 Megs and am not using all because of problem - not much, but not all).
When checking out the Ubuntu Help page… Even the moderator was not answering the question, as if they knew of the problem. But the time I finished reading ‘That’ line of the blog…
I have been to 4 distros… all in technoblab and NONE answered the question in a manner that made simple the solution. (all referred to extremely technical vaporware, all trying to claim ‘firsties’ on who posted ‘first’, and nothing was ever put in any of the blogs…
SIMPLE
STRAIGHTFORWARD
INSTRUCTIONS
on how the hell to fix the problem…
(This is an example… Not the endall nor, anywhere near the only example…
LINUX Will not be Windows…
Nor will it gain wide acceptance, until
SIMPLE installs/solutions/instructions start to become the norm…
I read about a ’simple’ solution to installing ‘anything’ by using what, in Linux, may one day become the standard for installing rms/tar/deb/appnr(best one yet) packages… Oh the headaches from reading what they call difficult instructions.
WHY does LINUX use so many incompatible software loaders??
Why not simplify….
And easily beat the c**p out of Redmond?
One simple try at finding a specific AMD64 load and guideline, lead me to 10 links, and the probability of loading Native AMD64 RealPlayer 10 (does not exist - and Helix is NOT RealPlayer)
