tytanick,
Is there a way to flip the display 180 deg using the smos shell commands?
Thanks.
Topic: [Mining OS] SimpleMining.net - Manage Your GPU farm the easy way! (30 days free) - page 74. (Read 836250 times)
October 05, 2019, 09:11:29 AM
October 02, 2019, 07:22:27 AM
Miners update:
- cryptodredge-v0.22.0 (New X16RV2 algo. Fix Stratum issue related to "resource deadlock would occur". Fix API. Other minor fixes)
- nanominer-v1.6.0 (Added RandomHash2 algo for Pascal. DevFee increased from 3% to 5% for both RandomHash and RandomHash2 to support RandomHash2 development. Cuckarood29 faster up to 24% on AMD and Nvidia. Updated node protocol supported for QuarkChain. Wallet can now be set up in miner's configuration file, not only configured on node itself. Public full nodes are used by default)
- cryptodredge-v0.22.0 (New X16RV2 algo. Fix Stratum issue related to "resource deadlock would occur". Fix API. Other minor fixes)
- nanominer-v1.6.0 (Added RandomHash2 algo for Pascal. DevFee increased from 3% to 5% for both RandomHash and RandomHash2 to support RandomHash2 development. Cuckarood29 faster up to 24% on AMD and Nvidia. Updated node protocol supported for QuarkChain. Wallet can now be set up in miner's configuration file, not only configured on node itself. Public full nodes are used by default)
September 28, 2019, 12:58:57 PM
Miners update:
- gminer-v1.67 (performance improvements for cuckarood29 - specially on RTX cards)
- gminer-v1.67 (performance improvements for cuckarood29 - specially on RTX cards)
September 27, 2019, 04:56:18 AM
Miners update:
- tt-miner-v3.0.9 (Removed library depency to cuda 10.1 for ProgPoWZ and Ubiq. Shows information about the DAG size and the available memory. Fixes another bug with the device option: -d)
- z-enemy-v2.2 (Added x16rv2 algo for upcoming Ravencoin hardfor. Added support for secure stratum+ssl connections. New --no-cert-verify key. Fixed phi2 bug on Cuda 10.1)
- tt-miner-v3.0.9 (Removed library depency to cuda 10.1 for ProgPoWZ and Ubiq. Shows information about the DAG size and the available memory. Fixes another bug with the device option: -d)
- z-enemy-v2.2 (Added x16rv2 algo for upcoming Ravencoin hardfor. Added support for secure stratum+ssl connections. New --no-cert-verify key. Fixed phi2 bug on Cuda 10.1)
September 26, 2019, 03:44:45 AM
Miners update:
- teamredminer-v0.5.9 (Added x16rv2 for Ravencoin fork. Faster 8-10% x16r. Memory clock no longer as important for x16r. Kernels split into multiple binaries to fix amd driver issues)
- teamredminer-v0.5.9 (Added x16rv2 for Ravencoin fork. Faster 8-10% x16r. Memory clock no longer as important for x16r. Kernels split into multiple binaries to fix amd driver issues)
September 25, 2019, 02:32:19 PM
Miners update:
- t-rex-v0.14.4 (Add x16rv2 algorithm (upcoming RVN fork). Add auto-switch mining algorithm using --fork-at)
- t-rex-v0.14.4 (Add x16rv2 algorithm (upcoming RVN fork). Add auto-switch mining algorithm using --fork-at)
Good direction. it would enlarge Nvidia's GPU capacity of mining.
September 25, 2019, 09:25:15 AM
Miners update:
- t-rex-v0.14.4 (Add x16rv2 algorithm (upcoming RVN fork). Add auto-switch mining algorithm using --fork-at)
- t-rex-v0.14.4 (Add x16rv2 algorithm (upcoming RVN fork). Add auto-switch mining algorithm using --fork-at)
September 25, 2019, 05:04:21 AM
Miners update:
- gminer-v1.66 (10% faster cuckarood29)
- tt-miner-v3.0.6 (Autodetect cuda library version - no longer need to append -092/-100/-101 to algo. Faster start. Support EPIC/Progpow. Added multi-mining alternate coin mode. New option -poolinfo. Added new coins for the -coin command line option for improve the DAG handling and avoid double creations of the DAG)
- gminer-v1.66 (10% faster cuckarood29)
- tt-miner-v3.0.6 (Autodetect cuda library version - no longer need to append -092/-100/-101 to algo. Faster start. Support EPIC/Progpow. Added multi-mining alternate coin mode. New option -poolinfo. Added new coins for the -coin command line option for improve the DAG handling and avoid double creations of the DAG)
September 23, 2019, 07:04:38 AM
Advanced Cmd update:
- now possible of using your own local web or ftp server with copy of SimpleMining OS image file by specifying any full URL address to save your internet connection traffic limits (detailed info in dashboard by selecting „Advanced Cmd” and then „OS reflash custom image”)
- fixed random text color in console during reflashing process
- now possible of using your own local web or ftp server with copy of SimpleMining OS image file by specifying any full URL address to save your internet connection traffic limits (detailed info in dashboard by selecting „Advanced Cmd” and then „OS reflash custom image”)
- fixed random text color in console during reflashing process
September 21, 2019, 11:36:31 AM
Miners update:
- teamredminer-v0.5.8 (Added Chukwa-512 for Turtlecoin. Fix for kernels not loaded properly for Conceal. Added logic for pool reconnect on N rejected shares in a row)
- teamredminer-v0.5.8 (Added Chukwa-512 for Turtlecoin. Fix for kernels not loaded properly for Conceal. Added logic for pool reconnect on N rejected shares in a row)
September 19, 2019, 07:19:55 AM
I have sent the email ...
Though I totally agree. This method of 'support' is archaic and outdated. I will see what the chat is all about, and try to get online there.
Either way, the email is sent with the details of the Account and Rig. This is a test system, and NOT the rest of the mining systems we have, so I will work on these older units to fathom whether the switch to a system like SMOS will be a viable switch for us and theFARM.
Thanks so much for your help.
#crysx
Though I totally agree. This method of 'support' is archaic and outdated. I will see what the chat is all about, and try to get online there.
Either way, the email is sent with the details of the Account and Rig. This is a test system, and NOT the rest of the mining systems we have, so I will work on these older units to fathom whether the switch to a system like SMOS will be a viable switch for us and theFARM.
Thanks so much for your help.
#crysx
Ok. i wrote reply.
Most probably this is the case that rig with old graphics can handle up to 8 GPUs and while there are 10 GPUs in system it does not work.
8 GPUs should be working fine but it would be best to test with 6 GPUs first.
September 19, 2019, 05:13:51 AM
What should I do next to get this running?
Please just wrote to me at [email protected]
And tell me you email account (not here !) and name of this rig (if you have more of them).
Please leave this rig online for next 3 hours and we will check it and let you know whats wrong.
OK ...
I'll do just that mate. I appreciate this help.
I don't usually frequent emails, only here and Discord, but I will do this now.
Thanks.
#crysx
Getting support via bitcointalk is pain in the .....
It is better just to write also on chat.simplemining.net - you will get instant help there. But i will wait for your email and check whats wrong
I have sent the email ...
Though I totally agree. This method of 'support' is archaic and outdated. I will see what the chat is all about, and try to get online there.
Either way, the email is sent with the details of the Account and Rig. This is a test system, and NOT the rest of the mining systems we have, so I will work on these older units to fathom whether the switch to a system like SMOS will be a viable switch for us and theFARM.
Thanks so much for your help.
#crysx
September 19, 2019, 04:59:08 AM
What should I do next to get this running?
Please just wrote to me at [email protected]
And tell me you email account (not here !) and name of this rig (if you have more of them).
Please leave this rig online for next 3 hours and we will check it and let you know whats wrong.
OK ...
I'll do just that mate. I appreciate this help.
I don't usually frequent emails, only here and Discord, but I will do this now.
Thanks.
#crysx
Getting support via bitcointalk is pain in the .....
It is better just to write also on chat.simplemining.net - you will get instant help there. But i will wait for your email and check whats wrong
September 19, 2019, 04:57:42 AM
What should I do next to get this running?
Please just wrote to me at [email protected]
And tell me you email account (not here !) and name of this rig (if you have more of them).
Please leave this rig online for next 3 hours and we will check it and let you know whats wrong.
OK ...
I'll do just that mate. I appreciate this help.
I don't usually frequent emails, only here and Discord, but I will do this now.
Thanks.
#crysx
September 19, 2019, 04:43:04 AM
What should I do next to get this running?
Please just wrote to me at [email protected]
And tell me you email account (not here !) and name of this rig (if you have more of them).
Please leave this rig online for next 3 hours and we will check it and let you know whats wrong.
September 19, 2019, 04:40:36 AM
Tytanick ...
The image downloaded and copied to the USB without a hitch.
Bootup went without a hitch.
Running the miner - dead.
It seems you no longer have the miners required to run these older versions of the OS in your repository, so that these older cards can mine.
I have to admit, this seems to be the simplest and quickest way to get running, but unfortunately, SMOS requires the miners which no longer exist in your repos. What needs to be done here, and what are the next steps required to get this machine running? If you don't mind, I would also like to ask what miners is this version of SMOS after?
#crysx
The image downloaded and copied to the USB without a hitch.
Bootup went without a hitch.
Running the miner - dead.
It seems you no longer have the miners required to run these older versions of the OS in your repository, so that these older cards can mine.
I have to admit, this seems to be the simplest and quickest way to get running, but unfortunately, SMOS requires the miners which no longer exist in your repos. What needs to be done here, and what are the next steps required to get this machine running? If you don't mind, I would also like to ask what miners is this version of SMOS after?
#crysx
Can you tell me what GPUs models do you are using and which image did you flashed your pendrive with ?
About miner programms. We have all most frequently used miner programms in SMOS.
It is not up to us if miner program support some GPU or does not support it.
I need more details. What OS you used, what GPU model you have and what miner programm are you trying to run.
Then we will verify where is problem.
It whould be faster if you would just write to [email protected]
Write there your email account and rig that has problems and we will look into it - please leave it running - we will check it within 2 hours
Hi Tytanick ...
The OS was the one you pointed me to -
Yes, try using this image especially for R200 series and HD series.
https://download.simplemining.net/images/SimpleMiningOS-R-v1235-4.2.0.img.zip
- which seems to work really well until it starts to download the miner. I know you are inundated with work, but if you look up a few posts in my previous post, the cards are older GigaByte 7970/280x oc Cards. We have many of them, and just want them mining. You referred me to the download link of the OS Image, which is working as it should be thus far. The only thing that is missing is the miners that SMOS is looking for in your repositories.
What should I do next to get this running?
#crysx
September 19, 2019, 04:27:30 AM
Tytanick ...
The image downloaded and copied to the USB without a hitch.
Bootup went without a hitch.
Running the miner - dead.
It seems you no longer have the miners required to run these older versions of the OS in your repository, so that these older cards can mine.
I have to admit, this seems to be the simplest and quickest way to get running, but unfortunately, SMOS requires the miners which no longer exist in your repos. What needs to be done here, and what are the next steps required to get this machine running? If you don't mind, I would also like to ask what miners is this version of SMOS after?
#crysx
The image downloaded and copied to the USB without a hitch.
Bootup went without a hitch.
Running the miner - dead.
It seems you no longer have the miners required to run these older versions of the OS in your repository, so that these older cards can mine.
I have to admit, this seems to be the simplest and quickest way to get running, but unfortunately, SMOS requires the miners which no longer exist in your repos. What needs to be done here, and what are the next steps required to get this machine running? If you don't mind, I would also like to ask what miners is this version of SMOS after?
#crysx
Can you tell me what GPUs models do you are using and which image did you flashed your pendrive with ?
About miner programms. We have all most frequently used miner programms in SMOS.
It is not up to us if miner program support some GPU or does not support it.
I need more details. What OS you used, what GPU model you have and what miner programm are you trying to run.
Then we will verify where is problem.
It whould be faster if you would just write to [email protected]
Write there your email account and rig that has problems and we will look into it - please leave it running - we will check it within 2 hours
September 19, 2019, 04:09:52 AM
tytanick ...
Is there ANY software in SMOS that will allow mining via the old AMD cards at all?
Specifically 7970/280x as we have found quite a number of them and are building machines out of all of them. The issue is the support/installs have all but disappeared, and I have personally been looking into what could be used in place of a full install/hack ed system to get these cards to run.
If you can provide a distro that supports these cards (as old and nn-supported by AMD as they are), then using these cards in a mining environment will be worth the effort.
I am no newbie here, and have been around for some time (over 8.5years now), so comments about why, when, where, how, and why not kill those cards is not what I am after. We have a considerable GPU processing plant already, and are highly experience, but honestly, with the lack of support from AMD, I am personally stumped now. I guess that is why nVidia has the largest world marketshare to date.
In any case, I will be happy to explore the possibility of reimbursement of sorts for such a mining distro that will allow me to use this small farm of cards to their fullest.
It will be much appreciated.
#crysx
Is there ANY software in SMOS that will allow mining via the old AMD cards at all?
Specifically 7970/280x as we have found quite a number of them and are building machines out of all of them. The issue is the support/installs have all but disappeared, and I have personally been looking into what could be used in place of a full install/hack ed system to get these cards to run.
If you can provide a distro that supports these cards (as old and nn-supported by AMD as they are), then using these cards in a mining environment will be worth the effort.
I am no newbie here, and have been around for some time (over 8.5years now), so comments about why, when, where, how, and why not kill those cards is not what I am after. We have a considerable GPU processing plant already, and are highly experience, but honestly, with the lack of support from AMD, I am personally stumped now. I guess that is why nVidia has the largest world marketshare to date.
In any case, I will be happy to explore the possibility of reimbursement of sorts for such a mining distro that will allow me to use this small farm of cards to their fullest.
It will be much appreciated.
#crysx
Yes, try using this image especially for R200 series and HD series.
https://download.simplemining.net/images/SimpleMiningOS-R-v1235-4.2.0.img.zip
This image has FGLRX old drivers that are needed for support of those old cards.
This should work. But as i saw i have like 0.1% of rigs that are using so old amd gpus
On top of that you need o use alghoritm that will use low memory and will be compatible with those old cards.
Let me know if this is working.
If you still have some problems, you can ask on chat.simplemining.net as i will not be available here.
I appreciate that mate ...
There may be only a few using the older cards, but support is important to our mining systems, and farm, even though we are probably one of the last to pull up the old cards out of the dust holes they lived in these last few years
I will let you know as soon as I am able to test the units at the end of this week.
Seriously, much appreciated.
#crysx
Tytanick ...
The image downloaded and copied to the USB without a hitch.
Bootup went without a hitch.
Running the miner - dead.
It seems you no longer have the miners required to run these older versions of the OS in your repository, so that these older cards can mine.
I have to admit, this seems to be the simplest and quickest way to get running, but unfortunately, SMOS requires the miners which no longer exist in your repos. What needs to be done here, and what are the next steps required to get this machine running? If you don't mind, I would also like to ask what miners is this version of SMOS after?
#crysx
September 19, 2019, 02:30:57 AM
Unable to successfully use the SimpleMiningImager.
(...)
In windows, I can only see the 2.50 GB FAT32 partition and in order to access it I have to format it.
(...)
In windows, I can only see the 2.50 GB FAT32 partition and in order to access it I have to format it.
I guess you miss one little step.
After successful flashing SM Imager using balenaEtcher you should unplug the drive and plug again in order to see this 2.5G FAT32 partition in explorer under windows (on Mac is the same procedure). After that you should see in explorer disk named "SMOS_IMAGER" with two txt files (config.txt and options.txt)
Please try again.
About content of SM Imager .img file... just flash SM Imager img file (unpacked) or even original img.xz (without unpacking before flashing)
About putting SimpleMiningOS image on that partition. Do not unpack. Just put img.zip or img.xz file on this FAT32 partition. Packed image is 500MB size (older images are 1GB size), and those files after unpacking are 7GB size - will not fit on this partition anyway.
Remember to securely unplug/unmount this disk after putting SMOS image and editing config.txt file before you unplug the drive from USB to make sure every data is saved properly.
If all failed, start again using newest balena Etcher version. Procedure is same as with flashing our every SMOS image. Download, flash, unplug drive, plug again...and than partition (SMOS_CONFIG or SMOS_IMAGER) should be seen properly.
Please let us know if this help.
September 18, 2019, 09:40:03 PM
Unable to successfully use the SimpleMiningImager. I downloaded the SMI-v1.5.img.xz file and flashed it to usb drive with etcher. I tried two different ways, flashing the unzipped image from the SMI-v1.5.img.xz to usb as well as flashing with just the SMI-v1.5.img.xz file. The results of this is I have a usb with:
32mb unallocated partition
2.50 GB FAT32 partition (of which I have to format in order to use this in windows.) I'm assuming this is the partition where smos image is supposed to be placed? Should I place the unzipped or zipped smos image in there?
1.50 GB partition
25.85 GB partition unallocated.
In windows, I can only see the 2.50 GB FAT32 partition and in order to access it I have to format it.
I don't see the config.txt or options.txt in this partition (obviously because I formatted it) I am assuming either: these files are on this partition but I formatted over them, or they are on another partition I can't access.
I notice that looking at the contents of SMI-v1.5.img: 0.img and 1.fat, whereas the normal smos image is 0.fat and 1.img i wonder if that has anything to do with how etcher creates the usb image, making it so I can't see what I need to see.
32mb unallocated partition
2.50 GB FAT32 partition (of which I have to format in order to use this in windows.) I'm assuming this is the partition where smos image is supposed to be placed? Should I place the unzipped or zipped smos image in there?
1.50 GB partition
25.85 GB partition unallocated.
In windows, I can only see the 2.50 GB FAT32 partition and in order to access it I have to format it.
I don't see the config.txt or options.txt in this partition (obviously because I formatted it) I am assuming either: these files are on this partition but I formatted over them, or they are on another partition I can't access.
I notice that looking at the contents of SMI-v1.5.img: 0.img and 1.fat, whereas the normal smos image is 0.fat and 1.img i wonder if that has anything to do with how etcher creates the usb image, making it so I can't see what I need to see.
Jump to: