spakk Posted September 19, 2015 Share Posted September 19, 2015 Okay, I had not noticed. perhaps it's because I'm using an external USB interface with their own drivers. Thanks, for the tip Gils, so then use with AppleHDADisabler. Link to comment Share on other sites More sharing options...
polyzargone Posted September 19, 2015 Share Posted September 19, 2015 My 2 cts . AppleHDA > No audio AppleHDA + VoodooHDA > KP VoodooHDA w/o AppleHDA > iTunes issues AppleHDA + AppleHDADisabler + VoodooHDA > All fine ! Lastly : AppleHDA + AppleHDADisabler + VoodooHDA > No issue whenever you update since it's very likely that AppleHDA will be reinstalled (not a problem anymore assuming 10.10.5 is the last update for Yosemite but still true with newer versions of OS X). 1 Link to comment Share on other sites More sharing options...
spakk Posted September 19, 2015 Share Posted September 19, 2015 My 2 cts . AppleHDA > No audio AppleHDA + VoodooHDA > KP VoodooHDA w/o AppleHDA > iTunes issues AppleHDA + AppleHDADisabler + VoodooHDA > All fine ! Lastly : AppleHDA + AppleHDADisabler + VoodooHDA > No issue whenever you update since it's very likely that AppleHDA will be reinstalled (not a problem anymore assuming 10.10.5 is the last update for Yosemite but still true with newer versions of OS X). Gils and I have tested successfully for a while ago, another variant, but one must look it as an experiment. A hybrid of AppleHDA and VoodooHDA ... works without Kernel Panic. Link to comment Share on other sites More sharing options...
polyzargone Posted September 19, 2015 Share Posted September 19, 2015 Gils and I have tested successfully for a while ago, another variant, but one must look it as an experiment. A hybrid of AppleHDA and VoodooHDA ... works without Kernel Panic. Yes, it's possible but IMHO, too complex for the same result… And don't forget the updates ! With this method, any modification of the AppleHDA will break the trick. unless they're only applied in the VoodooHDA … Link to comment Share on other sites More sharing options...
spakk Posted September 19, 2015 Share Posted September 19, 2015 I have already mentioned, this is to be regarded only as an experiment and has no chance of a daily use ... then you have after each update, tinker .. that's not good. 1 Link to comment Share on other sites More sharing options...
polyzargone Posted September 19, 2015 Share Posted September 19, 2015 Sure . Sorry, read too fast as often Link to comment Share on other sites More sharing options...
cgiannakidis70 Posted September 19, 2015 Share Posted September 19, 2015 Hello to all Im new to Hackintosh.My rig is that in my signature.I ve installed Yosemite 10.10.1 (yosemite zone).My system as far as i can see and understand works fine but something is telling me to update to 10.10.3 .I tried some guides but without any luck. With all your respect what kernel should I use and which kexts. In other words if you have the patience how would i update to 10.10.3 succesfully. Thanks in advance. Link to comment Share on other sites More sharing options...
gils83 Posted September 19, 2015 Share Posted September 19, 2015 with kernel 14.5 Y2k4u listen , it's video and audio SF 4.5 video 960/540 30 fps // Audio 48 khz 320 kb/s but capture files UHD 4k 60 fps/audio FLAC 5.1 and files audio Itunes audio ALC 887 892 voodooHDA 2.8.4 96 Khz / 24 bit (Slice/Andy) works very good , no crackle and no desynchro files MP4 H265 ScreenFlow3.mp4.zip Link to comment Share on other sites More sharing options...
spakk Posted September 19, 2015 Share Posted September 19, 2015 Hello to all Im new to Hackintosh.My rig is that in my signature.I ve installed Yosemite 10.10.1 (yosemite zone).My system as far as i can see and understand works fine but something is telling me to update to 10.10.3 .I tried some guides but without any luck. With all your respect what kernel should I use and which kexts. In other words if you have the patience how would i update to 10.10.3 succesfully. Thanks in advance. use one of the last two current 10.10.5 kernels, see here: http://www.insanelymac.com/forum/topic/285580-database-of-current-working-amd-kernels/page-4?do=findComment&comment=2168603 whether it is necessary to replace system drivers, according to the update of 10.10.3 to 10.10.4 you must try it for yourself. I suspect that this is not necessary because we now have a current kernel. Link to comment Share on other sites More sharing options...
cgiannakidis70 Posted September 19, 2015 Share Posted September 19, 2015 Thank you for your anwser.I tried one of those current 10.10.5 kernels and I m getting a strange message " kernel invalid opcode 64 bit .........". Link to comment Share on other sites More sharing options...
spakk Posted September 20, 2015 Share Posted September 20, 2015 ....kernel invalid opcode 64 bit ..... 1.) It is always better to install the new kernel on a freshly installed version (clean Install without changes to the system drivers !! ). You must now reconstruct what changes you made before or after the update in the S/L/Extensions folder. make the changes undone! fix the permissions, renew the kernel cache. 2.) should you not know what system drivers you have exchanged or changed, that would not be good! Then you need to replace S/L/Extensions with the current "Extensions" folder from the current Yosemite version! (***1) Then you have to reparier the permessions and renew the kernel cache! Edit: Install all drivers for your hardware and FakeSMC, Nullpower etc. in Extra/Extensions/Boats with the addition: UsekernelCache=No (***1) Open the DMG with the DiskImageMounter or Disk Utility, or Pacifist, a pkg file can open with Pacifist.app and then export the complete Extensions folder, and thus exchange the Extensions folder in your partition. I hope that this description will help you to resolve your problem. 1 Link to comment Share on other sites More sharing options...
gils83 Posted September 20, 2015 Share Posted September 20, 2015 for invalid opcode , just replace pthread.kext is a simple solution 1 Link to comment Share on other sites More sharing options...
spakk Posted September 20, 2015 Share Posted September 20, 2015 @Gils, which may be possible in his case, but I am not sure what he has made changes Previously, I gave him a description in order to make a limit any Possible errors. Basically, he must be remembered what he has changed before. Edit: But such questions belong to the help toppic. Link to comment Share on other sites More sharing options...
gils83 Posted September 20, 2015 Share Posted September 20, 2015 the problem is that members confuse many things and created problems that do not exist now knowing that the update 10.10.5 asked many problems, members have mixed everything without knowing what changed. I recommend reinstalling the combo via 10.10.5 pacifist and proper tree resume his rights, then just replace the kernel and reboot with -f simply. Link to comment Share on other sites More sharing options...
gils83 Posted September 20, 2015 Share Posted September 20, 2015 (edited) no problem with Phenom x4 B55 sound works good , no crackle , no desynchro with voodooPstate enable and many thanks Bronya for file "boot" http://www.sendbox.fr/3f393d2ae7ff5b2b/small.zip Last login: Sun Sep 20 14:30:58 on console Mac-Pro-de-gils:~ gils$ uname -a Darwin Mac-Pro-de-gils 14.5.0 Darwin Kernel Version 14.5.0: Thu Sep 17 21:09:40 ICT 2015; rootrootroot:xnu-2782.40.9/BUILD/obj/RELEASE_X86_64 x86_64 Mac-Pro-de-gils:~ gils$ sysctl machdep machdep.user_idle_level: 0 machdep.cpu.max_basic: 5 machdep.cpu.max_ext: 2147483675 machdep.cpu.vendor: AuthenticAMD machdep.cpu.brand_string: AMD Phenom(tm) II X4 B55 Processor machdep.cpu.family: 16 machdep.cpu.model: 4 machdep.cpu.extmodel: 0 machdep.cpu.extfamily: 1 machdep.cpu.stepping: 3 machdep.cpu.feature_bits: 36064020440808447 machdep.cpu.extfeature_bits: 61572378786815 machdep.cpu.signature: 1052483 machdep.cpu.brand: 0 machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH MMX FXSR SSE SSE2 HTT SSE3 MON CX16 POPCNT machdep.cpu.extfeatures: SYSCALL 1GBPAGE EM64T LAHF LZCNT PREFETCHW RDTSCP TSCI machdep.cpu.logical_per_package: 4 machdep.cpu.cores_per_package: 4 machdep.cpu.microcode_version: 21 machdep.cpu.processor_flag: 1 machdep.cpu.mwait.linesize_min: 64 machdep.cpu.mwait.linesize_max: 64 machdep.cpu.mwait.extensions: 3 machdep.cpu.mwait.sub_Cstates: 0 machdep.cpu.cache.linesize: 64 machdep.cpu.cache.L2_associativity: 16 machdep.cpu.cache.size: 512 machdep.cpu.tlb.inst.small: 32 machdep.cpu.tlb.inst.large: 16 machdep.cpu.tlb.data.small: 48 machdep.cpu.tlb.data.small_level1: 512 machdep.cpu.tlb.data.large: 48 machdep.cpu.tlb.data.large_level1: 128 machdep.cpu.address_bits.physical: 48 machdep.cpu.address_bits.virtual: 48 machdep.cpu.core_count: 4 machdep.cpu.thread_count: 4 machdep.vectors.timer: 221 machdep.vectors.IPI: 222 machdep.pmap.hashwalks: 253818 machdep.pmap.hashcnts: 477535 machdep.pmap.hashmax: 30 machdep.pmap.kernel_text_ps: 2097152 machdep.pmap.kern_pv_reserve: 4000 machdep.memmap.Conventional: 4292390912 machdep.memmap.RuntimeServices: 0 machdep.memmap.ACPIReclaim: 53248 machdep.memmap.ACPINVS: 12288 machdep.memmap.PalCode: 0 machdep.memmap.Reserved: 290521088 machdep.memmap.Unusable: 0 machdep.memmap.Other: 0 machdep.tsc.frequency: 3214187560 machdep.tsc.deep_idle_rebase: 1 machdep.tsc.nanotime.tsc_base: 120325472800 machdep.tsc.nanotime.ns_base: 0 machdep.tsc.nanotime.scale: 1336252852 machdep.tsc.nanotime.shift: 0 machdep.tsc.nanotime.generation: 2 machdep.misc.panic_restart_timeout: 1266874889 machdep.misc.interrupt_latency_max: 0x1 0xde 0x1259af machdep.misc.machine_check_panic: machdep.misc.timer_queue_trace: machdep.misc.nmis: 0 machdep.eager_timer_evaluations: 79 machdep.eager_timer_evaluation_max: 414126 Mac-Pro-de-gils:~ gils$ sysctl kern kern.ostype: Darwin kern.osrelease: 14.5.0 kern.osrevision: 199506 kern.version: Darwin Kernel Version 14.5.0: Thu Sep 17 21:09:40 ICT 2015; rootrootroot:xnu-2782.40.9/BUILD/obj/RELEASE_X86_64 kern.maxvnodes: 66560 kern.maxproc: 1064 kern.maxfiles: 12288 kern.argmax: 262144 kern.securelevel: 0 kern.hostname: Mac-Pro-de-gils kern.hostid: 0 kern.clockrate: { hz = 100, tick = 10000, tickadj = 22, profhz = 100, stathz = 100 } kern.posix1version: 200112 kern.ngroups: 16 kern.job_control: 1 kern.saved_ids: 1 kern.boottime: { sec = 1442752182, usec = 0 } Sun Sep 20 14:29:42 2015 kern.nisdomainname: kern.maxfilesperproc: 10240 kern.maxprocperuid: 709 kern.ipc.maxsockbuf: 4194304 kern.ipc.sockbuf_waste_factor: 8 kern.ipc.somaxconn: 128 kern.ipc.nmbclusters: 32768 kern.ipc.soqlimitcompat: 1 kern.ipc.mleak_sample_factor: 500 kern.ipc.mb_normalized: 0 kern.ipc.mb_watchdog: 0 kern.ipc.mb_drain_force: 0 kern.ipc.mb_drain_maxint: 0 kern.ipc.socket_debug: 0 kern.ipc.sosendminchain: 16384 kern.ipc.sorecvmincopy: 16384 kern.ipc.sosendjcl: 1 kern.ipc.sosendjcl_ignore_capab: 0 kern.ipc.sosendbigcl_ignore_capab: 0 kern.ipc.sodefunctlog: 0 kern.ipc.sothrottlelog: 0 kern.ipc.sorestrictrecv: 1 kern.ipc.sorestrictsend: 1 kern.ipc.sotcdb: 1 kern.ipc.njcl: 10920 kern.ipc.njclbytes: 16384 kern.ipc.soqlencomp: 0 kern.ipc.io_policy.throttled: 0 kern.ipc.io_policy.log: 0 kern.ipc.io_policy.uuid: 1 kern.usrstack: 1433247744 kern.netboot: 0 kern.sysv.shmmax: 4194304 kern.sysv.shmmin: 1 kern.sysv.shmmni: 32 kern.sysv.shmseg: 8 kern.sysv.shmall: 1024 kern.sysv.semmni: 87381 kern.sysv.semmns: 87381 kern.sysv.semmnu: 87381 kern.sysv.semmsl: 87381 kern.sysv.semume: 10 kern.aiomax: 90 kern.aioprocmax: 16 kern.aiothreads: 4 kern.corefile: /cores/core.%P kern.coredump: 1 kern.sugid_coredump: 0 kern.delayterm: 0 kern.shreg_private: 0 kern.posix.sem.max: 10000 kern.usrstack64: 140734626635776 kern.nx: 0 kern.tfp.policy: 2 kern.procname: kern.speculative_reads_disabled: 0 kern.osversion: 14F27 kern.safeboot: 0 kern.lctx.last: 1 kern.lctx.count: 0 kern.lctx.max: 8192 kern.rage_vnode: 0 kern.tty.ptmx_max: 127 kern.threadname: kern.sleeptime: { sec = 0, usec = 0 } Thu Jan 1 01:00:00 1970 kern.waketime: { sec = 0, usec = 0 } Thu Jan 1 01:00:00 1970 kern.willshutdown: 0 kern.progressmeterenable: 0 kern.progressmeter: 0 kern.wakereason: kern.hibernatefile: kern.bootsignature: kern.hibernatemode: 0 kern.hibernategraphicsready: 0 kern.hibernatewakenotification: 0 kern.hibernatelockscreenready: 0 kern.hibernatehidready: 0 kern.wq_yielded_threshold: 2000 kern.wq_yielded_window_usecs: 30000 kern.wq_stalled_window_usecs: 200 kern.wq_reduce_pool_window_usecs: 5000000 kern.wq_max_timer_interval_usecs: 50000 kern.wq_max_threads: 512 kern.wq_max_constrained_threads: 64 kern.pthread_debug_tracing: 0 kern.dtrace.err_verbose: 0 kern.dtrace.buffer_memory_maxsize: 1431655765 kern.dtrace.buffer_memory_inuse: 0 kern.dtrace.difo_maxsize: 262144 kern.dtrace.dof_maxsize: 393216 kern.dtrace.global_maxsize: 16384 kern.dtrace.provide_private_probes: 0 kern.nbuf: 16384 kern.maxnbuf: 16384 kern.jnl_trim_flush: 240 kern.flush_cache_on_write: 0 kern.ds_supgroups_supported: 1 kern.sugid_scripts: 0 kern.zleak.active: 0 kern.zleak.max_zonemap_size: 1610612736 kern.zleak.global_threshold: 805306368 kern.zleak.zone_threshold: 100663296 kern.uuid: D7BFF2EB-DE16-35DF-A8B6-2FCDA64BC830 kern.bootargs: fsb=200 Mhz npci=0x2000 dart=0 -v kern.num_files: 1556 kern.num_vnodes: 51583 kern.num_tasks: 2048 kern.num_threads: 10240 kern.num_taskthreads: 2048 kern.namecache_disabled: 0 kern.ignore_is_ssd: 0 kern.preheat_max_bytes: 1048576 kern.preheat_min_bytes: 32768 kern.speculative_prefetch_max: 201326592 kern.speculative_prefetch_max_iosize: 524288 kern.vm_page_free_target: 4000 kern.vm_page_free_min: 3500 kern.vm_page_free_reserved: 800 kern.vm_page_speculative_percentage: 5 kern.vm_page_speculative_q_age_ms: 500 kern.vm_max_delayed_work_limit: 32 kern.vm_max_batch: 256 kern.bootsessionuuid: C2468D37-B2EC-41F3-B6F4-0876F26B260F kern.timer.coalescing_enabled: 1 kern.timer.deadline_tracking_bin_1: 2000000 kern.timer.deadline_tracking_bin_2: 5000000 kern.timer.longterm.threshold: 1000 kern.timer.longterm.qlen: 39 kern.singleuser: 0 kern.affinity_sets_enabled: 1 kern.affinity_sets_mapping: 1 kern.slide: 0 kern.ipc_voucher_trace_contents: 0 kern.stack_size: 16384 kern.stack_depth_max: 8744 kern.ipc_portbt: 0 kern.sched: multiq kern.timer_coalesce_bg_scale: -5 kern.timer_resort_threshold_ns: 50000000 kern.timer_coalesce_bg_ns_max: 100000000 kern.timer_coalesce_kt_scale: 3 kern.timer_coalesce_kt_ns_max: 1000000 kern.timer_coalesce_fp_scale: 3 kern.timer_coalesce_fp_ns_max: 1000000 kern.timer_coalesce_ts_scale: 3 kern.timer_coalesce_ts_ns_max: 1000000 kern.timer_coalesce_tier0_scale: 3 kern.timer_coalesce_tier0_ns_max: 1000000 kern.timer_coalesce_tier1_scale: 2 kern.timer_coalesce_tier1_ns_max: 5000000 kern.timer_coalesce_tier2_scale: 1 kern.timer_coalesce_tier2_ns_max: 20000000 kern.timer_coalesce_tier3_scale: -2 kern.timer_coalesce_tier3_ns_max: 75000000 kern.timer_coalesce_tier4_scale: -15 kern.timer_coalesce_tier4_ns_max: 10000000000 kern.timer_coalesce_tier5_scale: -15 kern.timer_coalesce_tier5_ns_max: 10000000000 kern.hv_support: 0 kern.memorystatus_purge_on_warning: 2 kern.memorystatus_purge_on_urgent: 5 kern.memorystatus_purge_on_critical: 8 kern.msgbuf: 16384 kern.secure_kernel: 0 kern.interrupt_timer_coalescing_enabled: 1 kern.timer_coalesce_idle_entry_hard_deadline_max: 5000000 Mac-Pro-de-gils:~ gils$ Archive.zip file boot.zip Edited September 20, 2015 by gils83 Link to comment Share on other sites More sharing options...
J0hny Posted September 20, 2015 Share Posted September 20, 2015 After update via App Store get black screen when try to boot. I've tried both kernels, no luck... Link to comment Share on other sites More sharing options...
spakk Posted September 20, 2015 Share Posted September 20, 2015 (edited) After update via App Store get black screen when try to boot. I've tried both kernels, no luck... try with: nvda_drv=1 or nv_disable=1 this bootflag was for Lion, to resolve the problem of the black screen.: darkwake=0 I do not know if that will work for Yosemite? Edited September 20, 2015 by spakk Link to comment Share on other sites More sharing options...
J0hny Posted September 20, 2015 Share Posted September 20, 2015 (edited) try with: nvda_drv=1 or nv_disable=1 Didn't work.( I've using official mac driver so it's useless.. this bootflag was for Lion, to resolve the problem of the black screen.: darkwake=0 I do not know if that will work for Yosemite? Same result. I think I will do a clean install of mac os x and then report here.) Edited September 20, 2015 by ImmortalSoulL Link to comment Share on other sites More sharing options...
gils83 Posted September 20, 2015 Share Posted September 20, 2015 After update via App Store get black screen when try to boot. I've tried both kernels, no luck... black screen or reboot ? and GraphicsEnabler=No -f Link to comment Share on other sites More sharing options...
spakk Posted September 20, 2015 Share Posted September 20, 2015 Gils, look at this one, please : http://www.insanelymac.com/forum/topic/307318-os-x-el-capitan-1011-public-beta/page-2?do=findComment&comment=2169236 Link to comment Share on other sites More sharing options...
J0hny Posted September 20, 2015 Share Posted September 20, 2015 black screen or reboot ? and GraphicsEnabler=No -f You're right, I was so blind! It was clover fault! When I've installed my mac, even then I couldn't boot, there was that black screen and then reboot! But then I've booted succesfully with chameleon, installed voodoohda, repair permissions and rebuild cache. And then I was able to boot into system with clover bootloader with my usual settings... Strange why clover couldn't boot for the first time after update or after clean installed mac. But now I have clean mac, I even have it working without patched pthread.kext, only original! Thank you guys for another good kernel! It's awesome! 2 Link to comment Share on other sites More sharing options...
polyzargone Posted September 20, 2015 Share Posted September 20, 2015 You're right, I was so blind! It was clover fault! When I've installed my mac, even then I couldn't boot, there was that black screen and then reboot! But then I've booted succesfully with chameleon, installed voodoohda, repair permissions and rebuild cache. And then I was able to boot into system with clover bootloader with my usual settings... Strange why clover couldn't boot for the first time after update or after clean installed mac. But now I have clean mac, I even have it working without patched pthread.kext, only original! Thank you guys for another good kernel! It's awesome! I had the same exact problem when trying to boot 10.10.5 vanilla fresh install Clover didn't boot at all and even when it could, it ended up with black screen (old Nvidia GT 8600 btw use now AMD Radeon HD 5450 because of conflicts between integrated nForce Geforce chipset and discrete card). The only solution was to first boot with boot-flags -f (and GE=Yes in my case GE=No with patched AMD kexts) to let the system rebuild the cache and load all necessary kexts. I guess this has something to do with the way how Clover manage kernelcache vs Chameleon booting directly on the kernel . After that, Clover was able to boot and inject it's own kexts from CLOVER/kexts/10.10. Now, it's not perfect since I'm still facing weird issues where the system boots but doesn't load the whole UI. I have mixed results using Clover or Chameleon but at the moment, it's still very hazardous and I can't figure why… But one thing is for sure, this new kernel 10.10.5 works terrific with vanilla OS X 10.10.5 (at least on AMD systems which is kinda ironic for Intel's unsupported CPUs ) and I want to thank all of you for this ! Guys, you rock as usual ! 3 Link to comment Share on other sites More sharing options...
gils83 Posted September 20, 2015 Share Posted September 20, 2015 you should know that with Clover, it is impossible to start without kernelCache, I tried all kinds of flag unsuccessful when the kernel change requires restart with Chameleon -f (ignore cache), once the cache rebuilt with kext wizard, it is then possible to restart with Clover Link to comment Share on other sites More sharing options...
polyzargone Posted September 20, 2015 Share Posted September 20, 2015 you should know that with Clover, it is impossible to start without kernelCache, I tried all kinds of flag unsuccessful when the kernel change requires restart with Chameleon -f (ignore cache), once the cache rebuilt with kext wizard, it is then possible to restart with Clover Correct ! Please be kind with me . This is my very first attempt to use Clover as the main bootloader on an AMD system . My old one was a fu****g HP with a bios that remind me the 90's era ! Link to comment Share on other sites More sharing options...
J0hny Posted September 20, 2015 Share Posted September 20, 2015 If you would told me that earlier, my old mac would be still live... p.s. in my opinion clover is the best bootloader, but I like chameleon too... They are actually both good bootloaders I think... 1 Link to comment Share on other sites More sharing options...
Recommended Posts