Search content
Sort by
Showing 20 of 23 results by cryptomanman
Re: [ANN] TeamRedMiner - CNv8 - Vega 64 2200+h/s Rx470 1025+h/s Low Power Draw
todxx,
So far, I only have 1 RX570 working in my server / workstation hardware. (BTW, previous version with lyra2z worked fine. 3.1, I think) Other RX570's in my celeron 6 card rig working great. Here is dmesg from a failing machine. FYI it's the whole thing since I don't know what parts will be helpful to you. Also, these machines boot up from PXE and xmr-stak starts by default. I went in and manually stopped it and started teamredminer before capturing the log. (Same workflow for working and non-working rigs) https://pastebin.com/eVszbM85
So far, I only have 1 RX570 working in my server / workstation hardware. (BTW, previous version with lyra2z worked fine. 3.1, I think) Other RX570's in my celeron 6 card rig working great. Here is dmesg from a failing machine. FYI it's the whole thing since I don't know what parts will be helpful to you. Also, these machines boot up from PXE and xmr-stak starts by default. I went in and manually stopped it and started teamredminer before capturing the log. (Same workflow for working and non-working rigs) https://pastebin.com/eVszbM85
There's a few errors reported by the amdgpu driver. Some of these I remember seeing in older drivers that I thought were now fixed.
Is this the 18.30 driver or the 17.30 driver?
That log was Ubuntu 16.04, kernel 4.4, amdgpu-pro 17.30. I'll try and find time to spin up the other PXE server with 18.30 tomorrow and put up the log. Thanks for all the work!
Re: [ANN] TeamRedMiner - CNv8 - Vega 64 2200+h/s Rx470 1025+h/s Low Power Draw
This is exactly the symptoms I get. Never finishes initializing the card/s.
These are the configurations on which I'm having failures with teamredminer 3.5.0 and 3.6.0 --
IBM X36550-M3, Ubuntu server 16.04, kernel 4.4, amdgpu-pro 17.30, 2x MSI Radeon RX560 Aero 4GB
HP z600, Ubuntu server 16.04 and 18.04, kernel 4.4 and 4.15, amdgpu-pro 17.30 and 18.30, ASUS ROG Strix RX570 4GB
Currently have 2 6GPU boxes with much less robust CPU's running just great and at least 1 of the z600's is also running great with teamredminer 3.5.0. Tried watching journalctl when starting the miner. No errors noted. And again, xmr-stak is very stable on these systems, just not as high hashrate.
Team Red Miner v0.3.6 released
https://github.com/todxx/teamredminer/releases
Changes in v0.3.6
Hopefully this is another step to achieving stability on larger rigs, especially with weaker cpus. It has been tested by one of the forum users who had both early initialization issues, then stability issues. His rigs have gone from crashing every 30-120 mins to running smoothly for 15+ hours except for (I think) a single crash due to insufficient voltage. I believe we have more work to do though, we'll monitor carefully and try to address all problems that appear.
For people with specific startup issues that are willing to help us nail them down and solve them, please reach out to me with a PM.
The ANN post will be updated shortly by todxx.
Linux kernel 4.13, 16.60 driver getting this with 12 RX 550 Lexa Pro in rig
compared it to my Vega rig and there it says "successfully initited ". It never does that with the RX 550 on Linux. So it never finishes initialization.
I tried 1 card on Windows, there it worked.
These are the configurations on which I'm having failures with teamredminer 3.5.0 and 3.6.0 --
IBM X36550-M3, Ubuntu server 16.04, kernel 4.4, amdgpu-pro 17.30, 2x MSI Radeon RX560 Aero 4GB
HP z600, Ubuntu server 16.04 and 18.04, kernel 4.4 and 4.15, amdgpu-pro 17.30 and 18.30, ASUS ROG Strix RX570 4GB
Currently have 2 6GPU boxes with much less robust CPU's running just great and at least 1 of the z600's is also running great with teamredminer 3.5.0. Tried watching journalctl when starting the miner. No errors noted. And again, xmr-stak is very stable on these systems, just not as high hashrate.
Team Red Miner v0.3.6 released
https://github.com/todxx/teamredminer/releases
Changes in v0.3.6
- Added support for Rx550 cards (gfx804).
- Improved stability on larger rigs, especially with weaker cpus.
- Improved error reporting on failed initialization.
Hopefully this is another step to achieving stability on larger rigs, especially with weaker cpus. It has been tested by one of the forum users who had both early initialization issues, then stability issues. His rigs have gone from crashing every 30-120 mins to running smoothly for 15+ hours except for (I think) a single crash due to insufficient voltage. I believe we have more work to do though, we'll monitor carefully and try to address all problems that appear.
For people with specific startup issues that are willing to help us nail them down and solve them, please reach out to me with a PM.
The ANN post will be updated shortly by todxx.
Linux kernel 4.13, 16.60 driver getting this with 12 RX 550 Lexa Pro in rig
Code:
[2018-11-02 04:33:39] Stats GPU 0 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 1 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 2 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 3 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 4 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 5 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 6 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 7 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 8 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 9 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU10 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU11 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats Total - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s
[2018-11-02 04:33:39] Pool pool.supportxmr.com received new job. (job_id: cRROY+SGvbG/T+sPA/wgUhFRvJDF)
[2018-11-02 04:33:39] Pool pool.supportxmr.com set difficulty to 5000
still nothing after 5 minutes...[2018-11-02 04:33:39] Stats GPU 1 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 2 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 3 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 4 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 5 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 6 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 7 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 8 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 9 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU10 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU11 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats Total - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s
[2018-11-02 04:33:39] Pool pool.supportxmr.com received new job. (job_id: cRROY+SGvbG/T+sPA/wgUhFRvJDF)
[2018-11-02 04:33:39] Pool pool.supportxmr.com set difficulty to 5000
compared it to my Vega rig and there it says "successfully initited ". It never does that with the RX 550 on Linux. So it never finishes initialization.
I tried 1 card on Windows, there it worked.
Hey cryptomanman,
It's strange that you're having issues with that RX 570. So far I've only see initialization issues on with Vegas when running 18.30 and newer drivers.
Can you try to run the miner again and see if there are any amdgpu/drm errors reported by the kernel driver?
With Vegas I've noticed that the driver will occasionally have problems and report tons of errors in dmesg/kernel logs.
todxx,
So far, I only have 1 RX570 working in my server / workstation hardware. (BTW, previous version with lyra2z worked fine. 3.1, I think) Other RX570's in my celeron 6 card rig working great. Here is dmesg from a failing machine. FYI it's the whole thing since I don't know what parts will be helpful to you. Also, these machines boot up from PXE and xmr-stak starts by default. I went in and manually stopped it and started teamredminer before capturing the log. (Same workflow for working and non-working rigs) https://pastebin.com/eVszbM85
Re: [ANN] TeamRedMiner - CNv8 - Vega 64 2200+h/s Rx470 1025+h/s Low Power Draw
This is exactly the symptoms I get. Never finishes initializing the card/s.
These are the configurations on which I'm having failures with teamredminer 3.5.0 and 3.6.0 --
IBM X36550-M3, Ubuntu server 16.04, kernel 4.4, amdgpu-pro 17.30, 2x MSI Radeon RX560 Aero 4GB
HP z600, Ubuntu server 16.04 and 18.04, kernel 4.4 and 4.15, amdgpu-pro 17.30 and 18.30, ASUS ROG Strix RX570 4GB
Currently have 2 6GPU boxes with much less robust CPU's running just great and at least 1 of the z600's is also running great with teamredminer 3.5.0. Tried watching journalctl when starting the miner. No errors noted. And again, xmr-stak is very stable on these systems, just not as high hashrate.
Team Red Miner v0.3.6 released
https://github.com/todxx/teamredminer/releases
Changes in v0.3.6
Hopefully this is another step to achieving stability on larger rigs, especially with weaker cpus. It has been tested by one of the forum users who had both early initialization issues, then stability issues. His rigs have gone from crashing every 30-120 mins to running smoothly for 15+ hours except for (I think) a single crash due to insufficient voltage. I believe we have more work to do though, we'll monitor carefully and try to address all problems that appear.
For people with specific startup issues that are willing to help us nail them down and solve them, please reach out to me with a PM.
The ANN post will be updated shortly by todxx.
Linux kernel 4.13, 16.60 driver getting this with 12 RX 550 Lexa Pro in rig
compared it to my Vega rig and there it says "successfully initited ". It never does that with the RX 550 on Linux. So it never finishes initialization.
I tried 1 card on Windows, there it worked.
These are the configurations on which I'm having failures with teamredminer 3.5.0 and 3.6.0 --
IBM X36550-M3, Ubuntu server 16.04, kernel 4.4, amdgpu-pro 17.30, 2x MSI Radeon RX560 Aero 4GB
HP z600, Ubuntu server 16.04 and 18.04, kernel 4.4 and 4.15, amdgpu-pro 17.30 and 18.30, ASUS ROG Strix RX570 4GB
Currently have 2 6GPU boxes with much less robust CPU's running just great and at least 1 of the z600's is also running great with teamredminer 3.5.0. Tried watching journalctl when starting the miner. No errors noted. And again, xmr-stak is very stable on these systems, just not as high hashrate.
Team Red Miner v0.3.6 released
https://github.com/todxx/teamredminer/releases
Changes in v0.3.6
- Added support for Rx550 cards (gfx804).
- Improved stability on larger rigs, especially with weaker cpus.
- Improved error reporting on failed initialization.
Hopefully this is another step to achieving stability on larger rigs, especially with weaker cpus. It has been tested by one of the forum users who had both early initialization issues, then stability issues. His rigs have gone from crashing every 30-120 mins to running smoothly for 15+ hours except for (I think) a single crash due to insufficient voltage. I believe we have more work to do though, we'll monitor carefully and try to address all problems that appear.
For people with specific startup issues that are willing to help us nail them down and solve them, please reach out to me with a PM.
The ANN post will be updated shortly by todxx.
Linux kernel 4.13, 16.60 driver getting this with 12 RX 550 Lexa Pro in rig
Code:
[2018-11-02 04:33:39] Stats GPU 0 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 1 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 2 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 3 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 4 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 5 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 6 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 7 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 8 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 9 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU10 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU11 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats Total - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s
[2018-11-02 04:33:39] Pool pool.supportxmr.com received new job. (job_id: cRROY+SGvbG/T+sPA/wgUhFRvJDF)
[2018-11-02 04:33:39] Pool pool.supportxmr.com set difficulty to 5000
still nothing after 5 minutes...[2018-11-02 04:33:39] Stats GPU 1 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 2 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 3 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 4 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 5 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 6 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 7 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 8 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU 9 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU10 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats GPU11 - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s 0/0
[2018-11-02 04:33:39] Stats Total - cnv8: 0.0 h/s, avg 0.0 h/s, pool 0.0 h/s
[2018-11-02 04:33:39] Pool pool.supportxmr.com received new job. (job_id: cRROY+SGvbG/T+sPA/wgUhFRvJDF)
[2018-11-02 04:33:39] Pool pool.supportxmr.com set difficulty to 5000
compared it to my Vega rig and there it says "successfully initited ". It never does that with the RX 550 on Linux. So it never finishes initialization.
I tried 1 card on Windows, there it worked.
Re: [ANN] TeamRedMiner - CNv8 - Vega 64 2200+h/s Rx470 1025+h/s Low Power Draw
Yes, running the current 0.3.5 version. Yes, CPU mining going on in the background both on the cards that successfully initialize and those that don't.
Quick edit. Just tried starting without CPU mining on 1 rig. Same result.
May I double check that you are running the latest version, v0.3.5? Also, are you doing any cpu mining in parallel when you start the miner?
Quick edit. Just tried starting without CPU mining on 1 rig. Same result.
So far getting approximately 5 to 7% increase over xmr-stak on cnv8. That's great! But, it seems to only work on about half of my rigs. They other half, it says it's initializing and getting work from the pool but the hashrate stays at 0 H/s. Same symptoms when trying to mine lyra2z also.
Same rig setups, though various models of cards. Ubuntu 16.04 server and Lubuntu 16.04, amdgpu-pro 17.30 and 18.30, server grade computers with Xeon CPU's, MSI and ASUS 470's, 480's, 560's, and 570's. No consistant pattern to which cards work or don't work with driver version, OS version, or card model that I been able to figure out.
Since there doesn't seem to be a way to enable any debug logging, I'm asking for some ideas here.
Thanks!
Same rig setups, though various models of cards. Ubuntu 16.04 server and Lubuntu 16.04, amdgpu-pro 17.30 and 18.30, server grade computers with Xeon CPU's, MSI and ASUS 470's, 480's, 560's, and 570's. No consistant pattern to which cards work or don't work with driver version, OS version, or card model that I been able to figure out.
Since there doesn't seem to be a way to enable any debug logging, I'm asking for some ideas here.
Thanks!
May I double check that you are running the latest version, v0.3.5? Also, are you doing any cpu mining in parallel when you start the miner?
Re: [ANN] TeamRedMiner - CNv8 - Vega 64 2200+h/s Rx470 1025+h/s Low Power Draw
So far getting approximately 5 to 7% increase over xmr-stak on cnv8. That's great! But, it seems to only work on about half of my rigs. They other half, it says it's initializing and getting work from the pool but the hashrate stays at 0 H/s. Same symptoms when trying to mine lyra2z also.
Same rig setups, though various models of cards. Ubuntu 16.04 server and Lubuntu 16.04, amdgpu-pro 17.30 and 18.30, server grade computers with Xeon CPU's, MSI and ASUS 470's, 480's, 560's, and 570's. No consistant pattern to which cards work or don't work with driver version, OS version, or card model that I been able to figure out.
Since there doesn't seem to be a way to enable any debug logging, I'm asking for some ideas here.
Thanks!
Same rig setups, though various models of cards. Ubuntu 16.04 server and Lubuntu 16.04, amdgpu-pro 17.30 and 18.30, server grade computers with Xeon CPU's, MSI and ASUS 470's, 480's, 560's, and 570's. No consistant pattern to which cards work or don't work with driver version, OS version, or card model that I been able to figure out.
Since there doesn't seem to be a way to enable any debug logging, I'm asking for some ideas here.
Thanks!
The node is karbo.ceallach.pro:32348. Anyone may use it. I didn't see any option to set or not set a fee when I configured. Where is that option? karbowanecd --help does not show that.
Thanks!
Thanks for the help setting up my node. I see a few transactions through it as I have several very small fees. I am glad some have found it useful.
I hope Karbo can sustain through this bear market! The node is karbo.ceallach.pro:32348. Anyone may use it. I didn't see any option to set or not set a fee when I configured. Where is that option? karbowanecd --help does not show that.
Thanks!
Yes. That it how it is running. All are welcome to use. I will leave it up and running as long as I have that VPS available.
I have a node setup on a VPS. I could open it up to public use. Any reason to do that at this point? Does this project have enough use to need more nodes for the light wallets?
Additional node is always welcomed. If you set fee address lite wallets will pay small fee but I doubt it will be economically sustainable, most of the owners do this to support the network, not to earn at this point. We will try to make nodes profitable providing them more rewards in the future.The node is karbo.ceallach.pro:32348. Anyone may use it. I didn't see any option to set or not set a fee when I configured. Where is that option? karbowanecd --help does not show that.
Thanks!
I have a node setup on a VPS. I could open it up to public use. Any reason to do that at this point? Does this project have enough use to need more nodes for the light wallets?
Re: SRBPolaris V3.3 - BIOS editor for RX4XX and RX5XX cards
I have a MSI RX 470 armor 4GB card with Hynix memory and the editor says unknown ROM and does not allow setting of clocks. Could you add this ROM? Link below
https://mega.nz/#!gnwiWT7C!vfYNVPI7YGWkcYpM76n9g2FU-J7RRG4vV69KZuvPU0g
Thanks!
https://mega.nz/#!gnwiWT7C!vfYNVPI7YGWkcYpM76n9g2FU-J7RRG4vV69KZuvPU0g
Thanks!
Try it now, download new ver 3.3
That was it! Works great. You're awesome! Thanks
Re: SRBPolaris V3.3 - BIOS editor for RX4XX and RX5XX cards
I have a MSI RX 470 armor 4GB card with Hynix memory and the editor says unknown ROM and does not allow setting of clocks. Could you add this ROM? Link below
https://mega.nz/#!gnwiWT7C!vfYNVPI7YGWkcYpM76n9g2FU-J7RRG4vV69KZuvPU0g
Thanks!
https://mega.nz/#!gnwiWT7C!vfYNVPI7YGWkcYpM76n9g2FU-J7RRG4vV69KZuvPU0g
Thanks!
Re: SRBPolaris V3.2 - BIOS editor for RX4XX and RX5XX cards
I have a new MSI RX 560 Aero ITX 4GB that I received as an RMA from MSI. I seems different from all the others I have and will not honor the GPU or MEM clock settings. Strap changes work fine however. Below are some screen shots from SRB and the ROM. Are there some changes you could add to allow clock settings that will not be ignored?
https://mega.nz/#!9zhkBRLB!4yT_d-xcvbnkCax6tnpqdCUoL3cXBIl35TCQYGR4YNg
https://mega.nz/#!1ygxEDQQ!xOeKSOYAA_xXp--MUb7u0ouAIy-kLROdUwAWiAXn7W4
https://mega.nz/#!UvYhSYiY!zzCEpbXEcaINzwlXDVA6dqJgqT2OW_y4O3cxKm5yAas
https://mega.nz/#!oyp2laCL!6NqA8f_4kNYezDRUNz7DT7srfBXoZztAMVuLMwDeBgY
https://mega.nz/#!9zhkBRLB!4yT_d-xcvbnkCax6tnpqdCUoL3cXBIl35TCQYGR4YNg
https://mega.nz/#!1ygxEDQQ!xOeKSOYAA_xXp--MUb7u0ouAIy-kLROdUwAWiAXn7W4
https://mega.nz/#!UvYhSYiY!zzCEpbXEcaINzwlXDVA6dqJgqT2OW_y4O3cxKm5yAas
https://mega.nz/#!oyp2laCL!6NqA8f_4kNYezDRUNz7DT7srfBXoZztAMVuLMwDeBgY
Re: Genesis Mining Presents: SGMiner-GM - now with Zawawa's GG! [Updated 17/01/2017]
Thats where I am too right now. Except how are you getting 700 on your 280x?! I'm getting right around 500, just like the 7970's. Different settings than the 7970's?
Unfortunately, the end is coming soon for those older cards and 14.04 I think. Plus the RX 470 / 480 uses so much less power. Something needs to improve soon with 16.04 and the amdgpu-pro drivers. Have to install Windows just to tweak those cards at all!
Unfortunately, the end is coming soon for those older cards and 14.04 I think. Plus the RX 470 / 480 uses so much less power. Something needs to improve soon with 16.04 and the amdgpu-pro drivers. Have to install Windows just to tweak those cards at all!
Amazing the amount of work that's gone into SGM 5.5 over the last few months. Compiles and runs in Linux like a charm. "What do you mean you can't find OpenCL, it's right **** there!" That all went away. Documentation went from like zero to pretty darn good. All the noob tutorials are now officially defunct, which is probably just as good.
Would personally recommend Xubuntu in version 14.04 if you have a card that'll work with fglrx; my older gen cards are killing it. 290x hashing 700-740 with no mods, 7950 500-520. 7850's getting 340, well in excess of what they get under windows/Claymore. SGM just screams in 14.04. It'll run from console, SSH, mosh, you name it. All on some, like $30 army-surplus motherboard I got off ebay. I've tried about umpteen distros over the last few weeks. My advice, for xmr anyway, is keep it simple. Go with some ubuntu flavor (I'd do xubuntu or mint, except for cinnamon), don't go nuts on your config file. Every card I've tried so far likes 2 threads, and it'll pretty much always run with a raw intensity of 512. Except for my 280, which I agree is kind of a conundrum.
Can't say I'm as thrilled with 16.04, which is kind of a pig. Somewhat interested to see where radeon goes with this. Bet they ditch X altogether. Bet everyone does, except ubuntu. I won't miss it.
Would personally recommend Xubuntu in version 14.04 if you have a card that'll work with fglrx; my older gen cards are killing it. 290x hashing 700-740 with no mods, 7950 500-520. 7850's getting 340, well in excess of what they get under windows/Claymore. SGM just screams in 14.04. It'll run from console, SSH, mosh, you name it. All on some, like $30 army-surplus motherboard I got off ebay. I've tried about umpteen distros over the last few weeks. My advice, for xmr anyway, is keep it simple. Go with some ubuntu flavor (I'd do xubuntu or mint, except for cinnamon), don't go nuts on your config file. Every card I've tried so far likes 2 threads, and it'll pretty much always run with a raw intensity of 512. Except for my 280, which I agree is kind of a conundrum.
Can't say I'm as thrilled with 16.04, which is kind of a pig. Somewhat interested to see where radeon goes with this. Bet they ditch X altogether. Bet everyone does, except ubuntu. I won't miss it.
Re: Genesis Mining Presents: SGMiner-GM - now with Zawawa's GG! [Updated 17/01/2017]
I use work size 8, threads 1, and raw intensity 888 or 960. These seem to work best with all of my 280's and 7970's.
Anyone have optimal XMR intencity and worksize parameters for 280X?
I try --rawintensity 512 -w 4 -g 2
Changing any of them decreases speed.
I try --rawintensity 512 -w 4 -g 2
Changing any of them decreases speed.
Re: Genesis Mining Presents: SGMiner-GM - now with Zawawa's GG! [Updated 17/01/2017]
Update: After playing around with some bash scripting to monitor temps and adjust clocks, I had a hunch. Tried running sgminer with sudo. Blamo! Now have temps and fan speed control in the miner!
Running as root doesn't seem like a long term solution though. Does it?
No clock adjustment support either 
Also, now get this message on startup:
No sysfs pptable support for GPU0 ((null))
No sysfs pptable support for GPU1 ((null))
Good mining everybody!
Running as root doesn't seem like a long term solution though. Does it?
No clock adjustment support either Also, now get this message on startup:
No sysfs pptable support for GPU0 ((null))
No sysfs pptable support for GPU1 ((null))
Good mining everybody!
So, I enabled debug and logging so I could see. And, yes the problem is with the opening of the /sys/bus/pci/... files. I don't have much to contribute, but I do know from some other forums on setting and monitoring with the new drivers that you have to be root to access these directories. Hence I can manually set the fan speed with "echo 80 > /sys/class/DRM/card1/device/hwmon/hwmon0/pwm1" when root, but not as user or sudo.
I tried recompiling both with and without the ADL headers. Still not seeing fan speed or temps. Without the ADL headers it does complain during compile. And, I have no gpu-powertune settings in my config.
So, for now have gone back to 5.5.4. Still works great and I can see my temps. Hopefully it'll get straightened out and I'll try again.
Thanks GM team!
Edit: The ADL headers are no longer needed, if the binaries are used together with the AMDGPU driver.
Edit2: I figured out that gpu-powertune needs to be removed from the config if you're not using kernel 4.9 or later.
Did you try the master branch? There is a fix for invalid settings, which kind of crash the kernel. Just try with a minimal config. Futhermore, sgminer compiles withouts ADL headers.So, for now have gone back to 5.5.4. Still works great and I can see my temps. Hopefully it'll get straightened out and I'll try again.
Thanks GM team!
After moving from 5.5.4 to 5.5.5, it no longer shows gpu temp or fan speed. This is on lubuntu 16.04, amdgpu-pro 16.40, AMDSDK 3.0. And yes, I did move the required files to ADL_SDK. Any thoughts?
Hi, the difference between 5.5.4 and 5.5.5 is that the sysfs files are now opened by using the PCIe topology, i.e. if the miner fails to open the required files, then it should output something like "Failed to open /sys/bus/pci/devices/..." during startup when debugging is enabled. This was necessary in order to have the correct mapping between one GPU and it's sysfs files. Maybe you disabled this kind of GPU control during startup, i.e. just don't use --no-adl or "no-adl": true as command line argument or in the config file, if you want to have this information.Edit: The ADL headers are no longer needed, if the binaries are used together with the AMDGPU driver.
Edit2: I figured out that gpu-powertune needs to be removed from the config if you're not using kernel 4.9 or later.
Re: Genesis Mining Presents: SGMiner-GM - now with Zawawa's GG! [Updated 17/01/2017]
So, I enabled debug and logging so I could see. And, yes the problem is with the opening of the /sys/bus/pci/... files. I don't have much to contribute, but I do know from some other forums on setting and monitoring with the new drivers that you have to be root to access these directories. Hence I can manually set the fan speed with "echo 80 > /sys/class/DRM/card1/device/hwmon/hwmon0/pwm1" when root, but not as user or sudo.
I tried recompiling both with and without the ADL headers. Still not seeing fan speed or temps. Without the ADL headers it does complain during compile. And, I have no gpu-powertune settings in my config.
So, for now have gone back to 5.5.4. Still works great and I can see my temps. Hopefully it'll get straightened out and I'll try again.
Thanks GM team!
Edit: The ADL headers are no longer needed, if the binaries are used together with the AMDGPU driver.
Edit2: I figured out that gpu-powertune needs to be removed from the config if you're not using kernel 4.9 or later.
Did you try the master branch? There is a fix for invalid settings, which kind of crash the kernel. Just try with a minimal config. Futhermore, sgminer compiles withouts ADL headers.So, for now have gone back to 5.5.4. Still works great and I can see my temps. Hopefully it'll get straightened out and I'll try again.
Thanks GM team!
After moving from 5.5.4 to 5.5.5, it no longer shows gpu temp or fan speed. This is on lubuntu 16.04, amdgpu-pro 16.40, AMDSDK 3.0. And yes, I did move the required files to ADL_SDK. Any thoughts?
Hi, the difference between 5.5.4 and 5.5.5 is that the sysfs files are now opened by using the PCIe topology, i.e. if the miner fails to open the required files, then it should output something like "Failed to open /sys/bus/pci/devices/..." during startup when debugging is enabled. This was necessary in order to have the correct mapping between one GPU and it's sysfs files. Maybe you disabled this kind of GPU control during startup, i.e. just don't use --no-adl or "no-adl": true as command line argument or in the config file, if you want to have this information.Edit: The ADL headers are no longer needed, if the binaries are used together with the AMDGPU driver.
Edit2: I figured out that gpu-powertune needs to be removed from the config if you're not using kernel 4.9 or later.