pauℓzurrr. Posted January 7, 2013 Share Posted January 7, 2013 Booting RC4 with -x Without -x it kernel panic's because of NVidia Link to comment Share on other sites More sharing options...
instant idiot Posted January 7, 2013 Share Posted January 7, 2013 ... It should be more efficient ... It works just as well as the previous one, but it comes in exactly 3 seconds before the old one with a boot time of 1:37. I can take a video if you'd like to see where it hangs during boot. Link to comment Share on other sites More sharing options...
Andy Vandijck Posted January 7, 2013 Share Posted January 7, 2013 I think the graphics drivers have cpuids in them... need to check though... (Allready confirmed for Intel HD) 2 Link to comment Share on other sites More sharing options...
theconnactic Posted January 7, 2013 Author Share Posted January 7, 2013 Great insight, Andy! Hopefully this will help us nVidia users. On a side note, our friend Sinetek had a somewhat related idea a couple of hours ago, that the files cpuid.c and kern_mib.c perhaps should be patched to properly enable nVidia graphics. Unfortunately he had to leave for his class, so it didn't finished his patches for us to test. Best regards. 1 Link to comment Share on other sites More sharing options...
wastez Posted January 7, 2013 Share Posted January 7, 2013 This Version of the kernel is working better then the Last versions. It seems to be stable but the Boot time is still long. The graphic Problems are still there on ATI. Link to comment Share on other sites More sharing options...
theconnactic Posted January 8, 2013 Author Share Posted January 8, 2013 Well, Andy! I just disassembled some kexts and found a lot of cpuid instructions inside one that's really crucial, NVDAResman.kext (responsible for resolution control, i think). I talked with meklort and he agreed some of the cpuids could perhaps cause trouble, so i decided to upload the txt output of otool for you to take a look. Best regards! RSMN.txt.zip P.S.: Shane told me he patched NVDAResman.kext with your amd_insn_patcher, but it didn't solve the issue. It was supposed to remove the bad cpuids? Link to comment Share on other sites More sharing options...
Deltac0 Posted January 8, 2013 Share Posted January 8, 2013 Well, Andy! I just disassembled some kexts and found a lot of cpuid instructions inside one that's really crucial, NVDAResman.kext (responsible for resolution control, i think). I talked with meklort and he agreed some of the cpuids could perhaps cause trouble, so i decided to upload the txt output of otool for you to take a look. Best regards! RSMN.txt.zip P.S.: Shane told me he patched NVDAResman.kext with your amd_insn_patcher, but it didn't solve the issue. It was supposed to remove the bad cpuids? Doesn't amd_insn_patcher just remove the code signature or something? Link to comment Share on other sites More sharing options...
pauℓzurrr. Posted January 8, 2013 Share Posted January 8, 2013 Someone should run Marvin's AMD Utility on the Nvidia & ATI kext's.. http://www.insanelymac.com/forum/topic/67917-marvins-amd-utility/ Link to comment Share on other sites More sharing options...
Andy Vandijck Posted January 8, 2013 Share Posted January 8, 2013 Someone should run Marvin's AMD Utility on the Nvidia & ATI kext's.. http://www.insanelymac.com/forum/topic/67917-marvins-amd-utility/ Marvin's utility only does 32-bit cpuid patching and aes 32-bit decryption... Doesn't amd_insn_patcher just remove the code signature or something? No it patches up cpuid's and sysenter traps too... Int FB = cpuid 0FA2 to CDFB Int FC = sysenter Link to comment Share on other sites More sharing options...
wastez Posted January 8, 2013 Share Posted January 8, 2013 I checked every binarie of the ati/amd kexts which my card is using but there are no cpuids.... in the nvdaresman are 2 inside.... Or i´m wrong??? Link to comment Share on other sites More sharing options...
Andy Vandijck Posted January 8, 2013 Share Posted January 8, 2013 I checked every binarie of the ati/amd kexts which my card is using but there are no cpuids.... in the nvdaresman are 2 inside.... Or i´m wrong??? And the .plugin files used for Core Image / Quartz Extreme? Oh yeah... and the Geforce.kext? Link to comment Share on other sites More sharing options...
wastez Posted January 8, 2013 Share Posted January 8, 2013 There are just bundles and they contain also nothing. i checked the binaries of the following files: AMDRadeonVADriver.bundle; AMDRadeonAccelerator.kext; AMDRadeonX3000GLDriver.bundle ATI5000Controller.kext;ATIFramebuffer.kext; ATISupport.kext The first row should be for qe/ci I checked them with otool -tv /path/to/file|grep cpuid Should be enough to see it, right? Link to comment Share on other sites More sharing options...
Andy Vandijck Posted January 8, 2013 Share Posted January 8, 2013 Yep. I'll check the kexts later for other "sabotage code" X-) Link to comment Share on other sites More sharing options...
wastez Posted January 8, 2013 Share Posted January 8, 2013 The Geforce.kext does also not contain a cpuid. Link to comment Share on other sites More sharing options...
Deltac0 Posted January 8, 2013 Share Posted January 8, 2013 No it patches up cpuid's and sysenter traps too... Int FB = cpuid 0FA2 to CDFB Int FC = sysenter Thanks for correcting me! Link to comment Share on other sites More sharing options...
theconnactic Posted January 8, 2013 Author Share Posted January 8, 2013 Hi, folks! I'm almost sure i checked every single graphics kext inside my system but intel ones. The only one that has cpuids inside is NVDAResman.kext. Not only two, but dozens of them. Best regards! Link to comment Share on other sites More sharing options...
pauℓzurrr. Posted January 8, 2013 Share Posted January 8, 2013 Hi, folks! I'm almost sure i checked every single graphics kext inside my system but intel ones. The only one that has cpuids inside is NVDAResman.kext. Not only two, but dozens of them. Best regards! I'm only getting 2? otool -tv NVDAResman | grep cpuid 0000000000064f32 cpuid 000000000006cdc9 cpuid Link to comment Share on other sites More sharing options...
Shaneee Posted January 8, 2013 Share Posted January 8, 2013 Hmm just randomly got a KP... I had just installed nVidia retail drivers and patched the possible one with amd_insn_patcher and rebooted. Link to comment Share on other sites More sharing options...
spakk Posted January 8, 2013 Share Posted January 8, 2013 (edited) Hi Andy! one wonderful event today with my Phenom II X6, the mountain lion is now awakened from a deep sleep. It's not all right, I'm still working on the adjustments. I booted with the USB external IDE HDD, it is my Vanilla Mountain Lion, I used the latest kernel from you and accordingly the drivers for my hardware,see images. PS: Gils, many thanks for sending your good Information by E-Mail, now I can boot ML. Edit: The CPU is incorrectly listed but that is secondary, primary I have not graphics problems, I'm still doing install my graphics card drivers. The installation process takes almost in slow motion, the system is very slow. Once I wanted to restart the system, it depends on now: PCI Configuration begin although I boot with npci=0x2000 or npci=0x3000 boote Edited January 8, 2013 by spakk 1 Link to comment Share on other sites More sharing options...
theconnactic Posted January 8, 2013 Author Share Posted January 8, 2013 Way to go, spakk!! Can you get QE CI with your nVidia card? Link to comment Share on other sites More sharing options...
spakk Posted January 8, 2013 Share Posted January 8, 2013 (edited) Way to go, spakk!! Can you get QE CI with your nVidia card? I'll test as soon as I have resolved the problem with: PCI Configuration begin who can make suggestions how I can fix the problem-with .....PCI Configuration begin ? :wink2: Edited January 8, 2013 by spakk Link to comment Share on other sites More sharing options...
instant idiot Posted January 8, 2013 Share Posted January 8, 2013 PCI Configuration begin My motherboard needs the flag npci=0x3000. I've heard of PCI Configuration begin being solved by npci=0x2000, PCIRootUID=1, and PCIRootUID=0 as well. 1 Link to comment Share on other sites More sharing options...
pauℓzurrr. Posted January 8, 2013 Share Posted January 8, 2013 I'll test as soon as I have resolved the problem with: PCI Configuration begin who can make suggestions how I can fix the problem-with .....PCI Configuration begin ? :wink2: I needed these kext, since all the npci and pcirootuid methods didn't work for me... Link to comment Share on other sites More sharing options...
spakk Posted January 8, 2013 Share Posted January 8, 2013 I needed these kext, since all the npci and pcirootuid methods didn't work for me... it makes kernel panic with Mountain Lion 10.8.2 !!! Link to comment Share on other sites More sharing options...
Shaneee Posted January 8, 2013 Share Posted January 8, 2013 it makes kernel panic with Mountain Lion 10.8.2 !!! Roll back the IOPCIFamily kext from 10.8.0 Link to comment Share on other sites More sharing options...
Recommended Posts