Would this work on a M83 Tiny?

[uberfunk]

Which do you have: an M73 Tiny or an M93p?: Neither, M83 Tiny.

Do your specifications match the ones shown in the README.md? (not including the USB WiFi adapter): Very close...

If your specifications do not match, what are your specifications?: Intel Core i5-4590T @ 2.00Ghz 2x4GB (8GB) of DDR3-1600 Intel HD Graphics 4600 256GB SSD Intel I217-LM Full M83 Tiny specs

What version of OS X/macOS are you using?: I am planning on installing Monterey.

What is your issue?: As the title says, would this work on a M83 Tiny? Specs are similar and it's from the same era as the M73 and M93 so I don't see why this wouldn't work. But can you see any "gotchas" I might run into (other than the wifi not working and no VGA)? Thanks!

[UHDbits]

Huh, I never knew that existed! According to the specs, I see no reason why this configuration wouldn't work on this computer. Most of the bugs are pretty minor, there are no other ones that I can think of that should really affect you other than the two mentioned. I recommended double-checking the issues listed to make sure there is nothing that should affect you, there should be no extra issues caused by the M83.

If you do test this, I would greatly appreciate it if you let me know if it works! Thank you!

[UHDbits]

Sorry, just noticed it said you are planning to install Monterey, so the Ventura issues don't apply.

[humblepi4]

I have been trying to get Monterey working on my M83 TFF and I'm having issues.

cpu: i5-4570T device id 12040000 (0x412) igpu: HD4600 wifi: AzureWave AW-CE123H (BCM94352HMB) 256 SSD 2x8GB DDR3

I've tried using your efi but get all kinds of errors when throwing your SSDTs for the 4 core i7 at my 2 core i5. I've tried creating my own SSDTs with SSDTTime in windows but the system bootloops before I can see whats happening. I've spent hours on it and it's late so I will try and get some better debug info tomorrow. I've tried the prebuilt SSDTs and haven't reached the installer that way either. One major problem is that I'm using VGA and/or a passive DP to HDMI adapter. I don't own a display with a DP. What's interesting is that I've had success with both VGA and DP working (on Monterey) with this machine when using "easy and fast" method and designating all three ports as DP among some other settings under DeviceProperties. I just could not get hardware acceleration to work with that approach which is one of many reasons I prefer a more authentic approach. In the meantime I have ordered a VGA to HDMI active adapter and will be testing that out soon. I like the work here at this repo. Any input on things I could try would be great and I'll be back with better debug info. I've also tried SMBIOS for imac18,1 and macmini7,1 which is what I had working before.

Here's my DeviceProperties settings for display - these should work for anyone with a matching platform id (0300220D) and 3 ports. The "00040000" designation for "type" is for Display Port and more info can be found on the Whatevergreen github page:

[humblepi4]

OK still getting reboots.

Things I've changed:

