Recent content by robinhuang

By booting into verbose mode you should see the output. Attach a photo of it, as it's impossible to help you debug without clues.

What do you mean by sluggish? What action is behaving wrongly?

You should be able to format it as HFS+ format w/ GUID partition table with either disk utility (by selecting the device and hitting "erase" or "partition" button) or the disktuil command in terminal. There isn't and has never been one button called "scheme", I think.

tl;dr, a fresh install wouldn't be much helpful for debugging sleep issues. Sleeping is tricky, which needs some time to be figured out. Do you already have proper power management? You need native power management for sleep to function well. Also, you may take a look at the sleep log by the...

Boot with verbose mode to check the boot outputs. Use left/right keys to select the partition to boot, hit spacebar, tick the "-v verbose" option and hit "boot with selected options"

If you're asking about the ethernet, it's IntelMausiEthernet.kext.

It sort of "works", but you'll get random crazy artifacts. Please take a look at this thread. And yes, using the iGPU for installation process is a good idea. Doing so eliminates issues from dedicated GPU.

No offense. The config.plist really made me laugh out loud :D Glad to see you making big progress.

For a (assuming that it is) kernel panic, as they're kept in /Library/Logs/DiagnosticReports, check out there first.

As you're dealing with ethernet problems, at least you could find the specs of your Ethernet chipset out - it's kinda hard for everybody else here to guess about.

Sometimes a faulty USB thumb drive do that. Have you tried using another one?

Both GTX 660Ti and GTX 550Ti aren't (fully) supported in HighSierra. Use iGPU or switch to a new GPU instead.

The working kext for Thisbe mono would be the latest version of RealtekRTL8111.kext. If you have that one installed but it's still not working, maybe you're running into mobo-related issues. I randomly found that out by using a linux live cd to test the connection. Solved that by completely...

If I remember it right, kernel panic logs are now kept in /Library/Logs/DiagnosticReports directory, not /System/Logs. Maybe you can check there.

Filter out what process(es) is eating up your CPU by looking at the activity monitor.