Hi forum folks!
nhat179,
Any luck with the sleep/usb issue? The only thing I can think of is in your initial set up options in multibeast, in the misc section, you want to make sure that the USB 3.0 - Universal is not checked. It is unnecessary on this build. I also am not using EvOreboot (unchecked), and that may have something to do with your issue if you are using that. If you can remember checking either of those I'd suggest hunting down those kexts and removing them.
There are several good benchmarking programs that folks use. Geekbench 3 (good overall benchmark of system), blackmagic disk speed test (for HD/SSD), Unigine Heaven (for GPU), cinebench (CPU/GPU), luxmark render (CPU/GPU). There are a million more out there, but those are popular and have free versions. There is a thread on this site somewhere that has links to them all, but a google search will provide the same.
palote99,
Thank you for your appreciation!
I know the pain of system definition testing
For the most part I was able to switch freely between them and not run into any problems, until I tried 5,1 sys def. After trying that I was unable to boot back up because of panics I didn't understand.
I would suggest firstly going back to a functional system definition you are comfortable with (3,1 would be my suggestion, I tried a lot of different ones and even though 3,1 has been around for a long time, I have the most stability with it, as well as the highest benchmarks).
Once you are back on a a system definition you know worked, find the audio driver/kext and delete it. Then open multibeast and reinstall it.
Then open disk utility and verify/repair permisssions on your hd, then I also like to run kext utility (which can be downloaded from this website in the downloads section under community software).
Restart and open your sound preferences, make sure the proper input/output selections have been made (I use external speakers plugged into the motherboard, an old logitech system. my sound preference selections for sound output are; Internal Speakers / Built-in). Do some testing.
If that doesn't work I hate to say it, but I would probably just start over again, I had to do that quite a few times and it really doesn't take too long, in many of my cases doing this was much faster than finding and fixing a problem by other means. You could also open a thread in the forums "post installation" "Audio" subforum with a detailed description, perhaps someone there will know a more simple fix than I do.
