<![CDATA[COMPILADOS NOSTR]]> https://compilados.npub.pro/tag/linux/ https://compilados.npub.pro/tag/linux/rss/ episodic Fri, 02 May 2025 03:50:46 GMT Fri, 02 May 2025 03:50:46 GMT <![CDATA[COMPILADOS NOSTR]]> https://compilados.npub.pro/tag/linux/ https://pfp.nostr.build/d04bb7baa476bbb67c4b0bb02e676d0fb8cd20b809f6956ed68d2adc647b91b1.jpg <![CDATA[Surviving the Raspberry Pi ZFS Kernel Trap: From Panic to Recovery]]> Fri, 02 May 2025 03:50:46 GMT https://compilados.npub.pro/post/1746157452265/ https://compilados.npub.pro/post/1746157452265/ naddr1qqxnzde5xccn2de5x5eryd34qgsrl7kr5my9n6423nwaktrsq2nwzzenal4e95p9k9826mu294jkv4crqsqqqa28n0u4dt raspberrypi naddr1qqxnzde5xccn2de5x5eryd34qgsrl7kr5my9n6423nwaktrsq2nwzzenal4e95p9k9826mu294jkv4crqsqqqa28n0u4dt npub18lav8fkgt8424rxamvk8qq4xuy9n8mltjtgztv2w44hc5tt9vets0hcfsz Introduction: Don't Despair—This Can Be Fixed (But Don't Reboot Yet)

Running ZFS on a Raspberry Pi offers powerful features for home servers and personal NAS setups. But with power comes complexity, and in recent months, a quiet pitfall has emerged for Pi users who track kernel updates closely: upgrading to an unsupported kernel version breaks ZFS.

⚠️ Important Warning: If you've just upgraded your kernel and you're using ZFS, do not reboot yet. Rebooting without a working ZFS module can leave your system unbootable—even if you don't have critical partitions on ZFS. The system may hang because it tries to load the missing ZFS kernel module during boot and fails, halting the boot process.

If you're already facing a broken setup or can't boot — don't panic. This guide outlines both the worst-case scenario and the ideal recovery strategy. Whether you're locked out or preparing for a smooth upgrade, we've got you covered.

The Problem: A Kernel Update Too Far

As of ZFS version 2.2.3 (used in Debian-based Raspberry Pi OS), the filesystem supports Linux kernels up to 6.7. However, Raspberry Pi OS backports recently began shipping 6.12.x kernels. If you upgrade to 6.12 without precautions:

  • ZFS will fail to compile against the new kernel
  • DKMS errors will appear during package updates
  • Your ZFS module will be missing after reboot
  • Your Raspberry Pi may fail to boot, even without ZFS-mounted root or critical paths, simply due to systemd or boot scripts expecting the kernel module to be present

Example ZFS Compilation Error:

During package updates or installs, you'll see something like:

checking whether bdev_open_by_path() exists... configure: error:
        *** None of the expected "blkdev_get_by_path()" interfaces were detected.
        *** This may be because your kernel version is newer than what is
        *** supported, or you are using a patched custom kernel with
        *** incompatible modifications.
        ***
        *** ZFS Version: zfs-2.2.3-1~bpo12+1~rpt1
        *** Compatible Kernels: 3.10 - 6.7

This error means ZFS cannot build its kernel module against Linux 6.12.x, making it unusable.

Why This Happens: The Version Trap

The key problem is that ZFS 2.2.3 remains installed even after a kernel upgrade, and it doesn't get upgraded automatically during apt upgrade. Since ZFS 2.2.3 only supports up to kernel 6.7, it fails to compile against 6.12.x.

However, if you remove and then reinstall ZFS, the package manager installs ZFS 2.3.1, which does support Linux kernel 6.12.x. This version transition is what resolves the issue — but only if you explicitly purge and reinstall ZFS.

Worst Case: The System That Wouldn’t Boot

After upgrading the kernel and rebooting, the system failed to boot properly. It showed errors like:

cannot open access to console, the root account is locked

Although the system did not have critical filesystems on ZFS, the boot process still stalled because system services attempted to load the ZFS kernel module, which was no longer available. This resulted in an unrecoverable boot failure.

