Jump to content
theconnactic

Mavericks kernel testing on AMD (formerly Mountain Lion kernel testing on AMD)

6,477 posts in this topic

Recommended Posts

nvidia, maybe others channel exceptions ...

 

10.9.4 Confirmed working here on a fx-8350.

 

The combo pack from apple from apple was used to update. I didn't use the app store, but I don't believe it makes any difference. 

 

I booted to single user and safe mode and replaced AppleACPIPlatform.kext, IOPCIFamily.kext, System.kext, AppleMatch.kext, and Sandbox.kext with the ones from my previous working 10.9.3 install. 

 

I am using bronya's kernel (thank you bronya :) ) mach_10.9.2_rc7_fixed.zip. I am using the fx kernel. 

 

The -f boot flag was needed because it was booting using the apple mach kernel.

 

I also have an asus bt 4.0 dongle. I had previously changed the product id and vendor id in the broadcom plugin of the IOBluetoothFamily.kext. Apple must have updated this for 10.9.4 because I had to add the ids back to the plugin kext.

 

Things seem faster, but I did switch from a nov 2013 bronya kernel to the one mentioned above.

 

Hi all,

 

I apologize if this is the wrong forum for this and would appreciate appropriate advice.

 

Using AMD kernels for a long time AMD kernel developers deserve my deep respect and I want to pay something back.

 

I have lost QE/CI since 10.9.2 and found replacing IOPCIFamily.kext and AppleACPIPlatform.kext to be the cure. I was digging deeper and realized following facts:

- it is not kernel related

- nvidia has changed default interrupt mode to msi in the past
- apple has changed msi interrupt base from 0x90 to 0x70 in IOPCIFamily-224 (used in 10.9.2) in 10.9.1 it was 0x90

- my rig reports

03.07.14 21:05:18,000 kernel[0]: IOAPIC: Version 0x21 Vectors 88:119
03.07.14 21:05:18,000 kernel[0]: IOAPIC: Version 0x21 Vectors 64:87

  So IOAPIC vectors cover a range from 0x40 to 0x78 overlapping the new msi basevalue.

- modifying IOPCIFamily-224 (after release of code) to the old value revealed that QE/CI came back in a almost vanilla OSX 10.9.2

 

Attached is a patch and a binary version of IOPCIFamily.kext. I introduced a boot argument 'msibase=0xAB' to it. This kext let me do all updates from 10.9.1 to 10.9.4 with retaining QE/CI just replacing it and nothing else. It expects a parameter as in 'msibase=0x90' (the value I use) specifying the value the base vector should take. A value of 0x00 effectively disables the use of message based interrupts.

 

If someone would confirm my facts, I would be glad. Otherwise try to just forget this post or delete it by an administrator.

 

Please excuse me, if this post is misplaced and is of no interest to anyone.

 

best regards

 

 

IOPCIFamily.zip

Share this post


Link to post
Share on other sites
Advertisement

Hi axamanA,

many thanks for your work on this drivers, as soon as I see an opportunity to work on my hackintosh, I will test their work and report my results.

Every good work is welcome here..many thx.

Share this post


Link to post
Share on other sites

Beauty.... You guys are amazing :wub: , I was wondering about that. It didn't seem like it was kernel related at all :)

Share this post


Link to post
Share on other sites
Hi !

I found one really odd !!! 

1) If original mach_kernel from apple_dvd_10.8.5 - works icloud , imessage on  CPU INTEL iMac  !

2) if download original xnu-2050.48.1.tar and extract , then immediately compile , and copy mach_kernel from xnu-2050.48.1.tar in system . Then reboot and start system 10.8.5 with new mach_kernel , and i tried Icloud and imessage - don't working !!!!!!

3 ) i back original to mach_kernel and try run icloud - works !!!

 

WHY don't works iMessage and iCloud , if  use mach_kernel from compilation xnu-2050.48.1.tar ???? 

Who know ? ))))

