Jump to content


  • Content Count

  • Joined

  • Last visited

About m28ew

  • Rank
    InsanelyMac Protégé
  1. I would like to say CONGRATULATION & THANK YOU for all member of the "Dev Team" finally all version of OSX (v10.6 - v10.10) can run flawlessly on my AMD P-II x4 965 But there’s an old issue still occurs with all the latest kernel of Bronya's RC5 & Tora Chi Yo's Rev-8N When I open the MAXIMA http://maxima.sourceforge.net/ I can confirm that the app can work with the latest kernel (both Bronya’s & Tora’s) But I also notice that the console still repeatedly reports some kernel related errors which is “invalid user opcode (32-bit)” And here's the error list reported by the dmesg
  2. read this: http://www.insanelymac.com/forum/topic/281450-mavericks-kernel-testing-on-amd-formerly-mountain-lion-kernel-testing-on-amd/page-218?do=findComment&comment=1967675
  3. yep! she's right i run some flash testings (comparing latest & older version of flash player -> v13 vs v12 ) by opening: http://www.speedtest.net/ And here're the results: with the latest version of FP (v13.0.0.214) with the older one (v12.0.0.3)
  4. and the console also reports these errors:
  5. Sorry, I'm not trying to hijack your post but, have you also tried to capture an open window instead of a selected area ? Here are the shorcut keys: capturing a selected area => press Command (⌘ )- Shift - 4 capturing a window => press Command (⌘) - Shift - 4, AND press the Space bar capturing a selected area = no issue (normal screenshot) capturing a window = purple issue
  6. Thanks... the new kernel works on my old p-ii-x4 amd but the known issue still exists --> capturing a window will result in purple
  7. Thanks to Rhys Oxenham I found a temporary solution for the "kernel task" issue 1. go to this directory cd " /System/Library/Extensions/IOPlatformPluginFamily.kext/Contents/PlugIns/ACPI_SMC_PlatformPlugin.kext/Contents/Resources" 2. find your Model Identifier by opening System Info or running this command system_profiler -detailLevel mini | grep "Model Identifier:" 3. find if the .plist file of your Model Identifier exists in the directory (step #1) e.g. my model is iMac11,2 ---> then I have to find the iMac11_2.plist <--- note: change iMac11,2 to iMac11_2 (with underscore "_") ls iMac11_2.plist or ls "/System/Library/Extensions/IOPlatformPluginFamily.kext/Contents/PlugIns/ACPI_SMC_PlatformPlugin.kext/Contents/Resources/iMac11_2.plist" 4. if it exists, backup the .plist to your backup directory & delete the original one sudo mv iMac11_2.plist ~/desktop or sudo mv "/System/Library/Extensions/IOPlatformPluginFamily.kext/Contents/PlugIns/ACPI_SMC_PlatformPlugin.kext/Contents/Resources/iMac11_2.plist" ~/desktop 5. restart your pc NOTES: it would appear that the system may also use another plist in the directory, therefore removing all of the plists may also work too. It’s likely that this kext will get updated in the future by Apple in their update packs and as a result will replace the file you deleted/moved therefore you may have to repeat this process in the future TRY IT AT YOUR OWN RISK !!!
  8. yup! same issue for me too the XBMC won't start (it just closes instantly) under osx Mavericks with both AnV & Bronya 's kernels (the latest & earlier ones) but it can run properly under osx ML 10.8.5 with the latest Bronya's kernel EDIT ISSUE SOLVED !!! the latest BETA build of XBMC works well with osx Mavericks + Bronya's latest kernel
  9. what bootloader are you using ? maybe changing / updating it would solve your problem http://www.insanelymac.com/forum/topic/291642-clock-time-too-fast-1084/
  10. LOL sorry I missed that part btw, have you tried booting the osx either with busratio= or using VoodooTSCSyncAMD.kext ?
  11. your clock looks normal to me FYI, 19:46 is the ARMY TIME for 07:46 PM you only have to untick the "use 24 hour clock" option to restore your clock to AM/PM
  12. I think you may be right the culprit may be the cpu-x itself since it's too old & it hasn't been updated since 2008 I've just found another false reading of intel i5's L2 by cpu-x (mavericks + vanilla kernel) cpuz = 4 x 256KB cpux = 2 x 256KB
  13. nope your kernel still detects my L2 as 2 x 512KB instead of 4 x 512KB
  14. mostly I removed some kexts which (I thought) might not not related to my hardware and I read this thread as my reference http://www.projectosx.com/forum/index.php?showtopic=102 don't get too excited since that might not be the real solution try at your own risk