The only way forward was to reformat and reinstall Raspberry Pi OS. However, the default Raspberry Pi OS image still comes with a 6.6.x kernel, which is incompatible with ZFS 2.3.1 and newer kernels unless upgraded. Therefore, the recovery process requires one crucial step:

  1. First, perform a full system upgrade:

    sudo apt update && sudo apt full-upgrade

    This brings the kernel up to 6.12.x.

  2. Then, reinstall ZFS:

    sudo apt install zfs-dkms zfsutils-linux

Once this is complete, your system will be running kernel 6.12 with ZFS 2.3.1, and you can safely import your pools and resume operations.

Best Case Recovery: Clean Cut, Clean Upgrade

For users who can still log into their system, here's the cleanest and safest sequence to move forward:

  1. Stop all services using ZFS, including Docker, NFS, Samba, backup tools, etc.

  2. Export all ZFS pools:

    sudo zpool export -a

  3. Disable swap if it lives on a ZFS vdev:

    sudo swapoff /dev/sdXn

  4. Purge ZFS packages:

    sudo apt purge zfsutils-linux zfs-dkms zfs-zed
sudo rm -rf /usr/src/zfs* /var/lib/dkms/zfs

  5. Update the kernel to the desired version:

    sudo apt update && sudo apt full-upgrade

  6. Reboot into the new kernel:

    sudo reboot

  7. Reinstall ZFS:

    sudo apt install zfs-dkms zfsutils-linux

  8. Import your pool(s):

    sudo zpool import poolname

  9. Restart services that depend on ZFS.

Final Notes: Prevention Is Better Than Recovery

To avoid this issue in the future:

  • Hold your current working kernel version:

    sudo apt-mark hold linux-image-rpi-v8 linux-headers-rpi-v8

  • Or track ZFS GitHub for kernel compatibility before upgrading

  • Or test upgrades on a second Pi or cloned SD card before rolling them out to production

Conclusion: A Solvable Trap

ZFS on the Raspberry Pi remains a powerful option, but it demands careful version tracking. If you upgrade responsibly, or recover cleanly as described above, you can continue benefiting from advanced features like snapshots, send/receive, and compression even on this tiny powerhouse.

Don’t let a kernel update ruin your storage plans—with preparation, the Pi + ZFS combo can remain stable and strong.

]]> Introduction: Don't Despair—This Can Be Fixed (But Don't Reboot Yet)

Running ZFS on a Raspberry Pi offers powerful features for home servers and personal NAS setups. But with power comes complexity, and in recent months, a quiet pitfall has emerged for Pi users who track kernel updates closely: upgrading to an unsupported kernel version breaks ZFS.

⚠️ Important Warning: If you've just upgraded your kernel and you're using ZFS, do not reboot yet. Rebooting without a working ZFS module can leave your system unbootable—even if you don't have critical partitions on ZFS. The system may hang because it tries to load the missing ZFS kernel module during boot and fails, halting the boot process.

If you're already facing a broken setup or can't boot — don't panic. This guide outlines both the worst-case scenario and the ideal recovery strategy. Whether you're locked out or preparing for a smooth upgrade, we've got you covered.

The Problem: A Kernel Update Too Far

As of ZFS version 2.2.3 (used in Debian-based Raspberry Pi OS), the filesystem supports Linux kernels up to 6.7. However, Raspberry Pi OS backports recently began shipping 6.12.x kernels. If you upgrade to 6.12 without precautions:

  • ZFS will fail to compile against the new kernel
  • DKMS errors will appear during package updates
  • Your ZFS module will be missing after reboot
  • Your Raspberry Pi may fail to boot, even without ZFS-mounted root or critical paths, simply due to systemd or boot scripts expecting the kernel module to be present

Example ZFS Compilation Error:

During package updates or installs, you'll see something like:

checking whether bdev_open_by_path() exists... configure: error:
        *** None of the expected "blkdev_get_by_path()" interfaces were detected.
        *** This may be because your kernel version is newer than what is
        *** supported, or you are using a patched custom kernel with
        *** incompatible modifications.
        ***
        *** ZFS Version: zfs-2.2.3-1~bpo12+1~rpt1
        *** Compatible Kernels: 3.10 - 6.7

This error means ZFS cannot build its kernel module against Linux 6.12.x, making it unusable.

