look into public pool if you'd like to mine to your own node/pool. pretty sure you can compile that locally if you have access to the terminal.

https://github.com/benjamin-wilson/public-pool

as for running the usb stick miner on the raspberry pi 5, while i don't have a Pi 5, i have mynode running on a pi 4/compac F. if you install tmux, you should be able to run the miner "in a separate window" that runs in the background.

I'm not sure of the specifics of running a solo node, but you should be able to point cgminer at your local for work generation. I tend to solo using a solo pool (like kano's solo) but I know mining entirely to a local node is possible.

Instead of looking specifically for information for this miner, look up information for cgminer in general and go from there.

There's a good thread here for setting up a solo bitcoin node.

https://bitcointalk.org/index.php?topic=5415335.0

Though I don't think Kano has imported the modifications required to his branch of CGMiner to allow it to mine to Bitcoind directly.

I had to mod Kano's CGMiner 4.12.1 with the changes from https://github.com/cmmodtools/cgminer to make it work.

So its not straight forward unfortunately.


Using stock CGMiner from Kano https://github.com/kanoi/cgminer/ with a solo pool is far easier for the novice and that would be my preferred route too after finding out the effort required to set-up a local bitcoind node.

These should be in the wild soon.

The new code is up in my git (see my sig)
It reports temperature and per chip voltage on the screen
It does cooldown if it overheats
Voltage is controlled by startup and via the API.
Current code is only tested on Linux so far.

There's a new 01-cgminer.rules needed for linux for the new USB chip
See the README/USB for details,
though this works the same as required before for linux, just an updated file.

I'll update the help page https://kano.is/gekko.php at a later date,
but the dual BM1362 has mostly the same API as the R909 and CompacF
but a couple of extras.

It has a specific A1 start value - which I guess all the old Gekkos should have had before,
but it's there for the new A1
All the A1 specific options are:
--gekko-compaca1-start-freq NNN
--gekko-compaca1-corev nnn (mV)
--gekko-compaca1-detect
--gekko-compaca1-freq NNN

Miner selection by serial --gekko-serial can now also be a comma list of miners,
not only just one miner.

The blinky led is as follow:
When you first plug it in, it blinks every 1 second until it starts mining.
When mining, it blinks with work processing.
When you stop mining, the led goes off.

Have fun

Which version and on which algorithm?
When the cards are not OC its often an implementation bug on my side - especially the ZERO / GENX code of 0.5 had this problem because I was not careful enough in some routines so sometimes I write to memory addresses that did not exist - and that caused the problem. I had hope to get rid of this in 0.6, if not - please report with a bit more detail and I will revise the code again

Sorry for the delay here, this time debugging hurts me a lot.

Well at least I can resolve the AION game here.
Following the table with guesses, best guess in bold and in red the actual value:

1080 FE (~176 in 0.5):

User	Guess
mrshaw070	190
squeekie	200
catfish78	202
Benchmark 0.6	206.5
invizion	228
baraday	232

Rx 580 4G (~106.5 in 0.5):

User	Guess
mrshaw070	116
Benchmark 0.6	118.3
squeekie	120
catfish78	123
invizion	135
baraday	143

May the two winners send me an AION Mainnet Addr as private message so I can send their price?

I have to say the optimization was very odd this time. I started with Nvidia and the changing to 0.6 code style brought most of the improvements. So far so good. Then I tried more things I had in mind but ran into a kind of wall - it just did not want to improve behind this point. Or rather - one idea worked locally but then added a penalty later when reconstructing the solutions such that it was almost +-0.

AMD was totally different. Here the change to 0.6 code base was very buggy in  the beginning and once done it was exactly same speed as 0.5. Something is saturated there and so did not find the bottle neck. But then the +-0 idea of the NV code brought at least approx 4 sol/s. That was a start. Then started playing around and introduced some code part that I did not try anywhere before. But while NV was totally not impressed by this, here it brought about 7% speedup. Strange but well.

So, right now fixing more stuff - expect 0.6 alpha 3 in next 4-5 days.

----


The mining code is not stable for so many cards. The only way atm is to run 2x4 cards. That works fine. Still working on this issue and thats also why alpha 3 will not be last 0.6 alpha.


Imao perfectly fine. 100 sol/s is impossible for this cards - even a 2080ti without power limit may do 85 to 90 or so but no way more. Who ever told you 100 had no clue.


Hmm ... GCN1 cards is a bit difficult, some of them lacking some of the newer features. But the Hawaii series cards already do not run so bad - at least not slower then the Polaris cards that are much newer. I doubt that there is a specific optimization for them to make them fly higher. If any every trick for Polaris will help them, too.
So, plan for alpha 4 is to test some of the things recently learned in the 144/5 code. Lets see if anything there helps the AMDs.


I just can confirm that 0.6 alpha 3 will run all algorithms of 0.5, so MNX on AMD will run. But no idea about speed yet




The config file looking ok, but the miner may have problems with the fact that EXAMPLE_AION exists twice. But else it should work with 0.5. 0.6 does not yet support AION but will be changed in next alpha.

Both Wolf0 and ElioVP have decoded the timings
Editing bios is near impossible because it needs to be signed, good luck with that.

Hey Folks,

I just made the lolMiner 0.6 alpha 2 release public.
You can find the new version here:

Readme: https://github.com/Lolliedieb/lolMiner-preview/blob/master/README.md
Release: https://github.com/Lolliedieb/lolMiner-preview/releases


Changes so far:

- A new mining code for 192/7 (Zero, GenX) -
This one is based on the better 144/5 code. Compared to 0.5 the Nvidia code is ~25% faster, AMD approx 15%.
Also the code now should again work on headless 3G cards (~2860 MB required)

- A new mining code for MNX on Nvidia -
The AMD code will follow next week - I had some problems getting is full stable.
The Nvidia one is ~20% faster then 0.5 code. This will likely not be the final code for full 0.6, because well -
it beats ewbf 0.5, but not 0.6, so have enough motivation to improve it further xD

- Massive rework in the stratum interface -
I fixed a lot of bugs there. Most important are better routines to handle miner stuck when first connection attempt
does not work and a fix to the "received new job but stopped mining bug".
Also as new feature, lolMiner now is detecting which GPU got accepted shares and it measures the latency of the
pool response.

- Improved API / Statistics Module -
All the stats are now collected at one position in the miner (that was a code cleanup haha  )
The API now provides info about the pool latency, submitted and accepted shares for each GPU, the GPU names,
the GPUs PCIE address (for connecting miner with external tools) and so on.




Hope the new versions serves you well
Next then: MNX / AMD and Aion Looking forward to do this ... learned a lot working on this version again.


-------------------------------------
Room for your questions:


Yep


Good question - can not say it as well - but maybe check the new version ... maybe thats more stable.



This is not required - for suprnova just use --coin BTG and you will be fine.
For example I mine BTG with the line


What is odd here: clinfo is returning exactly nothing ...
Did you use the amdgpu-install with the right parameter for OpenCL, e.g.
Because if --opencl is not set it will only install the graphic part and not the compute part of the driver.