What is Digg?13 Comments
- ommadawn, on 07/27/2008, -1/+9Read before burying. I know you guys love defending Linux in a Medieval fashion, but get the facts straight first. TheAlmightyCthulhu (Ryan), author of the original post that made the FP yesterday, has sent Matthew Garrett his ACPI table that he'd disassembled. There actually seem to be problems with the board that TheAlmightyCthulhu uses, as he describes in the original post on Ubuntu Forums:
http://ubuntu-virginia.ubuntuforums.org/showthread ...
but, according to analysis from Garrett, they don't result from DELIBERATE SABOTAGE, as Ryan ranted, but rather from either a Linux bug or common Linux indifference from Foxconn (the latter being less likely, as the table seems to be ACPI compliant). As in Garrett's post:
"There is no code in this DSDT that could determine that the system is running any Linux kernel of 2.6.9 or later. This may even be true of earlier versions (...)"
He also explains the fact that currently there is NO WAY for the BIOS to determine that the OS running is Linux (as of recent kernels).
I understand that support of Linux might have been improperly handled, but we need the truth and to know that there is no actual reason to start boycotting the company out of existence (which won't happen anyway). Or to make complete fools out of ourselves in front of the whole IT world... - ommadawn, on 07/27/2008, -1/+7Apparently at least 4000 people on digg solely aren't reasonable people. Well, call that news.
- ommadawn, on 07/28/2008, -0/+4I actually have little insight to the details, I neither hack on the kernel or BIOS. But my common sense tells me to choose the most likely possibility - that they never gave a ***** about Linux, like everyone else does, period. Doing it deliberately wouldn't make absolutely any sense. Linux is economically mere dust to them and unless some sick Windows zealot worker did it on purpose whlie noone was watching that had no chance to happen.
Acknowledging a problem, filing a proper bug report, calling the support is one thing. Sensationalism and conspiracy theories involving idle accusations are other and it's ***** dangerous.
As for them calling you, making public announcements, what's strange about that? They want you to shut up, you made thousands of people hate them overnight, many of them never hearing the company's name before. - inactive, on 07/28/2008, -1/+3***** You! Two of my friends died trying to run Linux on a Foxconn motherboard!
- createuniverses, on 07/29/2008, -0/+2Let me throw some wood on the flames.
Foxconn has blamed this on American Megatrends, and says they have programmers working at HOME on their own time fixing it, Carl Brunning and Zhane Heart have both confirmed that it is their BIOS, and to expect a fix within the next few days probably.
The exact terms he used....(fetches email)
On Mon, 2008-07-28 at 15:59 +0200, Carl Brunning wrote:
> Should have a some answer tomorrow from them
>
> We have found the asus and msi board that have ami have the same problem
> If the bios is award on the same chipset its fine
>
> So we are working on it and the bios writer are working at home as well.
>
> I would love to say we have a fix tomorrow but am unable to
> As this could be fixed tomorrow or take a few days
> It's more like how bad is the ami source code we use is and how much rewrite is there
>
> Sorry about this
>
> But keep smiling we will get there
>
>
> Thanks
>
>
> Kind Regards
> Carl Brunning
> - createuniverses, on 07/29/2008, -0/+1Instant digg success recipe:
1) Use the "***** You! Two of my friends died [insert thread related action here]" meme
2) Get instant diggs from people who haven't heard the joke before
http://farm4.static.flickr.com/3150/2709036365_a72 ... - Leffe, on 07/27/2008, -2/+3Huh? What's new about this? Any reasonable person would have doubted this from the start.
- JasonHaley, on 07/28/2008, -1/+2...And the plot thickens.... I'm going to feel very sorry for the reputation of whoever loses this battle after all the public attention it's garnered in tech world.
- baron1984, on 07/28/2008, -1/+0Sick Windows zealots?
You mean Linuxhaters has a mole in AMI? :P - baron1984, on 07/27/2008, -4/+3Item 1: Foxconn has admitted there is a problem, I have been in contact with them, they have a public announcement about their issues tomorrow (Monday) according to Carl Brunnings.
Item 2: I've been talking to Matthew Garrett, my workaround does work, I know it does because I use it and most of the errors just disappear, according to him, this is impossible.
I only sent him a small part of the overall BIOS, I can't retreive all of it, he even notes the DSDT table has the CPU execute something in an area of memory the OS does not have access to, this could be truly anything, including a malicious payload, we just don't know.
Item 3: Why would Foxconn be ***** themselves and calling me at 1 AM from Taipei, asking me to help them debug the errors that they are also getting, with same board and BIOS, when they try to boot Linux.....if there is not a problem? - baron1984, on 07/28/2008, -3/+1Foxconn has blamed this on American Megatrends, and says they have programmers working at HOME on their own time fixing it, Carl Brunning and Zhane Heart have both confirmed that it is their BIOS, and to expect a fix within the next few days probably.
The exact terms he used....(fetches email)
On Mon, 2008-07-28 at 15:59 +0200, Carl Brunning wrote:
> Should have a some answer tomorrow from them
>
> We have found the asus and msi board that have ami have the same problem
> If the bios is award on the same chipset its fine
>
> So we are working on it and the bios writer are working at home as well.
>
> I would love to say we have a fix tomorrow but am unable to
> As this could be fixed tomorrow or take a few days
> It's more like how bad is the ami source code we use is and how much rewrite is there
>
> Sorry about this
>
> But keep smiling we will get there
>
>
> Thanks
>
>
> Kind Regards
> Carl Brunning
> - baron1984, on 07/28/2008, -4/+1Foxconn has blamed this on American Megatrends, and says they have programmers working at HOME on their own time fixing it, Carl Brunning and Zhane Heart have both confirmed that it is their BIOS, and to expect a fix within the next few days probably.
The exact terms he used....(fetches email)
On Mon, 2008-07-28 at 15:59 +0200, Carl Brunning wrote:
> Should have a some answer tomorrow from them
>
> We have found the asus and msi board that have ami have the same problem
> If the bios is award on the same chipset its fine
>
> So we are working on it and the bios writer are working at home as well.
>
> I would love to say we have a fix tomorrow but am unable to
> As this could be fixed tomorrow or take a few days
> It's more like how bad is the ami source code we use is and how much rewrite is there
>
> Sorry about this
>
> But keep smiling we will get there
>
>
> Thanks
>
>
> Kind Regards
> Carl Brunning
> - baron1984, on 07/28/2008, -5/+1Foxconn has blamed this on American Megatrends, and says they have programmers working at HOME on their own time fixing it, Carl Brunning and Zhane Heart have both confirmed that it is their BIOS, and to expect a fix within the next few days probably.
The exact terms he used....(fetches email)
On Mon, 2008-07-28 at 15:59 +0200, Carl Brunning wrote:
> Should have a some answer tomorrow from them
>
> We have found the asus and msi board that have ami have the same problem
> If the bios is award on the same chipset its fine
>
> So we are working on it and the bios writer are working at home as well.
>
> I would love to say we have a fix tomorrow but am unable to
> As this could be fixed tomorrow or take a few days
> It's more like how bad is the ami source code we use is and how much rewrite is there
>
> Sorry about this
>
> But keep smiling we will get there
>
>
> Thanks
>
>
> Kind Regards
> Carl Brunning
>
Browsing Digg on your phone just got easier with our enhancements to the 
© Digg Inc. 2009
— Content created and posted by Digg users is 