Jump to content

Search the Community: Showing results for tags 'Asrock'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • InsanelyMac Lounge
    • Front Page News and Rumors
    • Reader News and Reviews
    • Forum Information and Feedback
  • OSx86 Project
    • New Releases and Updates
    • New Users Lounge
    • Developers Corner
    • Tutorials (The Genius Bar)
    • Technical FAQ
    • Installation
    • Post-Installation
    • DSDT and SSDT
    • Hardware Components and Drivers
    • Desktops
    • Notebooks
    • Netbooks
    • Tablets
    • MacMod of the Month
    • Multi-booting and Virtualisation
  • International
    • Your Language
    • Deutsch
    • Español
    • Français
    • Italiano
    • Português
    • Русский
  • Apple World
    • Mac OS X
    • Apple Computers and Hardware
    • iOS Devices
    • Mac Applications
    • Mac Programming and Development
    • iOS Programming and Development
    • Mac Gaming
    • Mac Accessories
  • Discuss and Learn
    • Windows Discussion
    • *nix
    • Apple Opinions and Discussion
    • The Great Debates
    • Internet(s), Servers, and Networks
    • Buying Thoughts, Reviews, and Recommendations
    • Mods and Overclocking
    • The Big Issues [Real Life]
  • Everything Else
    • Creativity
    • Thunderdome (Random Stuff)
    • Laughs
    • The Marketplace


  • Kexts
    • Graphics Cards
    • Audio
    • LAN and Wireless
    • Other
  • Kernels
  • Bootloaders
  • DSDTs
    • Patches
  • Pandora
  • Apps
  • Miscellaneous
  • Customization

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start




Website URL







