Jump to content
arsradu

[HOW TO] Fix second stage boot logo and loading bar for some dedicated desktop video cards

389 posts in this topic

Recommended Posts

Advertisement

In my experience, you don't need a custom one. Clover does a good job at injecting the correct EDID for you monitor.

 

But on some monitors, especially on higher resolution ones (over 1080p) some people were saying that they don't have the Apple logo for the second stage boot.

 

Try to set Clover resolution to 1080p and also OS X resolution to 1080p. Just for testing purposes. See if it makes any difference.

 

Also, if your motherboard supports this feature and if you don't have any MBR-booted drives (legacy drives), you can try to turn OFF CSM in your UEFI Bios. See if that works for you.

 

Exactly, have a little bit other configuration,

2560x1440 on 13inch screen...

 

What i can say, if i set clover to 1280x720 and OS X to 1280x720 = perfect logo + perfect loading bar

if i use default 2560x1440 both, i get with "second boot fix" perfect logo + loading bar little bit distored...

without the bin patch it is completely distored on 2560x1440...

 

so I'm using hidpi mode, 1600x900 = 3200x1800, but i can't set that resolution to clover because clover can't patch integrated graphics vbios as far i know, since this vbios is inside laptops bios in core_dxe... 

edid patching won't help here, since a new modeline makes a distored screen on first draw... if you changing resolution and change back, its working... but you won't do that every time after system start :-)

 

So what i can say, use a 16:10 screen for OS X or 16:9 but anything greater 2800+ (2880xxx, 3200xxx...)

there is a hole in OS X for 16.9 resolutions from 1920xxxx till 2800xxxx...

what i mean with the hole is, distorted boot or not working hiDPI modes on 16:9 screens...

 

Dunno why, but i tested some other systems, everything else is fine :-)

 

Cheers :-)

Share this post


Link to post
Share on other sites

Just did this with my 970 on a 1440p DVI-DL screen (along with setting 1440p within Clover) and it works perfectly. The second stage isn't glitched at all - the loading bar is centered and looks perfectly and the Apple logo looks great! :D

Share this post


Link to post
Share on other sites

Just did this with my 970 on a 1440p DVI-DL screen (along with setting 1440p within Clover) and it works perfectly. The second stage isn't glitched at all - the loading bar is centered and looks perfectly and the Apple logo looks great! :D

 

Thank you very much for your feedback! And glad to hear that this works for you too.

 

What about the resolution in OS X? Is it set to 1440p, as well?

Share this post


Link to post
Share on other sites

Dunno if that was mentioned before, but at least for me, the solution was way simpler as described in this guide, so it might be of interest.

 

Really, all I had to do was adding this entry:

"@2,AAPL,boot-display", 
Buffer (One)
{
    0x00
}, 

to my GPU Device in my SSDT.

 

The whole entry currently looks like this: (I have a NVIDIA card)

Device (_SB.PCI0.NPE3.PXS1)
    {
        Name (_ADR, Zero)
        Method (_DSM, 4, NotSerialized)
        {
            If (LEqual (Arg2, Zero))
            {
                Return (Buffer (One)
                {
                    0x03
                })
            }

            Return (Package (0x12)
            {
                "AAPL,slot-name", 
                Buffer (0x0B)
                {
                    "PCI Slot 1"
                }, 

                "@0,connector-type", 
                Buffer (0x04)
                {
                    0x00, 0x08, 0x00, 0x00
                }, 

                "@1,connector-type", 
                Buffer (0x04)
                {
                    0x00, 0x08, 0x00, 0x00
                }, 

                "@2,connector-type", 
                Buffer (0x04)
                {
                    0x00, 0x08, 0x00, 0x00
                }, 

                "@2,AAPL,boot-display", 
                Buffer (One)
                {
                    0x00
                }, 

                "@3,connector-type", 
                Buffer (0x04)
                {
                    0x00, 0x08, 0x00, 0x00
                }, 

                "@4,connector-type", 
                Buffer (0x04)
                {
                    0x00, 0x08, 0x00, 0x00
                }, 

                "@5,connector-type", 
                Buffer (0x04)
                {
                    0x00, 0x08, 0x00, 0x00
                }, 

                "hda-gfx", 
                Buffer (0x0A)
                {
                    "onboard-1"
                }
            })
        }
    }   

