Intel Core Duo battery life drained by USB devices

Discussion in 'Buying Tips and Advice' started by simie, Jan 29, 2006.

  1. simie macrumors 6502a

    simie

    Joined:
    Aug 26, 2004
    Location:
    Sitting
    #1
    http://www.theinquirer.net/?article=29326

    A REPORT claimed that plugging in any old USB 2.0 device will sap a notebook using Intel's Core Duo by over one hour of battery life.
    According to TG Daily, Intel is blaming the problem on a bug in a Microsoft driver.

    But that's debatable - according to the site. It claims that the Napa chipset is the real problem, and quotes a number of unnamed notebook manufacturers saying the 945GM chipset is the real botheration.

    This would mean, for example, that if you plugged in the famous USB duck device, you would be unlikely to get the four or five hours of battery life you might have expected. Intel was unavailable for comment at the time of quacking.

    Are the new MacBook Pro's affected by this ?
    Are all variations of the 945 chipset affected?
     
  2. robbieduncan Moderator emeritus

    robbieduncan

    Joined:
    Jul 24, 2002
    Location:
    London
    #2
    This appears to be a driver problem in Windows XP only at this point of time. OSX is not reported to be effected yet.
     
  3. mkrishnan Moderator emeritus

    mkrishnan

    Joined:
    Jan 9, 2004
    Location:
    Grand Rapids, MI, USA
    #3
    Intel's theory will certainly be validated or invalidated by the MBP, if this is not resolved by then! I wonder whether the device needs to actually use USB2, since it is called out specifically? Would this happen even if you used a USB mouse? People who use mice with wires are crazy, but they still don't deserve that. :(
     
  4. Abstract macrumors Penryn

    Abstract

    Joined:
    Dec 27, 2002
    Location:
    Location Location Location
    #4
    Will a USB 2 device sap a notebook's battery life by an hour, or will an extra hour's worth of power be stored in the battery, unused? I'm sure it's the latter, but the story doesn't provide any details whatsoever, so lets just wait for the MBPs before us Mac users act like boogers about this.
     
  5. robbieduncan Moderator emeritus

    robbieduncan

    Joined:
    Jul 24, 2002
    Location:
    London
    #5
    There appears to be a MS KB article. It this /. post is accurate it's an XP problem, not a hardware one.
     
  6. mkrishnan Moderator emeritus

    mkrishnan

    Joined:
    Jan 9, 2004
    Location:
    Grand Rapids, MI, USA
    #6
    Did I miss it, or according to this KB, is this problem in XP completely unrelated to the Core Duo?
     
  7. plinden macrumors 68040

    plinden

    Joined:
    Apr 8, 2004
    #7
    AnandTech just reported on this issue - http://www.anandtech.com/mobile/showdoc.aspx?i=2693

    AnandTech has shown that it's a problem with XP only, not just with the Core Duo but also on older Pentium-M CPUs. Edit: And it happens with the Intel 915 chipset, so it's not chipset related.

    So nothing to worry about here.
     
  8. twoodcc macrumors P6

    twoodcc

    Joined:
    Feb 3, 2005
    Location:
    Right side of wrong
    #8
    why am i not suprized that it's just a windows xp problem?
     
  9. ~Shard~ macrumors P6

    ~Shard~

    Joined:
    Jun 4, 2003
    Location:
    1123.6536.5321
    #9
    This is old news, and there were already threads/discussions on it here at MacRumors 2-3 weeks ago. Just do a search and you'll find them.

    Nothing more to see here people, move along... :p ;) :cool:
     
  10. Timepass macrumors 65816

    Joined:
    Jan 4, 2005
    #10

    well they blame it on drivers ifor XP but at the same time they are the ones who are responible for designing the Drivers and they are different for each OS. M$ does have a valid point in point it back at intel for fixing it. Intel designed the boards and are the ones who are responible for the drivers. M$ drivers are general drivers and are designed to get the computer up and running. After that the drivers designed for rest of the hardware needs to be taken care of. Now M$ will put those drivers on windows update but it needs the drivers to put there first, which is intels job.

    That or part of the problem could trace down to the MOBO them selves and issue dealling with BIOS over EFI that apple users. A windows computer can not go to full sleep mode and still be waked up by a USB device and the issue deals with the BIOS over firmware. USB requires the CPU to be used. Com ports I/O and PS/2 ports do not require any cpu power to be used. It a limitation of the BIOS no the OS itself. I hope with EFI that windows is switching over 2 will allow those computer to do the full sleep as well.
     
  11. chaosbunny macrumors 68000

    chaosbunny

    Joined:
    Mar 11, 2005
    Location:
    down to earth, far away from any clouds
    #11
    Slightly off topic, but WHY?????????????????????
     
  12. plinden macrumors 68040

    plinden

    Joined:
    Apr 8, 2004
    #12
    Which is why I posted the new information (i.e. affects older CPUs, not chipset dependent) in a two week old thread, rather than creating a new one. I thought it was interesting in a general sort of way, not "OMG, teh duel cors are cr@P!!"
     
  13. ~Shard~ macrumors P6

    ~Shard~

    Joined:
    Jun 4, 2003
    Location:
    1123.6536.5321
    #13
    Gotcha - makes sense. :)
     

Share This Page