Why This Happens: The Version Trap

The key problem is that ZFS 2.2.3 remains installed even after a kernel upgrade, and it doesn't get upgraded automatically during apt upgrade. Since ZFS 2.2.3 only supports up to kernel 6.7, it fails to compile against 6.12.x.

However, if you remove and then reinstall ZFS, the package manager installs ZFS 2.3.1, which does support Linux kernel 6.12.x. This version transition is what resolves the issue — but only if you explicitly purge and reinstall ZFS.

Worst Case: The System That Wouldn’t Boot

After upgrading the kernel and rebooting, the system failed to boot properly. It showed errors like:

cannot open access to console, the root account is locked

Although the system did not have critical filesystems on ZFS, the boot process still stalled because system services attempted to load the ZFS kernel module, which was no longer available. This resulted in an unrecoverable boot failure.

The only way forward was to reformat and reinstall Raspberry Pi OS. However, the default Raspberry Pi OS image still comes with a 6.6.x kernel, which is incompatible with ZFS 2.3.1 and newer kernels unless upgraded. Therefore, the recovery process requires one crucial step:

  1. First, perform a full system upgrade:

    sudo apt update && sudo apt full-upgrade

    This brings the kernel up to 6.12.x.

  2. Then, reinstall ZFS:

    sudo apt install zfs-dkms zfsutils-linux

Once this is complete, your system will be running kernel 6.12 with ZFS 2.3.1, and you can safely import your pools and resume operations.

Best Case Recovery: Clean Cut, Clean Upgrade

For users who can still log into their system, here's the cleanest and safest sequence to move forward:

  1. Stop all services using ZFS, including Docker, NFS, Samba, backup tools, etc.

  2. Export all ZFS pools:

    sudo zpool export -a

  3. Disable swap if it lives on a ZFS vdev:

    sudo swapoff /dev/sdXn

  4. Purge ZFS packages:

    sudo apt purge zfsutils-linux zfs-dkms zfs-zed
sudo rm -rf /usr/src/zfs* /var/lib/dkms/zfs

  5. Update the kernel to the desired version:

    sudo apt update && sudo apt full-upgrade

  6. Reboot into the new kernel:

    sudo reboot

  7. Reinstall ZFS:

    sudo apt install zfs-dkms zfsutils-linux

  8. Import your pool(s):

    sudo zpool import poolname

  9. Restart services that depend on ZFS.

Final Notes: Prevention Is Better Than Recovery

To avoid this issue in the future:

  • Hold your current working kernel version:

    sudo apt-mark hold linux-image-rpi-v8 linux-headers-rpi-v8

  • Or track ZFS GitHub for kernel compatibility before upgrading

  • Or test upgrades on a second Pi or cloned SD card before rolling them out to production

Conclusion: A Solvable Trap

ZFS on the Raspberry Pi remains a powerful option, but it demands careful version tracking. If you upgrade responsibly, or recover cleanly as described above, you can continue benefiting from advanced features like snapshots, send/receive, and compression even on this tiny powerhouse.

Don’t let a kernel update ruin your storage plans—with preparation, the Pi + ZFS combo can remain stable and strong.

]]> <![CDATA[How to Run a Sapphire Block Erupter USB for Mining on Linux in 2025]]> Sat, 08 Mar 2025 23:07:55 GMT https://compilados.npub.pro/post/1741475186693/ https://compilados.npub.pro/post/1741475186693/ naddr1qqxnzde5xy6rwdf38qmrvwfnqgsrl7kr5my9n6423nwaktrsq2nwzzenal4e95p9k9826mu294jkv4crqsqqqa28586s4e Bitcoin naddr1qqxnzde5xy6rwdf38qmrvwfnqgsrl7kr5my9n6423nwaktrsq2nwzzenal4e95p9k9826mu294jkv4crqsqqqa28586s4e npub18lav8fkgt8424rxamvk8qq4xuy9n8mltjtgztv2w44hc5tt9vets0hcfsz Recently, I found an old Sapphire Block Erupter USB at home that I used for Bitcoin mining back in 2013. Out of curiosity and nostalgia, I decided to try getting it to work again. I spent an entire afternoon configuring the device and, after much trial and error, discovered that I needed an older version of CGMiner to make it work.

