Jump to content
Slice

RadeonMonitor problems

128 posts in this topic

Recommended Posts

I think RadeonDump can onyl dump (read) not write.

PS: I found that newest Darwindumper has perhaps newer Version (finder show conent, Tools..) of RadenDump.

With that version (same dump values) the range end works better in case shows only the range wanted, not always a complete line - more bytes shown as given range.

RadeonDump -r 6b4,6b4

Found a device of class RadeonPCI: IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEG0@1/IOPP/GFX0@0/RadeonPCI
it matched on name "ATY_GPU"
0x06B4: 0x0001E083
GA-EP35:~ andreasm$ 
 

https://bitbucket.org/blackosx/darwindumper/downloads/

 

Do we need that DirectHW.kext (also within DarwinDumper) to write in some addresses?

I dont have installed  - i think also Darwindumper may kextload that at runtime? And how could we write in that adress space you told us?

Share this post


Link to post
Share on other sites
Advertisement

Found a device of class RadeonPCI: IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEG0@1/IOPP/PEGP@0/RadeonPCI

it matched on name "ATY_GPU"

0x0000:  FFFF7E5C FF404138 00000000 00000000 00000000 00000000 00000000 00000000

0x0020:  00000000 00000000 00000000 00000000 100100A2 00D816E6 100100A2 00D816E6

0x0040:  00000000 00000000 00010000 00010000 00000000 00000000 00000000 00000000

0x0060:  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

0x0080:  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

0x00A0:  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

0x00C0:  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

0x00E0:  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

0x0100:  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

 

my 290x


Found a device of class RadeonPCI: IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEG0@1/IOPP/PEGP@0/RadeonPCI

it matched on name "ATY_GPU"

0xFFFF7E5C:  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

 

Share this post


Link to post
Share on other sites

Hi, Slice.

I think the working RadeonPCI.kext (for use with that RadeonDump) is a few posts later. http://www.insanelymac.com/forum/topic/317915-clover-test-and-patches-for-polaris-gpu/page-8?do=findComment&comment=2340126 (otherwise all results are zeros)

How do you mean your range: in range 6A0,40 ... If crash then 6B0,10

In the examples the command looks:

RadeonDump2 -r 0,200 , how are the parameters for in range 6A0,40 (you mean start=6A0 and 40 length, so 6A0, 6EF would be OK ?

RX 460 0x67ef , Sierra working (for this test: no RadeonMonitor in use, only kextutil  RadeonPCI.kext, in Clover Lilu + whatevergreen )

RadeonDump2 -r 6A0,6FF

Found a device of class RadeonPCI: IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEG0@1/IOPP/GFX0@0/RadeonPCI
it matched on name "ATY_GPU"
0x06A0:  00000000 AAAA5555 00000000 AAAA5555 0003F010 0001E083 00000000 AAAA5555
0x06C0:  00000000 AAAA5555 00000000 AAAA5555 00000000 AAAA5555 00000000 00000064
0x06E0:  00000002 00000000 00000000 00000000 00000000 00000000 00000000 00000000
 
/RadeonDump2 -r 1700,1750  (found that you looked for that range in the past : ) )
Found a device of class RadeonPCI: IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEG0@1/IOPP/GFX0@0/RadeonPCI
it matched on name "ATY_GPU"
0x1700:  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
0x1720:  00000000 00000000 00000000 00000000 00000000 00010000 00000000 00000000
0x1740:  00000200 00000000 00000000 00000000 00000000 00000000 00000000 000
 
​RadeonDump2 -r 5400,5450 (found that you looked for that range in the past : ) )
Found a device of class RadeonPCI: IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEG0@1/IOPP/GFX0@0/RadeonPCI
it matched on name "ATY_GPU"
0x5400:  00000000 00000001 00000000 00000000 00000000 0000001A 00000002 00000002
0x5420:  00000000 00000000 00000800 80000000 00000100 00040000 00000000 00000000
0x5440:  00000000 00000000 00000000 00000000 00018003 00000000 00040040 4010E110
 
PS: attached the used two tools.
Usage:
sudo chown -R root:wheel ~/Downloads/RadeonPCI.kext

sudo chmod -R 755 ~/Downloads/RadeonPCI.kext

sudo kextutil -v ~/Downloads/RadeonPCI.kext

..

~/Downloads/RadeonDump2 -r start,end 

I seems have no those sources. Did you have it?

Share this post


Link to post
Share on other sites

Corrected RadeonPCI.kext. Hope it will work on most Radeon cards.

Utility I'll remake later.

attachicon.gifRadeonPCI.kext.zip

not worked at my machine

Picos-Mac-Pro:radeon pico$ ./RadeonDump1 -r 0,200

Found a device of class RadeonPCI: IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEGP@1/IOPP/GFX1@0/RadeonPCI

it matched on name "ATY_GPU"

