MuHack - User contributions [en]

UniBS Street Party 2025

2025-09-12T14:30:34Z

Mrmoddom: /* Stuff we need */

{{Event
|Picture=News usp25.jpg
|Website=https://www.unibs.it/it/ateneo/comunicazione/tutte-le-news/unibs-street-party-la-festa-di-inizio-anno-accademico-2025
|Super user=MrMoDDoM
|DateStart=2025-09-17
|DateEnd=2025-09-17
}}
= Stuff we have =
* Rollup
* Bandiera MuHack
* Bandiera WHY2025 (Ceres)
* Cabinato (Manuel)
* Valigetta laboratorio (Pesci)
* Amplificatore (Pesci)
* Targa MuHack (Pesci)
* Merch:
** Spille
** Portachiavi
** Sticker
* TV 50"
* Xbox
* Stampante 3D
* Scatola materiale elettrico (ciabatte, prolunghe, adattatori)
* Divano piccolo (?)
* Lampione + Gelatine colorate
* Scala
* Prolunga 30m

=== BSint ===
* Air Hockey
* Panche osteria
* Tavolo osteria
* Sedie plastica campeggio
* Carrello trasporto cose?

= Stuff we need =
* <s>Striscia led RGB (20m)</s>
* Faretti DMX (da chiedere, oppure [https://www.amazon.it/dp/B0DLZKBYX5 Amazon])
* Botticella 5l birra

== Stuff we might want to ask Uni to buy ==
* <s>Dischi air hockey</s>
* <s>Paperelle</s> Prese quelle NON squeaky ma florescenti
* Cavo AUX

= People =
* Pesci: Musica
* Ross: Press
* Ceres, Baraz: Recuperare cose BSint
* Dera, Davide, Luca: Recuperare cose aula associazioni
* Cammo: Xbox?
* Kibo: Luci

Whitepages

2025-05-28T07:56:58Z

Mrmoddom: /* Services */

= MuHack Services Index =
Welcome to the MuHack internal services directory. Below is a list of all the currently available tools, services, and internal resources for members.

* Services marked with 🔒 require VPN access or local/special permissions.
* Services marked with 🧑‍🤝‍🧑 require an active membership.

== Communication ==
* Telegram Channel - https://t.me/muhack - Public announcements
* 🧑‍🤝‍🧑 Telegram Group - Chat and coordination.
* 🧑‍🤝‍🧑 Discord - Discord Server for chatting, hacking, gaming together

== Hosting / Infrastructure ==
* Website - https://muhack.org - Public-facing site.
* MuHack Wiki - https://wiki.muhack.org/ - This wiki.
* 🔒 VPS - Coordinator server with services
* 🔒 [[GPU Server]] - Proxmox server with GPU
* 🔒 [[CPU Server]] - Proxmox server for general purpose VM/LXC

== Services ==
* 🔒 Ollama - http://ollama.muhack/ - Ollama instance for running LLM
* 🔒 Open WebUI - http://open-webui.muhack/ - Open WebUI for interacting with LLM in a graphical interface

== Development ==

== Access Control ==
* 🧑‍🤝‍🧑 Google Workspace - Every member has access to some of the GW's application, such as GMail and GDrive
* 🧑‍🤝‍🧑 VPN Access - Secure remote access to Tailscale network.

== Monitoring ==
Todo: eventually we want to setup some internal grafana and a public status page.

== Internal Tools ==
* 🔒 KnowledgeBase - https://kb.muhack.org/ - Repository for the internal technical/bureaucratic know-how
* 🧑‍🤝‍🧑 Vikunja - https://todo.muhack.org/ - Todo list for administrative/technical tasks
* 🧑‍🤝‍🧑 VaultWarden - https://vault.muhack.org/ - Web-based Password Manager

{{Note|type=info|text=For questions → email ceres-c@muhack.com, mrmoddom@muhack.com, or cammo@muhack.com - or just meet us at the Tuesday MuHack meeting :) }}

Open WebUI

2025-05-27T17:40:17Z

Mrmoddom: Created Open WebUI page

= Open WebUI =

'''Open WebUI''' is a self-hosted, browser-based user interface for accessing and interacting with large language models (LLMs) and AI tools running on MuHack’s internal GPU server. The project is designed to provide a clean, secure, and responsive interface for experimentation and development with AI models.

== Overview ==
* '''Project Name:''' Open WebUI
* '''Hosted on:''' [[GPU Server]]
* '''Access:''' by [[Tailscale VPN]]
* '''Purpose:''' To provide a lightweight, fast and extensible interface for interacting with local or remote LLMs from a web browser.

== Access Restrictions ==
Access to Open WebUI is strictly limited to internal members of MuHack.
To connect:
# Establish a secure connection via our internal VPN.
# Visit the internal address: `http://open-webui.muhack/`

For security and bandwidth reasons, the interface is **not exposed to the public internet**.

== Features ==
* Chat interface with markdown and code formatting
* Token and GPU usage tracking
* Multiple model backends supported (e.g. LLaMA, Mistral, GGUF)
* Local embeddings & vector search
* Session persistence
* Role-based access (using MuHack SSO)

== Current Status ==
Check the current service status on [[https://status.muhack.org/status/public|the status page]]

== Related Projects ==
* [[GPU Server]]
* [[Status monitor]]
* [https://github.com/open-webui/open-webui Upstream GitHub Project]

== Contact ==
For access or troubleshooting, contact:
* 📧 Email: webmaster@muhack.org

Status monitor

2025-05-27T16:45:31Z

Mrmoddom: Created Status monitor page - need to find a way to add Open Badges generated by Uptime Kuma

= Current Status =

We use [https://status.muhack.org Uptime Kuma] to monitor the availability of our self-hosted services.


== See Also ==
* [https://wiki.hackerspaces.org/MuHack MuHack on hackerspaces.org]

Melchiorre (Server)

2025-05-22T15:43:02Z

Mrmoddom:

{{Service
|Service URI=cpu.muhack
|Location=Aula associazioni
|Contact email=webmaster@muhack.org
|Operational Status=Working
|Super Users=Ceres-c, Mrmoddom, Cammo
|Owner=MuHack
|Physical Location=Aula associazioni
|URI=gpu.vpn.muhack (reachable on the MuHack Tailscale net)
|Project Status=Active
|Participants=Ceres-c, Mrmoddom, Cammo
}}
= MUHACK CPU SERVER =
A shared machine that gives all members access to personal VM/LXC for general purpose computations.

== What this box is for ==

* General computational needs

== Fast facts ==

* Host name : '''cpu.muhack''' (reachable only locally or through the MuHack Tailscale network)
* Management : Proxmox web UI @ port 8006 → [https://cpu.muhack:8006 Link]
* Sysadmins : '''Ceres-c, Mrmoddom, Cammo'''
* Contact : [mailto:webmaster@muhack.com webmaster@muhack.com] • or in person every Tuesday evening at the MuHack meeting

== Hardware ==

* CPU : 36 x Intel(R) Xeon(R) CPU E5-2696 v3 @ 2.30GHz (1 Socket)
* RAM : 64 GB ECC DDR4 @ 2400 Mhz
* GPU-A : NVIDIA GK208B [GeForce GT 710]
* Disks : SSD 256GB - 6TB Raid0 (3+3 HDD)
* NICs : Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller

== Software stack ==

* Proxmox VE 8.x (kernel 6.8)

= Getting your own environment =

# Make sure your laptop/PC is connected to the MuHack Tailscale tail-net and can <tt>ping gpu.muhack</tt>.
# Go to the [https://cpu.muhack:8006 proxmox login page] and login a first time to create your account and then logout immediately
# Talk to '''any sysadmin''' (email or in person on Tuesday). Tell us
## what you plan to run
## an estimate of how much RAM / runtime you’ll need
# We’ll create a container (or VM) for you and hand back:
## ID (e.g. <tt>ct104</tt> or <tt>vm203</tt>)
## a '''random initial password'''

''Typical turnaround time: usually same day or next-day. However might take more time if the sysadmins are busy.''
{{Note|type=warn|text=After the first login you have to re-login a second time to let proxmox setup correctly your account's group }}

At this point you have two options for interact with the console:
# Use the [https://cpu.muhack:8006 proxmox web interface]'s integrated console
# Join the machine to a tailnet (your personal or the MuHack's one) and connect trough SSH -> remember to enable ssh root access within sshd config file!

= Fair-share policy =

* Jobs longer than '''12 h''' → announce them at the Tuesday meeting or in the telegram channel.
* Sysadmins may pause/stop workloads that block others
* Crypto-mining strictly forbidden

== Good-citizen checklist ==

* If don't need to keep you VM/LXC up, shut it down for others: the resources are limited and shared!
* Keep <tt>/tmp</tt> and your home directory tidy; disk space is shared
* '''BACK UP YOUR OWN DATA: we have no data persistency or backup guarantee'''

Questions / ideas → email '''[mailto:ceres-c@muhack.com ceres-c@muhack.com]''', '''[mailto:mrmoddom@muhack.com mrmoddom@muhack.com]''', or '''[mailto:cammo@muhack.com cammo@muhack.com]''' — or just grab us at the Tuesday MuHack meeting.

Melchiorre (Server)

2025-05-22T15:42:34Z

Mrmoddom:

{{Service
|Service URI=cpu.muhack
|Location=Aula associazioni
|Contact email=webmaster@muhack.org
|Operational Status=Functional
|Super Users=Ceres-c, Mrmoddom, Cammo
|Owner=MuHack
|Physical Location=Aula associazioni
|URI=gpu.vpn.muhack (reachable on the MuHack Tailscale net)
|Project Status=Active
|Participants=Ceres-c, Mrmoddom, Cammo
}}
= MUHACK CPU SERVER =
A shared machine that gives all members access to personal VM/LXC for general purpose computations.

== What this box is for ==

* General computational needs

== Fast facts ==

* Host name : '''cpu.muhack''' (reachable only locally or through the MuHack Tailscale network)
* Management : Proxmox web UI @ port 8006 → [https://cpu.muhack:8006 Link]
* Sysadmins : '''Ceres-c, Mrmoddom, Cammo'''
* Contact : [mailto:webmaster@muhack.com webmaster@muhack.com] • or in person every Tuesday evening at the MuHack meeting

== Hardware ==

* CPU : 36 x Intel(R) Xeon(R) CPU E5-2696 v3 @ 2.30GHz (1 Socket)
* RAM : 64 GB ECC DDR4 @ 2400 Mhz
* GPU-A : NVIDIA GK208B [GeForce GT 710]
* Disks : SSD 256GB - 6TB Raid0 (3+3 HDD)
* NICs : Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller

== Software stack ==

* Proxmox VE 8.x (kernel 6.8)

= Getting your own environment =

# Make sure your laptop/PC is connected to the MuHack Tailscale tail-net and can <tt>ping gpu.muhack</tt>.
# Go to the [https://cpu.muhack:8006 proxmox login page] and login a first time to create your account and then logout immediately
# Talk to '''any sysadmin''' (email or in person on Tuesday). Tell us
## what you plan to run
## an estimate of how much RAM / runtime you’ll need
# We’ll create a container (or VM) for you and hand back:
## ID (e.g. <tt>ct104</tt> or <tt>vm203</tt>)
## a '''random initial password'''

''Typical turnaround time: usually same day or next-day. However might take more time if the sysadmins are busy.''
{{Note|type=warn|text=After the first login you have to re-login a second time to let proxmox setup correctly your account's group }}

At this point you have two options for interact with the console:
# Use the [https://cpu.muhack:8006 proxmox web interface]'s integrated console
# Join the machine to a tailnet (your personal or the MuHack's one) and connect trough SSH -> remember to enable ssh root access within sshd config file!

= Fair-share policy =

* Jobs longer than '''12 h''' → announce them at the Tuesday meeting or in the telegram channel.
* Sysadmins may pause/stop workloads that block others
* Crypto-mining strictly forbidden

== Good-citizen checklist ==

* If don't need to keep you VM/LXC up, shut it down for others: the resources are limited and shared!
* Keep <tt>/tmp</tt> and your home directory tidy; disk space is shared
* '''BACK UP YOUR OWN DATA: we have no data persistency or backup guarantee'''

Questions / ideas → email '''[mailto:ceres-c@muhack.com ceres-c@muhack.com]''', '''[mailto:mrmoddom@muhack.com mrmoddom@muhack.com]''', or '''[mailto:cammo@muhack.com cammo@muhack.com]''' — or just grab us at the Tuesday MuHack meeting.

Melchiorre (Server)

2025-05-22T10:54:17Z

Mrmoddom: Created CPU Server - some information missing, need more details

{{Service
|Service URI=cpu.muhack
|Location=Aula associazioni
|Contact email=webmaster@muhack.org
|Operational Status=Needs: Work
|Super Users=Ceres-c, Mrmoddom, Cammo
|Owner=MuHack
|Physical Location=Aula associazioni
|URI=gpu.vpn.muhack (reachable on the MuHack Tailscale net)
|Project Status=Active
|Participants=Ceres-c, Mrmoddom, Cammo
}}

= MUHACK CPU SERVER =
A shared machine that gives all members access to personal VM/LXC for general purpose computations.

== What this box is for ==

* General computational needs

== Fast facts ==

* Host name : '''cpu.muhack''' (reachable only locally or through the MuHack Tailscale network)
* Management : Proxmox web UI @ port 8006 → [https://cpu.muhack:8006 Link]
* Sysadmins : '''Ceres-c, Mrmoddom, Cammo'''
* Contact : [mailto:webmaster@muhack.com webmaster@muhack.com] • or in person every Tuesday evening at the MuHack meeting

== Hardware ==

* CPU : Xeon 32 Threads
* RAM :
* GPU-A :
* Disks : SSD 256GB - 6TB Raid0 (3+3 HDD)
* NICs :

== Software stack ==

* Proxmox VE 8.x (kernel 6.8)

= Getting your own environment =

# Make sure your laptop/PC is connected to the MuHack Tailscale tail-net and can <tt>ping gpu.muhack</tt>.
# Go to the [https://cpu.muhack:8006 proxmox login page] and login a first time to create your account and then logout immediately
# Talk to '''any sysadmin''' (email or in person on Tuesday). Tell us
## what you plan to run
## an estimate of how much RAM / runtime you’ll need
# We’ll create a container (or VM) for you and hand back:
## ID (e.g. <tt>ct104</tt> or <tt>vm203</tt>)
## a '''random initial password'''

''Typical turnaround time: usually same day or next-day. However might take more time if the sysadmins are busy.''
{{Note|type=warn|text=After the first login you have to re-login a second time to let proxmox setup correctly your account's group }}

At this point you have two options for interact with the console:
# Use the [https://cpu.muhack:8006 proxmox web interface]'s integrated console
# Join the machine to a tailnet (your personal or the MuHack's one) and connect trough SSH -> remember to enable ssh root access within sshd config file!

= Fair-share policy =

* Jobs longer than '''12 h''' → announce them at the Tuesday meeting or in the telegram channel.
* Sysadmins may pause/stop workloads that block others
* Crypto-mining strictly forbidden

== Good-citizen checklist ==

* If don't need to keep you VM/LXC up, shut it down for others: the resources are limited and shared!
* Keep <tt>/tmp</tt> and your home directory tidy; disk space is shared
* '''BACK UP YOUR OWN DATA: we have no data persistency or backup guarantee'''

Questions / ideas → email '''[mailto:ceres-c@muhack.com ceres-c@muhack.com]''', '''[mailto:mrmoddom@muhack.com mrmoddom@muhack.com]''', or '''[mailto:cammo@muhack.com cammo@muhack.com]''' — or just grab us at the Tuesday MuHack meeting.

Whitepages

2025-05-22T10:43:50Z

Mrmoddom: Created Whitepages

= MuHack Services Index =
Welcome to the MuHack internal services directory. Below is a list of all the currently available tools, services, and internal resources for members.

== Communication ==
* Telegram Channel - https://t.me/muhack - Public announcements
* 🧑‍🤝‍🧑 Telegram Group - Chat and coordination.
* 🧑‍🤝‍🧑 Discord - Discord Server for chatting, hacking, gaming together

== Hosting / Infrastructure ==
* Website - https://muhack.org - Public-facing site.
* MuHack Wiki - https://wiki.muhack.org/ - This wiki.
* 🔒 VPS - Coordinator server with services
* 🔒 [[GPU Server]] - http://gpu.muhack:8006/ - Proxmox server with GPU
* 🔒 [[CPU Server]] - http://cpu.muhack:8006/ - Proxmox server for general purpose VM/LXC

== Services ==
* 🔒 Ollama - http://ollama.muhack/ - Ollama instance for running LLM
* 🔒 Open WebUI - http://open-webui.muhack:8080 - Open WebUI for interacting with LLM in a graphical interface

== Development ==

== Access Control ==
* 🧑‍🤝‍🧑 Google Workspace - Every member has access to some of the GW's application, such as GMail and GDrive
* 🧑‍🤝‍🧑 VPN Access - Secure remote access to Tailscale network.

== Monitoring ==

== Internal Tools ==
* 🔒 KnoledBase - https://kb.muhack.org/ - Repository for the internal know-how
* 🧑‍🤝‍🧑 Vikunja - https://todo.muhack.org/ - Todo list for tasks
* 🧑‍🤝‍🧑 VaultWarden - https://vault.muhack.org/ - Web Passwords Manager

== Notes ==
* Services marked with 🔒 require VPN access or local/special requirements.
* Services marked with 🧑‍🤝‍🧑 require an active member subscription.

{{Note|type=info|text=For questions → email ceres-c@muhack.com, mrmoddom@muhack.com, or cammo@muhack.com - or just meet us at the Tuesday MuHack meeting :) }}

Tailscale VPN

2025-05-18T08:52:39Z

Mrmoddom: /* Access */ Updated the tailscale instruction with a LXC container

= Accessing Internal Services via Tailscale =

Many of our non-public services, those hosted on servers physically located in the ''Aula Associazioni'', are only accessible from within our VPN.

== VPN Access via Tailscale ==

We use [https://tailscale.com/ Tailscale] to manage our internal VPN. Tailscale is a mesh VPN that simplifies access to our local infrastructure.

=== Headscale Deployment ===

We run a self-hosted [https://github.com/juanfont/headscale Headscale] instance, which serves as the coordination server for our Tailscale network. You will need to authenticate through it in order to join the VPN.

=== Important Notes ===
# This VPN does not provide an exit node: your external IP address will remain unchanged.
# The VPN only allows access to internal services—we do not route general internet traffic through it.
# Once connected, you'll be able to reach services hosted in the ''Aula Associazioni'' using their Tailscale IPs or hostnames thanks to the [https://tailscale.com/kb/1081/magicdns MagicDNS]. On each [[:Category:Services|service]] page, the [[Property:Service URI]] (and port, if necessary) should be available in the infobox on the right side.

== Access ==
# Follow the Tailscale client [https://tailscale.com/kb/1347/installation install guide] for your operating system.
# Use the following command to login our tailnet
<syntaxhighlight lang="bash">
tailscale login --login-server=https://vpn.muhack.org
</syntaxhighlight>
Then open the link you'll get in the terminal, and log in with your [[MuHack Account|MuHack workspace account]]

Note: this also works with the mobile app

{{Note|text=On MacOS
<syntaxhighlight lang="bash">
brew install tailscale
tailscale login --login-server=https://vpn.muhack.org
</syntaxhighlight>
}}

{{Note|text=On LXC Container
if you're trying to run tailscale on you LXC Container on one of our servers, you need to run the daemon in [https://tailscale.com/kb/1112/userspace-networking userspace-networking mode]

# Modify the tailscale daemon config file and add <code>--tun=userspace-networking‎</code> and the end of line starting with "ExecStart" and save the file
# Reload the daemon service file with <code>systemctl daemon-reload</code>
# Restart the Tailscaled service with <code>systemctl restart tailscaled.service</code>
# Login to MuHack's network with <code>tailscale login --login-server=https://vpn.muhack.org</code> or your personal network with just <code>tailscale up</code>
}}

Index

2025-05-14T14:51:13Z

Mrmoddom: /* MuHack's index */

= MuHack's index =

In this page are listed with no particular order, the services and stuff currently active in our hackerspace. Some of them require access to our tailnet

{| class="wikitable"
! Name
! Description
! Link
|-
| Todo's
| An instance of [https://vikunja.io/ Vikunja] to keep track of all the task and assignments
| [https://todo.muack.org/ https://todo.muack.org/]
|-
| Wiki
| This very wiki you are reading from :D
| [https://wiki.muack.org/ https://wiki.muack.org/]
|-
| Google's Workspace
| Every user has access to the App within the Google Workspace
| [https://accounts.google.com/ https://accounts.google.com/]
|-
| GPU Server
| [[GPU Server|Our self-hosted GPU server]] based on Proxmox
| [http://gpu.muhack http://gpu.muhack] (tailnet)
|}

Index

2025-05-14T14:50:57Z

Mrmoddom: Created page with "= MuHack's index = In this page are listed with no particular order, the services and stuff currently active in our hackerspace. Some of them require access to our tailnet {| class="wikitable" ! Name ! Description ! Link |- | Todo's | An instance of [https://vikunja.io/ Vikunja] to keep track of all the task and assignments | [https://todo.muack.org/ https://todo.muack.org/] |- | Wiki | This very wiki you are reading from :D | [https://wiki.muack.org/ https://wiki.mua..."

Tailscale VPN

2025-05-14T13:59:04Z

Mrmoddom: /* Access */

= Accessing Internal Services via Tailscale =

Many of our non-public services, those hosted on servers physically located in the ''Aula Associazioni'', are only accessible from within our VPN.

== VPN Access via Tailscale ==

We use [https://tailscale.com/ Tailscale] to manage our internal VPN. Tailscale is a mesh VPN that simplifies access to our local infrastructure.

=== Headscale Deployment ===

We run a self-hosted [https://github.com/juanfont/headscale Headscale] instance, which serves as the coordination server for our Tailscale network. You will need to authenticate through it in order to join the VPN.

=== Important Notes ===
# This VPN does not provide an exit node: your external IP address will remain unchanged.
# The VPN only allows access to internal services—we do not route general internet traffic through it.
# Once connected, you'll be able to reach services hosted in the ''Aula Associazioni'' using their Tailscale IPs or hostnames thanks to the [https://tailscale.com/kb/1081/magicdns MagicDNS]. On each [[:Category:Services|service]] page, the [[Property:Service URI]] (and port, if necessary) should be available in the infobox on the right side.

== Access ==
# Follow the Tailscale client [https://tailscale.com/kb/1347/installation install guide] for your operating system.
# Use the following command to login our tailnet
<syntaxhighlight lang="bash">
tailscale login --login-server=https://vpn.muhack.org
</syntaxhighlight>
Then open the link you'll get in the terminal, and log in with your [[MuHack Account|MuHack workspace account]]

Note: this also works with the mobile app

{{Note|text=On MacOS
<syntaxhighlight lang="bash">
brew install tailscale
tailscale login --login-server=https://vpn.muhack.org
</syntaxhighlight>
}}

{{Note|text=On LXC Container
if you're trying to run tailscale on you LXC Container on one of our servers, you need to run the daemon in [https://tailscale.com/kb/1112/userspace-networking userspace-networking mode]
<syntaxhighlight lang="bash">
tailscaled --tun=userspace-networking
tailscale login --login-server=https://vpn.muhack.org
</syntaxhighlight>
}}

Gaspare (Server)

2025-05-14T13:54:08Z

Mrmoddom: /* MUHACK GPU SERVER */

{{Service
|Service URI=gpu.muhack
|Location=Aula associazioni
|Contact email=webmaster@muhack.org
|Operational Status=Working
|Super Users=Ceres-c, Mrmoddom, Cammo
|Owner=MuHack
|Physical Location=Aula associazioni
|URI=gpu.vpn.muhack (reachable on the MuHack Tailscale net)
|Project Status=Active
|Participants=Ceres-c, Mrmoddom, Cammo
}}
= MUHACK GPU SERVER =
A shared machine that gives all members access to serious GPU horsepower for AI/ML, rendering, data-science and other compute-intensive experiments.

== What this box is for ==

* Training / fine-tuning neural networks
* CUDA / OpenCL development and compilation
* 3-D rendering, video encoding or scientific workloads
* General “I-need-48-GB-of-VRAM” tinkering

The host runs Proxmox VE, so we can either
# carve the GPU into vGPU slices for VMs, or
# passthrough the full card to Debian 12 LXC containers.

== Fast facts ==

* Host name : '''gpu.muhack''' (reachable only locally or through the MuHack Tailscale network)
* Management : Proxmox web UI @ port 8006 → [https://gpu.muhack:8006 Link]
* Sysadmins : '''Ceres-c, Mrmoddom, Cammo'''
* Contact : [mailto:webmaster@muhack.com webmaster@muhack.com] • or in person every Tuesday evening at the MuHack meeting

== Hardware ==

* CPU : Intel Core i7-4930K — 6 cores / 12 threads @ 3.40 GHz (3.90 GHz Turbo)
* RAM : 64 GB DDR3-1866
* GPU-A : NVIDIA Quadro RTX 8000 — 48 GB GDDR6 (compute card)
* GPU-B : NVIDIA GeForce GT 710 — emergency host console only
* Disk : 1 TB PNY SATA SSD + additional SATA ports free for expansion
* NICs :
** Intel 82574L Gigabit
** Intel 82579V Gigabit

== Software stack ==

* Proxmox VE 8.x (kernel 6.8)
* “Merged” NVIDIA driver 550.90.07 (both vGPU and passthrough available)

'''Pre-built images'''
* Debian 12 LXC (default; CUDA-ready; shared GPU)
* Ubuntu 22.04 / Windows VM (on request, with dedicated vGPU slice, only for specific necessities)

= Getting your own environment =

# Make sure your laptop/PC is connected to the MuHack Tailscale tail-net and can <tt>ping gpu.muhack</tt>.
# Go to the [https://gpu.muhack:8006 proxmox login page] and login a first time to create your account and then logout immediately
# Talk to '''any sysadmin''' (email or in person on Tuesday). Tell us
## what you plan to run (ML, rendering, etc.)
## an estimate of how much GPU RAM / runtime you’ll need
# We’ll create a container (or VM) for you and hand back:
## ID (e.g. <tt>ct104</tt> or <tt>vm203</tt>)
## a '''random initial password'''

''Typical turnaround time: usually same day or next-day. However might take more time if the sysadmins are busy.''
{{Note|type=warn|text=After the first login you have to re-login a second time to let proxmox setup correctly your account's group }}

At this point you have two options for interact with the console:
# Use the [https://gpu.muhack:8006 proxmox web interface]'s integrated console
# Join the machine to a tailnet (your personal or the MuHack's one) and connect trough SSH -> remember to enable ssh root access within sshd config file!

== Using your Debian 12 LXC ==

Need CUDA toolkit? Run the following script:
<syntaxhighlight lang="bash">
#!/bin/bash
wget https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64/cuda-keyring_1.1-1_all.deb
apt install -y ./cuda-keyring_1.1-1_all.deb
apt update
rm cuda-keyring_1.1-1_all.deb
apt install -y cuda-toolkit-12-4

echo "export PATH=\${PATH}:/usr/local/cuda/bin" >> ~/.bashrc
echo "export LD_LIBRARY_PATH=\${LD_LIBRARY_PATH}:/usr/local/cuda/lib64" >> ~/.bashrc
</syntaxhighlight>

After running the script, apply the environment changes by sourcing your `.bashrc`:

<syntaxhighlight lang="bash">
source ~/.bashrc
</syntaxhighlight>

You’ll get CUDA toolkit 12.4 that matches the host driver.

= Fair-share policy =

* Jobs longer than '''12 h''' → announce them at the Tuesday meeting or in the telegram channel.
* Sysadmins may pause/stop workloads that block others
* Crypto-mining strictly forbidden

== Good-citizen checklist ==

* Before logging out, run <tt>watch -n60 nvidia-smi</tt> and confirm your process is gone and is not hogging the gpu.
* Keep <tt>/tmp</tt> and your home directory tidy; disk space is shared
* '''BACK UP YOUR OWN DATA: we have no data persistency or backup guarantee'''

= Extras =

* vGPU-enabled Windows or Ubuntu VMs — ask if needed
* Docker-inside-LXC supported (nesting + cgroupv2 enabled)

== Troubleshooting quick-ref ==

{| class="wikitable"
! Problem
! Fix
|-
| <tt>nvidia-smi</tt> shows no devices
| Container lost its GPU mapping—tell a sysadmin
|-
| Driver mismatch error
| Host driver was updated—reinstall matching userspace driver with <tt>--no-kernel-modules</tt>—tell a sysadmin
|-
| Out-of-memory in PyTorch
| If using a VM: request a larger vGPU slice. If using a container: someone else might be using some GPU memory. Check with <tt>nvidia-smi</tt> (gui for that coming up sometime kinda soon).
|}

Questions / ideas → email '''[mailto:ceres-c@muhack.com ceres-c@muhack.com]''', '''[mailto:mrmoddom@muhack.com mrmoddom@muhack.com]''', or '''[mailto:cammo@muhack.com cammo@muhack.com]''' — or just grab us at the Tuesday MuHack meeting.

Gaspare (Server)

2025-05-14T13:47:46Z

Mrmoddom: /* Getting your own environment */

{{Service
|Service URI=gpu.muhack
|Location=Aula associazioni
|Contact email=webmaster@muhack.org
|Operational Status=Working
|Super Users=Ceres-c, Mrmoddom, Cammo
|Owner=MuHack
|Physical Location=Aula associazioni
|URI=gpu.vpn.muhack (reachable on the MuHack Tailscale net)
|Project Status=Active
|Participants=Ceres-c, Mrmoddom, Cammo
}}
= MUHACK GPU SERVER =
A shared machine that gives all members access to serious GPU horsepower for AI/ML, rendering, data-science and other compute-intensive experiments.

== What this box is for ==

* Training / fine-tuning neural networks
* CUDA / OpenCL development and compilation
* 3-D rendering, video encoding or scientific workloads
* General “I-need-48-GB-of-VRAM” tinkering

The host runs Proxmox VE, so we can either
# carve the GPU into vGPU slices for VMs, or
# passthrough the full card to Debian 12 LXC containers.

== Fast facts ==

* Host name : '''gpu.muhack''' (reachable only locally or through the MuHack Tailscale network)
* Management : Proxmox web UI @ port 8006 → [https://gpu.muhack:8006 Link]
* Sysadmins : '''Ceres-c, Mrmoddom, Cammo'''
* Contact : [mailto:webmaster@muhack.com webmaster@muhack.com] • or in person every Tuesday evening at the MuHack meeting

== Hardware ==

* CPU : Intel Core i7-4930K — 6 cores / 12 threads @ 3.40 GHz (3.90 GHz Turbo)
* RAM : 64 GB DDR3-1866
* GPU-A : NVIDIA Quadro RTX 8000 — 48 GB GDDR6 (compute card)
* GPU-B : NVIDIA GeForce GT 710 — emergency host console only
* Disk : 1 TB PNY SATA SSD + additional SATA ports free for expansion
* NICs :
** Intel 82574L Gigabit
** Intel 82579V Gigabit

== Software stack ==

* Proxmox VE 8.x (kernel 6.8)
* “Merged” NVIDIA driver 550.90.07 (both vGPU and passthrough available)

'''Pre-built images'''
* Debian 12 LXC (default; CUDA-ready; shared GPU)
* Ubuntu 22.04 / Windows VM (on request, with dedicated vGPU slice, only for specific necessities)

== Getting your own environment ==

# Make sure your laptop/PC is connected to the MuHack Tailscale tail-net and can <tt>ping gpu.muhack</tt>.
# Go to the [https://gpu.muhack:8006 proxmox login page] and login a first time to create your account and then logout immediately
# Talk to '''any sysadmin''' (email or in person on Tuesday). Tell us
## what you plan to run (ML, rendering, etc.)
## an estimate of how much GPU RAM / runtime you’ll need
# We’ll create a container (or VM) for you and hand back:
## ID (e.g. <tt>ct104</tt> or <tt>vm203</tt>)
## a '''random initial password'''

''Typical turnaround time: usually same day or next-day. However might take more time if the sysadmins are busy.''
{{Note|type=warn|text=After the first login you have to re-login a second time to let proxmox setup correctly your account's group }}

At this point you have two options for interact with the console:
# Use the [https://gpu.muhack:8006 proxmox web interface]'s integrated console
# Join the machine to a tailnet (your personal or the MuHack's one) and connect trough SSH -> remember to enable ssh root access within sshd config file!

== Using your Debian 12 LXC ==

Need CUDA toolkit? Run the following script:
<syntaxhighlight lang="bash">
#!/bin/bash
wget https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64/cuda-keyring_1.1-1_all.deb
apt install -y ./cuda-keyring_1.1-1_all.deb
apt update
rm cuda-keyring_1.1-1_all.deb
apt install -y cuda-toolkit-12-4

echo "export PATH=\${PATH}:/usr/local/cuda/bin" >> ~/.bashrc
echo "export LD_LIBRARY_PATH=\${LD_LIBRARY_PATH}:/usr/local/cuda/lib64" >> ~/.bashrc
</syntaxhighlight>

After running the script, apply the environment changes by sourcing your `.bashrc`:

<syntaxhighlight lang="bash">
source ~/.bashrc
</syntaxhighlight>

You’ll get CUDA toolkit 12.4 that matches the host driver.

== Fair-share policy ==

* Jobs longer than '''12 h''' → announce them at the Tuesday meeting or in the telegram channel.
* Sysadmins may pause/stop workloads that block others
* Crypto-mining strictly forbidden

== Good-citizen checklist ==

* Before logging out, run <tt>watch -n60 nvidia-smi</tt> and confirm your process is gone and is not hogging the gpu.
* Keep <tt>/tmp</tt> and your home directory tidy; disk space is shared
* '''BACK UP YOUR OWN DATA: we have no data persistency or backup guarantee'''

== Extras ==

* vGPU-enabled Windows or Ubuntu VMs — ask if needed
* Docker-inside-LXC supported (nesting + cgroupv2 enabled)

== Troubleshooting quick-ref ==

{| class="wikitable"
! Problem
! Fix
|-
| <tt>nvidia-smi</tt> shows no devices
| Container lost its GPU mapping—tell a sysadmin
|-
| Driver mismatch error
| Host driver was updated—reinstall matching userspace driver with <tt>--no-kernel-modules</tt>—tell a sysadmin
|-
| Out-of-memory in PyTorch
| If using a VM: request a larger vGPU slice. If using a container: someone else might be using some GPU memory. Check with <tt>nvidia-smi</tt> (gui for that coming up sometime kinda soon).
|}

Questions / ideas → email '''[mailto:ceres-c@muhack.com ceres-c@muhack.com]''', '''[mailto:mrmoddom@muhack.com mrmoddom@muhack.com]''', or '''[mailto:cammo@muhack.com cammo@muhack.com]''' — or just grab us at the Tuesday MuHack meeting.

Gaspare (Server)

2025-05-14T13:44:41Z

Mrmoddom: /* Getting your own environment */

{{Service
|Service URI=gpu.muhack
|Location=Aula associazioni
|Contact email=webmaster@muhack.org
|Operational Status=Working
|Super Users=Ceres-c, Mrmoddom, Cammo
|Owner=MuHack
|Physical Location=Aula associazioni
|URI=gpu.vpn.muhack (reachable on the MuHack Tailscale net)
|Project Status=Active
|Participants=Ceres-c, Mrmoddom, Cammo
}}
= MUHACK GPU SERVER =
A shared machine that gives all members access to serious GPU horsepower for AI/ML, rendering, data-science and other compute-intensive experiments.

== What this box is for ==

* Training / fine-tuning neural networks
* CUDA / OpenCL development and compilation
* 3-D rendering, video encoding or scientific workloads
* General “I-need-48-GB-of-VRAM” tinkering

The host runs Proxmox VE, so we can either
# carve the GPU into vGPU slices for VMs, or
# passthrough the full card to Debian 12 LXC containers.

== Fast facts ==

* Host name : '''gpu.muhack''' (reachable only locally or through the MuHack Tailscale network)
* Management : Proxmox web UI @ port 8006 → [https://gpu.muhack:8006 Link]
* Sysadmins : '''Ceres-c, Mrmoddom, Cammo'''
* Contact : [mailto:webmaster@muhack.com webmaster@muhack.com] • or in person every Tuesday evening at the MuHack meeting

== Hardware ==

* CPU : Intel Core i7-4930K — 6 cores / 12 threads @ 3.40 GHz (3.90 GHz Turbo)
* RAM : 64 GB DDR3-1866
* GPU-A : NVIDIA Quadro RTX 8000 — 48 GB GDDR6 (compute card)
* GPU-B : NVIDIA GeForce GT 710 — emergency host console only
* Disk : 1 TB PNY SATA SSD + additional SATA ports free for expansion
* NICs :
** Intel 82574L Gigabit
** Intel 82579V Gigabit

== Software stack ==

* Proxmox VE 8.x (kernel 6.8)
* “Merged” NVIDIA driver 550.90.07 (both vGPU and passthrough available)

'''Pre-built images'''
* Debian 12 LXC (default; CUDA-ready; shared GPU)
* Ubuntu 22.04 / Windows VM (on request, with dedicated vGPU slice, only for specific necessities)

== Getting your own environment ==

# Make sure your laptop/PC is connected to the MuHack Tailscale tail-net and can <tt>ping gpu.muhack</tt>.
# Talk to '''any sysadmin''' (email or in person on Tuesday). Tell us
## what you plan to run (ML, rendering, etc.)
## an estimate of how much GPU RAM / runtime you’ll need
# We’ll create a container (or VM) for you and hand back:
## ID (e.g. <tt>ct104</tt> or <tt>vm203</tt>)
## a '''random initial password'''

''Typical turnaround time: usually same day or next-day. However might take more time if the sysadmins are busy.''
{{Note|type=warn|text=After the first login you have to re-login a second time to let proxmox setup correctly your account's group }}

At this point you have two options for interact with the console:
# Use the [https://gpu.muhack:8006 proxmox web interface]'s integrated console
# Join the machine to a tailnet (your personal or the MuHack's one) and connect trough SSH -> remember to enable ssh root access within sshd config file!

== Using your Debian 12 LXC ==

Need CUDA toolkit? Run the following script:
<syntaxhighlight lang="bash">
#!/bin/bash
wget https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64/cuda-keyring_1.1-1_all.deb
apt install -y ./cuda-keyring_1.1-1_all.deb
apt update
rm cuda-keyring_1.1-1_all.deb
apt install -y cuda-toolkit-12-4

echo "export PATH=\${PATH}:/usr/local/cuda/bin" >> ~/.bashrc
echo "export LD_LIBRARY_PATH=\${LD_LIBRARY_PATH}:/usr/local/cuda/lib64" >> ~/.bashrc
</syntaxhighlight>

After running the script, apply the environment changes by sourcing your `.bashrc`:

<syntaxhighlight lang="bash">
source ~/.bashrc
</syntaxhighlight>

You’ll get CUDA toolkit 12.4 that matches the host driver.

== Fair-share policy ==

* Jobs longer than '''12 h''' → announce them at the Tuesday meeting or in the telegram channel.
* Sysadmins may pause/stop workloads that block others
* Crypto-mining strictly forbidden

== Good-citizen checklist ==

* Before logging out, run <tt>watch -n60 nvidia-smi</tt> and confirm your process is gone and is not hogging the gpu.
* Keep <tt>/tmp</tt> and your home directory tidy; disk space is shared
* '''BACK UP YOUR OWN DATA: we have no data persistency or backup guarantee'''

== Extras ==

* vGPU-enabled Windows or Ubuntu VMs — ask if needed
* Docker-inside-LXC supported (nesting + cgroupv2 enabled)

== Troubleshooting quick-ref ==

{| class="wikitable"
! Problem
! Fix
|-
| <tt>nvidia-smi</tt> shows no devices
| Container lost its GPU mapping—tell a sysadmin
|-
| Driver mismatch error
| Host driver was updated—reinstall matching userspace driver with <tt>--no-kernel-modules</tt>—tell a sysadmin
|-
| Out-of-memory in PyTorch
| If using a VM: request a larger vGPU slice. If using a container: someone else might be using some GPU memory. Check with <tt>nvidia-smi</tt> (gui for that coming up sometime kinda soon).
|}

Questions / ideas → email '''[mailto:ceres-c@muhack.com ceres-c@muhack.com]''', '''[mailto:mrmoddom@muhack.com mrmoddom@muhack.com]''', or '''[mailto:cammo@muhack.com cammo@muhack.com]''' — or just grab us at the Tuesday MuHack meeting.

Gaspare (Server)

2025-05-14T13:38:40Z

Mrmoddom: /* Getting your own environment */

{{Service
|Service URI=gpu.muhack
|Location=Aula associazioni
|Contact email=webmaster@muhack.org
|Operational Status=Working
|Super Users=Ceres-c, Mrmoddom, Cammo
|Owner=MuHack
|Physical Location=Aula associazioni
|URI=gpu.vpn.muhack (reachable on the MuHack Tailscale net)
|Project Status=Active
|Participants=Ceres-c, Mrmoddom, Cammo
}}
= MUHACK GPU SERVER =
A shared machine that gives all members access to serious GPU horsepower for AI/ML, rendering, data-science and other compute-intensive experiments.

== What this box is for ==

* Training / fine-tuning neural networks
* CUDA / OpenCL development and compilation
* 3-D rendering, video encoding or scientific workloads
* General “I-need-48-GB-of-VRAM” tinkering

The host runs Proxmox VE, so we can either
# carve the GPU into vGPU slices for VMs, or
# passthrough the full card to Debian 12 LXC containers.

== Fast facts ==

* Host name : '''gpu.muhack''' (reachable only locally or through the MuHack Tailscale network)
* Management : Proxmox web UI @ port 8006 → [https://gpu.muhack:8006 Link]
* Sysadmins : '''Ceres-c, Mrmoddom, Cammo'''
* Contact : [mailto:webmaster@muhack.com webmaster@muhack.com] • or in person every Tuesday evening at the MuHack meeting

== Hardware ==

* CPU : Intel Core i7-4930K — 6 cores / 12 threads @ 3.40 GHz (3.90 GHz Turbo)
* RAM : 64 GB DDR3-1866
* GPU-A : NVIDIA Quadro RTX 8000 — 48 GB GDDR6 (compute card)
* GPU-B : NVIDIA GeForce GT 710 — emergency host console only
* Disk : 1 TB PNY SATA SSD + additional SATA ports free for expansion
* NICs :
** Intel 82574L Gigabit
** Intel 82579V Gigabit

== Software stack ==

* Proxmox VE 8.x (kernel 6.8)
* “Merged” NVIDIA driver 550.90.07 (both vGPU and passthrough available)

'''Pre-built images'''
* Debian 12 LXC (default; CUDA-ready; shared GPU)
* Ubuntu 22.04 / Windows VM (on request, with dedicated vGPU slice, only for specific necessities)

== Getting your own environment ==

# Make sure your laptop/PC is connected to the MuHack Tailscale tail-net and can <tt>ping gpu.muhack</tt>.
# Talk to '''any sysadmin''' (email or in person on Tuesday). Tell us
## what you plan to run (ML, rendering, etc.)
## an estimate of how much GPU RAM / runtime you’ll need
# We’ll create a container (or VM) for you and hand back:
## ID (e.g. <tt>ct104</tt> or <tt>vm203</tt>)
## a '''random initial password'''

''Typical turnaround time: usually same day or next-day. However might take more time if the sysadmins are busy.''
{{Note|type=warn|text=After the first login you have to re-login a second time to let proxmox setup correctly your account's group }}

== Using your Debian 12 LXC ==

Need CUDA toolkit? Run the following script:
<syntaxhighlight lang="bash">
#!/bin/bash
wget https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64/cuda-keyring_1.1-1_all.deb
apt install -y ./cuda-keyring_1.1-1_all.deb
apt update
rm cuda-keyring_1.1-1_all.deb
apt install -y cuda-toolkit-12-4

echo "export PATH=\${PATH}:/usr/local/cuda/bin" >> ~/.bashrc
echo "export LD_LIBRARY_PATH=\${LD_LIBRARY_PATH}:/usr/local/cuda/lib64" >> ~/.bashrc
</syntaxhighlight>

After running the script, apply the environment changes by sourcing your `.bashrc`:

<syntaxhighlight lang="bash">
source ~/.bashrc
</syntaxhighlight>

You’ll get CUDA toolkit 12.4 that matches the host driver.

== Fair-share policy ==

* Jobs longer than '''12 h''' → announce them at the Tuesday meeting or in the telegram channel.
* Sysadmins may pause/stop workloads that block others
* Crypto-mining strictly forbidden

== Good-citizen checklist ==

* Before logging out, run <tt>watch -n60 nvidia-smi</tt> and confirm your process is gone and is not hogging the gpu.
* Keep <tt>/tmp</tt> and your home directory tidy; disk space is shared
* '''BACK UP YOUR OWN DATA: we have no data persistency or backup guarantee'''

== Extras ==

* vGPU-enabled Windows or Ubuntu VMs — ask if needed
* Docker-inside-LXC supported (nesting + cgroupv2 enabled)

== Troubleshooting quick-ref ==

{| class="wikitable"
! Problem
! Fix
|-
| <tt>nvidia-smi</tt> shows no devices
| Container lost its GPU mapping—tell a sysadmin
|-
| Driver mismatch error
| Host driver was updated—reinstall matching userspace driver with <tt>--no-kernel-modules</tt>—tell a sysadmin
|-
| Out-of-memory in PyTorch
| If using a VM: request a larger vGPU slice. If using a container: someone else might be using some GPU memory. Check with <tt>nvidia-smi</tt> (gui for that coming up sometime kinda soon).
|}

Questions / ideas → email '''[mailto:ceres-c@muhack.com ceres-c@muhack.com]''', '''[mailto:mrmoddom@muhack.com mrmoddom@muhack.com]''', or '''[mailto:cammo@muhack.com cammo@muhack.com]''' — or just grab us at the Tuesday MuHack meeting.

Main Page

2025-05-14T13:23:53Z

Mrmoddom: /* What we do */

__NOTOC__
= Welcome to the MuHack's Wiki =

{| border="2" cellspacing="0" cellpadding="4" rules="all" style="float:right; clear:right; width:370px; width: 20%; max-width: 370px; margin:5px 0 1em 1em; border-collapse:collapse; font-size:95%; empty-cells:hide;"
|- style="background: {{Style|header}}; text-align:center;"
! colspan=2| ''New and updated projects''
{{#ask:
[[Category:Projects]]
|?Project Last Update
|sort=Project Last Update
|order=descending
|limit=10
|format=template
|template=NewProjectsTableRow
|headers=plain
}}
|}

'''MuHack''' is the first hackerspace in '''Brescia''', created to promote open-source culture through the sharing of ideas, resources, and experiences.
We are a non-profit association open to anyone passionate about technology, electronics, computing, and free culture.

== Who we are ==
MuHack is a place where anyone — regardless of experience level — can meet, learn, experiment, and collaborate.
We organize courses, talks, workshops, group projects, and more, all aimed at spreading knowledge and a passion for open technologies.

== What we do ==
Start from the [[:Category:Projects|Projects]] page to see which projects are currently active, or browse trough the [[:Category:Machines|Machines]] to see what we offer to our members.

We also have some self-hosted [[:Category:Services|Services]] that can be used.

== Where and when to find us ==
We meet every '''Tuesday from 18:00 to 23:45''' at the '''Associations Room of the University Campus''' located at '''Via Valotti 3, Mompiano, Brescia'''.
For more details on how to reach us, visit our [https://muhack.org/about/ About] page.

== Join us ==
If you'd like to become a member, please read our charter and fill out the registration form available [https://muhack.org/about/ here].

== Contact ==
* '''Email''': [mailto:info@muhack.org info@muhack.org]
* '''Website''': [https://muhack.org https://muhack.org]
* '''GitHub''': [https://github.com/muhack https://github.com/muhack]
* '''YouTube''': [https://www.youtube.com/c/MuhackOrgIT MuHack Channel]
* '''Facebook''': [https://www.facebook.com/muhackIT MuHack IT]
* '''Instagram''': [https://www.instagram.com/hackerspace_muhack/ @hackerspace_muhack]
* '''Telegram''': [https://t.me/muhack t.me/muhack]

Feel free to contribute pages about projects, how-to guides, technical documentation, or event summaries.
Let's build shared knowledge together as a community.

----

Gaspare (Server)

2025-05-13T19:49:14Z

Mrmoddom: /* Fast facts */

{{Service
|Service URI=gpu.muhack
|Location=Aula associazioni
|Contact email=webmaster@muhack.org
|Operational Status=Working
|Super Users=Ceres-c, Mrmoddom, Cammo
|Owner=MuHack
|Physical Location=Aula associazioni
|URI=gpu.vpn.muhack (reachable on the MuHack Tailscale net)
|Project Status=Active
|Participants=Ceres-c, Mrmoddom, Cammo
}}
= MUHACK GPU SERVER =
A shared machine that gives all members access to serious GPU horsepower for AI/ML, rendering, data-science and other compute-intensive experiments.

== What this box is for ==

* Training / fine-tuning neural networks
* CUDA / OpenCL development and compilation
* 3-D rendering, video encoding or scientific workloads
* General “I-need-48-GB-of-VRAM” tinkering

The host runs Proxmox VE, so we can either
# carve the GPU into vGPU slices for VMs, or
# passthrough the full card to Debian 12 LXC containers.

== Fast facts ==

* Host name : '''gpu.muhack''' (reachable only locally or through the MuHack Tailscale network)
* Management : Proxmox web UI @ port 8006 → [https://gpu.muhack:8006 Link]
* Sysadmins : '''Ceres-c, Mrmoddom, Cammo'''
* Contact : [mailto:webmaster@muhack.com webmaster@muhack.com] • or in person every Tuesday evening at the MuHack meeting

== Hardware ==

* CPU : Intel Core i7-4930K — 6 cores / 12 threads @ 3.40 GHz (3.90 GHz Turbo)
* RAM : 64 GB DDR3-1866
* GPU-A : NVIDIA Quadro RTX 8000 — 48 GB GDDR6 (compute card)
* GPU-B : NVIDIA GeForce GT 710 — emergency host console only
* Disk : 1 TB PNY SATA SSD + additional SATA ports free for expansion
* NICs :
** Intel 82574L Gigabit
** Intel 82579V Gigabit

== Software stack ==

* Proxmox VE 8.x (kernel 6.8)
* “Merged” NVIDIA driver 550.90.07 (both vGPU and passthrough available)

'''Pre-built images'''
* Debian 12 LXC (default; CUDA-ready; shared GPU)
* Ubuntu 22.04 / Windows VM (on request, with dedicated vGPU slice, only for specific necessities)

== Getting your own environment ==

# Make sure your laptop/PC is connected to the MuHack Tailscale tail-net and can <tt>ping gpu.vpn.muhack</tt>.
# Talk to '''any sysadmin''' (email or in person on Tuesday). Tell us
## what you plan to run (ML, rendering, etc.)
## an estimate of how much GPU RAM / runtime you’ll need
# We’ll create a container (or VM) for you and hand back:
## ID (e.g. <tt>ct104</tt> or <tt>vm203</tt>)
## a '''random initial password'''

''Typical turnaround time: usually same day or next-day. However might take more time if the sysadmins are busy.''
{{Note|type=warn|text=After the first login you have to re-login a second time to let proxmox setup correctly your account's group }}

== Using your Debian 12 LXC ==

Need CUDA toolkit? Run the helper script already placed in <tt>/root</tt>:
<syntaxhighlight lang="bash">
/root/install-cuda-toolkit.sh
source ~/.bashrc
nvcc --version
</syntaxhighlight>
You’ll get CUDA toolkit 12.4 that matches the host driver.

== Fair-share policy ==

* Jobs longer than '''12 h''' → announce them at the Tuesday meeting or in the telegram channel.
* Sysadmins may pause/stop workloads that block others
* Crypto-mining strictly forbidden

== Good-citizen checklist ==

* Before logging out, run <tt>watch -n60 nvidia-smi</tt> and confirm your process is gone and is not hogging the gpu.
* Keep <tt>/tmp</tt> and your home directory tidy; disk space is shared
* '''BACK UP YOUR OWN DATA: we have no data persistency or backup guarantee'''

== Extras ==

* vGPU-enabled Windows or Ubuntu VMs — ask if needed
* Docker-inside-LXC supported (nesting + cgroupv2 enabled)

== Troubleshooting quick-ref ==

{| class="wikitable"
! Problem
! Fix
|-
| <tt>nvidia-smi</tt> shows no devices
| Container lost its GPU mapping—tell a sysadmin
|-
| Driver mismatch error
| Host driver was updated—reinstall matching userspace driver with <tt>--no-kernel-modules</tt>—tell a sysadmin
|-
| Out-of-memory in PyTorch
| If using a VM: request a larger vGPU slice. If using a container: someone else might be using some GPU memory. Check with <tt>nvidia-smi</tt> (gui for that coming up sometime kinda soon).
|}

Questions / ideas → email '''[mailto:ceres-c@muhack.com ceres-c@muhack.com]''', '''[mailto:mrmoddom@muhack.com mrmoddom@muhack.com]''', or '''[mailto:cammo@muhack.com cammo@muhack.com]''' — or just grab us at the Tuesday MuHack meeting.

Gaspare (Server)

2025-05-13T19:48:42Z

Mrmoddom: /* Fast facts */

{{Service
|Service URI=gpu.muhack
|Location=Aula associazioni
|Contact email=webmaster@muhack.org
|Operational Status=Working
|Super Users=Ceres-c, Mrmoddom, Cammo
|Owner=MuHack
|Physical Location=Aula associazioni
|URI=gpu.vpn.muhack (reachable on the MuHack Tailscale net)
|Project Status=Active
|Participants=Ceres-c, Mrmoddom, Cammo
}}
= MUHACK GPU SERVER =
A shared machine that gives all members access to serious GPU horsepower for AI/ML, rendering, data-science and other compute-intensive experiments.

== What this box is for ==

* Training / fine-tuning neural networks
* CUDA / OpenCL development and compilation
* 3-D rendering, video encoding or scientific workloads
* General “I-need-48-GB-of-VRAM” tinkering

The host runs Proxmox VE, so we can either
# carve the GPU into vGPU slices for VMs, or
# passthrough the full card to Debian 12 LXC containers.

== Fast facts ==

* Host name : '''gpu.muhack''' (reachable only locally or through the MuHack Tailscale network)
* Management : Proxmox web UI @ port 8006 → [https://gpu.muhack:8006]
* Sysadmins : '''Ceres-c, Mrmoddom, Cammo'''
* Contact : [mailto:webmaster@muhack.com webmaster@muhack.com] • or in person every Tuesday evening at the MuHack meeting

== Hardware ==

* CPU : Intel Core i7-4930K — 6 cores / 12 threads @ 3.40 GHz (3.90 GHz Turbo)
* RAM : 64 GB DDR3-1866
* GPU-A : NVIDIA Quadro RTX 8000 — 48 GB GDDR6 (compute card)
* GPU-B : NVIDIA GeForce GT 710 — emergency host console only
* Disk : 1 TB PNY SATA SSD + additional SATA ports free for expansion
* NICs :
** Intel 82574L Gigabit
** Intel 82579V Gigabit

== Software stack ==

* Proxmox VE 8.x (kernel 6.8)
* “Merged” NVIDIA driver 550.90.07 (both vGPU and passthrough available)

'''Pre-built images'''
* Debian 12 LXC (default; CUDA-ready; shared GPU)
* Ubuntu 22.04 / Windows VM (on request, with dedicated vGPU slice, only for specific necessities)

== Getting your own environment ==

# Make sure your laptop/PC is connected to the MuHack Tailscale tail-net and can <tt>ping gpu.vpn.muhack</tt>.
# Talk to '''any sysadmin''' (email or in person on Tuesday). Tell us
## what you plan to run (ML, rendering, etc.)
## an estimate of how much GPU RAM / runtime you’ll need
# We’ll create a container (or VM) for you and hand back:
## ID (e.g. <tt>ct104</tt> or <tt>vm203</tt>)
## a '''random initial password'''

''Typical turnaround time: usually same day or next-day. However might take more time if the sysadmins are busy.''
{{Note|type=warn|text=After the first login you have to re-login a second time to let proxmox setup correctly your account's group }}

== Using your Debian 12 LXC ==

Need CUDA toolkit? Run the helper script already placed in <tt>/root</tt>:
<syntaxhighlight lang="bash">
/root/install-cuda-toolkit.sh
source ~/.bashrc
nvcc --version
</syntaxhighlight>
You’ll get CUDA toolkit 12.4 that matches the host driver.

== Fair-share policy ==

* Jobs longer than '''12 h''' → announce them at the Tuesday meeting or in the telegram channel.
* Sysadmins may pause/stop workloads that block others
* Crypto-mining strictly forbidden

== Good-citizen checklist ==

* Before logging out, run <tt>watch -n60 nvidia-smi</tt> and confirm your process is gone and is not hogging the gpu.
* Keep <tt>/tmp</tt> and your home directory tidy; disk space is shared
* '''BACK UP YOUR OWN DATA: we have no data persistency or backup guarantee'''

== Extras ==

* vGPU-enabled Windows or Ubuntu VMs — ask if needed
* Docker-inside-LXC supported (nesting + cgroupv2 enabled)

== Troubleshooting quick-ref ==

{| class="wikitable"
! Problem
! Fix
|-
| <tt>nvidia-smi</tt> shows no devices
| Container lost its GPU mapping—tell a sysadmin
|-
| Driver mismatch error
| Host driver was updated—reinstall matching userspace driver with <tt>--no-kernel-modules</tt>—tell a sysadmin
|-
| Out-of-memory in PyTorch
| If using a VM: request a larger vGPU slice. If using a container: someone else might be using some GPU memory. Check with <tt>nvidia-smi</tt> (gui for that coming up sometime kinda soon).
|}

Questions / ideas → email '''[mailto:ceres-c@muhack.com ceres-c@muhack.com]''', '''[mailto:mrmoddom@muhack.com mrmoddom@muhack.com]''', or '''[mailto:cammo@muhack.com cammo@muhack.com]''' — or just grab us at the Tuesday MuHack meeting.

Gaspare (Server)

2025-05-13T19:48:10Z

Mrmoddom: /* Getting your own environment */ - relogin workaround for user permission

{{Service
|Service URI=gpu.muhack
|Location=Aula associazioni
|Contact email=webmaster@muhack.org
|Operational Status=Working
|Super Users=Ceres-c, Mrmoddom, Cammo
|Owner=MuHack
|Physical Location=Aula associazioni
|URI=gpu.vpn.muhack (reachable on the MuHack Tailscale net)
|Project Status=Active
|Participants=Ceres-c, Mrmoddom, Cammo
}}
= MUHACK GPU SERVER =
A shared machine that gives all members access to serious GPU horsepower for AI/ML, rendering, data-science and other compute-intensive experiments.

== What this box is for ==

* Training / fine-tuning neural networks
* CUDA / OpenCL development and compilation
* 3-D rendering, video encoding or scientific workloads
* General “I-need-48-GB-of-VRAM” tinkering

The host runs Proxmox VE, so we can either
# carve the GPU into vGPU slices for VMs, or
# passthrough the full card to Debian 12 LXC containers.

== Fast facts ==

* Host name : '''gpu.muhack''' (reachable only locally or through the MuHack Tailscale network)
* Management : Proxmox web UI @ port 8006 → [https://gpu.vpn.muhack:8006]
* Sysadmins : '''Ceres-c, Mrmoddom, Cammo'''
* Contact : [mailto:webmaster@muhack.com webmaster@muhack.com] • or in person every Tuesday evening at the MuHack meeting

== Hardware ==

* CPU : Intel Core i7-4930K — 6 cores / 12 threads @ 3.40 GHz (3.90 GHz Turbo)
* RAM : 64 GB DDR3-1866
* GPU-A : NVIDIA Quadro RTX 8000 — 48 GB GDDR6 (compute card)
* GPU-B : NVIDIA GeForce GT 710 — emergency host console only
* Disk : 1 TB PNY SATA SSD + additional SATA ports free for expansion
* NICs :
** Intel 82574L Gigabit
** Intel 82579V Gigabit

== Software stack ==

* Proxmox VE 8.x (kernel 6.8)
* “Merged” NVIDIA driver 550.90.07 (both vGPU and passthrough available)

'''Pre-built images'''
* Debian 12 LXC (default; CUDA-ready; shared GPU)
* Ubuntu 22.04 / Windows VM (on request, with dedicated vGPU slice, only for specific necessities)

== Getting your own environment ==

# Make sure your laptop/PC is connected to the MuHack Tailscale tail-net and can <tt>ping gpu.vpn.muhack</tt>.
# Talk to '''any sysadmin''' (email or in person on Tuesday). Tell us
## what you plan to run (ML, rendering, etc.)
## an estimate of how much GPU RAM / runtime you’ll need
# We’ll create a container (or VM) for you and hand back:
## ID (e.g. <tt>ct104</tt> or <tt>vm203</tt>)
## a '''random initial password'''

''Typical turnaround time: usually same day or next-day. However might take more time if the sysadmins are busy.''
{{Note|type=warn|text=After the first login you have to re-login a second time to let proxmox setup correctly your account's group }}

== Using your Debian 12 LXC ==

Need CUDA toolkit? Run the helper script already placed in <tt>/root</tt>:
<syntaxhighlight lang="bash">
/root/install-cuda-toolkit.sh
source ~/.bashrc
nvcc --version
</syntaxhighlight>
You’ll get CUDA toolkit 12.4 that matches the host driver.

== Fair-share policy ==

* Jobs longer than '''12 h''' → announce them at the Tuesday meeting or in the telegram channel.
* Sysadmins may pause/stop workloads that block others
* Crypto-mining strictly forbidden

== Good-citizen checklist ==

* Before logging out, run <tt>watch -n60 nvidia-smi</tt> and confirm your process is gone and is not hogging the gpu.
* Keep <tt>/tmp</tt> and your home directory tidy; disk space is shared
* '''BACK UP YOUR OWN DATA: we have no data persistency or backup guarantee'''

== Extras ==

* vGPU-enabled Windows or Ubuntu VMs — ask if needed
* Docker-inside-LXC supported (nesting + cgroupv2 enabled)

== Troubleshooting quick-ref ==

{| class="wikitable"
! Problem
! Fix
|-
| <tt>nvidia-smi</tt> shows no devices
| Container lost its GPU mapping—tell a sysadmin
|-
| Driver mismatch error
| Host driver was updated—reinstall matching userspace driver with <tt>--no-kernel-modules</tt>—tell a sysadmin
|-
| Out-of-memory in PyTorch
| If using a VM: request a larger vGPU slice. If using a container: someone else might be using some GPU memory. Check with <tt>nvidia-smi</tt> (gui for that coming up sometime kinda soon).
|}

Questions / ideas → email '''[mailto:ceres-c@muhack.com ceres-c@muhack.com]''', '''[mailto:mrmoddom@muhack.com mrmoddom@muhack.com]''', or '''[mailto:cammo@muhack.com cammo@muhack.com]''' — or just grab us at the Tuesday MuHack meeting.

MuHack Account

2025-05-09T16:38:39Z

Mrmoddom: Added "Create your profile page" section

When you become a member of the association, you're given a ''<nickname>''@muhack.org account, where ''<nickname>'' is the name you picked when you became a member. This account is registered in our Google Workspace, and gives you access to all the web services hosted by the association, as well as an email inbox. You can use it to log in:
* Your Gmail/Google Drive/...
* This wiki
* Our Proxmox VE cluster
* The VPN
* ''Give us more ideas...''

= Creating Your Personal Page =

We encourage you to create and complete your personal page here on the wiki, to be able to include you within pages. And don't forget to carefully read the [[User Policy]]!

=== Steps to Create Your Page ===
# Log in to the wiki.
# Click on your name in the top right corner
# Click '''"Edit with form"''' in the topbar.
# Fill the form and use the following template as a starting point:

<pre>
= Username's MuHack Page =

== About Me ==
(Write a short bio or your interests.)

== Projects ==
* Project 1 – Short description
* Project 2 – Short description

== Contact ==
(Optional ways for people to reach out to you.)
</pre>


Finally hit "Save page" and you're live!

By using the MuHack-provided Google Workspace email account, as well as any other services provided with it, members acknowledge and '''agree to adhere to [[User Policy]]'''. For any questions or concerns regarding this policy, members should contact the board of the association at [mailto:info@muhack.org info@muhack.org].

Main Page

2025-05-09T16:34:32Z

Mrmoddom: Removed "Create your profile page" section

= Welcome to the MuHack's Wiki =

'''MuHack''' is the first hackerspace in Brescia, created to promote open-source culture through the sharing of ideas, resources, and experiences.
We are a non-profit association open to anyone passionate about technology, electronics, computing, and free culture.

== Who we are ==
MuHack is a place where anyone — regardless of experience level — can meet, learn, experiment, and collaborate.
We organize courses, talks, workshops, group projects, and more, all aimed at spreading knowledge and a passion for open technologies.

== What we do ==
Start from the [[:Category:Projects]]'s page to see which project is currently active, or brows trough the [[:Category:Machines]]'s page to see our current machines.

== Where and when to find us ==
We meet every '''Tuesday from 18:00 to 23:45''' at the '''Associations Room of the University Campus''' located at '''Via Valotti 3, Mompiano, Brescia'''.
For more details on how to reach us, visit our [https://muhack.org/about/ About] page.

== Join us ==
If you'd like to become a member, please read our charter and fill out the registration form available [https://muhack.org/about/ here].

== Contact ==
* '''Email''': [mailto:info@muhack.org info@muhack.org]
* '''Website''': [https://muhack.org https://muhack.org]
* '''GitHub''': [https://github.com/muhack https://github.com/muhack]
* '''YouTube''': [https://www.youtube.com/c/MuhackOrgIT MuHack Channel]
* '''Facebook''': [https://www.facebook.com/muhackIT MuHack IT]
* '''Instagram''': [https://www.instagram.com/hackerspace_muhack/ @hackerspace_muhack]
* '''Telegram''': [https://t.me/muhack t.me/muhack]

Feel free to contribute pages about projects, how-to guides, technical documentation, or event summaries.
Let's build shared knowledge together as a community.

----

Main Page

2025-05-09T13:14:23Z

Mrmoddom: /* What we do */ - typo corrected

Main Page

2025-05-09T09:26:06Z

Mrmoddom: Init home page

= Welcome to the MuHack's Wiki =

'''MuHack''' is the first hackerspace in Brescia, created to promote open-source culture through the sharing of ideas, resources, and experiences.
We are a non-profit association open to anyone passionate about technology, electronics, computing, and free culture.

== Who we are ==
MuHack is a place where anyone — regardless of experience level — can meet, learn, experiment, and collaborate.
We organize courses, talks, workshops, group projects, and more, all aimed at spreading knowledge and a passion for open technologies.

== What we do ==
Start from the [[:Category:Projects]]'s page to see which project is currently active, or brows trough the [[:Catergory:Machines]]'s page to see our current machines.

== Where and when to find us ==
We meet every '''Tuesday from 18:00 to 23:45''' at the '''Associations Room of the University Campus''' located at '''Via Valotti 3, Mompiano, Brescia'''.
For more details on how to reach us, visit our [https://muhack.org/about/ About] page.

== Join us ==
If you'd like to become a member, please read our charter and fill out the registration form available [https://muhack.org/about/ here].

== Contact ==
* '''Email''': [mailto:info@muhack.org info@muhack.org]
* '''Website''': [https://muhack.org https://muhack.org]
* '''GitHub''': [https://github.com/muhack https://github.com/muhack]
* '''YouTube''': [https://www.youtube.com/c/MuhackOrgIT MuHack Channel]
* '''Facebook''': [https://www.facebook.com/muhackIT MuHack IT]
* '''Instagram''': [https://www.instagram.com/hackerspace_muhack/ @hackerspace_muhack]
* '''Telegram''': [https://t.me/muhack t.me/muhack]

Feel free to contribute pages about projects, how-to guides, technical documentation, or event summaries.
Let's build shared knowledge together as a community.

----

= Creating Your Personal Page =

This homepage is just the beginning! We encourage you to create and complete your personal page here on the wiki, to be able to include you within pages. And don't forget to carefully read the [User Policy]

=== Steps to Create Your Page ===
# Log in to the wiki.
# Click on your name in the top right corner
# Click '''"Edit with form"''' in the topbar.
# Fill the form and use the following template as a starting point:

<pre>
= Username's MuHack Page =

== About Me ==
(Write a short bio or your interests.)

== Projects ==
* Project 1 – Short description
* Project 2 – Short description

== Contact ==
(Optional ways for people to reach out to you.)
</pre>


Finally hit "Save page" and you're live!

Wishlist

2025-05-07T12:45:09Z

Mrmoddom: /* Current Wishlist */

= MuHack Wishlist =

We are a community-driven association passionate about making, hacking, and learning together.
Your donations help us grow and support our projects and members. Below is a list of materials we currently need.

== How You Can Help ==

If you have any of the items listed below and would like to donate them to MuHack, please contact us at '''info@muhack.org'''.
We also welcome any tools, electronics, or materials that you think could be useful in a hackerspace.

== Current Wishlist ==

{| class="wikitable"
! Item Description
! Purpose / Use
! Project

|-
| Hard drives (SSD or HDD, 500GB or more)
| For upgrading shared workstations and storing project data
| [[GPU Server]]

|-
| RAM modules (DDR3/DDR4, any size)
| To improve performance of our workshop PCs and servers
| [[GPU Server]]

|-
| Graphics cards (NVIDIA or AMD, any working model)
| For AI, machine learning experiments, and 3D design tasks
| [[GPU Server]]

|-
| Raspberry Pi 4 (any model)
| For workshops, IoT experiments, and Linux learning sessions
|

|-
| PLA/ABS filament (1.75mm)
| Used in 3D printing projects and prototyping
|

|-
| Microcontrollers (ESP32, Arduino, etc.)
| Core components in our embedded systems workshops
|

|-
| Storage boxes / tool organizers
| To keep our workspace tidy and tools easily accessible
|

|-
| Safety gear (goggles, gloves, etc.)
| To ensure safe practices during hands-on sessions
| [[:Category:Members]]
|}

== Thank You! ==

Every donation makes a difference.
Thank you for supporting the MuHack community and helping us inspire more makers!

Gaspare (Server)

2025-05-07T12:33:46Z

Mrmoddom: GPU Server project page initial creation

{{Project
|Project Status=Active
|Participants=Ceres-c, Mrmoddom
}}
We are currently setting up a proxmox server with the support for Virtual GPU.

== Hardware ==

TDB

MuHack SAO 10th anniversary

2025-05-07T12:23:06Z

Mrmoddom: MuHack SAO 10th anniversary project page

{{Project
|Picture=MuHack-SAO-10th-all-colors.jpg
|Project Status=Finished
|Participants=Mrmoddom
}}
== MuHack SAO 10th anniversary ==

For the 10th anniversary of the MuHack hackerspace, I made a little SAO that can also be pinned to your shirt or backpack, working off a button battery.

=== Features ===
* Two configurations: SAO and pin
* Two LEDs mounted on a transparent part of the PCB
* I²C interface for connecting a small SPI flash memory
* Gold-plated for a neat design
* Clasp butterfly pin

== Getting Started ==
This PCB is designed to be used in two different configurations: as a pin or as a SAO.

The pin configuration is the simplest, with only two LEDs and a switch to turn them on and off, everything powered by a CR1220 battery.

There is also a solderable footprint for a clasp butterfly pin, so you can wear it on your shirt or backpack.

=== BOM for PIN configuration ===
* 2 × 0805 LEDs
* 1 × CR1220 battery holder (e.g. Keystone 3002)
* 1 × CR1220 battery
* 1 × 0805 1 kΩ resistor
* 1 × switch for on/off (e.g. C&K PCM12SMTR)

=== BOM for SAO configuration ===
* 2 × 0805 10 kΩ resistors
* 1 × SPI SOIC-8 flash memory (e.g. Winbond W25Q32JVSSIM)
* (Optional) Everything listed in the PIN configuration BOM except the battery and holder

:''Do not use the SAO configuration with the battery inserted, as it may damage the circuit or the connected badge!''

== Links ==

All the files for this project are available on the [https://github.com/mrmoddom/MuHack-SAO-10th GitHub Repo].

== License ==
This work is licensed under [https://creativecommons.org/licenses/by/4.0/ CC BY 4.0] by the author.

File:MuHack-SAO-10th-all-colors.jpg

2025-05-07T12:19:24Z

Mrmoddom:

MuTag

2025-05-07T12:03:37Z

Mrmoddom: Created MuTag project page with features, repository structure, usage, and contact info.

{{Project
|Picture=Mutag v2 1.jpg
|Project Status=Finished
|Participants=Mrmoddom
}}
== MuTag v2.1 ==
The first MuHack's NFC keychain!

This is a custom PCB with the ATTiny44a microcontroller and an ST25 NFC ISO15 tag.

From the microcontroller, you can access the NFC tag via I²C, modify its configuration, and read/write data.

== Features ==
* '''MCU''': ATTiny44a
* '''NFC Tag''': ST25 NFC ISO15 (4 Kbit memory)
* '''Energy harvesting'''
* '''High-speed Mailbox''': 256 bytes
* '''4 LEDs''' in different colors
* '''Dimensions''': 20 × 60 mm

== Getting Started ==
In the Hardware folder, you'll find the PCB design files and electrical schematics.

<pre>
#define YELLOW_LED 0
#define GREEN_LED 1
#define BLUE_LED 2
#define RED_LED 3
</pre>

The LEDs are connected to:
* Yellow → PA0
* Green → PA1
* Blue → PA2
* Red → PA3

The NFC tag is on the I²C bus of the ATTiny:
* SDA → PA6
* SCL → PA4

The tag's GPO pin is connected to INT0 of the ATTiny (PB2).

=== Activating Energy Harvesting Mode ===
By default, the tag is in "on demand" mode. To set it to permanent energy harvesting mode:
# Install the ST25 NFC app from the Play Store: https://play.google.com/store/apps/details?id=com.st.st25nfc
# Scan the tag and go to "Register Management"
# Read the tag again; locate the register `EH_MODE` (0x01 = on demand)
# Set `EH_MODE` to 0x00 and press "Save" (default password = 0000)

== Programming the ATTiny44a ==
An external ISP programmer is required: we will use an Arduino Uno as the programmer.

# Upload the `ArduinoISP` sketch to the Arduino.
# Add this URL to the "Additional Boards Manager URLs" in the Arduino IDE preferences:
<pre>http://drazzy.com/package_drazzy.com_index.json</pre>
# Install "ATTinyCore" by Spence Konde and select:
{| class="wikitable"
|+ Settings
|-
! Option !! Value
|-
| Board || ATTiny24/44/84 (noBootloader)
|-
| Chip || ATTiny44(a) (v2.0 → select 24)
|-
| Clock || 1 MHz internal
|-
| BOD || Disabled
|-
| LTO || Enabled
|-
| EEPROM || Retained
|-
| millis()/micros() || Enabled
|-
| Programmer || Arduino as ISP
|}
# MuTag ↔ Arduino connections:
{| class="wikitable"
|-
! MuTag !! Arduino
|-
| VDD || 5 V
|-
| GND || GND
|-
| SCK || 13
|-
| MISO || 12
|-
| MOSI || 11
|-
| RST || 10
|}
*Note:* The through-hole pads on the MuTag are now 2.54 mm.

To start flashing, touch GND with the Arduino's reset pin a few seconds before hitting "Upload" in the IDE (or use "Upload using Programmer").

== Accessing the NFC tag via I²C ==
The internal memory of the ST25 tag is mapped as an I²C EEPROM at address `0x53`.
Example sketch: `Hello_MuHack.ino`.

== TODO ==
* Add 3D model of the PCB
* Find a bootloader for UART programming
* Evaluate removing the diodes
* Enlarge programming pads
* Change MCU to ATTiny44/84 (more memory)
* Remove the `RESET` pad

== Bootloader Notes ==
The Optiboot bootloader (Spence Konde) uses the AIN0/AIN1 pins (connected to the LEDs). Options:
* Remove the LEDs to use the pins for UART
* Recompile the bootloader with different pins

This project is designed as a keychain (single programming), so the LEDs were kept and the bootloader was not invested in.

== License ==
Copyright © 2023 MrMoDDoM
This project is licensed under the GNU Affero General Public License (AGPL-3.0).
See [[LICENSE.md]] for details.

== Links ==
* Project page on GitHub: https://github.com/MrMoDDoM/MuTag
* Google Play ST25 NFC App: https://play.google.com/store/apps/details?id=com.st.st25nfc

File:Mutag v2 1.jpg

2025-05-07T11:48:04Z

Mrmoddom: Photo of the MuTag version v2.1

Photo of the MuTag version v2.1

MuHack Badge

2025-05-07T11:40:41Z

Mrmoddom:

{{Project
|Picture=MuHack Badge.png
|Project Status=Active
|Participants=Mrmoddom
}}
= MuHack Badge =

The MuHack Badge is the official badge of the MuHack hackerspace, designed for learning, hacking, and experimenting with embedded systems. It features a combination of microcontrollers, sensors, and connectivity options, making it a versatile platform for various projects.

== Features ==

* '''RP2040 MCU''': Serves as the main microcontroller, running MicroPython. It controls LEDs, buttons, buzzer, and communicates with sensors.
* '''ESP32 MCU''': Optional co-processor providing Wi-Fi and Bluetooth connectivity.
* '''BHI160B Sensor Hub''': A 6-axis sensor hub with a 3-axis gyroscope and a 3-axis accelerometer, capable of gesture detection and orientation sensing.
* '''14 WS2812B RGB LEDs''': Individually addressable LEDs for visual feedback and effects.
* '''USB, I2C, and UART Interfaces''': For communication and expansion.
* '''Two Buttons and One Buzzer''': For user interaction.
* '''NFC Subsystem''': Allows data storage and communication with other devices via I2C.

== BHI160B Sensor Hub ==

The BHI160B integrates a 3-axis gyroscope and a 3-axis accelerometer, providing fused data outputs like quaternions and rotation matrices. It can detect gestures and determine the board's orientation. Connected to the RP2040 via I2C, it streams data from the gyroscope and accelerometer.

== System Architecture ==

The board comprises three main subsystems:

* '''RP2040''': Controls hardware components and communicates with sensors and NFC.
* '''ESP32''': Optional module for wireless connectivity.
* '''BHI160B''': Manages motion sensing and can interface with additional sensors like the BMM150 magnetometer.

== Getting Started ==

# '''Install MicroPython''': Since the RP2040 is similar to the Raspberry Pi Pico, use the official MicroPython firmware from [https://micropython.org/download/RPI_PICO/ micropython.org].
# '''Upload BOSS System''': Copy all files from the <code>Software/BOSS/</code> folder of the [https://github.com/MrMoDDoM/MuHack-Badge MuHack Badge repository] to the board. Ensure the <code>BHY</code> folder is also copied, as it contains the BHI160B driver.
# '''Interact with the Badge''': Use a serial terminal (e.g., screen, minicom, PuTTY) to connect and interact with the BOSS system or run example applications.

== Changelog ==

=== Version 2 ===

* Added USB connector for the ESP32.
* Integrated NFC subsystem.
* Reworked the power system.
* Added LEDs for battery status and ESP32.
* Included a button for the ESP32.
* Ongoing firmware updates for improved BHI support.

=== Version 1 ===

* Initial release.

== TODOs ==

* <s>Connect the interrupt line of BHI to the RP2040.</s>
* <s>Invert TX/RX of UART between ESP32 and RP2040.</s>
* <s>Modify the ESP32 debug port footprint.</s>
* <s>Possibly add buttons for boot selection and reset for the ESP32.</s>
* <s>Improve silkscreen text size and labeling.</s>
* <s>Expose BHI's internal I2C and interrupt lines for future sensors.</s>
* <s>Adjust I2C pull-up resistor placement.</s>
* <s>Add polarity indicators for LEDs and diodes.</s>
* <s>Remove or replace the power inductor.</s>
* Enhance documentation and code comments.
* <s>Remove the D16 Schottky Diode from the battery line.</s>
* <s>Add capacitors to prevent brown-out when disconnecting USB power.</s>
* Implement a method in the BHY library to stop all sensors.
* <s>Consider adding an NFC tag.</s>

== License ==

This project is licensed under the AGPL-3.0 License.

== Links ==

* [https://github.com/MrMoDDoM/MuHack-Badge MuHack Badge GitHub Repository]
* [https://mrmoddom.github.io/posts/MuHack-Badge/ Original Blog Post]

== Credits ==

Special thanks to '''@gcammisa''' and '''Paolino''' for their contributions.

User:Mrmoddom

2025-05-07T11:40:11Z

Mrmoddom: MrMoDDoM Profile - correct one, delete the other

{{Member
|Picture=MrMoDDoM-Avatar-512x512.png
|Nickname=MrMoDDoM
|URL=https://mrmoddom.github.io/
|Email=mrmoddom@muhack.org
|Member Status=Member
}}
= About MrMoDDoM =

Hi all!

I'm Daniele, also known as '''MrMoDDoM''', a member of the [https://muhack.org MuHack hackerspace].

I enjoy exploiting things, learning new stuff by breaking other stuff, and I love cooking.

For any questions, suggestions, or research offers, feel free to reach out to me:

* '''Email''': [mailto:mrmoddom@muhack.org mrmoddom@muhack.org]
* '''Twitter''': [https://twitter.com/mrmoddom @mrmoddom]

> Mail with PGP will come soon.

MrMoDDoM

2025-05-07T11:25:04Z

Mrmoddom: MrMoDDoM Profile

File:MrMoDDoM-Avatar-512x512.png

2025-05-07T11:20:51Z

Mrmoddom: MrMoDDoM's Profile picture

MrMoDDoM's Profile picture

MuHack Badge

2025-05-07T10:27:52Z

Mrmoddom: /* TODOs */

{{Project
|Picture=MuHack Badge.png
|Project Status=Active
|Participants=MuHack
}}
= MuHack Badge =

The MuHack Badge is the official badge of the MuHack hackerspace, designed for learning, hacking, and experimenting with embedded systems. It features a combination of microcontrollers, sensors, and connectivity options, making it a versatile platform for various projects.

== Features ==

* '''RP2040 MCU''': Serves as the main microcontroller, running MicroPython. It controls LEDs, buttons, buzzer, and communicates with sensors.
* '''ESP32 MCU''': Optional co-processor providing Wi-Fi and Bluetooth connectivity.
* '''BHI160B Sensor Hub''': A 6-axis sensor hub with a 3-axis gyroscope and a 3-axis accelerometer, capable of gesture detection and orientation sensing.
* '''14 WS2812B RGB LEDs''': Individually addressable LEDs for visual feedback and effects.
* '''USB, I2C, and UART Interfaces''': For communication and expansion.
* '''Two Buttons and One Buzzer''': For user interaction.
* '''NFC Subsystem''': Allows data storage and communication with other devices via I2C.

== BHI160B Sensor Hub ==

The BHI160B integrates a 3-axis gyroscope and a 3-axis accelerometer, providing fused data outputs like quaternions and rotation matrices. It can detect gestures and determine the board's orientation. Connected to the RP2040 via I2C, it streams data from the gyroscope and accelerometer.

== System Architecture ==

The board comprises three main subsystems:

* '''RP2040''': Controls hardware components and communicates with sensors and NFC.
* '''ESP32''': Optional module for wireless connectivity.
* '''BHI160B''': Manages motion sensing and can interface with additional sensors like the BMM150 magnetometer.

== Getting Started ==

# '''Install MicroPython''': Since the RP2040 is similar to the Raspberry Pi Pico, use the official MicroPython firmware from [https://micropython.org/download/RPI_PICO/ micropython.org].
# '''Upload BOSS System''': Copy all files from the <code>Software/BOSS/</code> folder of the [https://github.com/MrMoDDoM/MuHack-Badge MuHack Badge repository] to the board. Ensure the <code>BHY</code> folder is also copied, as it contains the BHI160B driver.
# '''Interact with the Badge''': Use a serial terminal (e.g., screen, minicom, PuTTY) to connect and interact with the BOSS system or run example applications.

== Changelog ==

=== Version 2 ===

* Added USB connector for the ESP32.
* Integrated NFC subsystem.
* Reworked the power system.
* Added LEDs for battery status and ESP32.
* Included a button for the ESP32.
* Ongoing firmware updates for improved BHI support.

=== Version 1 ===

* Initial release.

== TODOs ==

* <s>Connect the interrupt line of BHI to the RP2040.</s>
* <s>Invert TX/RX of UART between ESP32 and RP2040.</s>
* <s>Modify the ESP32 debug port footprint.</s>
* <s>Possibly add buttons for boot selection and reset for the ESP32.</s>
* <s>Improve silkscreen text size and labeling.</s>
* <s>Expose BHI's internal I2C and interrupt lines for future sensors.</s>
* <s>Adjust I2C pull-up resistor placement.</s>
* <s>Add polarity indicators for LEDs and diodes.</s>
* <s>Remove or replace the power inductor.</s>
* Enhance documentation and code comments.
* <s>Remove the D16 Schottky Diode from the battery line.</s>
* <s>Add capacitors to prevent brown-out when disconnecting USB power.</s>
* Implement a method in the BHY library to stop all sensors.
* <s>Consider adding an NFC tag.</s>

== License ==

This project is licensed under the AGPL-3.0 License.

== Links ==

* [https://github.com/MrMoDDoM/MuHack-Badge MuHack Badge GitHub Repository]
* [https://mrmoddom.github.io/posts/MuHack-Badge/ Original Blog Post]

== Credits ==

Special thanks to '''@gcammisa''' and '''Paolino''' for their contributions.

MuHack Badge

2025-05-07T10:27:12Z

Mrmoddom: /* TODOs */

{{Project
|Picture=MuHack Badge.png
|Project Status=Active
|Participants=MuHack
}}
= MuHack Badge =

The MuHack Badge is the official badge of the MuHack hackerspace, designed for learning, hacking, and experimenting with embedded systems. It features a combination of microcontrollers, sensors, and connectivity options, making it a versatile platform for various projects.

== Features ==

* '''RP2040 MCU''': Serves as the main microcontroller, running MicroPython. It controls LEDs, buttons, buzzer, and communicates with sensors.
* '''ESP32 MCU''': Optional co-processor providing Wi-Fi and Bluetooth connectivity.
* '''BHI160B Sensor Hub''': A 6-axis sensor hub with a 3-axis gyroscope and a 3-axis accelerometer, capable of gesture detection and orientation sensing.
* '''14 WS2812B RGB LEDs''': Individually addressable LEDs for visual feedback and effects.
* '''USB, I2C, and UART Interfaces''': For communication and expansion.
* '''Two Buttons and One Buzzer''': For user interaction.
* '''NFC Subsystem''': Allows data storage and communication with other devices via I2C.

== BHI160B Sensor Hub ==

The BHI160B integrates a 3-axis gyroscope and a 3-axis accelerometer, providing fused data outputs like quaternions and rotation matrices. It can detect gestures and determine the board's orientation. Connected to the RP2040 via I2C, it streams data from the gyroscope and accelerometer.

== System Architecture ==

The board comprises three main subsystems:

* '''RP2040''': Controls hardware components and communicates with sensors and NFC.
* '''ESP32''': Optional module for wireless connectivity.
* '''BHI160B''': Manages motion sensing and can interface with additional sensors like the BMM150 magnetometer.

== Getting Started ==

# '''Install MicroPython''': Since the RP2040 is similar to the Raspberry Pi Pico, use the official MicroPython firmware from [https://micropython.org/download/RPI_PICO/ micropython.org].
# '''Upload BOSS System''': Copy all files from the <code>Software/BOSS/</code> folder of the [https://github.com/MrMoDDoM/MuHack-Badge MuHack Badge repository] to the board. Ensure the <code>BHY</code> folder is also copied, as it contains the BHI160B driver.
# '''Interact with the Badge''': Use a serial terminal (e.g., screen, minicom, PuTTY) to connect and interact with the BOSS system or run example applications.

== Changelog ==

=== Version 2 ===

* Added USB connector for the ESP32.
* Integrated NFC subsystem.
* Reworked the power system.
* Added LEDs for battery status and ESP32.
* Included a button for the ESP32.
* Ongoing firmware updates for improved BHI support.

=== Version 1 ===

* Initial release.

== TODOs ==

* <s>Connect the interrupt line of BHI to the RP2040.<s>
* <s>Invert TX/RX of UART between ESP32 and RP2040.<s>
* <s>Modify the ESP32 debug port footprint.<s>
* <s>Possibly add buttons for boot selection and reset for the ESP32.<s>
* <s>Improve silkscreen text size and labeling.<s>
* <s>Expose BHI's internal I2C and interrupt lines for future sensors.<s>
* <s>Adjust I2C pull-up resistor placement.<s>
* <s>Add polarity indicators for LEDs and diodes.<s>
* <s>Remove or replace the power inductor.<s>
* Enhance documentation and code comments.
* <s>Remove the D16 Schottky Diode from the battery line.<s>
* <s>Add capacitors to prevent brown-out when disconnecting USB power.<s>
* Implement a method in the BHY library to stop all sensors.
* <s>Consider adding an NFC tag.<s>

== License ==

This project is licensed under the AGPL-3.0 License.

== Links ==

* [https://github.com/MrMoDDoM/MuHack-Badge MuHack Badge GitHub Repository]
* [https://mrmoddom.github.io/posts/MuHack-Badge/ Original Blog Post]

== Credits ==

Special thanks to '''@gcammisa''' and '''Paolino''' for their contributions.

MuHack Badge

2025-05-07T10:23:19Z

Mrmoddom: Created MuHack Badge page with feature overview, setup instructions, changelog, and technical notes.

{{Project
|Picture=MuHack Badge.png
|Project Status=Active
|Participants=MuHack
}}
= MuHack Badge =

The MuHack Badge is the official badge of the MuHack hackerspace, designed for learning, hacking, and experimenting with embedded systems. It features a combination of microcontrollers, sensors, and connectivity options, making it a versatile platform for various projects.

== Features ==

* '''RP2040 MCU''': Serves as the main microcontroller, running MicroPython. It controls LEDs, buttons, buzzer, and communicates with sensors.
* '''ESP32 MCU''': Optional co-processor providing Wi-Fi and Bluetooth connectivity.
* '''BHI160B Sensor Hub''': A 6-axis sensor hub with a 3-axis gyroscope and a 3-axis accelerometer, capable of gesture detection and orientation sensing.
* '''14 WS2812B RGB LEDs''': Individually addressable LEDs for visual feedback and effects.
* '''USB, I2C, and UART Interfaces''': For communication and expansion.
* '''Two Buttons and One Buzzer''': For user interaction.
* '''NFC Subsystem''': Allows data storage and communication with other devices via I2C.

== BHI160B Sensor Hub ==

The BHI160B integrates a 3-axis gyroscope and a 3-axis accelerometer, providing fused data outputs like quaternions and rotation matrices. It can detect gestures and determine the board's orientation. Connected to the RP2040 via I2C, it streams data from the gyroscope and accelerometer.

== System Architecture ==

The board comprises three main subsystems:

* '''RP2040''': Controls hardware components and communicates with sensors and NFC.
* '''ESP32''': Optional module for wireless connectivity.
* '''BHI160B''': Manages motion sensing and can interface with additional sensors like the BMM150 magnetometer.

== Getting Started ==

# '''Install MicroPython''': Since the RP2040 is similar to the Raspberry Pi Pico, use the official MicroPython firmware from [https://micropython.org/download/RPI_PICO/ micropython.org].
# '''Upload BOSS System''': Copy all files from the <code>Software/BOSS/</code> folder of the [https://github.com/MrMoDDoM/MuHack-Badge MuHack Badge repository] to the board. Ensure the <code>BHY</code> folder is also copied, as it contains the BHI160B driver.
# '''Interact with the Badge''': Use a serial terminal (e.g., screen, minicom, PuTTY) to connect and interact with the BOSS system or run example applications.

== Changelog ==

=== Version 2 ===

* Added USB connector for the ESP32.
* Integrated NFC subsystem.
* Reworked the power system.
* Added LEDs for battery status and ESP32.
* Included a button for the ESP32.
* Ongoing firmware updates for improved BHI support.

=== Version 1 ===

* Initial release.

== TODOs ==

* Connect the interrupt line of BHI to the RP2040.
* Invert TX/RX of UART between ESP32 and RP2040.
* Modify the ESP32 debug port footprint.
* Possibly add buttons for boot selection and reset for the ESP32.
* Improve silkscreen text size and labeling.
* Expose BHI's internal I2C and interrupt lines for future sensors.
* Adjust I2C pull-up resistor placement.
* Add polarity indicators for LEDs and diodes.
* Remove or replace the power inductor.
* Enhance documentation and code comments.
* Remove the D16 Schottky Diode from the battery line.
* Add capacitors to prevent brown-out when disconnecting USB power.
* Implement a method in the BHY library to stop all sensors.
* Consider adding an NFC tag.

== License ==

This project is licensed under the AGPL-3.0 License.

== Links ==

* [https://github.com/MrMoDDoM/MuHack-Badge MuHack Badge GitHub Repository]
* [https://mrmoddom.github.io/posts/MuHack-Badge/ Original Blog Post]

== Credits ==

Special thanks to '''@gcammisa''' and '''Paolino''' for their contributions.

File:MuHack Badge.png

2025-05-07T10:19:00Z

Mrmoddom: Photo (bad quality) of the MuHack official Badge

Photo (bad quality) of the MuHack official Badge

Wishlist

2025-05-07T08:55:14Z

Mrmoddom: Created initial MuHack Wishlist page with introduction, donation instructions, and detailed materials table.

= MuHack Wishlist =

We are a community-driven association passionate about making, hacking, and learning together.
Your donations help us grow and support our projects and members. Below is a list of materials we currently need.

== How You Can Help ==

If you have any of the items listed below and would like to donate them to MuHack, please contact us at '''info@muhack.org'''.
We also welcome any tools, electronics, or materials that you think could be useful in a hackerspace.

== Current Wishlist ==

{| class="wikitable"
! Item Description
! Purpose / Use

|-
| Hard drives (SSD or HDD, 500GB or more)
| For upgrading shared workstations and storing project data

|-
| RAM modules (DDR3/DDR4, any size)
| To improve performance of our workshop PCs and servers

|-
| Graphics cards (NVIDIA or AMD, any working model)
| For AI, machine learning experiments, and 3D design tasks

|-
| Raspberry Pi 4 (any model)
| For workshops, IoT experiments, and Linux learning sessions

|-
| PLA/ABS filament (1.75mm)
| Used in 3D printing projects and prototyping

|-
| Microcontrollers (ESP32, Arduino, etc.)
| Core components in our embedded systems workshops

|-
| Storage boxes / tool organizers
| To keep our workspace tidy and tools easily accessible

|-
| Safety gear (goggles, gloves, etc.)
| To ensure safe practices during hands-on sessions
|}

== Thank You! ==

Every donation makes a difference.
Thank you for supporting the MuHack community and helping us inspire more makers!