Language Selection

English French German Italian Portuguese Spanish

Foxconn ‘sabotages’ BIOS to stop Linux running

Filed under
Linux
Hardware

Much like the fiasco over Daniel_K’s modded Creative drivers, the Internet community has once again given a voice to the angry people against the big companies. This time the company facing the wrath of Joe Public is Foxconn, which is alleged to have deliberately ‘sabotaged’ the BIOS on some of its motherboards to stop them running Linux.

The accusations stem from a post on the Ubuntu forums, where a poster called The AlmightyCuthulu details his Linux-woes with a Foxconn BIOS. After rooting around in the BIOS on his Foxconn G33M-S motherboard, he says that it contains different tables for different operating systems, and the one for Linux ‘points to a badly written table that does not correspond to the board's ACPI implementation.’ This, he says, results in ‘weird kernel errors, strange system freezing, no suspend or hibernate, and other problems.’

He then goes into more detail, saying that he used a disassemble program to get into the BIOS, and ‘found that it detects Linux specifically and points it to bad DSDT [Differentiated System Description Table] tables, thereby corrupting it's [sic] hardware support.’

Full Story




Even More Incriminating Evidence in The Foxconn Debacle!

After looking through the disassembled BIOS for the last several hours, rebooting it, and tweaking it more, I’d say this is very intentional, I’ve found redundant checks to make sure it’s really running on Windows, regardless what the OS tells it it is, and then of course fatal errors that will kernel panic FreeBSD or Linux, scattered all over the place, even in the table path for Windows 9x, NT, 2000, XP, and Vista, and had to correct them (Well, at least divert them off into a segment of RAM I hope to god I’m sure about)

No, this looks extremely calculated, it’s like they knew someone would probably go tearing it apart eventually and so tried to scatter landmines out so as to where you’d probably hit one eventually.

So if it is a mistake, or incompetence, then it’s the most meticulous, targeted, and dare I say, anal retentive incompetence I’ve seen.

Original Thread

More Here

Ubuntu Forums is no longer Free

Ubuntu Forums has for long been my favourite forum. In the past whenever I had a problem, and I googled about the problems more often than not I found the solution right at the Ubuntu Forums.

Unfortunately, sometimes some incidents crash out all your internal joy over something which has given you joy for a long time. And this is exactly my feelings over Ubuntu Forums right now. Most unfortunately, these feelings are being spurred due to the decisions of Ubuntu Forums admins themshelves.

However, the Admins at Ubuntu Forums closed the particular thread at Ubuntu Forums. Initially it was closed by the Admins on pretext that the staff were “reviewing” it and later the following statement was declared here by one of the forum admins:

More Here

re: Ubuntu Forum FUD

Hard to believe I'm defending Unoobtu forums, but the fact that they deleted a potentially libel thread hardly makes them "not free".

Do they charge to join? Do they charge to post?

No, but they do maintain the right to restrict ANY and ALL content they feel doesn't support their mission statement.

Don't like Foxconn or how they handle Linux installs - vote with your money - don't buy Foxconn.

The Truth About ACPI

http://antitrust.slated.org/www.iowaconsumercase.org/011607/3000/PX03020.pdf

--

From: Bill Gates
Sent: Sunday, January 24, 1999 8:41 AM
To: Jeff Westorinen; Ben Fathi
Cc: Carl Stork (Exchange); Nathan Myhrvold; Eric Rudder
Subject: ACPI extensions

One thing I find myself wondering about is whether we shouldn’t try and make the “ACPI” extensions somehow Windows specific.

It seems unfortunate if we do this work and get our partners to do the work and the results is that Linux works great without having to do the work.

Maybe there is no way to avoid this problem but it does bother me.

Maybe we could define the APIs so that they work well with NT and not
the others even if they are open.

Or maybe we could patent something related to this.

---

http://www.phoronix.com/scan.php?page=news_item&px=NjYyMA

Foxconn Does Hate Linux Support

[…]
The DSDT for Windows is correct, but Foxconn isn’t interested in issuing a (simple) update to fix the Linux support. However, this isn’t surprising to us. We’ve known that Foxconn does not wish to support Linux at all. Going back to 2006, Foxconn has told us at Phoronix that they aren’t interested in Linux on their motherboards and they have no desire to support it.

