Contribute
Register

HP Envy 15t-J100; Trouble booting from HD and problems with Chimera

Status
Not open for further replies.
Thats the guide I followed. I've successfully gotten it to work on my desktop when using multiple hard drives but It doesn't work on my laptop. Both OSes are on separate partitions on the same drive in my laptop... Its weird, Mac sees the windows partition as MS DOS FAT but can't mount it. Windows sees the partition as NTFS... On my desktop, mac recognizes the windows drive as ntfs.

I think you didn't follow carefully enough. Likely your Windows is installed UEFI. Or you didn't follow the instructions carefully enough when using the Windows installer (you must be sure to only format the existing partition created from Disk Utility, nothing more).

Followed this, still didn't work, not too concerned though at the moment because I have larger problems and I can go without backlight - I never use it anyways.

You have no need to adjust the LCD backlight on the internal display?

It does work... you must have done something wrong. If you want me to check your work, post ioreg: http://www.tonymacx86.com/audio/58368-guide-how-make-copy-ioreg.html

After I patch my dsdt and ssdt, I am able to reboot into mac with -f and sometimes am able to reboot once more. When I reboot again however (without touch any kexts or dsdts or ssdts or plists or anything), I get the same problem as before. Is there some way that simply running mac can affect the next boot even if I'm booting without caches (-f)?

You should be sure your kernel cache can be built. Use DPCIManager to rebuild cache, and pay attention to any errors, then fix them if you have conflicting or invalid kexts installed.
 
I think you didn't follow carefully enough. Likely your Windows is installed UEFI. Or you didn't follow the instructions carefully enough when using the Windows installer (you must be sure to only format the existing partition created from Disk Utility, nothing more).

You're probably right. I did a clean install and am not getting this problem!


You have no need to adjust the LCD backlight on the internal display?

It does work... you must have done something wrong. If you want me to check your work, post ioreg: http://www.tonymacx86.com/audio/58368-guide-how-make-copy-ioreg.html

A copy of my ioreg is attached.

You should be sure your kernel cache can be built. Use DPCIManager to rebuild cache, and pay attention to any errors, then fix them if you have conflicting or invalid kexts installed.

I got it working well, had to be booted without caches though (-f). I edited my boot.plist and it got messed up again. Not sure why. Are DSDTs and SSDts dependent on the org.chameleon.boot.plist file at all? or on any of the kexts?! I did run DPCIManager and though there were warnings, there were no errors. A copy of that is also attached. It doesn't look like there is any problem building a cache so I'm not sure why I need to boot -f.
 

Attachments

  • DPCIManager Rebuild Cache Output.jpg
    DPCIManager Rebuild Cache Output.jpg
    196.7 KB · Views: 99
  • Saribe0's IOReg.ioreg
    1.3 MB · Views: 84
A copy of my ioreg is attached.

From ioreg/bootlog there is no evidence of a patched DSDT/SSDT being loaded.

I got it working well, had to be booted without caches though (-f). I edited my boot.plist and it got messed up again. Not sure why. Are DSDTs and SSDts dependent on the org.chameleon.boot.plist file at all? or on any of the kexts?! I did run DPCIManager and though there were warnings, there were no errors. A copy of that is also attached. It doesn't look like there is any problem building a cache so I'm not sure why I need to boot -f.

Cache rebuild looks ok. Use -v to troubleshoot.
 
From ioreg/bootlog there is no evidence of a patched DSDT/SSDT being loaded.

Cache rebuild looks ok. Use -v to troubleshoot.

-v says that a custom dsdt and a custom ssdt are being loaded during the initial boot phase (checked useing wait=yes)... could they not be running after? If so, how do I get them to load, shouldn't chameleon automatically load them? Also things like the battery work...is it possible only the part of the dsdt/ssdt responsible for backlight isn't loading???