The Sapphire Block Erupter USB was one of the first ASIC devices designed for Bitcoin mining. Although obsolete for competitive mining, it can still be used for learning, nostalgia, or experimentation. In this post, I’ll show you how to run a Block Erupter USB on Linux today.

1. Prerequisites

Before you start, make sure you have:

  • A Sapphire Block Erupter USB
  • A powered USB hub (optional but recommended)
  • A computer running Linux (Ubuntu, Debian, or another compatible distribution)
  • A mining pool account (e.g., Slush Pool, KanoPool, etc.)

2. Installing Dependencies

Before running the miner, install some dependencies:

sudo apt update && sudo apt install -y git build-essential autoconf automake libtool pkg-config libusb-1.0-0-dev

3. Determining the Compatible Version of CGMiner

To find the correct CGMiner version that still supports Block Erupter USB, I performed a binary search across different versions, testing each one until I found the last one that properly recognized the device. The result was that version 3.4.3 is the most recent one that still supports Block Erupters. However, different versions of these devices may require different CGMiner versions.

4. Downloading and Compiling CGMiner

CGMiner is one of the software options compatible with Block Erupters. You can download the correct version from two trusted sources:

To ensure file integrity, verify the SHA-256 hash:

3b44da12e5f24f603eeeefdaa2c573bd566c5c50c9d62946f198e611cd55876b

Now, download and extract it:

wget https://github.com/ckolivas/cgminer/archive/refs/tags/v3.4.3.tar.gz
# Or, alternatively:
wget https://haven.girino.org/3b44da12e5f24f603eeeefdaa2c573bd566c5c50c9d62946f198e611cd55876b.tgz

sha256sum v3.4.3.tar.gz  # Confirm that the hash matches

# Extract the file
tar -xvf v3.4.3.tar.gz
cd cgminer-3.4.3

# Compile CGMiner
./autogen.sh --enable-icarus
make -j$(nproc)

# Install on the system (optional)
sudo make install

5. Connecting the Block Erupter USB

Plug the device into a USB port and check if it is recognized:

dmesg | grep USB
lsusb

You should see something like:

Bus 003 Device 004: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP2102 USB to UART Bridge Controller

If needed, adjust the USB device permissions:

sudo chmod 666 /dev/ttyUSB0

6. Configuring and Running CGMiner

Now, run CGMiner, pointing it to your mining pool:

./cgminer -o stratum+tcp://your.pool.com:3333 -u yourUsername -p yourPassword

If the miner detects the Block Erupter correctly, you should see something like:

 [2025-03-08 22:26:45] Started cgminer 3.4.3
 [2025-03-08 22:26:45] No devices detected!
 [2025-03-08 22:26:45] Waiting for USB hotplug devices or press q to quit
 [2025-03-08 22:26:45] Probing for an alive pool
 [2025-03-08 22:26:46] Pool 0 difficulty changed to 65536
 [2025-03-08 22:26:46] Network diff set to 111T
 [2025-03-08 22:26:46] Stratum from pool 0 detected new block
 [2025-03-08 22:27:02] Hotplug: Icarus added AMU 0

Conclusion

Although no longer viable for real mining, the Sapphire Block Erupter USB is still great for learning about ASICs, testing mining pools, and understanding Bitcoin mining. If you enjoy working with old hardware and have one lying around, it’s worth experimenting with!

If you have any questions or want to share your experience, leave a comment below!

]]> Recently, I found an old Sapphire Block Erupter USB at home that I used for Bitcoin mining back in 2013. Out of curiosity and nostalgia, I decided to try getting it to work again. I spent an entire afternoon configuring the device and, after much trial and error, discovered that I needed an older version of CGMiner to make it work.

The Sapphire Block Erupter USB was one of the first ASIC devices designed for Bitcoin mining. Although obsolete for competitive mining, it can still be used for learning, nostalgia, or experimentation. In this post, I’ll show you how to run a Block Erupter USB on Linux today.

1. Prerequisites

Before you start, make sure you have:

  • A Sapphire Block Erupter USB
  • A powered USB hub (optional but recommended)
  • A computer running Linux (Ubuntu, Debian, or another compatible distribution)
  • A mining pool account (e.g., Slush Pool, KanoPool, etc.)

