Slashdot Mirror


Stallman Calls For Action on Free BIOS

Dolda2000 writes "Seeking to achieve 100% software freedom, RMS is now calling for action for a free BIOS. From the article: "The most uncooperative company is Intel, which has started a sham 'open source' BIOS project. The software consists of all the unimportant parts of of a BIOS, minus the hard parts. It won't run, and doesn't bring us any closer to a BIOS that does. It is just a distraction. By contrast, AMD cooperates pretty well." For reference, there are currently two projects for a free BIOS that I know of: LinuxBIOS and OpenBIOS."

30 of 487 comments (clear)

  1. It makes sense by Anonymous Coward · · Score: 4, Insightful

    It makes sense, to me anyways, to have an open bios. How can one claim to run a free system when their very boot process is hidden and secretive?

    1. Re:It makes sense by Anonymous Coward · · Score: 5, Insightful

      Do you think your processor should contain open microcode as well? Even if you install free software on your mainboard BIOS, what about the firmware on your drives and graphics card?

      While a wholly open-source machine would be great, it won't be a reality until we have technology that breaks the electronics mass production bottleneck (perhaps nanoassemblers). In the mean time you just have to decide which companies you're prepared to trust.

    2. Re:It makes sense by Anonymous Coward · · Score: 5, Insightful

      free-software religion aside, there are serious practical considerations to having closed bios code.

      Bios support is an ongoing issue. Newer CPUs, RAM modules, hard drives, video cards are always coming out, as are bugs. With a closed source bios, support is cut after a certain length of time, and it is tough luck if any bios limitations exist after then. Oftentimes they don't address all the issues even while they're still making updates.

      How many people are stuck with a motherboard they can't put a hard drive into, or can't do this or that, or are being bitten by a bug because of the bios. This happens all the time.

      Also, bios setup screens are consistantly poorly designed, excessively limited, and written in "somebody set us up the bios" Engrish.

    3. Re:It makes sense by Anonymous Coward · · Score: 5, Insightful
      BSD style licenses allow me to get recognition (not much I haven't written a lot of Open Source) and allow me to re-use that software in my commercial projects, which benefits me and Open Source as it allows me to get buy-in from management.

      GPL licenses do not. Essentialy I write GPL software and I cannot use it in any commercial projects.

      First of all, thank you for any and all Free Software you have written, under any Free Software license, copyleft or not.

      Second, please don't conflate "commercial" and "proprietary"; many people make a living selling development of Free Software and support for Free Software, and confusing those two terms makes it more difficult for those people, just as you have encountered difficulty from managers that fear Free Software due to copyleft. Please have some sympathy for those people, and ensure that your statements do not undermine their use of GPLed software to make a living.

      Finally, note that if you write a piece of software, you hold the copyright on that software; you may release it under the GPL, and you may also use it in proprietary products. You are in no way restricted by the license on a piece of software wholly written by you. The GPL simply prevents others from taking your software and making it proprietary, and prevents you from taking other people's GPLed software proprietary.
    4. Re:It makes sense by pe1rxq · · Score: 3, Insightful

      Developers can make money writting open source to...

      As for the 'just for the sake of it' part:
      Imagine buying a new harddisk and finding that your bios doesn't support such large drives..
      What are you going to do? Beg the vendor of your closed source bios to make an update for a board they consider obsolete?
      If the bios was open you could add support yourself. (Or alternativly pay one of those starving developers to make the changes for you)

      Jeroen

      --
      Secure messaging: http://quickmsg.vreeken.net/
    5. Re:It makes sense by pe1rxq · · Score: 4, Insightful


      We as humanity have a finite amount of resources, which means that if I'm going to expend resources by writing software I need to get something in return, in order to provide for my family


      The problem is that we are using the end product as if it were a limited resource. It is not, we use special laws like copyright to limit it by force.
      The real limited resource here are programmers.
      With the right business model you can get paid for programming regardless which license the end result is released under.

      BSD style licenses allow me to get recognition (not much I haven't written a lot of Open Source) and allow me to re-use that software in my commercial projects, which benefits me and Open Source as it allows me to get buy-in from management.

      GPL licenses do not. Essentialy I write GPL software and I cannot use it in any commercial projects.


      BSD doesn't guarantee buy-in... management could simply take your code and release it under a non-free license. They might say 'thank you' if you are lucky.

      With GPL code you can guarantee buy in: they need to license it from you (asuming you are the sole copyright holder) under a different license than the GPL and you can dictate the payment terms.

      Jeroen

      --
      Secure messaging: http://quickmsg.vreeken.net/
    6. Re:It makes sense by Anonymous Coward · · Score: 4, Insightful
      Quote the foolish.....

      BSD style licenses allow me to get recognition (not much I haven't written a lot of Open Source) and allow me to re-use that software in my commercial projects, which benefits me and Open Source as it allows me to get buy-in from management.

      GPL licenses do not. Essentialy I write GPL software and I cannot use it in any commercial projects.


      Okay, it obvious from the quote above that you either:

      1) Are a Troll
      2) Are a Shill
      3) Don't understand the GPL

      When you write the software (as you stated above) you retain copyright to the software - then you are still the copyright holder. Thus even if you license it under the GPL you can turn around and license the same thing under the BSD, X, Mozilla, your own custom license, and anything else you so choose - YOU ARE THE STILL COPYRIGHT HOLDER.

      Thus when you take somebody else's hard work that they have put under the GPL - then you have to abide by their terms. However, that does not stop you from approaching them asking for a closed source license or "commercial" to their code. The reason they can do that is because THEY RETAIN COPYRIGHT TO THEIR CODE.

      Sorry to use caps/bold, but I really don't think the previous poster could understand these concepts without it. They have only be discussed several hundred times and still people seem to shift their keyboards into overdrive before their brains get out of neutral.
    7. Re:It makes sense by interiot · · Score: 3, Insightful
      One function of OSS is to ensure that the freedom available to programmers now is never diminished.

      Can the microcode can be used in a malevolent manner that exercises corporate control at the expense of the invidual? Companies have already threatened to do this with the BIOS (eg. DRM and such). Graphics firmware probably will never threaten the control over the general-purpose computing like the CPU bios can, but if it does, we can implement an OSS version at that point.

    8. Re:It makes sense by Aim+Here · · Score: 5, Insightful

      Re: the abc program - there is no compulsion for a user of GPLed software to distribute anything at all. You are allowed, for your own personal (or internal company) use, to glue proprietary and GPLed code together in any combination you see fit - the only restrictions are on distribution of the code.
      However if you plan to distribute someone else's GPLed code to any third parties, then all the code in there would have to be GPLed and the source code would have to be made available.

      If YOU wrote all of b and c, then things are easier. Just put your code out under multiple licenses. You can GPL b and c and put it on a website AND license the same code to your company under a proprietary license for use in 'abc' - some companies, like Trolltech, actually make a living by producing GPLed code, and selling proprietary software companies the right to make derivative works of the same software under non-GPLed terms.

      Hope this helps.

    9. Re:It makes sense by Unknown+Lamer · · Score: 4, Insightful

      Free Software is not Open Source. Do I want an Open Source system? Hell no! I want an entirely Free system from software down to the hardware! I use GNU/Linux because I support the idea of Free Software, not because it doesn't cost me money to use. In fact, it does cost me to not use non-Free software; some of it isn't as usable as the proprietary counterpart and may require me to work on the code itself to make it do what I need.

      But I have the freedom to modify the code if I want to. I'd like this with my firmware too. OpenBIOS is promising for the firmware replacement. The Open Graphics Card project is progressing and will finally give me a decent graphics card that is well supported and documented (I have a Radeon 9100; it is the last ATi card I will purchase since they to have gone down the path of not even providing specs to the DRI developers...so no more Matrox, ATi, nVidia, ...).

      The graphics card thing is a really good example of why we should demand Free Hardware. Unless you give up your Freedom and use proprietary drivers, you no longer can use a modern graphics card and get 3d acceleration under X. Printers are another good example; look at how many printers have no Ghostscript backend because the manufacturers refuse to provide specifications for their proprietary protocols. Specs are nice but open hardware documentation would be nicer since we could then e.g. reprogram the printer's firmware to support PostScript (or if it is too slow for that, something like PPA that we have decent drivers for).

      The Neuros has had its firmware and even full hardware specs released! Neuros Audio isn't going out of business; not even close to it. The hardware schematics release may not be immediately useful but the firmware release is; things are progressive with FLAC support and soon MPC, things that never would have happened if the firmware had remain non-free software. Look at Rockbox too. The Rockbox firmware is far superior to the stock firmware.

      Free Software needs to run on a system that is Free down to its lowest level. We live in a world now where everyone is trying to kill us with things like hardware-based Digital Restrictions Management. We must demand at the very least Free firmware for the hardware and good enough hardware interface specs to actually do something with the firmware (stuff like e.g. the Verilog for the ASIC doesn't matter so much when you have that, but it would be nice to have).

      --

      HAL 7000, fewer features than the HAL 9000, but just as homicidal!
  2. Liability problems? by bigtallmofo · · Score: 4, Insightful

    I can't really imagine a free piece of software that will undoubtedly render some people's motherboards totally unusable.

    Admittedly, not many people actually screw up their motherboards today because of company-supplied BIOS updates, but in my opinion the most likely reason for that is that most people don't update their motherboard's BIOS.

    I think this is a necessary problem to solve for a host of reasons (the most pressing in my mind being removing "Trusted Computing Initiatives" or DRM) but I can't imagine who might be willing to distribute such a thing because of the liability concerns.

    --
    I'm a big tall mofo.
    1. Re:Liability problems? by Max+Romantschuk · · Score: 4, Insightful

      A free (as in freedom) BIOS does not mandate that the motherboard manufacturer allows it's customers to tinker with it and still retain their warranty. But those who are willing to take the risk have the option, that's what freedom is all about.

      Take the Linksys WRT54G, it's Linux-based. Linksys gains from using the well tested Linux core, and the customers gain by having the option to hack it at will. Check out http://openwrt.org/ for an example of the positive results.

      Think of the BIOS as the ignition to your car. You can dismantle it if you wish, why should the PC's BIOS be any different?

      --
      .: Max Romantschuk :: http://max.romantschuk.fi/
  3. How would "cooperating"..... by bpuli · · Score: 4, Insightful

    to create "free" BIOS help Intel? Would gain market share? Would it somehow end up with a new revenue stream that it cannot access with its current marketing and other strategies? What can it gain by winning over a bunch of geeks?

    This is not flame bait. I am just trying to understand why corporations like Intel would cooperate.

    All I can say is stop whining and move on.

    --
    BP http://www.card-central.com
    1. Re:How would "cooperating"..... by FrostedWheat · · Score: 3, Insightful

      For all the effort it would take them! All that have to do is release some documents. Even if they charged a small and fair fee to cover the costs of someone finding it and giving it a quick review before releasing it.

      In short, if done correctly it would cost them nothing and give them a bit more credibility.

    2. Re:How would "cooperating"..... by thejam · · Score: 5, Insightful

      Stop whining? RMS not only instilled in us the ideal of free software but also provided gobs of it and with excellent quality yet! Move on? You mean accept the situation. You mean define what _we_ desire in terms of other's interests? Especially if those interests can hurt us all? I say respect yourself more and value your freedom.

    3. Re:How would "cooperating"..... by drooling-dog · · Score: 4, Insightful
      How would cooperating to create "free" BIOS help Intel?

      There: You've just underlined the need for an Open Source BIOS yourself. Why would any company consider the interests of its customers if there's no obvious, immediate profit in it? And if they wouldn't, why would you trust their proprietary, closed-source software?

      What can it gain by winning over a bunch of geeks?

      Because the Geeks are the ones who advise everybody else on what motherboard to buy.

  4. It's my flashBIOS chip... by Amnenth · · Score: 5, Insightful

    An open-source BIOS is something I'd really appreciate having, especially with the big corporations moving towards their big 'Trusted Computing' platform. It's MY hardware and I'll runn whatever the hell I want on it, not what some mega-corporate conglomerate decides I should.

    1. Re:It's my flashBIOS chip... by Mmm+coffee · · Score: 4, Insightful

      That's exactly why a Free bios is necessary. I am typing this up in a Free Software browser (Konqueror) in a Free Software window manager (KDE), which run on top of a Free Software graphical manager (X), which runs on top of a Free Software system (Gnu), which runs on top of a Free Software kernel (Linux), which is booted by a Free Software boot loader (Grub). All of this Free Software runs on top of a non-free BIOS.

      This raises the question - Am I really Free? When a Free Software BIOS exists, you can make a safe bet that I'll be using it.

      (P.S. I'd suggest against using the term Open Source to describe software which is made to protect the rights of the users. There is a huge difference between Free Software and Open Source - Namely OS completely avoids any real mention of software Freedom. You won't find any mention of the four freedoms on OSI's site. Indeed, the only real mention of software freedom is where they call it ideological tub-thumping. This is definitely a Free Software issue, not an Open Source issue.)

    2. Re:It's my flashBIOS chip... by Mmm+coffee · · Score: 5, Insightful

      How do I know that there isn't spyware code in my bios revealing information about me without my knowledge? How do I know that the lowest level components of my system will perform without any "Trusted Computing" quirks? If I for some reason need to modify my bios to gain a function (to make boot time clustering easier, for example), how could I do that with a non-Free BIOS? As a student, what if I wanted to study the code to my BIOS so I know how my computer _really_ works, on all levels?

      Saying "The license to your BIOS doesn't matter as long as you can run stuff on it" is like saying "The fact that my car's engine is sealed in a lead black box doesn't matter as long as I can still drive." Yeah, on the surface it's true but when you think of the subject with any actual depth it just doesn't make sense.

    3. Re:It's my flashBIOS chip... by Mmm+coffee · · Score: 4, Insightful

      Personal response since you asked - For me the #1 reason I began to detest using non-Free software is because I don't like to feel like a damned criminal, and I don't like to feel like I'm getting screwed over. Let's say I buy WinXP. I go in the store, I pay for it with cash, and I walk out. When I get home and try to install I'm faced with a screwed up EULA which forces me to agree to terms that I find highly objectionable. I was not presented with this contract at the time of sale when I bought that software.

      I don't like being screwed over. Yes, I do read all contracts I agree to. I'd suggest you do the same, you'd be horrified.

      Then after I give permissions to that particular software company, I have to input a number to prove to the software that I actually bought it. And for this particular software I may need to call up the parent company and ask them "May I please have your permission to use this software that I legally bought?"

      I don't like being treated like a criminal. I buy, I use, end of subject. I will not have to prove to anyone that I am law-abiding.

      So I switched two years ago, and Free Software has given me countless personal freedoms that were unthinkable when I was using a non-free system. I no longer need to worry about legality when I want to heavily modify my system to my liking. I no longer feel as if I'm looking at a sealed black box whenever I want to learn something - the entire system is open to explore in any way I choose. The development of the programs I use are not dictated by any one entity, but instead by the users who have our needs in mind.

      It sounds strange, but I think freely now. The technology I use is free for me to hack, rip apart, study, put together, package, Frankenstein into my own project, and so on. And through the freedom of knowledge given to me by free documentation, I have learned how to do just that.

      Now when I think of using a non-Free system I am filled with contempt. Such a system would not be modifiable and explorable, but instead packaged together at the whim of someone else and kept from study. On top of this it's bound by an EULA which is morally deplorable and legally questionable. With the current copyright and patent laws, the actions of the largest software vendors, and the BSA breathing down everyone's necks... I refuse to use a non-Free system. I'd be giving up a hell of a lot more than I'm willing to part with.

      (Note - please be kind, this is a deep subject and I tossed this together off the top of my head while trying to keep it short. This explanation is far from perfect.)

  5. Motherboard support by lisaparratt · · Score: 5, Insightful

    The problem with a motherboard BIOS is that it's tailored to the motherboard. Could the open source fratenity actually produce a workable product across a large number of motherboards? Would they produce something that works properly on all of them, instead of having modules that have been got to a state where they're good enough for the hacker creating them, but not Joe average on the street.

    To be honest, if it's just a BIOS clone, I won't be interested anyway - wake me up when someone recreates OpenFirmware for the PC.

  6. Paranoia? by ayn0r · · Score: 4, Insightful
    The most uncooperative company is Intel, which has started a sham 'open source' BIOS project. The software consists of all the unimportant parts of of a BIOS, minus the hard parts. It won't run, and doesn't bring us any closer to a BIOS that does. It is just a distraction.

    It might just be me being naïve, but would Intel really go to such lengths to create a "distraction"? I find it a bit paranoid to think they'd start a project with the sole intention of just slowing down the progress for an open sourced BIOS.

  7. Treacherous computing by IO+ERROR · · Score: 4, Insightful
    RMS calls this treacherous computing, and with good reason. The BIOS is where everything starts; if a manufacturer doesn't want you doing something with your computer, that is where they would put it.

    "Treacherous computing" is a more appropriate name, because the plan is designed to make sure your computer will systematically disobey you. In fact, it is designed to stop your computer from functioning as a general-purpose computer. Every operation may require explicit permission.

    This makes it even more critical that we get free software BIOSes, and soon!

    --
    How am I supposed to fit a pithy, relevant quote into 120 characters?
  8. Re:Show us the code by Anonymous Coward · · Score: 4, Insightful

    This is a greatly injust comment to the man who started the free software movement. Please note that RMS is the man behind gcc, the most important free piece of software in existance.

  9. OpenBIOS rah rah rah! by NekoXP · · Score: 3, Insightful


    Everyone should support and increase the compatibility of OpenBIOS!

    OpenFirmware is the best BIOS standard ever, the joy of being able to code
    from the command line and have non-interrupt-hijacking calls to the firmware,
    a rudimentary HAL etc. is absolutely 100% cool.

    It won't improve your Windows experience but who the hell cares about that? :)

    It already has the support of Apple, Sun, SGI and IBM, comes in 32 and 64bit
    versions in the standard, has a framebuffer, text console that redirects to
    serial, video etc. automatically, blah blah blah.. Intel won't support it
    because they like EFI.

    But forget Intel too :)

    Everyone should move to PowerPC, but then call me biased..

  10. Wrong implicit assumption! by PontifexPrimus · · Score: 5, Insightful

    I'm sorry, but you're making a wrong assumption: this is not a zero-sum game. A zsg would require a situation where every gain on your opponent's side is a loss for you. Software development doesn't work that way. If you "invest" in creating new software that's freely shared you increase the pie, so to speak. By allowing other people to use your work and not requiring them to re-invent the wheel there is a net gain for the community, including you, since you benefit from others. This is a principle that might be hard to understand for someone who accepts the tenets of capitalism as the only ones possible (I do not wish to insult you, but many Americans seem terribly narrow-minded and uninformed in that respect, having been tought from childhood that everything related to communism is "bad" without ever going into detail).

    --
    -- Language is a virus from outer space.
  11. Re:Mmm_coffee++ by Mmm+coffee · · Score: 4, Insightful

    Agreed wholeheartedly. I've been around the man a few times, and the image most people have in thier minds about him is way off.

    His problem is that he's not the most social creature around, so he tends to come off poorly due to his social ineptitude. Take his speech about free documentation at the O'Reilly conference. While it is very nice (and appreciated) that they're releasing awesome manuals, it's not free for all to use. This threatens Free Documentation -- Since there's these non-free manuals that rock (bought a few of 'em myself), people will be less inclinded to write good Free (speech) documentation, which the movement is in dire need of.

    RMS was 1010% correct. However, he told it at the worst possible moment in the most outright manner possible, so he came off as a jerk.

    Listen to his words. Watch his actions. But try to ignore how he presents the former. He just doesn't know people all that well.

  12. Re:The problem is, "what do you mean by BIOS?" by Ahaldra · · Score: 4, Insightful
    You are contradicting yourself:
    Now, I know somebody will point out OpenFirmware [...] This is nothing more than the Maximalist approach [...]
    [The OpenFirmware drivers] are good enough to boot the system, and then get replaced by OS specific drivers [...]
    You are thinking too black-and-white. Nothing is stopping you from using a hardware and OS independant approach like Open Firmware and then instead of booting a kernel, bring up a device hardware abstraction layer that boots a kernel.
    It hasn't been done yet (to my knowledge) but that shouldn't stop you right? ;-)

    Reading your text I think you have a few misconceptions on what Open Firmware is and which features it provides. I suggest reading this very insightful introduction.
    If you are an embedded systems engineer, what do you think about alternate approaches like Tinyboot?

    --
    Code is Speech. No to Censorship.
  13. Re:You can't eliminate companies by ultranova · · Score: 4, Insightful

    The GPL version of open source is not going to work, especially if you want an entire system from thousands of different vendors to be 100% open source. It's hard enough to get industry-wide standards adopted WITHOUT requiring everyone to give their products away for free.

    How does something that directly contradicts reality get modded insightful ?

    The only thing that will work is to either reinvent the wheel from scratch, in your own country, under communism, and hope you'll succeed where no one else has. (China seems to be making progress).

    The current scarecrow to throw at your enemies is terrorism, not communism. Please follow your times.

    Also, if you meant that shared ownership implies communism, it logically follows that any company with more than one shareholder is communistic.

    Come up with an open source license that doesn't take away control of finished products from companies who haven't yet had a chance to earn a profit from their work

    AFAIK most open source projects are (or at least started as) the work of people, not corporations.

    The GPL doesn't work, it requires immediate release of source that can be used by competitors or would-be customers, and eliminates the profit motive.

    Um, isn't this exactly what the company releasing its code would want ? That anyone who distributes products based on the code must release any enhancments to the code under GPL as well ?

    You do realize that just because you, the original author and copyright holder, released version 1.0 under the GPL, doesn't mean you that you are under any obligation to release version 1.0.1 under any license - assuming, of course, that you own the copyrights to all the code in version 1.0.1 ? Licenses are used togrant rights, under certain terms, to people who don't have the copyright to whatever is being licensed.

    Or were you bemoaning over companies inability to take GPL'd code, add some features, and sell the result as their own proprietary product ? If so, keep on lamenting; you won't get any sympathy from me.

    --

    Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

  14. Three Arguments For An Open BIOS by po8 · · Score: 3, Insightful

    Offhand, I can think of three strong arguments for an OpenBIOS.

    1. Decreased obsolence: As others have noted, changes in BIOS requirements can be responded to given the BIOS source. BIOS maintenance is no longer at the whim of the hardware vendor. This could extend the useful life of hardware.
    2. Decreased HW lockout: As others have noted, the move toward "Trusted Computing" could easily take a sinister turn. An open BIOS would make it much harder for hardware vendors to lock out libre software.
    3. Increased OS compatibility: Many seem concerned about getting hardware compatibility right in an open BIOS. The flip side of this is that getting the BIOS to work with an open OS would become much easier. The premiere example is ACPI, where the BIOS often has bugs with corresponding Windows workarounds.
    I think the goal of producing an open BIOS that works well on a number of machines is quite a difficult one. The rewards of achieving it, however, seem high.