Also, while looking at my ssdts, I noticed that ssdt5 has many GFX0 occurrences. The Device GFX0 is in ssdt4 though. I tried changing them to IGPU and placing that ssdt in the extra folder and because all the other occurrences were changed to that but I got a kernel panic (in safe mode as well). Should I edit this ssdt at all? I'm thinking I have it because I have the graphics card but I'm not sure what to do with it... (I deleted the file via terminal from the installer so I'm back to where I was before.)
 
-v says that a custom dsdt and a custom ssdt are being loaded during the initial boot phase (checked useing wait=yes)... could they not be running after? If so, how do I get them to load, shouldn't chameleon automatically load them? Also things like the battery work...is it possible only the part of the dsdt/ssdt responsible for backlight isn't loading???

I did not see them in your bootlog. But you are using a weird bootloader. Perhaps install Chameleon instead: http://www.insanelymac.com/forum/topic/231075-chameleon-22svn-official-pkg-installer-binaries/

Also, while looking at my ssdts, I noticed that ssdt5 has many GFX0 occurrences. The Device GFX0 is in ssdt4 though. I tried changing them to IGPU and placing that ssdt in the extra folder and because all the other occurrences were changed to that but I got a kernel panic (in safe mode as well). Should I edit this ssdt at all? I'm thinking I have it because I have the graphics card but I'm not sure what to do with it... (I deleted the file via terminal from the installer so I'm back to where I was before.)

For each SSDT you plan to include you should do the GFX0->IGPU rename if it includes references to GFX0. Also, keep in mind that Chameleon will stop loading SSDTs at the first SSDT it does not find. It loads in this sequence: SSDT.aml, SSDT-1.aml, SSDT-2.aml, SSDT-3.aml, etc. It stops when it fails to find an SSDT in the sequence.

For a good template on patching the Envy DSDT/SSDT, see: https://github.com/RehabMan/HP-Envy-DSDT-Patch
 
Sorry I haven't responded in so long... I haven't really had a chance to work on my laptop until recently. Anyways, I did a fresh install and I'm running into the same problem as before - I can only boot in safe mode. I am using a patched DSDT and two patched SSDTs (from SSDT-4 and SSDT-5). The patches I applied are below as well as a description of what else I installed.

I have attached my DSDT and SSDTs (patched and unpatched versions) as well as a copy of my IOReg. I'm not sure why I'm not able to boot without using safe mode. Any advice would be extremely helpful!



Other things installed:
ACPIBacklight.kext (from https://github.com/RehabMan/OS-X-ACPI-Backlight)
ACPIBatteryManager.kext (from https://github.com/RehabMan/OS-X-ACPI-Battery-Driver)
FakeSMC.kext
RealtekRTL8111.kext
VoodooPS2Controller and associated plugins etc (from https://bitbucket.org/RehabMan/os-x-voodoo-ps2-controller/downloads)
FileNVRAM.dylib
KernalPatcher.dylib
Keylayout.dylib
Chimera 2.2.1 with a theme
Patched Mac Kernel for Haswell cpus (from

DSDT edits:
syntax_dsdt.txt
remove_wmi.txt
patches.txt (only the stuff in the for dsdt section)
audio_HDEF_layout12.txt
battery_HP-Envy-17t.txt
graphics_Rename-GFX0.txt
system_MCHC.txt
system_OSYS.txt
system_IRQ.txt
system_WAK2.txt
usb_7-series.txt

SSDT4 edits (renamed to SSDT upon installation)
graphics_Rename-GFX0.txt
graphics_PNLF_haswell.txt

SSDT5 edits (renamed to SSDT-1 upon installation
graphics_Rename-GFX0.txt

Note: I have tried deleting all the Nvidia drivers but it didn't change anything.

All edits are from https://github.com/RehabMan/HP-Envy-DSDT-Patch and https://github.com/RehabMan/Laptop-DSDT-Patch
 

Attachments

  • saribe0's files.zip
    445.9 KB · Views: 60
Sorry I haven't responded in so long... I haven't really had a chance to work on my laptop until recently. Anyways, I did a fresh install and I'm running into the same problem as before - I can only boot in safe mode. I am using a patched DSDT and two patched SSDTs (from SSDT-4 and SSDT-5). The patches I applied are below as well as a description of what else I installed.

I have attached my DSDT and SSDTs (patched and unpatched versions) as well as a copy of my IOReg. I'm not sure why I'm not able to boot without using safe mode. Any advice would be extremely helpful!



Other things installed:
ACPIBacklight.kext (from https://github.com/RehabMan/OS-X-ACPI-Backlight)
ACPIBatteryManager.kext (from https://github.com/RehabMan/OS-X-ACPI-Battery-Driver)
FakeSMC.kext
RealtekRTL8111.kext
VoodooPS2Controller and associated plugins etc (from https://bitbucket.org/RehabMan/os-x-voodoo-ps2-controller/downloads)
FileNVRAM.dylib
KernalPatcher.dylib
Keylayout.dylib
Chimera 2.2.1 with a theme
Patched Mac Kernel for Haswell cpus (from

DSDT edits:
syntax_dsdt.txt
remove_wmi.txt
patches.txt (only the stuff in the for dsdt section)
audio_HDEF_layout12.txt
battery_HP-Envy-17t.txt
graphics_Rename-GFX0.txt
system_MCHC.txt
system_OSYS.txt
system_IRQ.txt
system_WAK2.txt
usb_7-series.txt

SSDT4 edits (renamed to SSDT upon installation)
graphics_Rename-GFX0.txt
graphics_PNLF_haswell.txt

SSDT5 edits (renamed to SSDT-1 upon installation
graphics_Rename-GFX0.txt

Note: I have tried deleting all the Nvidia drivers but it didn't change anything.

All edits are from https://github.com/RehabMan/HP-Envy-DSDT-Patch and https://github.com/RehabMan/Laptop-DSDT-Patch

You're not injecting an ig-platform-id. If you use Chimera, install Chimera3.

Then use: IGPlatformID=0a260006 IGPEnabler=Yes

Also, when you go to implement correct power management, you might want to rename your SSDTs such that you can have the generated CPU SSDT as SSDT.aml.

Also, MacBookPro11,2 would be a more appropriate smbios.

Unless everything is working with AppleUSBXHCI, You will want to use GenericUSBXHCI.kext and -gux_defer_usb2 kernel flag to avoid USB sleep issues.

As far as DSDT patches, take a close look at my envy repo. As a for example, patches.txt is not used anymore and has been removed. And keyboard.txt will enable your brightness keys.
 
You're not injecting an ig-platform-id. If you use Chimera, install Chimera3.

Then use: IGPlatformID=0a260006 IGPEnabler=Yes
I did this but I'm still running into the same problem...

Also, when you go to implement correct power management, you might want to rename your SSDTs such that you can have the generated CPU SSDT as SSDT.aml.
Which ssdt would this be?! I'm assuming its SSDT3, however others also have cpu objects (I think?). Also, do I need to edit this ssdt at all? I tried copying SSDT3 to /Extra as SSDT and it didn't change anything.

Also, MacBookPro11,2 would be a more appropriate smbios.
How do I find a smbios with this configuration? Chameleon Wizard's greatest option is 10,1. I tried using it but it didn't change anything either. Should I manually just edit the title to be 11,2?

Unless everything is working with AppleUSBXHCI, You will want to use GenericUSBXHCI.kext and -gux_defer_usb2 kernel flag to avoid USB sleep issues.
I will look into this after getting it to boot without safe m

As far as DSDT patches, take a close look at my envy repo. As a for example, patches.txt is not used anymore and has been removed. And keyboard.txt will enable your brightness keys.
Are there any other patches I should change? I repatched my DSDT without the patches.txt patch and with the keyboard.txt but it didn't allow me to boot without -x. I thought I was taking a close look at the envy repo when I patched it originally... Is there any place that explains what each patch does?

Also, how would I edit my DSDT or SSDTs to turn off Nvidia graphics? I've been looking for a source to explain what to do but none of them have made sense to me.
 
I did this but I'm still running into the same problem...

Boot however you can to get into the system (with those flags and -x maybe?). Then post ioreg.

Which ssdt would this be?! I'm assuming its SSDT3, however others also have cpu objects (I think?). Also, do I need to edit this ssdt at all? I tried copying SSDT3 to /Extra as SSDT and it didn't change anything.

Generally we use /Extra/ssdt.aml as the generated CPU power management SSDT (generated from Pike's ssdtPRgen.sh script or the ProBook Installer). You should not include any OEM SSDTs that contain CPU related objects.

How do I find a smbios with this configuration? Chameleon Wizard's greatest option is 10,1. I tried using it but it didn't change anything either. Should I manually just edit the title to be 11,2?

It is not just the title that matters.. board-id and ROM version are related. You should use a Haswell era smbios. iMac14,2 will work and is in Multibeast. Most correct is MacBookPro11,2. You can use Clover Configurator to get the required data and enter it manually into smbios.plist. My understanding is that the author of Chameleon Wizard is not interested in providing new versions...

I will look into this after getting it to boot without safe m

You need graphics and power management implemented before even looking at sleep...

Are there any other patches I should change? I repatched my DSDT without the patches.txt patch and with the keyboard.txt but it didn't allow me to boot without -x. I thought I was taking a close look at the envy repo when I patched it originally... Is there any place that explains what each patch does?

The repo has a README. You should read it. Keep in mind that I used Clover for this machine. I provide a config.plist for Clover. You can make it work with Chameleon/Chimera, but the way you activate graphics is specific to the bootloader (as I didn't do it in DSDT).

Also, how would I edit my DSDT or SSDTs to turn off Nvidia graphics? I've been looking for a source to explain what to do but none of them have made sense to me.

The basic idea is to call _OFF from _INI in the object that represents the discrete nvidia card. It isn't difficult, but there is a lot of details to get correct. If you were to provide all native SSDT/DSDT from Linux, I could probably look and see if the automated DSDT patch repo could be modified for it.
 
Boot however you can to get into the system (with those flags and -x maybe?). Then post ioreg.
-x is the only way. ioreg is attached.

Generally we use /Extra/ssdt.aml as the generated CPU power management SSDT (generated from Pike's ssdtPRgen.sh script or the ProBook Installer). You should not include any OEM SSDTs that contain CPU related objects.
I was not aware of this. I used Pike's script to generate the ssdt and relabeled my other ones but I found that when it was being used, I could not open applications and my fan was constantly running like crazy and my cpu was heating up. Also wouldn't restart without holding the power button. This also means that ioreg is without this ssdt, however it is included as ssdt in the attached files.

It is not just the title that matters.. board-id and ROM version are related. You should use a Haswell era smbios. iMac14,2 will work and is in Multibeast. Most correct is MacBookPro11,2. You can use Clover Configurator to get the required data and enter it manually into smbios.plist. My understanding is that the author of Chameleon Wizard is not interested in providing new versions...
Took a while to figure out, but I successfully edited my smbios.plist to be for MacBookPro11,2 using Cover Configurator which seems much more complete than Chameleon Wizard.

The repo has a README. You should read it. Keep in mind that I used Clover for this machine. I provide a config.plist for Clover. You can make it work with Chameleon/Chimera, but the way you activate graphics is specific to the bootloader (as I didn't do it in DSDT).
Graphics look like they are activated from the verbose output. I'm pretty sure my Boot.plist is right for injecting them.

The basic idea is to call _OFF from _INI in the object that represents the discrete nvidia card. It isn't difficult, but there is a lot of details to get correct. If you were to provide all native SSDT/DSDT from Linux, I could probably look and see if the automated DSDT patch repo could be modified for it.
I found the _INI method and the _OFF and _ON ones below it in SSDT-5 (labeled SSDT-2 in the attached files). I added the line "_OFF ()" at the bottom of the _INI method.

I have attached my ssdts, ioreg, and org.chameleon.Boot.plist.
 

Attachments

  • files.zip
    415.5 KB · Views: 58
Status
Not open for further replies.
Back
Top