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.
I have used several Intel Linux development products for several years. The C++ compiler, performance primitive library (IPP), and VTUNE are all extremely excellent products, and well supported under Linux.
It would be nice if VTUNE would be brought up to equal footing with VTUNE for Windows, but it's pretty good as is.
I've got that same motherboard. While I haven't fiddled with the other onboard lan card, the onboard 3com one can used with only a vanilla kernel, 2.4.22 or higher. (Don't think it's gotten into the 2.6 series yet) Just use the 3com driver.
Otherwise, haven't had any problems with my board. I'd hardly call it 'craptastic'. I've gotten much better and more reliable performance out of it than my previous boards, while using Windows or Linux.
Cogito ergo sum in Slashdot.
You have a choice, restrict yourself only to hardware that provides open source drivers, use what is made available, or use another OS. Centrino users don't really have the option of demanding open source, if they chose to use the hardware that they want to use. You made the same choice with your video card.
If Intel's choices boil down to "release a binary driver or ignore Linux", which realistically, they do, I'd prefer that they support Linux in any way that they realistically can.
Intel is obligated to its shareholders to protect it's technology. Open source drivers could tip their cards to AMD or some newcomer could gain the upper hand. That is the REALITY of how the hardware business works.
I have had no problem with Nvidia drivers and stability, but I stayed away from the Nforce chipset due to the ongoing support problems it has had.
I too would prefer open source drivers, but I'm not going to threaten to hold my breath until I turn blue just because all they want to give me is binaries.
"Oh my God. This is terrible. This is the end of my Presidency. I'm fucked."; ~ Donald J. Trump
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.
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
Centrino is a set of 3 chipsets.
Intel(R) Pentium(R) M processor
Intel(R) 855 Chipset Family
Intel(R) PRO/Wireless Network Connection.
These 3 parts make up the Centrino, it's not just the wireless part.
There is already full support for the processor in the 2.6 kernel
The 855 Chipset is also supported
The PRO/Wireless is what this is all about. Intel has been saying that they will be supporting the wireless for the last year and we have not seen a thing. The best chance we have currently is running a wrapper for the Windows drivers, this is not bad but not good either. If Intel can deliver a driver that gives Linux users FULL functionality with the Wireless, I know I will at least be happy.
"Some things have to be believed to be seen." - Ralph Hodgson
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.
Since I'm running Debian GNU/Linux stable (yes, that's right, I'm on woody), I had to install a newer version of iwconfig and modify my /etc/network/interfaces file to make it work well:
Of course, since ndiswrapper use the Windows XP drivers file, it does not resolve the problems about proprietary drivers. But at least, I was not stuck to wait (an eternity) for Intel to release their Linux drivers.This space is reserved.