Foxconn Releases Test BIOS Fixing Linux Crashes 196
Ryan1984 writes "Only a week after the bad press coverage regarding the Linux-related bugs in a number of motherboards released by Foxconn (which turned out to be the AMI BIOS that several board makers use), Foxconn is the first vendor out with a publicly released test patch that fixes the bulk of the problems, allowing kernel 2.6.26 to run well on the afflicted boards. The remaining issues appear to either be kernel bugs in builds earlier than 2.6.26, issues with the Intel chipset itself, or minor annoyances that Foxconn is still working to resolve. Foxconn representative Heart Zhang has posted on the Ubuntu forums (where the situation began), apologizing for the issues, thanking Foxconn customers and the community at-large for their feedback, and promising that Foxconn will take Linux support and testing seriously, going forward."
When a mobo manufacturer supports linux publicly.. (Score:1, Interesting)
I'll consider their stuff. What I can't accept is non-acknowledgment, ostrich-style. That just loses me.
Re:Good sign (Score:5, Interesting)
So, you think it would have been fixed if there had not been angry, almost rabid, users? You know, the ones you refer to as "crazy zealots"?
I don't believe so. I believe the issue would have been ignored, and Linux would have been patched in some obscene manner to "work around" the issue. Giving a bad reputation to Linux; "it doesn't work -- what kind of fucking shit is THIS?". Hurting the reputations of many developers.
Sometimes, the only sane response is to be angry and rabid.
Was it a bug? Was it deliberate? Who knows. That debate is still open. What IS important is that there is at least ONE open source OS with the clout to keep vendors honest.
Re:Theyre fixing it (Score:3, Interesting)
Re:When a mobo manufacturer supports linux publicl (Score:4, Interesting)
Ubuntu forum thread [ubuntuforums.org]. Starts at post #114.
If he is correct in what he writes, then it doesn't seem much like speculation.
Perhaps if someone else has linkage to a sound refutation of his claims, it would be a good thing to post here. I've seen comments that TheAlmightyCthulu's claims were 'debunked', but the comments didn't say where, or have links.
companies often contradictory on Linux support (Score:4, Interesting)
Yeah. This also seems to be an example of a more general phenomenon with Linux support, which is that the same company will make completely contradictory statements about their own Linux support. In the earlier slashdot story [slashdot.org], someone from Foxconn is directly quoted as saying 'it doesn't support Linux;' now they say they always intended to support Linux. The truth is probably that they never even thought about Linux support, and then when the issue was brought to their attention random representatives started saying random things off the cuff.
I've had a similar experience with Amazon's MP3 store. If you want to buy entire albums (as opposed to individual tracks), you have to use special downloading software that they supply. The software was initially only available in Windows and Mac versions, but pretty quickly they brought out Linux versions as well. Nowadays when you use your Linux box to shop for albumbs on their site, if you don't have the software installed your browser will detect that, and detect your OS as linux, and they'll generate a page for you offering links to download a linux version of the downloader. In fact, they even have it available in multiple versions for different linux distros. However, the linux downloader has been pretty buggy for me (and was also hard to get working properly on x64). I've had it working, then it broke, etc. I've done two calls to Amazon's tech support about this, and in both cases, the initial reaction was to tell me to do a bunch of stuff (with the usual confusion because the Indian tech support person gives Windows+IE instructions, and has never heard of Linux), and then when that didn't help they checked with someone else, who told them Linux wasn't supported. Never mind that they've had Linux versions of the software up on the site for months now.
I think part of the problem is that so many people in the hardware and software industries live in a 100%-Windows environment. It honestly never even occurs to them that anyone is running any other OS. (In the case of Foxconn, they're not making mac-compatible boards, so it's probably true that 99% of their boards are being used with Windows.) Then when the issue comes up, they just deal with it off the cuff. It's like asking them what their policy is on recycling cardboard -- they probably don't have one, and they don't see why it's important.
Another problem may be that in a Windows monoculture environment, many people don't understand what a standard really is. They think Windows and Word and IE are standards. Instead of developing for the relevant standard, some PHB makes the decision that they're going to target something proprietary, calling that a "standard," and they think of it as extra work to add support for anything else -- when in fact, it would have made more sense just to support the standard properly in the first place.
Re:Theyre fixing it (Score:5, Interesting)
I believe we have that, it's called ACPI. And if motherboard manufacturers are having a hard time properly coding things due to the spec, the spec needs to be fixed. If they're being lazy about it, then people should avoid buying their products.
But what really needs to happen is for MS to stop accepting broken implementations. I don't know for sure, but I'm sure that the broken ACPI implementations are a headache for those writing the parts of Windows that have to interact or take results from the ACPI, requiring a proper adherence would make it less of a headache for everybody.
No issue, only bad press from one guy (Score:1, Interesting)
http://mjg59.livejournal.com/
Quote :
Take home messages? There's no evidence whatsoever that the BIOS is deliberately targeting Linux. There's also no obvious spec violations, but some further investigation would be required to determine for sure whether the runtime errors are due to a Linux bug or a firmware bug. Ryan's modifications should result in precisely no reasonable functional change to the firmware (if it's ever hitting the mutex timeout, something has already gone horribly wrong), and if they do then it's because Linux isn't working as it's intended to. I can't find any way in which the code Foxconn are shipping is worse than any other typical vendor. This entire controversy is entirely unjustified.
Re:When a mobo manufacturer supports linux publicl (Score:3, Interesting)
Well, it is definitely written into the APCI 2.0 specs. When implemented, the bios can check the OS running and give specific tables to the OS that ease compliance and nuances that are different among other operating systems.
If this is the case in which it happened that way, then it can be as simple as other mainboard manufacturers not using specific DSDT tables or referring all non recognized or handled returns as NT and providing NT versions of the DSDT tables. When Foxxcom's programmer decided not to acknowledge linux and/or forgot to point it back to the windows tables, we see an issue that is specific to one instance and manufacturer.
Make no mistake, they didn't write anything specific into the bios to check for linux. That is already there and part of the spec. Failing to handle the return properly is a mistake but it doesn't imply the malice accusations that are going around. And no, this first appearance doesn't mean it can't happen with the other manufacturers, it just means that it hasn't because they did something different or were more thorough. Linux mimics windows in a lot of ways on these levels and for the most part, can handle the windows DSDT returns. If a mainboad simply passes the windows tables on a linux return, you would likely never know the difference without the source or decompiling the bios.
Re:Theyre fixing it (Score:3, Interesting)
An even better thing to do would be to standardize one API that the Linux kernel uses and give that to manufacturers so they can support all Linuxes, rather than masquerading as Windows.
We already do that, Linux implements ACPI. However Windows doesn't.
So motherboard makers theoretically would have to accommodate the Windows oddities *and* support the standard (which wouldn't work in Windows). Fun huh ? How many are prepared to support the extra cost ?
Or of course the kernel developers can make do with the broken implementation of ACPI that are seen in the wild and that do work with Windows. In practice it's the only way to make sure the system will work on a random x86 type of machine.
AARD (Score:5, Interesting)
Re:This is Foxconn's BIOS problems, not generic to (Score:4, Interesting)
Re:They're fixing themselves all else is incidenta (Score:2, Interesting)
I'm proud that Slashdot has the rep of having really smart posters who know their shit.
BTW, I was always in the "bad copy-paste" camp.