---

http://ubuntuforums.org/showthread.php?t=869249

You are incorrect in that the motherboard is not ACPI complaint. If it were not, then it would not have received Microsoft Certification for WHQL.

What does the Microsoft Certification say? “The BIOS ain’t done until Linux won’t run”?

re: ACPI

schestowitz wrote:
Going back to 2006, Foxconn has told us at Phoronix that they aren’t interested in Linux on their motherboards and they have no desire to support it.

And yet here it is in 2008 and morons are STILL buying Foxconn and BIG SURPRISE, they STILL don't work with Linux.

How many times do the Linux folks need to be screwed before they figure it out - DON'T BUY FOXCONN.

Nothing says ANY vendor MUST support Linux - vote with your dollars and buy from the ones that do (ASUS, GIGABYTE, TYAN, SUPERMICRO to name just a few).

re: mobos

tell ya the truth, I haven't seen that many Foxconn mobos to choose from. I live in america and order online sometimes, but buy locally sometimes too, but when this whole mess started, I couldn't recall ever seeing a foxconn mobo for sale. Then I find out their parent company is the one of the largest in the world.

If I had seen one, I don't know if I'da known not to buy it. I mean, I do /now/, but sometimes folks just don't know. They should print right on the packaging -> will not function under Linux or FreeBSD. You can't go by the "Requires Windows blah blah blah" because if we paid attention to that, we might not have many components to choose from.

re: mobos

srlinuxx wrote:
They should print right on the packaging -> will not function under Linux or FreeBSD.

In a nice theoretical happy world - that would happen. In THIS world - it's buyer beware (and has been since the first Hominid traded something for a shiny rock). At least now with the Internet, it's very easy to do your homework on pretty much ANYTHING before you buy.

Plus, I don't know of toooooo many products that list what they WON'T work with (Warning: This car will not fly, swim, cross fresh lava, deflect asteroids, etc).

I think it's a safe assumption that if it's not on the "Works with...." label, you're on your own.

re: mobos

silly me. the older I get the longer it takes to wake up in the morning. Big Grin

re: mobos

More likely you're just kind and optimistic, where as I'm crunchy and a die hard cynic. :evil:

SJVN, is that you?

Cyber cynic.

Foxconn Official Response

Foxconn is supposed to issue an official response on Monday. It will be interesting to see what it is.

Hmmm, perhaps I could write a fairly accurate version now of what they're going to say. I'm betting they're going to blame a rogue programmer (some temporary that nobody can find). OK, maybe that's not what they're going to say.

I hate to join the tin-hat brigade, but it's hard to believe that a specific Linux OS detection pointing to a bad table is an accident.

Anyway, I'm fortunate enough to have never purchased a Foxconn MB, and now, I certainly never will.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Scrivener Writing Software has a Linux Version

In some ways, Scrivener is the very embodiment of anti-Linux, philosophically. Scrivener is a writing program, used by authors. In Linux, one strings together well developed and intensely tested tools on data streams to produce a result. So, to author a complex project, create files and edit them in a simple text editor, using some markdown. Keep the files organized in the file system and use file names carefully chosen to keep them in order in their respective directories. when it comes time to make project-wide modifications, use grep and sed to process all of the files at once or selected files. Eventually, run the files through LaTeX to produce beautiful output. Then, put the final product in a directory where people can find it on Gopher.

Gopher? Anyway …

On the other hand, emacs is the ultimate linux program. Emacs is a text editor that is so powerful and has so many community-contributed “modes” (like add-ins) that it can be used as a word processor, an email client, a calendar, a PIM, a web browser, an operating system, to make coffee, or to stop that table with the short leg from rocking back and forth. So, in this sense, a piece of software that does everything is also linux, philosophically.

And so, Scrivener, despite what I said above, is in a way the very embodiment of Linux, philosophically.

I’ve been using Scrivener on a Mac for some time now, and a while back I tried it on Linux. Scrivener for the Mac is a commercial product you must pay money for, though it is not expensive, but the Linux version, being highly experimental and probably unsafe, is free. But then again, this is Linux. We eat unsafe experimental free software for breakfast. So much that we usually skip lunch. Because we’re still fixing breakfast. As it were.