Share this post


Link to post
Share on other sites

it is a known problem. Facetime, icloud, imessages, etc. won't work with the open source kernel. The only way these could work on AMD machines would be if the diffs were binary patches for the original apple kernel.

Share this post


Link to post
Share on other sites

it is a known problem. Facetime, icloud, imessages, etc. won't work with the open source kernel. The only way these could work on AMD machines would be if the diffs were binary patches for the original apple kernel.

you're telling a developer of the kernel...

 

anyway updated without rolling back anything, as others said.

 

But Bronya, my clock is running a bit fast with your rc7 kernel fix, but not much, it amounts to about 8 minutes ahead per 24 hours. so no biggie but it didnt happen with your rc6/7 kernel. I cant rollback to them because if I boot with any of those I get blue launchpad icons.

Share this post


Link to post
Share on other sites

Many thanks axmanA! I can too confirm that it fixed the QE/CI issue I was experiencing on my Precsion 670 with nVidia GeForce 9800GT. I was experiencing very serious lagging despite apparent full QE/CI but after applying your patched IOPCIFamily.kext (I found I had to replace the vanilla kext in /S/L/E), the lagging disappeared! I did not replace the AppleACPIPlatform kext. Is boot option msibase=0x90 valid and necessary?

 

A big Thank you for your thorough analysis and fix.  :thumbsup_anim:

 

My old girl is now running 10.9.4 very smoothly. I've also reverted to IOPCIFamily + AppleACPIPlatform kexts from 10.9.1 and obtained exact same results. So, graphics issues were all down to these particular driver changes on my old system. 'really chuffed it's finally sorted and updated to 10.9.4.

Share this post


Link to post
Share on other sites

 

Hi !
I found one really odd !!! 
1) If original mach_kernel from apple_dvd_10.8.5 - works icloud , imessage on  CPU INTEL iMac  !
2) if download original xnu-2050.48.1.tar and extract , then immediately compile , and copy mach_kernel from xnu-2050.48.1.tar in system . Then reboot and start system 10.8.5 with new mach_kernel , and i tried Icloud and imessage - don't working !!!!!!
3 ) i back original to mach_kernel and try run icloud - works !!!
 
WHY don't works iMessage and iCloud , if  use mach_kernel from compilation xnu-2050.48.1.tar ???? 
Who know ? ))))

 

Bronya, try to make hex diff , may be we found way to bypass icloud verification

Share this post


Link to post
Share on other sites

Bronzovka, this is old subject.

 

I think it was Master Chief - but correct me if I'm wrong - who discovered it: no compiled kernel supports any of Apple's cloud services. The reason is Apple doesn't feel obligated to make the related sources available under the open source license it follows. So what we've got is kind of a barebones kernel: it will boot the OS, but nothing beyond that. That's also why binary-patched kernels or the vanilla kernel when patched-on-the-fly (that is, by the boot loader) fully work with these Cloud services. The only way we have support for all of them is somehow implement the AMD-specific changes via binary patch. I know, it's no easy feat, that's why nobody even tried.

 

All the best!

Share this post


Link to post
Share on other sites

where I can download mach_10.9_3_rc7_fixed.zip. Link is dead. Thanks in advance.

Look under downloads or register to root86.com

Here is the download link: http://www.root86.com/files/file/469-mach-10-9-2-bronya-rc7-fixed/

Share this post


Link to post
Share on other sites

After 10.9.4 I have this KP after every second/third boot.

Any idea how can I avoid it?

 

bronya rc7 fixed kernel

 

B7KETGP.jpg

delete AppleTyMCEDriver.kext

Share this post


Link to post
Share on other sites

After 10.9.4 I have this KP after every second/third boot.

Any idea how can I avoid it?

 

bronya rc7 fixed kernel

 

 

Hi ! MacPro5.1 don't support AppleTyMCEDriver.kext , you need change to other model ;)

Share this post


Link to post
Share on other sites

