MAPOSD3toNV in detail :)

[Guest C810_user]

:) My laptop has a problem powering up from standby mode with this driver. All I see is a black screen. Has anyone here experienced this? If so, how do I tweak the file to fix this?

Thanks.

Latitude 810, Pentium III 1.13 GHz, 15" UXGA 1600x1200 IBM

512 MB SDRAM, 20GB Hard Drive, Windows XP Professional [sP2],FlashBIOS

Version A12

32MB NVIDIA GeForce2 Go, NVIDIA 7.1.8.0 mod driver

[®®®]

Try around with MAPOSD3toNV value in the mobile INF.

Default i think is still 3, so you can try 2. That's what i use for my Pre GF FX card and it solves the Standby issue.

[LSudlow]

Yes, 3 is for FX cards and newer. Previous cards should use 2.

[®®®]

Pieter, could this be added to your INF or should we just use Teraphy's INF Enhancer? I mean this is a fairly general setting which applies to a wide range of cards. Though i can't remember all the DEV_IDs from people who posted about the problem. The only thing i know for sure is that DEV_ID 177 (460 Go) needs it.

[mobilenvidia]

I added a wee remmed line with this in the INF just after the HKR settings, did this a few weeks back.

I prefer to keep the INF for newer GPU support, as technology moves on it's no use lagging behind. (and I'm the furtherest in Caveman territory)

I could split the INF up into 2 sections but would doube the size of the INF.

Mine works fine with standby, just not with Hibernate, although it used to, I prefer standby anyway a lot quicker.

[nv_SoftwareDeviceSettings]HKR,, InstalledDisplayDrivers,      %REG_MULTI_SZ%, nv4_disp

HKR,, Acceleration.Level,            %REG_DWORD%,    0

HKR,, MultiFunctionSupported,        %REG_DWORD%,    1

HKR,, NvCplEnableHardwarePage,      %REG_DWORD%,    1

HKR,, OverlayMode2,                  %REG_DWORD%,    0xF00050

HKR,, OverlayMode3,                  %REG_DWORD%,    0x10400001

HKR,, OverlayMode4,                  %REG_DWORD%,    0x3

HKR,, RotateFlag,                    %REG_DWORD%,    4

HKR,, UseBestResolution,            %REG_DWORD%,    1

HKR,, VgaCompatible,                %REG_DWORD%,    0

HKR,, NV_Modes,                      %REG_MULTI_SZ%, "{*}S 320x200 320x240 400x300 480x360 512x384 640x400=1FFF;SHV 640x480 720x480 768x576 800x600 1024x768 1152x864 1280x720 1280x768 1280x800 1280x854 1280x960 1280x1024 1360x768 1366x768 1400x1050 1440x900 1600x900 1600x1000 1600x1024 1600x1200 1680x1050 1920x1200 1920x1440 2048x1536x8,16,32=1FFF"

HKR,, DCBOverride0,                  %REG_BINARY%,  04,25,00,22,18,20,10,01,00,02,b8,88,00,00,00,02,01,01,b8,88,00,00,02,02,11,02,00

00,00,00,02,01,11,02,00,00,00,00,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,3f

3e,00,00,37,36,00,00,51,50,00,00,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

ff,ff,ff,ff,ff,ff,ff,ff,ff

HKR,, DCBOverride1,                  %REG_BINARY%,  04,25,00,23,09,20,10,01,00,02,b8,88,00,00,00,02,01,01,b8,88,00,00,02,02,11,02,00

00,00,00,02,01,11,02,00,00,00,00,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,3f

3e,00,00,37,36,00,00,51,50,00,00,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

ff,ff,ff,ff,ff,ff,ff,ff,ff

[Mobile_Tweaks]

HKR,, EnableAGPSBA,                  %REG_DWORD%,    0

HKR,, MapOSD3ToNV,                  %REG_DWORD%,    3

HKR,, MapOSD4ToNV,                  %REG_DWORD%,    3

HKR,, PowerSaverHsyncOn,            %REG_DWORD%,    1

