 Show Posts
|
|
Pages: [1] 2 »
|
We're pleased to release Bminer 16.1.0.
* Support for BFC and Cuckatoo32.
Thank you for the Cuckatoo32 support! I've been using Bminer for Cuckatoo31 for a long time. That said, Cuckatoo32 mining is not very stable. I'm running Ubuntu with Nvidia 1080ti cards. It runs good for about 5 minutes, then it has GPU issues, where it can't communicate with one ore more of the GPUs. I'm using the exact same config as Cuckatoo31. I've tried reducing OC, but that doesn't seem to make a difference. Here is what the log shows: [INFO] [2020-04-12T12:59:30-07:00] [GPU 0] Speed: 0.06 G/s Fidelity 0.981 Temp: 1C Fan: 1% Power: 1W 0.06 G/J
[ERRO] [2020-04-12T12:59:30-07:00] Failed to fetch device Status for device id: 0, Error code: 15
[INFO] [2020-04-12T12:59:30-07:00] [GPU 1] Speed: 0.06 G/s Fidelity 1.162 Temp: 1C Fan: 1% Power: 1W 0.06 G/J
[ERRO] [2020-04-12T12:59:30-07:00] Failed to fetch device Status for device id: 1, Error code: 15
[INFO] [2020-04-12T12:59:30-07:00] [GPU 2] Speed: 0.65 G/s Fidelity 1.124 Temp: 78C Fan: 50% Power: 204W 0.00 G/J
[INFO] [2020-04-12T12:59:30-07:00] [GPU 3] Speed: 0.06 G/s Fidelity 0.760 Temp: 1C Fan: 1% Power: 1W 0.06 G/J
[ERRO] [2020-04-12T12:59:30-07:00] Failed to fetch device Status for device id: 3, Error code: 15
[INFO] [2020-04-12T12:59:31-07:00] [GPU 4] Speed: 0.66 G/s Fidelity 0.804 Temp: 79C Fan: 50% Power: 196W 0.00 G/J
[INFO] [2020-04-12T12:59:31-07:00] [GPU 5] Speed: 0.06 G/s Fidelity 1.243 Temp: 1C Fan: 1% Power: 1W 0.06 G/J
[ERRO] [2020-04-12T12:59:31-07:00] Failed to fetch device Status for device id: 5, Error code: 15
[INFO] [2020-04-12T12:59:31-07:00] [GPU 6] Speed: 0.06 G/s Fidelity 1.210 Temp: 1C Fan: 1% Power: 1W 0.06 G/J
[ERRO] [2020-04-12T12:59:31-07:00] Failed to fetch device Status for device id: 6, Error code: 15
[INFO] [2020-04-12T12:59:31-07:00] [GPU 7] Speed: 0.06 G/s Fidelity 1.129 Temp: 1C Fan: 1% Power: 1W 0.06 G/J
[ERRO] [2020-04-12T12:59:31-07:00] Failed to fetch device Status for device id: 7, Error code: 15
[INFO] [2020-04-12T12:59:32-07:00] Accepted share
[INFO] [2020-04-12T12:59:32-07:00] Total 1.68 G/s Accepted shares 191 Rejected shares 0
[INFO] [2020-04-12T12:59:35-07:00] Accepted share
[FATA] [2020-04-12T12:59:56-07:00] Irrecoverable errors: [D5] GPU hang detected
Mining Cuckatoo32 using gminer is more stable, but the hashrate is 20% lower and CPU usage is much higher. |
|
|
|
At least for the summer.
I run a small farm of ASIC A9 Zmasters and they were heating my shop and giving me a decent profit over the winter but even at $0.06 a KW it will cost me too much to run them through the hot weather. So I'm drinking Bushmill's, smoking a Cuban cigar, and crying a little.
Want to sell them? |
|
|
|
Please give a spin on 15.0.0.
Same problem on 15.0.0. Plus the miner dies every 30-90 minutes. Latest version of HiveOS. [INFO] [2019-02-17T18:39:58-08:00] Total 10.83 G/s Accepted shares 1690 Rejected shares 79
[INFO] [2019-02-17T18:39:58-08:00] Accepted share
[INFO] [2019-02-17T18:39:59-08:00] Accepted share
[INFO] [2019-02-17T18:40:00-08:00] Received new job 1823285012380
[WARN] [2019-02-17T18:40:03-08:00] Miner died! It will be restarted soon...
[INFO] [2019-02-17T18:40:13-08:00] Bminer: When Crypto-mining Made Fast (v15.0.0-e143cb4)
[INFO] [2019-02-17T18:40:14-08:00] Watchdog has started.
[INFO] [2019-02-17T18:40:14-08:00] Starting miner on 8 devices
[INFO] [2019-02-17T18:40:14-08:00] Free memory 10996.1 MB available on device (#0). Selecting 11GB solver.
[INFO] [2019-02-17T18:40:14-08:00] Starting the management API at 127.0.0.1:1880
[INFO] [2019-02-17T18:40:14-08:00] Starting miner on device 0...
[INFO] [2019-02-17T18:40:14-08:00] Connected to grincuckatoo31.usa.nicehash.com:3372
[INFO] [2019-02-17T18:40:14-08:00] Authorized with the server
[INFO] [2019-02-17T18:40:14-08:00] Received new job 1823285012477
[INFO] [2019-02-17T18:40:14-08:00] Started miner on device 0
[INFO] [2019-02-17T18:40:14-08:00] Free memory 11012.5 MB available on device (#1). Selecting 11GB solver.
[INFO] [2019-02-17T18:40:14-08:00] Starting miner on device 1...
[INFO] [2019-02-17T18:40:14-08:00] Started miner on device 1
[INFO] [2019-02-17T18:40:14-08:00] Free memory 11012.5 MB available on device (#2). Selecting 11GB solver.
[INFO] [2019-02-17T18:40:14-08:00] Starting miner on device 2...
[INFO] [2019-02-17T18:40:14-08:00] Started miner on device 2
[INFO] [2019-02-17T18:40:14-08:00] Free memory 11012.5 MB available on device (#3). Selecting 11GB solver.
[INFO] [2019-02-17T18:40:14-08:00] Starting miner on device 3...
[INFO] [2019-02-17T18:40:15-08:00] Started miner on device 3
[INFO] [2019-02-17T18:40:15-08:00] Free memory 11012.5 MB available on device (#4). Selecting 11GB solver.
[INFO] [2019-02-17T18:40:15-08:00] Starting miner on device 4...
[INFO] [2019-02-17T18:40:15-08:00] Started miner on device 4
[INFO] [2019-02-17T18:40:15-08:00] Free memory 11012.5 MB available on device (#5). Selecting 11GB solver.
[INFO] [2019-02-17T18:40:15-08:00] Starting miner on device 5...
[INFO] [2019-02-17T18:40:15-08:00] Started miner on device 5
[INFO] [2019-02-17T18:40:15-08:00] Free memory 11012.5 MB available on device (#6). Selecting 11GB solver.
[INFO] [2019-02-17T18:40:15-08:00] Starting miner on device 6...
[INFO] [2019-02-17T18:40:15-08:00] Started miner on device 6
[INFO] [2019-02-17T18:40:15-08:00] Free memory 11012.5 MB available on device (#7). Selecting 11GB solver.
[INFO] [2019-02-17T18:40:15-08:00] Starting miner on device 7...
[INFO] [2019-02-17T18:40:16-08:00] Started miner on device 7
[INFO] [2019-02-17T18:40:19-08:00] Accepted share
[INFO] [2019-02-17T18:40:19-08:00] Accepted share
[INFO] [2019-02-17T18:40:27-08:00] Received new job 1823285012598
[INFO] [2019-02-17T18:40:37-08:00] Accepted share
[INFO] [2019-02-17T18:40:43-08:00] Accepted share
[INFO] [2019-02-17T18:40:43-08:00] Accepted share
[INFO] [2019-02-17T18:40:44-08:00] [GPU 0] Speed: 1.37 G/s Fidelity 0.000 Temp: 64C Fan: 51% Power: 80W 0.02 G/J
[INFO] [2019-02-17T18:40:44-08:00] [GPU 1] Speed: 1.18 G/s Fidelity 1.400 Temp: 62C Fan: 54% Power: 72W 0.02 G/J
[INFO] [2019-02-17T18:40:44-08:00] [GPU 2] Speed: 1.37 G/s Fidelity 0.000 Temp: 61C Fan: 51% Power: 66W 0.02 G/J
[INFO] [2019-02-17T18:40:45-08:00] [GPU 3] Speed: 1.18 G/s Fidelity 1.312 Temp: 62C Fan: 50% Power: 78W 0.02 G/J
[INFO] [2019-02-17T18:40:45-08:00] [GPU 4] Speed: 1.18 G/s Fidelity 2.471 Temp: 61C Fan: 57% Power: 63W 0.02 G/J
[INFO] [2019-02-17T18:40:45-08:00] [GPU 5] Speed: 1.18 G/s Fidelity 0.000 Temp: 61C Fan: 50% Power: 74W 0.02 G/J
[INFO] [2019-02-17T18:40:45-08:00] [GPU 6] Speed: 1.37 G/s Fidelity 0.000 Temp: 61C Fan: 53% Power: 69W 0.02 G/J
[INFO] [2019-02-17T18:40:46-08:00] [GPU 7] Speed: 1.37 G/s Fidelity 1.077 Temp: 60C Fan: 50% Power: 83W 0.02 G/J
[INFO] [2019-02-17T18:40:46-08:00] Total 10.19 G/s Accepted shares 5 Rejected shares 0
[INFO] [2019-02-17T18:40:48-08:00] Accepted share
[INFO] [2019-02-17T18:40:52-08:00] Accepted share
[INFO] [2019-02-17T18:40:57-08:00] Accepted share
[INFO] [2019-02-17T18:40:58-08:00] Accepted share
[INFO] [2019-02-17T18:40:58-08:00] Accepted share
[INFO] [2019-02-17T18:41:03-08:00] Received new job 1823285012776
[INFO] [2019-02-17T18:41:03-08:00] Accepted share
[WARN] [2019-02-17T18:41:04-08:00] Rejected share #0 ({"code":-1,"message":"Share above target."})
[INFO] [2019-02-17T18:41:11-08:00] Accepted share
...
[WARN] [2019-02-17T18:42:34-08:00] Rejected share #0 ({"code":-1,"message":"Share above target."})
...
[WARN] [2019-02-17T18:50:38-08:00] Rejected share #0 ({"code":-5,"message":"Invalid nonce; is miner not compatible with NiceHash?"})
[WARN] [2019-02-17T18:50:39-08:00] Rejected share #0 ({"code":-5,"message":"Invalid nonce; is miner not compatible with NiceHash?"})
|
|
|
|
Guys, what is your hashrate on c31 using 1080ti on Windows?
I have about 0.75-0.87 per card (but 7.12 on c29)
Win7, 1080ti Asus Strix, 416.94 drivers
949mv locked,
power limit 100% (working at about 80% average),
core +220 (working at about 1923 mhz)
memory +400 at P0 (working at 5899 mhz) + Pill
Not on Windows, but on HiveOS - 1.29-1.43. Pool side shows about the same but with 5-6% rejects. 210w power limit +100/+1000 and running the OhGodAnETHlargementPill. However, bminer crashes and restarts every 1-3 hours. It's still much faster than gminer. |
|
|
|
Does anybody had a memory leakage/full problem with A9? When "Used memory" is about 99% mine stops working/responding. I have reboot it manually. And it happens every 24-25 hours  Firmware is uptodate. Known problem. Use a miner control program, like HiveOS, or set up a cron job to have it automatically reboot every 24 hours. |
|
|
|
Hi,
Would like to report a crash/restart due to memory leak/ out of memory. This happens maybe once every few days so far, so its not too important, but may end up reducing my share for a certain block if it cuts out at a bad time.
What firmware version are you running? |
|
|
|
You are not doing anything wrong. You can ignore the error. if you want to confirm the changes were made to the cgminer.conf file, type: cat cgminer.conf If you are going to go poking around as root in your miner, I suggest you learn some basic unix/linux commands. If you are not careful, you can really mess up the operating system on your miner. |
|
|
|
thanks for quick reply. I have this issue then trying to enter to config file. What I should do with this swap file? https://imgur.com/wqAi9ZSThanks in advance. You can ignore this error. After you edit the cgminer.conf file, you need to type: systemctl restart cgminer That will restart the miner program and it should use the new cgminer.conf settings. |
|
|
|
|
Anyone have any updates on possible PSU fixes?
|
|
|
|
How are you guys editing the file? On Linux I usually use nano but I'm sure that doesn't exist on the A9. I'd like to just change the fan speeds, sick of these high temps.
Thanks!
vi |
|
|
|
any numbers in increased hashrate you can provide? suprnova seems to vary widely with zencash for me in terms of hash rate reporting...
I'm not seeing a significant increase in hash rate. I'm mining ZEC on flypool so I'll watch that for a while to get a better idea if there is an increase. |
|
|
|
I'd be careful adjusting voltages if it's anything similar to overclocking gpus. Perhaps just start with clockspeeds.
Attempting to set PLL to 1350 w/o setting voltages seems to make miner go back to default settings 1400/175 seems to be working ok so far. |
|
|
|
So I tried the following config: "api-listen": true,
"api-port": "4028",
"api-allow": "R:0/0,W:127.0.0.1",
"noauto": true,
"T1Pll": 1300,
"T2Pll": 1300,
"T3Pll": 1300 and the miner log still showed it didnt go past 1250 PLL: Jul 22 18:25:56 InnoMiner mcompat_lib[1316]: chain 2 set PLL Lv.355 success Jul 22 18:25:57 InnoMiner mcompat_lib[1316]: chain 0 pll 1250 finished Jul 22 18:25:57 InnoMiner mcompat_lib[1316]: chain 1 pll 1250 finished Jul 22 18:25:57 InnoMiner mcompat_lib[1316]: chain 2 pll 1250 finished Jul 22 18:25:57 InnoMiner mcompat_lib[1316]: #####Write t/v sensor Value Success! Jul 22 18:25:57 InnoMiner mcompat_lib[1316]: #####Write t/v sensor Value Success! Try this: "noauto": true,
"T1Pll1": "1300",
"T1Pll2": "1300",
"T1Pll3": "1300",
"T1VID1": "170",
"T1VID2": "170",
"T1VID3": "170",
"A1Fanspd": "50",
"A1Fanmode": "0"
Fan is running at a constant 50% and the PLL seems to be at 1300. Jul 22 18:52:27 InnoMiner mcompat_lib[1419]: WARNING: unable to read temperature, force fan speed to 100 Jul 22 18:52:27 InnoMiner mcompat_lib[1419]: fan speed set to 100, TARGET is 50 Jul 22 18:52:39 InnoMiner mcompat_lib[1419]: fan speed set to 50, TARGET is 50 Jul 22 18:53:38 InnoMiner mcompat_lib[1419]: chain 0 pll 1300 finished Jul 22 18:53:38 InnoMiner mcompat_lib[1419]: chain 1 pll 1300 finished Jul 22 18:53:38 InnoMiner mcompat_lib[1419]: chain 2 pll 1300 finished |
|
|
|
Thanks, did not know that. The 7/18 file name is: b29+_20180718_055037.swu However, 7/18 firmware caused me the following issues: very slow to reach peak hash rate (~30 min), and caused many HW errors. 7/20 (7/06?) firmware resolved both of these issues for me. Are you getting the full 50k hashrate? I had the same issues with the 7/18 firmware. I'm getting ~50k on 2 A9 and only ~40k one 1. I've tried everything I can think of to get the hash rate up on the slow one, but nothing seems to make a difference. |
|
|
|
Weird, I just checked and I'm also having the same problem. My previous installed firmware was from 07/18. But after installing today's 07/20 firmware, it is now saying I have 07/06 firmware installed... I'm guessing they will push out a new firmware to fix this soon.
I'm seeing the same thing. Installed the 7/20 firmware, but the system overview shows it as the 7/6 firmware. |
|
|
|
What's the command line you're using.
I'm doing ./hashcat64.bin -1 abcdefghijklmnopqrstuvwxyz0123456789 -d 1 -a 3 -m 1800 example.hash ?1?1?1?1?1
..oh looks like it's working now..
hashcat -m 1800 -a 3 --increment -O --session 8char --outfile ~/hashcat.txt ~/hash.txt ?a?a?a?a?a?a?a?a |
|
|
|
The SWU file is several files in one, each with a section and hash of the data of that file. If you search for "$6$", you'll find that contents of the shadow file which has that root:$6$... structure. The $6$ indicates it's a SHA512. The salt is the characters in between the second and third "$" signs. The hashed portion of the password is after the third "$" sign. Note that these are put into a different format due to linux's "crypt" routine. Read here: http://manpages.ubuntu.com/manpages/trusty/man3/crypt.3.htmlThis is why brute-force cracking this is not reasonable (in my mind). I think it's more probable that the SWU image gets updated to a known hashed password. I'm going to throw 8 1080Ti at it for a while trying to brute force crack it. Well, it's not a 1-5 character password. Checking 6 characters is going to take a week... Can you try all 8 character passwords with inno as the first 4 chars? Are you using hashcat? I'd throw a rig at it but I'm not sure how to proceed witih the salt part. Yes, hashcat. I just tried with inno as the first 4 characters with a maximum length of 8 characters and I didn't get any results. |
|
|
|
The SWU file is several files in one, each with a section and hash of the data of that file. If you search for "$6$", you'll find that contents of the shadow file which has that root:$6$... structure. The $6$ indicates it's a SHA512. The salt is the characters in between the second and third "$" signs. The hashed portion of the password is after the third "$" sign. Note that these are put into a different format due to linux's "crypt" routine. Read here: http://manpages.ubuntu.com/manpages/trusty/man3/crypt.3.htmlThis is why brute-force cracking this is not reasonable (in my mind). I think it's more probable that the SWU image gets updated to a known hashed password. I'm going to throw 8 1080Ti at it for a while trying to brute force crack it. Well, it's not a 1-5 character password. Checking 6 characters is going to take a week... |
|
|
|
they provided no explanation...pretty much just said no, sorry, wont give it to you, neener neener neener.
ive started looking at brute forcing the ssh password knowing that some keywords will probably be "inno" "t1t2t3" "a9" based on previous innosilicon passwords but probably wont have much luck....
Is it possible to mount the firmware on a linux box or something, so could try and brute force it a little more firmly  Yes, it's possible! Here is the /etc/shadow entry from the firmware file if anyone wants to take a go at it: root:$6$AFqSg1Lk$PcjGWzIPX1ghz7GqGzXoFq0WsYTAwz5VsbG/DiKBQmxYno4igKlPLhqwTkdenTevxS9K9bFqzUMGiB1KdIX3G.:10933:0:99999:7::: Please share any results here! I'm trying to figure out the ssh password to my Inno D9 and it looks like you guys are going down the same paths as I have (without success). I don't think it's reasonable to brute force this. I tried it with hashcat for about a week and didn't find anything. My latest theory is to modify the SWU file as it contains the rootfs.ubi file. Change the hashed password in the binary that's in the shadow file to a known hash value (with the particular salt), then update the hash of the rootfs.ubi section. Unfortunately, I'm stuck at being able to reproduce the hash of the original .ubi file section. Then, flash the modified SWU file. However, I'm really trying not to brick my miner. I just haven't dealt with SWU files before so I'm a little cautious here. I'm interested in learning a bit more about this. How did you get the /etc/passwd? I've extracted the .swu but just see BOOT.bin and rootfs.ubi etc. Do we know which hashing algorithm that password is? MD5 or SHA512 Which part of the root:$6$AFqSg1Lk$PcjGWzIPX1ghz7GqGzXoFq0WsYTAwz5VsbG/DiKBQmxYno4igKlPLhqwTkdenTevxS9K9bFqzUMGiB1KdIX3G.:10933:0:99999:7::: are we trying to force? I guess if there's a salt as well there's little chance of figuring it out. The SWU file is several files in one, each with a section and hash of the data of that file. If you search for "$6$", you'll find that contents of the shadow file which has that root:$6$... structure. The $6$ indicates it's a SHA512. The salt is the characters in between the second and third "$" signs. The hashed portion of the password is after the third "$" sign. Note that these are put into a different format due to linux's "crypt" routine. Read here: http://manpages.ubuntu.com/manpages/trusty/man3/crypt.3.htmlThis is why brute-force cracking this is not reasonable (in my mind). I think it's more probable that the SWU image gets updated to a known hashed password. I'm going to throw 8 1080Ti at it for a while trying to brute force crack it. |
|
|
|
I tried it earlier today for about 6 hours. No obvious improvements and in fact, the hash rate was very slow to ramp up - taking over an hour to plateau. I went back to the 7/6 firmware. |
|
|
|
|
