Latitude E6330

[ghorwith]

Don't know how the stuff I injected became so different. Will have to go back and examine it. Anyway, I injected the EDID into the dsdt and now I don't have to push the power button when it goes into sleep at boot, but otherwise behavior is the same. Upon booting, it initially goes into sleep for a few seconds, and now comes back to life with the logon screen. After booting, going into sleep manually produces the same scenario. After a few seconds it starts up again. However, shutdown does work. Also, the issues with the monitors remains the same. If the external is connected at boot, it's the only one seen. If connected after the logon screen, both are seen.

Any caveats with regard to the bios settings (other than of course AHCI) that might cause this?

 

[RehabMan]

Don't know how the stuff I injected became so different. Will have to go back and examine it. Anyway, I injected the EDID into the dsdt and now I don't have to push the power button when it goes into sleep at boot, but otherwise behavior is the same. Upon booting, it initially goes into sleep for a few seconds, and now comes back to life with the logon screen. After booting, going into sleep manually produces the same scenario. After a few seconds it starts up again. However, shutdown does work. Also, the issues with the monitors remains the same. If the external is connected at boot, it's the only one seen. If connected after the logon screen, both are seen.

Any caveats with regard to the bios settings (other than of course AHCI) that might cause this?

Check BIOS for "wake on Lan" or "wake on USB". You should probably also look at doing the standard EHCI DSDT patches for USB. See: https://github.com/RehabMan/HP-ProBook-4x30s-DSDT-Patch/blob/master/02b_EHCI_4x40s.txt

I'm really not sure what would cause the system to go into sleep upon boot. That's just really strange. Have you thought of doing a fresh install retracing your steps to see what might be causing that behavior?

Also, post your ioreg with failed built-in panel (eg. external connected at boot...).

 

[ghorwith]

Bios has wake on usb and lan disabled. Just noticed something else that may lend some help. When I boot with the external monitor connected, as I described before, the initial part of the boot screen is on the laptop lcd, but then the external monitor fires up with the logon screen (i.e. becomes the primary display). After logging on, if I manually put the computer to sleep, it starts up again after a few seconds, but this time both monitors start up [as configured in system preferences] with the primary switched back to the laptop lcd and the extended screen on the external monitor. Gremlins for Labor Day weekend ;-)

 

[RehabMan]

Bios has wake on usb and lan disabled. Just noticed something else that may lend some help. When I boot with the external monitor connected, as I described before, the initial part of the boot screen is on the laptop lcd, but then the external monitor fires up with the logon screen (i.e. becomes the primary display). After logging on, if I manually put the computer to sleep, it starts up again after a few seconds, but this time both monitors start up [as configured in system preferences] with the primary switched back to the laptop lcd and the extended screen on the external monitor. Gremlins for Labor Day weekend ;-)

Sure sounds like bad EDID pickup... Post your IOREG dump just after boot w/ external monitor connected. Maybe there is a clue there...

For immediate wake after sleep, look at system.log, search for 'wake reason'...

 

[ghorwith]

Aug 30 07:01:01 --- last message repeated 3 times ---
Aug 30 07:01:01 localhost WindowServer[71]: Display 0x3900d300: MappedDisplay Unit 0; ColorProfile { 2, "Display"}; TransferFormula (1.000000, 1.000000, 1.000000)
Aug 30 07:01:01 localhost WindowServer[71]: Display 0x2b284a17: MappedDisplay Unit 3; ColorProfile { 3, "DELL P2412H"}; TransferFormula (1.000000, 1.000000, 1.000000)
Aug 30 07:01:01 localhost WindowServer[71]: Display 0x3900d300: MappedDisplay Unit 0; ColorProfile { 2, "Display"}; TransferFormula (1.000000, 1.000000, 1.000000)
Aug 30 07:01:01 --- last message repeated 1 time ---
Aug 30 07:01:01 localhost WindowServer[71]: Display 0x2b284a17: MappedDisplay Unit 3; ColorProfile { 3, "DELL P2412H"}; TransferFormula (1.000000, 1.000000, 1.000000)
Aug 30 07:01:01 localhost WindowServer[71]: Display 0x3900d300: MappedDisplay Unit 0; ColorProfile { 2, "Display"}; TransferFormula (1.000000, 1.000000, 1.000000)
Aug 30 07:01:01 localhost WindowServer[71]: Display 0x2b284a17: MappedDisplay Unit 3; ColorProfile { 3, "DELL P2412H"}; TransferFormula (1.000000, 1.000000, 1.000000)
Aug 30 07:01:01 --- last message repeated 1 time ---
Aug 30 07:01:01 localhost WindowServer[71]: Display 0x3900d300: MappedDisplay Unit 0; ColorProfile { 2, "Display"}; TransferFormula (1.000000, 1.000000, 1.000000)
Aug 30 07:01:01 --- last message repeated 1 time ---
Aug 30 07:01:01 localhost WindowServer[71]: Display 0x2b284a17: MappedDisplay Unit 3; ColorProfile { 3, "DELL P2412H"}; TransferFormula (1.000000, 1.000000, 1.000000)
Aug 30 07:01:01 --- last message repeated 1 time ---
Aug 30 07:01:01 localhost WindowServer[71]: Display 0x3900d300: MappedDisplay Unit 0; ColorProfile { 2, "Display"}; TransferFormula (1.000000, 1.000000, 1.000000)
Aug 30 07:01:01 --- last message repeated 1 time ---
Aug 30 07:01:01 localhost WindowServer[71]: Display 0x2b284a17: MappedDisplay Unit 3; ColorProfile { 3, "DELL P2412H"}; TransferFormula (1.000000, 1.000000, 1.000000)
Aug 30 07:01:31 --- last message repeated 1 time ---
Aug 30 07:02:46 localhost kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=204[ksadmin] clearing CS_VALID
Aug 30 07:02:46 localhost kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=208[ksadmin] clearing CS_VALID
Aug 30 07:13:18 localhost coreaudiod[141]: Disabled automatic stack shots because audio IO is active
Aug 30 07:13:28 localhost coreaudiod[141]: Enabled automatic stack shots because audio IO is inactive
Aug 30 07:18:58 localhost coreaudiod[141]: Disabled automatic stack shots because audio IO is active
Aug 30 07:19:03 localhost coreaudiod[141]: Enabled automatic stack shots because audio IO is inactive


