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

GNOME and Fedora

  • RFC: Integrating rsvg-rs into librsvg
    I have started an RFC to integrate rsvg-rs into librsvg. rsvg-rs is the Rust binding to librsvg. Like the gtk-rs bindings, it gets generated from a pre-built GIR file.
  • 1+ year of Fedora and GNOME hardware enablement
    A year and a couple of months ago, Christian Schaller asked me to pivot a little bit from working full time on Fleet Commander to manage a new team we were building to work on client hardware enablement for Fedora and GNOME with an emphasis on upstream. The idea was to fill the gap in the organization where nobody really owned the problem of bringing up new client hardware features vertically across the stack (from shell down to the kernel), or rather, ensure Fedora and GNOME both work great on modern laptops. Part of that deal was to take over the bootloader and start working closer to customers and hardware manufacturing parnters.
  • Fedora Atomic Workstation: Works on the beach
    My trip is getting really close, so I decided to upgrade my system to rawhide. Wait, what ? That is usually what everybody would tell you not to do. Rawhide has this reputation for frequent breakage, and who knows if my apps will work any given day. Not something you want to deal with while traveling.
  • 4 cool new projects to try in COPR for February

Why You Shouldn’t Use Firefox Forks (and Proprietary Opera)

  • Why You Shouldn’t Use Firefox Forks Like Waterfox, Pale Moon, or Basilisk
    Mozilla Firefox is an open source project, so anyone can take its code, modify it, and release a new browser. That’s what Waterfox, Pale Moon, and Basilisk are—alternative browsers based on the Firefox code. But we recommend against using any of them.
  • Opera Says Its Next Opera Release Will Have the Fastest Ad Blocker on the Block
    Opera Software promoted today its upcoming Opera 52 web browser to the beta channel claiming that it has the faster ad blocker on the market compared to previous Opera release and Google Chrome. One of the key highlights of the Opera 52 release will be the improved performance of the built-in ad blocker as Opera claims to have enhanced the string matching algorithm of the ad blocker to make it open web pages that contain ads much faster than before, and, apparently than other web browsers, such as Chrome.

Graphics: Glxinfo, ANV, SPIR-V

  • Glxinfo Gets Updated With OpenGL 4.6 Support, More vRAM Reporting
    The glxinfo utility is handy for Linux users in checking on their OpenGL driver in use by their system and related information. But it's not often that glxinfo itself gets updated, except that changed today with the release of mesa-demos-8.4.0 as the package providing this information utility. Mesa-demos is the collection of glxinfo, eglinfo, glxgears, and utilities related to Mesa. With the Mesa-demos 8.4.0 it is predominantly glxinfo updates.
  • Intel ANV Getting VK_KHR_16bit_storage Support Wrapped Up
    Igalia's Jose Maria Casanova Crespo sent out a set of patches today for fixes that allow for the enabling of the VK_KHR_16bit_storage extension within Intel's ANV Vulkan driver. The patches are here for those interested in 16-bit storage support in Vulkan. This flips on the features for storageBuffer16BitAccess, uniformAndStorageBuffer16BitAccess, storagePushConstant16 and the VK_KHR_16bit_storage extension. This support is present for Intel "Gen 8" Broadwell graphics and newer. Hopefully the work will be landing in Mesa Git soon.
  • SPIR-V Support For Gallium3D's Clover Is Closer To Reality
    It's been a busy past week for open-source GPU compute with Intel opening up their new NEO OpenCL stack, Karol Herbst at Red Hat posting the latest on Nouveau NIR support for SPIR-V compute, and now longtime Nouveau contributor Pierre Moreau has presented his latest for SPIR-V Clover support. Pierre has been spending about the past year adding SPIR-V support to Gallium3D's "Clover" OpenCL state tracker. SPIR-V, of course, is the intermediate representation used now by OpenCL and Vulkan.

Security: Updates, Tinder, FUD and KPTI Meltdown Mitigation

  • Security updates for Friday
  • Tinder vulnerability let hackers [sic] take over accounts with just a phone number

    The attack worked by exploiting two separate vulnerabilities: one in Tinder and another in Facebook’s Account Kit system, which Tinder uses to manage logins. The Account Kit vulnerability exposed users’ access tokens (also called an “aks” token), making them accessible through a simple API request with an associated phone number.

  • PSA: Improperly Secured Linux Servers Targeted with Chaos Backdoor [Ed: Drama queen once again (second time in a week almost) compares compromised GNU/Linux boxes to "back doors"]
    Hackers are using SSH brute-force attacks to take over Linux systems secured with weak passwords and are deploying a backdoor named Chaos. Attacks with this malware have been spotted since June, last year. They have been recently documented and broken down in a GoSecure report.
  • Another Potential Performance Optimization For KPTI Meltdown Mitigation
    Now that the dust is beginning to settle around the Meltdown and Spectre mitigation techniques on the major operating systems, in the weeks and months ahead we are likely to see more performance optimizations come to help offset the performance penalties incurred by mitigations like kernel page table isolation (KPTI) and Retpolines. This week a new patch series was published that may help with KPTI performance.