Note that I did not have to add "Load VBIOS" in Clover, and also not "Inject EDID". Actually I was surprised that the solution was so minimalistic. Works in both 10.10 and 10.11. Of course you might need to change the connector from "@2" to something that corresponds on your System.

 

Maybe it even works if you add this entry to all availbale connectors in the SSDT, but I have not tried that.

Edit: if you do that, you will have multiple loading bars. So it should be only one entry that matches the connected main display. Just FYI

Share this post


Link to post
Share on other sites

Dunno if that was mentioned before, but at least for me, the solution was way simpler as described in this guide, so it might be of interest.

 

Really, all I had to do was adding this entry:

"@2,AAPL,boot-display", 
Buffer (One)
{
    0x00
}, 

to my GPU Device in my SSDT.

 

The whole entry currently looks like this: (I have a NVIDIA card)

Device (_SB.PCI0.NPE3.PXS1)
    {
        Name (_ADR, Zero)
        Method (_DSM, 4, NotSerialized)
        {
            If (LEqual (Arg2, Zero))
            {
                Return (Buffer (One)
                {
                    0x03
                })
            }

            Return (Package (0x12)
            {
                "AAPL,slot-name", 
                Buffer (0x0B)
                {
                    "PCI Slot 1"
                }, 

                "@0,connector-type", 
                Buffer (0x04)
                {
                    0x00, 0x08, 0x00, 0x00
                }, 

                "@1,connector-type", 
                Buffer (0x04)
                {
                    0x00, 0x08, 0x00, 0x00
                }, 

                "@2,connector-type", 
                Buffer (0x04)
                {
                    0x00, 0x08, 0x00, 0x00
                }, 

                "@2,AAPL,boot-display", 
                Buffer (One)
                {
                    0x00
                }, 

                "@3,connector-type", 
                Buffer (0x04)
                {
                    0x00, 0x08, 0x00, 0x00
                }, 

                "@4,connector-type", 
                Buffer (0x04)
                {
                    0x00, 0x08, 0x00, 0x00
                }, 

                "@5,connector-type", 
                Buffer (0x04)
                {
                    0x00, 0x08, 0x00, 0x00
                }, 

                "hda-gfx", 
                Buffer (0x0A)
                {
                    "onboard-1"
                }
            })
        }
    }   

Note that I did not have to add "Load VBIOS" in Clover, and also not "Inject EDID". Actually I was surprised that the solution was so minimalistic. Works in both 10.10 and 10.11. Of course you might need to change the connector from "@2" to something that corresponds on your System. Maybe it even works if you add this entry to all availbale connectors in the SSDT, but I have not tried that.

 

I did mention in the initial post (pretty long one, I know, but this is somewhere on the top) that this can also be achieved by using DSDT editing. Actually a few of my friends got it fixed this way. However I do not know how to do it right now (I'm still very much a noob in DSDT editing), so I can't teach others ether. :))

 

Also, you don't have to Inject EDID and Patch VBIOS if you're using an UEFI GOP Vbios (this is also mentioned on the first post :P). And even if you're not using a UEFI VBIOS, apparently not all the people need that. I needed it, so I mentioned it for other people to know about it.

 

Thanks for sharing! And also, glad it works for you! :D

Share this post


Link to post
Share on other sites

I did mention in the initial post (pretty long one, I know, but this is somewhere on the top) that this can also be achieved by using DSDT editing. Actually a few of my friends got it fixed this way. However I do not know how to do it right now (I'm still very much a noob in DSDT editing), so I can't teach others ether. :))

 

Also, you don't have to Inject EDID and Patch VBIOS if you're using an UEFI GOP Vbios (this is also mentioned on the first post :P). And even if you're not using a UEFI VBIOS, apparently not all the people need that. I needed it, so I mentioned it for other people to know about it.

 

Thanks for sharing! And also, glad it works for you! :D

 