The best thing to do is to actually remove that kext. It often causes issues on Hackintoshes machines and it's not mandatory.

Share this post


Link to post
Share on other sites

nvidia, maybe others channel exceptions ...

 

 

Hi all,

 

I apologize if this is the wrong forum for this and would appreciate appropriate advice.

 

Using AMD kernels for a long time AMD kernel developers deserve my deep respect and I want to pay something back.

 

I have lost QE/CI since 10.9.2 and found replacing IOPCIFamily.kext and AppleACPIPlatform.kext to be the cure. I was digging deeper and realized following facts:

- it is not kernel related

- nvidia has changed default interrupt mode to msi in the past

- apple has changed msi interrupt base from 0x90 to 0x70 in IOPCIFamily-224 (used in 10.9.2) in 10.9.1 it was 0x90

- my rig reports

03.07.14 21:05:18,000 kernel[0]: IOAPIC: Version 0x21 Vectors 88:119
03.07.14 21:05:18,000 kernel[0]: IOAPIC: Version 0x21 Vectors 64:87

  So IOAPIC vectors cover a range from 0x40 to 0x78 overlapping the new msi basevalue.

- modifying IOPCIFamily-224 (after release of code) to the old value revealed that QE/CI came back in a almost vanilla OSX 10.9.2

 

Attached is a patch and a binary version of IOPCIFamily.kext. I introduced a boot argument 'msibase=0xAB' to it. This kext let me do all updates from 10.9.1 to 10.9.4 with retaining QE/CI just replacing it and nothing else. It expects a parameter as in 'msibase=0x90' (the value I use) specifying the value the base vector should take. A value of 0x00 effectively disables the use of message based interrupts.

 

If someone would confirm my facts, I would be glad. Otherwise try to just forget this post or delete it by an administrator.

 

Please excuse me, if this post is misplaced and is of no interest to anyone.

 

best regards

 

thanks  now my AMD PC works fine :D

can this edit done through binary patch for future releases  ?

Share this post


Link to post
Share on other sites

I update to 9.4 and try both RC6 and RC7 kernels, but same problem persist.

Machine boots fine but on login screen is all sluggish and slow and machine need 10 - 15 seconds to accept password and after that drop me again to login screen. I try with IOPCIFamily.kext but without results.

Have anyone any idea how to resolve that problem?

 

P.S. Same problem was with 9.3 update

Share this post


Link to post
Share on other sites

I update to 9.4 and try both RC6 and RC7 kernels, but same problem persist.

Machine boots fine but on login screen is all sluggish and slow and machine need 10 - 15 seconds to accept password and after that drop me again to login screen. I try with IOPCIFamily.kext but without results.

Have anyone any idea how to resolve that problem?

 

P.S. Same problem was with 9.3 update

Try to paste VoodooTSCSync for AMD, maybe that will help

Share this post


Link to post
Share on other sites

Hi Mohamed,

 

this exceeds my capabilities :-(

hi axmanA :)

 

don't know if this idea will help

 

we can compile vanilla code  of iopcifamily 

once with

kBaseMessagedInterruptVectors = 0x70,

and anther compile with

kBaseMessagedInterruptVectors = 0x90,

 

and after compiling  of this two kexts

take ipcifamily binary file 

and open them with hex edit and copy hex code of this binary to two separate text file

then compare them using file merge on Xcode 

this will show us diff when using 70 or 90 

then we use this diff trough fly patch on clover :)

 

hope this will work

can't test this as vanilla ipcifamily code doesn't compile  directly :/

Share this post


Link to post
Share on other sites

Hello everyone, i just joined hackintoshing and would like to know if any of these mavericks kernels would work on AMD E2-2000 APU processor and suppor QE/CI on Radeon HD 7340 GPU. Thanks in advance!

Share this post


Link to post
Share on other sites

Confirming that the 10.9.4 with AppStore update works great. There is no problems at all with update and the system is much faster than 10.9.3.

