Contribute
Register

[Guide] HP ProBook/EliteBook/Zbook using Clover UEFI hotpatch (10.11)

Status
Not open for further replies.
it does not go to sleep. it makes that sound just like i would have pressed and hold down a key (press F1 on your desktop and hold it that is the sound). and the sound it keeps on going for some time like 15 seconds and then stops, after a minute or so sound comes up again . - all this time the laptop does not sleep .

if i open the switch meanwhile that sound is playing display light's on with the sound keeping rolling and if i press a key on the keyboard the sound stops. (open switch=remove the magnet)
 
liniaunu said:
it does not go to sleep. it makes that sound just like i would have pressed and hold down a key (press F1 on your desktop and hold it that is the sound). and the sound it keeps on going for some time like 15 seconds and then stops, after a minute or so sound comes up again . - all this time the laptop does not sleep .
Click to expand...

You didn't mention it, but I assume this happens after the 15-20 sec delay.
Correct?
(details matter in this game)
 
WhenMusicAttacks said:
Sadly, i cannot, tried while on 1.39 with official hp installer for 1.37 and also by creating usb recovery bios key.
Attached ACPI from 1.37. I hae to say i did not check wich state i left his bios DVMT setting. I hope i left it 64 or it does not matter...
Click to expand...

No real differences in the two BIOS as far as ACPI except for the additional SSDT in the 1.39 case (may be different options set in BIOS, or different hardware in the laptop).

So the change must be somewhere else. The way BIOS initializes the graphics hardware perhaps. Or just different BIOS settings between the two cases.
 
liniaunu said:
if i open the switch meanwhile that sound is playing display light's on with the sound keeping rolling and if i press a key on the keyboard the sound stops. (open
Click to expand...

if after doing like the above i once again close the switch it goes to sleep , but after i open it (power button) and closed the switch once again the sound started immediately and did not sleep, opens the switch again, hitting a key on the keyboard stopes the sound , and if i closed the switch once more it sleeped.
 
liniaunu said:
if after doing like the above i once again close the switch it goes to sleep , but after i open it (power button) and closed the switch once again the sound started immediately and did not sleep, opens the switch again, hitting a key on the keyboard stopes the sound , and if i closed the switch once more it sleeped.
Click to expand...

If you have some C++ skills, you might want to experiment with the code that executes upon sleep.
This is from VoodooPS2Controller.cpp:
Code: 
void ApplePS2Controller::setPowerStateGated( UInt32 powerState )
{
  if ( _currentPowerState != powerState )
  {
    switch ( powerState )
    {
      case kPS2PowerStateSleep:

        //
        // 1. Make sure clocks are enabled, but IRQ lines held low.
        //
       
        ++_ignoreInterrupts;
        DEBUG_LOG("%s: setCommandByte for sleep 1\n", getName());
        setCommandByte(0, kCB_EnableKeyboardIRQ | kCB_EnableMouseIRQ);
       
        // 2. Notify clients about the state change. Clients can issue
        //    synchronous requests thanks to the recursive lock.
        //    First Mouse, then Keyboard.
           
        dispatchDriverPowerControl( kPS2C_DisableDevice, kDT_Mouse );
        dispatchDriverPowerControl( kPS2C_DisableDevice, kDT_Keyboard );

        // 3. Freeze the request queue and drop all data received over
        //    the PS/2 port.

        _hardwareOffline = true;

        // 4. Disable the PS/2 port.

#if DISABLE_CLOCKS_IRQS_BEFORE_SLEEP
        // This will cause some machines to turn on the LCD after the
        // ACPI display driver has turned it off. With a real display
        // driver present, this block of code can be uncommented (?).

        DEBUG_LOG("%s: setCommandByte for sleep 2\n", getName());
        setCommandByte(kCB_DisableKeyboardClock | kCB_DisableMouseClock, 0);
#endif // DISABLE_CLOCKS_IRQS_BEFORE_SLEEP
        break;

...
 
and it, s going on in cycle like this: one no(sleeps) sound comes up hit a button then next try is working, third time not working -pressing key on keyboard , 4th time working. and so on
 
liniaunu said:
and it, s going on in cycle like this: one no(sleeps) sound comes up hit a button then next try is working, third time not working -pressing key on keyboard , 4th time working. and so on
Click to expand...

Once the PS2 kext is setup for sleep, PS2 interrupts should stop, and no more keys should come through.
If that is not working, you will get the behavior you describe...

I think you will need to do some debugging to further determine what is going on.
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top