Bronya Posted August 20, 2014 Share Posted August 20, 2014 first test I have delete the folder /modules/... same error message appears .. Second Test with custom drivers, as already described in my first post ... no error message. Bronya ... this is not to due with Files from /modules/ folder For me flag -f and i get error message , i tried delete modules and no error message with flag -f . 1 Link to comment Share on other sites More sharing options...
spakk Posted August 20, 2014 Share Posted August 20, 2014 Bronya, but that's no problem for me .. my hackintosh works very good with all other kernels of you. I wanted to share just my experience with this error here. Thank you for your information and report ☺ 1 Link to comment Share on other sites More sharing options...
Bronya Posted August 20, 2014 Share Posted August 20, 2014 Yes , but problem loading kext AMD2400Controller.kext and get "Memory allocation error" - need delete it is kext AMD2400Controller.kext, and is working ))) Or repair permissions and same working . Is problem only Chameleon =))) Link to comment Share on other sites More sharing options...
spakk Posted August 20, 2014 Share Posted August 20, 2014 this error message appears continuously until all kext drivers are not compatible with the hardware.... Only when all are not compatible kext drivers removed from s/l/e then the system boot successfully without error message. If I adjust or change ob delete drivers from my system I start basically the Repair Disk Permissions and renew the cache Link to comment Share on other sites More sharing options...
gils83 Posted August 20, 2014 Share Posted August 20, 2014 big thank you Bronya !! Большое спасибо вам Броня !! 1 Link to comment Share on other sites More sharing options...
Eweie Posted August 20, 2014 Share Posted August 20, 2014 Bronya, I tried your rc2 kernel and system.kext, with the -cpuEFI flag and it fixed the fast system clock. no more bug in avatars in Skype or other programs and iMovie/Final Cut work again. but as others, I have launchpad bug (white icons) and weird names on desktop. keep up the good work. 1 Link to comment Share on other sites More sharing options...
EsLam Easa Posted August 20, 2014 Share Posted August 20, 2014 please find something for Amd Turion ii p520 and ... tell me how to work this 2 GPU ... anyone Graphics card :ATI Mobility Radeon HD 5470 AMD M880G with ATI Mobility Radeon HD 4250 Link to comment Share on other sites More sharing options...
gils83 Posted August 21, 2014 Share Posted August 21, 2014 please find something for Amd Turion ii p520 and ... tell me how to work this 2 GPU ... anyone Graphics card :ATI Mobility Radeon HD 5470 AMD M880G with ATI Mobility Radeon HD 4250 Graphics card :ATI Mobility Radeon HD 5470 AMD M880G with ATI Mobility Radeon HD 4250 , no work CI/QE 1 Link to comment Share on other sites More sharing options...
spakk Posted August 21, 2014 Share Posted August 21, 2014 @EsLam Easa I think your laptop with two integrated graphics card can work only with a matching DSDT.aml for your System, but it can works with only one graphics card Link to comment Share on other sites More sharing options...
spakk Posted August 21, 2014 Share Posted August 21, 2014 (edited) Boot Problem with new update 10.9.5 build 13f18the new update has this change carried out in S / L / E see imageEdit:after the update to Mavericks 10.9.5 Build 13F18 Mavericks I got boot problems, the system collapsed because of a Kernel Panic. then I've booted with my second OS X partition. replaced the System.kext from kernel package of Bronya and replaced the IOHIDFamily.kext from Mavericks 10.9.5, then I've removed with myHack.app the problem kexts drivers (Nvidia Graphic card) , and repaired the permissions, then I could boot again without problems. Edited August 21, 2014 by spakk Link to comment Share on other sites More sharing options...
Bronya Posted August 21, 2014 Share Posted August 21, 2014 MACH_Kernel for "panic(cpu 0 caller 0xffffff8000309997): Kernel trap at 0xffffff80002fb3ff, type 0=divide error, registers:" in Vmvare fixed . Wait ... Working in vmware ... 2 Link to comment Share on other sites More sharing options...
AlmirKadric Posted August 21, 2014 Share Posted August 21, 2014 I'd try with full legit' Chameleon, not that other stuff and with Bronya's 10.9.2 RC7 FX before trying Bronya's 10.9.4 RC2. Then, be aware that virtual machines are often found problematic. Can't you try and build an installation directly on a external media (USB key, HDD)?. This is a "full legit Chameleon". I checked it out from the SVN repository and built it. As for virtual machines being a problem, I managed to install 10.9.2 distro already. However I wanted to re-create the process from scratch with 10.94. This is a pet project I'm working on to make installer ISOs a lot easier to create with an automated process. Hi ! It is panic in Vmware 10 ? Right ? Yes it is. I'm testing my ISOs against both VMWare 10 and VirtualBox. Plan on creating some automated installer and startup tests using vagrant. If you're interested in setting up some form of versioning and automated unit testing for your kernels let me know. I was planning on setting something up once the above scripts are complete. Yes , but problem loading kext AMD2400Controller.kext and get "Memory allocation error" - need delete it is kext AMD2400Controller.kext, and is working ))) Or repair permissions and same working . Is problem only Chameleon =))) Yeah this seems to have been the problem. I could have sworn this was the first thing I tried. But after seeing the next error it seems that when i saw the same error again but with AMD2600Controller.kext instead, I must have thought it wasn't fixed. It was late when i did the initial tests XD So far I had to remove:- AMD2400Controller.kext - AMD2600Controller.kext - AMD3800Controller.kext - AMD7000Controller.kext And the following load fine: - AMD4600Controller.kext - AMD4800Controller.kext - AMD5000Controller.kext - AMD6000Controller.kext I will work through the last of the kexts and see how far I can get. Will keep you all posted on my progress. MACH_Kernel for "panic(cpu 0 caller 0xffffff8000309997): Kernel trap at 0xffffff80002fb3ff, type 0=divide error, registers:" in Vmvare fixed . Wait ... Thanks! that should be a big help Also I don't think the above are related to Chameleon since they don't appear to be a problem with the rc1 kernel. rc1 kernel get's past the kexts and ends up with the divide by 0 error once the kernel starts to load. I will let you know if the divide by 0 error appears on rc2 once i got all the kext issues resolved. Link to comment Share on other sites More sharing options...
pico joe Posted August 22, 2014 Share Posted August 22, 2014 Hi all, today I update Mavericks build 13f18 .. with bronya_kernel 10.9.4 rc2 and get a problem like spakk machines .. rollback IOHIDFamily n IOUSBFamily .. and normal again, but not that point. I think build 13f18 is more complicated or similiar like Yosemite problem in AMD .. so maybe we can make experiment with this kernel on Yosemite .. .., or maybe bronya can share his experimental kernel for Yosemite 1 Link to comment Share on other sites More sharing options...
spakk Posted August 22, 2014 Share Posted August 22, 2014 (edited) @pico joeThese tests I've made yesterday with rc1 and rc2 ... I can get upload the kernel panic message, after ... the update Build 13F18 and the last amd kernels of Bronya come to the specifications of Yosemite very close. Edit:you can comparing the three kernels (rc1, rc2 and yosemite dp6 kernel) with each other then one sees some differences in the structure of yosemite kernel. I have compared the respective tree with Ida and then compared the trees structure with DiffDoc. Edited August 22, 2014 by spakk Link to comment Share on other sites More sharing options...
AlmirKadric Posted August 22, 2014 Share Posted August 22, 2014 @Bronya out of curiosity, how are you patching the kernels? Are you taking current XNU source code and patching it? Or are you taking the binary and doing assembly patching? Link to comment Share on other sites More sharing options...
spakk Posted August 22, 2014 Share Posted August 22, 2014 @Bronya out of curiosity, how are you patching the kernels? Are you taking current XNU source code and patching it? Or are you taking the binary and doing assembly patching? all Mavericks kernels were created and based on xnu-source but Yosemite xnu source has apple not been released and therefore not available for developer, therefore the experiment is based on binary kernel patch. Link to comment Share on other sites More sharing options...
AlmirKadric Posted August 22, 2014 Share Posted August 22, 2014 BREAK THROUGH!!!So I did some more thorough testing and it seems Bronya was right on the mark. My Chameleon modules were causing my kext issues. More specifically FileNVRAM. After removing it all my kext issues were resolved and the kernel loads. For simplicity reasons I decided to only keep 2 Chameleon modules, Keylayout.dylib and Resolution.dylib. Now for the next part. I'm now hitting the "divide by 0" panic with rc2 kernel, the same as all other versions. @Bronya You mentioned that you fixed the VMWare issue? Where can I download this new kernel version? all Mavericks kernels were created and based on xnu-source but Yosemite xnu source has apple not been released and therefore not available for developer, therefore the experiment is based on binary kernel patch. Ah thanks for that, do you guys use any versioning system for the updates? i.e. merging in official changes and having patches applied in a separate branch? gitflow etc? Also to add, I never got the module issue with kernel rc1 and below, so I think there is something in the rc2 kernel that breaks the FileNVRAM module. As for the "divide by 0" panic, I get this with all the recent versions of the 10.9 kernels. However I didn't get this when I used installed Niresh's 10.8 distro or when I used the 10.9 kernel I got from Niresh's site. Though I would prefer to identify what these issue are and have them fixed at the source. Would love to also help you guys improve workflow to prevent bugs and backward breakage. Will see what I can do about a XNU github mirror and patching workflow to make this all more efficient.According to Apples XNU license should be perfectly legal Link to comment Share on other sites More sharing options...
Morpheus NS Posted August 22, 2014 Share Posted August 22, 2014 It does, but it didn't help with my iCloud issues, so it is pretty much useless... at least on my system. 1 Link to comment Share on other sites More sharing options...
spakk Posted August 22, 2014 Share Posted August 22, 2014 Afaik, FileNVRAM module does not work with AMD kernels... Do you ever see any nvram-xxxxxxx.plist created? If no, then you can simply get rid of the module as it's ineffective. @ Hervé, that's not right !! I always boot with FileNVRam.dylib and the nvram * plist was created automatically, I have no problems with it on my AMD Hackintosh does not respect my chaotic mess on my test partition 1 Link to comment Share on other sites More sharing options...
Eweie Posted August 22, 2014 Share Posted August 22, 2014 @ Hervé, that's not right !! I always boot with FileNVRam.dylib and the nvram * plist was created automatically, I have no problems with it on my AMD Hackintosh does not respect my chaotic mess on my test partition But does it do anything at all? I did this too but I don't see a difference with or without it so I just deleted it. Link to comment Share on other sites More sharing options...
Bronya Posted August 22, 2014 Share Posted August 22, 2014 Hi ! This kernel_rc3 for FX , but for old cpus - glitches graphics icons . I know how fix , but don't effect . Need wait . Is working in Vmware, VirtualBox and Parallels Desktop ! Diff file in archive include ! mach_10_9_4_rc3.zip 6 Link to comment Share on other sites More sharing options...
spakk Posted August 22, 2014 Share Posted August 22, 2014 (edited) I gotta fight my way through, Bronya first test with the same error as picture 1 http://www.insanelymac.com/forum/topic/281450-mavericks-kernel-testing-on-amd-formerly-mountain-lion-kernel-testing-on-amd/page-308?do=findComment&comment=2053689 I am just remove the driver from /S/L/E, then I start tmy hackintosh and will report Edit: @bronya no chance for AMD Phenom II X6, with and without replace of System.kext. my hackintosh will not boot with amd kernel rc3 Edited August 22, 2014 by spakk Link to comment Share on other sites More sharing options...
Redbyte Posted August 22, 2014 Share Posted August 22, 2014 So I might just be a moron and missing something but it seems that all the new kernels from bronya they seem to be inconsistent with posting to the OS X installer (via MyHack flashdrive). I will attach a log from one of the times it did load. But even so the installer says it has an error and doesn't load. Its weird because the exact same flags might boot once and then not for another 3-4 tries. The attached log is with my fx8150, no system.kext replace (as it seems to not matter), and these boot flags; mach_kernel-rc3-94 -v -f -F npci=0x2000 GraphicsEnabler=No PciRoot=1 Cheers mates Installer Log 22-Aug-2014 rc3 No-SystemK 8150.txt Link to comment Share on other sites More sharing options...
gils83 Posted August 23, 2014 Share Posted August 23, 2014 kabini 5350 work !! it's good new with lag but work machdep.user_idle_level: 0 machdep.cpu.max_basic: 13 machdep.cpu.max_ext: 2147483678 machdep.cpu.vendor: AuthenticAMD machdep.cpu.brand_string: AMD Athlon(tm) 5350 APU with Radeon(tm) R3 machdep.cpu.family: 22 machdep.cpu.model: 0 machdep.cpu.extmodel: 0 machdep.cpu.extfamily: 7 machdep.cpu.stepping: 1 machdep.cpu.feature_bits: 4528406856356068351 machdep.cpu.extfeature_bits: 1531285442464578559 machdep.cpu.signature: 7343873 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 PCLMULQDQ MON SSSE3 CX16 SSE4.1 SSE4.2 MOVBE POPCNT AES XSAVE OSXSAVE AVX1.0 F16C machdep.cpu.extfeatures: SYSCALL XD 1GBPAGE EM64T LAHF LZCNT PREFETCHW RDTSCP TSCI machdep.cpu.logical_per_package: 4 machdep.cpu.cores_per_package: 4 machdep.cpu.microcode_version: 395049983 machdep.cpu.processor_flag: 2 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.thermal.sensor: 0 machdep.cpu.thermal.dynamic_acceleration: 0 machdep.cpu.thermal.invariant_APIC_timer: 0 machdep.cpu.thermal.thresholds: 0 machdep.cpu.thermal.ACNT_MCNT: 1 machdep.cpu.thermal.core_power_limits: 0 machdep.cpu.thermal.fine_grain_clock_mod: 0 machdep.cpu.thermal.package_thermal_intr: 0 machdep.cpu.thermal.hardware_feedback: 0 machdep.cpu.thermal.energy_policy: 0 machdep.cpu.xsave.extended_state: 7 832 832 0 machdep.cpu.arch_perf.version: 0 machdep.cpu.arch_perf.number: 0 machdep.cpu.arch_perf.width: 0 machdep.cpu.arch_perf.events_number: 0 machdep.cpu.arch_perf.events: 0 machdep.cpu.arch_perf.fixed_number: 0 machdep.cpu.arch_perf.fixed_width: 0 machdep.cpu.cache.linesize: 64 machdep.cpu.cache.L2_associativity: 16 machdep.cpu.cache.size: 2048 machdep.cpu.address_bits.physical: 40 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: 306688 machdep.pmap.hashcnts: 2309379 machdep.pmap.hashmax: 91 machdep.pmap.kernel_text_ps: 2097152 machdep.pmap.kern_pv_reserve: 4000 machdep.memmap.Conventional: 4232548352 machdep.memmap.RuntimeServices: 2097152 machdep.memmap.ACPIReclaim: 524288 machdep.memmap.ACPINVS: 835584 machdep.memmap.PalCode: 0 machdep.memmap.Reserved: 38707200 machdep.memmap.Unusable: 0 machdep.memmap.Other: 0 machdep.tsc.frequency: 2000000000 machdep.tsc.deep_idle_rebase: 1 machdep.tsc.nanotime.tsc_base: 39822963216 machdep.tsc.nanotime.ns_base: 0 machdep.tsc.nanotime.scale: 2147483648 machdep.tsc.nanotime.shift: 0 machdep.tsc.nanotime.generation: 2 machdep.misc.fast_uexc_support: 1 machdep.misc.panic_restart_timeout: 1266874889 machdep.misc.interrupt_latency_max: 0x0 0xdd 0x5ef73 machdep.misc.machine_check_panic: machdep.misc.timer_queue_trace: machdep.misc.nmis: 0 machdep.xcpm.mode: 0 machdep.xcpm.asserts_enabled: 0 machdep.xcpm.asserts_traced: 0 machdep.xcpm.cpu_wakeup_energy_cost_selector: 0 machdep.xcpm.disable_quiesce: 0 machdep.xcpm.mp_match: 0 machdep.xcpm.disable_idle_self_select: 0 machdep.xcpm.mp_load_txfr_coeff: 128 machdep.xcpm.scalability_cpi_threshold: 4 machdep.xcpm.scalability_cpi_demotion_threshold: 5 machdep.xcpm.scalability_reeval_interval: 1000 machdep.xcpm.scalability_eval_ratio_min: 17 machdep.xcpm.scalability_detection_enabled: 0 machdep.xcpm.hard_plimit_max_100mhz_ratio: 0 machdep.xcpm.hard_plimit_min_100mhz_ratio: 0 machdep.xcpm.soft_plimit_max_100mhz_ratio: 0 machdep.xcpm.soft_plimit_min_100mhz_ratio: 0 machdep.xcpm.tuib_plimit_max_100mhz_ratio: 0 machdep.xcpm.tuib_plimit_min_100mhz_ratio: 0 machdep.xcpm.tuib_enabled: 0 machdep.xcpm.power_source: 0 machdep.xcpm.tuib_ns: 0 machdep.xcpm.ratio_changes_hf: 0 machdep.xcpm.ratio_changes_lf: 0 machdep.xcpm.ratio_change_limited: 0 machdep.xcpm.ratio_change_hf_limit: 2 machdep.xcpm.ratio_change_lf_limit: 1 machdep.xcpm.ratio_change_ratelimit_ns: 500000 machdep.xcpm.ratio_changes_total: 0 machdep.xcpm.maxbusdelay: 0 machdep.xcpm.maxintdelay: 0 machdep.xcpm.mbd_mode: 1 machdep.xcpm.mbd_applications: 0 machdep.xcpm.mbd_relaxations: 0 machdep.xcpm.forced_idle_ratio: 100 machdep.xcpm.forced_idle_period: 30000000 machdep.xcpm.deep_idle_log: 0 machdep.xcpm.qos_txfr: 1 machdep.xcpm.q_migration_ttd_min: 1000000 machdep.xcpm.q_migration_ttd_max: 100000000 machdep.xcpm.preidle_spin_tsc: 0 machdep.xcpm.qos_ratio_change_limited: 0 machdep.xcpm.qos_ratio_change_hf_limit: 8 machdep.xcpm.qos_ratio_change_lf_limit: 1 machdep.xcpm.qos_ratelimiting_enabled: 1 machdep.xcpm.quiesce_trace: 0 machdep.xcpm.non_focal_qos_active: 0 machdep.xcpm.utility_qos_active: 0 machdep.xcpm.utility_qos_target: 9 machdep.xcpm.utility_qos_default: 6 machdep.xcpm.utility_qos_current: 6 machdep.xcpm.deep_idle_count: 0 machdep.xcpm.deep_idle_last_stats: n/a machdep.xcpm.deep_idle_total_stats: n/a machdep.xcpm.cpu_thermal_level: 0 machdep.xcpm.gpu_thermal_level: 0 machdep.xcpm.io_thermal_level: 0 machdep.eager_timer_evaluations: 28 machdep.eager_timer_evaluation_max: 322291 kern.ostype: Darwin kern.osrelease: 14.0.0 kern.osrevision: 199506 kern.version: Darwin Kernel Version : Sat May 24 01:15:10 PDT 2014; root:xnu-2738.0.0.0.5~1/RELEASE_X86_64 kern.maxvnodes: 66560 kern.maxproc: 1064 kern.maxfiles: 12288 kern.argmax: 262144 kern.securelevel: 0 kern.hostname: iMac-de-gils.local 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 = 1293848342, usec = 0 } Sat Jan 1 03:19:02 2011 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.sosendminchain: 16384 kern.ipc.sorecvmincopy: 16384 kern.ipc.sosendjcl: 1 kern.ipc.sosendjcl_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: 1569484800 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: 140734762872832 kern.nx: 1 kern.tfp.policy: 2 kern.procname: kern.speculative_reads_disabled: 0 kern.osversion: 14A238x 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.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: D3A0B696-3353-314D-BA61-A8DDC7775770 kern.bootargs: busratio=20 fsb=100 Mhz -f -v npci=0x2000 kern.num_files: 1326 kern.num_vnodes: 14009 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: 2100 kern.vm_page_free_min: 1500 kern.vm_page_free_reserved: 228 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: D0156679-2BA4-4AFC-8FD1-F146447B3FEB 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: 52 kern.singleuser: 0 kern.affinity_sets_enabled: 1 kern.affinity_sets_mapping: 1 kern.slide: 1 kern.ipc_voucher_trace_contents: 0 kern.stack_size: 16384 kern.stack_depth_max: 8560 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 iMac-de-gils:~ gils$ 1 Link to comment Share on other sites More sharing options...
spakk Posted August 23, 2014 Share Posted August 23, 2014 rc3 will not boot with Phenom II X6..bronya can you programmed the kernel rc3 with opemu code for old AMD CPUs similar kernel rc1 ... Thanks in advance. Link to comment Share on other sites More sharing options...
Recommended Posts