HKR,, SoftEDIDs,                    %REG_DWORD%,    1

HKR,, UseHWSelectedDevice,          %REG_DWORD%,    1

;if upon reboot after install you have a black screen remove the ';' from line below and reinstall driver.

;HKR,, ModesetBlankDelay,            %REG_DWORD%,    1

; should you experienceproblems with Standby/Hibernate resume then change the following like above

;HKR,, MapOSD3ToNV,                  %REG_DWORD%,    2

[®®®]

Didn't mean to generally change the value from 2 to 3, but only for certain GPUs where we know they need it :) which would also keep the INF small.

What i saw in some original OEM iNFs looked roughly like this (using AddReg).

[NVIDIA.Mfg]

%NVIDIA_NV17.DEV_0177.1% = nv4_mobile_maposd3tonv, PCI\VEN_10DE&DEV_0177

[nv4_mobile_maposd3tonv.SoftwareSettings]

.... (standard mobile settings)

AddReg = nv_MapOSD3ToNV

.... (standard mobile settings)

[nv_MapOSD3ToNV]

HKR,,MapOSD3ToNV, %REG_DWORD%, 3

Would that be possible or easily to implement? If not i don't have a problem, but once in a while the standby problem pops up from users who aren't aware of the MAPOSD3 setting, Teraphy's INF enhancer page or obviously never had a look in the INF (not to blame them !, i made my mind with that and revise my statement from some months ago 'they should not be here' :) )

//edit i corrected it in red

Edited February 3, 2005 by ®®®

[mobilenvidia]

Not that simple I'm affraid, I would have to make 2 seperate sections of all these headings:

[nv4_mobile_nv1x]CopyFiles    = nv4.Miniport, nv.Display, nv4.icd, nv.Panel, nv.Help, nv.nViewPanel, nv.nViewHelp

DelFiles     = nv.oldrm, nv.delete.systemfiles

RegisterDLLs = nv.RegisterCPL

[nv4_mobile_nv1x.CoInstallers]

CopyFiles = nv.CoInstaller

AddReg    = nv_CoInstaller_AddReg

[nv4_mobile_nv1x.SoftwareSettings]

AddReg = nv_SoftwareDeviceSettings

AddReg = nv4_icdSoftwareSettings

AddReg = nv_ControlPanelSettings

AddReg = Mobile_Tweaks

AddReg = MapOSD3ToNV_2

DelReg = nv_ClearRegistrySwitches

[nv4_mobile_nv1x.Services]

AddService = nv,    0x00000002, nv4_Generic_Service_Inst, nv4_EventLog_Inst

AddService = NVSvc, 0x00000000, nv_NVSVC_Inst

DelService = nvarch

DelService = nvgfx

[nv4_mobile_nv1x.GeneralConfigData]

MaximumDeviceMemoryConfiguration = 80

MaximumNumberOfDevices           = 4

[nv4_WSApps_mobile_nv1x]

CopyFiles    = nv4.Miniport, nv.Display, nv4.icd, nv.Panel, nv.Help, nv.nViewPanel, nv.nViewHelp

DelFiles     = nv.oldrm, nv.delete.systemfiles

RegisterDLLs = nv.RegisterCPL

[nv4_WSApps_mobile_nv1x.CoInstallers]

CopyFiles = nv.CoInstaller

AddReg    = nv_CoInstaller_AddReg

AddReg    = nv_CoInstaller_nView_Quadro_AddReg, nv_CoInstaller_WSApps_AddReg

[nv4_WSApps_mobile_nv1x.SoftwareSettings]

AddReg = nv_SoftwareDeviceSettings

AddReg = nv4_icdSoftwareSettings

AddReg = nv_ControlPanelSettings

AddReg = Mobile_Tweaks

AddReg = MapOSD3ToNV_2

AddReg = nv_WSApps_AddReg

AddReg = nv_OGLFlatPanelScaler

AddReg = nv_UseUncachedPCIMappings

DelReg = nv_ClearRegistrySwitches

[nv4_WSApps_mobile_nv1x.Services]

