-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No luck with Big Sur (11.6.1) and Monterey (12.3) - can I help you fixing it? #4
Comments
I'm adding a follow-up here. The NVMe SSD installed in this laptop is a Samsung PM981a MZVLB512HBJQ 512Gb. Well, if I am to trust https://dortania.github.io/Anti-Hackintosh-Buyers-Guide/Storage.html then I have an unsupported SSD. This would explain problems 1a) and 1b). An interesting thread to read on this topic: tylernguyen/x1c6-hackintosh#43 It suggests that not all models of EUL-W19P laptops have the same NVMe SSDs. I'd be interested in knowing what SSD model you have in yours ? edit OK, I won't hope for a software fix, so I ordered a WD750 WDS100T1B0E. This laptop is rather simple to open (there are 4 extra screws under the rubber pads), then swapping the SSD is just a matter of unscrewing the lefthandmost screw on the copper plate, unscrewing the NVMe SSD that's just below, and carefully sliding it left. Now if someone has a clue on problem no 2 (Monterey) ? |
Hi, As soon as i've time i will update the repository so you can give a try to the new EFI. |
Hey, thank you for your reply. So it confirms these laptops can be fitted with different SSDs. I suggest you to add a prominent note in your readme that the PM981a ones should be swapped. I can provide photos on how to do that. I expect the new SSD to arrive tomorrow or the day after ; I'll renew my attempts then and I expect success at least with Big Sur. May I ask you why you did not upgrade to Monterey, is there a technical or philosophical reason ? |
So, the new WD SSD arrived today and was promptly fitted in place. Big Sur installed. Also, I re-enabled SIP in the config.plist (csr-active-config -> 0) as some software require it to function. Monterey still doesn't boot however, but now I can take time to study that more closely. |
Something else isn't working right: the automatic screen backlight adjustment. Have you toggled it off ? |
I don't any problem with screen backlight. If you've updated OC you Need to
update the backlight aml accordingly.
Il gio 28 apr 2022, 20:04 Pierre-Marie Baty ***@***.***> ha
scritto:
… Something else isn't working right: the automatic screen backlight
adjustment. Have you toggled it off ?
—
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALOKNTEZZU4VFSXVDPJBCWLVHLHMHANCNFSM5UCW6NRA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Thank you for the reminder. Well, the issue with the automatic backlight control seems to have disappeared and I couldn't find neither the reason why it appeared nor what made it disappear. The backlight was shifting up and down at random while I was typing and I noticed that the control keys for backlight and audio weren't working. One reboot later, these symptoms disappeared. Unfortunately not everything is fixed: when I leave the laptop for a few minutes and the screen goes black, nothing seems to be able to make it light up again. It's not frozen: I hear macOS playing the "bloop" sound when I hit the space bar. It's just that the display fails to wake up. edit thinking about it, it might be because I switched to a MacBookAir9,1 platform info, thinking it would be wiser regarding to the laptop's specs. But that was at first sight. When looking at it more closely, the CPU/GPU architecture (Comet Lake + UHD620) is perhaps closer to a MacBookPro15,1/15,3/16,1 or 16,4 (Coffee Lake + UHD630) than of a MacBookAir9,1 (Ice Lake + Iris Plus). Alright - let me switch back. edit 2 - it wasn't that. I'm still on MacBookAir9,1 and the problem disappeared when I started over from an EFI backup. I'm forced to conclude that the precompiled SSDT files from Dortania (which I updated following your advice) are not totally compatible with this laptop. Also, I'm wondering if your readme is up-to-date with your EFI. Because in the readme you say the touch screen is disabled via an ACPI patch, whereas here it's working, seemingly totally fine ? In a nutshell, my changes:
As you seem much more knowledgeable than me on this matter, if you could take the time to upload your latest EFI I'd be very interested in starting over from there. We'd have a common base to start with. |
Monterey installer boot success ! The culprits were the Bluetooth kernel extensions. I had overlooked that in Monterey the Bluetooth stack was moved from kernel to user space, and that the previous methods of uploading the BT firmware to the cards were not only no longer effective, but could cause the OS to fail to boot. My solution was as recommended by the OC user guide to use the MaxKernel and MinKernel values to provide a selective way of loading the kernel extensions, i.e.:
Now installing. |
The black screen Is totally normal in most Huawei laptop. I've created an
acpi patch to fix that. I Will try to update my GitHub with the latest
version but meanwhile could you upload here your untouched aml files? Use
patchmatic -extract to do that.
Il ven 29 apr 2022, 13:17 Pierre-Marie Baty ***@***.***> ha
scritto:
… Thank you for the reminder.
Well, the issue with the automatic backlight control seems to have
disappeared and I couldn't find neither the reason why it appeared nor what
made it disappear. The backlight was shifting up and down at random while I
was typing and I noticed that the control keys for backlight and audio
weren't working. One reboot later, these symptoms disappeared.
Unfortunately not everything is fixed: when I leave the laptop for a few
minutes and the screen goes black, nothing seems to be able to make it
light up again. It's not frozen: I hear macOS playing the "bloop" sound
when I hit the space bar. It's just that the display fails to wake up.
Also, I'm wondering if your readme is up-to-date with your EFI. Because in
the readme you say the touch screen is disabled via an ACPI patch, whereas
here it's working, seemingly totally fine ?
As you seem much more knowledgeable than me on this matter, if you could
take the time to upload your latest EFI I'd be very interested in starting
over from there. We'd have a common base to start with.
—
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALOKNTDK3QACG2NMUY7D6R3VHPAMDANCNFSM5UCW6NRA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Here you are. Let me know what interesting findings you discover - and thanks again. BTW, Monterey installed fine and things seem to work as good as with Big Sur. The touchscreen still works. Irrelevant question but, is there a possibility to wake up the laptop by hitting the touchpad instead of hitting a key ? |
I will upload in few minutes my latest EFI. I didn't have time to upgrade OC to the lastest version or the latest kexts but everything is working fine. I'm using some framebuffer patches to fix the problems i had with the Type C port when used as HDMI so switching to another SMBIOS will probably broke them due to different connectors type. |
Thank you. I'm going to make a diff with mine so as to highlight the changes. Right now everything seems to work in Monterey. I'm curious about the webcam not working, do you have an idea why ? Normally UVC webcams should work out of the box. I've read somewhere that MJPEG decoding on USB2 transport (which seems to be the case here) was broken in Monterey but it's been fixed since, and besides it was reported as nonworking in Big Sur as well, so the cause must be elsewhere. |
As for the issue proper, I guess you can mark it as resolved. The problems boiled down to this:
|
About the webcam i've tried lot of tricks and kexts but without luck. My theory is that in this laptop the webcam is connected over USB in a way that is not supported by MacOS. Usually as you can check in some forums they say : or it works OOB or it doesn't work at all. I've tried injecting various kexts but without luck. |
how to do it? please guide me ! |
Hello How to do what ? Swap the SSD ? Or something else mentioned in this thread ? |
Hello Mattia,
Congratulations for having putting this together. Are you still using this laptop ? I'm afraid an update is necessary...
Laptop model: EUL-W19P (same as yours)
BIOS: downgraded to 1.04 (same as yours?) with CFG-Lock and 64Mb DVMT patches applied (using RU.EFI)
1 - When trying to install Big Sur (version 11.6.1) :
1.a - When using your latest EFI release from 17 june 2021 (with a properly generated and validated MacBookPro16,3 PlatformInfo as you suggested)
- it boots OK to the installer screen, but:
- wiping/repartitioning the SSD to APFS or HFS+ through Disk Utility freezes the laptop during SSD reformatting
- wiping the SSD with Linux (dd if=/dev/zero etc...) and trying to install macOS after that freezes the laptop at about 60%
I couldn't find a way to get past these 2 problems.
1.b - When I update OpenCore to 0.8.0 + the base kernel extensions (Lilu, WhateverGreen, VirtualSMC etc) and apply the syntactic changes (checked using ocvalidate) --> same symptoms
2 - When trying to install Monterey (version 12.3)
2.a - When using your latest EFI release from 17 june 2021 (with a properly generated and validated MacBookPro16,3 PlatformInfo as you suggested)
- display initialization fails both on laptop screen and USB-C HDMI (right hand side) - meaning the boot process never switches to graphics mode on the laptop's screen, and the external screen never lits
- Trying to change the PlatformInfo to MacBookAir9,1 doesn't seem to change anything
- I can't seem to find another AAPL,ig-platform-id/device-id combination that works - but I'm not very experienced with that.
2.b - When I update OpenCore to 0.8.0 + the base kernel extensions (Lilu, WhateverGreen, VirtualSMC etc) and apply the syntactic changes (checked using ocvalidate) --> same symptoms
2.c - When I use a previous release of your EFI (1.0 or 2.0) --> no change
2.d - When I use @ske1996's EFI (from which you derived your own) --> no change either, Monterey doesn't switch to graphics mode. Which is strange as he claims it's working.
Could you please confirm (or infirm) whether you're still interested in all this ? I would very much appreciate your help so as to get this SMC/EFI stack working again for this very laptop. As for the background, I'm an experienced programmer, although a bit new to all the OpenCore/hackintosh jargon, so you can talk me technical - it shouldn't be a problem.
I am definitely interested in having this fixed, and you have my word that I'm not the kind of user that goes away and lets you down when I find a solution, I am committed to stay here and collaborate with you until we can confirm here a proper resolution :)
If you need me to provide you with anything - just ask.
The text was updated successfully, but these errors were encountered: