Intel i5-8400 using UHD 630 Graphics

[HackinMax]

If you’re using DisplayPort it should work. But if you’re limited to HDMI, you can use an unsupported device ID such as 0x3E98. That will trigger the default VESA driver, but for boot purposes it should suffice.

Not so far. It doesn't matter if I connect DP or HDMI, it freezes in the same place -
every. single.. time.

I'm about done with this board. I haven't been this frustrated since Windows 95 was released.

The main installation should not be damaged... considering I've been basically unable to access it throughout this process. But, I'm about 'there' myself. I may just blast it and reinstall.

If this gives me this much problem after that, I will put it in a larger case and slap in a RX 580 from the closet. However, I see that people have gotten the board working... with HEADLESS IGPU. But, I don't see one where the iGPU is used exclusively.

It's time to step away and consider my options.

 

[HackinMax]

If you’re using DisplayPort it should work. But if you’re limited to HDMI, you can use an unsupported device ID such as 0x3E98. That will trigger the default VESA driver, but for boot purposes it should suffice.

I am very disappointed to report that it did not work either way. It still hangs at exactly the same place. This board will not work with any of the suggestions I have tried.
I wish I could remember how I got Unibeast to work that once.

At this point, there is no way I can even reinstall. I created a brand new Unibeast stick and started from the beginning. But, I only get the 'prohibited' sign when I try to run install.
none of the available EFI samples available work either - even after stripping away the unneeded stuff.

 

[jb007]

I am very disappointed to report that it did not work either way. It still hangs at exactly the same place. This board will not work with any of the suggestions I have tried.
I wish I could remember how I got Unibeast to work that once.

At this point, there is no way I can even reinstall. I created a brand new Unibeast stick and started from the beginning. But, I only get the 'prohibited' sign when I try to run install.
none of the available EFI samples available work either - even after stripping away the unneeded stuff.

I feel your disappointment.

With the new Unibeast, if you select the verbose and halt on kernel panic, what error messages do you get?
Also at the clover menu have you cleared the NVRAM (this is different to the kernelcache), by pressing F11 (or is it F12?), the system should clear the NVRAM and reboot. Make sure also that you have above 4G enabled in your BIOS.

Jim

 

[HackinMax]

I feel your disappointment.

With the new Unibeast, if you select the verbose and halt on kernel panic, what error messages do you get?
Also at the clover menu have you cleared the NVRAM (this is different to the kernelcache), by pressing F11 (or is it F12?), the system should clear the NVRAM and reboot. Make sure also that you have above 4G enabled in your BIOS.

Jim

It's F11. I have the sequence memorized at this point. But, clearing the NVRAM does not seem to help anything. And, I am always in verbose mode now so I can see that it hangs at the same place every time.

I am trying to learn what to do in order to at least boot again. I miss the day that it booted fine. But, the graphics were corrupted... Ah... good times they were.

 

[HackinMax]

Hello again!

There has been progress!

MiniZee is back from the dead... Although, not exactly ready for action.

I have managed to patch together an EFI that reliably boots into the system (attached)

Video is UHD rez. But, acceleration and higher features are not available. Tearing and other motion defects are obvious.
(I will try the FB-Patcher approach once I get my courage back up to dive in again.) At least I have a bootable Unibeast key again.

most USB ports are completely non-functional after boot (They work long enough to boot from the USB key... and then gone.) I located two (directly under the Ethernet port) that work for the mouse and keyboard. I realize there is a patch for this somewhere. But, at this point, I would rather wait for advice on the proper approach.

I have a TP Link T4U V3 that works fine with my mac-actuals... But, installing the driver on my hack results in a non-booting system. Fortunately, I was able to boot in safe-mode, and deep-six the driver.

The Bluetooth dongle (forgot the brand. But, it's on the buyer's guide) of course, doesn't work as most of the USB ports are dead.

QuickView and Preview actually work at this point. So, the IGPU is operating, at least well enough for that. See screen shots

Shutdown and Restart do not work. The verbose output indicates that the system is 'finished'. But, the system never cycles the power mode.

Well, that is the best I can do today on this one. What an uncooperative beasty this thing is.

Any assistance, advise, or even laughter at my expense are quite welcome. It's been 24 hours now. And, YAY! I have a bootable MiniZee again...

Onwards and Upwards! ... or is it "In for a penny... in for a pound?"

 

[CaseySJ]

Hello again!

There has been progress!

MiniZee is back from the dead... Although, not exactly ready for action.

I have managed to patch together an EFI that reliably boots into the system (attached)