AddService = nv,    0x00000002, nv4_Generic_Service_Inst, nv4_EventLog_Inst

AddService = NVSvc, 0x00000000, nv_NVSVC_Inst

DelService = nvarch

DelService = nvgfx

[nv4_WSApps_mobile_nv1x.GeneralConfigData]

MaximumDeviceMemoryConfiguration = 80

MaximumNumberOfDevices           = 4

[nv4_mobile]

CopyFiles    = nv4.Miniport, nv.Display, nv4.icd, nv.Panel, nv.Help, nv.nViewPanel, nv.nViewHelp

DelFiles     = nv.oldrm, nv.delete.systemfiles

RegisterDLLs = nv.RegisterCPL

[nv4_mobile.CoInstallers]

CopyFiles = nv.CoInstaller

AddReg    = nv_CoInstaller_AddReg

[nv4_mobile.SoftwareSettings]

AddReg = nv_SoftwareDeviceSettings

AddReg = nv4_icdSoftwareSettings

AddReg = nv_ControlPanelSettings

AddReg = Mobile_Tweaks

AddReg = MapOSD3ToNV_3

DelReg = nv_ClearRegistrySwitches

[nv4_mobile.Services]

AddService = nv,    0x00000002, nv4_Generic_Service_Inst, nv4_EventLog_Inst

AddService = NVSvc, 0x00000000, nv_NVSVC_Inst

DelService = nvarch

DelService = nvgfx

[nv4_mobile.GeneralConfigData]

MaximumDeviceMemoryConfiguration = 80

MaximumNumberOfDevices           = 4

[nv4_WSApps_mobile]

CopyFiles    = nv4.Miniport, nv.Display, nv4.icd, nv.Panel, nv.Help, nv.nViewPanel, nv.nViewHelp

DelFiles     = nv.oldrm, nv.delete.systemfiles

RegisterDLLs = nv.RegisterCPL

[nv4_WSApps_mobile.CoInstallers]

CopyFiles = nv.CoInstaller

AddReg    = nv_CoInstaller_AddReg

AddReg    = nv_CoInstaller_nView_Quadro_AddReg, nv_CoInstaller_WSApps_AddReg

[nv4_WSApps_mobile.SoftwareSettings]

AddReg = nv_SoftwareDeviceSettings

AddReg = nv4_icdSoftwareSettings

AddReg = nv_ControlPanelSettings

AddReg = Mobile_Tweaks

AddReg = MapOSD3ToNV_3

AddReg = nv_WSApps_AddReg

AddReg = nv_OGLFlatPanelScaler

AddReg = nv_UseUncachedPCIMappings

DelReg = nv_ClearRegistrySwitches

[nv4_WSApps_mobile.Services]

AddService = nv,    0x00000002, nv4_Generic_Service_Inst, nv4_EventLog_Inst

AddService = NVSvc, 0x00000000, nv_NVSVC_Inst

DelService = nvarch

DelService = nvgfx

[nv4_WSApps_mobile.GeneralConfigData]

MaximumDeviceMemoryConfiguration = 80

MaximumNumberOfDevices           = 4

And this

[nv_SoftwareDeviceSettings]HKR,, InstalledDisplayDrivers,       %REG_MULTI_SZ%, nv4_disp

HKR,, Acceleration.Level,            %REG_DWORD%,    0

HKR,, MultiFunctionSupported,        %REG_DWORD%,    1

HKR,, NvCplEnableHardwarePage,       %REG_DWORD%,    1

HKR,, OverlayMode2,                  %REG_DWORD%,    0xF00050

HKR,, OverlayMode3,                  %REG_DWORD%,    0x10400001

HKR,, OverlayMode4,                  %REG_DWORD%,    0x3

HKR,, RotateFlag,                    %REG_DWORD%,    4

HKR,, UseBestResolution,             %REG_DWORD%,    1

HKR,, VgaCompatible,                 %REG_DWORD%,    0

