Contribute
Register

[Guide] Lenovo Yoga C930-13IKB (4K/i7-8550u) 99% working, updated 7 Feb

Status
Not open for further replies.
I multiboot and using apfs fuse in linux I was able to copy off all of the data I needed from my mojave install.

I tried an upgrade to big sur 11.2.1 with open core on the latest bios and it appeared to complete the upgrade but it got stuck at the prohibited support.apple.com/mac/startup so I then erased the volume and tried a fresh install of big sur 11.2.1 which appeared to work.. and even booted.. once .. I got to a desktop and then chose restart to see if it would reboot and it has gotten stuck at the same prohibited support.apple.com/mac/startup screen. I'm using the efi from above but I'm stuck... any suggestions as how to resolve the prohibited black screen?

*time passes*

I did some more messing around and if I boot from the usb stick with open core and the big sur installer on it then I can boot up big sur that is installed on my internal hard disk. But if I copy the OC directory from the usb stick to my internal hard disk's EFI and try and boot it results in a prohibited black screen on boot.

Other issue is the touch pad doesn't work at all so I'm having to get by with my mouse (which is driving me nuts because it's so broken I should have replaced it years ago)... any fixes for the touch pad? Or things to try so I can boot big sur without having to have the usb stick plugged in?

And some of you mentioned the brightness controls don't work but for me from the top right drop down control panel brightness seems to work fine.
 
Last edited:
I'm using the efi from above but I'm stuck... any suggestions as how to resolve the prohibited black screen?
Which EFI folder did you use? The one I posted or the one from Feb 7? Have you tried enabling the Debug flags in config.plist and adding Debug OC files?
 
I managed to get big sur to boot from the internal ssd drive without needing to boot it from the usb. I have windows/linux/big sur on my internal ssd and I was using grub to chainload opencore... this appears to have been the cause of my problems... for whatever reason I can't make the bios find the opencore boot option so through some dodgy file copies if I select windows it will boot opencore and big sur boots...

Now to try and get the touch pad working.... Does anyone have the touchpad working with big sur already?
 
Last edited:
I would highly recommend using rEFInd for your triple boot. My rEFInd is setup to boot OpenCore, Windows, Grub and a specific Linux kernel directly. You can setup the config file in rEFInd to automatically locate EFI files in your EFI folder. I have my OC config set so that it doesn't show the OC menu on boot to simplify things and on the rare occasion i need to alter anything I just edit the config.plist to show the menu. rEFInd is just a boot manager so it won't have any ACPI injection issues with Windows the way that OC will. There is a fork of OC that only does injection for the Mac partition but I haven't even looked into it because rEFInd provides me with better options for my setup.
 
Last edited:
Silent99 does the touchpad work for you?
Have you tried applying the dsdt patch to set the pin to 55 for the touchpad that Navaira lists on the first page?

Also, I upgraded big sur to 11.2.2 and it went smoothly.

Current status:

Working:
- 4k screen works fine (brightness control from the menu bar works fine)
- occasional split second glitch (can live with this though)
- internal speakers work (sound a bit tinny though compared to windows)
- usb ports appear to work
- bluetooth (internal chip replaced with broadcom)
- wifi (internal chip replaced with broadcom)
- sleep seems to kind of work.. need to long press the power button to wake it back up
- app store .. can download apps and upgrade big sur

Not working:
- touchpad (driving me a bit nuts that it's not working)
- touch screen (not a big deal)
- battery status
 
Last edited:
The only thing that doesn't work for me is the internal microphone, which also won't register in Linux at all and I doubt that will change. Sleep works okay... I think there is a way to enable S3 sleep, but I never really had that working in the past either so I haven't bothered to try.
Have you tried the EFI folder that I posted? You'd have to edit the config.plist to add ROM, UUID, Serial number, and MLB as I removed those. I'm curious how that will work for you.
 
Last edited:
What version of the bios do you have?
Did you dump your DSDT.aml and then apply any patches to it? If so, which ones?

I tried using your EFI but it fails to boot. wcos namespace not found acpi style error.
Which is weird as I'm comparing your EFI and mine now and I thought I was using yours ... so far everything is the same.. confused!
 
Last edited:
I first tried your EFI folder instead of mine, @Silent99 – it didn't help me with the BS install. So I used my folder, updated OpenCore to 0.6.6, created another installer USB for Big Sur, got past install – now I get stuck on:

ALF, old data swfs_pid_entry (ptr), updaterules_msg (ptr), updaterules_state (ptr)tx_flush:1074: disk4 xld 1237 tx stats: # 20 finish 20 enter 465 unit 0 8ms close 8us flush 16320us

…on trying to boot for the first time.

First I tried to install over Catalina, then formatted and tried anew – so far, no luck.

I removed Windows completely, because of course there would never be any BIOS updates, and I just saw there's a Jan 21 BIOS update. Looks like I shouldn't touch that one though…

Will now compare what is and isn't in your EFI vs mine.
 
Can't figure it out for love nor money. Tried Big Sur recovery, which to my surprise even loaded, but got me to "disk5 is write locked". Then I tried to use the USB installer again, and "disk5 is write locked" repeated 6 times, at which point the fun ends, is the new error.

Edit: oh wait, I just remembered that the installer takes 16 minutes to load because of the Brcm driver. Will delete it for the time being and see what happens.
 

Attachments

  • IMG_1052.jpg
    IMG_1052.jpg
    387.1 KB · Views: 58
Oh crap!!!

I tried to downgrade the BIOS and bricked it.
What do I do?!?
:((((
 
Status
Not open for further replies.
Back
Top