Jump to content


  • Content count

  • Joined

  • Last visited

About Crazor

  • Rank
    InsanelyMac Protégé
  1. So I think that the problem is caused by the system not recognizing my SSD as an actual Solid State Drive. I researched a bit about how the OS can detect an SSD, and found out about the ATA8-ACS standard: A drive that reports 1rpm as the rotational speed is to be considered a Solid State Drive (this is the way Windows >= 7 disables online defrag, btw, and is required behaviour for SSDs to conform to the Windows Logo program). So I installed smartmontools, and of course smartctl -i does report my drive as an SSD, and from looking at the raw data the drive returns when queried, I found out that it does report as 1rpm. Also, I played around again with every major OS X release starting from 10.8.3 and up until 10.11 and had a look at what the system thinks of my SSD when I install OS X on it, without creating a FUD. Every version does report my SSD as "Solid State: no", and the various TRIM enabling hacks (patching the kext, running trimforce on recent versions) don't work for this drive (although they had before). This is soooo weird!
  2. Since my WD RED died on me a few days ago, I had to rebuild my Fusion Drive setup. At first, I was using a LiteOn LITEONIT LCT-128M3S 128GB SSD and a Seagate Barracuda 1.5TB HDD since 10.8.3 came around, and soon upgraded to a WD RED 3TB. I verified that the Fusion Drive was more than a JBOD array by using iostat and dd to read and write stuff. I saw the "4GB write cache" behaviour as well as the "moving blocks to SSD after reading them often" behaviour, so I concluded that my Fusion Drive was working fine. I upgraded my system from 10.8.3 up to 10.11 just fine. Skip to now, the WD RED died and was replaced by another 3TB WD RED, same model in fact (WD30EFRX-68EUZN0). Only this time I noticed that diskutil in Yosemite and El Capitan showed "Fusion Drive: no" when querying the drive for information (El Cap's Disk Utility GUI said it was Type: Fusion Drive, though). This made me wonder what happenend. I've since tried to recreate the Fusion Drive from 10.8.3, 10.9, 10.10 and 10.11, to no avail. Funny thing is: Using the exact same USB thumbdrive with 10.10, I set up a buddy's 2011 iMac which I upgraded with a SSD a few weeks ago. His Fusion Drive is said by diskutil to be "Fusion Drive: yes". I haven't verified it working with iostat and dd yet, but I plan on doing so soon. My Mom's iMac also got the Fusion Drive treatment a few months ago, running Yosemite. Everything appears to be fine with it, too. I noticed that 10.11 Disk Utility (GUI version) seems to think that my SSD is a HDD. When looking at the disk's info, it says "Solid State: no", even when I delete the whole CoreStorage shebang. Also I had wondered why there is no more TRIM info in System Profiler since I upgraded to Yosemite, but I figured that that information has been omitted after all the TRIM discussion. So maybe this is the cause for my Fusion Drive problems? How can I convice OS X that my SSD is in fact a Solid State Drive? Maybe OS X is looking for the string "SSD" in the device's name? Can I change the name with Clover? I remember patching the SATA driver to look for "SSD" instead of "APPLE SSD" to enable TRIM in previous versions of OS X, maybe this problem is related?
  3. Fusion Drive or not?

    I recently had to recreate my Fusion Drive, which I was using since 10.8.3 or .4 and which ran perfectly fine (used iostat to verify). Since the HDD recently died, I had to recreate the drive. However, diskutil info and diskutil cs info always claim that what I created was not a Fusion Drive. I tried El Capitan and Yosemite to create the Fusion Drive to no avail. I'm downloading Mavericks right now. I tried names like "Fusion Drive" (which worked before), "Fusion", "FUSION" and "FUSE", but that did not change anything. Funny thing is: A few weeks ago, I upgraded a friend's iMac and replaced the Superdrive with an SSD. I then used a thumb drive with the Yosemite installer to create the Fusion Drive (naming it "Fusion Drive" as I always do) and it worked absolutely fine! The iMac is on a model that never sold with a Fusion Drive (Late 2011 AFAIK). Does anyone know what exactly causes Disk Utility (the GUI version) to claim that the Fusion Drive needs repair? From what I've heard, on iMacs sold with a Fusion Drive, there must be some magic string in the NVRAM that causes Disk Utility to always recreate the Fusion Drive if it ever gets broken. Is there any more info on that?
  4. I've got this weird problem with my system that worked fine for months. All of a sudden, it started panicking a few seconds after waking the system from sleep. The most recent addition to the system kext-wise are the drivers for my M-Audio Fast Track USB audio interface. But the panic doesn't hint to the Fast Track at all (in fact, it doesn't hint to anything). Also, removing the drivers didn't help, and the panics happen even when it's not connected. Before that, I updated to 10.9.2 when it was released, but I'm not sure if the problems started back then or some time later. I'm booting with debug=0x144 and I get the panic screen as in this gallery: http://imgur.com/aE53D2Q,KUv0psr#0 Also note the second picture with the console on my second screen: http://imgur.com/aE53D2Q,KUv0psr#1 I cleared the log, put the machine to sleep, woke it back up and snapped the picture while the other screen showed the panic. System specs: Gigabyte GA-P35-DS4, Intel Core 2 Quad Q9300, 8GB RAM, Geforece GT 640, booting with Chameleon. Besides FakeSMC.kext, the system is running pretty vanilla. I'm really out of ideas on how to troubleshoot this problem. Also, I can't restore back to 10.9.1 easily, since I recently had to reformat my Time Machine drive =( Any ideas on what to do now?
  5. OS X 10.9 DP's builds

    I had this problem several times yesterday, but while updating from DP1 to DP4 with the combo updater. Today, I went from DP1 to DP2 to DP3 to DP4 via software update, and everything is working fine, no problems at all. I usually update my hackintosh with software update, but since it seems to be "hackintosh wisdom" to use combo updaters, I thought I would give it a shot, since I already downloaded the combo updater. Turns out combo updaters are not that good after all =) Instead of saving two hours by not doing the install and three updates one after another, I wasted more than three hours yesterday reinstalling and trying again with different settings (NullCPUPM etc.) =)
  6. ESI Juli@ / Envy 24 with OSX86 - Any progress?

    Any news on the Envy24 front? I mirrored the sources to GitHub, but haven't had a chance to look at them yet. I'm using the Delta 1010LT on 10.6.4 as my recording workstation and I'm running into issues which I haven't been able to pinpoint. Sometimes the system locks up, sometimes it just won't boot. Since I'm running with 2GB RAM only, i guess the himemory_mode flag doesn't apply here?
  7. Hallo, ich habe seit Lion ein seltsames Problem an meinem Hackintosh: Nachdem der Rechner im Ruhezustand war, und auch wenn ich ihn neustarte, habe ich oft kein Bild. Schalte ich den Monitor ab und wieder an, dann funktioniert aber alles wieder. Erst habe ich das auf den Monitor geschoben, aber das Problem tritt bei Windows und Linux nicht auf. Ich habe eine GeForce 8400GS und einen Samsung SyncMaster 2343BW per DVI dranhängen. Ich habe die Grafikinfos in die DSDT eingepflegt, sodass ich also keinen Injector und auch nicht den Graphics Enabler von Chameleon verwende. Leider bin ich etwas ratlos, an welcher Stelle ich anfangen soll, nach dem Problem zu suchen. Ich hoffe, ihr könnt mir helfen Edit: Schließe ich den Monitor per VGA an, tritt das Problem auch nicht auf.
  8. Recently, I discovered the ifconfig method to fix Bonjour. Basically, it consists of a patched ifconfig which allows to enter promiscuous mode and a way to execute the command at boot time. The solutions I found either involved scripts or apps which need to be placed in your user's login items. Aside from being rather ugly solutions, these have a problem: Finder is started before the card is switched to promiscuous mode, and so has problems discovering nearby computers for some time. Attached is a bundle containing Daniel Becker's patched ifconfig (from http://www.stanford.edu/~dub/macstuff/index.html) and a launchd plist file which runs the command at boot time. To fix Bonjour, do the following: 0) If necessary, edit de.crazor.BonjourFix.plist and replace en0 with your device name. 1) place ifconfig in /usr/local/sbin: $ sudo mkdir -p /usr/local/sbin $ sudo cp ifconfig /usr/local/sbin 2) place de.crazor.BonjourFix.plist in /Library/LaunchDaemons: $ sudo cp de.crazor.BonjourFix.plist /Library/LaunchDaemons 3) reboot BonjourFix.zip
  9. All things AHCI on ICH9R

    Could someone point me at the path of the default "internal" hard disk icon?
  10. Moin moin, habe mir kürzlich einen Pentium D 950 zugelegt. Das Board ist ein Asus P5N32-SLI Deluxe. Mit dem Pentium 4 630 vorher lief alles wunderbar stabil, mit dem Pentium D stirbt der Leopard leider nach ganz unterschiedlichen Zeitintervallen weg, manchmal mit Kernel panics, meistens aber friert das System einfach ein. Baue ich dann den P4 wieder ein, ist alles beim alten. Hardwareprobleme kann ich ausschließen, Vista und Linux tuns auch mit dem Pentium D 100% zuverlässig. Kühlung usw. ist auch soweit in Ordnung. Im System laufen ferner: 2GB Corsair RAM, GeForce 7600GS (oder wahlweise GeForce 6500GS zwecks Dualhead, warum das mit der 7600 nicht geht, ist aber eine andere Sache), diverse SATA-Festplatten. Es handelt sich um einen nForce 4 Intel Edition Chipsatz. Ich verwende Leo4All. Gibts irgendwelche Kext's oder so, die ich mal testhalber wegbewegen sollte oder die ersetzt werden müssen? Braucht man einen bestimmten Kernel für Dualcore? Bitte postet fleißig eure Ideen, werde am Sonntag dann schauen und ausprobieren =) Edit: Es war DOCH ein Hitzeproblem. Hatte den (turmförmigen) CPU-Kühler 90° verdreht eingebaut gegenüber sonst. Ist mir vorher irgendwie nicht aufgefallen =) Jedenfalls hat der CPU-Lüfter die Chipsatzkühlrippen prächtig angewärmt, die waren regelrecht am Kochen...
  11. Uphuck v1.4i 10.4.9 ist nicht komplett Deutsch

    Keine Druckertreiber... Das macht schon viel aus...
  12. Leo beta soll laufen........

    not quite die skripte sind alle okay, funzte hier top ganz oben im skript wird das eingehängte image der leopard dvd in osx86 umbenannt mittels hdiutil dazu muss aber die dvd den originalnamen haben. wenn das umbenennen nicht klappt, kann der rest auch nciht gehen dass /Volumes im image leer ist ist okay. Da schreibt der patcher auch nciht hin, sondern in /Volumes deiner Festplatte hängt das leo image drin.
  13. Leo beta soll laufen........

    whoami sollte root sagen. aber das prompt sieht nach root aus
  14. Leo beta soll laufen........

    Is a directory ist der hinweis dass man verzeichnisse nicht starten kann =) versuch mal terminal aufzumachen, cd leerzeichen einzugeben und dann deinen ordner aufs terminal zu ziehen. dann enter und ./patch-it.sh
  15. Leo beta soll laufen........

    Das meinte ich. sehe grad: du solltest das skript nicht mit absolutem pfad starten. zuerst mit cd in das verzeichnis wechseln und dann ./patch-it.sh aufrufen denn das skript nutzt oben pwd um das aktuelle verzeichnis festzuhalten, in dem es noch zusätzliche dateien findet. alternativ einfach die andere variable auf das verzeichnis des patches setzen (statt auf `pwd`)