HKR,, NV_Modes,                      %REG_MULTI_SZ%, "{*}S 320x200 320x240 400x300 480x360 512x384 640x400=1FFF;SHV 640x480 720x480 768x576 800x600 1024x768 1152x864 1280x720 1280x768 1280x800 1280x854 1280x960 1280x1024 1360x768 1366x768 1400x1050 1440x900 1600x900 1600x1000 1600x1024 1600x1200 1680x1050 1920x1200 1920x1440 2048x1536x8,16,32=1FFF"

HKR,, DCBOverride0,                  %REG_BINARY%,   04,25,00,22,18,20,10,01,00,02,b8,88,00,00,00,02,01,01,b8,88,00,00,02,02,11,02,00

00,00,00,02,01,11,02,00,00,00,00,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,3f

3e,00,00,37,36,00,00,51,50,00,00,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

ff,ff,ff,ff,ff,ff,ff,ff,ff

HKR,, DCBOverride1,                  %REG_BINARY%,   04,25,00,23,09,20,10,01,00,02,b8,88,00,00,00,02,01,01,b8,88,00,00,02,02,11,02,00

00,00,00,02,01,11,02,00,00,00,00,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,3f

3e,00,00,37,36,00,00,51,50,00,00,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

ff,ff,ff,ff,ff,ff,ff,ff,ff

[Mobile_Tweaks]

HKR,, EnableAGPSBA,                  %REG_DWORD%,    0

HKR,, MapOSD4ToNV,                   %REG_DWORD%,    3

HKR,, PowerSaverHsyncOn,             %REG_DWORD%,    1

HKR,, SoftEDIDs,                     %REG_DWORD%,    1

HKR,, UseHWSelectedDevice,           %REG_DWORD%,    1

;if upon reboot after install you have a black screen remove the ';' from line below and reinstall driver.

;HKR,, ModesetBlankDelay,            %REG_DWORD%,    1

[MapOSD3ToNV_2]

HKR,, MapOSD3ToNV,                   %REG_DWORD%,    2

[MapOSD3ToNV_3]

HKR,, MapOSD3ToNV,                   %REG_DWORD%,    3

And this

[NVIDIA.Mfg];Mobile PCI-ID's

%NVIDIA_NV11.DEV_0112.1% = nv4_mobile_nv1x,          PCI\VEN_10DE&DEV_0112

%NVIDIA_NV11.DEV_0113.1% = nv4_WSApps_mobile_nv1x,   PCI\VEN_10DE&DEV_0113

%NVIDIA_NV17.DEV_0174.1% = nv4_mobile_nv1x,          PCI\VEN_10DE&DEV_0174

%NVIDIA_NV17.DEV_0175.1% = nv4_mobile_nv1x,          PCI\VEN_10DE&DEV_0175

%NVIDIA_NV17.DEV_0176.1% = nv4_mobile_nv1x,          PCI\VEN_10DE&DEV_0176

%NVIDIA_NV17.DEV_0177.1% = nv4_mobile_nv1x,          PCI\VEN_10DE&DEV_0177

%NVIDIA_NV17.DEV_0179.1% = nv4_mobile_nv1x,          PCI\VEN_10DE&DEV_0179

%NVIDIA_NV17.DEV_017C.1% = nv4_WSApps_mobile_nv1x,   PCI\VEN_10DE&DEV_017C

%NVIDIA_NV17.DEV_017D.1% = nv4_mobile_nv1x,          PCI\VEN_10DE&DEV_017D

%NVIDIA_NV18.DEV_0186.1% = nv4_mobile_nv1x,          PCI\VEN_10DE&DEV_0186

%NVIDIA_NV18.DEV_0187.1% = nv4_mobile_nv1x,          PCI\VEN_10DE&DEV_0187

%NVIDIA_NV28.DEV_0286.1% = nv4_mobile,               PCI\VEN_10DE&DEV_0286

%NVIDIA_NV28.DEV_028C.1% = nv4_WSApps_mobile,        PCI\VEN_10DE&DEV_028C

%NVIDIA_NV31.DEV_0316.1% = nv4_mobile,               PCI\VEN_10DE&DEV_0316