Found 9 results

  1. Hello everyone, I managed to install Mavericks onto my system. The problem is that it can only boot in safe mode, the audio is not working and the graphics are "flickery" when something is moving on the screen. Is there a way to fix these issues? Or can someone help me configure a DSDT? Here are my specs of the hackintosh : - Intel i5-3570K - nvidia GTX650 - 8 gb ddr3 ram - 60 gb SSD Thanks everyone!
  2. Hi, I have all of my hardware (on my sig) working almost perfectly, what I do not have working is sleep/wake. When setting the computer to sleep, the screen goes black but the computer fans stay spinning. If comes of this "sleep" just fine. From what I've read it this might be fixable using a DSDT. The thing is I do not know if it is possible to use a DSDT with Clover or how to "create" one. Although I'm not computer illiterate I'm a little afraid of ruining my currently pretty nice system. Can I enable sleep/wake without the need of DSDT and using a kext instead? I currently have this BIOS flashed: http://biosrepo.wordpress.com/asrock/z77/ Can someone shed me some lights? Thanks in advance to all the community that's been so helpful since the beginning.
  3. Ciao a tutti, Chiedo un consiglio per un curioso problema che mi si presenta su un sistema come da titolo. Ho usato MyHack 3.x per l'installazione e tutto va alla perfezione. Uso i driver Lnx4Mac per Lan Realteck e Voodoo per l'audio Via. Arrivo all'aggiornamento ML 10.8.4 regolare e rete, audio e grafica vanno perfettamente. Ora vorrei collegare il mio account iCloud. Uso il sistema qui descritto. Funziona sempre, ma questa volta, al primo riavvio prima di re inserire la rete nuova, la grafica si spegne. Parte Cameleon, il sistema si avvia ma non si accende la grafica. Se non tocco org.chameleon.Boot.plist tutto regolare, appena lo modifico per aggiungere i parametri della scheda di rete come da tutorial, il sistema si avvia ma la grafica non si avvia. Ho provato tutte le combinazioni di -x, -f, -F PCIRoot o GraphicsEnable=Yes No Maybe che di solito funzionano con le Nvidia ma nulla. Appena ripristino il sistema tutto riparte. Come posso accedere per eventualmente ripristinare una versione precedente dei file modificati? Grazie
  4. Buon giorno a tutti ragazzi Vi scrivo cosa accade sulla seguente build successivamente all'installazione. Build: - MOBO: asrock b75m-gl R2.0 - CPU: Intel i7-2600k - GPU: HD3000 (con uscita DVI-Digitale dalla mobo) OS X: El Capitan 10.10.3 Bootloader: Clover v2.3k r3333 Il bios della b75m-gl R2.0 è stato moddato in modo da poter ottenere il corretto power management. Preparata la chiavetta di installazione con la guida di Gengik84, avvio l'installazione ed eseguo tutta l'installazione. Terminata la procedura avvio da chiavetta ed installo clover in Legacy sull'hdd. A questo punto, finchè vengono utilizzati i file creati automaticamente dalla procedura di installazione di clover, il computer parte anche se non vengono riconosciute ad esempio la scheda video integrata dando quindi una risoluzione errata del monitor e la mancanza delle trasparenze. Riavvio, ed estraggo il DSDT originale. A questo punto inserisco il DSDT modificato ed il config preparato appositamente. In questo momento iniziano i problemi... Inserendo il dsdt modificato ottengo un bel kernel panic. Eliminando il dsdt e iniziando a lavorare solo con il config modificato per lavorare senza dsdt ottengo sempre dei mancati avvii sia in verbose che in modalità normale. Es: foto1, foto2, foto3. Tentando di verificare, eliminato già in precedenza il dsdt modificato, tento rimettendo anche il config originale. Il risultato è quello iniziale, ovvero: il computer parte anche se non vengono riconosciute ad esempio la scheda video integrata dando quindi una risoluzione errata del monitor e la mancanza delle trasparenze. A questo punto, pensando di aver sbagliato qualcosa nella mod del bios, torno indietro e riflasho il bios. Ecco il nuovo dsdt cui tento di procedere. Nulla da fare, sempre stessa situazione. A mali estremi, estremi rimedi... Bypassiamo la HD3000. Inserisco una GT210, la imposto come primaria nel bios e modifico il config. Il dsdt modificato era già stato rimesso e... Se avvio in verobese, il computer parte e viene riconosciuto tutto correttamente, invece se avvio in modalità normale il computer non parte e si blocca alla mela senza nemmeno farmi vedere la barra di caricamento. Qualcuno ha qualche idea su questo bell'inghippo?
  5. First you need to install: Voodoo_HDA_2.8.5_MAV.pkg.zip Source: http://www.insanelymac.com/forum/topic/297207-voodoohda-285-for-mavericks-slice-anv-signed/ Second if your sound card not working (probably it's VIA VT1708S on Asrock P5B-DE) In my Asrock P5B-DE works perfectly (on Maverick 10.9.2). I connected 3.1 sound system and subwoofer was works, 7.1 will work. Install mentioned pkg7 And replace attached VoodooHDA.kext into "/System/Library/Extensions" If you have any sugestion please post it here (maybe it will be work with all outputs -> in HDA) This is my first (fast) mod special thanks for Andy Vandijck, chris1111 and others who worked for VoodooHDA VoodooHDA.kext.zip
  6. Hey everybody - The idea for this post is to try to clearly document the process of my new first built-from-scratch Hack Pro, so that others might benefit. I've been reading insanelymac, tonymacx86, myHack, ox86.net, etc, etc., but sticking at various points, and still need help. THE SPECS: CoolerMaster HAF 932 case AsRock Z68 Extreme7 Gen3 motherboard Intel I7-2600K CPU @ 3.4Ghz (plan to O/C to 4.6Ghz) CoolerMaster Hyper 212 CPU cooler G.SKILL Ripjaws Series 16GB (4 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600 (2133 O/C) Lightscribe DVD burner 24x Radeon HD 6870 2GB Eyefinity 6 graphics card (with 6 minidisplayport outputs) CoolerMaster SilentPro 700W power supply Dell u2410m monitors (3 so far, 6 possible) 24" IPS 16:10 1920x1200 resolution Additional info: Intel I7-2600K: Has Intel HD Graphics 3000; SSE up to 4.2 Asrock Z68 board: SATA: (4) SATA 3 at 3Gb/s and (6) SATA 3 at 6Gb/s: 2 are controlled by Intel Z68 chipset, 4 by Asmedia 1061 (of which 2 are shared with the eSata port). I've connected the SSD to one of the 6Gb/s by Z68. AUDIO: Realtek ALC892, and supports THX LAN: (2) Broadcom BCM57781 chipsets PORTS: Onboard DVI, HDMI, DisplayPort, Firewire/1394, (6) USB 2.0, (6) USB 3.0, eSATA GRAPHICS: 3-way SLI and 3-way Crossfire supported Radeon HD 6870 Graphics card by Powercolor: Has 6 mini-DisplayPort outputs, 2GB GDDR5, 900Mhz engine, 1050Mhz memory Using the InstallESD from the App store THE STEPS: 1. Assembled machine. Newegg's build videos (link: http://www.newegg.co...014&PID=3266097 ) extremely helpful. POST beep first time. Nice. 2. [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url]: First tried [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] by tonymacx86, which my brotherinlaw put on his Asus slate and got working first time. Not so easy on this build. Got to installer once, but it never completed. On [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] page, it suggested entering boot loader flags. After a few hours, figured out that all that is needed on the Chimera boot loader screen is to hit any key, and it will open the prompt. So tried -x -v -s "GraphicsEnabler=No" as suggested possibilities on the [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] page, and got to the point where it gives error message "Waiting on root disk". I dug around and have tried "rd=disk0s3" to try and indicate where to install Lion (the SSD with the EFI partition, the Windows 7 partition, and the 3rd partition waiting for Lion). Is that right? Or should I point it to the USB? Not sure what the rd= flag is asking... Anyways, one of the rd= combinations I tried (aargh, I didn't document which one) then says that the files are READ only, and that to write, I need to type in the commands "fsck -fy" and "sbin/mount -uw" . I tried that, but it just gets to same point and then screen goes black, still not reaching installer even after hours of letting it run. Stuck at this point with [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url]. 3. WINDOWS 7: Wondered if having a working build (with Windows) would help. Installed Windows7 and updated all drivers and Windows Updates. Everything working well on Windows side. Wow this is a fast machine - boots in about 5 seconds! Used DiskManagement to partition the SSD in preparation for OSX. Now have the EFI (System) Partiton, the Windows 7 Partition, and the unused partition waiting for Lion. 4. [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url], part2: Back to trying [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url]. No changes from last attempts - see step 2. Windows still runs fine, by the way. 5. MYHACK: Decided to try myHack. Also a nice application with nice GUI. Tried a verbose boot (-v) at boot loader screen, but after loading the kext files (learning that those are similar to drivers or dll files in Windows), it goes to black screen with a white bar half way across the top. Tried a verbose safe boot (-v -x) and this time it gets farther, but then gets to same error message: "Waiting for boot volume with UUID 1AF86C55-A6A1-3A81-BIFC-72842DD14EEA", then pauses, then "Waiting on <dict ID="0"><key>IOProviderClass</key><string ID+"1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-medida</string></dict>, then pauses, then "Still waiting for root device" which repeats endlessly until reset. Time to try the "rd=" command again, I guess. At boot loader screen, typed in "-v -x rd=disk0s3" and variations such as rd=disk0, rd=disk0s1, rd=disk0s2, etc, but never gets beyond the "Still waiting for root device" error. I should also mention that the fakesmc plugins and nullcpupowermanagement kext all seem to be indicating that they are installed successfully. 6. MALDON'S STICK METHOD. Will probably try Maldon's stick method here on insanelymac next.... But at this point, since both other methods have given same error about "Still waiting for root disk", I'm thinking that I need to get past that to get to the installer. So for now, will try showing you all the error screen (jpg attached). I'm pretty sure this is an easy fix, if I knew what I was doing. These links: http://apple2pc.blog...oot-device.html and http://books.google....%20s%3D&f=false have explanations that are fairly good, but if I need to point back to the USB drive to boot, I don't know how. The SSD is in the 0 position, according to BIOS. Please HELP if you can. Trying to make this a post that will be beneficial to others. Thanks in advance!
  7. Hello everyone, I'm posting a new thread on behalf of myself and a few other members here (konrad11901, blackswords and Dmitry R). We've been experiencing an unstable system after wake. My system is ab Asrock Z97M OC Formula with an i5-4670k, konrad11901 has an MSI B85-G43 Gaming with an i5-4460, blackswords has an MSI PC Mate Z97 with an i5-4690k and Dimitry R has an Asrock Z170M-ITX ac with an i3-6100. I recently got my Z97M OC Formula to replace a GA-Z87MX-D3H which suffered from corrupted memory after long sleep. I'm booting using Clover, with a patched DSDT, and an SSDT generated with PikerAlpha's ssdtPRGen.sh. I've attached the files of my configuration. Soon after wake, the log shows messages such as: 2016-03-29 11:23:21,000 kernel[0]: Unsynchronized TSC for cpu 1: 0x0000000193273184, delta 0x18e0a1aca 2016-03-29 11:23:21,000 kernel[0]: Unsynchronized TSC for cpu 2: 0x0000000193428ced, delta 0x18e0a1aed 2016-03-29 11:23:21,000 kernel[0]: Unsynchronized TSC for cpu 3: 0x00000001935de52f, delta 0x18e0a1aed followed by process crashes, usually culminating in a launchd crash, causing a kernel panic and a reboot: *** Panic Report ***panic(cpu 1 caller 0xffffff800cb9aaa4): launchd exited (signal 8, exit status 0 ) … Thread 3 crashed … We have noticed that the output of pmset -g log | grep -i failure points to various PCIe devices, most notably the graphics card. Here's my output at the moment: 2016-03-29 13:11:50 +0200 Failure Drivers Failure panic during wake due to PEG0(NVDA NVDA NVDA NVDA NVDA NVDA),IGPU(): 2016-03-29 22:45:40 +0200 Failure Drivers Failure panic during wake due to PEG0(NVDA NVDA NVDA NVDA NVDA NVDA),IGPU(): With VoodooTSCSync.kext, we've noticed launchd crashes less often, meaning waking from sleep works, apart from the other processes that do crash. My theory is that there's something wrong with the firmware of our boards, or an issue with the DSDT or with CPU power management. This underlying problem is causing a TSC sync issue, which causes problems with PCIe devices as well as processes. Does anyone know the cause? Are there more people with this issue? And can anyone explain the relationship between the TSC, the HPET and the RTC? Thanks in advance to anyone who can shed any light on this issue. Kind regards, Pieter Edit: I forgot to mention that konrad11901 discovered that when using hibernation (hibernatemode=25) in stead of sleep there are no crashes, but of course, this isn't an ideal solution. Z97M OC Formula.zip
  8. I was wondering for a long time if it is possible to have the power LED pulsing on a hackintosh in the same as a real Mac but never really found the time for an in-depth research. Reading through the datasheet of my board's SuperIO, a Nuvoton NCT6776D, I found the following table which confirms that the hardware supports this feature too. As sleep/wake is controlled by the DSDT, I had the idea that it might be possible to get the pulsing power LED just with a small DSDT patch and, to my great surprise, its much simpler than expected. But see for yourself. In the DSDT of my board, an Asrock B85 Killer, I found method SLED controlling the switch between on in S0 and blinking mode in S3 (sleep): Method (SLED, 1, NotSerialized) { ENFG (0x0B) If (Arg0) { If (LEqual (OPT7, 0x87)) { Store (0x45, OPT7) } } Else { If (LNotEqual (OPT7, Zero)) { Store (0x87, OPT7) } } EXFG () } Replacing the line "Store (0x45, OPT7)" with "Store (0x4A, OPT7)" gave me a slowly pulsing power LED while the machine sleeps. That's really trivial. Ok, it's not as pretty as on a real Mac, but very close to the original. This patch should work for most of Asrock's series 8 and 9 ATX/µATX boards as far as I can see. The mini-ITX boards may be different, at least my Asrock B85M-ITX is, but it should be possible to get this feature working with them too. Many of Asrock's 100 series board also come with the same SuperIO chip but the DSDT looks different. Here is an example from an Asrock Z170M-Pro4S which woks in the same way. The following code snippet was found in method SIOS, which is called in order to prepare the SuperIO for sleep mode: If (LEqual (Arg0, 0x03)) { Store (0x0A, LDN) Or (OPT0, 0x20, OPT0) Or (RGE4, 0x10, RGE4) Store (0x0B, LDN) If (LEqual (OPT7, 0x87)) { Store (0x45, OPT7) } } Changing 0x45 to 0x4A should give you the pulsing power LED on this board too. As far as I know, Nuvoton SuperIOs can be also found on many ASUS and MSI boards. The NCT5577D supports this feature too. Other chips might support it as well but you need to have a datasheet to verify it and learn how to control the LED. Mieze
  9. Yesterday I got my new mainboard, an Asrock Fatal1ty B85 Killer. The first thing I did was upgrading the BIOS to the latest version available (V1.30). Next I wanted to patch it with PMpatch in order to unlock the MSRs but I was very surprised that PMpatch didn't found a match pattern in the power management module. This made me curious and I tried to boot Mavericks with the vanilla BIOS and it succeeded. No KP, no early reboot. Obviously Asrock has decided to change their policy with regard to the CPU's MSRs in some of their latest BIOS releases for at least a few of their boards because I don't think that the Fatal1ty B85 Killer is the only board with unlocked MSRs. I wouldn't be surprised in case other members of their Fatal1ty series of mainboards are affected of this change of mind too. It would be great if anybody with access to one of these boards could confirm this. Update: I downloaded the BIOS files of the following boards from Asrock's website and tried to patch them with PMPatch but it didn't find a matching pattern in any of these BIOS files. It looks like all these boards have unlocked MSRs too. Well, it might also be the case that PMPatch lacks some matching patterns but you would need a board in order to verify this. Asrock Fatal1ty H97 Killer (Version 1.10) Asrock Fatal1ty Z97 Killer (Version 1.30) Asrock Fatal1ty Z87 Killer (Version 1.40) Mieze