Jump to content
TimeWalker75a

OSX on DELL Vostro 3450 / Inspiron N4110 / XPS L702x UEFI Clover

1,148 posts in this topic

Recommended Posts

Advertisement

@TW, thank to mention about brightness info. i use the rehadman's default patch http://www.tonymacx86.com/hp-probook-mavericks/121031-native-brightness-working-without-blinkscreen-using-patched-applebacklight-kext.html.  After remove the config.plist patch, install the patched kext from rehadman's script and dsdt. works well. But i still have 0 step as black, so i guess you mod the script, right ?

 

One more thing, i found IOR's about backlight panel value isn't right, real mac has 0x400 max & 0x0 min, but  i have 0x28 mac & 0xff min. 

Share this post


Link to post
Share on other sites

You have two options here in regards to brightness.

1. To use native AppleBacklight kext with an injection of your panel (no need to use the kext his script produces, we have CustomPeripheral kext and we can use that). We have the info of all 3 displays found on Inspiron and Vostro.. so I've added them to CustomPeripheral injector (not sure about 02e9 display panel).

2. Use ACPIBacklight kext that allows you to have fluent and subtle transition between brightness levels like on real Mac .. but with our stupid WMI keyboard it's not really that subtle, still rough and jumpy, because driver takes time to process WMI packets before sending NX_BRIGHTNESS notifications to system.

 

You can try both if you like .. I'm still debating on which approach to use.. 

 

The intel folder includes CustomPeripheral kext with injections for bluetooth and wireless for the AzureWave Broadcom card, the kext included in amd folder doesn't. If you need these injections on your amd machine just take them from intel kext. CustomPeripheral kexts in ACPIBacklight folder are just a roll back (to the one before you tried AppleBacklight) in case you forgot to back up the kext you had before.

 

I've also included latest HWsensors (you need to replace everything)...

 

Download: https://www.dropbox.com/s/p0dio2mck58t028/Fan%2BBrightness-Control-10.9.2.zip

 

P.S. Forgot an important bit. In your config edit the 'HDMI+VGA+Brightness' patch (the start of the replace part from it) to 01020300 10070000 10070000

Share this post


Link to post
Share on other sites

@TW, thank to mention about brightness info. i use the rehadman's default patch http://www.tonymacx86.com/hp-probook-mavericks/121031-native-brightness-working-without-blinkscreen-using-patched-applebacklight-kext.html.  After remove the config.plist patch, install the patched kext from rehadman's script and dsdt. works well. But i still have 0 step as black, so i guess you mod the script, right ?

 

One more thing, i found IOR's about backlight panel value isn't right, real mac has 0x400 max & 0x0 min, but  i have 0x28 mac & 0xff min.

0 step as black is 'by design'. It is the way Macs work. My Apple MacBookAir is the same.

Share this post


Link to post
Share on other sites

Well, then clearly something is wrong with either your ACPI tables (not being injected properly) or your IO80211Family kext. Are you actually seeing the edits you make in IORegistry (like ID changing) ?

Share this post


Link to post
Share on other sites

 

 

You need to boot without caches and with injected kexts. Your hard drive on the controller is not being detected. 

 

I've booted "without caches and with injected kexts" I still cannot boot into installer, I get the message: 

 

P-State Stepper Error 18 at step 35 in context 2 on CPU 0

 

Please see the screenshots from boot

 

boot_error_05.jpg
 
boot_error_06.jpg
 
Anything else I should try?

Share this post


Link to post
Share on other sites

0 step as black is 'by design'. It is the way Macs work. My Apple MacBookAir is the same.

thx, confirm 0 step is black. may get further test from TW's package. 

Share this post


Link to post
Share on other sites

Attached files with the wifi signal and ioreg.

I fail to see any issues, make sure your kexts are ok.

 

 

 

P-State Stepper Error 18 at step 35 in context 2 on CPU 0

 
Anything else I should try?

 

Remove my SSDT table for i3-2350M and enable P and C state generation in clovers config file:

	<key>ACPI</key>
	<dict>
			…..

		<key>SSDT</key>
		<dict>
			<key>Generate</key>
			<dict>
				<key>PStates</key>
				<true/>
				<key>CStates</key>
				<true/>
			</dict>
			<key>C3Latency</key>
			<integer>250</integer>
			<key>EnableC2</key>
			<false/>
			<key>EnableC4</key>
			<false/>
			<key>EnableC6</key>
			<true/>
			<key>EnableC7</key>
			<true/>
		</dict>
	</dict>

In regards to brightness - I've fixed the bug when it would reboot with display set at full brightness after you adjust backlight in OSX. For this we need RehabMan's ACPIBacklight with subtle level changes. I've noticed that after reset CBLV VGA register is being set with value 0x80000064 and when EC queries perform AND 0xFF on it the result is 0x64 - 100% brightness. I've added a table to check against and set CBLV to a value between stock 6% to 100% with 6% increments. This way laptop reboots with about the same brightness (in BIOS, Clover or Boot Manager) as you had in OSX.

 