%NVIDIA_NV31.DEV_0317.1% = nv4_mobile,               PCI\VEN_10DE&DEV_0317

%NVIDIA_NV31.DEV_031A.1% = nv4_mobile,               PCI\VEN_10DE&DEV_031A

%NVIDIA_NV31.DEV_031B.1% = nv4_mobile,               PCI\VEN_10DE&DEV_031B

%NVIDIA_NV31.DEV_031C.1% = nv4_WSApps_mobile,        PCI\VEN_10DE&DEV_031C

%NVIDIA_NV34.DEV_0324.1% = nv4_mobile,               PCI\VEN_10DE&DEV_0324

%NVIDIA_NV34.DEV_0325.1% = nv4_mobile,               PCI\VEN_10DE&DEV_0325

%NVIDIA_NV34.DEV_0328.1% = nv4_mobile,               PCI\VEN_10DE&DEV_0328

%NVIDIA_NV34.DEV_032C.1% = nv4_mobile,               PCI\VEN_10DE&DEV_032C

%NVIDIA_NV34.DEV_032D.1% = nv4_mobile,               PCI\VEN_10DE&DEV_032D

%NVIDIA_NV36.DEV_0348.1% = nv4_mobile,               PCI\VEN_10DE&DEV_0348

%NVIDIA_NV36.DEV_034C.1% = nv4_WSApps_mobile,        PCI\VEN_10DE&DEV_034C

%NVIDIA_NV41.DEV_00C8.1% = nv4_mobile,               PCI\VEN_10DE&DEV_00C8

%NVIDIA_NV41.DEV_00CC.1% = nv4_WSApps_mobile,        PCI\VEN_10DE&DEV_00CC

%NVIDIA_NV43.DEV_0146.1% = nv4_mobile,               PCI\VEN_10DE&DEV_0146

%NVIDIA_NV43.DEV_0148.1% = nv4_mobile,               PCI\VEN_10DE&DEV_0148

%NVIDIA_NV44.DEV_0167.1% = nv4_mobile,               PCI\VEN_10DE&DEV_0167

%NVIDIA_NV44.DEV_0168.1% = nv4_mobile,               PCI\VEN_10DE&DEV_0168

Attached is 71.80 with the above added.

We'll need to find folk to test it before I make it a permanent part of the INF

With the current arrangement only GPU's NV11, 17 and 18 have MapOs = 2, all the rest have MapOs=3.

INF version 30.54 remember this when testing see also post below this.

nv4_disp.inf

[mobilenvidia]

The above doesn't work for my machine, I can't resume with D3=2 and D4=3

I can resume with D3=3 and D4=3

I can also resume with D3=2 and D4 not used at all.

So attached here is D3=2 for GPU's upto NV18 and D4 is not used.

GPU's above this have D3=3 and D4=3

Could folk please test this.

INF version number 30.55 (remember this when testing)

nv4_disp.inf

[®®®]

Got rid of the old driver, cleaned out the registry, installed 71.80 with the above attached 30.55 inf, and it works fine!

MAPOS is set to 2 everywhere in the registry, Standby and Hibernation works properly. Didn't found MAPOSd4 as it's not meant to be existant for us or uses hardware default?!

[LSudlow]

Very few OEM infs include the D4 line. As far as I know, the only laptops with D4 state capability are the Centrino models.

None of the current nVidia chips have a D4 state, which is why they have to be mapped to NV3 or NV2. Some Mobile P4 machines use Centrino technology, so I include it in my inf "just in case..."

NV Chips didn't include a D3 state until the FX series, so if you have to map OSD3 to NV2, you would also have to do the same with OSD4.

Pieter, I'm not sure why you can resume with D3=3 and D4=3 unless your machine never really hits D3 and ignores the line. But in that case I don't know why D3=2 and D4=3 would fail.

One of the mysteries of computing...

:)

[®®®]

Remember the Enregy Capabilities readout in the device manager?

Mine shows D0 and D3 is supported and S3,S4,S5 (standby, hibernate and off) will all get redirected to D3 as D1 and D2 are not supported.

Here's a screenshot how to check the status

