Slashdot Mirror
Gateway Says Bug Affects 1GHz Thunderbird Systems
krautt writes: "AMD's desperate plight for technical superiority looks like it has caught up with them according to
this article from CNET. I guess that's what happens when you ignore your Q&R engineers and release improperly tested hardware to market." According to the article, the "chip itself is not the likely cause. Instead, the flaw probably results from the overall design of the system or other components." Sounds more like a kink like a showstopper, but a disappointment for anyone in line for a Thunderbird.
The commentary by timothy reads like an astroturf advertisment for Intel.
*exasperated sigh*
Doesn't anyone know the difference between quoted and unquoted text?
timothy: According to the article, the "chip itself is not the likely cause. Instead, the flaw probably results from the overall design of the system or other components." Sounds more like a kink like a showstopper, but a disappointment for anyone in line for a Thunderbird.
timothy states three things:
1. Article says the problem is not with the chip.
2. Problem is minor, not a show-stopper.
3. Disappointment for anyone waiting for systems with the chip.
#1 and #2 seem pretty much in favor of AMD. Number three seems pretty neutral to me, too. This would be a disappointment to anyone waiting for one of the systems, as they would now have to wait longer.
Now, yes, krautt's comment seems rather biased, or at least jumps to conclusions, but everyone's entitled to their opinions.
dragonhawk@iname.microsoft.com
I do not like Microsoft. Remove them from my email address.
Okay, repeat after me: "I will read the story before I post. I will read the story before I post. I will read the story before I post. I will read the story before I post. I will read the story before I post." The actual story referenced mentioned it as a problem with *Gateway's* GHz Athlon system. It is *NOT* a flaw in the chip, it is a flaw in Gateway's crappy, shitty, pissy, worthless motherboard/chipset/firmware/drivers, pick any or all of the above. Read the Techweb story at http://www.techweb.com/wire/story/TWB20000630S0011 for better coverage.
Unfortunately, the idiot who submitted the story was clearly--read his words, his bias--an Intel nut, who was ready to jump the gun and blame AMD for the problem which is Gateway's fault. Now, look at the commentary by Slashdot guy timothy right after the quote from the submitter, that it appears to be a Gateway problem not an AMD problem.
What you must understand is that motherboards by Gateway, Compaq, Hewlett-Packard, Packard-Bell (yuck), and most other big-name systems manufacturers are substandard pieces of junk. To begin with, they are usually so tightly integrated that they have no available AGP slot and few PCI slots, with integrated crappy audio unfit for an old Gravis Ultrasound, integrated video that's four or six generations behind and shares system memory instead of using its own, an integrated NIC which is okay since a NIC is a NIC is a NIC but often it has an IRQ conflict with whatever you plug into the PCI slot, and uses ancient in-house circuitry designed for older chips and manufactured in some third-world hellhole by people who are more skilled with using stone implements than modern silicon-working machinery, by third-tier motherboard manufacturers whom you wouldn't trust to make a decent wristwatch much less a functional motherboard. The BIOSes are almost always in-house vendor-specific stuff, and usually nonstandard and way behind in their support of anything recent. Which is why when you buy a Gateway system it comes with, in addition to the OS, a "system restoration CD" with custom drivers because Windows doesn't even work properly on such a nonstandard shitty motherboard with crufty old custom logic without special nonstandard drivers. The Gateway 1 GHz motherboard in question is manufactured by Jabil. Ever heard of them? Few have or ever will, because they produce crap that no one would ever buy unless it were in a Gateway box with pretty cow-colored cardboard all over it.
This is all, completely, totally, absolutely, undoubtedly a Gatway problem. AMD's Athlon does not bear any responsibility whatsoever for this. Intel zealots will want to exploit it and blame AMD, but the fact remains that the Athlon gives superior performance numbers now that the L2 cache has been integrated on-die, and that there is no problem with the 1 GHz or any other Athlon.
"The more corrupt the state, the more numerous the laws."--Tacitus, *The Annals*
YAEOSMH (Yet Another Example Of Slashdot Media Hype)
Read the headline - oh no! Athlons have a bug! I knew it!
Read the actual story - oh wait, Gateway announced that their motherboard may have a slight problem. Or maybe even their power supply. (How hard is it to build a power supply?) The same thing could affect Intel, Cyrix, G4, or Sparc motherboards, and HAVE NOTHING TO DO WITH THE PROCESSOR.
Sorry, I'm a bit pissed about slashdot content lately. Is it just me, or have their been ALOT of crappy stories lately, as well as alot of missed ones.
---- I made the Kessel Run in under 11 parsecs.