I left the '0' level as backlight off, since it's a feature 'by design' .. 

 

Files: https://www.dropbox.com/s/iwjhqh8tckl0n26/proper-backlight.zip

Share this post


Link to post
Share on other sites

Yes, they are ok! What I realized is that if I also remove the kext AppleRTL8169 the wired network does not work, it also was not meant to work only with placed injections in SSDT-2?

Share this post


Link to post
Share on other sites

So you are completely removing kexts and expect things to work? No comment there .. 

ACPI tables are not magical .. if there's not kernel extension for your hardware in the system it will not work.

Share this post


Link to post
Share on other sites

@TW, works well from latest acpibacklight as fan control. 

 

Edit:

i find something in the kernel log:

2/21/14 9:35:19.000 PM kernel[0]: Unable to parse max RPM for fan 1

It seems that acpisensor has detect fan control as real FAN.

Share this post


Link to post
Share on other sites

 

@TW, works well from latest acpibacklight as fan control. 

 

Edit:

i find something in the kernel log:

2/21/14 9:35:19.000 PM kernel[0]: Unable to parse max RPM for fan 1

It seems that acpisensor has detect fan control as real FAN.

 

glad it works for amd models as well. kudos to RehabMan for finishing what hotKoffy started .. I've tried the kext ages ago (in early 2012) and it didn't work at all. 

fan 1 is actually the system fan, it doesn't know (and has no way to tell) what is the maxim rpm for it. fan0 is fake fan.. and i have no way to make it something else except a fake fan, so pay no attention to it.

 

 

@timewalker75a

 

which patch you used to get control and read speed of  FAN  

my dsdt doesnt have EC device will this effect ?

