netkas.org

Archive for the 'ATI' Category

it’s not Navi10, Navi16

In the comment to this news – https://videocardz.com/newz/amd-radeon-navi-gpus-spotted-in-macos-mohave-update

Navi10, Navi16, Navi9 is not chip names, the number is just c++ name separator

I would use c++filt name demangler to show this:

Function names as is:

$nm AMDRadeonX6000HWServices | grep Navi

__GLOBAL__sub_I_AMDRadeonHWServicesNavi.cpp

__ZN38AMDRadeonX6000_AMDRadeonHWServicesNavi10MatchTableE

__ZN38AMDRadeonX6000_AMDRadeonHWServicesNavi10gMetaClassE

__ZN38AMDRadeonX6000_AMDRadeonHWServicesNavi10superClassE

__ZN38AMDRadeonX6000_AMDRadeonHWServicesNavi16ProjectNameTableE

__ZN38AMDRadeonX6000_AMDRadeonHWServicesNavi16getMatchPropertyEv

__ZN38AMDRadeonX6000_AMDRadeonHWServicesNavi9MetaClassC1Ev

__ZN38AMDRadeonX6000_AMDRadeonHWServicesNavi9MetaClassC2Ev

__ZN38AMDRadeonX6000_AMDRadeonHWServicesNavi9MetaClassD0Ev

__ZN38AMDRadeonX6000_AMDRadeonHWServicesNavi9MetaClassD1Ev

__ZN38AMDRadeonX6000_AMDRadeonHWServicesNavi9metaClassE

__ZN38AMDRadeonX6000_AMDRadeonHWServicesNaviC1EPK11OSMetaClass

__ZN38AMDRadeonX6000_AMDRadeonHWServicesNaviC1Ev

__ZN38AMDRadeonX6000_AMDRadeonHWServicesNaviC2EPK11OSMetaClass

__ZN38AMDRadeonX6000_AMDRadeonHWServicesNaviC2Ev

__ZN38AMDRadeonX6000_AMDRadeonHWServicesNaviD0Ev

__ZN38AMDRadeonX6000_AMDRadeonHWServicesNaviD1Ev

__ZN38AMDRadeonX6000_AMDRadeonHWServicesNaviD2Ev

__ZNK38AMDRadeonX6000_AMDRadeonHWServicesNavi12getMetaClassEv

__ZNK38AMDRadeonX6000_AMDRadeonHWServicesNavi9MetaClass5allocEv

__ZTV38AMDRadeonX6000_AMDRadeonHWServicesNavi

__ZTVN38AMDRadeonX6000_AMDRadeonHWServicesNavi9MetaClassE

__ZZN38AMDRadeonX6000_AMDRadeonHWServicesNavi16getMatchPropertyEvE18PROJECT_NAME_COUNT

with c++ name demangling: $ nm AMDRadeonX6000HWServices | grep Navi | c++filt

__GLOBAL__sub_I_AMDRadeonHWServicesNavi.cpp

AMDRadeonX6000_AMDRadeonHWServicesNavi::MatchTable

AMDRadeonX6000_AMDRadeonHWServicesNavi::gMetaClass

AMDRadeonX6000_AMDRadeonHWServicesNavi::superClass 

AMDRadeonX6000_AMDRadeonHWServicesNavi::ProjectNameTable 

AMDRadeonX6000_AMDRadeonHWServicesNavi::getMatchProperty() 

AMDRadeonX6000_AMDRadeonHWServicesNavi::MetaClass::MetaClass() 

AMDRadeonX6000_AMDRadeonHWServicesNavi::MetaClass::MetaClass() 

 AMDRadeonX6000_AMDRadeonHWServicesNavi::MetaClass::~MetaClass() 

AMDRadeonX6000_AMDRadeonHWServicesNavi::MetaClass::~MetaClass()

AMDRadeonX6000_AMDRadeonHWServicesNavi::metaClass

AMDRadeonX6000_AMDRadeonHWServicesNavi::AMDRadeonX6000_AMDRadeonHWServicesNavi(OSMetaClass const*)

AMDRadeonX6000_AMDRadeonHWServicesNavi::AMDRadeonX6000_AMDRadeonHWServicesNavi()

AMDRadeonX6000_AMDRadeonHWServicesNavi::AMDRadeonX6000_AMDRadeonHWServicesNavi(OSMetaClass const*)