Assertion failed: (KERN_SUCCESS == kr), function main, file ./RadeonDump1.c, line 301.

Abort trap: 6

 

with old RadeonPci.kext and newesr RadeonDump1

Picos-Mac-Pro:radeon pico$ ./RadeonDump1 -w 6b0,c0300014

Found a device of class RadeonPCI: IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEGP@1/IOPP/GFX1@0/RadeonPCI

it matched on name "ATY_GPU"

Picos-Mac-Pro:radeon pico$ ./RadeonDump1 -r 6b4,6b4

Found a device of class RadeonPCI: IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEGP@1/IOPP/GFX1@0/RadeonPCI

it matched on name "ATY_GPU"

0x06B4: 0x00000000

Share this post


Link to post
Share on other sites

Same for me, newer RadeonPCI.kext has that Abort Trap: 6. (AMD RX 460)

 

Using older RadeonPCI.kext together witj new RadeonDump1

 

RadeonDump1 -n 6b0,c0300014
Found a device of class RadeonPCI: IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEG0@1/IOPP/GFX0@0/RadeonPCI
it matched on name "ATY_GPU"
0xc0300014: 0x    5a2d
bash-3.2# 
 
RadeonDump1 -r 6B0,6BF
Found a device of class RadeonPCI: IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEG0@1/IOPP/GFX0@0/RadeonPCI
it matched on name "ATY_GPU"
0x06B0: 0xC0300014
0x06B4: 0x00005028
0x06B8: 0x00000000
0x06BC: 0xAAAA5555
 

 

Share this post


Link to post
Share on other sites

not worked at my machine

Picos-Mac-Pro:radeon pico$ ./RadeonDump1 -r 0,200

Found a device of class RadeonPCI: IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEGP@1/IOPP/GFX1@0/RadeonPCI

it matched on name "ATY_GPU"

Assertion failed: (KERN_SUCCESS == kr), function main, file ./RadeonDump1.c, line 301.

Abort trap: 6

 

with old RadeonPci.kext and newesr RadeonDump1

Picos-Mac-Pro:radeon pico$ ./RadeonDump1 -w 6b0,c0300014

Found a device of class RadeonPCI: IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEGP@1/IOPP/GFX1@0/RadeonPCI

it matched on name "ATY_GPU"

Picos-Mac-Pro:radeon pico$ ./RadeonDump1 -r 6b4,6b4

Found a device of class RadeonPCI: IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEGP@1/IOPP/GFX1@0/RadeonPCI

it matched on name "ATY_GPU"

0x06B4: 0x00000000

Should be

./RadeonDump1 -n 6b0,c0300014

 

Same for me, newer RadeonPCI.kext has that Abort Trap: 6. (AMD RX 460)

 

Using older RadeonPCI.kext together witj new RadeonDump1

 

RadeonDump1 -n 6b0,c0300014
Found a device of class RadeonPCI: IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEG0@1/IOPP/GFX0@0/RadeonPCI
it matched on name "ATY_GPU"
0xc0300014: 0x    5a2d
bash-3.2# 
 
RadeonDump1 -r 6B0,6BF
Found a device of class RadeonPCI: IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEG0@1/IOPP/GFX0@0/RadeonPCI
it matched on name "ATY_GPU"
0x06B0: 0xC0300014
0x06B4: 0x00005028
0x06B8: 0x00000000
0x06BC: 0xAAAA5555

 

Good!

Now see the behavior of output

5a2d -> 0x2d = 45 celsium degree

What if heavy load?

Share this post


Link to post
Share on other sites

HD 7790

Picos-Mac-Pro:radeon pico$ ./RadeonDump1 -n 6b0,c0300014
Found a device of class RadeonPCI: IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEGP@1/IOPP/GFX1@0/RadeonPCI
it matched on name "ATY_GPU"
0xc0300014: 0x       0

Share this post


Link to post
Share on other sites

Picos-Mac-Pro:radeon pico$ ./RadeonDump1 -r 714,7f4