added usb maps using usbtoolbox (no native setting) added 2 kexts and removed existing usbmap.kext used gensmbios to change to macmini7,1 (tested with and without this) replaced files with opencore debug 0.9.1 and set debug settings under Misc as per opencore guide replaced SSDTs with prebuilt versions removed SSDT-USBX (opencore guide suggests this is for Skylake and newer and I'm Haswell) used command-shift-R to rebuild config in propertree

opencore-2023-04-13-162020.txt

opencore-2023-04-13-162146.txt

[UHDbits]

Thanks a ton for all the information! I never did think about the SSDTs being different between the M73 and M83 Tiny, and since I built my SSDTs using SSDTTime for my computer, I guess they don't work for others. I'll think about replacing tehm with the prebuilts, just to make this config more compatible, but I also like to make the configurations as lightweight as possible.

By the way, SSDT-USBX is actually required for Skylake SMBIOS, not just Skylake machines. That's why I added it because I'm using a Kaby Lake SMBIOS for Ventura support, so that's why it's there. Do you know if the USBMap worked with native kexts, or did you just test it with the two kexts? Again, I just used the singular kext because they seemed lighter weight, since it was using the native USB properties. But, this also causes the USB maps to be SMBIOS specific, which is why you need to enter the SMBIOS that you are using in the USBToolbox application.

Also, thanks for the info on getting VGA working! I'll check to see if that works here (with graphics acceleration), and if it does I'll add those settings to the configuration.

I'll try to check out your OpenCore logs as soon as possible, hopefully by the end of today. I just kind of quickly looked over your comments to respond to them, so sorry for any mistakes made in this comment. I'll look at all of this closer later. Thanks a ton once again!

[UHDbits]

Also, could you try adding these boot arguments to the config? These should hopefully stop the computer from rebooting when it crashes, and will allow you to take photos of the macOS verbose logs.

"-v debug=0x100 keepsyms=1" Make sure to add them without the "s

[humblepi4]

Ok thanks! I'm going to start again with your efi and leave things like the ssdt-usbx. I will toy around with different usb scenarios and report back. I havnt got far enough to know if they're working but I could do some testing on the "fast and easy" installation if that would help. I will set the boot args as you suggested. side note: in the image above the "dpcd-max-link-rate" designation of 14 is for 4k output. Again more info under the spoiler at whatevergreen. I'm using vga and hdmi which are listed on lenovo specs as having max output of at or near 1080p. I have also tried setting the max link rate to 1080p and doesn't seem to make a difference. I assume that the max setting still allows for lower resolutions.

[UHDbits]

Yeah I know that (I'm currently working on an OC config for a 4K laptop), but 4K60 already seems to work on this config, at least for the M73 Tiny, because I'm using a 4K60 monitor with it right now. Does it not work for you without that?

On Thu, Apr 13, 2023, 11:04 AM humblepi4 @.***> wrote:

Ok thanks! I'm going to start again with your efi and leave things like the ssdt-usbx. I will toy around with different usb scenarios and report back. I havnt got far enough to know if they're working but I could do some testing on the "fast and easy" installation. I will set the boot args as you suggested. side note: in the image above the "dpcd-max-link-rate" designation of 14 is for 4k output. again more info under the spoiler at whatevergreen.

— Reply to this email directly, view it on GitHub https://github.com/UHDbits/M73-Tiny-OpenCore/issues/14#issuecomment-1507402336, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP6UVFOOQWM5U4M37QR74ELXBA525ANCNFSM6AAAAAAWFZOO54 . You are receiving this because you were assigned.Message ID: @.***>

[humblepi4]

Not sure. Just tried to throw everything I could at the VGA to make it appear as Display Port because I read somewhere that some motherboards assign a display port designation to the VGA and thought I might get lucky. Something is allowing it to work on the "fast and easy" install. I know he is using the RestrictEvents.kext and maybe that has something to do with it. It remains to be seen if I can get acceleration working through VGA. I've read that VGA doesn't work at all with macOS and so far that is not true with this setup.

[humblepi4]

OK. No reboots but still can't get to installer.

I re-downloaded your efi. replaced your SSDTs with my SSDTs including the USBX - built them with ssdttime I added my usbmap.kext and the usbtoolbox.kext (documentation says to add this kext too) - used native setting and imac18,1 added boot args and debug settings in misc reloaded the plist That's it The boot hangs

opencore-2023-04-13-194800.txt

If you want I can get system report dump too.

I noticed something strange when building the SSDTs ("Not Valid EC Device")

[UHDbits]

I don't think there's an issue with that error message, because I think what that message means is that it is verifying if the EC would already work without issues in macOS, but if it doesn't, then it will continue to create the patch.

Are you trying to run 4K through a VGA port?

[UHDbits]

Also it would be great if you could get the system report dump, or just send an image at the end of the verbose messages.

[humblepi4]

Are you trying to run 4K through a VGA port? no I left your settings

[UHDbits]

Mhm, that's definitely an issue with the GPU not being initialized properly, because that "gIOScreenLockState" message basically means that booting has basically finished, and it's initializing the GPU. Have you been able to test it out of anything other than the VGA port?

[humblepi4]

Getting the DP to HDMI adapter to display is tricky and random. I ran again with VGA and the DeviceProperties settings from before and got something a bit different:

[UHDbits]

It's still ending up being the same thing in that case, with "IOG flags 0x3 (0x51)" meaning a similar thing to what was mentioned above.

[humblepi4]

It's hard to read but here's a pic of the -v through the adapter.

this is a passive DP to HDMI adapter with an old sh*tty and very small monitor.

[uberfunk]

I just wanted to add, that I ended up following the OpenCore documentation and built my EFI folder but used the EFI folder and kexts here as a reference. Was a major help. Got Big Sur up and running and everything seems to work (USB ports mapped, Intel wifi, but dunno if VGA works). I'll add my EFI or list out the kexts that I'm using later when I get home from work.

I want to get Monterey installed on it but encountered an issue trying to get OpenCore Legacy Patcher to work. The "Build and Install OpenCore" button is greyed out and it doesn't seem to like my Model number.

[humblepi4]

I guess I need to get a display with DP ports Thanks for the help.

[UHDbits]

OpenCore Legacy Patcher doesn't need to be used on Monterey, only on Ventura. Plus, that function doesn't work on hackintoshes, all you need to do it "post-install patches"

On Thu, Apr 13, 2023, 2:43 PM uberfunk @.***> wrote:

I just wanted to add, that I ended up following the OpenCore documentation and built my EFI folder but used the EFI folder and kexts here as a reference. Was a major help. Got Big Sur up and running and everything seems to work (USB ports mapped, Intel wifi, but dunno if VGA works). I'll add my EFI or list out the kexts that I'm using later when I get home from work.

I want to get Monterey installed on it but encountered an issue trying to get OpenCore Legacy Patcher to work. The "Build and Install OpenCore" button is greyed out and it doesn't seem to like my Model number.

— Reply to this email directly, view it on GitHub https://github.com/UHDbits/M73-Tiny-OpenCore/issues/14#issuecomment-1507644977, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP6UVFIXTDXUCUOY35OJOILXBBXQBANCNFSM6AAAAAAWFZOO54 . You are receiving this because you were assigned.Message ID: @.***>

[UHDbits]

Okay, so I think in the README.md I may just suggest using prebuilt SSDTs for the M83 and M93p? I'd prefer to keep the configuration itself as lightweight as possible, so I will just provide links to the prebuilt SSDTs and replace them. But, of course, I'm not exactly sure if this would completely finish the problem. I may also just put in known issues that it's possible that the M83 Tiny and M93p may not work with the configuration, and suggest using the configuration as a guide (which is the point of the config anyways), and make your own. I'll think about which one I will do.

[uberfunk]

@humblepi4 Sorry for the major delay. I'm not sure if all of these are needed but as it is currently, the M83 Tiny works. Open to suggestions for refinement. :)

ACPI> SSDT-EC.aml SSDT-PLUG.aml SSDT-USBX.aml

Drivers> HfsPlus.efi OpenCanopy.efi OpenRuntime.efi ResetNvramEntry.efi ToggleSipEntry.efi

Kexts> AppleALC.kext BlueToolFixup.kext IntelBluetoothFirmware.kext IntelBTPatcher.kext IntelMausi.kext itlwm.kext Lilu.kext SMCProcessor.kext USBPorts.kext VirtualSMC.kext WhateverGreen.kext

I can post my config.plist as well, if needed.

[UHDbits]

@humblepi4, just a quite question, what version of macOS are you attempting to boot? I understand that it seems like you will need a DP display anyways (which is quite strange, I've used a DP to DVI adapter before and it's worked just fine), but I have just seen the kernel panic that you sent above and am trying to see the cause of it. If you are using Big Sur or older, please note that the latest version of the configuration does not support Big Sur. I think this may be causing your issues, but it's also quite possible that I am wrong.

[humblepi4]

@humblepi4, just a quite question, what version of macOS are you attempting to boot? I understand that it seems like you will need a DP display anyways (which is quite strange, I've used a DP to DVI adapter before and it's worked just fine), but I have just seen the kernel panic that you sent above and am trying to see the cause of it. If you are using Big Sur or older, please note that the latest version of the configuration does not support Big Sur. I think this may be causing your issues, but it's also quite possible that I am wrong.

Hey. Sorry for the delay I was working on another build and didn't check emails. I'm going to get back into this m83 today and I will let you know how things go. I was on Monterey. Let me know if you need anything specific.

[UHDbits]

Yeah, no problem! I'm going to do some research to try to fix the kernel panic you had with the DP adapter.

On Thu, Apr 27, 2023, 6:59 AM humblepi4 @.***> wrote:

@humblepi4 https://github.com/humblepi4, just a quite question, what version of macOS are you attempting to boot? I understand that it seems like you will need a DP display anyways (which is quite strange, I've used a DP to DVI adapter before and it's worked just fine), but I have just seen the kernel panic that you sent above and am trying to see the cause of it. If you are using Big Sur or older, please note that the latest version of the configuration does not support Big Sur. I think this may be causing your issues, but it's also quite possible that I am wrong.

Hey. Sorry for the delay I was working on another build and didn't check emails. I'm going to get back into this m83 today and I will let you know how things go. I was on Monterey. Let me know if you need anything specific.

— Reply to this email directly, view it on GitHub https://github.com/UHDbits/M73-Tiny-OpenCore/issues/14#issuecomment-1525748929, or unsubscribe https://github.com/notifications/unsubscribe-auth/AP6UVFJSTEJU6IN4KPXVOZTXDJ3U3ANCNFSM6AAAAAAWFZOO54 . You are receiving this because you were assigned.Message ID: @.***>

[humblepi4]

Right now I'm using VGA to HDMI adapter. I copied your EFI and replaced the SSDTs with my own and generated a new SMBIOS (iMac18,1) Currently installing Ventura. *couldn't get display through the DP adapter - I will try again if I get through the install

[humblepi4]

I have successfully installed ventura now when I try to do root patching with OCLP it's telling me that SIP is enabled. I tried disabling it in plist and also with the toggle sip option but I still get the same message from OCLP. Any ideas? Do I need it disabled in plist AND toggle sip? I am going to try with command from recovery. - nope that didnt' work either

OK the trick was to reset nvram After root patch no boot. I need to enable debugging and take a closer look. Taking a break

[UHDbits]

Thanks for the info, nice to know that it looks like replacing the SSDTs in the config at least partially fixes M83 Tiny support. I'll make sure to add that information to the repository soon. Also, were you able to get the VGA output working? Not sure if you did anything to fix it, but let me know if you did.

After root patching does it boot loop or just kind of freeze?

[humblepi4]

Thanks for the info, nice to know that it looks like replacing the SSDTs in the config at least partially fixes M83 Tiny support. I'll make sure to add that information to the repository soon. Also, were you able to get the VGA output working? Not sure if you did anything to fix it, but let me know if you did.

After root patching does it boot loop or just kind of freeze?

I built the same three SSDTs that are present in your ACPI folder using SSDTTime in windows and replaced the originals with the ones for m83 with i5-4570T. Opencore menu and installation worked through the VGA to HDMI adapter and I was able to boot to ventura desktop but no hardware acceleration (as expected) after running the OCLP root patch it froze during boot sequence - no bootloop. I will fire it up with debug settings and see if I can get any info.

[humblepi4]

It looks to me like maybe it's the VGA issue again. When I power the machine up with the DP to HDMI the display will show the lenovo splash then the 1st boot sequence text before the OC menu then I lose display. The same thing happens with windows.

[UHDbits]

Mhn, that's interesting, maybe activating graphics acceleration causes VGA to stop working? With the DisplayPort adapter, are you able to see the OC menu at all? Or does it freeze before the boot options even show up?

[humblepi4]

Mhn, that's interesting, maybe activating graphics acceleration causes VGA to stop working? With the DisplayPort adapter, are you able to see the OC menu at all? Or does it freeze before the boot options even show up?

The above screenshot was after root patch through VGA adapter. With the Display Port adapter I can see OC menu then display goes black and looses signal. The same with windows the pre desktop screen shows then looses signal. As if the computer is switching the port off. Sometimes there's no signal at all through DP I can see and get through an install with DP

[uberfunk]

@UHDbits Did you ever have an issue with shutting down? In particular, this issue: https://dortania.github.io/OpenCore-Post-Install/usb/misc/shutdown.html

I can't seem to resolve it. Restart and Sleep work fine but Shutdown not actually shutting down is driving me nuts!

[UHDbits]

@humblepi4 Mhm, I really wish I could help more, but I'm not sure anymore if this is an issue that could be solved with new hardware (probably a DP adapter), due to the DP adapter you currently have seeming to not work properly, and VGA being a currently unfixable issue at the moment (I'll do some more research into this in the next couple of weeks, just to be sure). Sorry that I can't find a fix at the moment, again I'll do just a bit more research but I'm not sure if there is anything else that I could help with. Thanks for contributing to this issue though, and thanks for being cooperative throughout this issue!

[UHDbits]

@UHDbits Did you ever have an issue with shutting down? In particular, this issue: https://dortania.github.io/OpenCore-Post-Install/usb/misc/shutdown.html

I can't seem to resolve it. Restart and Sleep work fine but Shutdown not actually shutting down is driving me nuts!

@uberfunk Huh, I've never encountered this issue. Although, I won't be surprised if a fix for this might need to be implemented for M83 Tiny and M93p models, due to the fact, if I'm correct, all the ports on those models are USB 3.0. Meanwhile, on the M73 Tiny, all the back ports at USB 2.0. Have you already tried the fixes listed in that link that you sent? If not, then you can send me the config that you made for the M83 Tiny, and I'll attempt to add the changes to your configuration. If the fixes end up working, I'll make sure to add these to the specific instructions for the M83 Tiny and M93p that I will be making, alongside mapping USB ports and changing the SSDTs that are used.

[UHDbits]

Hey @uberfunk, I just wanted to check if you had any answer to the above question? Just double checking so that this issue doesn't get marked as Stale until it's resolved. I'm still working on adding M83 Tiny support and documentation to the configuration, but it may be a bit delayed because I'm going to be dealing with the release of Sonoma.

[UHDbits]

I have finally (seriously, finally) made the guide for M83 Tiny and M93p ThinkCentres! It's will be merged into the "sonoma" branch soon, but that branch will be merged into "main" in the next week or so. I want to thank everyone here for contributing to this issue. This issue will be closed, but if anyone here still needs some help, please feel free to reopen the issue!