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

Fedora: Fedora + Plasma + Unity, Design Interns, and New ISO Build

  • Fedora + Plasma + Unity = Nice looks?
    Hybrid things aren't usually the best option around. Like hybrid cars, for example. Technically, when you marry concepts, you change the energy state, and while this could make sense in that you blend the best of several worlds, when this is done in a forced manner over a short period of time rather than eons of evolution, you end with the worst bits as the product of your mutation. I read about the United theme for Plasma a few months ago, and given that I've spent a fair deal of time fiddling with themes and icons and fonts and making different desktop environments look prettier than their defaults, I was intrigued. So I decided to see whether the notion of having Plasma look like Unity is a sane option. Let us.  Fedora + Plasma + Unity = Nice looks? [...] What is thy point, Vanessa, the astute among you may ask? Well, I have nothing against United or its creators, but I did come to the conclusion that too much tweaking is worse than no tweaking, if this statement makes sense. I like the notion of trying to overcome the inherent problems in each desktop through the use of themes and extensions. After all, I've been doing that profusely for the past few months. But it gets undone when you cross the desktop environment space. Making Gnome better yes. Making Plasma better, absolutely. Unity as an overlay for Plasma, well tricky. There's too much disparity for you to be able to hide the underlying workflow mechanisms and UI philosophies. Then, every little inconsistency glares. You notice things you do not expect, and you get angry because there are certain things you do expect. Some transformations work quite well because they build on the foundations, e.g. various Gnome panels or Macbuntu. But Plasma has its own special charm and flow and making it into a weird version of Unity, which itself is a weird version of Gnome misses the bigger picture. And so, if you're asking me, Plasma and Unity are two separate worlds, best enjoyed in isolation. United is an interesting notion, but it also signifies the upper limit for my own wild ideas and tweaking. Yes, you can make it work, then again, it means taking away from the beauty and style of what these two desktops do, and that's not the purpose of my pimping guides. So we shall stop here, and explore other colors and shapes. Have fun, little penguins.
  • Fedora Design Interns 2017
    Here’s an update on internships. Older post linked to here. Quick recap: there’s been 2 long-term interns for Fedora design team since February, and one short-term guy, who came for 2 weeks at the beginning of June. Guys have been doing an amazing job, I can’t stress enough how happy I am to have them around.
  • F26-20170815 Updated ISOs released

today's howtos

Security: Hardware Back Doors, Microsoft Windows, Kronos

  • Hiding malware in boobytrapped replacement screens would undetectably compromise your mobile device
     

    On the one hand, if you let an untrusted stranger install hardware in your electronic device, you're opening yourself up to all kinds of potential mischief; on the other hand, an estimated one in five smartphones has a cracked screen and the easiest, most efficient and cheapest way to get that fixed is to go to your corner repair-shop.  

  • How hackers {sic} are targeting the shipping industry [iophk: "Microsoft TCO"]
     

    Whenever one of the firm's fuel suppliers would send an email asking for payment, the virus simply changed the text of the message before it was read, adding a different bank account number.  

  • Locky ransomware is back from the dead with two new strains [iophk: "Windows TCO"]
     

    What hasn't changed, though, is the method of distribution.Rather than rifling through the trove of spilt US National Security Agency exploits, as the groups behind WannaCry and NotPetya did, Locky is distributed via phishing emails containing malicious Microsoft Office files or zipped attachments containing a malicious script.

  • Connected cars could have an airbag problem
     

    "It's not the car manufacturers' fault, and it's not a problem introduced by them. The security issue that we leveraged in our research lies in the standard that specifies how the car device network (i.e., CAN) works," added Trend.

    [...] To eliminate the risk entirely, an updated CAN standard should be proposed, adopted, and implemented. This whole process would likely require another generation of vehicles."

  • Code chunk in Kronos malware used long before MalwareTech published it
    A chunk of code found in the Kronos bank-fraud malware originated more than six years before security researcher Marcus Hutchins is accused of developing the underlying code, a fellow security researcher said Friday. The conclusion, reached in an analysis of Kronos published by security firm Malwarebytes, by no means proves or disproves federal prosecutors' allegations that Hutchins wrote Kronos code and played a role in the sale of the malware. It does, however, clarify speculation over a Tweet from January 2015, in which MalwareTech—the online handle Hutchins used—complained that a complex piece of code he had published a month earlier had been added to an unnamed malware sample without his permission.
  • Secret chips in replacement parts can completely hijack your phone’s security
    People with cracked touch screens or similar smartphone maladies have a new headache to consider: the possibility the replacement parts installed by repair shops contain secret hardware that completely hijacks the security of the device. The concern arises from research that shows how replacement screens—one put into a Huawei Nexus 6P and the other into an LG G Pad 7.0—can be used to surreptitiously log keyboard input and patterns, install malicious apps, and take pictures and e-mail them to the attacker. The booby-trapped screens also exploited operating system vulnerabilities that bypassed key security protections built into the phones. The malicious parts cost less than $10 and could easily be mass-produced. Most chilling of all, to most people, the booby-trapped parts could be indistinguishable from legitimate ones, a trait that could leave many service technicians unaware of the maliciousness. There would be no sign of tampering unless someone with a background in hardware disassembled the repaired phone and inspected it.

Ubuntu: Themes and Icons, MAAS, Podcast and More

  • Some interesting Ubuntu themes and icons
    Well, I guess there isn't much to say. If you like the stock looks, ignore this article. If you find the defaults not colorful or fun enough, or you just plain like tweaking, then you might want to consider some of the stuff I've outlined here. My taste is subjective, of course, but then, I aim for simple, clean designs and pleasing art work. Overall, you have a plenty of good options here. More icons than themes. Vimix or Arc seem like neat choices for the latter, and among the sea of icons, Moka, Numix and Uniform seem to do a great job. And of course, Macbuntu. I wish there were more monochrome or accented icons, but that's something I still haven't found. Anyhow, I hope you like this silly little piece. If you have suggestions, please send them, just remember my aesthetics criteria - simplicity of installation, clean lines, no gradients, no bugs. That would be all for today, fellas.
  • 7 of the Best Icon Themes for Ubuntu
    On a hunt to find the best icon themes for Ubuntu? Well, you’ve come to the right post place! In this post we will show you some of the best icon themes for Ubuntu, ranging from modern, flat icon sets, to a circular icon pack carrying a colourful twist. Oh, and as this article is constantly updated you don’t need to fret about any of the links or information being out of date. Feel free to bookmark this list for future reference, or share it on social media.
  • MAAS Development Summary – August 18th, 2017
  • S10E24 – Fierce Hurried Start
  • conjure-up dev summary: aws native integration, vsphere <3, and ADDONS