+- hashcat Forum (https://hashcat.net/forum)
+-- Forum: Support (https://hashcat.net/forum/forum-3.html)
+--- Forum: hashcat (https://hashcat.net/forum/forum-45.html)
+--- Thread: Hashcat see only 1 gpu - AMD RX470 rocm (/thread-7901.html)
Hashcat see only 1 gpu - AMD RX470 rocm - technobro - 10-27-2018
Hi guys ,
EDIT : i forgot to mention this is an old mining rig i just bough used
After 5-6 format i finally got rocm to cooperate . reading the FAQ ... etc
I can now run hashcat and it see the gpu , but it only see 1 . there are 5 gpu in the machine
Now my understanding is that before with amd driver we had to do this command to for hashcat to see them all
Code:
amdconfig --adapter=all --initial -fI was hoping somone can enlight me on that. thanks
the card are RX470 and RX570 and the cpu G4400
ubuntu 18.04
Code:
Linux x 4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10 10:59:38 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
root@x:/home/x/Desktop/hashcat-4.2.1# ./hashcat64.bin -b -m 1000 --force
hashcat (v4.2.1) starting in benchmark mode...
Benchmarking uses hand-optimized kernel code by default.
You can use it in your cracking session by setting the -O option.
Note: Using optimized kernel code limits the maximum supported password length.
To disable the optimized kernel code in benchmark mode, use the -w option.
OpenCL Platform #1: Advanced Micro Devices, Inc.
================================================
* Device #1: gfx803, 3481/4096 MB allocatable, 32MCU
Benchmark relevant options:
===========================
* --force
* --optimized-kernel-enable
Hashmode: 1000 - NTLM
Speed.Dev.#1.....: 20583.3 MH/s (51.29ms) @ Accel:256 Loops:512 Thr:256 Vec:1
Started: Sat Oct 27 09:21:43 2018
Stopped: Sat Oct 27 09:21:56 2018
root@x:/home/x/Desktop/hashcat-4.2.1# lspci | grep 570
root@x:/home/x/Desktop/hashcat-4.2.1# lspci | grep 470
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] (rev ef)
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] (rev ef)
05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] (rev ef)
06:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] (rev ef)
07:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] (rev ef)
08:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] (rev ef)RE: Hashcat see only 1 gpu - AMD RX470 rocm - undeath - 10-27-2018
why are you using --force? Do you have fglrx installed?
RE: Hashcat see only 1 gpu - AMD RX470 rocm - technobro - 10-27-2018
no actually i dont need it right.. just old habbits from running it on another computer without gpu.
in rocm it only see one as well
could it be somthing in the bios... this is an old mining rig i just bough use.
Code:
root@x:/home/x/Desktop/hashcat-4.2.1# /opt/rocm/bin/rocminfo
=====================
HSA System Attributes
=====================
Runtime Version: 1.1
System Timestamp Freq.: 1000.000000MHz
Sig. Max Wait Duration: 18446744073709551615 (number of timestamp)
Machine Model: LARGE
System Endianness: LITTLE
==========
HSA Agents
==========
*******
Agent 1
*******
Name: Intel(R) Pentium(R) CPU G4400 @ 3.30GHz
Vendor Name: CPU
Feature: None specified
Profile: FULL_PROFILE
Float Round Mode: NEAR
Max Queue Number: 0
Queue Min Size: 0
Queue Max Size: 0
Queue Type: MULTI
Node: 0
Device Type: CPU
Cache Info:
L1: 32768KB
Chip ID: 0
Cacheline Size: 64
Max Clock Frequency (MHz):3300
BDFID: 0
Compute Unit: 2
Features: None
Pool Info:
Pool 1
Segment: GLOBAL; FLAGS: KERNARG, FINE GRAINED
Size: 3910956KB
Allocatable: TRUE
Alloc Granule: 4KB
Alloc Alignment: 4KB
Acessible by all: TRUE
Pool 2
Segment: GLOBAL; FLAGS: COARSE GRAINED
Size: 3910956KB
Allocatable: TRUE
Alloc Granule: 4KB
Alloc Alignment: 4KB
Acessible by all: TRUE
ISA Info:
N/A
*******
Agent 2
*******
Name: gfx803
Vendor Name: AMD
Feature: KERNEL_DISPATCH
Profile: BASE_PROFILE
Float Round Mode: NEAR
Max Queue Number: 128
Queue Min Size: 4096
Queue Max Size: 131072
Queue Type: MULTI
Node: 1
Device Type: GPU
Cache Info:
L1: 16KB
Chip ID: 26591
Cacheline Size: 64
Max Clock Frequency (MHz):1281
BDFID: 256
Compute Unit: 32
Features: KERNEL_DISPATCH
Fast F16 Operation: FALSE
Wavefront Size: 64
Workgroup Max Size: 1024
Workgroup Max Size Per Dimension:
Dim[0]: 67109888
Dim[1]: 16778240
Dim[2]: 0
Grid Max Size: 4294967295
Waves Per CU: 40
Max Work-item Per CU: 2560
Grid Max Size per Dimension:
Dim[0]: 4294967295
Dim[1]: 4294967295
Dim[2]: 4294967295
Max number Of fbarriers Per Workgroup:32
Pool Info:
Pool 1
Segment: GLOBAL; FLAGS: COARSE GRAINED
Size: 4194304KB
Allocatable: TRUE
Alloc Granule: 4KB
Alloc Alignment: 4KB
Acessible by all: FALSE
Pool 2
Segment: GROUP
Size: 64KB
Allocatable: FALSE
Alloc Granule: 0KB
Alloc Alignment: 0KB
Acessible by all: FALSE
ISA Info:
ISA 1
Name: amdgcn-amd-amdhsa--gfx803
Machine Models: HSA_MACHINE_MODEL_LARGE
Profiles: HSA_PROFILE_BASE
Default Rounding Mode: NEAR
Default Rounding Mode: NEAR
Fast f16: TRUE
Workgroup Max Dimension:
Dim[0]: 67109888
Dim[1]: 1024
Dim[2]: 16777217
Workgroup Max Size: 1024
Grid Max Dimension:
x 4294967295
y 4294967295
z 4294967295
Grid Max Size: 4294967295
FBarrier Max Size: 32
*** Done ***
root@x:/home/x/Desktop/hashcat-4.2.1# lspci | grep 470
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] (rev ef)
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] (rev ef)
05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] (rev ef)
06:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] (rev ef)
07:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] (rev ef)
08:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] (rev ef)
root@x:/home/x/Desktop/hashcat-4.2.1#RE: Hashcat see only 1 gpu - AMD RX470 rocm - technobro - 10-27-2018
Do poking around in the logs i found this suspicious
cat /var/log/kern.logcat /var/log/kern.log
Code:
Oct 27 08:56:02 x kernel: [ 36.065580] pcieport 0000:00:1c.4: device [8086:a294] error status/mask=00000001/00002000
Oct 27 08:56:02 x kernel: [ 36.065581] pcieport 0000:00:1c.4: [ 0] Receiver Error (First)
Oct 27 08:56:02 x kernel: [ 36.065829] pcieport 0000:00:1c.3: AER: Corrected error received: id=00e3
Oct 27 08:56:02 x kernel: [ 36.065833] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e3(Receiver ID)
Oct 27 08:56:02 x kernel: [ 36.065834] pcieport 0000:00:1c.3: device [8086:a293] error status/mask=00000001/00002000
Oct 27 08:56:02 x kernel: [ 36.065836] pcieport 0000:00:1c.3: [ 0] Receiver Error (First)
Oct 27 08:56:02 x kernel: [ 36.066797] pcieport 0000:00:1c.3: AER: Corrected error received: id=00e3
Oct 27 08:56:02 x kernel: [ 36.066801] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e3(Receiver ID)
Oct 27 08:56:02 x kernel: [ 36.066802] pcieport 0000:00:1c.3: device [8086:a293] error status/mask=00000001/00002000
Oct 27 08:56:02 x kernel: [ 36.066803] pcieport 0000:00:1c.3: [ 0] Receiver Error (First)
Oct 27 08:56:02 x kernel: [ 36.067117] pcieport 0000:00:1c.3: AER: Corrected error received: id=00e3
Oct 27 08:56:02 x kernel: [ 36.067120] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e3(Receiver ID)
Oct 27 08:56:02 x kernel: [ 36.067122] pcieport 0000:00:1c.3: device [8086:a293] error status/mask=00000001/00002000
Oct 27 08:56:02 x kernel: [ 36.067123] pcieport 0000:00:1c.3: [ 0] Receiver Error (First)
Oct 27 08:56:02 x kernel: [ 36.067197] pcieport 0000:00:1c.3: AER: Corrected error received: id=00e3
Oct 27 08:56:02 x kernel: [ 36.067201] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e3(Receiver ID)
Oct 27 08:56:02 x kernel: [ 36.067202] pcieport 0000:00:1c.3: device [8086:a293] error status/mask=00000001/00002000
Oct 27 08:56:02 x kernel: [ 36.067204] pcieport 0000:00:1c.3: [ 0] Receiver Error (First)
Oct 27 08:56:02 x kernel: [ 36.067305] pcieport 0000:00:1c.3: AER: Corrected error received: id=00e3
Oct 27 08:56:02 x kernel: [ 36.067308] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e3(Receiver ID)
Oct 27 08:56:02 x kernel: [ 36.067310] pcieport 0000:00:1c.3: device [8086:a293] error status/mask=00000001/00002000
Oct 27 08:56:02 x kernel: [ 36.067311] pcieport 0000:00:1c.3: [ 0] Receiver Error (First)
Oct 27 08:56:02 x kernel: [ 36.067983] pcieport 0000:00:1c.3: AER: Corrected error received: id=00e3
Oct 27 08:56:02 x kernel: [ 36.067987] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e3(Receiver ID)
Oct 27 08:56:02 x kernel: [ 36.067989] pcieport 0000:00:1c.3: device [8086:a293] error status/mask=00000001/00002000
Oct 27 08:56:02 x kernel: [ 36.067990] pcieport 0000:00:1c.3: [ 0] Receiver Error (First)
Oct 27 08:56:02 x kernel: [ 36.068135] pcieport 0000:00:1c.3: AER: Corrected error received: id=00e3
Oct 27 08:56:02 x kernel: [ 36.068139] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e3(Receiver ID)
Oct 27 08:56:02 x kernel: [ 36.068141] pcieport 0000:00:1c.3: device [8086:a293] error status/mask=00000001/00002000
Oct 27 08:56:02 x kernel: [ 36.068143] pcieport 0000:00:1c.3: [ 0] Receiver Error (First)
Oct 27 08:56:02 x kernel: [ 36.068194] pcieport 0000:00:1c.3: AER: Corrected error received: id=00e3
Oct 27 08:56:02 x kernel: [ 36.068195] pcieport 0000:00:1c.4: AER: Corrected error received: id=00e4
Oct 27 08:56:02 x kernel: [ 36.068198] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e3(Receiver ID)
Oct 27 08:56:02 x kernel: [ 36.068200] pcieport 0000:00:1c.3: device [8086:a293] error status/mask=00000001/00002000
Oct 27 08:56:02 x kernel: [ 36.068200] pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e4(Receiver ID)
Oct 27 08:56:02 x kernel: [ 36.068202] pcieport 0000:00:1c.4: device [8086:a294] error status/mask=00000001/00002000
Oct 27 08:56:02 x kernel: [ 36.068203] pcieport 0000:00:1c.4: [ 0] Receiver Error (First)
Oct 27 08:56:02 x kernel: [ 36.068205] pcieport 0000:00:1c.3: [ 0] Receiver Error (First)
Oct 27 08:56:02 x kernel: [ 36.068715] pcieport 0000:00:1c.3: AER: Corrected error received: id=00e3
Oct 27 08:56:02 x kernel: [ 36.068719] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e3(Receiver ID)
Oct 27 08:56:02 x kernel: [ 36.068720] pcieport 0000:00:1c.3: device [8086:a293] error status/mask=00000001/00002000
Oct 27 08:56:02 x kernel: [ 36.068721] pcieport 0000:00:1c.3: [ 0] Receiver Error (First)
Oct 27 08:56:02 x kernel: [ 36.069236] pcieport 0000:00:1c.3: AER: Corrected error received: id=00e3
Oct 27 08:56:02 x kernel: [ 36.069240] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e3(Receiver ID)
Oct 27 08:56:02 x kernel: [ 36.069242] pcieport 0000:00:1c.3: device [8086:a293] error status/mask=00000001/00002000
Oct 27 08:56:02 x kernel: [ 36.069243] pcieport 0000:00:1c.3: [ 0] Receiver Error (First)
Oct 27 08:56:02 x kernel: [ 36.083287] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Oct 27 08:56:02 x kernel: [ 36.083292] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Oct 27 08:56:02 x kernel: [ 36.083295] pcieport 0000:00:1c.5: device [8086:a295] error status/mask=00000001/00002000
Oct 27 08:56:02 x kernel: [ 36.083297] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Oct 27 08:56:02 x kernel: [ 36.110698] pcieport 0000:00:1c.6: AER: Corrected error received: id=00e6
Oct 27 08:56:02 x kernel: [ 36.110709] pcieport 0000:00:1c.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e6(Receiver ID)
Oct 27 08:56:02 x kernel: [ 36.110719] pcieport 0000:00:1c.6: device [8086:a296] error status/mask=00000001/00002000
Oct 27 08:56:02 x kernel: [ 36.110726] pcieport 0000:00:1c.6: [ 0] Receiver Error (First)
Oct 27 08:56:02 x kernel: [ 36.114470] pcieport 0000:00:1c.6: AER: Corrected error received: id=00e6
Oct 27 08:56:02 x kernel: [ 36.114481] pcieport 0000:00:1c.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e6(Receiver ID)
Oct 27 08:56:02 x kernel: [ 36.114491] pcieport 0000:00:1c.6: device [8086:a296] error status/mask=00000001/00002000
Oct 27 08:56:02 x kernel: [ 36.114498] pcieport 0000:00:1c.6: [ 0] Receiver Error (First)
Oct 27 08:56:02 x kernel: [ 36.127667] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Oct 27 08:56:02 x kernel: [ 36.127672] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Oct 27 08:56:02 x kernel: [ 36.127674] pcieport 0000:00:1c.5: device [8086:a295] error status/mask=00000001/00002000
Oct 27 08:56:02 x kernel: [ 36.127675] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Oct 27 08:56:02 x kernel: [ 36.135340] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Oct 27 08:56:02 x kernel: [ 36.135350] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Oct 27 08:56:02 x kernel: [ 36.135358] pcieport 0000:00:1c.5: device [8086:a295] error status/mask=00000001/00002000
Oct 27 08:56:02 x kernel: [ 36.135365] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Oct 27 08:56:02 x kernel: [ 36.147980] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Oct 27 08:56:02 x kernel: [ 36.147984] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Oct 27 08:56:02 x kernel: [ 36.147986] pcieport 0000:00:1c.5: device [8086:a295] error status/mask=00000001/00002000
Oct 27 08:56:02 x kernel: [ 36.147987] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Oct 27 08:56:02 x kernel: [ 36.157033] pcieport 0000:00:1c.6: AER: Corrected error received: id=00e6
Oct 27 08:56:02 x kernel: [ 36.157044] pcieport 0000:00:1c.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e6(Receiver ID)
Oct 27 08:56:02 x kernel: [ 36.157054] pcieport 0000:00:1c.6: device [8086:a296] error status/mask=00000001/00002000
Oct 27 08:56:02 x kernel: [ 36.157061] pcieport 0000:00:1c.6: [ 0] Receiver Error (First)
Oct 27 08:56:07 x kernel: [ 40.874544] IPv6: ADDRCONF(NETDEV_UP): enp9s0: link is not ready
Oct 27 08:56:07 x kernel: [ 40.978970] r8169 0000:09:00.0 enp9s0: link down
Oct 27 08:56:07 x kernel: [ 40.979004] r8169 0000:09:00.0 enp9s0: link down
Oct 27 08:56:07 x kernel: [ 40.979222] IPv6: ADDRCONF(NETDEV_UP): enp9s0: link is not ready
Oct 27 08:56:10 x kernel: [ 43.966554] r8169 0000:09:00.0 enp9s0: link up
Oct 27 08:56:10 x kernel: [ 43.966562] IPv6: ADDRCONF(NETDEV_CHANGE): enp9s0: link becomes ready
Oct 27 08:56:21 x kernel: [ 55.303084] rfkill: input handler disabled
Oct 27 08:57:07 x kernel: [ 100.991207] amdgpu: [powerplay]
Oct 27 08:57:07 x kernel: [ 100.991207] failed to send message 18a ret is 0
Oct 27 08:57:07 x kernel: [ 101.345307] amdgpu: [powerplay]
Oct 27 08:57:07 x kernel: [ 101.345307] last message was failed ret is 0
Oct 27 08:57:07 x kernel: [ 101.699391] amdgpu: [powerplay]
Oct 27 08:57:07 x kernel: [ 101.699391] failed to send message 18b ret is 0
Oct 27 08:57:08 x kernel: [ 102.053452] amdgpu: [powerplay]
Oct 27 08:57:08 x kernel: [ 102.053452] last message was failed ret is 0
Oct 27 08:57:08 x kernel: [ 102.407558] amdgpu: [powerplay]
Oct 27 08:57:08 x kernel: [ 102.407558] failed to send message 18c ret is 0
Oct 27 08:57:09 x kernel: [ 103.115709] amdgpu: [powerplay]
Oct 27 08:57:09 x kernel: [ 103.115709] last message was failed ret is 0
Oct 27 08:57:09 x kernel: [ 103.469773] amdgpu: [powerplay]
Oct 27 08:57:09 x kernel: [ 103.469773] failed to send message 145 ret is 0
Oct 27 08:57:41 x kernel: [ 135.001688] amdgpu: [powerplay]
Oct 27 08:57:41 x kernel: [ 135.001688] last message was failed ret is 0
Oct 27 08:57:41 x kernel: [ 135.355858] amdgpu: [powerplay]
Oct 27 08:57:41 x kernel: [ 135.355858] failed to send message 189 ret is 0
Oct 27 08:57:42 x kernel: [ 135.710004] amdgpu: [powerplay]
Oct 27 08:57:42 x kernel: [ 135.710004] last message was failed ret is 0
Oct 27 08:57:42 x kernel: [ 136.064151] amdgpu: [powerplay]
Oct 27 08:57:42 x kernel: [ 136.064151] failed to send message 18a ret is 0
Oct 27 08:57:43 x kernel: [ 136.772411] amdgpu: [powerplay]
Oct 27 08:57:43 x kernel: [ 136.772411] last message was failed ret is 0
Oct 27 08:57:43 x kernel: [ 137.126557] amdgpu: [powerplay]
Oct 27 08:57:43 x kernel: [ 137.126557] failed to send message 145 ret is 0
Oct 27 08:57:53 x kernel: [ 147.479073] amdgpu: [powerplay]
Oct 27 08:57:53 x kernel: [ 147.479073] last message was failed ret is 0
Oct 27 08:57:54 x kernel: [ 147.833172] amdgpu: [powerplay]
Oct 27 08:57:54 x kernel: [ 147.833172] failed to send message 189 ret is 0
Oct 27 08:57:54 x kernel: [ 148.187301] amdgpu: [powerplay]
Oct 27 08:57:54 x kernel: [ 148.187301] last message was failed ret is 0
Oct 27 08:57:54 x kernel: [ 148.541423] amdgpu: [powerplay]
Oct 27 08:57:54 x kernel: [ 148.541423] failed to send message 18a ret is 0
Oct 27 08:57:55 x kernel: [ 148.895562] amdgpu: [powerplay]
Oct 27 08:57:55 x kernel: [ 148.895562] last message was failed ret is 0
Oct 27 08:57:55 x kernel: [ 149.249693] amdgpu: [powerplay]
Oct 27 08:57:55 x kernel: [ 149.249693] failed to send message 18b ret is 0
Oct 27 08:57:55 x kernel: [ 149.603847] amdgpu: [powerplay]
Oct 27 08:57:55 x kernel: [ 149.603847] last message was failed ret is 0
Oct 27 08:57:56 x kernel: [ 149.957977] amdgpu: [powerplay]
Oct 27 08:57:56 x kernel: [ 149.957977] failed to send message 18c ret is 0
Oct 27 08:57:56 x kernel: [ 150.666228] amdgpu: [powerplay]
Oct 27 08:57:56 x kernel: [ 150.666228] last message was failed ret is 0
Oct 27 08:57:57 x kernel: [ 151.020357] amdgpu: [powerplay]
Oct 27 08:57:57 x kernel: [ 151.020357] failed to send message 145 ret is 0
Oct 27 08:59:18 x kernel: [ 232.082972] amdgpu: [powerplay]
Oct 27 08:59:18 x kernel: [ 232.082972] last message was failed ret is 0
Oct 27 08:59:18 x kernel: [ 232.437060] amdgpu: [powerplay]
Oct 27 08:59:18 x kernel: [ 232.437060] failed to send message 189 ret is 0
Oct 27 08:59:19 x kernel: [ 232.791155] amdgpu: [powerplay]
Oct 27 08:59:19 x kernel: [ 232.791155] last message was failed ret is 0
Oct 27 08:59:19 x kernel: [ 233.145237] amdgpu: [powerplay]
Oct 27 08:59:19 x kernel: [ 233.145237] failed to send message 18a ret is 0
Oct 27 08:59:20 x kernel: [ 233.853391] amdgpu: [powerplay]
Oct 27 08:59:20 x kernel: [ 233.853391] last message was failed ret is 0
Oct 27 08:59:20 x kernel: [ 234.207474] amdgpu: [powerplay]
Oct 27 08:59:20 x kernel: [ 234.207474] failed to send message 145 ret is 0
Oct 27 08:59:20 x kernel: [ 234.609060] amdgpu: [powerplay]
Oct 27 08:59:20 x kernel: [ 234.609060] last message was failed ret is 0
Oct 27 08:59:21 x kernel: [ 234.963141] amdgpu: [powerplay]
Oct 27 08:59:21 x kernel: [ 234.963141] failed to send message 189 ret is 0
Oct 27 08:59:21 x kernel: [ 235.317245] amdgpu: [powerplay]
Oct 27 08:59:21 x kernel: [ 235.317245] last message was failed ret is 0
Oct 27 08:59:21 x kernel: [ 235.671335] amdgpu: [powerplay]RE: Hashcat see only 1 gpu - AMD RX470 rocm - technobro - 10-27-2018
ok so little update i upgraded the bios to the last version, and setup the bios as per mining rig using this tuto https://blockoperations.com/motherboard-bios-settings-for-asus-z270-a-and-z270-p/
it get rid the error in kernel.log
But i still only see one gpu in rocminfo, or hashcat
in the mining tuto they set the pcie to 2x , is this ok ?
RE: Hashcat see only 1 gpu - AMD RX470 rocm - technobro - 10-27-2018
i notice when i run hashcat i get this in
kernel.log
Oct 27 11:39:29 x kernel: [ 292.666346] amdgpu: [powerplay]
Oct 27 11:39:29 x kernel: [ 292.666346] failed to send message 145 ret is 0
Oct 27 11:39:29 x kernel: [ 293.072037] amdgpu: [powerplay]
Oct 27 11:39:29 x kernel: [ 293.072037] last message was failed ret is 0
Oct 27 11:39:30 x kernel: [ 293.426088] amdgpu: [powerplay]
Oct 27 11:39:30 x kernel: [ 293.426088] failed to send message 189 ret is 0
Oct 27 11:39:30 x kernel: [ 293.780168] amdgpu: [powerplay]
Oct 27 11:39:30 x kernel: [ 293.780168] last message was failed ret is 0
Oct 27 11:39:30 x kernel: [ 294.134225] amdgpu: [powerplay]
Oct 27 11:39:30 x kernel: [ 294.134225] failed to send message 18a ret is 0
Oct 27 11:39:31 x kernel: [ 294.488322] amdgpu: [powerplay]
Oct 27 11:39:31 x kernel: [ 294.488322] last message was failed ret is 0
Oct 27 11:39:31 x kernel: [ 294.842383] amdgpu: [powerplay]
Oct 27 11:39:31 x kernel: [ 294.842383] failed to send message 18b ret is 0
Oct 27 11:39:31 x kernel: [ 295.196427] amdgpu: [powerplay]
Oct 27 11:39:31 x kernel: [ 295.196427] last message was failed ret is 0
Oct 27 11:39:32 x kernel: [ 295.550513] amdgpu: [powerplay]
Oct 27 11:39:32 x kernel: [ 295.550513] failed to send message 18c ret is 0
Oct 27 11:39:32 x kernel: [ 296.258638] amdgpu: [powerplay]
Oct 27 11:39:32 x kernel: [ 296.258638] last message was failed ret is 0
Oct 27 11:39:33 x kernel: [ 296.612694] amdgpu: [powerplay]
Oct 27 11:39:33 x kernel: [ 296.612694] failed to send message 145 ret is 0
RE: Hashcat see only 1 gpu - AMD RX470 rocm - technobro - 10-27-2018
using the usb flash that came with the rig , i can see that it mines on all cards
RE: Hashcat see only 1 gpu - AMD RX470 rocm - technobro - 10-27-2018
so the problem seems to be atomic
anyone found a solution for that ?
root@x:/home/x# dmesg | grep kfd
[ 1.574252] kfd kfd: Initialized module
[ 3.171005] kfd kfd: Allocated 3969056 bytes on gart
[ 3.171104] kfd kfd: added device 1002:67df
[ 3.176243] kfd kfd: skipped device 1002:67df, PCI rejects atomics
[ 4.806404] kfd kfd: skipped device 1002:67df, PCI rejects atomics
[ 6.438475] kfd kfd: skipped device 1002:67df, PCI rejects atomics
[ 8.070061] kfd kfd: skipped device 1002:67df, PCI rejects atomics
[ 9.698513] kfd kfd: skipped device 1002:67df, PCI rejects atomics
RE: Hashcat see only 1 gpu - AMD RX470 rocm - technobro - 10-27-2018
So apparently this is due to the fact that my cpu have limited pcie lane configuration /my mb and it looks like i am not gonna be able to use rocm.
here the thread for reference over rocm git
https://github.com/RadeonOpenCompute/ROCm
RE: Hashcat see only 1 gpu - AMD RX470 rocm - technobro - 10-28-2018
(10-27-2018, 09:09 PM)technobro Wrote: So apparently this is due to the fact that my cpu have limited pcie lane configuration /my mb and it looks like i am not gonna be able to use rocm.
here the thread for reference over rocm git
https://github.com/RadeonOpenCompute/ROCm
Guys no one encounter that ?