 Show Posts
|
|
Pages: [1] 2 3 4 5 »
|
|
Braiins OS+ 21.09 S17Pro. Why can't i change anything in Configuration -> Performance menu? Everything is grayed out...
|
|
|
|
|
Ska man ange wallet adressen till skatteverket? Eller kommer dom kolla upp den?
|
|
|
|
|
Is there a known workaround for NVIDIA GeForce RTX 3060 Ti LHR?
Does the beta 470.05 driver work?
|
|
|
|
|
So whats this voting on the Draft Rehabilitation Plan mean? Do i have to read 205 pages and try to understand something?
Anybody who can explain it to me in general?
|
|
|
|
|
Ni som har deklarerat för trading och mining. Ska man ange wallet adressen till skatteverket?
|
|
|
|
Hi Got this message on NBMiner 35.0 couple of days ago: [09:38:04] INFO - Device 0 started, Free mem = 4096MB.
[09:38:04] ERROR - Error load opencl module: clBuildProgram
[09:38:04] WARN - QMutex: destroying locked mutex Any ideas what i could try to fix it? |
|
|
|
Depends on what unit we are talking about. J1, J2 and J3 were used on old S9 model as far as I know. I didn't see them on any of S/T 17 miners.
Can you provide more info about your unit and your problem?
S17 Pro. It's very hard to see on S17 control board. You can see J1, then you have to look with a flashlight between the tight cable connection to see J2 and J3. Chain 0 dropped out. Tried all the tricks on this thread to get it working. So decided to open it up and take a look on my heatsinks. Usually, the label on the control board will be represented in the kernel log, in case that is not the case, then the ordering is ascending, so your chain 0 will be J1, the labels are quite visible on the control board, you just need to follow the ribbon cable to see which hash board goes to which socket.
Thanks. Wanted it to clarify it. |
|
|
|
|
Now when i checked carefully with a flashlight, i saw J1, J2 and J3 on the control board. That should be it? Thanks.
|
|
|
|
Hi guys Which hashboard is hashboard 1 (chain 0)? Closes to the PSU for example. Maybe @mikeywith can help me?  |
|
|
|
|
The new version 20.10 seems to not work on my 2 S17Pro.
1st one drops a hashboard all the time. Works fine with the 20.09.1 version.
2nd one doing its autotune for 6 minutes and starts over again, like its in a loop all the time. Works fine with 20.09.1 version.
Any other have the same issues?
|
|
|
|
I have yet to try an S17, in the S9 you can set it to 100. Realistically, it will give about 100w to each card, so while you can type 100 (or 200), its more like 300w is the actual minimal for the S9.
I'm surprised that the S17 has such high minimal, i will ask and report.
Heard anything yet? |
|
|
|
|
We are talking about S17 Pro right? Forgot to mention it.
|
|
|
|
|
Why can´t we go below 1480 watt on the autotune setting? Is there a reason for that?
|
|
|
|
There are no jumpers in the S17. It boots from it if you insert an sd card.
Ok, thanks. Haven't open it to see if i find any jumpers. Now i know This looks smooth, gonna try tomorrow. |
|
|
|
Does this apply S17 Pro: Install Braiins OS+ using SD card
Download the SD card image from our website.
Flash the downloaded image on an SD card (e.g. using Etcher). Note: Simple copy to SD card will not work. The SD card has to be flashed!
Adjust the jumpers to boot from SD card (instead of NAND memory), as shown below.
|
|
|
|
Don't look at the kernel date, look at the File System Version date.
Ok, so can we install this to a newer S17Pro from January 2020? Don't know the exact file system version. |
|
|
|
What appears to be certain, is that the S19 ships with this "feature", and the newer firmware updates in the rest of the S17 family do this as well. So if you even have even the slightest plan to ever try Braiins OS in your S17, make sure you do not ever update the firmware. Because, it is yet to be seen if these could be bypassed somehow (without getting a solder gun, that is).
How old firmware are we talking about? I have Linux 4.6.0-xilinx-gff8137b-dirty #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018. Should be good. Thinking about buying another one for cheap bucks. |
|
|
|
So no HW Error % count yet? And the temp issue fixed? Keep up the good work  |
|
|
|
|
