Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

About xhala_debru

  • Rank
    InsanelyMac Geek

Profile Information

  • Gender
  • Location
  1. Clover General discussion

    Hi, Actually, it's Mavericks_SSD I'd like Clover to boot on. And I had already tried that with no luck <key>DefaultVolume</key> <string>Mavericks_SSD</string> Mavericks_250_Sata being the drive Clover always wants to boot to no matter what when reading nvram (<key>IgnoreNVRAMBoot</key> set to false) Strange thing is that when I print the nvram of my system (nvram -p), the variables of the system do point (Clover.MountEFI and efi-boot-device) towards Mavericks_SSD Thank you anyway, with the option <key>IgnoreNVRAMBoot</key> <true/> in config.plist, I'm able to boot on it System seems stable, I've been able to update all my Apps, so far so good
  2. Clover General discussion

    Yeah, rushing to help, that's nice Here's the bdmesg, quite big actually. If' there's a way to reset it, please let me know, it might be more readable Ok, so it DOES have something to do with NVRAM, because setting the IgnoreNVRAMBoot key , the defaultvolume key is read and working bdmesg.txt
  3. Clover General discussion

    Sure, and thanks for looking Edit/ Don't find boot.log. Guess I have to activate it diskutil info.rtf config.txt nvram.rtf
  4. Clover General discussion

    Making an USB clover disk sounds smart. Thanks for the idea. And I do think it has something to do with not finding what it is looking for. When I look in nvram.plist (maybe not the exact name but i'm not in front of my pc) I see uuid drive I don't know. And I've tried the pref pane but with no luck. And just to be sure I'm well understood, I do reach clover, but it's only default drive in cover that's wrong.
  5. Clover General discussion

    Hum I thought clover was used in UEFI mode... still, it's true that I wondered why there was the Legacy option (thought it was for compatibility). And I did use HVT to set cpu model by example and I think it built my smbios (imac 14,2) And I do have Chimera and Clover on the same drive... That's already a lot of nasty things... Edit: And in Bios, I do boot on OSX Clover UEFI (or some name like that)
  6. Clover General discussion

    Hi I have little problem with Clover but it unfortunately preventing me from using it. First a small introduction and why I want to use Clover. I'm not really what could be called a noob with hackintoshes. My first hackintosh was in Tiger 10.4.something... (I found an old 10.4.8 dvd at home...) Then 10.5, 10.6, 10.7 and lately, a jump to 10.9.3 on a new configuration which is as such: - Gigabyte Z87X UD3H - Intel Core I7 4770 - Asus GT 640 - 16 Gb Ram Still I'm not a guru by far, I'm none of a coder but I'm fairly good at googling and understanding most of what I read. The 10.9.3 was done at first using chimera 3.0.1 (as in t0ny...), after a lot of random freezes, I found out it was stable if I removed the Asus GT640 and worked on the internal IGFX 4600... Could have gone that way, but are we geeks or not? So I decided to give a try at Clover installation was quite "difficult" mixing with "Hackintosh Vietnam Tool", clover installer package (v2kr2721) and clover configurator. The problem I have is that I have several hard drive (a main SSD 250Gb, a backup drive 250Gb and another 160Gb raptor). All of them have a working installation of Mavericks, time taught me that it's better to have backup disks than none... So teh BIG problem is that, no matter what I set in config.plist or clover preference pane, the default boot volume is always the backup 250Gb disk. I've tried switching sata cables between both, it doesn't change anything. I've tried putting partition names or UUID, it doesn't work. Still I'm sure that the config.plist is read as I can change the theme. <key>Boot</key> <dict> <key>Arguments</key> <string>-v</string> <key>Legacy</key> <string>LegacyBiosDefault</string> <key>DefaultVolume</key> <string>Mavericks_SSD</string> <key>Log</key> <false/> <key>NeverHibernate</key> <true/> <key>Timeout</key> <integer>5</integer> <key>XMPDetection</key> <string>Yes</string> <key>Secure</key> <false/> </dict> My disks are all UEFI GPT Any clue of how I can set boot disk? Thanks!
  7. 10.7.2 update issues

    For me it did solve the KP. Thanks, you made my day
  8. SAS Controllers w/ EFI for Mac OS X / OSx86 Solutions

    Hi, I'm still pleased with my Areca 1222. My experience: - Drivers are buit-in in Leopard and SL, so drives are accessible from a vanilla installation DVD. - Areca sometimes delivers new drivers, but they are often following the release of the update. So once ( I think after 10.5.6), my system was not bootable anymore as a kext had been updated by apple, fortunately, I had a backup system and put the kext from 10.5.5 back and it was Ok. Areca delivered the new driver a few weeks later - You have to be carefull as now there are 32 and 64bits drivers, so if you upgrade you driver, you'll have to take the driver matching your kernel. Otherwise you'll have the "Still waiting for root device" problem. As a rule of a thumb, keep a clone of your installed system on a cheap sata/esata or usb drive just in case. I think all those problems are not hackintosh related. But still, I'm pleased with it and don't regret it. One final note: If you ever get one, don't flash it with an Efi firmware or it will not be bootable anymore. I tried it and had to boot on the Areca cd (which is a live linux distrib with drivers) to flash it back with pc firmware.
  9. J'aime bien Personellement, j'ai un gygabyte aurora 3d noir depuis bientôt 3 ans. Pratique, assez silencieux et grand (plein de HDD) http://www.pcinpact.com/articles/gigabyte-...ime--/136-1.htm
  10. As-tu trouvé/essayé de trouver un bootcd qui correspond ta carte mère? Car en général, le "still waiting for root device", c'est ce qui arrive quand Osx ne trouve pas le pilote (kext) pour les disques durs. Donc si c'est pour une installation, si le kext n'existe pas sur le dvd d'apple (ou que tu n'utilises pas une distrib), il faut le charger avant (avec le bootcd). Sur les CM à base de chipset intel, le mode d'accès des HDD soit être mis en AHCI dans le bios. Mais je ne connais pas le bios des chipsets nforce. As-tu mis les bons paramètres dans le bios (même que ceux qui ont réussi à faire fonctionner ta carte?) Dans ton lien, le gars utilisait quand même une version patchée de Leopard (Kaliway)
  11. Je ne veux pas être rabat joie, mais tu as une carte mère avec un chipset amd et ce n'est vraiment pas recommandé. Tu aurais plus de chance de choisir de trouver un bon tuto et de prendre la même CM. Car un hackintosh, c'est quand même toujours un peu de la bidouille et à moins de savoir se débrouiller seul, autant "rentrer dans le rang" et avoir une communauté derrière soi pour les différents fix et problèmes à venir (update, etc...)
  12. Random Beach Balls in UI

    I have the same issue. Beachball in an app, app reported as unresponsive in console. But I thought I had a bad hdd, since from time to time I can hear some drive noises, while not doing any hdd access. I can hear it clearly as I have 15krpm sas drives that are rather noisy. I'll try disconnecting the drives I don't need to see if I still have this issue.
  13. Getting Snow Leopard to recognize your CPU

    Kext installed in /E/E everything is fine. Q9450 recognized as Xeon as said before. Now I'll try to make my cpu speed right. Thanks
  14. PC EFI V10.3 Released by Netkas

    Pc efi 10.3 works fine for me. Before I was using GFX strings, but no need for them anymore. The only reason I tried graphics enabler is because I had a few seconds of display problems when display woke from sleep. PS: boot file of chameleon RC3 did not work (Ethernet recognized, but not video). Just swapped it with 10.3 and there it was "OSX86 in all it's glory" First time I say this (still I often thought about it) but well, good job Netkas Now I'd like to know why RC3 didn't work, is it beacuse of this PCI root thing?