Author

Topic: [Mining OS] SimpleMining.net - Manage Your GPU farm the easy way! (30 days free) - page 499. (Read 836164 times)

legendary
Activity: 4354
Merit: 9201
'The right to privacy matters'
Yep, new Beta updates (which you need to use yourself) :
- first beta kernel update 4.11
- then beta amd driver 16.60
And the speeds are very close to windows.
And i dont need to tell you how windows vs linux works in other maters Smiley

OK, can anyone from you confirm that MSI Z170 or Z270 is working or not working ?
Also how many gpus did anyone tested on those motherboards ?

I am looking for 6GPU motherboard cheapest alternative and the MSI Z170 and Z270 are one my aim right now.
But i need to confirm if they are working with SMOS without problems ? (becasue i had reports that there was problems Smiley

this board works  and does 5 as tested by me

https://www.amazon.com/gp/product/B01N2V0AHI/ref=oh_aui_detailpage_o03_s00?

It may do six I just never tested six.
legendary
Activity: 4354
Merit: 9201
'The right to privacy matters'
Somehow I can't get my miner to mine on Alpereum pool

Anyone knows how to join this, my miner just crash everytime it tries to join this pool.

Dwarfpool works fine.

Thanks.

give me a link to the pool I will try to figure out the issue

https://www.alpereum.ch Smiley

can't get it to work so far

 -s pool.alpereum.ch:3001 -u 0x2e577Eb55514b083825cfF4Fa51db598621A1F8a.test
sr. member
Activity: 487
Merit: 252
bou !
My problem is the hasrate that receives nanopool, I lose about 30mh on 390 Sad

I ask myself the question, maybe with your bone it will be better ....

I will try to test ..

legendary
Activity: 2660
Merit: 1096
Simplemining.net Admin
Yep, new Beta updates (which you need to use yourself) :
- first beta kernel update 4.11
- then beta amd driver 16.60
And the speeds are very close to windows.
And i dont need to tell you how windows vs linux works in other maters Smiley

OK, can anyone from you confirm that MSI Z170 or Z270 is working or not working ?
Also how many gpus did anyone tested on those motherboards ?

I am looking for 6GPU motherboard cheapest alternative and the MSI Z170 and Z270 are one my aim right now.
But i need to confirm if they are working with SMOS without problems ? (becasue i had reports that there was problems Smiley
sr. member
Activity: 366
Merit: 250
@tytanick: I would like to know if with this osss, my hasrate is better to represent rather than with windows?

Because on my pool I am always inferior,

Thx


you are correct.  you will do say 28 or 29  on windows  vs 27 or 28 a card here.

This isn't true anymore, hashing with new kerner and driver gives exactly same result like windows.
sr. member
Activity: 366
Merit: 250
I am now experiencing the 300/300 problem with gpu0, regardless of how I set up my rig or which PCIe slot I use.

Before this afternoon, everything was cruising along fine for the last week with my 3 x MSI rx 470 gaming 4GB rig. Today, I received risers in the mail, and proceeded to make my 3 gpu rig into a 6 gpu rig. I eventually managed to get it to boot up and everything looked like it was going as planned, but gpu0 was stuck at 4.04 mh/s (with the dashboard indicating it was clocked at 300/300), while the rest of the cards performed as expected.

I began working backwards, thinking I had a hardware problem, but after a couple rounds of unplugging what I thought was gpu0, and upon reboot, gpu0 still operating at 4.xx mh/s with the dashboard indicting the card was clocked at 300/300, I started to suspect otherwise. I finally got down to one card, and after several reboots and moving it around to several different PCIe slots, same thing.

I upgraded to the beta 4.11 kernel, and that didn't help.

After all of that, I started reversing the other changes I made to my rig in anticipation of adding additional cards. I purchased an MSI Z170A Gaming M5 mobo because all of the mobos traditionally favored by miners are scarce and, to put it politely, selling at a premium. There are several people who said they were able to get 7 cards running on this board, and they outlined the changes to the BIOS that were necessary. When I undid those changes, my gpu0 went back to working correctly. The changes to the BIOS consisted of the following to the PCI subsystem settings:

PEG0 - Max Link Speed: change from [Auto] to [Gen1]
PEG1 - Max Link Speed: change from [Auto] to [Gen1]
Above 4G Decoding: [Disabled] to [Enabled]

Through process of elimination (i.e., testing my system with only one card installed directly on the mobo), I determined that changing PEG1 - Max Link Speed from [Auto] to [Gen1] is the culprit. As long as I leave that setting on auto, I can change the other two settings as described above and gpu0 functions properly, but as soon as I change the PEG1 setting, gpu0 goes back to 4.xx mh/s and 300/300 on the dashboard.

To be clear, I didn't type all of this up because I expect someone to help me. To the contrary, this is a hobby to me, and I will work through it. However, it seems like the 300/300 problem has reared its ugly head multiple times without a decisive resolution of the underlying cause. I'm just hoping that the info I provided will help tytanick diagnose the problem.


Does any1 solve this problem? I have the same  Sad

Are you overclocking etc?

If yes, try to work from stock default settings, and move up until you hit that 300/300 issue.

No default settings is solving it, but I don't have any good news here I am facing this problem since January. It is not hardware related problem, it is something wrong with ubuntu or claymore eth miner. I have exactly the same, exchanged gpus, risers, slots, mixed cards, exchnaged MB, ram, PSU everything, gpus are crashing randomly. Also I have check ethOS, it is exactly the same. So it is not tytanick's fault anywhere. I was able to solved it partialy, it runs smoontly for weeks on windows machine (same configuration, same parts same everything), only windows instead of linux. Oh and yeee no bios , no straps working either. You can set default bios with default straps and  gpus will still hang on ubuntu. New drivers and kernel isn't solving this issue either.
newbie
Activity: 8
Merit: 0
Somehow I can't get my miner to mine on Alpereum pool

Anyone knows how to join this, my miner just crash everytime it tries to join this pool.

Dwarfpool works fine.

Thanks.

give me a link to the pool I will try to figure out the issue

https://www.alpereum.ch Smiley
0x2e577Eb55514b083825cfF4Fa51db598621A1F8a
legendary
Activity: 4354
Merit: 9201
'The right to privacy matters'
Somehow I can't get my miner to mine on Alpereum pool

Anyone knows how to join this, my miner just crash everytime it tries to join this pool.

Dwarfpool works fine.

Thanks.

give me a link to the pool I will try to figure out the issue
newbie
Activity: 8
Merit: 0
Somehow I can't get my miner to mine on Alpereum pool

Anyone knows how to join this, my miner just crash everytime it tries to join this pool.

Dwarfpool works fine.

Thanks.
legendary
Activity: 4354
Merit: 9201
'The right to privacy matters'
@tytanick: I would like to know if with this osss, my hasrate is better to represent rather than with windows?

Because on my pool I am always inferior,

Thx


you are correct.  you will do say 28 or 29  on windows  vs 27 or 28 a card here.


This os is about this:

  multi rigs  that you can control anywhere in the world with ease.

stable  systems that run for  weeks on end

lastly  srr   will re set a frozen rig automatically.

the ability to switch from coin to coin in around 1 minute  for every rig  even 50 or 60 or 70 rigs


See below



sr. member
Activity: 487
Merit: 252
bou !
@tytanick: I would like to know if with this osss, my hasrate is better to represent rather than with windows?

Because on my pool I am always inferior,

Thx
member
Activity: 68
Merit: 10
I am having an issue where my rig is mining but it isn't being displayed in my simplemining.net/dashboard. I have saved my email address to the config.txt.

I have noticed that in Ubuntu it says when starting,

YOUR EMAIL:
####################

and nothing updates when I change options on my dashboard
sr. member
Activity: 441
Merit: 252

Tytanick,

If you are working on this for next release or future release...

Can I upload my own epool.txt and which directory should I upload the file to?

Thanks

And dpool.txt too while you're at it Wink
legendary
Activity: 1834
Merit: 1080
---- winter*juvia -----
Hello T

Is there a way to put failover pools in epools.text automatically for Claymore ETH ?

Currently sgminer-GM ETH you can define failover pools in the same command line BUT for Claymore need to update the epools.text file.

Maeby..... put up to 3 failover pools in data entry field like what you did for BTC/ETH/SIA address?

What say you?

Thanks
Citronick



Tytanick,

If you are working on this for next release or future release...

Can I upload my own epool.txt and which directory should I upload the file to?

Thanks
legendary
Activity: 1834
Merit: 1080
---- winter*juvia -----
I am now experiencing the 300/300 problem with gpu0, regardless of how I set up my rig or which PCIe slot I use.

Before this afternoon, everything was cruising along fine for the last week with my 3 x MSI rx 470 gaming 4GB rig. Today, I received risers in the mail, and proceeded to make my 3 gpu rig into a 6 gpu rig. I eventually managed to get it to boot up and everything looked like it was going as planned, but gpu0 was stuck at 4.04 mh/s (with the dashboard indicating it was clocked at 300/300), while the rest of the cards performed as expected.

I began working backwards, thinking I had a hardware problem, but after a couple rounds of unplugging what I thought was gpu0, and upon reboot, gpu0 still operating at 4.xx mh/s with the dashboard indicting the card was clocked at 300/300, I started to suspect otherwise. I finally got down to one card, and after several reboots and moving it around to several different PCIe slots, same thing.

I upgraded to the beta 4.11 kernel, and that didn't help.

After all of that, I started reversing the other changes I made to my rig in anticipation of adding additional cards. I purchased an MSI Z170A Gaming M5 mobo because all of the mobos traditionally favored by miners are scarce and, to put it politely, selling at a premium. There are several people who said they were able to get 7 cards running on this board, and they outlined the changes to the BIOS that were necessary. When I undid those changes, my gpu0 went back to working correctly. The changes to the BIOS consisted of the following to the PCI subsystem settings:

PEG0 - Max Link Speed: change from [Auto] to [Gen1]
PEG1 - Max Link Speed: change from [Auto] to [Gen1]
Above 4G Decoding: [Disabled] to [Enabled]

Through process of elimination (i.e., testing my system with only one card installed directly on the mobo), I determined that changing PEG1 - Max Link Speed from [Auto] to [Gen1] is the culprit. As long as I leave that setting on auto, I can change the other two settings as described above and gpu0 functions properly, but as soon as I change the PEG1 setting, gpu0 goes back to 4.xx mh/s and 300/300 on the dashboard.

To be clear, I didn't type all of this up because I expect someone to help me. To the contrary, this is a hobby to me, and I will work through it. However, it seems like the 300/300 problem has reared its ugly head multiple times without a decisive resolution of the underlying cause. I'm just hoping that the info I provided will help tytanick diagnose the problem.


Does any1 solve this problem? I have the same  Sad

Are you overclocking etc?

If yes, try to work from stock default settings, and move up until you hit that 300/300 issue.
newbie
Activity: 8
Merit: 0
I am now experiencing the 300/300 problem with gpu0, regardless of how I set up my rig or which PCIe slot I use.

Before this afternoon, everything was cruising along fine for the last week with my 3 x MSI rx 470 gaming 4GB rig. Today, I received risers in the mail, and proceeded to make my 3 gpu rig into a 6 gpu rig. I eventually managed to get it to boot up and everything looked like it was going as planned, but gpu0 was stuck at 4.04 mh/s (with the dashboard indicating it was clocked at 300/300), while the rest of the cards performed as expected.

I began working backwards, thinking I had a hardware problem, but after a couple rounds of unplugging what I thought was gpu0, and upon reboot, gpu0 still operating at 4.xx mh/s with the dashboard indicting the card was clocked at 300/300, I started to suspect otherwise. I finally got down to one card, and after several reboots and moving it around to several different PCIe slots, same thing.

I upgraded to the beta 4.11 kernel, and that didn't help.

After all of that, I started reversing the other changes I made to my rig in anticipation of adding additional cards. I purchased an MSI Z170A Gaming M5 mobo because all of the mobos traditionally favored by miners are scarce and, to put it politely, selling at a premium. There are several people who said they were able to get 7 cards running on this board, and they outlined the changes to the BIOS that were necessary. When I undid those changes, my gpu0 went back to working correctly. The changes to the BIOS consisted of the following to the PCI subsystem settings:

PEG0 - Max Link Speed: change from [Auto] to [Gen1]
PEG1 - Max Link Speed: change from [Auto] to [Gen1]
Above 4G Decoding: [Disabled] to [Enabled]

Through process of elimination (i.e., testing my system with only one card installed directly on the mobo), I determined that changing PEG1 - Max Link Speed from [Auto] to [Gen1] is the culprit. As long as I leave that setting on auto, I can change the other two settings as described above and gpu0 functions properly, but as soon as I change the PEG1 setting, gpu0 goes back to 4.xx mh/s and 300/300 on the dashboard.

To be clear, I didn't type all of this up because I expect someone to help me. To the contrary, this is a hobby to me, and I will work through it. However, it seems like the 300/300 problem has reared its ugly head multiple times without a decisive resolution of the underlying cause. I'm just hoping that the info I provided will help tytanick diagnose the problem.


Does any1 solve this problem? I have the same  Sad
hero member
Activity: 672
Merit: 500
Hello, this question is to someone who is using smOS with 4+ GPUs on same board.
Are you using just the image for RX or you are adding additional swap space on top of it.
Is it really needed? Like on windows Claymore suggest 16GB+ virtual memory.


nope you dont really need any swap space with this linux distro
its a very basic OS uses around 1G of memory.
so you could get by with only 2G of ram
windows is also a recourse hog thats why you need to increase the physical memory limit
legendary
Activity: 1834
Merit: 1080
---- winter*juvia -----
Hello, this question is to someone who is using smOS with 4+ GPUs on same board.
Are you using just the image for RX or you are adding additional swap space on top of it.
Is it really needed? Like on windows Claymore suggest 16GB+ virtual memory.


In my lttle of knowledge of Linux.... swap files are dynamic and better optimised. That's why 4GB memory on most cases is more than sufficient.

You basically don't need to do anything apart from getting the RX or RX images to work on your USB, HDD or mSATA SSD.

Maybe the Linux experts can add on.
newbie
Activity: 29
Merit: 0
Hello, this question is to someone who is using smOS with 4+ GPUs on same board.
Are you using just the image for RX or you are adding additional swap space on top of it.
Is it really needed? Like on windows Claymore suggest 16GB+ virtual memory.
member
Activity: 61
Merit: 10
So just to clear this g up.. the NEW KERNEL + AMD drivers are only for the Rx image? I'm running R image and just want to check before updating.

Keep up the good work Tytanick
Yes its only for RX OS. In 4 OS the update button should be unavailable - It is not available right ?

The beta menu and updates are showing as available for me but not an issue.Planning to upgrade all of the old r9 series rigs this month and running rx470's in a few new builds.

On the topic of RX series what RX470/480's are performing the best currently with smos?

Thought it best to ask the smos community  Wink Smiley

Hello!

I am not sure if I understood the first sentence, just in case i'll say it! Do not update your R9 cards to the new beta build. The new beta build is only for RX cards (The kernel and the amd). Please update the kernel first and then the amd driver.

Our RX 470 and 480 are doing great overall. Most of our cards now do the same hashrate compared to windows. We just have a few left hashing for 0.2 to 0.35 less than what they used to do on windows. For the remote managing, we honestly couldn't care less. That OS was exactly what we needed to manage our farm.

Best of luck!
Jump to: