- Joined
- Nov 6, 2012
- Messages
- 5
- Motherboard
- CustoMac Mini Gigabyte Z77N-WIFI MacOSX 10.8.2
- CPU
- i5 3570K
- Graphics
- HD 4000
- Mac
- Classic Mac
- Mobile Phone
Article: Building a CustoMac: CustoMac Mini 2012
Thumbs up by the way for this excellent site.
This was my first Hackintosh and thanks to the clarity of the guides and forum feedback it went flawlessly.
For the record at the time of writing my build:
Case: CoolerMaster Elite 120
MB: Gigabyte Z77N-WIFI
CPU: Intel Core i5 3570K
RAM: Corsair memory 16GB Vengence Performance Kit (2x8GB) DDR3
PSU: Coolermaster PSU 520W Silent Pro M2 modular
HD: Some leftover 250GB WD SATA II drive (but new unused) for the moment to tide me over.
Built in HD graphics only for the moment, using on board DVI to a Philips 1680x1050 LCD (few years old).
Mountain Lion 10.8.2.
Network: Ethernet (on board)
Keyboard: Apple extended (wired)
Standard set up on Multibeast DSDT free
Bluetooth works.
Logitech c270h works! (btw UKP 9.99 from J Sainsbo's ! in UK)
No over-clocking (yet, want to explore a stable base config for a while)
which brings me to my only noticeable flaw so far which only lasts for two minutes:
after waking from sleep, logging in, all is well for like a few minutes (maybe 2-4 but not timed it) then the monitor goes black (like a blank screensaver kicks in). I can hear the MacOSX system is still up and pressing keys or mousing does not bring it back. But! If left alone for a minute or two more, it comes back by itself and is no trouble at all then all day long.
Put to sleep again, wake, start work, then after a couple of minutes… blank screen, then a few minutes more back OK again.
Note: it only does this once per wake from sleep and only after a couple of minutes from waking. Always comes back.
I do not think It is triggered by anything I am doing in MacOSX when it happens whatever I am doing at the time.
The OS is not asleep, its just the display part. Not touched the BIOS, all standard stuff as far as I can see.
Anyone else? Note I am only on HD4000 off the i5 and had a textbook trouble free install from the go thanks to this site and this is the only odd behaviour I have found (so far). Any ideas anyone?
Thumbs up by the way for this excellent site.
This was my first Hackintosh and thanks to the clarity of the guides and forum feedback it went flawlessly.
For the record at the time of writing my build:
Case: CoolerMaster Elite 120
MB: Gigabyte Z77N-WIFI
CPU: Intel Core i5 3570K
RAM: Corsair memory 16GB Vengence Performance Kit (2x8GB) DDR3
PSU: Coolermaster PSU 520W Silent Pro M2 modular
HD: Some leftover 250GB WD SATA II drive (but new unused) for the moment to tide me over.
Built in HD graphics only for the moment, using on board DVI to a Philips 1680x1050 LCD (few years old).
Mountain Lion 10.8.2.
Network: Ethernet (on board)
Keyboard: Apple extended (wired)
Standard set up on Multibeast DSDT free
Bluetooth works.
Logitech c270h works! (btw UKP 9.99 from J Sainsbo's ! in UK)
No over-clocking (yet, want to explore a stable base config for a while)
which brings me to my only noticeable flaw so far which only lasts for two minutes:
after waking from sleep, logging in, all is well for like a few minutes (maybe 2-4 but not timed it) then the monitor goes black (like a blank screensaver kicks in). I can hear the MacOSX system is still up and pressing keys or mousing does not bring it back. But! If left alone for a minute or two more, it comes back by itself and is no trouble at all then all day long.
Put to sleep again, wake, start work, then after a couple of minutes… blank screen, then a few minutes more back OK again.
Note: it only does this once per wake from sleep and only after a couple of minutes from waking. Always comes back.
I do not think It is triggered by anything I am doing in MacOSX when it happens whatever I am doing at the time.
The OS is not asleep, its just the display part. Not touched the BIOS, all standard stuff as far as I can see.
Anyone else? Note I am only on HD4000 off the i5 and had a textbook trouble free install from the go thanks to this site and this is the only odd behaviour I have found (so far). Any ideas anyone?