Search content
Sort by
Showing 12 of 12 results by red_x
Re: [Mining OS] SimpleMining.net - Manage Your GPU farm the easy way! (30 days free)
Hi, I've been mining with 7x r9 390 8GB with phoenix miner, but from 2/3 days ago it has started to reboot very often
So I disabled one to test if with only 6 would have the same error, but it mined for half hour and rebooted again
this a print form last crash:
GPUs: 1: 29.970 MH/s (18) 2: 29.970 MH/s (15) 3: 29.972 MH/s (13) 4: 29.971 MH/s (15) 5: 29.972 MH/s (14) 6: 29.972 MH/s (12)
GPU3: Starting up... (0)
GPU3: Generating ethash light cache for epoch #380
GPU6: Starting up... (0)
GPU4: Starting up... (0)
GPU5: Starting up... (0)
GPU1: Starting up... (0)
GPU2: Starting up... (0)
Light cache generated in 2.6 s (24.3 MB/s)
GPU3: Disabling DAG pre-allocation (not enough VRAM)
GPU6: Disabling DAG pre-allocation (not enough VRAM)
GPU4: Disabling DAG pre-allocation (not enough VRAM)
GPU5: Disabling DAG pre-allocation (not enough VRAM)
GPU1: Disabling DAG pre-allocation (not enough VRAM)
GPU2: Disabling DAG pre-allocation (not enough VRAM)
GPU3: Allocating DAG for epoch #380 (3.97) GB
GPU3: Allocating buffers failed with: clCreateBuffer (-61).
Fatal error detected. Restarting.
GPU6: Allocating DAG for epoch #380 (3.97) GB
GPU6: Allocating buffers failed with: clCreateBuffer (-61).
GPU4: Allocating DAG for epoch #380 (3.97) GB
GPU4: Allocating buffers failed with: clCreateBuffer (-61).
GPU5: Allocating DAG for epoch #380 (3.97) GB
GPU5: Allocating buffers failed with: clCreateBuffer (-61).
GPU1: Allocating DAG for epoch #380 (3.97) GB
GPU1: Allocating buffers failed with: clCreateBuffer (-61).
GPU2: Allocating DAG for epoch #380 (3.97) GB
GPU2: Allocating buffers failed with: clCreateBuffer (-61).
Eth speed: 0.000 MH/s, shares: 83/4/0, time: 0:26
Is this a miner error? Claymore also has this behaviour
teamred doesnt recognize hawaii?
witch version of linux image you have?So I disabled one to test if with only 6 would have the same error, but it mined for half hour and rebooted again
this a print form last crash:
GPUs: 1: 29.970 MH/s (18) 2: 29.970 MH/s (15) 3: 29.972 MH/s (13) 4: 29.971 MH/s (15) 5: 29.972 MH/s (14) 6: 29.972 MH/s (12)
GPU3: Starting up... (0)
GPU3: Generating ethash light cache for epoch #380
GPU6: Starting up... (0)
GPU4: Starting up... (0)
GPU5: Starting up... (0)
GPU1: Starting up... (0)
GPU2: Starting up... (0)
Light cache generated in 2.6 s (24.3 MB/s)
GPU3: Disabling DAG pre-allocation (not enough VRAM)
GPU6: Disabling DAG pre-allocation (not enough VRAM)
GPU4: Disabling DAG pre-allocation (not enough VRAM)
GPU5: Disabling DAG pre-allocation (not enough VRAM)
GPU1: Disabling DAG pre-allocation (not enough VRAM)
GPU2: Disabling DAG pre-allocation (not enough VRAM)
GPU3: Allocating DAG for epoch #380 (3.97) GB
GPU3: Allocating buffers failed with: clCreateBuffer (-61).
Fatal error detected. Restarting.
GPU6: Allocating DAG for epoch #380 (3.97) GB
GPU6: Allocating buffers failed with: clCreateBuffer (-61).
GPU4: Allocating DAG for epoch #380 (3.97) GB
GPU4: Allocating buffers failed with: clCreateBuffer (-61).
GPU5: Allocating DAG for epoch #380 (3.97) GB
GPU5: Allocating buffers failed with: clCreateBuffer (-61).
GPU1: Allocating DAG for epoch #380 (3.97) GB
GPU1: Allocating buffers failed with: clCreateBuffer (-61).
GPU2: Allocating DAG for epoch #380 (3.97) GB
GPU2: Allocating buffers failed with: clCreateBuffer (-61).
Eth speed: 0.000 MH/s, shares: 83/4/0, time: 0:26
Is this a miner error? Claymore also has this behaviour
teamred doesnt recognize hawaii?
It's running this image - SimpleMiningOS (SM-5.0.21-9-a18.20-n430.40)
- Kernel / Drv / upd: 5.0.21-sm9 / amd18.20r5.2.6 / v1291
I installed that image, and it has been also having random reboots with that error clCreateBuffer, but since today 8:00 AM it has been mining with no interruption, let's see how it goes, thanks
Re: [Mining OS] SimpleMining.net - Manage Your GPU farm the easy way! (30 days free)
Hi, I've been mining with 7x r9 390 8GB with phoenix miner, but from 2/3 days ago it has started to reboot very often
So I disabled one to test if with only 6 would have the same error, but it mined for half hour and rebooted again
this a print form last crash:
GPUs: 1: 29.970 MH/s (18) 2: 29.970 MH/s (15) 3: 29.972 MH/s (13) 4: 29.971 MH/s (15) 5: 29.972 MH/s (14) 6: 29.972 MH/s (12)
GPU3: Starting up... (0)
GPU3: Generating ethash light cache for epoch #380
GPU6: Starting up... (0)
GPU4: Starting up... (0)
GPU5: Starting up... (0)
GPU1: Starting up... (0)
GPU2: Starting up... (0)
Light cache generated in 2.6 s (24.3 MB/s)
GPU3: Disabling DAG pre-allocation (not enough VRAM)
GPU6: Disabling DAG pre-allocation (not enough VRAM)
GPU4: Disabling DAG pre-allocation (not enough VRAM)
GPU5: Disabling DAG pre-allocation (not enough VRAM)
GPU1: Disabling DAG pre-allocation (not enough VRAM)
GPU2: Disabling DAG pre-allocation (not enough VRAM)
GPU3: Allocating DAG for epoch #380 (3.97) GB
GPU3: Allocating buffers failed with: clCreateBuffer (-61).
Fatal error detected. Restarting.
GPU6: Allocating DAG for epoch #380 (3.97) GB
GPU6: Allocating buffers failed with: clCreateBuffer (-61).
GPU4: Allocating DAG for epoch #380 (3.97) GB
GPU4: Allocating buffers failed with: clCreateBuffer (-61).
GPU5: Allocating DAG for epoch #380 (3.97) GB
GPU5: Allocating buffers failed with: clCreateBuffer (-61).
GPU1: Allocating DAG for epoch #380 (3.97) GB
GPU1: Allocating buffers failed with: clCreateBuffer (-61).
GPU2: Allocating DAG for epoch #380 (3.97) GB
GPU2: Allocating buffers failed with: clCreateBuffer (-61).
Eth speed: 0.000 MH/s, shares: 83/4/0, time: 0:26
Is this a miner error? Claymore also has this behaviour
teamred doesnt recognize hawaii?
witch version of linux image you have?So I disabled one to test if with only 6 would have the same error, but it mined for half hour and rebooted again
this a print form last crash:
GPUs: 1: 29.970 MH/s (18) 2: 29.970 MH/s (15) 3: 29.972 MH/s (13) 4: 29.971 MH/s (15) 5: 29.972 MH/s (14) 6: 29.972 MH/s (12)
GPU3: Starting up... (0)
GPU3: Generating ethash light cache for epoch #380
GPU6: Starting up... (0)
GPU4: Starting up... (0)
GPU5: Starting up... (0)
GPU1: Starting up... (0)
GPU2: Starting up... (0)
Light cache generated in 2.6 s (24.3 MB/s)
GPU3: Disabling DAG pre-allocation (not enough VRAM)
GPU6: Disabling DAG pre-allocation (not enough VRAM)
GPU4: Disabling DAG pre-allocation (not enough VRAM)
GPU5: Disabling DAG pre-allocation (not enough VRAM)
GPU1: Disabling DAG pre-allocation (not enough VRAM)
GPU2: Disabling DAG pre-allocation (not enough VRAM)
GPU3: Allocating DAG for epoch #380 (3.97) GB
GPU3: Allocating buffers failed with: clCreateBuffer (-61).
Fatal error detected. Restarting.
GPU6: Allocating DAG for epoch #380 (3.97) GB
GPU6: Allocating buffers failed with: clCreateBuffer (-61).
GPU4: Allocating DAG for epoch #380 (3.97) GB
GPU4: Allocating buffers failed with: clCreateBuffer (-61).
GPU5: Allocating DAG for epoch #380 (3.97) GB
GPU5: Allocating buffers failed with: clCreateBuffer (-61).
GPU1: Allocating DAG for epoch #380 (3.97) GB
GPU1: Allocating buffers failed with: clCreateBuffer (-61).
GPU2: Allocating DAG for epoch #380 (3.97) GB
GPU2: Allocating buffers failed with: clCreateBuffer (-61).
Eth speed: 0.000 MH/s, shares: 83/4/0, time: 0:26
Is this a miner error? Claymore also has this behaviour
teamred doesnt recognize hawaii?
It's running this image - SimpleMiningOS (SM-5.0.21-9-a18.20-n430.40)
- Kernel / Drv / upd: 5.0.21-sm9 / amd18.20r5.2.6 / v1291
Re: [Mining OS] SimpleMining.net - Manage Your GPU farm the easy way! (30 days free)
Hi, I've been mining with 7x r9 390 8GB with phoenix miner, but from 2/3 days ago it has started to reboot very often
So I disabled one to test if with only 6 would have the same error, but it mined for half hour and rebooted again
this a print form last crash:
GPUs: 1: 29.970 MH/s (18) 2: 29.970 MH/s (15) 3: 29.972 MH/s (13) 4: 29.971 MH/s (15) 5: 29.972 MH/s (14) 6: 29.972 MH/s (12)
GPU3: Starting up... (0)
GPU3: Generating ethash light cache for epoch #380
GPU6: Starting up... (0)
GPU4: Starting up... (0)
GPU5: Starting up... (0)
GPU1: Starting up... (0)
GPU2: Starting up... (0)
Light cache generated in 2.6 s (24.3 MB/s)
GPU3: Disabling DAG pre-allocation (not enough VRAM)
GPU6: Disabling DAG pre-allocation (not enough VRAM)
GPU4: Disabling DAG pre-allocation (not enough VRAM)
GPU5: Disabling DAG pre-allocation (not enough VRAM)
GPU1: Disabling DAG pre-allocation (not enough VRAM)
GPU2: Disabling DAG pre-allocation (not enough VRAM)
GPU3: Allocating DAG for epoch #380 (3.97) GB
GPU3: Allocating buffers failed with: clCreateBuffer (-61).
Fatal error detected. Restarting.
GPU6: Allocating DAG for epoch #380 (3.97) GB
GPU6: Allocating buffers failed with: clCreateBuffer (-61).
GPU4: Allocating DAG for epoch #380 (3.97) GB
GPU4: Allocating buffers failed with: clCreateBuffer (-61).
GPU5: Allocating DAG for epoch #380 (3.97) GB
GPU5: Allocating buffers failed with: clCreateBuffer (-61).
GPU1: Allocating DAG for epoch #380 (3.97) GB
GPU1: Allocating buffers failed with: clCreateBuffer (-61).
GPU2: Allocating DAG for epoch #380 (3.97) GB
GPU2: Allocating buffers failed with: clCreateBuffer (-61).
Eth speed: 0.000 MH/s, shares: 83/4/0, time: 0:26
Is this a miner error? Claymore also has this behaviour
teamred doesnt recognize hawaii?
So I disabled one to test if with only 6 would have the same error, but it mined for half hour and rebooted again
this a print form last crash:
GPUs: 1: 29.970 MH/s (18) 2: 29.970 MH/s (15) 3: 29.972 MH/s (13) 4: 29.971 MH/s (15) 5: 29.972 MH/s (14) 6: 29.972 MH/s (12)
GPU3: Starting up... (0)
GPU3: Generating ethash light cache for epoch #380
GPU6: Starting up... (0)
GPU4: Starting up... (0)
GPU5: Starting up... (0)
GPU1: Starting up... (0)
GPU2: Starting up... (0)
Light cache generated in 2.6 s (24.3 MB/s)
GPU3: Disabling DAG pre-allocation (not enough VRAM)
GPU6: Disabling DAG pre-allocation (not enough VRAM)
GPU4: Disabling DAG pre-allocation (not enough VRAM)
GPU5: Disabling DAG pre-allocation (not enough VRAM)
GPU1: Disabling DAG pre-allocation (not enough VRAM)
GPU2: Disabling DAG pre-allocation (not enough VRAM)
GPU3: Allocating DAG for epoch #380 (3.97) GB
GPU3: Allocating buffers failed with: clCreateBuffer (-61).
Fatal error detected. Restarting.
GPU6: Allocating DAG for epoch #380 (3.97) GB
GPU6: Allocating buffers failed with: clCreateBuffer (-61).
GPU4: Allocating DAG for epoch #380 (3.97) GB
GPU4: Allocating buffers failed with: clCreateBuffer (-61).
GPU5: Allocating DAG for epoch #380 (3.97) GB
GPU5: Allocating buffers failed with: clCreateBuffer (-61).
GPU1: Allocating DAG for epoch #380 (3.97) GB
GPU1: Allocating buffers failed with: clCreateBuffer (-61).
GPU2: Allocating DAG for epoch #380 (3.97) GB
GPU2: Allocating buffers failed with: clCreateBuffer (-61).
Eth speed: 0.000 MH/s, shares: 83/4/0, time: 0:26
Is this a miner error? Claymore also has this behaviour
teamred doesnt recognize hawaii?
Re: [Mining OS] SimpleMining.net - Easiest way to mine and manage all your rigs !!!
No worries about config in rig list.
Try this latest image and see if it will boot up without problems.
After that you can adjust your settings again in OC modal.
First we just need to boot it up, settings are not the fault of it
Try this latest image and see if it will boot up without problems.
After that you can adjust your settings again in OC modal.
First we just need to boot it up, settings are not the fault of it
Just tested your latest image, now it boots fine, I configured the miner and it started to mine ! yeah
Now, I'd like to undervolt the cards,
I set overclock to 1050 1500 950 but I get a message specified memory state doesn't exist and that these are not RX cards and it reverts to defaults
the only tabs that are working are the powerstates and fan speed
setting it to powerstate 6 is the only way to underclock it to 1011 and cool the cards a bit
thank you
Re: [Mining OS] SimpleMining.net - Easiest way to mine and manage all your rigs !!!
OK, one more try.
Please try this image for R9 390
https://download.simplemining.net/images/SM-5.0.21-3e-a19.30-n430.64-v1255.img.xz
And let me know
Please try this image for R9 390
https://download.simplemining.net/images/SM-5.0.21-3e-a19.30-n430.64-v1255.img.xz
And let me know
thanks I'll try that one too
Just tested with another pen and doesn't boot at all from grub, I have to choose recovery mode and it will boot
It started to update and then downloaded the previous config with the gtx 1070(?)
I already deleted the rig from the list but every time I restart it shows up again on the list with the core and mem settings of nVidia
Is there any way of deleting the rig config?
I'll try that image but if it downloads again the previous settings it will keep trying to find a nVidia card.
https://imgur.com/a/1H0XDa7
Cheers
Re: [Mining OS] SimpleMining.net - Easiest way to mine and manage all your rigs !!!
Is there any image that has been tested to work with this rig config?
Can You tell me what image did you used ?
Please this should be working fine:
https://download.simplemining.net/images/SM-4.17.19-17-a18.20-n430.40-v1247.img.xz
And this is very old image thas was ment for old series of those GPUs but we do not support it anymore.
Yet it supports 300 series but i think except 390
- so image above should be best for your case.https://download.simplemining.net/images/SM-4.2.0-R-v1252.img.xz
that's the image that I used
i'm going to try other usb pen
do you think that it would boot better from a ssd/hdd?
Re: [Mining OS] SimpleMining.net - Easiest way to mine and manage all your rigs !!!
Hi, I have a 6x r9 390 rig with H81 pro mobo, it has been working fine with Windows but with the constant drop of ethash speed, I'm giving a try to setup smos before I decide to dismantle it.
.I've flashed a 16gb usb3 pen with the latest image, but it can't seem to boot properly.
.Either it gets stuck after grub or if I choose the recovery mode option, it shows a no screen attached error on every card
.the rig shows up on the online dashboard
.if I swap one 390 with a gtx 1070, it will boot with all cards detected (only with recovery mode) and starts to mine but it is not possible to control the amd fan speeds, so they start to heat up to 90º.
Is there any image that has been tested to work with this rig config?
.I've flashed a 16gb usb3 pen with the latest image, but it can't seem to boot properly.
.Either it gets stuck after grub or if I choose the recovery mode option, it shows a no screen attached error on every card
.the rig shows up on the online dashboard
.if I swap one 390 with a gtx 1070, it will boot with all cards detected (only with recovery mode) and starts to mine but it is not possible to control the amd fan speeds, so they start to heat up to 90º.
Is there any image that has been tested to work with this rig config?
on nanopool calculator
v11.1 - I was getting 450usd month
v12 - with more H/s i'm getting only 350usd?
v11.1 - I was getting 450usd month
v12 - with more H/s i'm getting only 350usd?
The price of ZEC is degrading faster than you can increase in hash.
If you want ZEC rise up again, just don't sell it
From one day to the other? I just stopped one miner and started the other
- I'm not selling it
http://uupload.ir/files/74ma_image_2017-01-22_12-07-54.png
i use 11.1 claymore version and my gpus are r9 390x as i read in 11.1 description i must get about 365
what's the problem?
i use 11.1 claymore version and my gpus are r9 390x as i read in 11.1 description i must get about 365
what's the problem?
maybe different brands get different results
I have 6 asus strix 390 oc in one rig and had to play with core oc while reducing voltage to get near that value
Not every card is the same, I fine tune each card with different oc and voltage because some won't produce more h/s past certain setting so there's no need to keep stressing the card, some get there with only 1120-1130 others only with 1150 core clock.
drivers also have influence and you need to check wich is best for your rig
Hi,
I have a problem if I try to connect more than 6 GPUs to my AsRock H81 Pro BTC v2.0 mobo. I bought an extender riser (PCI-E x1 -> 3*PCI-E x1) and I use normal USB3 PCI-E x1->x16 risers. Everything's fine until I connect the 7th card. I can connect the first 6 card any way I want it but after the 7th card connected I got blank screen when I turn on the rig.
How do I make it work with 7 or 8 cards?
I have a problem if I try to connect more than 6 GPUs to my AsRock H81 Pro BTC v2.0 mobo. I bought an extender riser (PCI-E x1 -> 3*PCI-E x1) and I use normal USB3 PCI-E x1->x16 risers. Everything's fine until I connect the 7th card. I can connect the first 6 card any way I want it but after the 7th card connected I got blank screen when I turn on the rig.
How do I make it work with 7 or 8 cards?
are you using Windows 7 perhaps? I have an 8 Card system and the only way I got them to work was with Windows 10 and Ubuntu. But it can also be the fact that your MB don't support more than 6 PCIE cards. Have you tried connecting 5 cards and one dual card? such as 7990, 295x ? I have two 7990 and 4 other cards in my 8 card system. Not using the PCI Switch.
I use Win10, but I can't get to boot the OS. I turn on the rig and nothing happens. I don't have dual cards, I use RX470 GPUs.
Maybe AsRock H81 Pro BTC v2.0 mobo doesn't support more than 6 PCI-E devices? I tried to disable integrated audio, serial ports, etc. in the bios, then connected the 7th card but also didn't work.
I don't want to buy an expensive server/workstation mobo. Is there any chance to use 7 or 8 PCI-E devices? I searched for modded bios for this mobo but didn't find anything. Or it's the limit of the H81 chipset, not the bios?
Which PCIE slot are you connecting your 1x3 card into?
It is my understanding that each GPU requires a minimum of 1 PCIE lane/pipeline to transmit data. That means you would have to plug the 1x3 card into a slot with at least 3 lanes/pipelines (in the real world that means a 4x, 8x, or 16x slot). The H81 Pro BTC has a single 16x slot and five 1x slots. You could only ever run the 1x3 card on the 16x slot.
If I'm wrong on this I am open to correction. I've actually been wanting to play around with the exact setup you describe.
I used the 1->3 extender riser in the 6th PCI-E slot (which is an x1 slot) and the 3 cards worked fine on that extender. So I think it is a limitation of bios/chipset, or not enough IRQ available?
I have a meeting I need to run to but this thread I found may have some useful information in it. I will keep digging when I get back as well.
https://forum.ethereum.org/discussion/5195/riser-1-to-3-pci-e-1x
Edit 1:
After reading through the above thread and taking a look at Intel's specs on the h81 and z87 it would appear that the max PCIE lanes through the h81 chipset is 6, whereas the z87 chipset can handle 8. The 1x PCIE slots run through the chipset, but the 16x slot runs straight to the CPU.
I would think that you could run 6 GPUs max through the chipset while running the remainder of your GPUs through the 16x slot using the CPUs remaining availability. In this scenario you could only ever use a 1x2 card in one of your 1x slots. If you moved the 1x3 card to the 16x slot then you could run 5 GPU through the chipset and 3 (or more depending on CPU, driver, OS) through the 16x PCIE straight to the CPU.
But that doesn't seem to be your experience. If you have the 1x3 card in the last 1x PCIE slot then the 7th card you plug in should be the 6th card running through the chipset. Theoretically you should be able to run 7 cards with your setup, but not 8. And you can't.
So I'm wondering, perhaps we have a bottleneck somewhere else? Out of curiosity, what CPU are you using?
http://ark.intel.com/products/75013/Intel-Z87-Chipset
https://ark.intel.com/products/75016/Intel-H81-Chipset
Thank you for your research. I use G1840: http://ark.intel.com/products/80800/Intel-Celeron-Processor-G1840-2M-Cache-2_80-GHz
@fredeq: also thanks.
I also gave up trying to use the splitter for a 6+ gpu rig
First I used Asus P8P67 Workstation mobo that has 7 pcie slots but when I plugged the 7th card it even didn't appear on device manager on win10, with the splitter is did the same.
I even swapped the g860 for a xeon with 20 lanes and same happened.
Then with Asus p8z77 ws, the same happens
with a p5q pro it didn't even boot with the splitter and 7 gpus
I won't buy more recent hardware for mining unless it gets possible to have more than 6 gpu in one system
So for now i'm using it for what is intended for - a splitter/extension of my home pc
In the main pc case I have a saphire rx480 8g running cool&quiet and outside in a open frame diy case, one asus 390 and two 280x running through a 3m usb 3 cable to the splitter.
rig 1
r9 280x oc 1120/1500 - 245 h/s
r9 390 oc 1150/1500 - 365 h/s
rx 480 oc 1250/2150 - 265 h/s (bios mod)
this rig gets none shares rejected
rig 2
6x r9 390 oc 1130/1500 - 340-360 h/s total = 2140 h/s
this rig is getting a lot of shares rejected since v10
any hint for rejected shares? rigs are in different places and ISPs.
r9 280x oc 1120/1500 - 245 h/s
r9 390 oc 1150/1500 - 365 h/s
rx 480 oc 1250/2150 - 265 h/s (bios mod)
this rig gets none shares rejected
rig 2
6x r9 390 oc 1130/1500 - 340-360 h/s total = 2140 h/s
this rig is getting a lot of shares rejected since v10
any hint for rejected shares? rigs are in different places and ISPs.