MultiBeast 5.2 Update
- Thread starter MacMan
- Start date
- Status
- Joined
- Oct 13, 2012
- Messages
- 9
- Motherboard
- GIGABYTE z370 SLI Gaming
- CPU
- i5-8600K
- Graphics
- GTX 1050 Ti
- Mac
- Classic Mac
- Mobile Phone
Article: MultiBeast 5.2 Update
Why would any of you here who are reportedly having issues with this new version of MB (5.2.1) not have already cloned a complete back-up 'test' boot build on another HD, or partition within your Hackintosh for program upgrading and bug/tweak fixes like this one? Once I had a fully operational and stable 10.8.2 build up and runnin, any of my future testing of any new program releases and/or bug fixes are automatically done on the back-up cloned copy, and NEVER, ever on my primary working build. If something goes awry on my cloned 'test' build, I can try and troubleshoot a fix, or just erase the entire drive/partition and start another new test clone all over again.
Why would any of you here who are reportedly having issues with this new version of MB (5.2.1) not have already cloned a complete back-up 'test' boot build on another HD, or partition within your Hackintosh for program upgrading and bug/tweak fixes like this one? Once I had a fully operational and stable 10.8.2 build up and runnin, any of my future testing of any new program releases and/or bug fixes are automatically done on the back-up cloned copy, and NEVER, ever on my primary working build. If something goes awry on my cloned 'test' build, I can try and troubleshoot a fix, or just erase the entire drive/partition and start another new test clone all over again.
- Joined
- Dec 14, 2012
- Messages
- 9
- Motherboard
- Motherboard OR System/Laptop make and model names > See Forum Rules!
- CPU
- i7-3770K
- Graphics
- GT 520
- Mac
- Mobile Phone
I have EVGA GFORCE GT 520 2GB, which option should i use? please help me with this.
- Joined
- Aug 17, 2012
- Messages
- 525
- Motherboard
- Gigabyte Z490 Aorus Pro AX
- CPU
- i7-10700K
- Graphics
- RX 570
- Mac
- Mobile Phone
@stevielee
You are right. If a new update is available we should always try this on a backup drive. I learned my lessons
You are right. If a new update is available we should always try this on a backup drive. I learned my lessons
- Joined
- Oct 25, 2012
- Messages
- 9
- Motherboard
- Gigabyte GA-Z77X-UD5H
- CPU
- i5-3570K
- Graphics
- RX 580
- Classic Mac
- Mobile Phone
I was having the same KP with my EVGA GTX 670 FTW card. I deleted the GPUSensors.kext from S/L/E for a successful boot, then found this thread.
I don't know anything about Git, but I downloaded the HWSensors-master .zip file from https://github.com/kozlek/HWSensors.
I just don't know what to do with it. I was expecting to find a new GPUSensors.kext file for me to put back in, but it seems more complicated than that.
I'm going to clone my drive before I start tinkering with it. Any advice on how to install kozlek's fix would be greatly appreciated!
I don't know anything about Git, but I downloaded the HWSensors-master .zip file from https://github.com/kozlek/HWSensors.
I just don't know what to do with it. I was expecting to find a new GPUSensors.kext file for me to put back in, but it seems more complicated than that.
I'm going to clone my drive before I start tinkering with it. Any advice on how to install kozlek's fix would be greatly appreciated!
- Joined
- Feb 20, 2011
- Messages
- 195
- Motherboard
- Asus Maximus Hero XI Z390
- CPU
- i9-9900K
- Graphics
- RX 560
- Classic Mac
- Mobile Phone
Hi,
As a small improvement I would like to suggest that Multibeast should not generate a new SMserial in the Smbios.plist every time it is run, but instead use the existing SMserial if there is one already -- I have the feeling some software packages use it for their activation verification, so if one runs Multibeast to reinstall Chimera or something else after a system update, one has to remember to restore the previous SMserial since Multibeast writes in a new one every time.
As a small improvement I would like to suggest that Multibeast should not generate a new SMserial in the Smbios.plist every time it is run, but instead use the existing SMserial if there is one already -- I have the feeling some software packages use it for their activation verification, so if one runs Multibeast to reinstall Chimera or something else after a system update, one has to remember to restore the previous SMserial since Multibeast writes in a new one every time.
- Status