Language Selection

English French German Italian Portuguese Spanish

Microsoft denies Xbox issues

Filed under
Microsoft

Microsoft has denied a report in the British tech publication The Register, that last month's recall of power cords for 14.1 million Xboxes was connected to broken solder joints inside early Xbox consoles.

Charlotte Stuyvenberg, director of global communications for the Xbox, said the report was incorrect. The problem with the power cord and the solder joints were mutually exclusive, she said.

A Microsoft statement sent earlier said: "In rare cases, solder joints have broken. This issue is not associated with the power cord replacement program..."

The statement came the same day that The Register reported that an Xbox had blown up in a user's face in Sweden even though the power cord had been replaced.

Ms Stuyvenberg said this incident was being dealt with separately. "Our people have got hold of this console to investigate the circumstances which caused it," she said.

According to hardware experts quoted in The Register, the problem is not with the power cable, but rather with the power supply on certain models.

The experts were quoted as saying that the new cable only made the problem worse; the meltdown and fire risk were caused by wear and tear on the power supply used in early models and the new replacement cables only contained a trip that reduced the risk of a fire but left users with a console which was literally fried.

In enthusiast forums, such as the Xbox Scene, there are plenty of complaints about the problem.
Postings are accompanied by screenshots to show the areas where owners claim the solder has worn off in earlier models and caused the problem.

Ms Stuvyenberg said the Swedish case was a "one of a kind situation," and there was nothing wrong with the Foxline power supplies, the ones which users have named as being those from which solder was wearing off and posing a fire risk.

She said the question of broken solder joints would be covered under a warranty. All Xbox consoles had been designed so that a broken solder joint did not present any safety issue.
Several Xbox users have reported that the v1.0 and v1.1 power supplies, not the cable, is to blame for the issue. Users of later Xbox versions are also getting replacement cables even though the machines aren't faulty.

An online petition, which claims that the recall of the power cords is a cover-up of the real problem, has now collected 1779 signatures.
A Swedish newspaper appears to have been the first to publicise the actual problem.

There have been problems with the Xbox in the past. In February 2002, soon after the console went on sale in Japan, there were complaints from customers about it scratching game and film discs.

The discs and DVD movies came out scratched after being removed from the Xbox, though in most cases the discs were still playable.

At the timer Microsoft said that the scratching affected "significantly less than 1 percent of systems sold."

The complaints in Japan came after a few reports of defective units in North America, where the Xbox went on sale in November 2001.

Source.

More in Tux Machines

today's howtos

Graphics: VC4 and AMDVLK Driver

  • VC4 display, VC5 kernel submitted
    For VC5, I renamed the kernel driver to “v3d” and submitted it to the kernel. Daniel Vetter came back right away with a bunch of useful feedback, and next week I’m resolving that feedback and continuing to work on the GMP support. On the vc4 front, I did the investigation of the HDL to determine that the OLED matrix applies before the gamma tables, so we can expose it in the DRM for Android’s color correction. Stefan was also interested in reworking his fencing patches to use syncobjs, so hopefully we can merge those and get DRM HWC support in mainline soon. I also pushed Gustavo’s patch for using the new core DRM infrastructure for async cursor updates. This doesn’t simplify our code much yet, but Boris has a series he’s working on that gets rid of a lot of custom vc4 display code by switching more code over to the new async support.
  • V3D DRM Driver Revised As It Works To Get Into The Mainline Kernel
    Eric Anholt of Broadcom has sent out his revised patches for the "V3D" DRM driver, which up until last week was known as the VC5 DRM driver. As explained last week, the VC5 driver components are being renamed to V3D since it ends up supporting more than just VC5 with Broadcom VC6 hardware already being supported too. Eric is making preparations to get this VideoCore driver into the mainline Linux kernel and he will then also rename the VC5 Gallium3D driver to V3D Gallium3D.
  • AMDVLK Driver Gets Fixed For Rise of the Tomb Raider Using Application Profiles
    With last week's release of Rise of the Tomb Raider on Linux ported by Feral Interactive, when it came to Radeon GPU support for this Vulkan-only Linux game port the Mesa RADV driver was supported while the official AMDVLK driver would lead to GPU hangs. That's now been fixed. With the latest AMDVLK/XGL source code as of today, the GPU hang issue for Rise of the Tomb Raider should now be resolved.

AMD Ryzen 7 2700X Linux Performance Boosted By Updated BIOS/AGESA

With last week's initial launch-day Linux benchmarks of the Ryzen 5 2600X / Ryzen 7 2700X some found the Linux performance to be lower than Windows. While the root cause is undetermined, a BIOS/AGESA update does appear to help the Linux performance significantly at least with the motherboard where I've been doing most of my tests with the Ryzen 7 2700X. Here are the latest benchmark numbers. Read more

GNU: The GNU C Library 2.28 and Guix on Android

  • Glibc 2.28 Upstream Will Build/Run Cleanly On GNU Hurd
    While Linux distributions are still migrating to Glibc 2.27, in the two months since the release changes have continued building up for what will eventually become the GNU C Library 2.28. The Glibc 2.28 work queued thus far isn't nearly as exciting as all the performance optimizations and more introduced with Glibc 2.27, but it's a start. Most notable at this point for Glibc 2.28 is that it will now build and run cleanly on GNU/Hurd without requiring any out-of-tree patches. There has been a ton of Hurd-related commits to Glibc over the past month.
  • Guix on Android!
    Last year I thought to myself: since my phone is just a computer running an operating system called Android (or Replicant!), and that Android is based on a Linux kernel, it's just another foreign distribution I could install GNU Guix on, right? It turned out it was absolutely the case. Today I was reminded on IRC of my attempt last year at installing GNU Guix on my phone. Hence this blog post. I'll try to give you all the knowledge and commands required to install it on your own Android device.
  • GNU Guix Wrangled To Run On Android
    The GNU Guix transactional package manager can be made to run on Android smartphones/tablets, but not without lots of hoops to jump through first.