Yeah, sorry if I may have overlooked something ;)

 

And I am absolutely no expert in DSDT editing, so if I can do it, everyone can ;)

 

So you also have some type of SSDT patch for your GPU, right? So apparently, the only thing needed is to add this entry in the _DSM method, using the correct connector adress of course.

Share this post


Link to post
Share on other sites

Yeah, sorry if I may have overlooked something ;)

 

And I am absolutely no expert in DSDT editing, so if I can do it, everyone can ;)

 

So you also have some type of SSDT patch for your GPU, right? So apparently, the only thing needed is to add this entry in the _DSM method, using the correct connector adress of course.

 

I'm not using any kind of patched SSDT/DSDT files. Only Clover patching. :D

 

I'll try to learn a bit more about it and, maybe I'll add that part as well. I think it would be a nice addition.

Share this post


Link to post
Share on other sites

Ah, understand. Even if I am not an expert I still try to avoid Clover patches when possible. And there is always something new to learn ;)

Share this post


Link to post
Share on other sites

If you would like to avoid having to patch your DSDT ever time your change your monitor setup or default you can use this DSM method,

                Device (GFX0)
                {
                    Name (_ADR, Zero)
                    Method (_DSM, 4, NotSerialized)
                    {
                        If (LEqual (Arg2, Zero))
                        {
                            Return (Buffer (One)
                            {
                                0x03
                            })
                        }

                        Return (Package (0x12)
                        {
                            "@0,AAPL,boot-display", 
                            Buffer (Zero) {}, 
                            "@0,connector-type", 
                            Buffer (0x04)
                            {
                                0x00, 0x08, 0x00, 0x00
                            }, 

                            "@1,AAPL,boot-display", 
                            Buffer (Zero) {}, 
                            "@1,connector-type", 
                            Buffer (0x04)
                            {
                                0x00, 0x08, 0x00, 0x00
                            }, 

                            "@2,AAPL,boot-display", 
                            Buffer (Zero) {}, 
                            "@2,connector-type", 
                            Buffer (0x04)
                            {
                                0x00, 0x08, 0x00, 0x00
                            }, 

                            "@3,AAPL,boot-display", 
                            Buffer (Zero) {}, 
                            "@3,connector-type", 
                            Buffer (0x04)
                            {
                                0x00, 0x08, 0x00, 0x00
                            }, 

                            "hda-gfx", 
                            Buffer (0x0A)
                            {
                                "onboard-2"
                            }
                        })

Share this post


Link to post
Share on other sites

 

If you would like to avoid having to patch your DSDT ever time your change your monitor setup or default you can use this DSM method,

                Device (GFX0)
                {
                    Name (_ADR, Zero)
                    Method (_DSM, 4, NotSerialized)
                    {
                        If (LEqual (Arg2, Zero))
                        {
                            Return (Buffer (One)
                            {
                                0x03
                            })
                        }

                        Return (Package (0x12)
                        {
                            "@0,AAPL,boot-display", 
                            Buffer (Zero) {}, 
                            "@0,connector-type", 
                            Buffer (0x04)
                            {
                                0x00, 0x08, 0x00, 0x00
                            }, 

                            "@1,AAPL,boot-display", 
                            Buffer (Zero) {}, 
                            "@1,connector-type", 
                            Buffer (0x04)
                            {
                                0x00, 0x08, 0x00, 0x00
                            }, 

                            "@2,AAPL,boot-display", 
                            Buffer (Zero) {}, 
                            "@2,connector-type", 
                            Buffer (0x04)
                            {
                                0x00, 0x08, 0x00, 0x00
                            }, 

                            "@3,AAPL,boot-display", 
                            Buffer (Zero) {}, 
                            "@3,connector-type", 
                            Buffer (0x04)
                            {
                                0x00, 0x08, 0x00, 0x00
                            }, 

                            "hda-gfx", 
                            Buffer (0x0A)
                            {
                                "onboard-2"
                            }
                        })

 

So..basically setting the same boot-display property for all ports? Did I get that part right?

Share this post


Link to post
Share on other sites

So..basically setting the same boot-display property for all ports? Did I get that part right?

 

@asradu

 

This above seems for me like boot display for every frame buffer... dunno if this is useless or not...

 

But, there must be some registers, which changes, based where your display is connected,

just need to read in the Nvidia/Amd Specification sheet...

 

Like Rehab found the BAR1 register in the Intel Graphics specification sheet... (different thing, because BAR1 is for brightness)

 

But theoretically i think its possible...

 

If we find the register it should be very easy to make an ACPI Method for this...

 

 

PS: i don't have here Nvidia/Amd Graphics, since i have on my laptop only Iris5100...

So i can't test... Im Sry...

 

Cheers :-)

Share this post


Link to post
Share on other sites

This above seems for me like boot display for every frame buffer... dunno if this is useless or not...

 

Imho, it is. When I do this, I get the Apple Logo, but also a second loading bar bottom-left, just like without the patch.

Share this post


Link to post
Share on other sites

I followed the guide and got my 2nd stage boot screen 95% working but for some reason my monitor still blinks blank before the logo/loading screen finishes?

 

Before it did the same but I didn't have the logo/loading screen properly centred as it just showed the bar on the bottom left hand corner.

 

I'm guessing this is an EDID issue with my monitor?

Share this post


Link to post
Share on other sites

I followed the guide and got my 2nd boot screen 95% working but for some reason my monitor still blinks blank before the logo/loading screen finishes?

 

Before it did the same but I didn't have the logo/loading screen properly centred as it just showed the bar on the bottom left hand corner.

Yeah, that's a glitch that most of us have (especially desktop users). Interestingly, even some real iMacs have it too. And no, I'm not sure it has anything to do with the EDID. But I might be wrong.

 

So far, that's the best we can have. When there will be a solution for that as well, I'll post it.

Share this post


Link to post
Share on other sites

Yeah, that's a glitch that most of us have (especially desktop users). Interestingly, even some real iMacs have it too. And no, I'm not sure it has anything to do with the EDID. But I might be wrong.

 

Ah OK. I thought I was alone. Seems like a weird glitch -- it would be nice to have a fix for it sometime but it's already much better than before. Thanks for the guide!

Share this post


Link to post
Share on other sites

So..basically setting the same boot-display property for all ports? Did I get that part right?

 

Yes that's all I did... Makes not difference on my end with multi-monitors or single monitor switched to a different port...

 

I guess OS X thinks the displays are mirrored for the boot process maybe?

Share this post


Link to post
Share on other sites

Yes that's all I did... Makes not difference on my end with multi-monitors or single monitor switched to a different port...

 

I guess OS X thinks the displays are mirrored for the boot process maybe?

 

That is really interesting. :D I wonder if it works with the device-properties method. Should work..I guess. I just can't test this. :))

Share this post


Link to post
Share on other sites

Hi I've followed steps 1-4 but the only thing I got from step 5 is the loading bar at the center with no logo. Patch Vbios and Inject EDID made the first stage logo bigger with the loading bar at the center with no logo on the second stage. I've tried with/without CsmVideoDrv.efi but to no avail. My bios, tho UEFI, had no CSM option (it's an H61M). I'm booting in UEFI and I'm not using DSDT/SSDT coz Clover does the good job already. I'm using Manli GeForce 210 on this one. Any ideas?

I'm using the VGA port BTW.

Please have a look at the file (attached) I edited using @1 as the default.

device-properties.xml

Share this post


Link to post
Share on other sites

Hi I've followed steps 1-4 but the only thing I got from step 5 is the loading bar at the center with no logo. Patch Vbios and Inject EDID made the first stage logo bigger with the loading bar at the center with no logo on the second stage. I've tried with/without CsmVideoDrv.efi but to no avail. My bios, tho UEFI, had no CSM option (it's an H61M). I'm booting in UEFI and I'm not using DSDT/SSDT coz Clover does the good job already. I'm using Manli GeForce 210 on this one. Any ideas?

I'm using the VGA port BTW.

Please have a look at the file (attached) I edited using @1 as the default.

 

1. What's your display resolution? What's the resolution set in Clover? What's the resolution set in OS X?

2. Did you set a specific display-cfg in Clover config or anywhere else? Does it work without it?

 

Also, something seems a bit off in your xml... Is this the one that you edited or the one generated after reboot, when extracting it again from the system?

 

Also, a screenshot of your IOreg might help in this case.

Share this post


Link to post
Share on other sites

My display resolution is set to 1600x900 in OS X and in Clover.

 

No I didn't set any display-cfg in Clover. 

 

The xml I sent was the edited xml already.

 

What seems to be off in the xml?

 

Here's my ioreg. Thanks

post-942609-0-96357200-1447537139_thumb.png

Share this post


Link to post
Share on other sites

My display resolution is set to 1600x900 in OS X and in Clover.

 

No I didn't set any display-cfg in Clover. 

 

The xml I sent was the edited xml already.

 

What seems to be off in the xml?

 

Here's my ioreg. Thanks

 

 

I'm pretty sure hda-gfx is not in the initial tutorial. I'm not sure it's the cause of the issue. Probably not. But let's just do it exactly like it is on the first page for once.

 

So, could you please, try the hex txt in the attachment? Please, make a copy of your current one, just to be safe. And let's see if that makes any difference. Also please, try with and without PatchVbios.

hex_txt.txt

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 Arman Hossain
      HI 
      I want install High Sierra  on my pc . my CPU is : AMD Ryzen 3 2200g and my MotherBoard is : ASUS EX A320m. and 8gb ram DDR4 ram . i dont have any external gripch card. i have seen some video on youtube how to install High Sierra but they use extranal gripch card to make it good  but i don't have any extranal gripch card . on my windows sysem the shared gpu is 2GB which is using my ram to crate the vega gripch  . i want know is it possible to install High Sierra on my pc with out any extarnal gripsh card  ?


    • By Andres ZeroCross
      First my Old Threads is here http://www.insanelymac.com/forum/topic/308178-el-capitan-wih-i7-6700-skylake-gigabyte-ga-z170-hd3-palit-jetstream-gtx960/

      My Computer Specifications
      1. Processor : Intel Core i7 6700
      2. Motherboard : Gigabyte Z170-HD3
      3. VGA Card : Palit Jetstream GTX960 4GB DDR5
      4. Wifi Card ; TP-Link TL-WDN4800
      5. PCI-E to Sata = Bafo PCI-e to 2 Sata3 and 2 e-Sata
      6. PCI to USB 2.0 - NEC Chipset
      7. Main Harddisk Harddisk : Fujitsu SSD 120GB + Seagate 500GB that plug into Bafo PCIe to Sata3
      8. Other Harddisk : Natno SSD 12GB, 2x Seagate 2TB, Seagate 500GB, all of it are plug into onboard Sata Chipset Controller (But Unknow at El Capitan / 10th Intel Chipset)
      9. RAM : Team 3000Mhz 8GB (2x4GB)
      10. Display : Asus VN248H
      11. Clover version : 3280

      My Step :
      1. Because Internal Sata Chipset and USB 3.0 are not supported yet, so i clone my Fujitsu 120GB SSD from my Hacbook Asus X455LA that already installed El Capitan Build 15B30a with Carbon Copy Cloner
      2. I use MacPro 6.1 as SMBIOS and use FakeCPUIID of Intel 4790k (0x0306C3)
      3. Remove CPUSensor.kext from "FakeSMC.kext/Contents/Plugins" if you don't do this it will be stuck at ACPI log verbose.
      4. I try boot from USB that already install Clover 3280 and it boot. I use "-v nv_disable=1 dart=0"
      5. Then at desktop, i install nvidia web driver 346.03.02F02 (before that you need to modif it,, use pkgutil --expand bla bla ba,, google it and change required os to "15B" then use pkgutl --flatten bla bla to repackage) then i change info plist from AppleGraphicsControl.kext/Contents/Plugin/AppleGraphicsDevicePolicy.kext/Contents/info.plist and change line that contain board-id of MacPro 6.1 from Config2 to none
      6. Then i install that kext,, and restart
      7. i use "-v dart=0 nvda_drv=1 and it will need more time than usual to get login form,, yeah i did it. But there is some bugs
       
      Bugs :
      1. Internal sata is not function
      2. USB 3.0 is error too,,  at verbose i see "error mantisa log"
      3. Sometimes my system get freeze for a few seconds. I thinks this is error from Nvidia web driver,, i see nvdia error log from "sudo dmesg"

      At last,, sorry for my bad english
      Thanks
       
      This is for screenshots
       

       

      I upload my IOREG and DSDT
       
       
    • By fantomas
      Hi InsanelyMacaholics   

      Use this thread to link / talk about of the future Nvidia Web Driver updates for macOS Sierra.
       
      10.12.6
      Nvidia Web Driver - 378.05.05.25f19 --> build 16G2136 (thanks to BreBo) New!
      Nvidia Web Driver - 378.05.05.25f18 --> build 16G2028 (thanks to Riley Freeman)
      Nvidia Web Driver - 378.05.05.25f16 --> build 16G2016 (thanks to Cyberdevs)
      Nvidia Web Driver - 378.05.05.25f15 --> build 16G1918 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f14 --> build 16G1917 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f13 --> build 16G1815 (thanks to flowrider)
      Nvidia Web Driver - 378.05.05.25f12 --> build 16G1710 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f11 --> build 16G1618 (thanks to Frank Nitty)
      Nvidia Web Driver - 378.05.05.25f10 --> build 16G1510 (thanks to BreBo) 
      Nvidia Web Driver - 378.05.05.25f09 --> build 16G1408 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f08 --> build 16G1314 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f07 --> build 16G1314 (thanks to haring)
      Nvidia Web Driver - 378.05.05.25f06 --> build 16G1212 (thanks to WeBeRiO)
      Nvidia Web Driver - 378.05.05.25f04 --> build 16G1114 (thanks to lukazm)
      Nvidia Web Driver - 378.05.05.25f03 --> build 16G1036 (thanks to Gradou)
      Nvidia Web Driver - 378.05.05.25f01 --> build 16G29 (thanks to Badruzeus)
       
       
      10.12.5
      Nvidia Web Driver - 378.05.05.15f01 --> build 16F73 (see this post)
       
       
      10.12.4
      Nvidia Web Driver - 378.05.05.05f02 --> build 16E195(thanks to crachmaster4999)
      Nvidia Web Driver - 378.05.05.05f01 --> build 16E195 (thanks to Moviemakergr)  Pascal support!!!
      Nvidia Web Driver - 367.15.10.45f01 --> build 16E195 (thanks to Lanc)
       
       
      10.12.3

      Nvidia Web Driver - 367.15.10.35f01 --> build 16D32 (thanks to shatterhenner)
       
       
      10.12.2
      Nvidia Web Driver - 367.15.10.25f02 --> build 16C68 (see this post)
      Nvidia Web Driver - 367.15.10.25f01 --> build 16C67 (see this post)
      Nvidia Web Driver - 367.15.10.25b06 --> build 16C60b/16C63a (see this post)
       
       
      10.12.1
      Nvidia Web Driver - 367.15.10.15f03 --> build 16B2657/16B2659 (thanks to Moviemakergr).
      Nvidia Web Driver - 367.15.10.15f01 --> build 16B2555 (thanks to Moviemakergr)
       
       
      10.12.0
      Nvidia Web Driver - 367.15.10.05f01 --> build 16A323 (thanks to phi777)
       
       
      GM
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A323 (same driver since DP4/PB3)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A322 (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A320 (see this post)
       
       
      DP/PB
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A313a (DP8 & PB7) (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A304a (DP7 & PB6) (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A294a (DP6 & PB5) (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A286a (DP5 & PB4) (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A270f (DP4 & PB3) (thanks to TheRacerMaster)
      Nvidia Web Driver - 367.05.10.05b07 --> build 16A254g (DP3 & PB2) (see this post)
      Nvidia Web Driver - 367.05.10.05b07 --> build 16A238m (PB1) (thanks to Faun) 
      Nvidia Web Driver - 367.05.10.05b07 --> build 16A239j (DP2) (thanks to Faun)
      Nvidia Web Driver - 367.05.10.05b03 --> build 16A201w (DP1) (thanks to Xmedik)
       
    • By verdazil
      Notebook: Acer A315-53-34MP, High Sierra 10.13.6 && Mojave 10.14.6 installation
       
      Hardware
      CPU: Intel® Core™ i3-8130U, 3400 MHz
      Memory: Kingston, DDR4, 2x4Gb, 2400 MHz
      Video: Intel UHD620 (integrated)
      Display: CMN N156HGA-EAB [15.6" LCD] (embedded)
      External monitor: LG TV 42LF650V
      SSD: Leven JAJS300M240C, 240 Gb (replacement)
      Chipset: Intel Sunrise Point-LP
      Sound: Intel Kaby Lake HDMI + Realtek ALC255
      LAN: Realtek RTL8168/8111 PCI-E Gigabit Ethernet Adapter
      Wi-Fi + Bluetooth: Broadcom BCM94352Z (replacement)
      Touchpad: ELAN0504 
      Cardreader: Realtek PCIE RTS5289
      VGA WebCam
      Mac model: MacBookPro14,2
      MacOS versions tested: High Sierra 10.13.6 (17G8030) && Mojave 10.14.6 (18G95) && Catalina 10.15 (19A558d)
       
      Here is what I used to install and configure the system:
      - Video settings: https://www.insanelymac.com/forum/topic/334899-intel-framebuffer-patching-using-whatevergreen/
      - Wi-Fi settings: https://github.com/acidanthera/AirportBrcmFixup
      - Bluetooth settings: https://github.com/RehabMan/OS-X-BrcmPatchRAM/blob/master/README.md
      - Touchpad settings: https://voodooi2c.github.io
      - Cardreader settings: https://www.insanelymac.com/forum/topic/321080-sineteks-driver-for-realtek-rtsx-sdhc-card-readers/
      - Clover, version v2.5k r5033: https://github.com/Dids/clover-builder/releases/tag/v2.5k_r5033
      - The results of the work of many developers in this and other forums.
       
      What works?
      - Video: Full HD x 60Hz accelerated video on embedded and external (HDMI) monitors
      - Sound: embedded and external (audio jack + HDMI audio)
      - Microphone
      - Touchpad (gestures)
      - Cardreader
      - Wi-Fi
      - USB2 && USB3 ports
      - LAN
      - Bluetooth
      - VGA WebCam
      - Sleep mode
      - Display brightness and volume control using function keys
      - Battery Indication
      - Automatically dimming the screen when the laptop is running on battery power
      - Sound notification when external power is connected
       
      What does not work?
      -
       
      How to use
      1. Update BIOS to version 2.02. Secure boot must be disabled, Touchpad settings - Advanced
      2. To make a bootable flash drive, you can use my EFI directory (link at the end of the message) Tested for High Sierra 10.13.6 (17G8030) && Mojave 10.14.6 (18G95) && Catalina 10.15 (19A558d) installation.
      Note: you must insert your own SeralNumber && MLB && ROM in the config.plist file.
      3. After installation, just copy EFI directory from flash drive to the system drive.
      4. Install kexts BrcmFirmwareRepo.kext && BrcmPatchRAM2.kext to the /Library/Extensions and update system caches.
       
      Link: https://drive.google.com/open?id=11vTmPKjQUSEs2ddUzgwXG9A59EcDMrCs
    • By shinho73
      Can someone help me fix reboot issue? Actually it reboots, but sometimes the hackintosh just hangs with screen off. Here is the Extra folder containing org.chameleon.boot.plist. https://drive.google.com/drive/folders/1MX8-DpQk9kaRUfjPcToxf-ElWh-bN6EY?usp=sharing  and the spec of the PC. https://drive.google.com/drive/folders/1NlcUNK5DBzJFxeFeuyt92eRjQqwO5T32?usp=sharing Can someone look at it? I might be doing something wrong. Any help will be greatly appreciated. Thank you. 

×