Details with Screen Shots Here

Anyway, here’s what Scrivener does. It does everything. The full blown Mac version has more features than the Linux version, but both are feature rich. To me, the most important things are: A document is organised in “scenes” which can be willy nilly moved around in relation to each other in a linear or hierarchical system. The documents are recursive, so a document can hold other documents, and the default is to have only the text in the lower level document as part of the final product (though this is entirely optional). A document can be defined as a “folder” which is really just a document that has a file folder icon representing it to make you feel like it is a folder.

Associated with the project, and with each separate document, is a note taking area. So, you can jot notes project-wide as you work, like “Don’t forget to write the chapter where everyone dies at the end,” or you can write notes on a given document like “Is this where I should use the joke about the slushy in the bathroom at Target?” Each scene also has a number of attributes such as a “label” and a “status” and keywords. I think keywords may not be implemented in the Linux version yet.

Typically a project has one major folder that has all the actual writing distributed among scenes in it, and one or more additional folders in which you put stuff that is not in the product you are working on, but could be, or was but you pulled it out, or that includes research material.

You can work on one scene at a time. Scenes have meta-data and document notes.

The scenes, folders, and everything are all held together with a binder typically displayed on the left side of the Scrivener application window, showing the hierarchy. A number of templates come with the program to create pre-organized binder paradigms, or you can just create one from scratch. You can change the icons on the folders/scenes to remind you of what they are. When a scene is active in the central editing window, you can display an “inspector” on the right side, showing the card (I’ll get to that later) on top the meta data, and the document or project notes. In the Mac version you can create additional meta-data categories.

An individual scene can be displayed in the editing window. Or, scenes can be shown as a collection of scenes in what is known as “Scrivenings mode.” Scrivenings mode is more or less standard word processing mode where all the text is simply there to scroll through, though scene titles may or may not be shown (optional). A lot of people love the corkboard option. I remember when PZ Myers discovered Scrivener he raved about it. The corkboard is a corkboard (as you may have guessed) with 3 x 5 inch virtual index cards, one per scene, that you can move around and organize as though that was going to help you get your thoughts together. The corkboard has the scene title and some notes on what the scene is, which is yet another form of meta-data. I like the corkboard mode, but really, I don’t think it is the most useful features. Come for the corkboard, stay for the binder and the document and project notes!

Community chest: Storage firms need to pay open-source debts

Linux and *BSD have completely changed the storage market. They are the core of so many storage products, allowing startups and established vendors alike to bring new products to the market more rapidly than previously possible. Almost every vendor I talk to these days has built their system on top of these and then there are the number of vendors who are using Samba implementations for their NAS functionality. Sometimes they move on from Samba but almost all version 1 NAS boxen are built on top of it. Read more

Black Lab SDK 1.8 released

QT Creator - for QT 5 Gambas 3 - Visual Basic for Linux Ubuntu Quickly - Quick and dirty development tool for python emacs and Xemacs - Advanced Text Editor Anjuta and Glade - C++ RAD development tool for GTK Netbeans - Java development environment GNAT-GPS - IDE for the following programming languages. Ada, C, JavaScript, Pascal and Python Idle - IDE for Python Scite - Text Editor Read more

Did Red Hat’s CTO Walk – Or Was He Pushed?

He went on to say that some within Red Hat speculate that tensions between Stevens and Paul Cormier, Red Hat’s president of products and technologies, might be responsible, although there doesn’t appear to have been any current argument between the two. Cormier will take over Stevens’ duties until a replacement is found. Vaughan-Nichols also said that others at Red Hat had opined that Stevens might’ve left because he’d risen as high as he could within the company and with no new advancement opportunities open to him, he’d decided to move on. If this was the case, why did he leave so abruptly? Stevens had been at Red Hat for nearly ten years. If he was leaving merely because “I’ve done all I can here and it’s time to seek my fortune elsewhere,” we’d expect him to work out some kind of notice and stay on the job long enough for Red Hat to find a suitable replacement. Turning in a resignation that’s effective immediately is not the ideal way to walk out the door for the last time. It smells of burning bridges. Read more