Aug 30 07:00:56 localhost kernel[0]: Wake reason = XHC

 

[RehabMan]

Aug 30 07:01:01 --- last message repeated 3 times ---
...
Aug 30 07:00:56 localhost kernel[0]: Wake reason = XHC

USB3 is waking your computer. Are you using GenericUSBXHCI or just native kexts?

From ioreg you can see both AppleDisplay (framebuffer@3) and AppleBacklightDisplay (framebuffer@0) present (which is good). I wonder if it is a brightness issue? Do you have brightness up/down keys working? Have you tried using them?

Probably unrelated, but I also notice you have Sandy Bridge power management, but Ivy CPU and Ivy sysdef (MacBookPro9,2). You might want to generate a proper SSDT (you can use the ProBook Installer for this). Make sure to use stock AppleACPIPlatform, GeneratePStates=No, GenerateCStates=No, and DropSSDT=Yes. Or you could switch to a Sandy sysdef...

Edit: Actually I see you are using GenericUSBXHCI. You might take a look at the boot flags associated with that driver there are some specifically for sleep issues and the Intel chipset.

Edit2: Experiment... Install blinkscreen from ProBook Installer. Boot with external display connected. Login. Screen should blink off/on after login. What happens to internal display?

 

[ghorwith]

USB3 is waking your computer. Are you using GenericUSBXHCI or just native kexts?

From ioreg you can see both AppleDisplay (framebuffer@3) and AppleBacklightDisplay (framebuffer@0) present (which is good). I wonder if it is a brightness issue? Do you have brightness up/down keys working? Yes, it works.Have you tried using them?

Probably unrelated, but I also notice you have Sandy Bridge power management, but Ivy CPU and Ivy sysdef (MacBookPro9,2). You might want to generate a proper SSDT (you can use the ProBook Installer for this). Make sure to use stock AppleACPIPlatform, GeneratePStates=No, GenerateCStates=No, and DropSSDT=Yes. Generated SSDT and all other switches are as suggestedOr you could switch to a Sandy sysdef...

Edit: Actually I see you are using GenericUSBXHCI. You might take a look at the boot flags associated with that driver there are some specifically for sleep issues and the Intel chipset.The only switch that had an effect was -gux_nosleep. As I read the documentation, it should prevent sleep. Instead, the switch allows sleep as expected. So, I would assume there's a toggle effect and for some reason when I boot, sleep mode is toggled 'off'.

Edit2: Experiment... Install blinkscreen from ProBook Installer. Boot with external display connected. Login. Screen should blink off/on after login. What happens to internal display? It does cause the external display to blink, but unfortunately doesn't start the laptop lcd.

See above

 

[RehabMan]

See above

By "yes it works" wrt brightness keys, do you mean if you hit brightness up while having no laptop display that the display lights up?

Post ioreg again, if you want me to look at/verify your power management situation...

Let me know how the blinkscreen thing turns out...

 

[ghorwith]

When the laptop first boots and I have only the external display, the brightness keys do nothing. After I sleep and resume, the laptop display wakes up, and the brightness keys control the laptop display as expected. Blinkscreen blinks the external display after logon.

 

[RehabMan]

When the laptop first boots and I have only the external display, the brightness keys do nothing. After I sleep and resume, the laptop display wakes up, and the brightness keys control the laptop display as expected. Blinkscreen blinks the external display after logon.

Looks like you have Ivy PM loading now... You could test pstates with DPCIManager or MSRdumper.kext...

The only other thing I can think of wrt laptop display would be to rename GFX0 to IGPU (in DSDT). But that has more to do with power management than anything. Too bad a display sleep doesn't help you there. I have no other ideas right now...