Slashdot Mirror


Linux Centrino Driver Update

Edy52285 writes "An article on News.com talks about how Intel has been, and still is, dragging on releasing their Linux drivers for Centrino. Intel is reluctant to release its drivers as open source since doing so would reveal secrets about their wireless hardware. Linux in currently unable to take advantage of Centrino's wireless networking devices, without, that is, prying $20 from your thin wallet to buy Linuxant's DriverLoader (discussed in an earlier story). Will Swope (Intel's General Manager of Software and Solutions Group) said in an interview said "What I believe will happen is we will end up having a Linux compatibility driver that is not open source at first, then designing future drivers in such a way that they are open source but will not expose intellectual property," Intel seem to be taking its time on releasing the drivers, and even in the article, there is a lack of any commitment on a date or under what conditions the drivers will be released." Also, someone pointed out that it's worth checking out ndiswrapper for the driver.

11 of 273 comments (clear)

  1. ndiswrapper by theridersofrohan · · Score: 5, Informative
    Linux in currently unable to take advantage of Centrino's wireless networking devices, without, that is, prying $20 from your thin wallet to buy Linuxant's DriverLoader

    Not true. I'm using the open-source ndiswrapper project together with the win32 drivers, and it works, although a bit buggy. See here

  2. Re:Secrets? by Fortunato_NC · · Score: 4, Informative

    Much of the actual work of the Centrino wireless hardware is performed in software, much like the "Winmodems" that were so widespread a few years ago (and, I guess, still are - does anyone make a modem with an actual UART on it anymore?) Intel is hesitant to provide the information that will allow people to write a driver for Linux, because that information would necessarily provide 100% of the software engineering necessary for someone else to create a Centrino-like hardware solution.

    --
    Blogging Weight Loss, Distance Education, and more at verlin.com
  3. Re:Secrets? by BenjyD · · Score: 5, Informative

    AFAIK, the radio emissions from the wireless card are regulated (by the FCC in the US?) so as to avoid interference with other spectrum users. Much of this regulation is acheived through the close-source drivers.
    Using modified drivers, it would be possible to make the card emit different frequencies or more power, thereby violating the usage licence.

  4. Do it like M-Systems... by DarkDust · · Score: 4, Informative

    M-Systems' DiscOnChips are very nice flash chips which we use in some ThinClients. While there is support for those in the 2.4.x kernel tree it never worked for us. So we took M-Systems drivers.

    Now they seem to be in a similar boat: they don't like to give out their intellectual property. Their solution is what looks like a driver stub and a binary .o file which is the real driver which does the real work. This way you can build kernel modules for you favourite kernel with M-Systems not releasing any "critical" source code.

    This practice means that you can't compile the driver into the kernel, you have to build a module (since the GPL does not allow building that propietary driver into the GPL'ed kernel, but allows non-GPL'ed kernel modules since they are not part of the resulting program or so... at least this what I recall Linus saying about that subject).

    But having a module does the job as well, using an initrd we can boot from M-Systems DoC perfectly (in Real Mode they are accessible like a harddisk). The extra-effort is worth it since in our experience they are a lot more reliable than Flash IDE Chips, and reliablity is an important factor in embedded systems like ThinClients :-)

    Intel could do it the same way: release a driver stub and a binary .o file which links together a kernel module. Et voila: Neutrino support for every kernel without releasing the real source code !

  5. Re:Secrets? by water-and-sewer · · Score: 5, Informative

    This revealed, do most linux users even want a Centrino-based laptop?

    Hells yeah! I'm within a year of replacing my old PIII 550Mhz Compaq laptop, which has been a trusty and faithful machine until recently but is now starting to give me hardware problems.
    My next machine would be a Dell 300M running SUSE because it's ultra-portable, but thanks to Intel dragging their feet my next machine will probably be a G5 powerbook running Fink. Actually, Dell gets part-credit. Their recent quality control problems have made me suspect the reliability of their hardware.
    That's the way the market works. Hey Intel, thanks for playing, but this ball just went over the fence!

    --
    If this were Usenet, I'd killfile the lot of you.
  6. Prism 54g by Jacco+de+Leeuw · · Score: 4, Informative
    Better yet, get a Prism based WLAN card. Then you will even have 802.11g, which the Centrino doesn't have, AFAIK.

    These card are relatively inexpensive. There's no particular reason to pick a Centrino laptop because of the built-in WLAN support.

    --
    -------
    Warning: Slashdot may contain traces of nuts.
  7. Re:Simple answer, Don't buy nutrino laptops! by TWX · · Score: 4, Informative

    you miss the fact that the vast majority of people who buy these laptops don't care. When 95% of customers don't care, the 5% who do are ignored because of the profit that the majority brings.

    --
    Do not look into laser with remaining eye.
  8. Replace it with MadWifi 802.11a/b/g from Atheros by Erik_ · · Score: 4, Informative

    I've simply removed from my laptop the Intel Pro Wireless 2100 WiFi Mini-PCI card and replaced it with a Atheros 802.11a/b/g chipset. The Multiband Atheros Driver for Wifi (aka MadWifi) is well supported under Linux. It even has a great FAQ.
    The card I bought is an IBM 11a/b/g Wireless LAN MiniPCI Adapter (IBM Part Number: 31P9701), and works flawlessly under REHL3.

  9. Re:Secrets? by marcopo · · Score: 4, Informative
    They could patent everything, but for that they must disclose the technology, and it is no longer secret. No reverse engineering needed - just go grab a copy of the patent application. Clearly they do patent many things. Still, it stands to reason that they some parts of a technology will be kept as trade secrets at least for some period of time.

    --It only takes 20 years for a liberal to become a conservative without changing a single idea.

  10. Re:Secrets? by Anonymous Coward · · Score: 5, Informative

    Odds are Intel does know better than you armchair engineers.

    Having worked there up until a few years ago, I'd say that most of them agree with the "armchair engineers" and think it's silly to try to hide stuff this way. But there are (lets see, where's that Post Anonymously button?) flaming morons in various management positions (mostly marketing) that are totally clueless. AMD, et al. have the resources to disassemble the binary only drivers anyway, so the only thing you are doing is slowing the adoption by technically oriented users, but they can not / will not see this.

    We even had people like Linus, ESR, BP, etc. come out and do dog & pony shows about why it's a Good Idea to open things like this up, but the only thing that seems to be working is a gradual process of selective retirement of the morons. (Intel's culling process to rid itself of the clueless can best be described as "brutal".) Saddly (since I still have stock & and friends in Intel) there is a fair voluntary exodus of the cluefull as well.

    -- Anonomous Coward

    P.S. The funniest part of the dog & pony show was when one of the PHPs listed among the downside of open sourcing the "fact" that it would piss off MS.

    The legal department people who were there were not clueless and came down on the poor idiot like a ton of lead. From the hurt look on his face I think he expected them to side with him.

  11. I stand corrected by TubeSteak · · Score: 4, Informative
    I found this explanation through google: forums.designtechnica.com
    Just a clarification about the whole Centrino thing...just so people have a clear understanding of it.

    Centrino is an Intel brand/platform for promoting mobile wireless technologies. So, it's really not a specific chipset but rather a set of different technologies designed to work together to promote longer battery life without sacrificing performance and good wireless performance (in terms of signal strength).

    Currently, Intel demands that for a product to carry the Centrino moniker, they must have 3 things: a Pentium M mobile processor, an Intel designed supporting chipset (currently the 855GM/PM), and an Intel designed wireless chipset (currently the PROWireless 2100 and 2200).

    If you change out any one of those components you don't get the blue and pink sticker. The most common part to change out is the wireless card since up until recently it only support 802.11b. If a manufacturer does this, they can have a Pentium M sticker for their product.

    Another misconception is that "wireless" is built into the "Centrino chipset". This is untrue from the point of view that the wireless chipset is not part of the 855GM/PM northbridge chipset nor the Intel southbridge. The Intel PROWireless 2100 chipset is nothing more than a miniPCI Wifi card (like everyone else's card). You can easily change out Intel's card for any other industry standard miniPCI card. To Intel's credit, even though it's only 802.11b (for the most part), the performance of their product (in terms of antenna strength and throughput performance) is very good and much better than the consumer crap (i.e. and PRISM based chipset) that was put out before it.

    So, while it's ok to say "Centrino processor" or "Centrino chipset" you should know that it is an umbrella term that refers to a specific set of technologies and not an actual product.

    --
    [Fuck Beta]
    o0t!