Found a device of class RadeonPCI: IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEGP@1/IOPP/GFX1@0/RadeonPCI
it matched on name "ATY_GPU"
0x0714: 0x00000000
0x0718: 0x00000000
0x071C: 0x00000000
0x0720: 0x00000000
0x0724: 0x00000000
0x0728: 0x00000000
0x072C: 0x00000000
0x0730: 0x00000000
0x0734: 0x00000000
0x0738: 0x00000000
0x073C: 0x00000000
0x0740: 0x00000000
0x0744: 0x00000000
0x0748: 0x00000000
0x074C: 0x00000000
0x0750: 0x00000000
0x0754: 0x00000000
0x0758: 0x00000000
0x075C: 0x00000000
0x0760: 0x00000000
0x0764: 0x00000000
0x0768: 0x00000000
0x076C: 0x00000000
0x0770: 0x00000000
0x0774: 0x00000000
0x0778: 0x00000000
0x077C: 0x00000000
0x0780: 0x00000000
0x0784: 0x00000000
0x0788: 0x00000000
0x078C: 0x00000000
0x0790: 0x00000000
0x0794: 0x00000000
0x0798: 0x00000000
0x079C: 0x00000000
0x07A0: 0x00000000
0x07A4: 0x00000000
0x07A8: 0x00000000
0x07AC: 0x00000000
0x07B0: 0x00000000
0x07B4: 0x00000000
0x07B8: 0x00000000
0x07BC: 0x00000000
0x07C0: 0x00000000
0x07C4: 0x00000000
0x07C8: 0x00000000
0x07CC: 0x00000000
0x07D0: 0x00000000
0x07D4: 0x00000000
0x07D8: 0x00000000
0x07DC: 0x00000000
0x07E0: 0x00000000
0x07E4: 0x00000000
0x07E8: 0x00000000
0x07EC: 0x00000000
0x07F0: 0x00000000
0x07F4: 0x00000000


Picos-Mac-Pro:radeon pico$  ./RadeonDump1 -n 6b0,c0300e0c
Found a device of class RadeonPCI: IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEGP@1/IOPP/GFX1@0/RadeonPCI
it matched on name "ATY_GPU"
0xc0300e0c: 0x       0

Share this post


Link to post
Share on other sites

Should be

./RadeonDump1 -n 6b0,c0300014

Good!

Now see the behavior of output

5a2d -> 0x2d = 45 celsium degree

What if heavy load?

 

Sir, you want heavy GPU  load?!, Sir :)

Then you get it :)

 

running Geeks3D Tessmark X64 -

 

post-110586-0-92068100-1511953512_thumb.jpg

 

Before (idle, Desktop):

RadeonDump1 -n 6b0,c0300014 ... 0xc0300014: 0x    562b (43 Celsius?)

Start GPU stress:
0xc0300014: 0x    6a3a > 0xc0300014: 0x    703e (62 C)
Near Eend of GPU Test:   0xc0300014: 0x    7641 (65 C)

Very short after gpu load ends :

0xc0300014: 0x    6a36 (54 C) > 0xc0300014: 0x    6633 (51 C)

Now, after about 3 Min idle: 

0xc0300014: 0x    5028 (40 C)

 

PS:

