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.

Florian U.

  • Content count

  • Joined

  • Last visited

About Florian U.

  • Rank
    InsanelyMac Protégé
  1. So, here's the file you requested. This is the Extra folder that I placed into my root directory of the El Capitan system. However, the FileNVRAM.kext from /Extra/Extensions is also placed in /S/L/E/ as well., yes I used the usual sudo nvram commands, but keep in mind that one of the two values requires you to include % symbols in ID. Extra-Folder as zip-file: http://uploaded.net/file/uc9c18wc You should also make sure that you check if the kext is actually capable of loading! (plus rebuild cache with kextutility) I boot the system without any FileNVRAM-files by using Chameleons -v -f commands, then run a full kext-utility services, reboot regularly, then place the files in its position (kext in two locations and dylib only in /Extra/modules) and run kext-utility again. then reboot normally with the cached cache file (chameleon using just -v or nothing). keep in mind I am not using a chameleon.boot.plist - only an smbios.plist)
  2. I'm using the ROM and MLB values from a real mac, that i dumped with imessagedebug - and yes - this mac is sitting next to my main workstation. so there is no way around to get legit values at this moment, as the auto generated don't work usually. but maybe you get lucky. cheers.
  3. Same here. Cousin has good results with Clover, but I'm very reluctant to using it (and actually getting it to work as it requires lots of learning^^)
  4. Are you using Chameleon? Or what boot loader are you using? Is your NVRAM functional? Does your iMessage work? Curious - as I still think AMD does make excellent products, yet they haven't gotten the attention they should in the past years. Maybe the new processor line-up is going to change that a bit. Thanks to PS4/XBox One
  5. I'm the type that doesn't like to mess with the original files from Apple, thus I adjusted the FileNVRAM.kext version dependencies, which fixed the issue. It could possibly eliminate the need to change the kext, but Yosemite runs on IOStorageFamily 2.0 (El Capitan 2.1) so wouldn't think of a big difference in terms of the other bugs that are well known among the users of Chameleon/FileNVRAM.
  6. Dear Mac users, I'd like to talk about iMessage, El Capitan and Yosemite. I've been using Mac OS X on a Maximus V Gene motherboard with an i7-3770K processor for quite some time now. With the introduction of Yosemite I needed to figure out a way to make iMessage work as it included changes around the same time with validation of MLB and ROM values that were reported by the system and the NVRAM. Here's my basic setup: Chameleon boot loader (previously regular flavor, now ENOCH), drop the Chameleon.plist, insert SMBIOS.plist, FakeSMC, IntelE1000-Ethernet.kext and my systems is working. To enable iMessage I had to install the FileNVRAM.kext (1.1.4 package) and FileNVRAM.dylib (1.1.4 package) file onto the USB stick containing the chameleon boot loader. With this setup, I was able to boot Yosemite fine and get a working NVRAM. However, keep in mind that you have to create the /Extra folder on the hard drive of your OS X install and make it writable by anyone. Then the FileNVRAM.kext is able to create the nvram.1d34-12d4d1234-1d341234.plist ( ) which contains the data you have written. Whenever I needed to boot the system with -v -f or when doing software updates, I had to use a second Chameleon stick that did not include the FileNVRAM.kext and dylib files. (If booting with -v -f and FileNVRAM installed, the system would crash on caching the kexts) I would then boot the system, run kext utility or similar permissions-checking and kext-caching applications and reboot with the FileNVRAM-USB stick. This was my full working arrangement. Tedious, but worked excellent. Never had a problem with iMessage, FaceTime, iPhone Calls, AppStore, iTunes or iCloud. So far so good, but it was time to move to El Capitan. In El Capitan I encountered the problem that kexts cannot be passed through the Chameleon boot loader but have to be installed directly into /S/L/E and have to be cached by a running system (usually just boot the same SSD from a real Mac). This forced me into a predicament with the FileNVRAM.kext which had to be loaded through Chameleon as it wouldn't otherwise boot. So by trial and error I examined a problem with the FileNVRAM.kext on 10.11.3 which resulted in it not being loaded, no matter where you put it. Reason why? The Info.plist of the FileNVRAM.kext has the following code written in it: <key>OSBundleLibraries</key> <dict> <key>com.apple.iokit.IOStorageFamily</key> <string>1.0b1</string> <key>com.apple.kpi.bsd</key> <string>8.0b1</string> <key>com.apple.kpi.iokit</key> <string>7.0</string> <key>com.apple.kpi.libkern</key> <string>8.0d0</string> <key>com.apple.kpi.mach</key> <string>8.0d0</string> <key>com.apple.kpi.unsupported</key> <string>8.0b1</string> </dict> Not sure if you spotted the error yourself, but the IOStorageFamily version is too low for El Capitan. This OS X ships with 2.1 instead and the kext simply refuses to load. If you change this value in the Info.plist file, the kext is loadable. This is more of a dirty patch than a correct solution. So what happens next: I got my El Capitan working again with the same approach as above, but no FileNVRAM module or kext anywhere, neither Chameleon, nor OS X. When the system is booted up I would install the FileNVRAM.kext into /S/L/E, onto the /E/E on the Chameleon stick and in the /E/E folder on the hard drive. Same with the module, /E/E on both hard drive and chameleon stick. Now I would have to run kext utility again to precache the FileNVRAM.kext into the system and reboot. Sometimes it wouldn't boot up, sometimes it would "break" the system (fixable by dropping FileNVRAM from all instances and touching /S/L/E and running kextcache -u / from single-user mode or external system) - but most of the times it just works. NVRAM is capable of saving and creating the /Extra/nvram.xxxxxx.plist file and returning the required MLB/ROM values after being saved - even after reboot. Thus I have managed to get FileNVRAM.kext working by this trick in El Capitan. Despite this solution working for me and probably others, my hope is that there is someone capable of updating the FileNVRAM.kext file for El Capitan and its latest Xcode? The kext itself is still working, but the dependencies are off and thus causing the issues. Thank you and have fun! Florian P.S. Edit: Here's the files I used. (dylib and kext) http://uploaded.net/file/uc9c18wc(zip-file of the Extra folder)
  7. It's still the same rapidshare file, however, with the appropriate "share" link... https://www.rapidsha...patchedcode.bin worked for me on iMac 2011 27" and windows 7 64bit
  8. i dont think it is broken, you just need to use terminal and cd into that directory and launch the application from there -> else it'll report files missing
  9. Mac Pro W3520 - HD5770 - 8.06ms - 124.14fps iMac i7 3.4 - HD6970M - 3.45ms - 289.47fps Cheers Florian
  10. Confirmed, is working. Thank you so much. Got my GT440 and GTX285 now working in my MacPro4,1 (W3520) on Lion with ATY_init, openCL patch and CMF's patch. Still need to check if Final Cut Pro X will now render faster than with single GTX285.
  11. Hey there I have a little issue here. The error is the exact same one, although I am using a GT440 card, which is a little different. Bigger issue: I also have a GTX285 installed. (mac pro) When changing that value to a fixed value, both cards get changed, and the gtx285 is a bit older and supports only sm1.3 i think. not sure about gt440, seems like it only supports sm1.0 ?! any chance I can use the patch to get them both to be recognized with sm1.3 or sm1.0 that they will both work? I tried final cut pro x with a few rendering tests, seems like gt440 + gtx285 is slower than just the gtx285 o.O any advice is appreciated. THANK YOU florian
  12. Hello =) I have googled and searched for hours, but I only found, that the GT440 graphics card is supposed to be supported by the GF100 driver of Lion. 0x0dc010de&0xffc0ffff <-- this ID is also including the ID for my GT440, which is this one: 0x0DE010DE However, i can't seem to get it activated/loaded by OS X. The only entries I get in system profiler looks like that: Display: Type: GPU Bus: PCIe Slot: Slot-2 PCIe-Lane-Breite: x16 Manufacturer: NVIDIA (0x10de) Device-ID: 0x0de0 Version-ID: 0x00a1 Displays: Display Connector: Not recognized by any tool either. GPU-Z, LuxMark, etc.. I got a EVGA GTX285 in the lowest slot, and the first open one (should be slot 2) I installed the GT440 in it. It works via BootCamp with both CUDA and OpenGL/DirectX... So it can't be really an issue of wrong slots, too much power, etc. You guys keep saying that LION natively supports Fermi (GF1xx) cards. How do you manage to get them loaded? By Chameleons GraphicsEnabler? Any other chance for me to get it in there? I appreciate your advice. Thank you
  13. Introduce yourself.

    I'm a Mac fan since 2006 and been working with real macs for a long while. At the moment, I have a Mac Pro 2009 Quad-Core, 12GB Ram, HD4890 graphics, OCZ Vertex 2 120GB. For hackintoshes, I've had a P4 with 10.5.x a while ago and a Nokia Booklet 3G at the moment. I'm from Germany, and will be working as a pilot within the next year.
  14. Nokia Booklet 3G - OSx86

    10.6.0 retail installed, updated to 10.6.6, 10.6.5 atom kernel, [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] 3.0 with userDSDT + dsdt.aml. won't go any further than that. Do you see anything that's wrong? Thanks.