Video is UHD rez. But, acceleration and higher features are not available. Tearing and other motion defects are obvious.
(I will try the FB-Patcher approach once I get my courage back up to dive in again.) At least I have a bootable Unibeast key again.

most USB ports are completely non-functional after boot (They work long enough to boot from the USB key... and then gone.) I located two (directly under the Ethernet port) that work for the mouse and keyboard. I realize there is a patch for this somewhere. But, at this point, I would rather wait for advice on the proper approach.

I have a TP Link T4U V3 that works fine with my mac-actuals... But, installing the driver on my hack results in a non-booting system. Fortunately, I was able to boot in safe-mode, and deep-six the driver.

The Bluetooth dongle (forgot the brand. But, it's on the buyer's guide) of course, doesn't work as most of the USB ports are dead.

QuickView and Preview actually work at this point. So, the IGPU is operating, at least well enough for that. See screen shots

Shutdown and Restart do not work. The verbose output indicates that the system is 'finished'. But, the system never cycles the power mode.

Well, that is the best I can do today on this one. What an uncooperative beasty this thing is.

Any assistance, advise, or even laughter at my expense are quite welcome. It's been 24 hours now. And, YAY! I have a bootable MiniZee again...

Onwards and Upwards! ... or is it "In for a penny... in for a pound?"

One immediate issue I see is that you have both FakeSMC and VirtualSMC in your /Library/Extensions folder. Only 1 is allowed. You should delete VirtualSMC and run Kext Utility to rebuild kernel cache (just running it will rebuild cache) and wait for it to finish (the spinner on bottom left must stop, followed by Quit button appearing on bottom right).

 

[jb007]

Cool
Will look into it tomorrow after work about same time as today.
I’m down to the beach house for the rest of the week, but the internet us on and will be taking the Z370 to start writing the new thread. Let us know how it all goes, and I’ll try to help we’re I can.
Remember backup, backup and backup!

Jim

 

[HackinMax]

In preparing for the PB-Patcher process, I noticed that it was necessary to remove some settings from the plist... Well, these are the very settings that 'make it go'.

But, I followed the instructions faithfully and, of course it will not initialize video at all without those settings.

This is what we call a 'catch-22'.

I'm going to back up a step and re-install the FB patches previously posted. Let's try that. FB-Patcher is a non-starter if the required prep for the app makes the system un-bootable.

 

[CaseySJ]

Here's a more complete reply:

• As mentioned in previous post, FakeSMC and VirtualSMC are currently installed in /Library/Extensions. Only one is allowed at a time. VirtualSMC should be deleted (with Finder) and kernel cache should be rebuilt (simply running Kext Utility will rebuild caches).
• In CLOVER/drivers64UEFI there are two memory fix drivers: (a) OsxAptioFix2Drv-free2000 and (b) AptioMemoryFix-64. Only one is allowed at a time. AptioMemoryFix-64 should be deleted.
• USB port limit patch does not seem to work when USBInjectAll is used. USBInjectAll injects all ports, but MacOS subsequently truncates the list to the first 15. So the attached image shows the result where only the USB 2.0 ports are activated. For the time being, we can manually disable a few of the unused USB 2.0 ports to allow SSxx (USB 3.0) ports to come through, but your best solution is to create a custom USB SSDT (I know this sends shivers of fright)! Temporarily disabling some ports can be done easily by adding this argument to the Boot section of config.plist using Clover Configurator:
  • -uia_exclude=HS01,HS02,HS10,HS11,HS12
  • This will allow 5 other ports to come through (USB 3.0 SSxx ports will come through).
• I've also modified your config.plist to better handle USB ports, SATA ports, and CPU power management for sleep/wake. Feel free to try it (backing up existing file first).

I certainly don't want to add any unnecessary frustration -- I know how painful this has been. So please create a full backup of your system as @jb007 very wisely suggested. This will be your restore point and it should provide peace of mind before undertaking further changes.

 

[CaseySJ]

In preparing for the PB-Patcher process, I noticed that it was necessary to remove some settings from the plist... Well, these are the very settings that 'make it go'.

But, I followed the instructions faithfully and, of course it will not initialize video at all without those settings.

This is what we call a 'catch-22'.

I'm going to back up a step and re-install the FB patches previously posted. Let's try that. FB-Patcher is a non-starter if the required prep for the app makes the system un-bootable.

Thank you for the feedback. That's very helpful actually. I've clarified Preflight Check item #8.

By the way, patching the framebuffer should be the last thing to do! It's more important to get other devices in the system configured and stabilized.