[LSudlow]

Mine's not too different. It might be interesting to catalog the different GPUs, to build an accurate database of power state capabilities.

[®®®]

then why not make a new thread :) hopefully c810 user can find it :)

[®®®]

Pieter, what does the GF2 Go show?

[LSudlow]

Not sure why I didn't think of this sooner: That panel is showing the operating system's D3 state, not the true NV power state. Presumably the driver is invisibly mapping all those D3 settings to the D2 (NV2) capabilities of your card. However, the OS still sees D3.

:)

[®®®]

:P I don't qiute understand what you mean.

The true power state is naturally always D0 (ON :) ) and my card shows D3 as the only other supported Status supported in one of the other Energy Kapazity tabs (PDCAPS_D0_SUPPORTED & PDCAPS_D3_SUPPORTED). But you mean that this is the supported mode only from the OS and not from the card itself? :) Need a coffee to make my mind about that...

Taken from the ACPI specification .pdf file:

2.4 Sleeping State Definitions

Sleeping states (Sx states) are types of sleeping states within the global sleeping state, G1. The Sx states are briefly defined below. For a detailed definition of the system behavior within each Sx state, see section 7.3.4, ?System \_Sx States.? For a detailed definition of the transitions between each of the Sx states, see section 9.1, ?Sleeping States.?

S1 Sleeping State

The S1 sleeping state is a low wake latency sleeping state. In this state, no system context is lost (CPU or chip set) and hardware maintains all system context.

S2 Sleeping State

The S2 sleeping state is a low wake latency sleeping state. This state is similar to the S1 sleeping state except that the CPU and system cache context is lost (the OS is responsible for maintaining the caches and CPU context). Control starts from the processor?s reset vector after the wake event.

S3 Sleeping State

The S3 sleeping state is a low wake latency sleeping state where all system context is lost except system memory. CPU, cache, and chip set context are lost in this state. Hardware maintains memory context and restores some CPU and L2 configuration context. Control starts from the processor?s reset

vector after the wake event.

S4 Sleeping State HIBERNATION

The S4 sleeping state is the lowest power, longest wake latency sleeping state supported by ACPI. In order to reduce power to a minimum, it is assumed that the hardware platform has powered off all devices. Platform context is maintained.

S5 Soft Off State SHUT DOWN

The S5 state is similar to the S4 state except that the OS does not save any context. The system is in the ?soft? off state and requires a complete boot when it wakes. Software uses a different state value to distinguish between the S5 state and the S4 state to allow for initial boot operations within the BIOS to distinguish whether or not the boot is going to wake from a saved memory image.

http://www.acpi.info/DOWNLOADS/ACPIspec-2-0c.pdf

And then Sx=Dx=NVx? in normal cases, but then there's MAPOSD3toNV=2 which should map the D3 state to the NV2 state, because NV3 is not supported by my card? And then there is the fact that in NV 30s to 50s driver series i always needed to have the MAPOSD3toNV value set to 3 instead of 2?

Question, questions??

Edited February 4, 2005 by ®®®

[mobilenvidia]

Mine shows the same as Dontknow's.

I would need to have D4 for more modern GPU that have Centrino CPU.

D4=3 causes problems with D3=2.

I think my v30.55 would work the best for overall results.

nv18 and lower D3=2, D4 not used at all.

nv28 and higher D3=3 and D4=3 for best of both worlds.

I'll start a new thread to do some testing, where folks can try and post results.

I'll do this later today.

[®®®]

This should be the thread :) I splitted the post from the 71.80 thread to here.

[LSudlow]

Sounds good, Pieter! But I think it might be the Centrino chipset that controls this, not the CPU. I think it's part of ACPI.

Rene, your summary is exactly right. All those D3s are being mapped to (hopefully) the best available NV state. I read somewhere NV3 wasn't available until the FX series, but it may well have been available earlier. nVidia frequently slips features into their cards before they're "officially" supposed to be available.

:)

[mobilenvidia]

All these features are also BIOS and chipset related, as the chipset will have the final control of what happens with standby/hibernate and resume.