2. Installing Dependencies

Before running the miner, install some dependencies:

sudo apt update && sudo apt install -y git build-essential autoconf automake libtool pkg-config libusb-1.0-0-dev

3. Determining the Compatible Version of CGMiner

To find the correct CGMiner version that still supports Block Erupter USB, I performed a binary search across different versions, testing each one until I found the last one that properly recognized the device. The result was that version 3.4.3 is the most recent one that still supports Block Erupters. However, different versions of these devices may require different CGMiner versions.

4. Downloading and Compiling CGMiner

CGMiner is one of the software options compatible with Block Erupters. You can download the correct version from two trusted sources:

To ensure file integrity, verify the SHA-256 hash:

3b44da12e5f24f603eeeefdaa2c573bd566c5c50c9d62946f198e611cd55876b

Now, download and extract it:

wget https://github.com/ckolivas/cgminer/archive/refs/tags/v3.4.3.tar.gz
# Or, alternatively:
wget https://haven.girino.org/3b44da12e5f24f603eeeefdaa2c573bd566c5c50c9d62946f198e611cd55876b.tgz

sha256sum v3.4.3.tar.gz  # Confirm that the hash matches

# Extract the file
tar -xvf v3.4.3.tar.gz
cd cgminer-3.4.3

# Compile CGMiner
./autogen.sh --enable-icarus
make -j$(nproc)

# Install on the system (optional)
sudo make install

5. Connecting the Block Erupter USB

Plug the device into a USB port and check if it is recognized:

dmesg | grep USB
lsusb

You should see something like:

Bus 003 Device 004: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP2102 USB to UART Bridge Controller

If needed, adjust the USB device permissions:

sudo chmod 666 /dev/ttyUSB0

6. Configuring and Running CGMiner

Now, run CGMiner, pointing it to your mining pool:

./cgminer -o stratum+tcp://your.pool.com:3333 -u yourUsername -p yourPassword

If the miner detects the Block Erupter correctly, you should see something like:

 [2025-03-08 22:26:45] Started cgminer 3.4.3
 [2025-03-08 22:26:45] No devices detected!
 [2025-03-08 22:26:45] Waiting for USB hotplug devices or press q to quit
 [2025-03-08 22:26:45] Probing for an alive pool
 [2025-03-08 22:26:46] Pool 0 difficulty changed to 65536
 [2025-03-08 22:26:46] Network diff set to 111T
 [2025-03-08 22:26:46] Stratum from pool 0 detected new block
 [2025-03-08 22:27:02] Hotplug: Icarus added AMU 0

Conclusion

Although no longer viable for real mining, the Sapphire Block Erupter USB is still great for learning about ASICs, testing mining pools, and understanding Bitcoin mining. If you enjoy working with old hardware and have one lying around, it’s worth experimenting with!

If you have any questions or want to share your experience, leave a comment below!

]]> <![CDATA[Como Rodar um Sapphire Block Erupter USB para Mineração no Linux em 2025]]> Sat, 08 Mar 2025 23:02:08 GMT https://compilados.npub.pro/post/1741474660659/ https://compilados.npub.pro/post/1741474660659/ naddr1qqxnzde5xy6rwdpkxccrvdfeqgsrl7kr5my9n6423nwaktrsq2nwzzenal4e95p9k9826mu294jkv4crqsqqqa28f3r5l4 Mineração naddr1qqxnzde5xy6rwdpkxccrvdfeqgsrl7kr5my9n6423nwaktrsq2nwzzenal4e95p9k9826mu294jkv4crqsqqqa28f3r5l4 npub18lav8fkgt8424rxamvk8qq4xuy9n8mltjtgztv2w44hc5tt9vets0hcfsz Como Rodar um Sapphire Block Erupter USB para Mineração no Linux em 2025

Recentemente, encontrei um Sapphire Block Erupter USB velho aqui em casa que eu usava para minerar Bitcoin em 2013. Por curiosidade e nostalgia, resolvi tentar colocá-lo para funcionar novamente. Passei uma tarde inteira tentando configurar o dispositivo e, depois de muita tentativa e erro, descobri que precisava de uma versão mais antiga do CGMiner para fazê-lo funcionar.