none. I deciphered what the embedded controller registers are and how to control the fan, then made my own acpi tables and control logic (except average temp part, that was borrowed from Rehab's). this won't affect because you can always add what's missing.. your laptop has to have an embedded controller and you can read all the data from it from RW Everything.

Share this post


Link to post
Share on other sites

actually i learn os x from 2009, when hotKoffy create post, but i owned a laptop just has ten steps brightness, it is controlled by bios, also doesn't use WMI to control it. so there is no way know how to do it, a friend from chinese forum has a temporary idea, make 6 fake value to BCL, then it has 16 steps to adjust brightness. But the laptop is too old then i bought 14R instead. 

Share this post


Link to post
Share on other sites

glad it works for amd models as well. kudos to RehabMan for finishing what hotKoffy started .. I've tried the kext ages ago (in early 2012) and it didn't work at all. 

fan 1 is actually the system fan, it doesn't know (and has no way to tell) what is the maxim rpm for it. fan0 is fake fan.. and i have no way to make it something else except a fake fan, so pay no attention to it.

 

 

none. I deciphered what the embedded controller registers are and how to control the fan, then made my own acpi tables and control logic (except average temp part, that was borrowed from Rehab's). this won't affect because you can always add what's missing.. your laptop has to have an embedded controller and you can read all the data from it from RW Everything.

i added yours SSDT-1 

but it can't read values :/

post-378955-0-05329100-1393006036_thumb.png

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By glasgood
      CLOVER DUAL BOOT MOJAVE & WINDOWS 10 GUIDE 
       

       
       
      INCLUDES  MBR / LEGACY BIOS  TO  GPT / EFI CONVERSION
      USING MBR2GPT TOOL
       
       
      PREREQUISITE: Two physical discs ( SSD’s or HDD’s )
       
       
       
       
       
      STEP 1 - Clover dual boot configuration 
       
      Open config.plist with Clover Configurator
       
      Boot
       Legacy = PBR Timeout = True ( will remove the Timeout countdown, from Clover boot menu)  

       
      GUI 
      Scan / Custom
       Entries = True  Tool = True  Legacy = False ( removes extra Windows 10 entries )  
      Hide Volume
      - Preboot ( macOS Preboot )
      - Recovery ( macOS Recovery )
       

       
      So at boot you will have two options: boot macOS Mojave or Windows 10 
       
       
       
       
       
       
       
      ————————————————————
       
       
      STEP 2 - Using a drive without Windows 10 installed
       
      Disconnect system drive that contains your macOS Mojave install from computer ( This is so that Windows does not overwrite existing macOS Mojave boot loader )
       
      Proceed with a Windows 10 UEFI install.  
      After installation reconnect macOS Mojave Drive, the Windows installation should now be detected and usable in Clover. 
      If Windows 10 is not detected or able to boot,  then verify you installed Windows 10 as UEFI and not MBR ---->  ( Read step 2 - For a drive with Windows 10 installed )
       
       
      OR
       
       
       
      STEP 2 - Using a drive with Windows 10 already installed
       
      Verify your Windows install is  GPT / UEFI or MBR / Legacy BIOS.   
      If Windows install is GPT UEFI then Windows 10 install is ready to use at Clover boot menu, you should be able to boot into Windows directly from Clover boot screen. 
       

       
       
      But if  Windows drive is detected at Clover boot screen, but when booting Windows you get a black screen with a cursor on the top left,
      then this is most likely because Windows drive is MBR ( Legacy BIOS ).  You can easily convert MBR to GPT using  Windows MBR2GPT tool ( this saves hours work having to reinstall Windows 10 and setting up all your applications again  ) 
       
      If Windows 10 install is MBR / Legacy BIOS  then simply convert to GPT / UEFI  following instructions below ( read video summary and view video )
       
       
      ** To use Windows 10  MBR2GPT tool  you must have Windows 10 version 1703 ( creators update  ) or later and less than 3 partitions on 
      the Windows 10 drive **
       
      Video summary:
       
      Confirm Windows 10 drive is MBR Legacy BIOS ( in Windows Disk Management ) Reboot into Windows PE ( Advanced Startup ) Convert from MBR Legacy BIOS to GPT UEFI ( using commands below ) mbr2gpt /validate mbr2gpt /convert Restart Verify Windows 10 drive has changed to GPT UEFI ( in Windows Disk Management )  
       
       
       
      After conversion Windows 10 is ready to use at the Clover boot menu 
       
       
       
      STEP 3 - Stop Windows Boot manager from overriding Clover boot manager
       
      How to stop Windows boot manager from overriding your Hackintosh Clover boot manager when using dual booting between macOS and Windows
       
       
       
       
       
       
    • By SoThOr
      This was spurred on from a discussion in the Clover General thread. Where there was a debate on bcdedit being able create/read/edit (U)EFI Boot entries. I didn't think it appropriate to post all this information there and somebody may want to make use of this and its likely to get lost in that massive thread.
       
      Out of curiosity I decided to see if I could create an EFI entry using bcdedit. What can I say I like a challenge.  Whilst is not a documented method by Microsoft, as it turns out in a round about way it IS possible to create an EFI entry using bcdedit and these are the steps I went through to add UEFI Shell located on a USB stick to the EFI entries. 
       
      Third party software is available that can create and edit UEFI entries from Windows with better support and more features. I'm just making this information available in case those options are unavailable. 
       
      DISCLAIMER - This is not a supported method. Use at your own risk. I recommend backing up your BCD/Firmware variables/settings beforehand.
       
      1) Copy {bootmgr} entry.
      C:\Windows\System32>bcdedit /copy {bootmgr} /d "UEFI Shell" The entry was successfully copied to {34e8383c-73a7-11e9-9cb0-94de8078a7b5}. 2) Edit the new entry using the new GUID bcdedit generated in the copy step.
        a) Set the device and path for UEFI shell on my USB stick.
      bcdedit /set {34e8383d-73a7-11e9-9cb0-94de8078a7b5} device partition=G: bcdedit /set {34e8383d-73a7-11e9-9cb0-94de8078a7b5} path \EFI\SHELL\SHELLX64.efi   b) Clean up some of the stuff that was copied from {bootmgr} (optional as far as I can tell, just makes things tidier in bcdedit)
      3) Put the new EFI entry first in boot order. (optional)
       
      After completing the steps above, here is what "bcdedit /enum firmware" shows:
       
      I shutdown my computer and when I turned my computer back on it booted up into UEFI Shell. After exiting the shell my PC went on to boot Windows.
      Here is the resulting dump using "bcfg boot dump -v" from that shell:
       
      You may notice that the shell shows as "Windows Boot Manager" in the bcdedit output. This I believe is because of the "WINDOWS" at the beginning of the option data that bcdedit added to the EFI Boot entry. I also believe this why bcdedit shows my Windows 8 installation as "Firmware Application" because it has no option data. I don't know how to remove this data using bcdedit nor do I know how the option data, that bcdedit adds, will affect other EFI applications.

      There might be a way to create the EFI entry without copying the Windows entry but if there is I'm unable to find any documentation on how one would do so. If you use the create command then it just puts it in the BCD and I'm unaware of a way to tell it to create it in EFI instead, other than by doing the above.
    • By cvad
      Small tool to download, compile and build the latest Clover X64 package.
       
       
       

      The script inside is editable.

       
      Enjoy...
       
      Many thanks to the comrade SunKi for help with creating the script.
       
       
       
       
       
      Best thanks - click "Rate File".
       
    • By blxkspell
      Hey!
      As I have 3 Monitors connected, my RX 570 gets arround 50°C while ideling/ web browsing etc. The problem is, that this temp is apparently just the threshold, when the fans start to spin. So the fans start spinning for a minute then they stop for a while again... This is very annoying for me as the rest of my hackintosh is nearly quiet (SSD, 120mm low RPM cpu fan, nearly silent PSU,...), especially when Im using the pc to revise for school. Does somebody know wether its possible to "change" the threshold till the fans start spinning? Like it would probably not be a problem for the gpu at all, if the temp rises to 55°C but therefore be soundless....
       
       
×