I have question about FakeSMC (yours) vs Rehabman ( https://github.com/RehabMan/OS-X-FakeSMC-kozlek: also heavy load, but in this case of GPU FAN full speed :)

Both work as they should - i use rehabmans.

As i tried yours, for radeonMonitor tests there was some ??? about the FAN of the RX 460:

With your FakeSMC the GPU FAN runs full speed (for about 5 Seconds) at startup (Desktop appears) and at every wakeup (for me main problem).

With rehabmans the gpu fan stay quite in same situations (as it should).

Both with Sierra, no other change.

Can it be that some diff in SMC keys (exist or not or diff in value) can make that different FAN handling?

 

EDIT: I uploaded SMC -l of your & rehab Fakesmc

What can be they keys, values belong to the annoying full speed fan at start & wake?

SMC Slice: GPU fan runs full speed for 5 sec at startup  & wakeup
Last login: Wed Nov 29 12:49:54 on ttys000
GA-EP35:~ andreasm$ /Users/andreasm/Desktop/smc 
Apple System Management Control (SMC) tool 0.01
Usage:
/Users/andreasm/Desktop/smc [options]
    -f         : fan info decoded
    -h         : help
    -k <key>   : key to manipulate
    -l         : list all keys and values
    -r         : read the value of a key
    -w <value> : write the specified value to a key
    -v         : version

GA-EP35:~ andreasm$ /Users/andreasm/Desktop/smc -l
  #KEY  [ui32]  40 (bytes 00 00 00 28)
  $Num  [ui8 ]  1 (bytes 01)
  ACID  [ch8*]  (bytes ba be 3c 45 c0 03 10 43)
  ALI0  [{ali]  (bytes 06 01 02 00)
  ALRV  [ui16]  1 (bytes 00 01)
  ALV0  [{alv]  (bytes 01 01 03 b7 00 a3 00 15 6a f4)
  CLKH  [{clh]  (bytes 00 00 70 80 00 01 19 40)
  CLKT  [ui32]  162 (bytes 00 00 b3 a2)
  EPCI  [flag]  (bytes 06 90 07 00)
  FNum  [ui8 ]  (bytes 00)
  LSOF  [flag]  (bytes 01)
  LSSB  [{lso]  (bytes 01 01)
  LsNM  [ui8 ]  (bytes 01)
  LsbV  [{rev]  (bytes 01 04 0a 00 06)
  MOST  [ui16]  3 (bytes 80 03)
  MSDW  [ui8 ]  (bytes 01)
  MSPS  [{msp]  (bytes 00)
  MSSD  [si8 ]  (bytes 03)
  NATJ  [ui8 ]  (bytes 02)
  NTOK  [ui8 ]  (bytes 01)
  NVPR  [ui8 ]  (bytes 00)
  OSK0  [ch8*]  (bytes 6f 75 72 68 61 72 64 77 6f 72 6b 62 79 74 68 65 73 65 77 6f 72 64 73 67 75 61 72 64 65 64 70 6c)
  OSK1  [ch8*]  (bytes 65 61 73 65 64 6f 6e 74 73 74 65 61 6c 28 63 29 41 70 70 6c 65 43 6f 6d 70 75 74 65 72 49 6e 63)
  REV   [{rev]  (bytes 02 11 0f 00 00 16)
  RMde  [char]  (bytes 41)
  RPlt  [ch8*]  (bytes 64 38 00 00 00 00 00 00)
  RBr   [ch8*]  (bytes 64 38 00 00 00 00 00 00)
  BEMB  [flag]  (bytes 00)
  TC0D  [sp78]  (bytes 1f 00)
  FRC0  [freq]  (bytes 06 40)
  VC0C  [fp2e]  (bytes 3b a5)
  TC1D  [sp78]  (bytes 20 00)
  FRC1  [freq]  (bytes 06 40)
  TC2D  [sp78]  (bytes 1f 00)
  FRC2  [freq]  (bytes 06 40)
  TC3D  [sp78]  (bytes 20 00)
  FRC3  [freq]  (bytes 06 40)
  MPkC  [ui16]  0 (bytes a0 00)
  NATi  [ui16]  30 (bytes 00 1e)
  HE0N  [ui8 ]  (bytes 10)
GA-EP35:~ andreasm$ 

SMC rehabman https://github.com/RehabMan/OS-X-FakeSMC-kozlek
GPU FAN sosnt run full speed at startup / wakeup

GA-EP35:~ andreasm$ /Users/andreasm/Desktop/smc -l
  #KEY  [ui32]  46 (bytes 00 00 00 2e)
  FNum  [ui8 ]  0 (bytes 00)
  HWS0  [ch8*]  (bytes 47 69 67 61 62 79 74 65)
  HWS1  [ch8*]  (bytes 5a 37 37 2d 44 53 33 48)
  RPlt  [ch8*]  (bytes 64 38 00 00 00 00 00 00)
  RBr   [ch8*]  (bytes 64 38 00 00 00 00 00 00)
  TC0D  [sp78]  (bytes 27 00)
  TC1D  [sp78]  (bytes 29 00)
  TC2D  [sp78]  (bytes 27 00)
  TC3D  [sp78]  (bytes 28 00)
  TCAD  [sp78]  (bytes 2a 00)
  MlC0  [fp88]  (bytes 20 00)
  CC0C  [ui32]  128 (bytes 00 00 0c 80)
  MlC1  [fp88]  (bytes 20 00)
  CC1C  [ui32]  128 (bytes 00 00 0c 80)
  MlC2  [fp88]  (bytes 1f 00)
  CC2C  [ui32]  28 (bytes 00 00 0c 1c)
  MlC3  [fp88]  (bytes 1f 00)
  CC3C  [ui32]  28 (bytes 00 00 0c 1c)
  CCPA  [ui32]  21 (bytes 00 00 0c 15)
  PCTR  [sp78]  (bytes 17 92)
  PCPC  [sp78]  (bytes 12 4e)
  PCPG  [sp78]  (bytes 00 00)
  $Adr  [ui32]  0 (bytes 00 00 03 00)
  $Num  [ui8 ]  1 (bytes 01)
  ACID  [ch8*]  (bytes 85 fc 04 4d d8 12 7a f4)
  ALI0  [{ali]  (bytes 07 01 02 00)
  ALRV  [ui16]  1 (bytes 00 01)
  ALV0  [{alv]  (bytes 01 10 06 75 01 20 00 b6 0e e0)
  LsNM  [ui8 ]  1 (bytes 01)
  LsbV  [{rev]  (bytes 01 04 0a 00 06)
  MSLD  [ui8 ]  0 (bytes 00)
  MSSD  [si8 ]  (bytes 05)
  MSSP  [si8 ]  (bytes 05)
  NATJ  [ui8 ]  2 (bytes 02)
  OSK0  [ch8*]  (bytes 6f 75 72 68 61 72 64 77 6f 72 6b 62 79 74 68 65 73 65 77 6f 72 64 73 67 75 61 72 64 65 64 70 6c)
  OSK1  [ch8*]  (bytes 65 61 73 65 64 6f 6e 74 73 74 65 61 6c 28 63 29 41 70 70 6c 65 43 6f 6d 70 75 74 65 72 49 6e 63)
  REV   [{rev]  (bytes 02 11 0f 00 00 16)
  RMde  [char]  (bytes 41)
  RVBF  [{rev]  (bytes 01 30 0f 00 00 03)
  RVUF  [{rev]  (bytes 01 30 0f 00 00 03)
  BEMB  [flag]  (bytes 00)
  EPCI  [ui32]  0 (bytes 06 90 07 00)
  NATi  [ui16]  30 (bytes 00 1e)
  NTOK  [ui8 ]  1 (bytes 01)
  HE0N  [ui8 ]  16 (bytes 10)
GA-EP35:~ andreasm$ 

Share this post


Link to post
Share on other sites

Someone with Vega 10 test, please,

./RadeonDump -r 16658,16660

or

./RadeonDump -r 59968,59970

 

@mitch_de

Great!

So we know how to get temperature from Baffin family cards. And so my RadeonMonitor latest version should work for you? It already contains this method.

May be you test it with other FakeSMC?

About GPU FAN I don't know. It looks like GPU initializing but I nowhere do this. Only in Clover RadeonDeInit what I think is common for both your cases.

 

 

Ok that sounds like a lot of work. Is it something you are able to do ?

 

Thanks !

It is easy but requires a time. May be today evening I'll make it.

Share this post


Link to post
Share on other sites

Hope this kext will not crash and will show Radeon temperature.

doesn't crash anymore, but GPU 0 Core Temp -127° C ?!? (and NO, it is NOT cooled by liquid oxygen, just a one mile diameter fan with a million RpS)

 

Bildschirmfoto2017-11-29um18.45.38.png

but anyway... nice job.

Share this post


Link to post
Share on other sites

doesn't crash anymore, but GPU 0 Core Temp -127° C ?!? (and NO, it is NOT cooled by liquid oxygen, just a one mile diameter fan with a million RpS)

 

 

but anyway... nice job.

Can you, please, look into system.log or dmesg to find messages from RadeonMonitor?

Share this post


Link to post
Share on other sites

Hi, also for RX 460 - static (no changes under gpu load, idle) at -127 Celsius.

Nothing shown in dmesg & any log - Sierra.

Share this post


Link to post
Share on other sites

HD 7790  GPU 0

 

17    0 0xffffff7f8397a000 0x5000     0x5000     org.slice.RadeonMonitor (1.3.1) A388BA0F-9378-333A-8061-C9FE496C5B40 <16 12 7 4 3>

 

post-1113740-0-13405200-1512020964_thumb.png

Share this post


Link to post
Share on other sites

HD 7790  GPU 0

 

17    0 0xffffff7f8397a000 0x5000     0x5000     org.slice.RadeonMonitor (1.3.1) A388BA0F-9378-333A-8061-C9FE496C5B40

 

attachicon.gifScreen Shot 2017-11-30 at 12.47.46.png

 

Picos-Mac-Pro:radeon pico$ ./RadeonDump1 -r 714,7f4

 

Found a device of class RadeonPCI: IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEGP@1/IOPP/GFX1@0/RadeonPCI

it matched on name "ATY_GPU"

0x0714: 0x00000000

0x0718: 0x00000000

0x071C: 0x00000000

0x0720: 0x00000000

0x0724: 0x00000000

0x0728: 0x00000000

0x072C: 0x00000000

0x0730: 0x00000000

0x0734: 0x00000000

0x0738: 0x00000000

0x073C: 0x00000000

0x0740: 0x00000000

0x0744: 0x00000000

0x0748: 0x00000000

0x074C: 0x00000000

0x0750: 0x00000000

0x0754: 0x00000000

0x0758: 0x00000000

0x075C: 0x00000000

0x0760: 0x00000000

0x0764: 0x00000000

0x0768: 0x00000000

0x076C: 0x00000000

0x0770: 0x00000000

0x0774: 0x00000000

0x0778: 0x00000000

0x077C: 0x00000000

0x0780: 0x00000000

0x0784: 0x00000000

0x0788: 0x00000000

0x078C: 0x00000000

0x0790: 0x00000000

0x0794: 0x00000000

0x0798: 0x00000000

0x079C: 0x00000000

0x07A0: 0x00000000

0x07A4: 0x00000000

0x07A8: 0x00000000

0x07AC: 0x00000000

0x07B0: 0x00000000

0x07B4: 0x00000000

0x07B8: 0x00000000

0x07BC: 0x00000000

0x07C0: 0x00000000

0x07C4: 0x00000000

0x07C8: 0x00000000

0x07CC: 0x00000000

0x07D0: 0x00000000

0x07D4: 0x00000000

0x07D8: 0x00000000

0x07DC: 0x00000000

0x07E0: 0x00000000

0x07E4: 0x00000000

0x07E8: 0x00000000

0x07EC: 0x00000000

0x07F0: 0x00000000

0x07F4: 0x00000000

 

Picos-Mac-Pro:radeon pico$  ./RadeonDump1 -n 6b0,c0300e0c

Found a device of class RadeonPCI: IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEGP@1/IOPP/GFX1@0/RadeonPCI

it matched on name "ATY_GPU"

0xc0300e0c: 0x       0

It looks like HD7790 is other family. I see no a good method to get temperature for it.

 

Waiting for tests with other cards.

Share this post


Link to post
Share on other sites

It looks like HD7790 is other family. I see no a good method to get temperature for it.

 

Waiting for tests with other cards.

 

wake after sleep shown GPU Core -68

 

post-1113740-0-10317600-1512025892_thumb.png

Share this post


Link to post
Share on other sites

I found the mistake
Here
https://sourceforge.net/p/hwsensors/hwsensors3/code3/HEAD/tree/trunk/plugins/GPUSensors/RadeonMonitor/ATICard.cpp#l21
line:
IOPhysicalAddress bar = (IOPhysicalAddress)((VCard->configRead32(0x20)) & ~0x3f);
Must be 0x24 instead of 0x20

I can compile only in evening. If someone do it now it will be great!

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 blxkspell
      Hey!
      As I have 3 Monitors connected, my RX 570 gets arround 50°C while ideling/ web browsing etc. The problem is, that this temp is apparently just the threshold, when the fans start to spin. So the fans start spinning for a minute then they stop for a while again... This is very annoying for me as the rest of my hackintosh is nearly quiet (SSD, 120mm low RPM cpu fan, nearly silent PSU,...), especially when Im using the pc to revise for school. Does somebody know wether its possible to "change" the threshold till the fans start spinning? Like it would probably not be a problem for the gpu at all, if the temp rises to 55°C but therefore be soundless....
       
       
    • By golden eagl
      Hi everyone,
      I'm struggling with installing driver of my graphic adapter on high Sierra but till now I failed to find a solution to my issue ....
      My PC configuration is .
      CPU : AMD A8-5500 APU with integrated Radeon 7560 
      RAM : 8G    
      I tried to download a tool from tonymax website and after I used it I unable to login to my Mac high Sierra so I installed high Sierra again .....
       
      Any help with this issue
      Thanks in advance 
       
    • 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 corbrink
      Hi,
      I have the following system:
      - Gigabyte Z370M-D3H M-ATX
      - Core i7-8700K Coffee Lake
      - Gigabyte Radeon RX 560 4GB
      - Crucial Ballistix 16GB DDR4
      - 960 EVO 1TB NVMe SSD
      - 850 EVO 500GB SSD
      - Crucial 500GB SSD
      - The 2 500GB SSD's run in Raid for data storage.
      - Western Digital 3TB HDD - Time machine
      - EFI here (too large to attach): EFI.zip

      Questions:
      1. I have a dual screen running from Radeon card, 1 on DP and 1 on HDMI. The one screen on DP goes randomly blank from time to time. Any ideas?
      2. I've read that the kexts should preferably be installed in /library/extensions. I would like to know what kexts should remain in the EFI. I read that you should install FakeSMC in both locations (EFI and L/E). If I follow this route must I change something in the config.plist?
      3. USB info in System Information (attached does not seem correct. I've followed the changes suggested but I'm not sure if this is the best it can be.
      4. Are there something in the EFI and config.plist I don't need or doing wrong?

      Feedback will be appreciated.


    • By 1Ale1
      Ciao a tutti, ultimamente ho deciso di mettermi al lavoro e fare un investimento a lungo termine comprando un fisso che ho assemblato pezzo dopo pezzo leggendo numerosi forum per essere bene informato sul miglior hardware che potessi ottenere per un Hackintosh ottimizzando al meglio i costi: ho finito così per comprare:
       
      Hardware:
       
       
      -Motherboard: Gigabyte Z390 Aorus Pro (Rev 1.0)
      -CPU: Intel i7 9700k raffreddato a liquido (CoffeLake)
      -GPU: AMD Radeon RX580 (avendo letto le eccellenti prestazioni a ottimo prezzo per MacOS)
      -RAM: 32GB DDR4 Crucial Ballistix Sport LT (4x8GB 3000MHz)
      -NVMe SSD Samsung 970 Evo 250GB M.2 dedicato solo a MacOS, nel secondo slot della Mobo M.2 avrei poi messo un Western Digital Blue da 250GB con Windows 10 su metà disco e per l'altra metà il Debian che sto utilizzando adesso
       
       
      Poi mi sono messo subito al lavoro per cercare di far partire questo benedetto MacOs su una macchina non ufficiale, ho tovato quindi questa guida su GitHub che era molto simile alla mia configurazione:
       
      https://github.com/cmer/gigabyte-z390-aorus-master-hackintosh/blob/master/STEP_BY_STEP.md
       
      Dopo aver fatto partire una macchina virtuale per configurare la USB come comunemente viene fatto, scaricando l'applicazione e facendo il "burn/copia dei file" di macOS su pennetta esterna rendendola bootabile solamente da un pc ufficiale mac, sono passato alla configurazione di Clover (l'EFI installer, cartella che allegherò qui sotto, ma prima leggete il problema): Ho messo i driver necessari, mettendo quelli che lui menzionava sotto la sezione "building the usb installer"
       
      https://hackintosh.gitbook.io/-r-hackintosh-vanilla-desktop-guide/building-the-usb-installer
       
       
      Install Clover for UEFI booting only
      Install Clover to the ESP
      Under Drivers64UEFI:
      AptioMemoryFix (the new hotness that includes NVRAM fixes, as well as better memory management) (che poi ho dovuto rimuovere, leggi sezione https://github.com/cmer/gigabyte-z390-aorus-master-hackintosh/blob/master/STEP_BY_STEP.md#fixing-kernel-panics-at-rebootshutdown)
      VBoxHfs-64.efi (or HFSPlus.efi if available) - one of these is required for Clover to see and boot HFS+ volumes. If you see the option to enable it in the installer, make sure it's selected - if you don't see it in the installer, verify that one of them exists in the EFI -> CLOVER -> drivers64UEFI folder
      ApfsDriverLoader - (Available in Dids' Clover builds - or here) this allows Clover to see and boot from APFS volumes by loading apfs.efi from ApfsContainer located on block device (if using AptioMemoryFix as well, requires R21 or newer)
       
      applicando piccole modifiche a causa di un errore già riportato da questa persona che ha scritto la guida di GitHub di sostituire AptioMemoryFix-64 (dalla cartella EFI/EFI/CLOVER/driver64UEFI) con OsxAptioFix2Drv-free2000, questa infatti riportava  quanto segue dopo aver detto di aver sostituito AptioMemoryFix-64.efi con OsxaptioFix2Drv-free2000:
       
      "I am told that there are downsides (that I don't fully understand yet) to using OsxAptioFix2Drv-free2000, so do this at your own risk."
       
      Ho configurato poi il config.plist
       
      Come diceva lui, partendo da questo file: https://hackintosh.gitbook.io/-r-hackintosh-vanilla-desktop-guide/config.plist-per-hardware/coffee-lake e applicando le modifiche che sotto ha descritto, del tipo:
       
      Open coffeelake_sample_config.plist with Clover Configurator (right click → Open With → Clover Configurator)   In SMBIOS: - Click the button with an up/down arrow (middle right). Chose iMac18,3. This is important since we'll be connecting our monitor to the RX580. The HDMI port on our motherboard is NOT yet working for Hackintoshes. - Make sure the serial number generated is an iMac (mid-2017) by clicking Model Lookup. - Ensure that Check Coverage reports that the serial is NOT valid. You don't want to use somebody else's serial number. - While you're here, copy your Board Serial Number to your clipboard. You'll need it soon.
      In Rt Variables: Paste your Board Serial Number in the MLB field. Set CsrActiveConfig to 0x0 which enables SIP for extra security. This should work just fine for a Vanilla Hackintosh install and is how genuine Macs ship. In Boot: Change the Custom Flags to: shikigva=40 uia_exclude=HS14 (this disables onboard Bluetooth since we'll be using an external Broadcom Wi-Fi/Bluetooth adapter) In ACPI: Click List of Patches and enable the following: Change GFX0 to IGPU In Devices: Set Inject to 16. Now to enable our headless iGPU, we need to fake the device id. To do so, Click Properties, select PciRoot(0x0)/Pci(0x2,0x0). Then, click the + button to add a property. Add the following: Property Key: device-id Property Value: 923E0000 Value Type: DATA Click the Export Configuration button (bottom left), then Save As config.plist. Copy your newly generated config.plist to /EFI/CLOVER/ on your bootable USB key.  
      Impostazioni BIOS
       
      E avendo settato nel BIOS le impostazioni che questa perona configliava all'inizio della guida,                       (N.B. la mia versione di Bios è l'ultima, F7 https://www.gigabyte.com/Motherboard/Z390-AORUS-PRO-rev-10#support-dl-bios) (a quanto risulta il giorno 7.01.2019)
       
      Load Optimized Default Settings Peripherals → USB Configuration → XHCI Hand-off : Enabled Chipset → Internal Graphics : Enabled (important for Quicklook/Preview) Please note that we will be using our internal GPU in headless mode only and this guide assumes that. This is how an iMac18,3 (what we're basing our build on) behaves. That's it! I literally didn't change anything else and it just worked.
       
      Anche per me ha funzionato. Comunque lui riportava ulteriori settaggi, aggiungendo:
       
      However, these are settings that are generally recommended. Your mileage may vary:
       
      BIOS → Fast Boot : Disabled BIOS → LAN PXE Boot Option ROM : Disabled BIOS → Storage Boot Option Control : UEFI Peripherals → Trusted Computing → Security Device Support : Disable Peripherals → Network Stack Configuration → Network Stack : Disabled Peripherals → USB Configuration → Legacy USB Support : Auto Peripherals → USB Configuration → XHCI Hand-off : Enabled (Extremely important) () Chipset → Vt-d : Disabled (non l'ho messo e parte a volte, quindi penso che se parte non ha una importanza così rilevante) Chipset → Wake on LAN Enable : Disabled (era già così) Chipset → IOAPIC 24-119 Entries : Enabled  
       
      Il sistema è partito e soltanto alcune volte dava il seguente errore:
       
      Error allocating 0x11996pages at 0x000000001d453000 alloc type 2
      Couldn't allocate runtime area.
       
      Credo che sia questo piccolo problema: la NVRAM.
      Non riesco bene a capire dove cercare per sapere con esattezza se è supportato nativamente o meno. Ho cercato di informarmi, voi potreste dirmi se è vero?
      Premendo poi Ctrl+Alt+Canc riavviavo e selezionando da Clover l'NVMe interno partiva senza dare questo errore, per cui il kernel non trova spazio perché la memoria Non Volatile ad accesso Randomico è troppo frammentata, come
       
      Questa guida riportava:
       
      Primo post:
      https://nickwoodhams.com/x99-hackintosh-solving-osxaptiofixdrv-allocaterelocblock-can-not-allocate-relocation-block/
       
      Post aggiornato nel 2016:
      https://nickwoodhams.com/x99-hackintosh-osxaptiofixdrv-allocaterelocblock-error-update/
       
      Mi sono letto tutto e ho capito che lui applicava anche delle modifiche al file: "Changes to OsxLowMemFixDrv-64.efi were simply editing 0x10000000 to 0x20000000."
       
      Ho quindi seguito il suo consiglio di mettere OsxAptiofix Emuvariable 64 e Test2-2016.efi (che lui aveva creato) ma il problema sembrava persistere, più raramente
       
      La mia cartella driver64UEFI di ora
       
      Dopo aver trovato una strada senza soluzoni anche lì mi sono rivolto a degli amici, e di questo errore ne ho parlato anche con utenti del gruppo Telegram "Hackintosh Italia" che sono stati e ancora sono molto gentili ad aiutarmi spiegandomi che si tratta di un problema di NVRAM, che nel mio caso, avendo installato questi .efi file nella cartella EFI/EFI/CLOVER/driver64UEFI (che ancora è cosi attualmente, oscillando tra couldnt allocate runtime area (anche dopo aver definitivamente staccato la corrente dopo aver spento il PC per capire se poteva aiutare) e a volta anche nessun errore)
       
       
      -ApfsDriverLoader-64.efi
      -DataHubDxe-64.efi
      -EmuVariableUefi-64.efi
      -FSInject-64.efi
      -HFSPlus-64.efi
      -NTFS-64.efi
      -NvmExpressDxe-64.efi
      -OsxAptioFix2Drv-free2000.efi
      -PartitionDxe-64.efi
      -UsbKbDxe-64.efi
       
      In più ho aggiunto gli RC Scripts (come mi è stato consigliato dai membri del gruppo telegram) sul disco interno in cui mac è installato.
       
      Togliendo quindi qualsiasi test.efi o test2- 2016.efi ed ascoltando chi ne sapeva di più. Ora mi trovo a dover affrontare diverse volte questo errore dovendo riavviare per risolverlo, cosa che mi fa dedurre che Osxaptiofix2 2000 sia un po' instabile nel pulire la NVRAM prima di avviare la macchina/ allo spegnimento di questa.
      Questo problema di couldnt allocate runtime area persiste sebbene prema F12 dalla schermata di Boot di Clover.
       
      Vi chiedo gentilmente una mano, inoltre mi è stato detto che siccome il sistema da:
       
      -"3.6 GHz unknown nella sezione "Processor"
      -non riconosce la RAM con un Vendor ID? (del tipo Ballistix dovrebbe essere?)
       
       
      Serve di rivedere il config.plist che ho creato, rivedere i DSDT e gli efi? sono a posto?, (mi hanno detto che gengik84 fare, ma accolgo volentieri l'aiuto di tutti) ,  vi mando una foto della schermata di "About this Mac" e della EFI in allegato. Quello che farò sicuramente mentre attendo vostre risposte è il downgrade da 10.14.3 Beta a 10.14.2, l'upgrade l'ho fatto pensando che magari avrei aggiustato qualcosa, ma l'errore come lo dava prima lo dà ora, non credo che questo cambi molto le cose in gioco. Comunque è meglio non essere in Beta per aggiustare gli errori.
       
       
      Grazie mille per essere arrivato a leggere fino a questo punto, lo apprezzo molto.
       
       
      Per la cartella EFI: sono 22MB zippati, in allegato non entrano...
       
      https://drive.google.com/open?id=106jXkDB0Id045lzIIzAn9F5MwnzWFv3X
       

       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       

       
       
       
       



×