Os Sapphire Block Erupter USB foram um dos primeiros dispositivos ASIC voltados para mineração de Bitcoin. Embora estejam obsoletos para mineração competitiva, eles ainda podem ser usados para aprendizado, nostalgia ou experimentação. Neste post, vou te mostrar como rodar um Block Erupter USB no Linux atualmente.

1. Pré-requisitos

Antes de começar, certifique-se de que você tem:

  • Um Sapphire Block Erupter USB
  • Um hub USB alimentado (opcional, mas recomendado)
  • Um computador rodando Linux (Ubuntu, Debian, Arch ou outra distribuição compatível)
  • Um pool de mineração configurado (ex: Slush Pool, KanoPool, etc.)

2. Instalando as Dependências

Antes de rodar o minerador, instale algumas dependências:

sudo apt update && sudo apt install -y git build-essential autoconf automake libtool pkg-config libusb-1.0-0-dev

3. Determinando a Versão Compatível do CGMiner

Para encontrar a versão correta do CGMiner que ainda suporta os Block Erupter USB, realizei uma busca binária entre diferentes versões, testando cada uma até encontrar a última que reconhecia corretamente o dispositivo. O resultado foi que a versão 3.4.3 é a mais recente que ainda suporta os Block Erupters. No entanto, outras versões desses dispositivos podem requerer versões diferentes do CGMiner.

4. Baixando e Compilando o CGMiner

O CGMiner é um dos softwares compatíveis com os Block Erupters. Você pode baixar a versão correta de duas fontes confiáveis:

Para garantir a integridade do arquivo, você pode verificar o hash SHA-256:

3b44da12e5f24f603eeeefdaa2c573bd566c5c50c9d62946f198e611cd55876b

Agora, faça o download e extraia:

wget https://github.com/ckolivas/cgminer/archive/refs/tags/v3.4.3.tar.gz
# Ou, alternativamente:
wget https://haven.girino.org/3b44da12e5f24f603eeeefdaa2c573bd566c5c50c9d62946f198e611cd55876b.tgz

sha256sum v3.4.3.tar.gz  # Confirme que o hash bate

# Extraia o arquivo
 tar -xvf v3.4.3.tar.gz
 cd cgminer-3.4.3

# Compile o CGMiner
./autogen.sh --enable-icarus
make -j$(nproc)

# Instale no sistema (opcional)
sudo make install

4. Conectando o Block Erupter USB

Plugue o dispositivo na porta USB e verifique se ele foi reconhecido:

dmesg | grep USB
lsusb

Você deve ver algo como:

Bus 003 Device 004: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP2102 USB to UART Bridge Controller

Se necessário, ajuste as permissões para o dispositivo USB:

sudo chmod 666 /dev/ttyUSB0

5. Configurando e Rodando o CGMiner

Agora, execute o CGMiner apontando para seu pool de mineração:

./cgminer -o stratum+tcp://seu.pool.com:3333 -u seuUsuario -p suaSenha

Se o minerador detectar corretamente o Block Erupter, você verá algo como:

 [2025-03-08 22:26:45] Started cgminer 3.4.3
 [2025-03-08 22:26:45] No devices detected!
 [2025-03-08 22:26:45] Waiting for USB hotplug devices or press q to quit
 [2025-03-08 22:26:45] Probing for an alive pool
 [2025-03-08 22:26:46] Pool 0 difficulty changed to 65536
 [2025-03-08 22:26:46] Network diff set to 111T
 [2025-03-08 22:26:46] Stratum from pool 0 detected new block
 [2025-03-08 22:27:02] Hotplug: Icarus added AMU 0

Conclusão

Apesar de não serem mais viáveis para mineração real, os Sapphire Block Erupter USB ainda são ótimos para aprender sobre ASICs, testar pools e entender mais sobre a mineração de Bitcoin. Se você gosta de hardware antigo e tem um desses guardado, vale a pena experimentar!

Se tiver dúvidas ou quiser compartilhar sua experiência, comente abaixo!

]]> Como Rodar um Sapphire Block Erupter USB para Mineração no Linux em 2025

