Closed thaiiy closed 2 years ago
shiecldk
commented
2 years ago Hi @thaiiy, have you followed this guide? https://www.tonymacx86.com/threads/guide-general-framebuffer-patching-guide-hdmi-black-screen-problem.269149/
What's the screenshot of the connector section in Hackintool.app on your UX481?
shiecldk
commented
2 years ago @thaiiy Any update for your issue? If not, I will close this thread.
thaiiy
commented
2 years ago Thanks for following up on this.
I have tried changing BusID etc, just the simple stuff but haven't been successful. I tried turning output to the screen off using the RDM app but that didn't work either.
I haven't and don't think I will get time to work this one out using your link. So unless someone else wants to chime in, I won't have any further updates.
On Wed, 24 Nov 2021, 12:14 pm shiecldk, @.***> wrote:
@thaiiy https://github.com/thaiiy Any update for your issue? If not, I will close this thread.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/shiecldk/ASUS-ZenBook-Pro-Duo-15-OLED-UX582-Hackintosh/issues/2#issuecomment-977354980, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVMGD3KPAO5QZNDSL7CVW4LUNQ35VANCNFSM5IHDGE2A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
shiecldk
commented
2 years ago Hi, @thaiiy. Please send a screenshot of the connector section in Hackintool.app. No one cannot help without knowing the device setup (iGPU pin connection) on your laptop.
shiecldk
commented
2 years ago Issue closed due to inactive from the original post.
Qonfused
commented
2 years ago Hi, @shiecldk. I have the same laptop (w/ i7 10510u) and also haven't had success using the framebuffer patching guide on Monterey.
```ini [ASUS Zenbook Duo 14" Laptop (UX481FL-XS74T)] ``` ```md | [CPU][Intel Core i7-10510U 4-core Processor] | └──[iGPU][Intel UHD Graphics 620] | [Wifi][Intel Wi-Fi 6 AX201 (802.11ax), Bluetooth 5] | [Memory][Micron 16GB (4x4GB) LPDDR3-2133 CL16] | [dGPU][Nvidia GeForce MX250 2GB (10W 1D52 version; disabled)] |[Storage][Samsung 970 Evo 500GB M.2-2280 NVMe SSD] | ├──[Bootloader][OpenCore 0.7.3] | ├──[Operating System][MacOS Monterey 12.0 Beta 6] | └──[Operating System][Microsoft Windows 11 Pro 64-bit] | [Audio][Realtek HD Audio (ASUS SonicMaster)] |[Battery][Dynapack 70Wh (15.4V; 4440mAh) 4-cell LiPo Battery] ```
This is what the connectors section of Hackintool looks like for me:
^^^ In red I believe is the second display (idx 1, port 5) and hdmi is on port 4 (idx 2); the primary display is still on port 0 (idx 0).
I've tried applying patches from hackintool after changing the display type for the screenpad to LVDS and changing the hdmi connector to the HDMI type. From the original config in this repo, I renamed connectors 1-3 to 0-2, and also removed the enable-max-pixel-clock-override key, but beyond that only the framebuffer connector properties were changed (removing all-data keys and adding pipe/type keys).
Additionally, I also changed the platform-id/device-id for integrated graphics to match the 10510u (UHD 620), but this also still shows up as UHD 630 in Hackintool (and 'Intel HD Graphics CFL CRB 2048 MB' in the about this mac window). This could be related but I'm not sure if this is still problematic for patching the iGPU or just cosmetic.
I've included my DeviceProperties section of my plist below before/after patching w/ the hackintool patches below:
```
```
```
Qonfused
commented
2 years ago I think I see what I'm doing wrong lol. I'll work on a fix w/ touchscreen and probably make a new issue with other misc fixes for this specific model (if you want that here).
danperks
commented
2 years ago @Qonfused I have exactly the same issue, did you ever come up with a fix? For context, I just found this thread so haven't even downloaded Hackintool to see if I can fix it there.
Maleficent-Magik
commented
2 years ago I reopen the debate! Has there been any advancement? @danperks @Qonfused
danperks
commented
2 years ago Glad another has joined the quest, I have found nothing as of yet. Honestly considering paying someone on the r/Hackintosh Reddit/Discord to tell me how to fix it lol!
Qonfused
commented
2 years ago Sorry I meant to create a gist to dump everything in (w/ removing or changing some pro-duo specific kexts and SSDTs, etc). I got busy with work and with Metal 3 w/ Ventura on my main machine since then so I don’t think I got much done for the non-pro zenbook duo. I’m at vacation atm but I’ll get some free time to work on this again come Thursday.
danperks
commented
2 years ago Anything you may have to help would be great. I do have the Pro Duo so any help you have that may be of use for my device would be fantastic.
Once time is more on my side, I am hoping to learn more about this kind of stuff!
Maleficent-Magik
commented
2 years ago Personally, I had managed at one point not to have the screen blurred, but how? I don't know anymore hahaha ...! but since then, it came back blurry heh
Concerning @Qonfused 's vacations, well, happy vacations to you ! There is no worry about the timing, for now I stay on Windows x) but MacOS would be a plus for some things. Unfortunately, I don't know if @danperks tried to boot on Monterey but personally, I didn't succeed x) I crash on ACPI
On that note, good work to all of you and hope to get something done haha, have a good day to both of you!
See you soon!
Qonfused
commented
2 years ago I wanted to leave a quick update since I forgot to leave one the other day.
I couldn't find my monterey drive from June but from what I recall both displays would work separately but not at the same time (black screen for the other display; seems to be the same issue shiecldk ran into here).
I've spent pretty much all of yesterday and today figuring out how OpenCore overrides the AppleIntelCFLGraphicsFramebuffer kext used for both the UHD 620 and UHD 630 iGPUs (since I still had no idea what was actually happening with framebuffer/connector patches). I'm hoping to figure this out the next couple of days since this mainly only tedious to go through all the framebuffer/platform ids.
Concerning my previous post, this is the previous framebuffer data that I used before for framebuffer id 3EA50009 (from the WhateverGreen Manual):
| Index | Name | Connector Type | Port Number | Pipe | Flags |
|---|---|---|---|---|---|
| 0 | Framebuffer0 | LVDS and eDP |
0x0 |
8 |
98000000 |
| 1 | Framebuffer1 | Displayport |
0x5 |
9 |
C7010000 |
| 2 | Framebuffer2 | Displayport |
0x4 |
A |
C7010000 |
^ This apparently is actually the same framebuffer-id used in this repo for the i9-10980HK/Intel Core i7-10870H (which both have UHD 630 iGPUs). I before noted Framebuffer0 and Framebuffer1 showed displays attached in macOS with this framebuffer-id in my previous post, but no connector patch worked (maybe because I wasn't using the correct framebuffer-id for the iGPU?).
^ To me these would appear to have the wrong flags for the 3EA50009 framebuffer id used here (the flag would supposed to be C7010000) but not for the 3E9B0000 framebuffer id (the flag here would be 87010000). This is mostly what was throwing me off trying to test various bus-ids, etc for patching the screenpad-plus (and for finding the right framebuffer-id since these patches are the only indication of whether the screenpad plus is both mapped correctly and is using the right connector + busid).
^^ The other main thing to note is that the screenpad-plus for the pro-duo is connected to port 1 and busID 5 (the first part of the alldata patch; 01050900 --> 01 port, 05 busID, 0900 pipe), and both the primary display and secondary display are mapped as displayport (the second part of the alldata patch; 00040000). These I thought would both be mapped as LVDS/eDP since they're internal displays (and the connector type for the screenpad plus is eDP)?
The first framebuffer from the table (framebuffer0) seems to be unused for that configuration? I think before I assumed framebuffer0 to be the primary display but was confused when modifying the busID for the second framebuffer (framebuffer1) since I recall it would cause a black screen for the primary display since I was instead dealing with the primary display, not the screenpad plus.
I've been starting from here to find the proper framebuffer-id before doing any connector patching:
| ^ Above should work for both the i5-10210u and i7-10510u, which for this framebuffer-id has these properties: Index | Name | Connector Type | Port Number | Pipe | Flags |
|---|---|---|---|---|---|
| 0 | Framebuffer0 | LVDS and eDP |
0x0 |
8 |
98000000 |
| 1 | Framebuffer1 | Displayport |
0x5 |
9 |
87010000 |
| 2 | Framebuffer2 | Displayport |
0x4 |
A |
87010000 |
| This is the list of framebuffer ids from the CFL/CML section of the whatevergreen manual that I need to go through (I've converted the ids from small endian to big endian for OpenCore): Framebuffer ID | (AAPL,ig-platform-id) | Type | Connectors | Stolen Memory | Tested |
|---|---|---|---|---|---|
0x3EA50009 |
0900A53E |
mobile | 3 | 58 MB | yes |
0x3E920009 |
0900923E |
mobile | 3 | 58 MB | ? |
0x3E9B0009 |
09009B3E |
mobile | 3 | 58 MB | ? |
0x3EA50000 |
0000A53E |
mobile | 3 | 58 MB | ? |
0x3E920000 |
0000923E |
mobile | 3 | 58 MB | ? |
0x3E000000 |
0000003E |
mobile | 3 | 58 MB | ? |
0x3E9B0000 |
00009B3E <-- Default |
mobile | 3 | 58 MB | yes |
0x3EA50004 |
0400A53E |
mobile | 3 | 58 MB | ? |
0x3EA50005 |
0500A53E |
mobile | 3 | 58 MB | ? |
0x3EA60005 |
0500A63E |
mobile | 3 | 58 MB | ? |
I'll also ask in the Hackintosh Discord how I should be testing these framebuffer-ids since I'd otherwise be enumerating every bus-id and connector index from the dortania guide (and/or from the other guide mentioned before on tonymacx64) to test that the primary display is working, and that the secondary screenpad-plus display is properly recognized in display settings (and hopefully eventually working w/ the primary display).
Let me know if anything here doesn't seem correct since I'm not 100% sure on this (this is still my first time dealing with a laptop hackintosh w/ framebuffer patches, etc).
Qonfused
commented
2 years ago Personally, I had managed at one point not to have the screen blurred, but how? I don't know anymore hahaha ...! but since then, it came back blurry heh
Concerning @Qonfused 's vacations, well, happy vacations to you ! There is no worry about the timing, for now I stay on Windows x) but MacOS would be a plus for some things. Unfortunately, I don't know if @danperks tried to boot on Monterey but personally, I didn't succeed x) I crash on ACPI
On that note, good work to all of you and hope to get something done haha, have a good day to both of you!
See you soon!
@UsedDiscord I'd try a Monterey version after Beta 12.3 to be sure (I'm testing on 12.4 public build 21F79), but there were some ACPI patches I had to modify that otherwise might have caused that issue? I've created a fork here with what I'm currently using but please remember to use GenSMBIOS to generate your own serial & board data before trying to setup iCloud! I've included a warning in the README linking to instructions for that.
I'd also use this or suggest changes to this to verify that any framebuffer patches I find work on my machine also work on yours (if you have a different hardware configuration, etc).
Maleficent-Magik
commented
2 years ago Personally, I had managed at one point not to have the screen blurred, but how? I don't know anymore hahaha ...! but since then, it came back blurry heh Concerning @Qonfused 's vacations, well, happy vacations to you ! There is no worry about the timing, for now I stay on Windows x) but MacOS would be a plus for some things. Unfortunately, I don't know if @danperks tried to boot on Monterey but personally, I didn't succeed x) I crash on ACPI On that note, good work to all of you and hope to get something done haha, have a good day to both of you! See you soon!
@UsedDiscord I'd try a Monterey version after Beta 12.3 to be sure (I'm testing on 12.4 public build 21F79), but there were some ACPI patches I had to modify that otherwise might have caused that issue? I've created a fork here with what I'm currently using but please remember to use GenSMBIOS to generate your own serial & board data before trying to setup iCloud! I've included a warning in the README linking to instructions for that.
I'd also use this or suggest changes to this to verify that any framebuffer patches I find work on my machine also work on yours (if you have a different hardware configuration, etc).
Hello ! Glad to see you in my inbox early in the morning! I hope you are doing well. Well, I'm starting a bit backwards for your reading x)...
Concerning MacOS Monterey, I thank you very much! but really very much! I was able to take your EFI that you posted (linked to your Fork) and put it on my usb key, good news, everything starts (OpenCore + OpenCore GUI (Thank you! it is also sublime) )! When I went on the Recovery of MacOS Monterey; it was able to find my wifi password already registered on MacOS BigSur (I had already installed BigSur because as I said : )
I crash on ACPI µ
so now no problem.
The installation went well, he found my NVMe disk on the first try (Normal, he already had MacOS BigSur)
Strangely, it didn't get stuck where it is supposed to be stuck... I always screw up my installations, I get stuck at the "Less than a minute left" moment... strangely, it restarted by itself! and it was able to finish its installation properly.
So once I was able to boot on MacOS Monterey, everything was fine! The keyboard is now backlit! (Big & huge thanks) the USB works properly (unlike before where the key ejected itself)! and the sound, wow! it works perfectly! there is no lag. BT & Wifi works! (Airdrop would be available (not tested) ).
So already, a huge thank you for your work that I could not reproduce ...
Now, what is blocking : -> The trackpad doesn't work but the keyboard itself does (except the F1,F2 ect ect keys (maybe pressed FN+Fx?)).
-> The second screen (aka: ScreenPad) always decides to make the face, and to blur, well, in the meantime, I did not modify your configuration, except the SMBIOS that I modified as requested of course. I will try a little, but it's long to always restart the computer... we lose a crazy time x).
What I haven't tested yet:
-> Sleep, AirDrop, -> the camera, -> Touch screen (on the scrambled Screenpad, it works..)
I could also see that during the startup, there are problems of "KEXT" so, it's quite strange, I'll look at the logs tonight ( at the time of writing, it's 7pm) So already, a big thank you for all this! I'll read your first part and answer a bit! in the meantime, good evening!
-- UsedDiscord
(EDIT : 7pm06 : (My PC is also a Comet Lake and a UHD 620 / GT2 / HD630, I don't really understand but hey...) so we can take the same configuration!)
Maleficent-Magik
commented
2 years ago btw, which SMBios would you select?
Qonfused
commented
2 years ago btw, which SMBios would you select?
@UsedDiscord Use MacBookPro16,1. I meant regenerating your board no. and serial number btw with that earlier message. It's to prevent issues with people setting up different installs w/ the same serial info for iServices.
Maleficent-Magik
commented
2 years ago I meant regenerating your board no. and serial number btw with that earlier message. It's to prevent issues with people setting up different installs w/ the same serial info for iServices
Okay! I'll use GenSMBIOS with MacBookPro16,1. Thanks again to you! Tomorrow I'll try the other framebuffer and get back to you. For me, it's 11:37 pm, it's a good night ^^ for you, I wish you a good day or a good night !
Hi there, thanks for this repo! I have the ZenBook Duo UX481 so it's fairly simlar. It booted without issues with your EFI straight away.
However, secondary screen is not working, garbled as in the picture attached. Any ideas? Thanks