This triggers the CPU/GPU to wake up, the settings must be stored somewhere in the Flash-RAM where the BIOS looks to see what to do.

I'm keeping the D4 setting regardless for Centrino support, I don't think a Centrino would come out with a GF4go if it does it's in the minority, and we can't make the INF individual for every case.

Now we need to find out how many lappies need D3=2

I have already proven that D3=2 and D4=3 don't work (on my machine anyway)

So have only added D4 for nv28 and above where D3=3 anyway.

This will need testing also.

Do all nv28+ GPU's work with D3=3 ?

I'll start a new thread and can refer back here for Info.

It will be less confusing to just have a testing thread.

[mobilenvidia]

Started a pinned topic http://forums.laptopvideo2go.com/index.php?showtopic=6779.

For sytems that work or not, best leave any information here keep the other thread from cluttering up.

[Guest Kno One]

first off i want to give all of you guys a big hand :) for all the hard work you've done in putting this site together and helping out those of us laptop users ignored by the major manufacturers.

ok now onto the jist of my question. as you can see my lappy has a 440go 64meg so i want to keep using the 67.66 (v30.53 inf with the blackbar fix) for better speed while gaming.

if i 'm following this ok all i need to do is replace this section

[Mobile_Tweaks]HKR,, EnableAGPSBA,                  %REG_DWORD%,    0

HKR,, MapOSD3ToNV,                  %REG_DWORD%,    3

HKR,, PowerSaverHsyncOn,            %REG_DWORD%,    1

HKR,, SoftEDIDs,                    %REG_DWORD%,    1

HKR,, UseHWSelectedDevice,          %REG_DWORD%,    1

;if upon reboot after install you have a black screen remove the ';' from line below and reinstall driver.

;HKR,, ModesetBlankDelay,            %REG_DWORD%,    1

; should you experienceproblems with Standby/Hibernate resume then change the following like above

;HKR,, MapOSD3ToNV,                  %REG_DWORD%,    2

with

[Mobile_Tweaks]HKR,, EnableAGPSBA,                  %REG_DWORD%,    0

HKR,, PowerSaverHsyncOn,            %REG_DWORD%,    1

HKR,, SoftEDIDs,                    %REG_DWORD%,    1

HKR,, UseHWSelectedDevice,          %REG_DWORD%,    1

;if upon reboot after install you have a black screen remove the ';' from line below and reinstall driver.

;HKR,, ModesetBlankDelay,            %REG_DWORD%,    1

[MapOSD3ToNV_2]

HKR,, MapOSD3ToNV,                  %REG_DWORD%,    2

[MapOSD3ToNV_3]

HKR,, MapOSD3ToNV,                  %REG_DWORD%,    3

HKR,, MapOSD4ToNV,                  %REG_DWORD%,    3

from the v30.55 inf.

is that right? or is there another (easier?) way to make the v30.55 work with the 67.66(and still keep the blackbar fix)?

i'd just try it out but i'm pretty sure this hibernation power state prob is what killed my last vid card and i dont want to risk this card as its already past the 30 day return period.

p.s. i attached my LV2GO devcon specs log file just in case it'll help out.

LaptopVideo2Go_LogFile.txt

[LSudlow]

Don't create those extra inf sections because they won't be recognized unless they are called from elsewhere in the inf.

Just change the MapOSD3toNV value in your first example from 3 to 2.

[Guest Kno One]

'k I changed the MapOSD3toNV state from 3 to 2 it helped a little bit but I'm still getting graphical errors when coming back from hybernate. They aren't as bad as before, just your basic artifacting pixels instead of the "bleeding-throu" effect i was getting, but they are still there. however it still locks up or BSOD's right afterward.

p.s. If anyone would like to see what I mean by "bleeding-throu" effect I'm sure i could photochop something up, as i can't take a screenie when it happens.

[Teraphy]

You might want to give this combo a try:

HKR,, RMMaintainDevs,              %REG_DWORD%,    1
HKR,, UseHWSelectedDevice,     %REG_DWORD%,    1