Contribute
Register

An iDiot's Guide To Lilu and its Plug-ins

I followed the instructions and used the boot argument shikigva=16 first, but Netflix gave me error message as usual. The. I used the boot argument shikigva=80 and now I can see video playing but no picture behind it.
I definitely have progress on this, but something is still missing.
 

Attachments

  • Screen Shot 2020-04-14 at 7.36.39 PM.png
    Screen Shot 2020-04-14 at 7.36.39 PM.png
    151 KB · Views: 69
Last edited:
I didn't change anything, but now I can see picture during video play on Netflix for 5 sec and then black scree with subtitles running.
 
I used the boot argument shikigva=80 and now I can see video playing but no picture behind it.... definitely have progress on this, but something is still missing.


I didn't change anything, but now I can see picture during video play on Netflix for 5 sec and then black scree with subtitles running.


@rauan1,

Thanks for testing and reporting your findings ....

I think there is still an underlying issue when the shikigva= boot argument is used with Polaris based GPU's such as the RX 580. With each new release of Lilu + WEG things are getting better (it no longer crashes or locks the system up) but there is still some work to be done.

All we can do for now is report our findings to the devs on the official support thread and hope that they eventually get things sorted.


Cheers
Jay
 
@apt.dogcow,

Very interesting .. I will try and find some time to do some testing.

Cheers
Jay
VirtualSMC.efi is needed only if you want to enable FileVault 2 with unsupported bootloaders like Clover, the supported being OpenCore with certain configuration since January.
BTW, thanks for the guide!
 
First of all, thank you for this guide! it's a huge step forward for me just in understanding what is going on.

I'm having problems with all my third party programs giving me either OpenGL errors or just a greyed out UI (sown below)

I'm using an I-5 9500 CPU and using the built-in UHD Graphics 630 as my GPU I have looked it up and the device-id should be 0x3E98 That means I should be using 0x3E980003 according to this guide:


But that only seems to result in a Kernel panic. (The above guide also makes me assume that the 0x3E980003 id has no display connectors associated with it.) I tried spoofing the 0x3E9B0007 id and it results in a black screen. I'm currently connecting via screen share and using my MacBook as a display.

The program that previously had an OpenGL error now opens Ableton still gives me the greyed out UI. I checked my About This Mac section and the Graphics only displays "???". Hackintool also displays my Platform-id as 0x00000000 and it doesn't show that I have a monitor plugged into an HDMI port highlighted in red so, I'm assuming that for some reason my plist.config file is not pushing through the correct info.












 
First of all, thank you for this guide! it's a huge step forward for me just in understanding what is going on.

I'm having problems with all my third party programs giving me either OpenGL errors or just a greyed out UI (sown below)

I'm using an I-5 9500 CPU and using the built-in UHD Graphics 630 as my GPU I have looked it up and the device-id should be 0x3E98 That means I should be using 0x3E980003 according to this guide:


But that only seems to result in a Kernel panic. (The above guide also makes me assume that the 0x3E980003 id has no display connectors associated with it.) I tried spoofing the 0x3E9B0007 id and it results in a black screen. I'm currently connecting via screen share and using my MacBook as a display.

The program that previously had an OpenGL error now opens Ableton still gives me the greyed out UI. I checked my About This Mac section and the Graphics only displays "???". Hackintool also displays my Platform-id as 0x00000000 and it doesn't show that I have a monitor plugged into an HDMI port highlighted in red so, I'm assuming that for some reason my plist.config file is not pushing through the correct info.













Why are you still using macOS Mojave? I think its time for you to move forward to macOS Catalina for better Coffee Lake support.
 
Can anyone here explain to me why H264 decoder fails when Intel UHD 630 is in headless mode? As you can see, the Intel UHD 630 framebuffer is loaded and macOS detects it just fine. However, it makes no sense.

Screen Shot 2020-05-10 at 4.29.38 PM.png



Running VDA Decoder also gives an error:

Screen Shot 2020-05-10 at 4.39.21 PM.png


Screen Shot 2020-05-10 at 4.30.13 PM.png

So how can HEVC be working fine but not H264? Has H264 support been removed in 10.15.4?
 
Why are you still using macOS Mojave? I think its time for you to move forward to macOS Catalina for better Coffee Lake support.

I'm in audio so, a lot of the tools I use no longer works on Catalina like my Waves plugins which I would have to purchase again for working updates.
 
Back
Top