AMDRadeonX6000_AMDRadeonHWServicesNavi::AMDRadeonX6000_AMDRadeonHWServicesNavi()

AMDRadeonX6000_AMDRadeonHWServicesNavi::~AMDRadeonX6000_AMDRadeonHWServicesNavi()

AMDRadeonX6000_AMDRadeonHWServicesNavi::~AMDRadeonX6000_AMDRadeonHWServicesNavi()

AMDRadeonX6000_AMDRadeonHWServicesNavi::~AMDRadeonX6000_AMDRadeonHWServicesNavi()

AMDRadeonX6000_AMDRadeonHWServicesNavi::getMetaClass() const

AMDRadeonX6000_AMDRadeonHWServicesNavi::MetaClass::alloc() const

vtable for AMDRadeonX6000_AMDRadeonHWServicesNav

vtable for AMDRadeonX6000_AMDRadeonHWServicesNavi::MetaClass 

AMDRadeonX6000_AMDRadeonHWServicesNavi::getMatchProperty()::PROJECT_NAME_COUNT

RX 480 already works in osx 10.12

More news:

Using same trick as for R9 Nano it was possible to get new RX 480 card working in osx.

Not very stable.

more info in forum.

MacOS 10.12 brings Fiji acceleration support finally

Good news from our friends.

One can get working acceleration (and finally a full working driver) on amd Fiji cards (R9 Fury/X/Nano)

Just add device id (0x73001002) into Baffins section (AMDBaffinGraphicsAccelerator) in /System/Library/Extensions/AMDRadeonX4000.kext/Contents/Info.plist

Caveat – so far it only works on nmp as eGPU, some code that is checking for nmp is in place.

More here – Forum post

Image and video hosting by TinyPic

macOS 10.12 brings new amd drivers same old nvidia drivers

amd drivers has new amd9500Controller.kext which is for polaris gpus (0x67E01002 0x67FF1002 0x67C01002 0x67DF1002)

amdRadeonX4000.kext has new graphics accelerator – AMDBaffinGraphicsAccelerator (Polaris 11)  (0x67E01002 0x67FF1002 0x67EF1002)

still no fiji accele support, Polaris 10 only framebuffer support, Polaris 11 has full support – apple is working on some new macs with Polaris 11 included, AMD today announced new cards as well, RX460 (P11 based), RX470/RX480 (P10 based)

 

nvidia – new driver finally, but still no GM100 kext, so no maxwell.  355.10.05b02

Come on Apple, improve your 3d drivers

Few tests with same config (R9 290x, MP3,1, 2×2.8 GHZ cpu) in Unigine Valley. I know this cpu sucks for valley, but it’s enough to compare different OS/drivers.

(Read the article)

We have eGPU subform openned

Btw, we have eGPU subform now at forum.netkas.org to tell more about using eGPU in OS X via ThunderBolt

Join us.

egpu mini

New imacs…

M290X is radeon HD 7870 but at lower 900 mhz core clock. A bit slower than 780M you can find in current Imac.
and it comes with 2 gigs of vram, kidding?

M295X is some tonga chip, probably full tonga chip ( equal to 7970). Will be like one D700 of newMacPro.
4 gig vram here.

That’s too weak to play anything at 5K, they even will struggle at 2560×1440. Only for 1080p gaming.

Little Teaser

go here

Slow Radeons 7xxx+ on MacPro3,1

It’s known for a while that GCN radeons are low performers on 2008 MacPro using OSX 10.9

And the reason for this is…..

AppleIntelCPUPowerManagement.kext

Apple fucked up some CPU power management resulting in videocard not running properly. plz fix.

Just remove AppleIntelCPUPowerManagement.kext and AppleIntelCPUPowerManagementClient.kext if you like to workaround it, speedstepping still works, cpu isn’t hot/cosuming a lot, still drops the clocks.

 

Fuck you AMD!

Wanna use AMD and nvidia card in one system, AMD says no.
wanna use radeon 2600xt (uses legacy driver) and modern videocard in one system? AMD says no

AMD has the worst driver programmers I ever saw. To be able to have two different display drivers running in one system is just too hard for their small retarded minds. Every driver release gets worse. fuck you AMD!

Next Page »