Slashdot Mirror


Intel to Increase Linux Support, Release Centrino Drivers

jonman_d writes "ZDNet UK is reporting that Intel has promised to increase Linux support by releasing Linux drivers at the same time it releases Windows drivers for its hardware. According to the general manager of Intel's Software and Solutions Group, Intel wants Linux users to be able to use their hardware as easily, or easier, than any other hardware on the planet." Pingla writes in with more good news: "Intel promises to release Linux drivers for its Centrino chipset at the same time it releases drivers for Windows. An article featuring Lindows (aka Lin---s) on CNet has more." Sadly, the Centrino support will most likely be a proprietary driver, but it's better than nothing.

33 of 381 comments (clear)

  1. Proprietary drivers by mytec · · Score: 5, Interesting

    Sadly, the Centrino support will most likely be a proprietary driver, but it's better than nothing.

    I'll take proprietary drivers if it means I can use the hardware I like with the OS I love to get work done.

    1. Re:Proprietary drivers by Anonymous Coward · · Score: 5, Insightful
      I'll take proprietary drivers if it means I can use the hardware I like with the OS I love to get work done.

      People should not accept this or we'll get into another situation like you have with NVidia. Get a brand new box and you can't even do a net install on your Nforce chipset box because you need the nvnet driver which is a proprietary binary-only module and the manufacturer of the motherboard may or may not have included a pre-compiled binary on a floppy for you to use, but it's most likely only for Red Hat 9, etc. Screw all binary drivers, I insist on open source drivers for everything. The only thing I've had to relent on lately is the graphics card since the Nvidia stuff is the only decent graphics card out there but the modules are binary only. Sadly, my Nvidia card is also the most unstable part of my Linux box and it crashes (hard locks up) at least every 2 weeks or so and I have to power cycle the box. Fscking Nforce craptastic Asus A7N8X-Deluxe piece of shit motherboard.

    2. Re:Proprietary drivers by 10Ghz · · Score: 5, Insightful
      People should not accept this or we'll get into another situation like you have with NVidia.


      Which is what? A ompany providing kick-ass drivers that give superior performance than that same hardware would give in Windows? What do you suggest using as an alternative to NVIDIA? Ati? HAH, good luck trying to get those drivers to work, open-source or not! And if you do get them to work, what kind of performance are you getting from them? And how about their AMD64-support? NVIDIA has AMD64-drivers available right now. Where are Ati's drivers??? Where are open-source AMD64-drivers for Ati?

      Get a brand new box and you can't even do a net install on your Nforce chipset box because you need the nvnet driver which is a proprietary binary-only module


      One word: Forcedeth.

      Sadly, my Nvidia card is also the most unstable part of my Linux box and it crashes (hard locks up) at least every 2 weeks or so and I have to power cycle the box.


      You know, you CAN use the open-source NV-drivers that ship with Xfree. Or you could use the standard VESA-drivers. So it's not like you are forced to use those drivers. I for one haven't had any problems with NV-drivers.
      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    3. Re:Proprietary drivers by ThisIsFred · · Score: 5, Informative

      If you take the proprietary driver, it means that at some point you may not be able to get your work done. That's great that Intel is going to attempt an on-time release for Linux drivers once. But what happens every time the kernel changes? Or some system library changes? Or the compiler changes?

      And I'm not blaming Intel for this one either. Hardware installation under Linux is a nightmare of inconsistency. If the shipped kernel doesn't fully support your hardware, good luck! The typical Windows user is still not ready to compile a kernel.

      I sort of like what Nvidia does with it's video cards: The 'compile a small kernel interface on-the-spot' type of script. I'm sorry to hear about the fellow with the Nforce chipset problems, but Nvidia's video card drivers are solid.

      --
      Fred

      "A fool and his freedom are soon parted"
      -RMS
    4. Re:Proprietary drivers by Anonymous Coward · · Score: 5, Funny

      "A ompany providing kick-ass drivers that give superior performance than that same hardware would give in Windows?"

      Superior performance as in shorter time from bootup to lockup?

    5. Re: Proprietary drivers by Chris+Croome · · Score: 5, Interesting

      People should not accept this or we'll get into another situation like you have with NVidia. Get a brand new box and you can't even do a net install on your Nforce chipset box because you need the nvnet driver which is a proprietary binary-only module

      I totally agree.

      I built a shuttle box for my little sister a while ago not realising that the Nvidia motherboard's built in ethernet card will only run with a module from Nvidia, it took a while to work this out after installing Linux on it the first time...

      Then 6 months later I have a chance to upgrade Red Hat 9 to Fedora on the box and after the upgrade I discover that the network doesn't work... and at this point I remember what I had to do 6 months before... Aarh!

      So I have to go through the whole process again, find another computer that is connected to the net, download the Nvidia drivers, burn a CD... I thought I'd try the SRPM to make upgrades easier, well these don't build as a normal user so I gave up on them, so I then need to download the tgz version, burn another CD....

      This results in a situation where the kernel can't be upgraded without manually rebuilding the Nvidia modules and this isn't something that I would want to suggest to my sister (she never uses a CLI)... So the local root exploits that all but the latest Fedora kernal have don't get patched... (not a big issue since it's behind a NATed connection and there are only a couple of user accounts, but still it's not ideal...)

      The result of this is that I'll never recommend that anyone gets a Nvidia motherboard and I'll never buy one, it's far too much hassle.

      Sadly I'm stuck with Nvidia video cards in order to play games such as Quake 3 in linux... I wish this wasn't the case...

      What would be ideal would be if the manufactures either release enough info so that GPL drivers can be produced or if they release GPL drivers themselves so they can be included in the kernel.

      Last year I wanted a IDE RAID card and after much googling I discovered that the 3ware ones have drivers in the kernel and no others do, so I brought one even though it cost me more money it has saved me loads of time because I haven't had to mess with installing modules from a hardware company every time I upgrade the kernel... I have no regrets about this bit of hardware... unlike the Nvidia motherboard...

      --
      Check out MKDoc a mod_perl CMS
  2. Setting an example by anish1411 · · Score: 5, Interesting

    I don't think it matters if this is a proprietary driver, just yet. With big people like Intel and IBM showing an interest in Linux, its bound to encourage others to do the same. Then with time, open source drivers might just happen?

    1. Re:Setting an example by dreamchaser · · Score: 5, Insightful

      No, it will probably be the opposite. As Linux grows in popularity, you'll see more and more vendors shipping proprietary drivers for their products. That's not a bad thing unless OSS is your religion.

    2. Re:Setting an example by elgaard · · Score: 5, Insightful

      >That's not a bad thing unless OSS is your religion.

      Or if you use something other than ix86 platforms. Vendors will probably not make binary drivers for CF-cards on my Yopy.
      Although in this Centrino case this might not be a big issue.

      Or you want to path your driver. I.e to allow TV-out on your graphics card. Or fix a bug.

      Or you use a !Linux OSS OS, like BSD.

      Or you use an old or experimental kernel.

    3. Re:Setting an example by hweimer · · Score: 5, Insightful

      I don't think it matters if this is a proprietary driver, just yet. With big people like Intel and IBM showing an interest in Linux, its bound to encourage others to do the same. Then with time, open source drivers might just happen?

      That will take much longer if non-free drivers are available. Intel said somewhere that they won't release the driver as free software because they fear that this would reveal too much information about the hardware itself. So when Intel is out, the driver has to come from a third party. And clearly, the urge to develop a free driver is much lower when there is already a proprietary one available.

      --
      OS Reviews: Free and Open Source Software
    4. Re:Setting an example by BlackHawk-666 · · Score: 5, Insightful
      And then you can vote with your wallet and show these companies that you care about having open source drivers. It's really simple; if they supply open source drivers then consider buying their hardware, otherwise, don't.

      The people who don't care can do what they like at purchase time and they should have the ability to get their closed source drivers so they can use Linux too. It's all a stepping stone to going completely open source. That's not to say closed source should ship with the kernel, because it shouldn't - that position is reserved for open source only.

      --
      All those moments will be lost in time, like tears in rain.
    5. Re:Setting an example by SubtleNuance · · Score: 5, Insightful

      Well, OSS is not a religion. But remember RMS started GNU because of just this -- closed source printer drivers.

      What Intel is doing is doubly bad:

      1) They are releasing a Closed Driver, killing future development, growth and porting of support to future systems.

      2) Really only doing this to spite Lin--s. They are doing this to STOP Lin--s' open-source driver development.... probably not because they want to. Why couldnt they have been forthcoming "we are working on a driver. we intend to release it first qtr 2004. we are making it closed." Why keep the FreeSoftware universe in the dark..? Because they want to hold all the marbles, withholding information is dishonesty. Plain and simple. If you want to be 'trusted', keep no secrets.

  3. Big Hurdle by Mork29 · · Score: 5, Insightful

    Many claim that linux is held back by several factors including ease of use, interface, etc.. etc... I've always felt it was hardware compatiability. You could never be sure all of your hardware would work easily, and the average user can't try and go and build their own custom drivers, or even download them. This will certainly put pressure on the rest of the hardware manufacturors, and this could help linux take a few more points in the market share. No, it's not the magical answer, as their isn't one, but it's another start.

  4. Lin---s by cyber_rigger · · Score: 5, Funny

    Looks like the censors finally beeped out the profanity.

  5. Nice, but... by BassKnight · · Score: 5, Interesting

    It's nice that one of the giants to adopt this position, but I wonder about the form of these drivers. Maybe it's me, but I find more convenient to have drivers that can be compiled as kernel modules, and diffently from, for example Nvidia drivers, that they're not closed source, and license-compatible with the Linux kernel, so people can contribute in order to improve them, and maybe who knows if they can be integrated in the Linux kernel tree. Maybe i'm being too idealist.

  6. Reverse engineer the drivers! by Anonymous Coward · · Score: 5, Interesting

    If you really care about freedom, then help reverse engineer the drivers. Several drivers have already been reverse engineered (such as nvnet for example), whats so hard about a simple wireless network adapter!

    1. Re:Reverse engineer the drivers! by makapuf · · Score: 5, Informative

      That's a security problem with Intel hardware don't you think ?

      Security through obscurity doesn't work. It's possible to make a safe hardware, so that reverse engineering (as rightfully understood by the EU laws) is applied and legal for compatibility. And even (gasp) open-specced hw.

      Even by hardware, I do not mean realy that : software doesn't mean driver OR app OR os, you have firmware too.

  7. Then what about Linux? by Anonymous Coward · · Score: 5, Insightful

    Then I guess Linux been Free Software does not matter either? I am serious, what's the adventage if Linux is going to have the same issues than other OSes: have to get drivers every now and then from different places instead of just upgrade kernel or distro, "play but do not touch", "upgrade your hardware becuase we do not support it anymore", "we do not like your architecture, just x86-32", etc.

  8. Why would 'Proprietary Drivers' be so 'sad'? by cnelzie · · Score: 5, Insightful

    Seriously, what makes it so sad?

    Intel can do what they want. They are the owners of their hardware designs and the drivers to make that hardware function.

    If it's so sad that Intel is going to provide proprietary drivers, do you get sad everytime you get into your automobile? (The computer under your hood mosty likely uses proprietary drivers to interface with the autmobile.)

    There is room for both open and closed software in this world. I for one envision a world where the Operating System is wide open with all the tools one needs to make whatever changes they wish to it and to develop whatever they want to on it. If hardware manufacturers want to keep some or all of their drivers 'secret' that's fine, let them. If application developers want to keep their 'Whiz-Bang 2.0' application proprietary, let them.

    Believe whatever you want. I have and still use quite a large amount of both proprietary and open source software and in some cases, the open source software is better, in other cases, the proprietary software is better, even for the same task.

    What needs to end are silly proprietary APIs put into an OS by particular vendors to allow their other applications to run like the dickens while making competitor's applications less capable.

    --
    If you ignore the other uses of a tool, does that make the tool less useful, or you less useful?
    1. Re:Why would 'Proprietary Drivers' be so 'sad'? by id09542 · · Score: 5, Interesting

      Actually I do get sad when I get in my car with a proprietary computer under the hood. I enjoy "tinkering" and doing minor maintenance to my car, but something as simple as an oxygen sensor now requires a $50 trip to the dealer to tell me this is the reason why my check engine light is on.

    2. Re:Why would 'Proprietary Drivers' be so 'sad'? by JanneM · · Score: 5, Insightful

      There is room for both open and closed software in this world.

      Yes there is. That does not mean that the choice is value neutral, however.

      The licensing of the relevant code is a part of the feature set just as much as the checklist items for the hardware is. It is another item that the customer needs to evaluate and contrast with competing offerings.

      This is why the anguished cries of some manufacturers against governments requiring open source rings so hollow. Just as a customer can require for instance Word file import capability, or three year installation and upgrade support, they can require open source compatible licensing. It is another feature that may carry more or less importance depending on the customer.

      So, if someone says they will not consider hardware without open source drivers, that just means they, for various reasons, value the feature of open source relatively highly, and are ready to pick another supplier to get the feature they want. Note that it really is not just about whether open source or proprietary software is better; the licensing is in itself one (sometimes major) factor in determining the "betterness" of a piece of software.

      --
      Trust the Computer. The Computer is your friend.
    3. Re:Why would 'Proprietary Drivers' be so 'sad'? by arose · · Score: 5, Funny

      Those willing to give up a little liberty for a little hardware compatibility deserve neither drivers nor liberty.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
  9. Give us documentation... instead of closed drivers by zz99 · · Score: 5, Insightful

    "...Intel has promised to increase Linux support by releasing Linux drivers at the same time it releases Windows drivers for its hardware"

    I doubt that they will open souce their drivers. So the Linux developers will write their own anyway, whenever they can.

    And personaly, as a user, I find open source drivers much more convenient.

  10. Re:**SIGH** by Xpilot · · Score: 5, Insightful

    Who the hell cares besides RMS? I love using my machine and it has an nVidia card in it. I don't care that their "driver" is closed source, I can play a lot of heavy duty games with it.

    It's not about RMS. Open source drivers benefit the development of the kernel, and also the users of the drivers and hardware those drivers support. Remember when the linux kernel was at 2.6, but we had to wait some time before nvidia released 2.6 compatible drivers? If they were GPL, the kernel developers could have incorporated the drivers into the kernel and development would have gone concurrently.

    Even now, sticking a closed source driver in there is problematic if there's a kernel panic. How are you going to debug it? What about security? Nobody ourside of nvidia has audited the code. There could be a potential vulnerability that they missed. We negate the benefits of open source if only *part* of our program is open source.

    --
    "Backups are for wimps. Real men upload their data to an FTP site and have everyone else mirror it." -- Linus Torvalds
  11. Re:**SIGH** by Mr+Smidge · · Score: 5, Insightful

    Who the hell cares besides RMS?

    That's quite a flamebait-inducing post you've got there...

    What about other operating systems? Do we have to badger Intel to release drivers for BSD, and whatever other operating systems might be released in the future?

    What happens if we release a new kernel, or decide to change something that breaks the rigid structure into which this proprietary driver is locked?

    Releasing proprietary drivers like this seems to be no more than a "keep them happy" quick-fire solution, as this is by no means a long-term solution. And frankly, ignoring the long-term is a very short-sighted viewpoint indeed.

    What's the ideal solution? Write your drivers so that they use a well-documented and open API that can always be well-supported, and make the code as portable as possible. Then what happens when you want to use your hardware with a different operating system? Well, so long as your operating system implements that particular well-documented and open driver API, then you shouldn't have any problem. Recompile, rinse, repeat.

    Think ahead. We wouldn't be pushing for open source drivers without reason.

  12. proprierty drivers by gunix · · Score: 5, Interesting

    what is so secret about them, really?

    To use them for your own hardware, don't you have to create the exact same hardware? So no use there, since you have your own hardware...
    To use the hardware independet part of the code? Well.. that ought to be a lot of code.

    To use their algorithms? Well, there are a lot of code already they can have a look at (without telling they looked at it, if they are evil)..

    And if they are to stupid to come up with an algorithm of their own, how expencive would it be to hire someone to do it?

    I don't get it...

    --
    Evolution of Language Through The Ages: 6000 BC : ungh, grrf, booga 2000 AD : grep, awk, sed
    1. Re:proprierty drivers by Anonymous Coward · · Score: 5, Informative

      There are issues with regulations: Many WLAN chipsets are within regulation boundaries only due to software control. With a completely open driver, people could use channels which are off-limits for WLAN or boost the signal strength. Many drivers are therefore split into a firmware part which is kept proprietary and executed on the card and a host part which is open and runs on the system processor. Sometimes this is not possible because some chipsets rely on the system processor even for low-level control. Splitting an existing driver into proprietary parts and open parts can take some time too.

  13. proprietary drivers by Anonymous Coward · · Score: 5, Insightful

    A bunch of people in this thread have already posted responses that say things like "I don't care if a driver is bianary, I want to use my hardware, the only people who care are free software zealots."

    Bullshit. Proprietary drivers are a bad idea for linux. Now I have to say, the licensing issue does matter to me. Even if you don't care, there are plenty of technical reasons to avoid them and pester a company to release the source for their drivers. First of all, the code is usually sub-par. EEs right them, they're smart people, no doubt, but most of them aren't programmers and lot's of bugs and race conditions show up. The OSS community can't help debug them because we don't have the source. Furthermore, on a more personal level, most of the kernel hackers don't give two shits about proprietary drivers, because of that, they generally stay buggy and improperly maintained. Intel is a big enough company that they'll properly produce high-quality drivers; however, it is simply a fact that letting the OSS community have the source would increase their quality, more eyes looking at the code, and they would be the same people that have written the kernel. These debates flair up all the time on LKML. I was too lazy to go look for links to specific discussions, if you're interested in the issue however, they wouldn't be hard to find.

    - Ryan, who can't remember his password right now, and so posted AC

  14. Intel Centrino Drivers: A Series of Rumours by wehe · · Score: 5, Interesting

    Intel is announcing plans to release Linux drivers for the WLAN part of their centrino technology from the time beginning. Though there are no facts yet, no release date, no statement whether the drivers will be binary only or Open Source, no information which chipset generations will be supported eventually and so on. See details of the story and How to Get Linux Running on Centrino Laptops at TuxMobil. So don't miss to sign the Linux Support On Centrino Petition! More at the link above.

  15. To everyone saying whats wrong with proprietery. by MooKore+2004 · · Score: 5, Insightful

    Read this. Here is the problem. The kernel developers arent GPL zealots like RMS is, but closed source modules are a problem for them. If a kernel module crashes, and it is the propreitery modules fault, then they can't find out whats wrong and unable to sort out the bug. That is why since 2.6 the kernel developers discourage acccess to the kernel. By opening the drivers, drivers can be more stable on your system.

    To those who say, but Windows DRivers are closed. They are not to the kernel developers. When installing new drivers you may of had a warning that a driver wasnt signed. A signed driver means one that has had its source code audited by MS for bugs, and is more stable than a unsigned one. Microsoft dosent like closed source (unsigned) drivers, and will warn you if you try to install it.

    So if you want a stable Linux, don't load closed source modules into it. Dont take unstabllity for short term hardware support over stabillity in the long term. Encourage companies to open their source, or reverse engineer and stablise their drivers!

  16. Will other organizations follow suit? by jtwJGuevara · · Score: 5, Interesting
    Kudos to intel. Even if the drivers are proprietary, at least they are releasing drivers tailored for their hardware to run under linux. This has been a concern of mine ever since recently switching from the Windows world to linux. Although I may sound like a typical end user when I say this, when I switched from Windows to Linux, but it was an extreme pain in the tail to even configure a sound card in Linux. I know there are things like ALSA and similar projects, but hardly any organizations were packaging any of their own drivers customed suited to their hardware to be delivered in Linux. The result is that the novice user loses from this because he/she cannot use the hardware he/she chooses to use with the software and/or OS he/she chooses to use.

    With that said, this is a step in the right direction and I hope other hardware manufactures do what Intel has pledged to do. Closed source, proprietary drivers are better than no drivers at all.

  17. But he does have a point by bogie · · Score: 5, Insightful

    If you want to play the latest games your stuck with these proprietary drivers. This is only tolerated by many in the community because its either use the binaries are don't play the latest games under linux. btw yes I am aware of drivers for ati's older cards. When it comes to linux and gaming nvidia is the status quo.

    Now my main point is this could lead to some problems for us linux users. Like he pointed out its possible in the future that we'll all be stuck with mobo's that don't work unless we load a dozen proprietary drivers. We did without in the 90's and we can do without now. The nvidia, now the Intel, next the VIA chipsets, its a dangerous trend. You tried to deflate his point at the end by saying just the free nv or vesa etc. What about when that's no longer possible?

    The way I see it is this. You should be able to install your OS, have it support your mobo chipset, video card, mouse+keyboard, and ethernet card all with Free software. You should be able to surf the web, get email, use a calendar and contact list, play movies and music, and be able to create Office documents all with Free software. Those are the basics. Anything less is a failure. Right now all of the above is possible. Start throwing in a Nvidia card, a centrino chipset, and the truly Free desktop starts disappearing. Right now its the not the end of the world. But if in the future proprietary binary drivers become the standard a Truly Free Desktop won't exist and there will be no point in using Linux. After all if I need binary drivers for my hardware like in Windows and I continue to use all of my Windows apps via WINE, wtf is the point? Just stick with Windows and the closed source model. Throwing an opensource kernel on top of all that proprietary software is a lost cause.

    --
    If you wanna get rich, you know that payback is a bitch
  18. Re:I blame Linus Torvalds. by ncr53c8xx · · Score: 5, Insightful
    I say that this is Linus's fault because it's well-documented that the moving-target API's are his clear decision.

    He says so repeatedly in his posts, so it's not like it is a secret.

    And it's a bad decision.

    No you are wrong here. As a practical matter binary drivers lead to buggy unstable kernels. The people writing these drivers have no contact with or support from experienced kernel developers due to the closed nature of the process, and code quality suffers. And people posting about binary drivers waste everyone's time, including their own.

    Until the driver API is stabilized, Linux is going to have a hard time finding users outside the hacker set.

    Linux has a lot of users outside the "hacker set". Did you miss the part about Linux overtaking MacOS and it's current share of the server market?