Debian packages for cgminer

[turtle83]

Just been playing with debian packaging system, made a few builds of cgminer for Debian.

Raspbian (armhf binary for raspberry pi) : https://mega.co.nz/#!HdZWXaJL!f8Tq2Td275SK1Dkv0KiBYAQQuFN00vfsuL3v7_cIrsE
Freenet users: http://127.0.0.1:8888/CHK@Tg1d463DWjpJ0xemBlgDnKEomNkycdZFuNa36ceYLyI,bG~Q8DdHdZ93PmHuDBcDANxa8P78Wth2Ze98yWqzpCU,AAMC--8/cgminer_3.5.0-1_armhf.deb

Instructions:

Code:

sudo apt-get update #Make sure repos are up to date
sudo dpkg -i cgminer_3.5.0-1_armhf.deb #May complain about missing dependencies, dont panic next step takes care of it
sudo apt-get -f install #Installs the needed dependencies and then failed cgminer form above step.

Ubuntu (raring) :  launchpad. ppa:theturtle1983/mining . packages for raring should show up in there in 12 hours if the build was successful has binaries for Lucid thru Raring.
Instructions:

sudo add-apt-repository ppa:theturtle1983/mining
sudo apt-get update
sudo apt-get install cgminer

Cgminer is configured with following arguments

Code:

--disable-opencl --disable-adl --enable-bflsc --enable-bitforce --enable-icarus --enable-modminer --enable-ztex --enable-avalon

(Basically dissable GPU mining and enable all FPGA/ASIC)

You can then run cgminer normally.

Code:

sudo cgminer #arguments....

sudo is needed at the moment since currently no udev rules are being added. If you can add the rules for your devices then skip the sudo.

TODOs:-

Code:

#TODO: Description, etc (credit upstream)
#TODO: Print cgminer tip address post install
#TODO: Add in usb rules
#TODO: Add in default config
#TODO: Add init script (launch in screen). Launch on boot. start/stop/restart/status
#TODO: Add some kind of web interface
#TOTO: Perhaps some cli tools to get info from running instance
#TODO: Do the same for bfgminer if people are insterested

I built the raspbian package for personal use. Building on the pi takes for ever and I don't know how to cross compile. This is personal timesaver for next time i wanna install on raspi. Cuts few minutes to few seconds, and don't need to bloat production system with loads of -dev packages anymore.

[1714598989]

1714598989

[1714598989]

1714598989

[1714598989]

1714598989

[Chemicalbro]

How did you avoid running out of memory when building on the Pi?

[turtle83]

How did you avoid running out of memory when building on the Pi?

Never had memory issues. Didnt do anything fancy.

That said im using raspbian server edition, and allocated the lowest possible memory for GPU... so maybe without the added bloat of GUI it just doesnt encounter any limits.

Also, you can load up raspbian in qemu, but thats even slower than building on the device...

[Chemicalbro]

Hmm oh. Maybe my memory is bad, perhaps it was bitcoind that wouldn't build.

[turtle83]

Hmm oh. Maybe my memory is bad, perhaps it was bitcoind that wouldn't build.

Dont even try building bitcoind . even if you can build it... dont run it. It would run slower than turtle... and reduce life of your SD card.

[Chemicalbro]

Unless your booting from usb.

[turtle83]

Unless your booting from usb.

Even if you store the blockchain on usb, it would still be really shitty performance. The CPU just wont be able to handle it. Even simple queries would take minutes to complete. YMMW.

If the build is memory constrained, qemu wont help since the qemu kernel for raspbian is locked to 256MB... you would need to cross compile on proper PC. I don't know how to do that.

[Khertan]

In case you care, there is a tutorial on compiling ffmpeg for raspberrypi, as it s require that you install a cross compiling toolchain it s perfect for compiling other things

http://ffmpeg.org/trac/ffmpeg/wiki/How%20to%20compile%20FFmpeg%20for%20Raspberry%20Pi%20%28Raspbian%29

[turtle83]

In case you care, there is a tutorial on compiling ffmpeg for raspberrypi, as it s require that you install a cross compiling toolchain it s perfect for compiling other things

http://ffmpeg.org/trac/ffmpeg/wiki/How%20to%20compile%20FFmpeg%20for%20Raspberry%20Pi%20%28Raspbian%29

Interesting. This is a detailed guide... for cross compile noobs like me.

Was skiming over something earlier to hook in dpkg-buildpackage with crosscompile-ng will see if it works . if so then .deb creation process will probably be quick on my i7... want to use .deb that way when i can make and maintain init scrips, udev rules, etc.

[Khertan]

You could also use an Open Suse Builder service (OBS), if it has the arm arch and debian release, or set your own, but that will be more difficult i think than cross compiling on your own computer.

[turtle83]

You could also use an Open Suse Builder service (OBS), if it has the arm arch and debian release, or set your own, but that will be more difficult i think than cross compiling on your own computer.

Interesting.
I am now using launchpad for building ubuntu packages. Just need to upload source deb. Takes hours for a build, but i can build 100% compatible packages for various releases of ubuntu without thinking about dependencies, etc... if it got built there, its likely to get installed without any fuss on target release.

OBS looks interesting. but... https://build.opensuse.org/monitor  they seem to be missing armv6l

[Khertan]

That 's depends on the obs configuration (meego cobs got x86, armelv6 7l 7l with hf or not). But that s osb is dead now.