Bronya RC7_kernel here ;)

Hello everyone, i just joined hackintoshing and would like to know if any of these mavericks kernels would work on AMD E2-2000 APU processor and suppor QE/CI on Radeon HD 7340 GPU. Thanks in advance!

The best option is to try dude :) GPU's QE/CI is nothing to do with the kernels. Search on google and install your Mavericks and you will know :) Good Luck :)

Share this post


Link to post
Share on other sites

Give it a try, you'll soon find out. Kernels will have little if not nothing to do with QE/CI support with Radeon HD 7340 graphics card.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By karthiksh1989
      can somebody walkthrough with the mojave installation guide?
      i have a mac high sierra 13.6 version on my macbook pro and want to install mojave on my desktop
      Exact config is Gigabyte gaming wifi 7 motherboard amy ryzen 7 2nd gen 2700X processor Gigabyte G1 8GB grapgic card VEGA 64
      running 2 nvme Samsung 256gb cards and 1 intel 180gb ssd internal and 1tb WD HDD, with 64 GB 3200Mhz Ram
       
      https://wa.me/919611736534 (whatsapp)
    • By Fede1132
      Hi guys i have a problem install macOs Mojave on my PC, I have this configuration:

      CPU: Ryzen 7 2700X;
      GPU1: GTX 970 Strix(For game rendering and 144Hz Monitor);
      GPU2: GTX 750ti Strix(For 2nd monitor rendering to get 100% performances from 1st 144Hz Monitor);
      MotherBoard: MSI x470 GAMING PLUS
      Hard Disk 1 (Windows 10): Samsung EVO M.2;
      Hard Disk 2 (For Storage): RAID (1) between two hard disks;
      Hard Disk 3 (For Mojave): Kingston SSD 120GB;

      I have created my USB with this:
       
      Create Bootable USB Code: sudo /Applications/Install\ macOS\ Mojave.app/Contents/Resources/createinstallmedia --volume /Volumes/USB -- /Applications/Install\ macOS\ Mojave.app -- nointeract && say Done. Clover Settings: Boot: Verbose; dart=0; nv_disable=0; kext-dev-mode=1; GraphicsEnabler=No; XMPDetection = No. Cpu: C6. Devices: (Not Enabled = [ ] - Enabled = [-] - Full Enabled [✓]) Inject (Full Enabled); Add ClockID (Full Enabled); FixOwnership (Full Enabled); Gui: (Not Enabled = [ ] - Enabled = [-] - Full Enabled [✓]) Enabled (Full Enabled); Screen Resolution: 1920x1080; Kernel and Kext Patches: (Not Enabled = [ ] - Enabled = [-] - Full Enabled [✓]) Apple RTC (Full Enabled); KernelPm (Full Enabled); SMBIOS: iMac(18,3); System Parameters: Inject Kexts = Yes; Inject System ID; Used Kexts: FakeSMC FakePCIID NVIDIA WEB LILU BIOS: VT-d = Disabled; XHCI Hand-Off = Enabled; Legacy USB Support: Enabled; Hard Disk: AHCI Mode; Selection Mode: Legacy + EUFI; Clover Install Log:
      Full Error Log:
       
    • By tokia
      Hello,
       
      My desktop Hackintosh is running macOS Mojave 10.14.2 with two dedicated GPUs installed: NVIDIA GTX 1080 Ti, AMD Radeon HD 7970.
       
      The AMD GPU is used primarily under macOS and the NVIDIA one under Windows.
       
      macOS boots without issues as long as there are no displays connected to the NVIDIA GPU. If a display is connected then the display connected to the AMD GPU will become blank. The system can be accessed using Screen Sharing/VNC.
       
      There are no problems if I swap PCI-e slots for the GPUs so that the AMD GPU is in the first slot (primary GPU), but I prefer not to do this.
       
      I have tried to remove the whole PCI (bridge) device in the DSDT file and all the lines that refer to it. The PCI entries in ioreg and System Information are gone but System Information still shows an NVIDIA GPU under Graphics/Display.
       
      Many of the suggestions I have found in guides and forum posts do not seem to apply here. My problem with some of the guides and answers is that they give the solution without explaining how anything works, or they tell you what to do without explaining the reasons behind it.
       
      What else can I do? Thank you for any assistance you can provide!
       
      I have attached some files that may help you help me.
       
      DSDT_BIOS_3101.zip contains the original ACPI (*.aml) files without any patches.
      Send me Steffens-iMac.zip is a file produced by RunMe.app, and do contain simple patches to rename some devices.
      DSDT.dsl.patch is a diff of the original DSDT.dsl file and the one with the PCI devices removed (commented out).
       
      Motherboard: ASUS Rampage V Extreme (X99), BIOS version 3101 (macOS does not boot with anything newer).
      Clover version: 4813.
       
      DSDT.dsl.patch:
      --- /Users/sl/Desktop/DSDT_BIOS_3101/DSDT.dsl 2018-12-17 05:24:30.000000000 +0100 +++ /Volumes/EFI/EFI/CLOVER/ACPI/patched/DSDT.dsl 2018-12-17 16:52:08.000000000 +0100 @@ -5,7 +5,7 @@ * * Disassembling to symbolic ASL+ operators * - * Disassembly of DSDT.aml, Mon Dec 17 05:24:30 2018 + * Disassembly of DSDT.aml, Mon Dec 17 04:01:52 2018 * * Original Table Header: * Signature "DSDT" @@ -2128,7 +2128,7 @@ ^^PCI0.BR2B.OSHP () ^^PCI0.BR2C.OSHP () ^^PCI0.BR2D.OSHP () - ^^PCI0.BR3A.OSHP () + //^^PCI0.BR3A.OSHP () ^^PCI0.BR3B.OSHP () ^^PCI0.BR3C.OSHP () ^^PCI0.BR3D.OSHP () @@ -2274,7 +2274,7 @@ ^^PCI0.BR2B.OSHP () ^^PCI0.BR2C.OSHP () ^^PCI0.BR2D.OSHP () - ^^PCI0.BR3A.OSHP () + //^^PCI0.BR3A.OSHP () ^^PCI0.BR3B.OSHP () ^^PCI0.BR3C.OSHP () ^^PCI0.BR3D.OSHP () @@ -2420,7 +2420,7 @@ ^^PCI0.BR2B.OSHP () ^^PCI0.BR2C.OSHP () ^^PCI0.BR2D.OSHP () - ^^PCI0.BR3A.OSHP () + //^^PCI0.BR3A.OSHP () ^^PCI0.BR3B.OSHP () ^^PCI0.BR3C.OSHP () ^^PCI0.BR3D.OSHP () @@ -2570,7 +2570,7 @@ ^^PCI0.BR2B.OSHP () ^^PCI0.BR2C.OSHP () ^^PCI0.BR2D.OSHP () - ^^PCI0.BR3A.OSHP () + //^^PCI0.BR3A.OSHP () ^^PCI0.BR3B.OSHP () ^^PCI0.BR3C.OSHP () ^^PCI0.BR3D.OSHP () @@ -2803,12 +2803,14 @@ If ((CSTA (Arg0, Arg1) == 0x00)) { FLAG = 0x00 - PRID (APID = 0xFF) = 0xFF + APID = 0xFF + PRID = 0xFF } Else { Local0 = APID - PRID (FLAG = 0x01) = Local0 + FLAG = 0x01 + PRID = Local0 } Return (APIC) @@ -15259,7 +15261,7 @@ ^BR2B.OSHP () ^BR2C.OSHP () ^BR2D.OSHP () - ^BR3A.OSHP () + //^BR3A.OSHP () ^BR3B.OSHP () ^BR3C.OSHP () ^BR3D.OSHP () @@ -26861,7 +26863,7 @@ } } - Device (BR3A) + /*Device (BR3A) { Name (_ADR, 0x00030000) // _ADR: Address OperationRegion (MCTL, SystemMemory, 0xE0013188, 0x04) @@ -27496,7 +27498,7 @@ { Name (_ADR, 0xFFFF) // _ADR: Address } - } + }*/ Device (BR3B) { @@ -30267,7 +30269,7 @@ ^^PCI0.BR2B.OSHP () ^^PCI0.BR2C.OSHP () ^^PCI0.BR2D.OSHP () - ^^PCI0.BR3A.OSHP () + //^^PCI0.BR3A.OSHP () ^^PCI0.BR3B.OSHP () ^^PCI0.BR3C.OSHP () ^^PCI0.BR3D.OSHP () @@ -30567,21 +30569,21 @@ WordIO (ResourceProducer, MinFixed, MaxFixed, PosDecode, EntireRange, 0x0000, // Granularity 0x4158, // Range Minimum - 0x0000, // Range Maximum + 0x4158, // Range Maximum 0x0000, // Translation Offset 0x0001, // Length ,, , TypeStatic, DenseTranslation) WordIO (ResourceProducer, MinFixed, MaxFixed, PosDecode, EntireRange, 0x0000, // Granularity 0x5758, // Range Minimum - 0x0000, // Range Maximum + 0x5758, // Range Maximum 0x0000, // Translation Offset 0x0000, // Length ,, , TypeStatic, DenseTranslation) WordIO (ResourceProducer, MinFixed, MaxFixed, PosDecode, EntireRange, 0x0000, // Granularity 0x5858, // Range Minimum - 0x0000, // Range Maximum + 0x5858, // Range Maximum 0x0000, // Translation Offset 0x0000, // Length ,, , TypeStatic, DenseTranslation) @@ -37604,7 +37606,7 @@ ^^PCI0.BR2B.OSHP () ^^PCI0.BR2C.OSHP () ^^PCI0.BR2D.OSHP () - ^^PCI0.BR3A.OSHP () + //^^PCI0.BR3A.OSHP () ^^PCI0.BR3B.OSHP () ^^PCI0.BR3C.OSHP () ^^PCI0.BR3D.OSHP () @@ -37904,21 +37906,21 @@ WordIO (ResourceProducer, MinFixed, MaxFixed, PosDecode, EntireRange, 0x0000, // Granularity 0x4558, // Range Minimum - 0x0000, // Range Maximum + 0x4558, // Range Maximum 0x0000, // Translation Offset 0x0001, // Length ,, , TypeStatic, DenseTranslation) WordIO (ResourceProducer, MinFixed, MaxFixed, PosDecode, EntireRange, 0x0000, // Granularity 0x4259, // Range Minimum - 0x0000, // Range Maximum + 0x4259, // Range Maximum 0x0000, // Translation Offset 0x0000, // Length ,, , TypeStatic, DenseTranslation) WordIO (ResourceProducer, MinFixed, MaxFixed, PosDecode, EntireRange, 0x0000, // Granularity 0x4359, // Range Minimum - 0x0000, // Range Maximum + 0x4359, // Range Maximum 0x0000, // Translation Offset 0x0000, // Length ,, , TypeStatic, DenseTranslation) @@ -44941,7 +44943,7 @@ ^^PCI0.BR2B.OSHP () ^^PCI0.BR2C.OSHP () ^^PCI0.BR2D.OSHP () - ^^PCI0.BR3A.OSHP () + //^^PCI0.BR3A.OSHP () ^^PCI0.BR3B.OSHP () ^^PCI0.BR3C.OSHP () ^^PCI0.BR3D.OSHP () @@ -45241,21 +45243,21 @@ WordIO (ResourceProducer, MinFixed, MaxFixed, PosDecode, EntireRange, 0x0000, // Granularity 0x4958, // Range Minimum - 0x0000, // Range Maximum + 0x4958, // Range Maximum 0x0000, // Translation Offset 0x0001, // Length ,, , TypeStatic, DenseTranslation) WordIO (ResourceProducer, MinFixed, MaxFixed, PosDecode, EntireRange, 0x0000, // Granularity 0x4559, // Range Minimum - 0x0000, // Range Maximum + 0x4559, // Range Maximum 0x0000, // Translation Offset 0x0000, // Length ,, , TypeStatic, DenseTranslation) WordIO (ResourceProducer, MinFixed, MaxFixed, PosDecode, EntireRange, 0x0000, // Granularity 0x4659, // Range Minimum - 0x0000, // Range Maximum + 0x4659, // Range Maximum 0x0000, // Translation Offset 0x0000, // Length ,, , TypeStatic, DenseTranslation) @@ -53823,7 +53825,7 @@ Notify (\_SB.PCI0.BR2D.H007, Local0) } - If ((\_SB.PCI0.BR3A.PMEP == 0x01)) + /*If ((\_SB.PCI0.BR3A.PMEP == 0x01)) { Local0 = \_SB.PCI0.BR3A.PMEH (0x05) } @@ -53848,7 +53850,7 @@ Notify (\_SB.PCI0.BR3A.H005, Local0) Notify (\_SB.PCI0.BR3A.H006, Local0) Notify (\_SB.PCI0.BR3A.H007, Local0) - } + }*/ If ((\_SB.PCI0.BR3B.PMEP == 0x01)) { @@ -54608,11 +54610,11 @@ \_SB.PCI0.BR2D.PMEP = 0x01 } - If ((Local1 == 0x07)) + /*If ((Local1 == 0x07)) { \_SB.PCI0.BR3A.PMES = 0x01 \_SB.PCI0.BR3A.PMEP = 0x01 - } + }*/ If ((Local1 == 0x08)) { @@ -54879,10 +54881,10 @@ Notify (\_SB.PCI0.BR2D, 0x02) } - If ((\_SB.PCI0.BR3A.DEVS () != 0x00)) + /*If ((\_SB.PCI0.BR3A.DEVS () != 0x00)) { Notify (\_SB.PCI0.BR3A, 0x02) - } + }*/ If ((\_SB.PCI0.BR3B.DEVS () != 0x00)) { @@ -55927,10 +55929,10 @@ { Notify (\_SB.PCI0.BR2D, 0x00) } - Case (0x28) + /*Case (0x28) { Notify (\_SB.PCI0.BR3A, 0x00) - } + }*/ Case (0x29) { Notify (\_SB.PCI0.BR3B, 0x00) @@ -56736,11 +56738,11 @@ } } - Scope (_SB.PCI0.BR3A) + /*Scope (_SB.PCI0.BR3A) { Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { - If ((Arg0 == ToUUID ("e5c937d0-3553-4d7a-9117-ea4d19c3434d") /* Device Labeling Interface */)) + If ((Arg0 == ToUUID ("e5c937d0-3553-4d7a-9117-ea4d19c3434d") / * Device Labeling Interface * /)) { If (((Arg1 == 0x02) && (Arg2 == 0x00))) { @@ -56765,7 +56767,7 @@ 0x00 }) } - } + }*/ Scope (_SB.PCI1.QR1A) {  
      DSDT_BIOS_3101.zip
      Send me Steffens-iMac.zip
      DSDT.dsl.patch
    • By twikoffin
      Hello. My hardware is:
      AMD Athlon X2 7750 dual-core
      Gigabyte NVIDIA 8400GS 512MB ( [VGA] ,HDMI,DVI)
      Motherboard Gigabyte based on NFORCE without AHCI support (only IDE)
      I have successfully installed Mac OS Yosemite, Mavericks and El Capitan with AppleNFORCEATA.kext
      But I can't use it with Mac OS 10.8, don't know why, it just gives error and my internal HDD's are not appearing in Disk Utility.

       
         
×