Search content
Sort by
Showing 9 of 9 results by EncinoMan
Re: [Mining OS] SimpleMining.net - Easy to use GPU MINING Operating System
Mining with Claymore and get full HDD (128GB SSD) in half hour.
After checking find /var/log/syslog and kern.log grown up to 52GB each.
System write this 4 messages about 4-5 thousands per second !
Despite this mine worked properly 24.3 MH/s on each card until the disk is full
Someone also stumbled upon a similar problem?
System:
Lubuntu 16.04 with amdgpu-pro_16.30.3
5x RX 480 8GB ref model
Asrock FM2A88X + BTC
After checking find /var/log/syslog and kern.log grown up to 52GB each.
System write this 4 messages about 4-5 thousands per second !
Code:
Jul 9 23:58:37 test-rig kernel: [ 1399.017519] VM fault (0x01, vmid 6) at page 135290427, read from 'TC3' (0x54433300) (196)
Jul 9 23:58:37 test-rig kernel: [ 1399.017554] amdgpu 0000:04:00.0: GPU fault detected: 147 0x01c84801
Jul 9 23:58:37 test-rig kernel: [ 1399.017557] amdgpu 0000:04:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x08105E39
Jul 9 23:58:37 test-rig kernel: [ 1399.017559] amdgpu 0000:04:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0C048001
Jul 9 23:58:37 test-rig kernel: [ 1399.017561] VM fault (0x01, vmid 6) at page 135290425, read from 'TC4' (0x54433400) (72)
Jul 9 23:58:37 test-rig kernel: [ 1399.017567] amdgpu 0000:01:00.0: GPU fault detected: 147 0x01f08801
Jul 9 23:58:37 test-rig kernel: [ 1399.017569] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x08105E3E
Jul 9 23:58:37 test-rig kernel: [ 1399.017570] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0C088001
Jul 9 23:58:37 test-rig kernel: [ 1399.017572] VM fault (0x01, vmid 6) at page 135290430, read from 'TC6' (0x54433600) (136)
Jul 9 23:58:37 test-rig kernel: [ 1399.017607] amdgpu 0000:04:00.0: GPU fault detected: 147 0x01e84801
Jul 9 23:58:37 test-rig kernel: [ 1399.017610] amdgpu 0000:04:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x08105E3D
Jul 9 23:58:37 test-rig kernel: [ 1399.017612] amdgpu 0000:04:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0C048001
Jul 9 23:58:37 test-rig kernel: [ 1399.017554] amdgpu 0000:04:00.0: GPU fault detected: 147 0x01c84801
Jul 9 23:58:37 test-rig kernel: [ 1399.017557] amdgpu 0000:04:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x08105E39
Jul 9 23:58:37 test-rig kernel: [ 1399.017559] amdgpu 0000:04:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0C048001
Jul 9 23:58:37 test-rig kernel: [ 1399.017561] VM fault (0x01, vmid 6) at page 135290425, read from 'TC4' (0x54433400) (72)
Jul 9 23:58:37 test-rig kernel: [ 1399.017567] amdgpu 0000:01:00.0: GPU fault detected: 147 0x01f08801
Jul 9 23:58:37 test-rig kernel: [ 1399.017569] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x08105E3E
Jul 9 23:58:37 test-rig kernel: [ 1399.017570] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0C088001
Jul 9 23:58:37 test-rig kernel: [ 1399.017572] VM fault (0x01, vmid 6) at page 135290430, read from 'TC6' (0x54433600) (136)
Jul 9 23:58:37 test-rig kernel: [ 1399.017607] amdgpu 0000:04:00.0: GPU fault detected: 147 0x01e84801
Jul 9 23:58:37 test-rig kernel: [ 1399.017610] amdgpu 0000:04:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x08105E3D
Jul 9 23:58:37 test-rig kernel: [ 1399.017612] amdgpu 0000:04:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0C048001
Despite this mine worked properly 24.3 MH/s on each card until the disk is full
Someone also stumbled upon a similar problem?
System:
Lubuntu 16.04 with amdgpu-pro_16.30.3
5x RX 480 8GB ref model
Asrock FM2A88X + BTC
Hi, i have the same problem in my new project : http://simplemining.net/
Anyway it doesnt bother mining and about logs you can turn then off:
as root execute this command and you will have no longer such problem
systemctl disable rsyslog.servicethen delete big file logs from /var/log/ adn reboot system, then it will work fine.
If you want i will release my http://simplemining.net/ Operating System which will have this fix and many more + feature updates.
If you want make donation BTC: 1ERRVbvV23h51ScH73nQr6TDmaieKNuuVD
Can someone please clarify what Tytanick means here? Is this only for independent Linux users and not Simplemining users?
I am using Simplemining.net and I get these error messages with four out of six RX480s.
Fixes I have tried:
I have the -dbg -1 code in the config text in the global options window.
I have tried each card with risers that I know are stable because they work with two of my cards.
I have tried various versions of drivers and kernels but found no difference with these errors.
I still am thinking that it is a driver/kernel issue but I have run out of options that I know to try.
Please help!
Only Tytanick could think suppressing an actual fairly serious warning is a "feature."
It's a high memclk and/or very tight VBIOS GDDR5 timings. It's causing memory errors.
My memory clock on Simpleminer is set at stock: 2000MHz (8000Mhz GDDR5). So should I learn how to decode the timing values from the HEX code? Or can I just alter the timings in Simplemining?
Have you flashed a diff VBIOS? If not, then Tytanick is probably using AMDGPU firmware and/or a kernel that is older than Jesus.
Damn it. The BIOS page for my card is offline atm. Anything else while I wait (perhaps for quite some time)? I know there was the other well known atikmdag-patcher-1.4.5 which was a kernel issue, but this wouldn't even install without crashes on my system, which no other driver has. Are there any other patches out there?
Re: [Mining OS] SimpleMining.net - Easy to use GPU MINING Operating System
Mining with Claymore and get full HDD (128GB SSD) in half hour.
After checking find /var/log/syslog and kern.log grown up to 52GB each.
System write this 4 messages about 4-5 thousands per second !
Despite this mine worked properly 24.3 MH/s on each card until the disk is full
Someone also stumbled upon a similar problem?
System:
Lubuntu 16.04 with amdgpu-pro_16.30.3
5x RX 480 8GB ref model
Asrock FM2A88X + BTC
After checking find /var/log/syslog and kern.log grown up to 52GB each.
System write this 4 messages about 4-5 thousands per second !
Code:
Jul 9 23:58:37 test-rig kernel: [ 1399.017519] VM fault (0x01, vmid 6) at page 135290427, read from 'TC3' (0x54433300) (196)
Jul 9 23:58:37 test-rig kernel: [ 1399.017554] amdgpu 0000:04:00.0: GPU fault detected: 147 0x01c84801
Jul 9 23:58:37 test-rig kernel: [ 1399.017557] amdgpu 0000:04:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x08105E39
Jul 9 23:58:37 test-rig kernel: [ 1399.017559] amdgpu 0000:04:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0C048001
Jul 9 23:58:37 test-rig kernel: [ 1399.017561] VM fault (0x01, vmid 6) at page 135290425, read from 'TC4' (0x54433400) (72)
Jul 9 23:58:37 test-rig kernel: [ 1399.017567] amdgpu 0000:01:00.0: GPU fault detected: 147 0x01f08801
Jul 9 23:58:37 test-rig kernel: [ 1399.017569] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x08105E3E
Jul 9 23:58:37 test-rig kernel: [ 1399.017570] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0C088001
Jul 9 23:58:37 test-rig kernel: [ 1399.017572] VM fault (0x01, vmid 6) at page 135290430, read from 'TC6' (0x54433600) (136)
Jul 9 23:58:37 test-rig kernel: [ 1399.017607] amdgpu 0000:04:00.0: GPU fault detected: 147 0x01e84801
Jul 9 23:58:37 test-rig kernel: [ 1399.017610] amdgpu 0000:04:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x08105E3D
Jul 9 23:58:37 test-rig kernel: [ 1399.017612] amdgpu 0000:04:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0C048001
Jul 9 23:58:37 test-rig kernel: [ 1399.017554] amdgpu 0000:04:00.0: GPU fault detected: 147 0x01c84801
Jul 9 23:58:37 test-rig kernel: [ 1399.017557] amdgpu 0000:04:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x08105E39
Jul 9 23:58:37 test-rig kernel: [ 1399.017559] amdgpu 0000:04:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0C048001
Jul 9 23:58:37 test-rig kernel: [ 1399.017561] VM fault (0x01, vmid 6) at page 135290425, read from 'TC4' (0x54433400) (72)
Jul 9 23:58:37 test-rig kernel: [ 1399.017567] amdgpu 0000:01:00.0: GPU fault detected: 147 0x01f08801
Jul 9 23:58:37 test-rig kernel: [ 1399.017569] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x08105E3E
Jul 9 23:58:37 test-rig kernel: [ 1399.017570] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0C088001
Jul 9 23:58:37 test-rig kernel: [ 1399.017572] VM fault (0x01, vmid 6) at page 135290430, read from 'TC6' (0x54433600) (136)
Jul 9 23:58:37 test-rig kernel: [ 1399.017607] amdgpu 0000:04:00.0: GPU fault detected: 147 0x01e84801
Jul 9 23:58:37 test-rig kernel: [ 1399.017610] amdgpu 0000:04:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x08105E3D
Jul 9 23:58:37 test-rig kernel: [ 1399.017612] amdgpu 0000:04:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0C048001
Despite this mine worked properly 24.3 MH/s on each card until the disk is full
Someone also stumbled upon a similar problem?
System:
Lubuntu 16.04 with amdgpu-pro_16.30.3
5x RX 480 8GB ref model
Asrock FM2A88X + BTC
Hi, i have the same problem in my new project : http://simplemining.net/
Anyway it doesnt bother mining and about logs you can turn then off:
as root execute this command and you will have no longer such problem
systemctl disable rsyslog.servicethen delete big file logs from /var/log/ adn reboot system, then it will work fine.
If you want i will release my http://simplemining.net/ Operating System which will have this fix and many more + feature updates.
If you want make donation BTC: 1ERRVbvV23h51ScH73nQr6TDmaieKNuuVD
Can someone please clarify what Tytanick means here? Is this only for independent Linux users and not Simplemining users?
I am using Simplemining.net and I get these error messages with four out of six RX480s.
Fixes I have tried:
I have the -dbg -1 code in the config text in the global options window.
I have tried each card with risers that I know are stable because they work with two of my cards.
I have tried various versions of drivers and kernels but found no difference with these errors.
I still am thinking that it is a driver/kernel issue but I have run out of options that I know to try.
Please help!
Only Tytanick could think suppressing an actual fairly serious warning is a "feature."
It's a high memclk and/or very tight VBIOS GDDR5 timings. It's causing memory errors.
My memory clock on Simpleminer is set at stock: 2000MHz (8000Mhz GDDR5). So should I learn how to decode the timing values from the HEX code? Or can I just alter the timings in Simplemining?
Re: [Mining OS] SimpleMining.net - Easy to use GPU MINING Operating System
Mining with Claymore and get full HDD (128GB SSD) in half hour.
After checking find /var/log/syslog and kern.log grown up to 52GB each.
System write this 4 messages about 4-5 thousands per second !
Despite this mine worked properly 24.3 MH/s on each card until the disk is full
Someone also stumbled upon a similar problem?
System:
Lubuntu 16.04 with amdgpu-pro_16.30.3
5x RX 480 8GB ref model
Asrock FM2A88X + BTC
After checking find /var/log/syslog and kern.log grown up to 52GB each.
System write this 4 messages about 4-5 thousands per second !
Code:
Jul 9 23:58:37 test-rig kernel: [ 1399.017519] VM fault (0x01, vmid 6) at page 135290427, read from 'TC3' (0x54433300) (196)
Jul 9 23:58:37 test-rig kernel: [ 1399.017554] amdgpu 0000:04:00.0: GPU fault detected: 147 0x01c84801
Jul 9 23:58:37 test-rig kernel: [ 1399.017557] amdgpu 0000:04:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x08105E39
Jul 9 23:58:37 test-rig kernel: [ 1399.017559] amdgpu 0000:04:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0C048001
Jul 9 23:58:37 test-rig kernel: [ 1399.017561] VM fault (0x01, vmid 6) at page 135290425, read from 'TC4' (0x54433400) (72)
Jul 9 23:58:37 test-rig kernel: [ 1399.017567] amdgpu 0000:01:00.0: GPU fault detected: 147 0x01f08801
Jul 9 23:58:37 test-rig kernel: [ 1399.017569] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x08105E3E
Jul 9 23:58:37 test-rig kernel: [ 1399.017570] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0C088001
Jul 9 23:58:37 test-rig kernel: [ 1399.017572] VM fault (0x01, vmid 6) at page 135290430, read from 'TC6' (0x54433600) (136)
Jul 9 23:58:37 test-rig kernel: [ 1399.017607] amdgpu 0000:04:00.0: GPU fault detected: 147 0x01e84801
Jul 9 23:58:37 test-rig kernel: [ 1399.017610] amdgpu 0000:04:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x08105E3D
Jul 9 23:58:37 test-rig kernel: [ 1399.017612] amdgpu 0000:04:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0C048001
Jul 9 23:58:37 test-rig kernel: [ 1399.017554] amdgpu 0000:04:00.0: GPU fault detected: 147 0x01c84801
Jul 9 23:58:37 test-rig kernel: [ 1399.017557] amdgpu 0000:04:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x08105E39
Jul 9 23:58:37 test-rig kernel: [ 1399.017559] amdgpu 0000:04:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0C048001
Jul 9 23:58:37 test-rig kernel: [ 1399.017561] VM fault (0x01, vmid 6) at page 135290425, read from 'TC4' (0x54433400) (72)
Jul 9 23:58:37 test-rig kernel: [ 1399.017567] amdgpu 0000:01:00.0: GPU fault detected: 147 0x01f08801
Jul 9 23:58:37 test-rig kernel: [ 1399.017569] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x08105E3E
Jul 9 23:58:37 test-rig kernel: [ 1399.017570] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0C088001
Jul 9 23:58:37 test-rig kernel: [ 1399.017572] VM fault (0x01, vmid 6) at page 135290430, read from 'TC6' (0x54433600) (136)
Jul 9 23:58:37 test-rig kernel: [ 1399.017607] amdgpu 0000:04:00.0: GPU fault detected: 147 0x01e84801
Jul 9 23:58:37 test-rig kernel: [ 1399.017610] amdgpu 0000:04:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x08105E3D
Jul 9 23:58:37 test-rig kernel: [ 1399.017612] amdgpu 0000:04:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0C048001
Despite this mine worked properly 24.3 MH/s on each card until the disk is full
Someone also stumbled upon a similar problem?
System:
Lubuntu 16.04 with amdgpu-pro_16.30.3
5x RX 480 8GB ref model
Asrock FM2A88X + BTC
Hi, i have the same problem in my new project : http://simplemining.net/
Anyway it doesnt bother mining and about logs you can turn then off:
as root execute this command and you will have no longer such problem
systemctl disable rsyslog.servicethen delete big file logs from /var/log/ adn reboot system, then it will work fine.
If you want i will release my http://simplemining.net/ Operating System which will have this fix and many more + feature updates.
If you want make donation BTC: 1ERRVbvV23h51ScH73nQr6TDmaieKNuuVD
Can someone please clarify what Tytanick means here? Is this only for independent Linux users and not Simplemining users?
I am using Simplemining.net and I get these error messages with four out of six RX480s.
Fixes I have tried:
I have the -dbg -1 code in the config text in the global options window.
I have tried each card with risers that I know are stable because they work with two of my cards.
I have tried various versions of drivers and kernels but found no difference with these errors.
I still am thinking that it is a driver/kernel issue but I have run out of options that I know to try.
Please help!
Re: [Mining OS] SimpleMining.net - Easy to use GPU MINING Operating System
Hey all,
my new rig keeps rebooting about a minute after it connects to the pool. I'm running 6 x RX480s on the H270 chipset and using the main RX OS image (I have tried the other images but with the same constantly rebooting issue). There are a bunch of VM faults and OC errors, but I've selected the monitor to run on onboard video and the cards are all running stock.
Also, the few hash rates that I get each time before the rig crashes are highly variable between each readout.
I've updated the BIOS on my Asrock H270 Fatal1ty board and disconnected each card in turn to try and isolate the issue. But to no avail.
So, any ideas on why it reboots so regularly?
my new rig keeps rebooting about a minute after it connects to the pool. I'm running 6 x RX480s on the H270 chipset and using the main RX OS image (I have tried the other images but with the same constantly rebooting issue). There are a bunch of VM faults and OC errors, but I've selected the monitor to run on onboard video and the cards are all running stock.
Also, the few hash rates that I get each time before the rig crashes are highly variable between each readout.
I've updated the BIOS on my Asrock H270 Fatal1ty board and disconnected each card in turn to try and isolate the issue. But to no avail.
So, any ideas on why it reboots so regularly?
Re: [Mining OS] SimpleMining.net - Easy to use GPU MINING Operating System
I have been unable to get my rig working at all. I have been trouble shooting for three weeks now, and still not the smallest amount of eth!
My rig keeps rebooting itself after showing these error messages:
GPU fault detected: 147 0x0be0440c
VM_CONTEXT1_PROTECTION_FAULT_ADDR
VM_CONTEXT1_PROTECTION_FAULT_STATUS
VM fault (0x0c, vmid 1) at page 1343356, read from 'TC5' (0x054433500) (68)
etc...
The Console field in my Simplemining dashboard says: ERROR OC GPU0
I am running 6 x 480 8GB, and there are no overclocks on anything.
I have searched through this entire thread and could only find a brief mention on page 24 but it wasn't enough to help. What could I try?
My rig keeps rebooting itself after showing these error messages:
GPU fault detected: 147 0x0be0440c
VM_CONTEXT1_PROTECTION_FAULT_ADDR
VM_CONTEXT1_PROTECTION_FAULT_STATUS
VM fault (0x0c, vmid 1) at page 1343356, read from 'TC5' (0x054433500) (68)
etc...
The Console field in my Simplemining dashboard says: ERROR OC GPU0
I am running 6 x 480 8GB, and there are no overclocks on anything.
I have searched through this entire thread and could only find a brief mention on page 24 but it wasn't enough to help. What could I try?
Have you tried reflashing your drive with the most up to date SmOS? Those errors are usually Ubuntu errors, not necessarily the SmOS packaging. It may also be your MB's onboard video, try disabling it in the BIOS.
So I have just retried all three versions of the RX image, and the versions that seems to work the best is the z170, even though I am using a H270 chipset. Do you think the z170 version is why the system is confused about OC?
I did also try each with the onboard video on and off - but to no avail.
Has anyone else had this issue?
Re: [Mining OS] SimpleMining.net - Easy to use GPU MINING Operating System
I have been unable to get my rig working at all. I have been trouble shooting for three weeks now, and still not the smallest amount of eth!
My rig keeps rebooting itself after showing these error messages:
GPU fault detected: 147 0x0be0440c
VM_CONTEXT1_PROTECTION_FAULT_ADDR
VM_CONTEXT1_PROTECTION_FAULT_STATUS
VM fault (0x0c, vmid 1) at page 1343356, read from 'TC5' (0x054433500) (68)
etc...
The Console field in my Simplemining dashboard says: ERROR OC GPU0
I am running 6 x 480 8GB, and there are no overclocks on anything.
I have searched through this entire thread and could only find a brief mention on page 24 but it wasn't enough to help. What could I try?
My rig keeps rebooting itself after showing these error messages:
GPU fault detected: 147 0x0be0440c
VM_CONTEXT1_PROTECTION_FAULT_ADDR
VM_CONTEXT1_PROTECTION_FAULT_STATUS
VM fault (0x0c, vmid 1) at page 1343356, read from 'TC5' (0x054433500) (68)
etc...
The Console field in my Simplemining dashboard says: ERROR OC GPU0
I am running 6 x 480 8GB, and there are no overclocks on anything.
I have searched through this entire thread and could only find a brief mention on page 24 but it wasn't enough to help. What could I try?
I'm setting a rig with simplemining.net and after troubleshooting a few issues have finally got myself stuck, with these lines repeating:
Cannot resolve 'eth-au.dwarfpool.com'
ETH: Stratum - Cannot connect to eth-au.dwarfpool.com:8008
I am running 6 x RX480, H270 chipset, the alternate RX OS for Z170 (because the six GPU's weren't working with the standard version).
And, yes, I live in Australia. Although, I was getting the same text appearing with the eth-eu.dwarfpool command.
Any ideas?
Cannot resolve 'eth-au.dwarfpool.com'
ETH: Stratum - Cannot connect to eth-au.dwarfpool.com:8008
I am running 6 x RX480, H270 chipset, the alternate RX OS for Z170 (because the six GPU's weren't working with the standard version).
And, yes, I live in Australia. Although, I was getting the same text appearing with the eth-eu.dwarfpool command.
Any ideas?