duraaraa Posted June 25, 2014 Share Posted June 25, 2014 I tried with these drivers. I can get a white/gray screen with a mouse cursor on the external monitor (displayport). The mouse cursor will move. However, the login screen does not show up. It also seems like there should be two displays plugged in, as I can move the mouse far to the right of the first monitor, but no second monitor seems to be working. Any suggestion how to continue? I can find that without a doubt the problem is the framebuffer, so I will need to work on making a good one. Link to comment Share on other sites More sharing options...
duraaraa Posted June 25, 2014 Share Posted June 25, 2014 Ok, I got the card working with some caveats. Note that this is all on OS X 10.10 Yosemite, because Mavericks does not have the new AMD8000Controller kext to support Bonaire. I needed to patch the Baladi fb, obviously not the best choice for a laptop with nothing but display port outputs, but it was possible, eventually. With this patch, I can use the internal screen with absolutely no trouble, sometimes. Other times, it will boot to a gray screen. I need to boot again and again until it will work, at which point it works perfectly with CI QE and all that. My clover patch: <key>ATIConnectorsData</key> <string>000400000403000000010300120403030004000004030000000101001102010100040000040300000001020021030202000400000403000000010400220504040004000004030000000105001000050500040000040300000001060020010606</string> <key>ATIConnectorsPatch</key> <string>020000004000000009090100100600050003000004030000000101001102010100040000040300000001020021030202000400000403000000010400220503031000000004030000000105001000040800040000040300000001060020010506</string> You may notice that I passed a very odd value for the encoder, 6, which according to documentation doesn't exist. Me trying this is the only thing that allowed my screen to have proper colors without any screen tearing. No idea why, but it works. Here is where I have issues: 1. I cannot use more than one display at a time. I can set up the frame buffer so I can use an external display port monitor. However, if I plug in a display port monitor while using the internal screen, it freezes. Apparently this is a limitation of OS X's support for newer AMD cards. If anyone knows a way to support multiple monitors, my docking station and I will thank you profusely! 2. Sometimes I cannot get graphics working and it stalls at a gray screen. I'm pretty sure this has something to do with issue #1, though. 3. Sleep works, but resume doesn't. I have yet to patch my DSDT, so this could be why. 4. I haven't been able to recreate my success in Mavericks yet, but I will try later. Anyway, I think I might be the first person to get a Saturn XT card working, so I'm kind of happy. But if someone can improve this situation, I'll be happier! Link to comment Share on other sites More sharing options...
alexanderq Posted June 25, 2014 Share Posted June 25, 2014 Hello I have Radeon 6450 and with 10.7.x 10.8.x it was working ok but with the latest 10.9.x i allways have a ghost screen in taskbar but when i pressed it with mouse it diapears. I have triesd many variation with patching but same thing,here are my specs ATOM BIOS Rom: SubsystemVendorID: 0x174b SubsystemID: 0xe199 IOBaseAddress: 0x0000 Filename: 199P04S5.H01 BIOS Bootup Message:AMD HD6450 128MX16 2G PCI ID: 1002:6779Connector at index 0 Type [@offset 44542]: HDMI-A (11) Encoder [@offset 44546]: INTERNAL_UNIPHY1 (0x20) i2cid [@offset 44616]: 0x93, OSX senseid: 0x4Connector at index 1 Type [@offset 44552]: DVI-D (3) Encoder [@offset 44556]: INTERNAL_UNIPHY (0x1e) i2cid [@offset 44643]: 0x91, OSX senseid: 0x2Connector at index 2 Type [@offset 44562]: VGA (1) Encoder [@offset 44566]: INTERNAL_KLDSCP_DAC1 (0x15) i2cid [@offset 44670]: 0x90, OSX senseid: 0x1 <key>Graphics</key> <dict> <key>FBName</key> <string>Ipomoea</string> <key>VideoPorts</key> <integer>3</integer> </dict> <key>KernelAndKextPatches</key> <dict> <key>ATIConnectorsController</key> <string>6000</string> <key>ATIConnectorsData</key> <string>000400000403000000010000120401050008000004020000000100001102040310000000100000000001000000000002</string> <key>ATIConnectorsPatch</key> <string>040000001402000000010000100001020008000004020000000100002103040410000000100000000001000000100001</string> In latest versions i cant use ati injection because it shows up as radeon 7450. Thanks for any comment. Link to comment Share on other sites More sharing options...
duraaraa Posted June 29, 2014 Share Posted June 29, 2014 Do dual screens on Mobile radeons ever work? I have this situation with a different card (FirePro M5100) Using Buri FB unpatched, I can use the displayport with no problems. Upon patching Buri to properly allow the LVDS display to work, the LVDS display works, but stops working if I plug in something in the Display Port. When patching Buri, I patched only the LVDS line, and did not touch the other parts, which previously allowed a DisplayPort-connected monitor to work. Is there some fix for using multiple monitors on mobile AMD cards, or am I just out of luck? Edit: I managed to get dual screens working but have not been able to get three working. Two is good enough I guess. Unfortunately, I cannot get sleep to work, at all. It seems impossible at this point. I don't think it's 100% video card related, but I had the same computer with an nvidia card previously, and sleep did work (although the graphics card didn't resume when on battery properly.) On this model with ATI graphics, the processor, hard drive, nothing works on resume. I'm wondering if there isn't some fix for this that everyone knows but me? Update: It turns out sleep works if the Intel graphics are also enabled. Unfortunately, that means I can't use the internal screen with the radeon, so it's not good for me. I'm hoping maybe someone knows of a way to fix the sleep. I looked all through DSDT and tried many things but no success. Link to comment Share on other sites More sharing options...
applehacker Posted July 2, 2014 Share Posted July 2, 2014 Do dual screens on Mobile radeons ever work? I have this situation with a different card (FirePro M5100) Using Buri FB unpatched, I can use the displayport with no problems. Upon patching Buri to properly allow the LVDS display to work, the LVDS display works, but stops working if I plug in something in the Display Port. When patching Buri, I patched only the LVDS line, and did not touch the other parts, which previously allowed a DisplayPort-connected monitor to work. Is there some fix for using multiple monitors on mobile AMD cards, or am I just out of luck? Edit: I managed to get dual screens working but have not been able to get three working. Two is good enough I guess. Unfortunately, I cannot get sleep to work, at all. It seems impossible at this point. I don't think it's 100% video card related, but I had the same computer with an nvidia card previously, and sleep did work (although the graphics card didn't resume when on battery properly.) On this model with ATI graphics, the processor, hard drive, nothing works on resume. I'm wondering if there isn't some fix for this that everyone knows but me? Update: It turns out sleep works if the Intel graphics are also enabled. Unfortunately, that means I can't use the internal screen with the radeon, so it's not good for me. I'm hoping maybe someone knows of a way to fix the sleep. I looked all through DSDT and tried many things but no success. You may have to look at Rampage Dev's AMD 7xxx dsdt patch and apply with your card's values. some methods/values are introduced for power control, which may help for sleep, also probably may need to edit AGPM kext. Link to comment Share on other sites More sharing options...
SuccDfrutt Posted July 3, 2014 Share Posted July 3, 2014 hi there aren't kext for ati HD7470M? Link to comment Share on other sites More sharing options...
duraaraa Posted July 10, 2014 Share Posted July 10, 2014 Ok, so a problem which I'm starting to think is unfixable, but maybe someone can give me advice. I have a Dell Precision M4800, with AMD FirePro M5100. It works great after modifying the framebuffer and sleeping/waking up the computer when I want to attach an external monitor. With that said, I would like to attach two monitors. This is no problem -- I can attach one to the docking station and one to the computer, both display port converters, and it works. However, if I connect two displays to the docking station, only one of them works. If I connect one display, it works, but I can't use two at the same time with the docking station. Can anyone think of why it is that way? The computer detects the display, and shows it in Arrangement, but no picture on the display. Thanks. Edit: It's a framebuffer issue, apparently. I'm not sure how many concurrent monitors my computer supports, but I am able to change it so that the two docking port ports work concurrently, but one docking port port and the built-in displayport don't work concurrently. I'll work on the framebuffer. Link to comment Share on other sites More sharing options...
Rikoshet Posted August 9, 2014 Share Posted August 9, 2014 Slice, пожалуйста, take a look at my thread:http://www.insanelymac.com/forum/topic/300160-hd7970m-and-clevo-p370em/I did what you say in 1st post but cant reach desktop of my lappy!Thanks! Link to comment Share on other sites More sharing options...
gils83 Posted August 23, 2014 Share Posted August 23, 2014 Hello everyone,I have a CPU Kabini (Athlon 5350) that works on OS X, it has a GPU R3 type, it turns out that this is a GPU HD 8400.when using Clover (2795), he recognizes perfectly the AMD CPU and many device such as USB3 and network card and the HD 8400 graphics card R3 alias (0x98301002) as a HD 7600m?is a good sign? Link to comment Share on other sites More sharing options...
Slice Posted August 25, 2014 Author Share Posted August 25, 2014 AMD and OEMs often use different model names for the same chip. Link to comment Share on other sites More sharing options...
Rikoshet Posted September 12, 2014 Share Posted September 12, 2014 AMD and OEMs often use different model names for the same chip. Hi Slice! I know you are one of developers so would like to report maybe a bug of Clover injection. In config.plist using Inject ATI=true I have this color banding/gradient: http://www.insanelymac.com/forum/topic/291117-how-to-make-radeon-desktop-or-mobility-be-working-by-using-clover/page-3?do=findComment&comment=1976199 But injecting via DSDT the problem gone! Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { Store (Package (0x38) { "@0,ATY,EFIDisplay", Buffer (0x0C) { "LVDS" }, "@0,compatible", Buffer (0x0C) { "ATY,Buri" }, "@0,device_type", Buffer (0x08) { "display" }, "@0,name", Buffer (0x0E) { "ATY,Buri" }, "@1,device_type", Buffer (0x08) { "display" }, "@1,compatible", Buffer (0x0C) { "ATY,Buri" }, "@1,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "@1,name", Buffer (0x0E) { "ATY,Buri" }, "ATY,Card#", Buffer (0x0D) { "BR4-3595-003" }, "ATY,Rom#", Buffer (0x0D) { "BR4-3595-003" }, "device_type", Buffer (0x12) { "ATY,BuriParent" }, "VRAM,totalsize", Buffer (0x04) { 0x00, 0x00, 0x00, 0x80 }, "model", Buffer (0x11) { "AMD FirePro D300" }, "AAPL00,DualLink", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "@0,display-dual-link", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "AAPL,HasPanel", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "AAPL,Haslid", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "AAPL,backlight-control", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "@0,backlight-control", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "@0,AAPL,boot-display", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "@0,built-in", Buffer (One) { 0x01 }, "@0,display-link-component-bits", Buffer (0x04) { 0x06, 0x00, 0x00, 0x00 }, "@0,display-pixel-component-bits", Buffer (0x04) { 0x06, 0x00, 0x00, 0x00 }, "AAPL00,Dither", Buffer (0x04) { 0x00, 0x00, 0x00, 0x00 }, "@0,display-dither-support", Buffer (0x04) { 0x00, 0x00, 0x00, 0x00 }, "@0,inverter-current", Buffer (0x04) { 0x00, 0x00, 0x00, 0x00 }, "hda-gfx", Buffer (0x0A) { "onboard-1" }, }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } I'm not sure if it's a bug cause maybe via DSDT I'm injecting more properties that Clover does! Anyway, great work with Clover!!! Thank you! Link to comment Share on other sites More sharing options...
Slice Posted September 23, 2014 Author Share Posted September 23, 2014 To implement more injection into Clover by default I must know if it is useful, if it works for all and if it safe for all. Else I made a possibility to add your own properties to those produced by Clover For example <key>Devices</key> <dict> <key>NoDefaultProperties</key> <false/> <key>AddProperties</key> <array> <dict> <key>Device</key> <string>ATI</string> <key>Key</key> <string>AAPL00,Dither</string> <key>Value</key> <data>AQAAAA==</data> </dict> <dict> <key>Device</key> <string>ATI</string> <key>Key</key> <string>AAPL,Haslid</string> <key>Value</key> <data>AQAAAA==</data> </dict> </array> Link to comment Share on other sites More sharing options...
Rikoshet Posted September 23, 2014 Share Posted September 23, 2014 To me seems to be good alternative! Link to comment Share on other sites More sharing options...
caes95 Posted November 1, 2014 Share Posted November 1, 2014 work with Radeon HD 8530M (R5 M240)? Mavericks. Link to comment Share on other sites More sharing options...
cliffnj Posted November 6, 2014 Share Posted November 6, 2014 I have a Radeon Mobility 4670. I was able to patch and get this device working in Mavericks with full acceleration. Problem is after installing Yosemite using the same frame buffer settings causes the screen to come up black. I testing by clicking load Vbios and by setting the Inject ATI. The device came up to a black screen. Link to comment Share on other sites More sharing options...
vusun123 Posted November 7, 2014 Share Posted November 7, 2014 I have a Radeon Mobility 4670. I was able to patch and get this device working in Mavericks with full acceleration. Problem is after installing Yosemite using the same frame buffer settings causes the screen to come up black. I testing by clicking load Vbios and by setting the Inject ATI. The device came up to a black screen. The connector data might have changed, get someone to get you a framebuffer dump might help Link to comment Share on other sites More sharing options...
4everAnoob Posted November 14, 2014 Share Posted November 14, 2014 Could someone plz help get the m5950 (=6770m) working properly? With clover no matter what it always ends up with 7mb VRAM and corrupted graphics... Link to comment Share on other sites More sharing options...
Rikoshet Posted November 14, 2014 Share Posted November 14, 2014 Try to use dsdt injection 'cause clover injection does not work even for me, but dsdt one works fine! This is my dsm method, just adapt it for you and disable the clover injection! Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { Store (Package (0x42) { "@0,ATY,EFIDisplay", Buffer (0x0C) { "LVDS" }, "@0,compatible", Buffer (0x0C) { "ATY,Buri" }, "@0,device_type", Buffer (0x08) { "display" }, "@0,name", Buffer (0x0E) { "ATY,Buri" }, "@1,device_type", Buffer (0x08) { "display" }, "@1,compatible", Buffer (0x0C) { "ATY,Buri" }, "@1,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "@1,name", Buffer (0x0E) { "ATY,Buri" }, "ATY,Card#", Buffer (0x0D) { "BR4-3595-003" }, "ATY,Rom#", Buffer (0x0D) { "BR4-3595-003" }, "device_type", Buffer (0x12) { "ATY,BuriParent" }, "VRAM,totalsize", Buffer (0x04) { 0x00, 0x00, 0x00, 0x80 }, "model", Buffer (0x11) { "AMD FirePro D300" }, "AAPL00,DualLink", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "@0,display-dual-link", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "AAPL,HasPanel", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "AAPL,Haslid", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "AAPL,backlight-control", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "@0,backlight-control", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "@0,AAPL,boot-display", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "@0,built-in", Buffer (One) { 0x01 }, "@0,display-link-component-bits", Buffer (0x04) { 0x06, 0x00, 0x00, 0x00 }, "@0,display-pixel-component-bits", Buffer (0x04) { 0x06, 0x00, 0x00, 0x00 }, "AAPL00,Dither", Buffer (0x04) { 0x00, 0x00, 0x00, 0x00 }, "@0,display-dither-support", Buffer (0x04) { 0x00, 0x00, 0x00, 0x00 }, "@0,inverter-current", Buffer (0x04) { 0x00, 0x00, 0x00, 0x00 }, "hda-gfx", Buffer (0x0A) { "onboard-1" }, "AAPL00,override-no-edid", Buffer (0x80) { /* 0000 */ 0x00, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, /* 0008 */ 0x00, 0x4C, 0xA3, 0x48, 0x54, 0x00, 0x00, 0x00, /* 0010 */ 0x00, 0x14, 0x01, 0x04, 0x90, 0x29, 0x17, 0x78, /* 0018 */ 0x0A, 0xC8, 0x95, 0x9E, 0x57, 0x54, 0x92, 0x26, /* 0020 */ 0x0F, 0x50, 0x54, 0x00, 0x00, 0x00, 0x01, 0x01, /* 0028 */ 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, /* 0030 */ 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x29, 0x36, /* 0038 */ 0x80, 0xA0, 0x70, 0x38, 0x1F, 0x40, 0x18, 0x10, /* 0040 */ 0x25, 0x00, 0x99, 0xE6, 0x10, 0x00, 0x00, 0x1A, /* 0048 */ 0x1C, 0x24, 0x80, 0xA0, 0x70, 0x38, 0x1F, 0x40, /* 0050 */ 0x18, 0x10, 0x25, 0x00, 0x99, 0xE6, 0x10, 0x00, /* 0058 */ 0x00, 0x1A, 0x00, 0x00, 0x00, 0xFE, 0x00, 0x48, /* 0060 */ 0x47, 0x54, 0x33, 0x4A, 0x80, 0x31, 0x38, 0x34, /* 0068 */ 0x00, 0x00, 0x41, 0x01, 0x9E, 0x00, 0x00, 0x00, /* 0070 */ 0x00, 0x02, 0x01, 0x0A, 0x20, 0x20, 0x00, 0xA8 }, "device-id", Buffer (0x04) { 0x10, 0x68, 0x00, 0x00 }, "ATY,DeviceID", Buffer (0x02) { 0x10, 0x68 }, "vendor-id", Buffer (0x04) { 0x02, 0x10, 0x00, 0x00 }, "ATY,VendorID", Buffer (0x02) { 0x02, 0x10 }, "AAPL,slot-name", Buffer (0x07) { "Slot-1" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } Link to comment Share on other sites More sharing options...
Slice Posted December 2, 2014 Author Share Posted December 2, 2014 work with Radeon HD 8530M (R5 M240)? Mavericks. Why not? Try to use dsdt injection 'cause clover injection does not work even for me, but dsdt one works fine! This is my dsm method, just adapt it for you and disable the clover injection! Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { Store (Package (0x42) { "@0,ATY,EFIDisplay", Buffer (0x0C) { "LVDS" }, "@0,compatible", Buffer (0x0C) { "ATY,Buri" }, "@0,device_type", Buffer (0x08) { "display" }, "@0,name", Buffer (0x0E) { "ATY,Buri" }, "@1,device_type", Buffer (0x08) { "display" }, "@1,compatible", Buffer (0x0C) { "ATY,Buri" }, "@1,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "@1,name", Buffer (0x0E) { "ATY,Buri" }, "ATY,Card#", Buffer (0x0D) { "BR4-3595-003" }, "ATY,Rom#", Buffer (0x0D) { "BR4-3595-003" }, "device_type", Buffer (0x12) { "ATY,BuriParent" }, "VRAM,totalsize", Buffer (0x04) { 0x00, 0x00, 0x00, 0x80 }, "model", Buffer (0x11) { "AMD FirePro D300" }, "AAPL00,DualLink", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "@0,display-dual-link", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "AAPL,HasPanel", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "AAPL,Haslid", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "AAPL,backlight-control", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "@0,backlight-control", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "@0,AAPL,boot-display", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "@0,built-in", Buffer (One) { 0x01 }, "@0,display-link-component-bits", Buffer (0x04) { 0x06, 0x00, 0x00, 0x00 }, "@0,display-pixel-component-bits", Buffer (0x04) { 0x06, 0x00, 0x00, 0x00 }, "AAPL00,Dither", Buffer (0x04) { 0x00, 0x00, 0x00, 0x00 }, "@0,display-dither-support", Buffer (0x04) { 0x00, 0x00, 0x00, 0x00 }, "@0,inverter-current", Buffer (0x04) { 0x00, 0x00, 0x00, 0x00 }, "hda-gfx", Buffer (0x0A) { "onboard-1" }, "AAPL00,override-no-edid", Buffer (0x80) { /* 0000 */ 0x00, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, /* 0008 */ 0x00, 0x4C, 0xA3, 0x48, 0x54, 0x00, 0x00, 0x00, /* 0010 */ 0x00, 0x14, 0x01, 0x04, 0x90, 0x29, 0x17, 0x78, /* 0018 */ 0x0A, 0xC8, 0x95, 0x9E, 0x57, 0x54, 0x92, 0x26, /* 0020 */ 0x0F, 0x50, 0x54, 0x00, 0x00, 0x00, 0x01, 0x01, /* 0028 */ 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, /* 0030 */ 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x29, 0x36, /* 0038 */ 0x80, 0xA0, 0x70, 0x38, 0x1F, 0x40, 0x18, 0x10, /* 0040 */ 0x25, 0x00, 0x99, 0xE6, 0x10, 0x00, 0x00, 0x1A, /* 0048 */ 0x1C, 0x24, 0x80, 0xA0, 0x70, 0x38, 0x1F, 0x40, /* 0050 */ 0x18, 0x10, 0x25, 0x00, 0x99, 0xE6, 0x10, 0x00, /* 0058 */ 0x00, 0x1A, 0x00, 0x00, 0x00, 0xFE, 0x00, 0x48, /* 0060 */ 0x47, 0x54, 0x33, 0x4A, 0x80, 0x31, 0x38, 0x34, /* 0068 */ 0x00, 0x00, 0x41, 0x01, 0x9E, 0x00, 0x00, 0x00, /* 0070 */ 0x00, 0x02, 0x01, 0x0A, 0x20, 0x20, 0x00, 0xA8 }, "device-id", Buffer (0x04) { 0x10, 0x68, 0x00, 0x00 }, "ATY,DeviceID", Buffer (0x02) { 0x10, 0x68 }, "vendor-id", Buffer (0x04) { 0x02, 0x10, 0x00, 0x00 }, "ATY,VendorID", Buffer (0x02) { 0x02, 0x10 }, "AAPL,slot-name", Buffer (0x07) { "Slot-1" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } I see no reason why your method is better then Clover. It may work for you and only for you. 1 Link to comment Share on other sites More sharing options...
Rikoshet Posted December 2, 2014 Share Posted December 2, 2014 I see no reason why your method is better then Clover. It may work for you and only for you. Slice, it's not better, it's just Clover injection does not work in my case! Initially I was trying for 2 months your method without success and without understanding what's wrong with my card! Then, one day, I've tried dsdt method and BAM, all working instantly! Then I've asked you if you can add some properties to Clover injection and you've said it is not safe for all... That's all! I'm using Clover for everything else! Thanks for great job! Link to comment Share on other sites More sharing options...
128keaton Posted December 2, 2014 Share Posted December 2, 2014 Hi, I think I understand the guide, but maybe not. Anyway, have an ATI Radeon 6790 (0x6731002 according to About my Mac) and I've added that to the AMD7000Controller and ATIRadeonX3000 fields, but I still can't get full res/ CE/QI in Mavericks. Any suggestions? Link to comment Share on other sites More sharing options...
Slice Posted December 2, 2014 Author Share Posted December 2, 2014 Hi, I think I understand the guide, but maybe not. Anyway, have an ATI Radeon 6790 (0x6731002 according to About my Mac) and I've added that to the AMD7000Controller and ATIRadeonX3000 fields, but I still can't get full res/ CE/QI in Mavericks. Any suggestions? All suggestions are in the first post. I see no info to say more. EDITED. Did you forget to delete kernelcache? Link to comment Share on other sites More sharing options...
128keaton Posted December 2, 2014 Share Posted December 2, 2014 All suggestions are in the first post. I see no info to say more. EDITED. Did you forget to delete kernelcache? Nope, I boot with -f every time. This is what I don't understand: The same operation you must do with a kext AMDRadeonAccelerator or ATIRadeonX2000 or other one. Check all candidates if they contain such list of possible IDs and choose closest to you. I don't have the accelerator kext, but I edited the X3000 one. Which ones should I do for my card? All of them? Link to comment Share on other sites More sharing options...
Slice Posted December 2, 2014 Author Share Posted December 2, 2014 Clover has no key -f so you didn't delete kernelcache. AMDRadeonX3000.kext Link to comment Share on other sites More sharing options...
128keaton Posted December 2, 2014 Share Posted December 2, 2014 Clover has no key -f so you didn't delete kernelcache. AMDRadeonX3000.kext I'm not using clover, I'm using Chameleon. Well, I made some headway. I reinstalled, then I edited just the AMD7000Controller and the AMDRadeonX3000 with my ID, but since I didn't know wether it would be upper case or lower case, I put two ids in, 0x673E1002 and 0x673e1002. Now, whenever its about to load the login screen, the graphics cut off. Should I edit the AMD6000Controller (6790)? Or remove the extra IDs, if so which one? Thanks! EDIT: Got Clover working reliably, now just to get it to boot OS X Link to comment Share on other sites More sharing options...
Recommended Posts