Jump to content
theconnactic

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

6,477 posts in this topic

Recommended Posts

10.8.3: extensive tests

 

Screen Shot 2013-03-15 at 1.35.16 AM.png

 

Screen Shot 2013-03-15 at 2.24.35 AM.png

 

Screen Shot 2013-03-15 at 2.28.46 AM.png

 

Screen Shot 2013-03-15 at 2.26.07 AM.png

 

Screen Shot 2013-03-15 at 2.30.05 AM.png

 

Screen Shot 2013-03-15 at 2.30.21 AM.png

 

Screen Shot 2013-03-15 at 2.30.55 AM.png

 

Screen Shot 2013-03-15 at 2.31.41 AM.png

 

Screen Shot 2013-03-15 at 2.32.59 AM.png

 

Screen Shot 2013-03-15 at 2.33.21 AM.png

 

Screen Shot 2013-03-15 at 2.34.56 AM.png

 

Screen Shot 2013-03-15 at 2.35.06 AM.png

 

Screen Shot 2013-03-15 at 2.35.42 AM.png

 

Screen Shot 2013-03-15 at 2.36.22 AM.png

 

P.S.: All the programs of the Adobe CS6 suite were open at the same time. They took a while to load, but once open, all they worked without any glitch or lack of comparative performance against 10.7.5 or Windows 8.

 

10.8.3, the upsides: the archive utility bug (see the top of the page, where Sinetek answers to the post i describe it) went away. The amd_kernel (first post of the topic) works fine. No loss of performance (see topic Geekbench Scores).

 

10.8.3 the downsides: Safari remais unusable with the HD5450. VLC still cannot be reopened once closed, needing a reinstallation. The graphics are a bit more buggy: "phantoms" (persistent pixels) are left when a window is closed, but they can be erased by selecting the region affected, or shaking another window over it. Launchpad showed glitches once, but i wasn't able to reproduce it, so it should be an unfrequent glitch.

 

All in all, i recommend the update, as long your ATI graphics card is already working with 10.8.2.

 

P.S.: i might as well try to rollback the ATI kexts to the 10.8.2 ones to improve graphics stability. I'll test it, as soon as i back up my system.

Share this post


Link to post
Share on other sites
Advertisement

Hi Guys,

 

Let me pass on how I made the rarely known FirePro v4900 integrate and run with Snow Leopard on my FX-8350, Gigabyte GA-990FXA-UD5. I think it will be useful regardless of which OS X version. I used a couple different tools between lspci and System Info to make sure the Device ID (0x6749) and Vendor ID (0x1002) for the v4900 were consistent. Then upon noticing a set of ATI kernel extensions in S/L/E, I reviewed all ATI info.plist content for device and vendor id matches. I found one exact match within the ATIRadeonX3000 kext. I used a web site of listed PCI data and the Chameleon 2187 ati.c source code file to find the graphics family and other device ids in the same family. It turns out that the v4900 is part of the Turks family. Other video card models have different graphic families. Most importantly though, once you find the graphics family for the card you have, you may find that existing kexts already have yours and/or many of the graphics family members already present.

 

When reviewing all of the info.plist content via Show Package Contents (pop up menu in Finder) and navigating via Finder to Contents | info.plist, I happened to find the controller file listing Turks family members (not the v4900 though). Thinking that only two kexts would be enough, I booted up and expected graphics to magically work without forcing Graphics Mode. The screen was all blue, and I was pretty sure the desktop was hiding somewhere. With some more research, I found a couple posts implying that three items are needed for successful ATI graphics:

 

ATISupport.kext

A Controller kext

A Video Card kext (not sure what else to call it)

 

Anyhow, since I had determined which ATIController kext already uses other Turks family members, I added the v4900 to the IOPCIMatch key within the ATI6000Controller.kext. I doubt the order has any significance, since the listing was not ascending or descending. I did place it around other device ID values closest to the v4900 though. Keep in mind that an entry is

 

0xDeviceIDVendorID

 

The v4900 looks like: 0x67491002

 

After saving this change to the info.plist, updating the kernel caches and permissions with Kext Wizard (much faster than typing in Terminal), I rebooted without modifying any Chameleon 2.0, RC5 boot flags. After the gray apple screen was done, the screen went dark for about five seconds, then lo and behold, full graphics support appeared. After getting this to work, Graphics Mode and GraphicsEnabler values are ignored (possibly overridden).

 

I have been on the AMD OS X scene for a short time, so there may be something I am not aware of in Mountain Lion and Lion. As long as the more recent OS X releases do something similar with maintaining support for ATI video cards, there is a realistic chance that this will work. I suppose the most recently released ATI cards may not be so easily supported. So, your mileage may vary...

 

It looks odd on paper, but the kexts that are running the v4900 correctly are:

ATISupport.kext

ATI6000Controller.kext (only added the v4900 to the IOPCIMatch value set)

ATIRadeonX3000.kext

 

I can change the resolution just like on my MacBook Pro, modify refresh rate, run the screen saver, run the Grab application, etc. The connection is DVI dual link between the v4900 and my ancient Acer AL1917W monitor. I made no modifications to the DSDT. In fact only the default DSDT and smbios settings from the Chameleon 2 RC5 boot loader are in use at this time. Now that I have found the magic three lines to have a bootable USB via a cloned disk image boot successfully, I will be testing the more recent boot loader versions and determining upgrading to Mountain Lion.

Share this post


Link to post
Share on other sites

Hi guys,

 

I'm back again.

I see you did great progress on video distortion problems!

Have to test the aty_something and rd8111's way of getting rid of it.

When i have a new HDD, i'll try to join the development again :)

Might get a cheap ass HD5450 aswel :)

LETS GET FULL QE/CI and no distorion FOR ALL ATI (and Nvidea) CARDS !!!

Share this post


Link to post
Share on other sites

Hi!

 

