Device supports D3 power save but wrong map

  1. #1
    pastures is offline Full Member

    Question Device supports D3 power save but wrong map

    Minor issue. If I let my system hibernate automatically (when idle), my PCI TV Tuner & Video Capture card fails to revive properly after the system awakes (though the audio continues to come across okay); and I have to reboot the machine before my TV will work correctly again !?



    There are 4 sub-devices found on that TV card. The ones named "BtXBar, WDM Crossbar" and "BtTuner, WDM TV Tuner" are suspected of causing this difficulty.



    Really, I don't understand these Power Management functions or acronyms like D0, D3, and S0 thru S5. I installed this TV Tuner card and hunted down a newer fully-capable driver for the device (from driverguide.com of course) that will serve under WXP (I had bought the device ages ago for use under WME and the included driver CD wasn't working quite right under WXP). I toiled and toiled to locate this newer driver. It was a nasty and perilous trek, lemme tell ya. I wouldn't look forward to trying to replace this driver!



    I am looking at something on the Properties panel for those BtXBar and BtTuner devices that makes me very very suspicious. On the Details tab, under "Power State Mappings" it shows S0 thru S3 all mapping to D0, and that can't be right! It then shows S4 and S5 unspecified. This CANNOT be correct because according to the same tab under "Power Capabilities", both D0 and D3 are supported -- just like the other devices, both on the TV card and also true of most (if not all) of the other devices on my PC. But those other devices show what I presume to be the correct "Power State Mappings", that being S0->D0 and S1->D3 and S2 and S3 unspecified, and S4 and S5 map to D3.

    So my question is: does Windows get that information about the Power State Mappings directly from the device hardware, or is from one of the driver files, and how can it be modified to reflect S1 -> D3, which I'm thinking might overcome the present difficulty because D3 is ('seems obvious) the desired state for a device to be in when the PC goes to hibernation ?

    Thanks!

    [Edit: I should also mention here that I did peruse the .INF files for the BtXBar and BtTuner and there was no obvious mention of the Power Mappings to be seen. Drivers have other binary files too, like .SYS files, and I'm wondering if therein lies some key.]

    [Edit#2: Come to think of it, my system now refuses to go into hibernation voluntarily when idle, and I've got to presume it's those errant mappings that are the cause. I can still command my PC to hibernate, and in fact I gerry-rigged something using a free utility, SwitchOff, and setting it up as a scheduled task when idle, to achieve the same effect as the Windows automatic hibernate when idle.]
    Attached Files
    Last edited by pastures; 22-10-2009 at 09:06 AM. Reason: add attachment


+ Reply to Thread