I have followed the steps to image nvOC onto a drive however when I boot I get the login screen which show m1 user and guest with required passwords. I'm stuck on what to do next any advice would be greatly appreciated
It looks like a nvidia driver problem, ssh or login to tty and install nvidia-430
Post
Topic
BoardMining (Altcoins)
Re: [OS] nvOC Community Release free-easy-to-use Linux Nvidia Mining
Just a heads up that the Mega site down load of nvOC3.2 is corrupted and is only 2.85gigs while Google Drive is over 10 gigs. Had a long and hard fight as to why it would not boot up normal.
On your search for where the miners are launched, I have zeroed in on the Screen.rc files. As I still have issues with Python code, I have not figured it out either. Papampi is the man of the hour there. As of now, A 10head and a 4 head up and running 3.2 with all upgrades. Viva la Papampi.
And a big thanks to all of you who made NVOC happen and made it better
thay
Checkout nvOC github wiki All 19-3.2, Ubuntu 16.04, Cuda 9.2, Nvidia 418 images are 2.85 Gb
Post
Topic
BoardMining (Altcoins)
Re: [OS] nvOC Community Release free-easy-to-use Linux Nvidia Mining
Please tell me how can I fix the gtx1080 rig crash problem with using ohgodanethlagermentpill-r2 and mining eth. The rig crashes when running the utility.
1080ti rigs work well
Made some changes so you can use eth-pill flags Upgrade nvOC check new 1bash.template or Add this line after OhGodAnETHlargementPill="YES"
Code:
OhGodAnETHlargementPill_OPTS="" # Variables/Flags for ETH Pill
And add your variables
restart miner and check ethpill guake terminal
Let me know how it goes...
This did not fix the problem .. I add settings flag "--revA 0,1,2,3,4,5,6". And rig crash momently how run ohgodanethlagermentpill-r2
I try run mining eth with nbminer with the memory tweek option (nbminer opt "-mt 2") . The miner don't run and asks to run as administrator rules, how to do this in NVOC?
In nbminer folder open nvoc-mjner.json edit hcd line and add sudo before nbminer command like this:
Code:
"hcd": "sudo nbminer -o ...."
See if it solve your issue
Not solve
OK I made a mistake, revert nvoc-miner.json back to its default. Open 0miner and edit line 216 from:
Code:
eval $LAUNCH $HCD $OPTS
to
Code:
eval $LAUNCH sudo $HCD $OPTS
Post
Topic
BoardMining (Altcoins)
Re: [OS] nvOC Community Release free-easy-to-use Linux Nvidia Mining
Please tell me how can I fix the gtx1080 rig crash problem with using ohgodanethlagermentpill-r2 and mining eth. The rig crashes when running the utility.
1080ti rigs work well
Made some changes so you can use eth-pill flags Upgrade nvOC check new 1bash.template or Add this line after OhGodAnETHlargementPill="YES"
Code:
OhGodAnETHlargementPill_OPTS="" # Variables/Flags for ETH Pill
And add your variables
restart miner and check ethpill guake terminal
Let me know how it goes...
This did not fix the problem .. I add settings flag "--revA 0,1,2,3,4,5,6". And rig crash momently how run ohgodanethlagermentpill-r2
I try run mining eth with nbminer with the memory tweek option (nbminer opt "-mt 2") . The miner don't run and asks to run as administrator rules, how to do this in NVOC?
In nbminer folder open nvoc-mjner.json edit hcd line and add sudo before nbminer command like this:
Code:
"hcd": "sudo nbminer -o ...."
See if it solve your issue
Post
Topic
BoardMining (Altcoins)
Re: [OS] nvOC Community Release free-easy-to-use Linux Nvidia Mining
Please tell me how can I fix the gtx1080 rig crash problem with using ohgodanethlagermentpill-r2 and mining eth. The rig crashes when running the utility.
1080ti rigs work well
Made some changes so you can use eth-pill flags Upgrade nvOC check new 1bash.template or Add this line after OhGodAnETHlargementPill="YES"
Code:
OhGodAnETHlargementPill_OPTS="" # Variables/Flags for ETH Pill
And add your variables
restart miner and check ethpill guake terminal
Post
Topic
BoardMining (Altcoins)
Re: [OS] nvOC Community Release free-easy-to-use Linux Nvidia Mining
After issuing the command "bash /home/m1/NVOC/mining/nvOC restore-xorg", and running through a couple reboots, the system started properly. I am able to sit at the keyboard and watch the miner, and able to reach the console via SSH.
I no longer need to issue a manual command to start the miner. Nvidia-smi properly displays the video cards information. And, the system is now running Ubuntu 18.04.
Thank you! --scryptr
Glad its all OK.
Post
Topic
BoardMining (Altcoins)
Merits4 from 1 user
Re: [OS] nvOC Community Release free-easy-to-use Linux Nvidia Mining
I updated after configuring the release upgrade from the keyboard. I then connected from remote via SSH, and repeated the steps outlined above. The update completed without a system hangup, and then rebooted.
On reboot, nvOC did not start the miner. I issued "nvOC start", and received this response:
Unable to init server: Could not connect: Connection refused # Failed to parse arguments: Cannot open display: m1@m1-desktop:~$"
I will go into the miner directory and set up a standalone start script; but I would like to set the system straight so that it can talk to itself. Any suggestions? --scryptr
P.S. -- NOTE: When towards the end of the update, I was given an ASCII (colored text) command prompt asking what to do with the "grub" script. I had several choices. I could keep the original, use the new grub supplied by the package manager, merge the two or three grub scripts, open a window to edit them, and etc.
I chose to keep the original. The SSH session continued and scrolled through all the actions until it ended. No big errors popped up. I rebooted at the final prompt, and the system restarted. --scryptr
P.P.S. -- I went to the keyboard and noticed that the monitor had no display. The monitor reported "no signal". However, via SSH, my miner is running just fine. Further, if I open up the webpage/API display at the miner LAN address, the information is displayed properly. The readout reports that I am running UBUNTU 18.04.
Any clues? --scryptr
Restore xorg with:
Code:
bash /home/m1/NVOC/mining/nvOC restore-xorg
Post
Topic
BoardMining (Altcoins)
Re: [OS] nvOC Community Release free-easy-to-use Linux Nvidia Mining
After a quick web search, I pulled up the following steps:
Steps to upgrade Ubuntu 16.04 to 18.04
1) Login to Ubuntu box. 2) Patch current system by running sudo apt update && sudo apt upgrade. 3) After reboot make sure either UFW firewall is temporarily disabled or TCP port 1022 is open. 4) To upgrade Ubuntu 18.04 LTS from 16.04 LTS run sudo do-release-upgrade.
I'll try this and report my results. --scryptr
Quick answer: upon updating, upgrading, and rebooting, I issued "sudo do-release-upgrade". The message in return was "no upgrade found".
What do you suggest? Is there a setting that I need to change? --scryptr
Updates are usually disabled in nvOC, So you need to open up "Software & Updates" Check mark the updates in "Ubuntu Software" section and also in "Updates" section check mark them all Also in "Updates" section , the last part is "Notify me of a new Ubuntu version" select "For long term support version" When you click close it will reload and should notify of new release
Post
Topic
BoardMining (Altcoins)
Re: [OS] nvOC Community Release free-easy-to-use Linux Nvidia Mining
@PAPAMPI: IS IT POSSIBLE TO UPGRADE FROM 16.04 TO 18.04? HOW? --
I have two rigs runnning on the last (...v3.2) release with Ubuntu 16.04. They are very stable, and I have been able to upgrade the miners that I use and tweak 1bash in minor ways.
I'd like to do a system upgrade to Ubuntu 18.04 without destroying a stable system. How should I proceed?
Many thanks in advance... --scryptr
If I remember correctly some older miners needed libcurl3 which is changed to lubcurl4 in Ubuntu 18.04 Other than that there should be no problem.
Post
Topic
BoardMining (Altcoins)
Re: [OS] nvOC Community Release free-easy-to-use Linux Nvidia Mining
Thanks Already checked those before asking, GitHub only has source code and no specific images and feed only has the latest.
So after an unsuccessful attempt I boot from sd card. Flashing to nand goes ok and it gives the successful message to change jumpers and reboot, but it wont boot, just keeps rebooting.
Tried to restore to factory and gave me this error:
Code:
Could not open mtd device: BOOT.bin-env-dts-kernel Can't open device for writing!
full restore log:
Code:
python3 restore2factory.py --factory-image Antminer-S9j-all-201811071118-autofreq-user-Update2UBI-NF.tar.gz 192.168.1.180 Connecting to remote host... /home/payam/Desktop/braiins/braiins-os_am1-s9_ssh_2019-06-05-0-0de55997/.env/lib/python3.6/site-packages/paramiko/ecdsakey.py:164: CryptographyDeprecationWarning: Support for unsafe construction of public numbers from encoded data will be removed in a future version. Please use EllipticCurvePublicKey.from_encoded_point self.ecdsa_curve.curve_class(), pointinfo Password: Detected bOS mode: sd Creating configuration files... Uploading firmware... Skipping 'c5/soc_system.rbf' Skipping 'c5/upgrade-marker.bin' Skipping 'c5/angstrom_rootfs.jffs2' Skipping 'runme.sh' Skipping 'ubi_info' rootfs.jffs2: |################################| 48889856/48889856 upgrade-marker.bin: |################################| 16/16 devicetree.dtb: |################################| 7631/7631 BOOT.bin: |################################| 2559872/2559872 uImage: |################################| 3799480/3799480 Uploading restore scripts... /tmp/tmpvab5fhbe/config.tar.gz: |################################| 253/253 upgrade/restore.sh: |################################| 1305/1305 Restoring firmware... Could not open mtd device: BOOT.bin-env-dts-kernel Can't open device for writing!
Any helps would be much appreciated.
Post
Topic
BoardMining software (miners)
Re: Braiins OS: open-source mining firmware [S9, T1]. New release includes AsicBoost
by
papampi
on 21/09/2019, 08:32:54 UTC
Where do I find older images for s9?
My miners get hung on rebooting after Upgrade was successful! I never had this issue on older image
Here is the log:
Code:
python3 upgrade2bos.py --no-nand-backup 192.168.1.9 Connecting to remote host... /home/m1/Downloads/braiins/braiins-os_am1-s9_ssh_2019-06-05-0-0de55997/.env/lib/python3.5/site-packages/paramiko/ecdsakey.py:164: CryptographyDeprecationWarning: Support for unsafe construction of public numbers from encoded data will be removed in a future version. Please use EllipticCurvePublicKey.from_encoded_point self.ecdsa_curve.curve_class(), pointinfo /home/m1/Downloads/braiins/braiins-os_am1-s9_ssh_2019-06-05-0-0de55997/.env/lib/python3.5/site-packages/paramiko/client.py:822: UserWarning: Unknown ssh-rsa host key for 192.168.1.9: b'd1b9a53ccf18f8c71135b9d44adf6ad1' key.get_name(), hostname, hexlify(key.get_fingerprint()) Password: Preparing system for backup... Backuping configuration files... Backuping miner NAND... Preparing remote system... Copy ld-musl-armhf.so.1 to /lib/ld-musl-armhf.so.1 Copy sftp-server to /usr/lib/openssh/sftp-server Copy fw_printenv to /usr/sbin/fw_printenv
Uploading firmware... firmware/stage2.tgz: |################################| 17495127/17495127 firmware/u-boot.img: |################################| 573700/573700 firmware/uboot_env.bin: |################################| 131072/131072 firmware/boot.bin: |################################| 79647/79647 firmware/stage1.sh: |################################| 4069/4069 firmware/fit.itb: |################################| 7036220/7036220 firmware/system.bit.gz: |################################| 477812/477812 firmware/uboot_env.config: |################################| 382/382 firmware/CONTROL: |################################| 3081/3081 Upgrading firmware... total 25212 -rw-r--r-- 1 root root 3081 Sep 21 07:51 CONTROL -rw-r--r-- 1 root root 79647 Sep 21 07:51 boot.bin -rw-r--r-- 1 root root 7036220 Sep 21 07:51 fit.itb -rw-r--r-- 1 root root 4069 Sep 21 07:51 stage1.sh -rw-r--r-- 1 root root 17495127 Sep 21 07:51 stage2.tgz -rw-r--r-- 1 root root 477812 Sep 21 07:51 system.bit.gz -rw-r--r-- 1 root root 573700 Sep 21 07:51 u-boot.img -rw-r--r-- 1 root root 131072 Sep 21 07:51 uboot_env.bin -rw-r--r-- 1 root root 382 Sep 21 07:51 uboot_env.config Erasing 128 Kibyte @ 1fe0000 -- 100 % complete Writing U-Boot images with FPGA bitstream... Writing data to block 0 at offset 0x0 Writing data to block 4 at offset 0x80000 Writing data to block 5 at offset 0xa0000 Writing data to block 6 at offset 0xc0000 Writing data to block 7 at offset 0xe0000 Writing data to block 8 at offset 0x100000 Writing data to block 24 at offset 0x300000 Writing data to block 25 at offset 0x320000 Writing data to block 26 at offset 0x340000 Writing data to block 27 at offset 0x360000 Writing U-Boot environment... Writing data to block 56 at offset 0x700000 Writing data to block 57 at offset 0x720000 Erasing 128 Kibyte @ 2ec0000 -- 58 % complete flash_erase: Skipping bad block at 02ee0000 Erasing 128 Kibyte @ 3aa0000 -- 73 % complete flash_erase: Skipping bad block at 03ac0000 Erasing 128 Kibyte @ 4f40000 -- 99 % complete flash_erase: Skipping bad block at 04f60000 flash_erase: Skipping bad block at 04f80000 flash_erase: Skipping bad block at 04fa0000 flash_erase: Skipping bad block at 04fc0000 flash_erase: Skipping bad block at 04fe0000 Erasing 128 Kibyte @ 4fe0000 -- 100 % complete Writing kernel image... Writing data to block 0 at offset 0x0 Writing data to block 1 at offset 0x20000 Writing data to block 2 at offset 0x40000 Writing data to block 3 at offset 0x60000 Writing data to block 4 at offset 0x80000 Writing data to block 5 at offset 0xa0000 Writing data to block 6 at offset 0xc0000 Writing data to block 7 at offset 0xe0000 Writing data to block 8 at offset 0x100000 Writing data to block 9 at offset 0x120000 Writing data to block 10 at offset 0x140000 Writing data to block 11 at offset 0x160000 Writing data to block 12 at offset 0x180000 Writing data to block 13 at offset 0x1a0000 Writing data to block 14 at offset 0x1c0000 Writing data to block 15 at offset 0x1e0000 Writing data to block 16 at offset 0x200000 Writing data to block 17 at offset 0x220000 Writing data to block 18 at offset 0x240000 Writing data to block 19 at offset 0x260000 Writing data to block 20 at offset 0x280000 Writing data to block 21 at offset 0x2a0000 Writing data to block 22 at offset 0x2c0000 Writing data to block 23 at offset 0x2e0000 Writing data to block 24 at offset 0x300000 Writing data to block 25 at offset 0x320000 Writing data to block 26 at offset 0x340000 Writing data to block 27 at offset 0x360000 Writing data to block 28 at offset 0x380000 Writing data to block 29 at offset 0x3a0000 Writing data to block 30 at offset 0x3c0000 Writing data to block 31 at offset 0x3e0000 Writing data to block 32 at offset 0x400000 Writing data to block 33 at offset 0x420000 Writing data to block 34 at offset 0x440000 Writing data to block 35 at offset 0x460000 Writing data to block 36 at offset 0x480000 Writing data to block 37 at offset 0x4a0000 Writing data to block 38 at offset 0x4c0000 Writing data to block 39 at offset 0x4e0000 Writing data to block 40 at offset 0x500000 Writing data to block 41 at offset 0x520000 Writing data to block 42 at offset 0x540000 Writing data to block 43 at offset 0x560000 Writing data to block 44 at offset 0x580000 Writing data to block 45 at offset 0x5a0000 Writing data to block 46 at offset 0x5c0000 Writing data to block 47 at offset 0x5e0000 Writing data to block 48 at offset 0x600000 Writing data to block 49 at offset 0x620000 Writing data to block 50 at offset 0x640000 Writing data to block 51 at offset 0x660000 Writing data to block 52 at offset 0x680000 Writing data to block 53 at offset 0x6a0000 Writing stage2 tarball... Writing data to block 80 at offset 0xa00000 Writing data to block 81 at offset 0xa20000 Writing data to block 82 at offset 0xa40000 Writing data to block 83 at offset 0xa60000 Writing data to block 84 at offset 0xa80000 Writing data to block 85 at offset 0xaa0000 Writing data to block 86 at offset 0xac0000 Writing data to block 87 at offset 0xae0000 Writing data to block 88 at offset 0xb00000 Writing data to block 89 at offset 0xb20000 Writing data to block 90 at offset 0xb40000 Writing data to block 91 at offset 0xb60000 Writing data to block 92 at offset 0xb80000 Writing data to block 93 at offset 0xba0000 Writing data to block 94 at offset 0xbc0000 Writing data to block 95 at offset 0xbe0000 Writing data to block 96 at offset 0xc00000 Writing data to block 97 at offset 0xc20000 Writing data to block 98 at offset 0xc40000 Writing data to block 99 at offset 0xc60000 Writing data to block 100 at offset 0xc80000 Writing data to block 101 at offset 0xca0000 Writing data to block 102 at offset 0xcc0000 Writing data to block 103 at offset 0xce0000 Writing data to block 104 at offset 0xd00000 Writing data to block 105 at offset 0xd20000 Writing data to block 106 at offset 0xd40000 Writing data to block 107 at offset 0xd60000 Writing data to block 108 at offset 0xd80000 Writing data to block 109 at offset 0xda0000 Writing data to block 110 at offset 0xdc0000 Writing data to block 111 at offset 0xde0000 Writing data to block 112 at offset 0xe00000 Writing data to block 113 at offset 0xe20000 Writing data to block 114 at offset 0xe40000 Writing data to block 115 at offset 0xe60000 Writing data to block 116 at offset 0xe80000 Writing data to block 117 at offset 0xea0000 Writing data to block 118 at offset 0xec0000 Writing data to block 119 at offset 0xee0000 Writing data to block 120 at offset 0xf00000 Writing data to block 121 at offset 0xf20000 Writing data to block 122 at offset 0xf40000 Writing data to block 123 at offset 0xf60000 Writing data to block 124 at offset 0xf80000 Writing data to block 125 at offset 0xfa0000 Writing data to block 126 at offset 0xfc0000 Writing data to block 127 at offset 0xfe0000 Writing data to block 128 at offset 0x1000000 Writing data to block 129 at offset 0x1020000 Writing data to block 130 at offset 0x1040000 Writing data to block 131 at offset 0x1060000 Writing data to block 132 at offset 0x1080000 Writing data to block 133 at offset 0x10a0000 Writing data to block 134 at offset 0x10c0000 Writing data to block 135 at offset 0x10e0000 Writing data to block 136 at offset 0x1100000 Writing data to block 137 at offset 0x1120000 Writing data to block 138 at offset 0x1140000 Writing data to block 139 at offset 0x1160000 Writing data to block 140 at offset 0x1180000 Writing data to block 141 at offset 0x11a0000 Writing data to block 142 at offset 0x11c0000 Writing data to block 143 at offset 0x11e0000 Writing data to block 144 at offset 0x1200000 Writing data to block 145 at offset 0x1220000 Writing data to block 146 at offset 0x1240000 Writing data to block 147 at offset 0x1260000 Writing data to block 148 at offset 0x1280000 Writing data to block 149 at offset 0x12a0000 Writing data to block 150 at offset 0x12c0000 Writing data to block 151 at offset 0x12e0000 Writing data to block 152 at offset 0x1300000 Writing data to block 153 at offset 0x1320000 Writing data to block 154 at offset 0x1340000 Writing data to block 155 at offset 0x1360000 Writing data to block 156 at offset 0x1380000 Writing data to block 157 at offset 0x13a0000 Writing data to block 158 at offset 0x13c0000 Writing data to block 159 at offset 0x13e0000 Writing data to block 160 at offset 0x1400000 Writing data to block 161 at offset 0x1420000 Writing data to block 162 at offset 0x1440000 Writing data to block 163 at offset 0x1460000 Writing data to block 164 at offset 0x1480000 Writing data to block 165 at offset 0x14a0000 Writing data to block 166 at offset 0x14c0000 Writing data to block 167 at offset 0x14e0000 Writing data to block 168 at offset 0x1500000 Writing data to block 169 at offset 0x1520000 Writing data to block 170 at offset 0x1540000 Writing data to block 171 at offset 0x1560000 Writing data to block 172 at offset 0x1580000 Writing data to block 173 at offset 0x15a0000 Writing data to block 174 at offset 0x15c0000 Writing data to block 175 at offset 0x15e0000 Writing data to block 176 at offset 0x1600000 Writing data to block 177 at offset 0x1620000 Writing data to block 178 at offset 0x1640000 Writing data to block 179 at offset 0x1660000 Writing data to block 180 at offset 0x1680000 Writing data to block 181 at offset 0x16a0000 Writing data to block 182 at offset 0x16c0000 Writing data to block 183 at offset 0x16e0000 Writing data to block 184 at offset 0x1700000 Writing data to block 185 at offset 0x1720000 Writing data to block 186 at offset 0x1740000 Writing data to block 187 at offset 0x1760000 Writing data to block 188 at offset 0x1780000 Writing data to block 189 at offset 0x17a0000 Writing data to block 190 at offset 0x17c0000 Writing data to block 191 at offset 0x17e0000 Writing data to block 192 at offset 0x1800000 Writing data to block 193 at offset 0x1820000 Writing data to block 194 at offset 0x1840000 Writing data to block 195 at offset 0x1860000 Writing data to block 196 at offset 0x1880000 Writing data to block 197 at offset 0x18a0000 Writing data to block 198 at offset 0x18c0000 Writing data to block 199 at offset 0x18e0000 Writing data to block 200 at offset 0x1900000 Writing data to block 201 at offset 0x1920000 Writing data to block 202 at offset 0x1940000 Writing data to block 203 at offset 0x1960000 Writing data to block 204 at offset 0x1980000 Writing data to block 205 at offset 0x19a0000 Writing data to block 206 at offset 0x19c0000 Writing data to block 207 at offset 0x19e0000 Writing data to block 208 at offset 0x1a00000 Writing data to block 209 at offset 0x1a20000 Writing data to block 210 at offset 0x1a40000 Writing data to block 211 at offset 0x1a60000 Writing data to block 212 at offset 0x1a80000 Writing data to block 213 at offset 0x1aa0000 U-Boot configuration...
Content of U-Boot configuration: miner_pool_host=stratum+tcp://stratum.slushpool.com miner_pool_port=3333 miner_pool_user=!non-existent-user! load_addr=0x2000000 fdt_high=0x7FFFFFF initrd_high=0x7FFFFFF bitstream_addr=0x2100000 bootenv=uEnv.txt set_bootargs=setenv bootargs console=ttyPS0,115200 root=/dev/ram0 r rootfstype=squashfs ${mtdparts} earlyprintk uenv_load=load mmc 0 ${load_addr} ${bootenv} && echo Loaded environment from ${bootenv} && env import -t ${load_addr} ${filesize} load_fpga=nand read ${load_addr} ${bitstream_off} ${bitstream_size} && unzip ${load_addr} ${bitstream_addr} && fpga loadb 0 ${bitstream_addr} ${bitstream_size} nandboot=echo Copying FIT from NAND flash to RAM... && run uenv_load; test x${sd_boot} = xyes && run sdboot; run set_bootargs && run load_fpga && nand read ${load_addr} ${kernel_off} ${kernel_size} && bootm ${load_addr} sdboot=echo Copying FIT from SD to RAM... && run set_bootargs && run uenv_load; load mmc 0 ${load_addr} fit.itb && bootm ${load_addr} mtdids=nand0=pl35x-nand mtdparts=mtdparts=pl35x-nand:512k(boot),2560k(uboot),2m(fpga1),2m(fpga2),512k(uboot_env),512k(miner_cfg),22m(recovery),95m(firmware1),95m(firmware2) bootcmd=run $modeboot bitstream_off=0x300000 bitstream_size=0x74a74 kernel_off=0xB000000 kernel_size=0x6b5d3c stage2_off=0x3D00000 stage2_size=0x10af457 stage2_mtd=8 ethaddr=08:7d:20:56:db:72 miner_hwid=e6CrehyC3cSvWqql miner_freq=550 miner_voltage=0706 Upgrade was successful! Rebooting...
Post
Topic
BoardMining software (miners)
Merits2 from 1 user
Re: Braiins OS: open-source mining firmware [S9, T1]. New release includes AsicBoost
i added (( "bitmain-no-sensor-scan" : true , )) to cgminer.conf but temp sensor still has error . i want the system to ignore temperature error of specific Chain . please help
this is error log : 2019-08-28 09:03:44 temperature.c:188:is_temp_sensor_type_correct: Wrong temp sensor type, chain = 0, sensor = 39, type = 0x0, retry. 2019-08-28 09:03:44 temperature.c:188:is_temp_sensor_type_correct: Wrong temp sensor type, chain = 0, sensor = 39, type = 0x0, retry. 2019-08-28 09:03:44 driver-btm-api.c:189:set_miner_status: ERROR_TEMP_LOST_1ST 2019-08-28 09:03:44 driver-btm-api.c:143:stop_mining_and_reboot: stop mining: Re-run cgminer to check temerature sensor type again!
if it's the last config no "," after it And it should be --no-sensor-scan not what you used as below
Code:
"--no-sensor-scan":true
Post
Topic
BoardMining (Altcoins)
Re: [OS] nvOC Community Release free-easy-to-use Linux Nvidia Mining
I just upgraded my 8 rigs to the latest version. Prior to this they have been running on 19-2.0 from December 2017. I am gone a lot and very busy now and don't have a lot of time to mess with them so they have just been running Nicehash ET hash rather than me trying to chase the most profitable coins, deal with multiple wallets, etc. The pay in BTC is so convienent.
I decided to clean off all the rigs today and while at why not upgrade. It took me a while to get going as I was using the wrong 1bash.template. I downloaded the entire 7zip image but the 1.bash.template contained in it was not the newest and I had to get the latest from GitHub. Got that working.
I am still having an issue with the miners. the only one I can get to work with nice-ethash is claymore. I don't know if this is good or bad. On the old version I was using ethminer and it doesn't have a fee I think and Claymore does. Anything but claymore gives me "could not subscribe" errors.
What miner should I be using for best performance and how do I make it work if it isn't claymore?
Thanks.
Latest ethminer has made some changes.
have a look at their wiki and if you have problem with worker name check 1bash extended info for eth wallet address format:
Code:
ETHASH_WALLET_FORMAT="$WALLET_ADDRESS_FORMAT" # Some pools require to use "%2e" instead of "." More examples available :https://github.com/ethereum-mining/ethminer/blob/master/docs/POOL_EXAMPLES_ETH.md
Post
Topic
BoardMining software (miners)
Re: Braiins OS: open-source mining firmware [S9, T1]. New release includes AsicBoost
by
papampi
on 05/07/2019, 17:13:51 UTC
Some times web page need more than one time refresh.
Post
Topic
BoardMining software (miners)
Re: Braiins OS: open-source mining firmware [S9, T1]. New release includes AsicBoost
thanks for your reply, I will try to connect device directly to pc and Ill inform you about result
[...]
and yes I did it using sd card and permanently install bOS to NAND (both from web interface and ssh) and both of them completely successful in logs message! but when I changed the jumper to nand the device can not give IP address. totally it seems couldnt boot from nand.