Heavy graphic glitches with Safari, so i am using Chrome, which is absolutely fine. Other than that, no glitches at all, and only minor annoyances, like having to reinstall VLC every time i want to use it (but install VLC means copy it to the Applications folder, so there's no big deal). Games, movies and animations work just fine with absolutely no graphics corruption. Least but not last, i got my higher Geekbench2 score ever with this machine.

 

I am already using Mountain Lion as my primary system here. But i confess that, since is a HTPC, a computer for fun and content consumption, not for work, i cannot lightly recommend this for everyone.

 

The method i used for my graphics card will not necessarily work for yours. That said, i simply added the ID of my card to the info.plists of ATI5000Controller.kext, under IOPCIMatch, and also in AMDRadeonAccelerator, under cedar (the family of my card). I can boot with GE=Y or GE=N, but GE=N makes the system report my card as an AMD5000, not an AMD5450. With this method, only the default framebuffer, Eulemur, appears to work: all others will boot to a black screen.

 

All the best!

 

So is it worth it to fiddle around with the kext if everything is working fine minus graphic artifacts? I get artifcats using Chrome or Safari, with both being unusable for some sites. I see that in the iopcimatch, there's several device IDs, do I delete them all except mine? Thanks for your help!

Share this post


Link to post
Share on other sites

I don't think so, burkett375, and i think the biggest merit of rd811's method is getting the FirePro v4900 to work with OSX, not solving the graphics corruption bug related to kernel itself (which the method didn't do: the card simply appears not to experience it). I think that, if you already have QE/CI, your work with the kexts is done, and you will have to look elsewhere to solve this very annoying graphics corruption issue.

 

Rd811, i'll ask the staff to move your post to the Genius Bar as a tutorial: i'm pretty sure lots of FirePro users, regardless of being on Intel or AMD, can benefit of it.

 

All the best!

Share this post


Link to post
Share on other sites

I don't think so, burkett375, and i think the biggest merit of rd811's method is getting the FirePro v4900 to work with OSX, not solving the graphics corruption bug related to kernel itself (which the method didn't do: the card simply appears not to experience it). I think that, if you already have QE/CI, your work with the kexts is done, and you will have to look elsewhere to solve this very annoying graphics corruption issue.

 

Rd811, i'll ask the staff to move your post to the Genius Bar as a tutorial: i'm pretty sure lots of FirePro users, regardless of being on Intel or AMD, can benefit of it.

 

All the best!

 

Thank you, theconnactic. I think the approach will work for more than FirePro users. I found so many ATI graphic families that my head was spinning...

 

@burkett375, I would never remove already existing IDs from a kext. For a future hardware change (e.g. the latest video card with 10 GB Video RAM coming soon to a computer near you) the removal of valid IDs may be forgotten 2 years from now. Adding a DeviceIDVendorID to a kext that has other items in the same device family seems better. I have followed directions for replacing the contents within the VoodooHDA kext though, but that is specific to the "how to solve problems" FAQ the VoodooHDA team has out there. Besides, as long as you have backups via your preferred utility program, it is much much easier to try something and restore to a previous point if needed.

Share this post


Link to post
Share on other sites

Apple seem to be helping us out I think. Just updated to 10.8.3 and with no kext modifications yet I've booted without safe mode to desktop with buggy graphics and no QE/CI on my GT 430. Will keep you updated...

Share this post


Link to post
Share on other sites

Indeed, rd811: it could be a tutorial for any ATI user: could you rewrite your post in the form of a tutorial, so i can ask the staff to move it to the Genius Bar?

 

Sure. Do I post it here? I will look at a couple other tutorials and follow the format.

Share this post


Link to post
Share on other sites

At least you have AppleHDA audio, guys! I have to resort to VoodooHDA, and HDMI is yet a distant hope.

 

Now, to the news:

 

I can confirm the latest amd_kernel (which is attached in the first post of the topic) works with no performance loss and no errors with 10.8.3. Contrary to all common sense, i did the App Store update (but i recommend you use the combo update) and the only modifications i had to make was adding my card's ID in the plists of both ATI5000Controller.kext and AMDRadeonAccelerator.kext. I did this to the 10.8.3 stock kexts and all went fine, but i saved my 10.8.2 patched kexts just in case. That's what i recommend to you, fellow ATI users who have a stable system.

 

Best regards!

 

did you tried to test this:

http://www.osx86.net..._installer.html

and this

http://www.projectos...p?showtopic=355

Share this post


Link to post
Share on other sites

The following should be noted:

 

The information I receive via systeminfo do not match the specifications of Windows.

here has bgrau also confirmed again http://www.insanelym...gts-hdmi-sound/

I started everest ultimate edition and get other disclosures for my HDA controller (vendor-id and device-id) as the systeminfo tool.

Maybe that's the reason why we turn in the circle.?

 

can anyone confirm this?

Share this post


Link to post
Share on other sites

I managed to solve my problem with audio stuttering.

Only I put:

busratio = 15 fsb = 200

however, even though I put in org.chameleon.Boot, does not work.

Only works in typing boot.

I do not know if somebody already had this idea, how it happened in my case.

The problems of ATI and Nvidia, it would not be because of the wrong frequencies in the kernel?

Share this post


Link to post
Share on other sites

This is a historically common issue (busratio errors and sound corruption).

 

You need to delete the NVRAM plist inside your extra folder, then try again to edit your Chameleon plist and see if it works.

 

All the best!

Share this post


Link to post
Share on other sites

Open a topic here, and i'll ask the chief staff to move it to the Genius Bar.

 

Best regards!

 

Will do. I am reviewing it and making corrections right now. I will likely post a new topic later tonight (maybe Saturday morning).

 

Sincerely,

rd8111

Share this post


Link to post
Share on other sites

Apple still hasn't released the source to the kernel of 10.8.3.

 

So, kind community, tell me, the new Kexts are a no-go either?

No, as usual it takes about 2 weeks after the release of the binaries before the sources are released.

Share this post


Link to post
Share on other sites

I have DSDT injection for my 5850 following this tutorial

 

My system now recognizes 5800 series (Before 5000 only):

 

Kd2Rlet.png

 

This are my kexts:

 

izEkTmf.png

 

I dont have QE/QI. Do i Need AMDAccelerator.kext for get it?

Share this post


Link to post
Share on other sites

Yes, you do! In theory, the stock AMDAccelelrator.kext would do, since your card is expected to work OOB, but the AMD rig is the game changer (for worse) here.

 

But you're on the right path. Hope you get QE/CI. If instead of QE/CI you get heavy artifacts, that means your card is unusable with the current kernel, and you'll have to wait for a kernel fix (just like many nVidia owners whose cards should work OOB).

 

All the best!

 

Apple still hasn't released the source to the kernel of 10.8.3.

 

So, kind community, tell me, the new Kexts are a no-go either?

 

I didn't test with nVidia because i didn't have it in my AMD rig anymore. But for ATI, the new kexts are a bit more buggy instead of less, but i can be because i'm running 10.8.3 with Andy's 10.8.2 kernel.

 

By the way, hi, Andy: long time, no see!

Share this post


Link to post
Share on other sites

I will continue to modify the AppleHDA.kext and the DSDT, then I think that will work, see pic --->

 

http://www.workuploa...m/image/Ix2D7Ij

 

 

Graphics are very good! no graphical problems with my Nvidia GTX 550 TI 3 GB

:king:

 

Relevant problem lies in the adaptation of the AppleHDA.kext, DSDT and graphics drivers!

Share this post


Link to post
Share on other sites

videos unfortunately not run, I get this error message from quicktime: The document could not be opened. An unknown error occurred (-101) :wallbash:

Share this post


Link to post
Share on other sites

we need to work on the AppleHDA, Ethernet drivers and DSDT and graphics drivers, here are the sources of our problems with the graphics card !!! :wink2:

 

I have dispensed with this ML installation on the ethernet driver.! I do not installed :king:

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 shinho73
      Can someone help me fix reboot issue? Actually it reboots, but sometimes the hackintosh just hangs with screen off. Here is the Extra folder containing org.chameleon.boot.plist. https://drive.google.com/drive/folders/1MX8-DpQk9kaRUfjPcToxf-ElWh-bN6EY?usp=sharing  and the spec of the PC. https://drive.google.com/drive/folders/1NlcUNK5DBzJFxeFeuyt92eRjQqwO5T32?usp=sharing Can someone look at it? I might be doing something wrong. Any help will be greatly appreciated. Thank you. 

    • By shinho73
      I need a good vanilla guide for AMD A8 7600 with A58M-E FM2+ mother board and Palit GEforce GT 730. Any help will be greatly appreciated. Thank you.



    • By Coddyx
      Hi,
       
      I followed the AMD OSX Vanilla Guide and managed to successfully build my first hackingtosh.
      Everything works great EXCEPT for my MSI - Radeon RX 580 8 GB GAMING X.
      I ran some benchmarks (and tried World of Warcraft) and I am getting ~50% of the performance I am usually getting in Windows 10.
      Unigine Heaven reports ~950 vs 1750 in Windows and World of Warcraft runs @ 30 fps lowest settings vs 60 fps ultra settings in Windows.
       
      Here are the kexts I am using:
      AppleALC Lilu NullCPUPowerManagement RealtekRTL811 VirtualSMC WhateverGreen  
      I should mention that this is an AMD hackingtosh running on Ryzen 5 1600 3.2 GHz 6-Core Processor.
       
      I read and I completely understand that I should not expect 100% performance. But I believe a 50% drop is out of the ordinary.
       
      If anyone has ideas on what I could try to up the performance it would be greatly appreciated.
       
      Thank you!
       
       
    • By vlgngrbrdmn
      Hey all,
       
      This is my first time posting to this forum.
       
      Here is my problem: My main issue is random freezing of my display (i.e. cannot move my mouse) and nothing being displayed after my monitors go to sleep (i.e. lock my screen, wait a few minutes, try to move mouse/type on keyboard. My displays wake up but display "no signal"). I have to reboot in order to use my Hackintosh again.

      Another issue that I am experiencing is that, every time I reboot my system and login initially, my right and left vertical displays do not display correctly until I turn one of them off and back on again. It is kind of hard to describe what is wrong, but basically the dimensions of the display and the orientation (horizontal vs. vertical) is wrong, and my mouse does not display in the correct place on the screen.

      Either way, after some research it looks like this all may be due to my Framebuffer being incorrect. However, I am having a hard time trying to determine whether that is the case and, if so, how to fix it.

      I did manually try to add a Framebuffer ("Kamarang") into my config.plist below, however that did not seem to make a difference.

      Any help with this would be much appreciated! Also, please let me know if I should upload anymore information.

      Currently, My setup consists of 1 Dell U3415w and 2 Dell 2415 monitors in an "H" configuration (both 2415s setup vertically on either side of the U3415W).

      This is all being powered by a SAPPHIRE Radeon RX Vega 64 (https://www.newegg.com/Product/Product.aspx?Item=N82E16814202326) with each monitor plugged via a DisplayPort.

      I am currently running the latest version of macOS Mojave, 10.14.4.

      I am also using the latest version of the Clover boot loader (4920) with the following kexts located in kexts\Other:
      AppleALC.kext AtherosE2200Ethernet.kext Lilu.kext USBInjectAll.kext VegaTab_64.kext VirtualSMC.kext WhateverGreen.kext My config.plist file contains the following:
      ?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>#DisableDrivers</key> <array> <string>CsmVideoDxe</string> <string>VBoxExt4</string> </array> <key>ACPI</key> <dict> <key>DSDT</key> <dict> <key>Fixes</key> <dict> <key>FixHPET</key> <true/> <key>FixIPIC</key> <true/> <key>FixRTC</key> <true/> <key>FixShutdown</key> <true/> <key>FixTMR</key> <true/> </dict> <key>Patches</key> <array> <dict> <key>Comment</key> <string>change XHCI to XHC</string> <key>Disabled</key> <false/> <key>Find</key> <data> WEhDSQ== </data> <key>Replace</key> <data> WEhDXw== </data> </dict> <dict> <key>Comment</key> <string>change XHC1 to XHC</string> <key>Disabled</key> <false/> <key>Find</key> <data> WEhDMQ== </data> <key>Replace</key> <data> WEhDXw== </data> </dict> <dict> <key>Comment</key> <string>change SAT0 to SATA</string> <key>Disabled</key> <false/> <key>Find</key> <data> U0FUMA== </data> <key>Replace</key> <data> U0FUQQ== </data> </dict> </array> </dict> <key>DropTables</key> <array> <dict> <key>Signature</key> <string>DMAR</string> </dict> <dict> <key>Signature</key> <string>MATS</string> </dict> </array> <key>FixHeaders</key> <true/> <key>SSDT</key> <dict> <key>Generate</key> <dict> <key>PluginType</key> <true/> </dict> </dict> </dict> <key>Boot</key> <dict> <key>Arguments</key> <string>keepsyms=1 dart=0 debug=0x100 shikigva=40</string> <key>DefaultVolume</key> <string>LastBootedVolume</string> <key>Timeout</key> <integer>5</integer> </dict> <key>BootGraphics</key> <dict> <key>#DefaultBackgroundColor</key> <string>0xF0F0F0</string> <key>EFILoginHiDPI</key> <integer>1</integer> <key>UIScale</key> <integer>1</integer> </dict> <key>CPU</key> <dict> <key>#BusSpeedkHz</key> <integer>133330</integer> <key>#FrequencyMHz</key> <integer>3140</integer> <key>#HWPEnable</key> <true/> <key>#HWPValue</key> <string>0x30002a01</string> <key>#QPI</key> <integer>4800</integer> <key>#SavingMode</key> <integer>7</integer> <key>#TDP</key> <integer>95</integer> <key>#TurboDisable</key> <true/> <key>#Type</key> <string>0x0201</string> <key>#UseARTFrequency</key> <true/> </dict> <key>Devices</key> <dict> <key>Audio</key> <dict> <key>Inject</key> <integer>1</integer> <key>ResetHDA</key> <true/> </dict> <key>Properties</key> <dict> <key>PciRoot(0x0)/Pci(0x2,0x0)</key> <dict> <key>AAPL,ig-platform-id</key> <data> AAASGQ== </data> <key>framebuffer-patch-enable</key> <data> AQAAAA== </data> <key>framebuffer-stolenmem</key> <data> AAAwAQ== </data> </dict> </dict> <key>USB</key> <dict> <key>FixOwnership</key> <true/> </dict> </dict> <key>GUI</key> <dict> <key>Hide</key> <array> <string>PREBOOT</string> </array> <key>Scan</key> <dict> <key>Entries</key> <true/> <key>Linux</key> <true/> <key>Tool</key> <true/> </dict> </dict> <key>Graphics</key> <dict> <key>FBName</key> <string>Kamarang</string> <key>Inject</key> <dict> <key>ATI</key> <false/> <key>Intel</key> <false/> <key>NVidia</key> <false/> </dict> <key>RadeonDeInit</key> <true/> </dict> <key>KernelAndKextPatches</key> <dict> <key>KernelPm</key> <true/> <key>KextsToPatch</key> <array> <dict> <key>Comment</key> <string>Port limit increase</string> <key>Disabled</key> <false/> <key>Find</key> <data> g710////EA== </data> <key>InfoPlistPatch</key> <false/> <key>MatchOS</key> <string>10.12.x</string> <key>Name</key> <string>com.apple.driver.usb.AppleUSBXHCI</string> <key>Replace</key> <data> g710////Gw== </data> </dict> <dict> <key>Comment</key> <string>Port limit increase (RehabMan)</string> <key>Disabled</key> <false/> <key>Find</key> <data> g32IDw+DpwQAAA== </data> <key>InfoPlistPatch</key> <false/> <key>MatchOS</key> <string>10.13.x</string> <key>Name</key> <string>com.apple.driver.usb.AppleUSBXHCI</string> <key>Replace</key> <data> g32ID5CQkJCQkA== </data> </dict> <dict> <key>Comment</key> <string>Port limit increase (PMHeart)</string> <key>Disabled</key> <true/> <key>Find</key> <data> g/sPD4MDBQAA </data> <key>InfoPlistPatch</key> <false/> <key>MatchOS</key> <string>10.14.0</string> <key>Name</key> <string>com.apple.driver.usb.AppleUSBXHCI</string> <key>Replace</key> <data> g/sPkJCQkJCQ </data> </dict> <dict> <key>Comment</key> <string>Port limit increase (Ricky)</string> <key>Disabled</key> <false/> <key>Find</key> <data> g/sPD4OPBAAA </data> <key>InfoPlistPatch</key> <false/> <key>MatchOS</key> <string>10.14.x</string> <key>Name</key> <string>com.apple.driver.usb.AppleUSBXHCI</string> <key>Replace</key> <data> g/sPkJCQkJCQ </data> </dict> <dict> <key>Comment</key> <string>External Icons Patch</string> <key>Disabled</key> <false/> <key>Find</key> <data> RXh0ZXJuYWw= </data> <key>InfoPlistPatch</key> <false/> <key>Name</key> <string>AppleAHCIPort</string> <key>Replace</key> <data> SW50ZXJuYWw= </data> </dict> </array> </dict> <key>RtVariables</key> <dict> <key>BooterConfig</key> <string>0x28</string> <key>CsrActiveConfig</key> <string>0x67</string> <key>MLB</key> <string>C02601270QXGPF7FB</string> <key>ROM</key> <string>UseMacAddr0</string> </dict> <key>SMBIOS</key> <dict> <key>BoardSerialNumber</key> <string>C02601270QXGPF7FB</string> <key>ProductName</key> <string>iMac17,1</string> <key>SerialNumber</key> <string>C02R2HZDGG7L</string> <key>SmUUID</key> <string>91E0E343-A938-4117-BBC7-234EA3ED265E</string> </dict> <key>SystemParameters</key> <dict> <key>InjectKexts</key> <string>Yes</string> <key>InjectSystemID</key> <true/> </dict> </dict> </plist> Also, for what it is worth, sleep is disabled on my system:

      Again, thank you all for taking time out of your day to help a fellow hackintosher out!
×