Recentemente, encontrei um Sapphire Block Erupter USB velho aqui em casa que eu usava para minerar Bitcoin em 2013. Por curiosidade e nostalgia, resolvi tentar colocá-lo para funcionar novamente. Passei uma tarde inteira tentando configurar o dispositivo e, depois de muita tentativa e erro, descobri que precisava de uma versão mais antiga do CGMiner para fazê-lo funcionar.

Os Sapphire Block Erupter USB foram um dos primeiros dispositivos ASIC voltados para mineração de Bitcoin. Embora estejam obsoletos para mineração competitiva, eles ainda podem ser usados para aprendizado, nostalgia ou experimentação. Neste post, vou te mostrar como rodar um Block Erupter USB no Linux atualmente.

1. Pré-requisitos

Antes de começar, certifique-se de que você tem:

  • Um Sapphire Block Erupter USB
  • Um hub USB alimentado (opcional, mas recomendado)
  • Um computador rodando Linux (Ubuntu, Debian, Arch ou outra distribuição compatível)
  • Um pool de mineração configurado (ex: Slush Pool, KanoPool, etc.)

2. Instalando as Dependências

Antes de rodar o minerador, instale algumas dependências:

sudo apt update && sudo apt install -y git build-essential autoconf automake libtool pkg-config libusb-1.0-0-dev

3. Determinando a Versão Compatível do CGMiner

Para encontrar a versão correta do CGMiner que ainda suporta os Block Erupter USB, realizei uma busca binária entre diferentes versões, testando cada uma até encontrar a última que reconhecia corretamente o dispositivo. O resultado foi que a versão 3.4.3 é a mais recente que ainda suporta os Block Erupters. No entanto, outras versões desses dispositivos podem requerer versões diferentes do CGMiner.

4. Baixando e Compilando o CGMiner

O CGMiner é um dos softwares compatíveis com os Block Erupters. Você pode baixar a versão correta de duas fontes confiáveis:

Para garantir a integridade do arquivo, você pode verificar o hash SHA-256:

3b44da12e5f24f603eeeefdaa2c573bd566c5c50c9d62946f198e611cd55876b

Agora, faça o download e extraia:

wget https://github.com/ckolivas/cgminer/archive/refs/tags/v3.4.3.tar.gz
# Ou, alternativamente:
wget https://haven.girino.org/3b44da12e5f24f603eeeefdaa2c573bd566c5c50c9d62946f198e611cd55876b.tgz

sha256sum v3.4.3.tar.gz  # Confirme que o hash bate

# Extraia o arquivo
 tar -xvf v3.4.3.tar.gz
 cd cgminer-3.4.3

# Compile o CGMiner
./autogen.sh --enable-icarus
make -j$(nproc)

# Instale no sistema (opcional)
sudo make install

4. Conectando o Block Erupter USB

Plugue o dispositivo na porta USB e verifique se ele foi reconhecido:

dmesg | grep USB
lsusb

Você deve ver algo como:

Bus 003 Device 004: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP2102 USB to UART Bridge Controller

Se necessário, ajuste as permissões para o dispositivo USB:

sudo chmod 666 /dev/ttyUSB0

5. Configurando e Rodando o CGMiner

Agora, execute o CGMiner apontando para seu pool de mineração:

./cgminer -o stratum+tcp://seu.pool.com:3333 -u seuUsuario -p suaSenha

Se o minerador detectar corretamente o Block Erupter, você verá algo como:

 [2025-03-08 22:26:45] Started cgminer 3.4.3
 [2025-03-08 22:26:45] No devices detected!
 [2025-03-08 22:26:45] Waiting for USB hotplug devices or press q to quit
 [2025-03-08 22:26:45] Probing for an alive pool
 [2025-03-08 22:26:46] Pool 0 difficulty changed to 65536
 [2025-03-08 22:26:46] Network diff set to 111T
 [2025-03-08 22:26:46] Stratum from pool 0 detected new block
 [2025-03-08 22:27:02] Hotplug: Icarus added AMU 0

Conclusão

Apesar de não serem mais viáveis para mineração real, os Sapphire Block Erupter USB ainda são ótimos para aprender sobre ASICs, testar pools e entender mais sobre a mineração de Bitcoin. Se você gosta de hardware antigo e tem um desses guardado, vale a pena experimentar!

Se tiver dúvidas ou quiser compartilhar sua experiência, comente abaixo!

]]>