whatisgithub

What is bc250-cu-live-manager?

winnielv/bc250-cu-live-manager — explained in plain English

Analysis updated 2026-05-18

51ShellAudience · ops devopsComplexity · 4/5Setup · hard

In one sentence

A terminal tool that lets owners of the AMD BC-250 graphics card unlock extra compute units at runtime, from 24 up to 40, and optionally keep that change across reboots.

Mindmap

A visual breakdown will appear here once this repo is fully enriched.

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Temporarily test running the BC-250 with all 40 compute units active instead of the factory 24.

USE CASE 2

Save a custom compute unit layout and install a boot service so it survives every restart.

USE CASE 3

Restore the original factory driver layout if a custom configuration causes problems.

What is it built with?

BashUMRPythonsystemd

How does it compare?

winnielv/bc250-cu-live-managerliafanx/mtproxy-reanimationnelsonwerd/idea-to-ship-skills
Stars514954
LanguageShellShellShell
Setup difficultyhardmoderatemoderate
Complexity4/53/53/5
Audienceops devopsops devopsvibe coder

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · hard Time to first run · 30min

Requires the specific AMD BC-250 hardware, root access, the UMR utility, Python 3, and a compatible AMD GPU system library.

The README does not state a license.

So what is it?

This is an interactive terminal tool for managing compute units on the AMD BC-250 graphics card. The BC-250 normally boots with 24 compute units active, controlled by the driver. This tool lets you route additional compute units at runtime using a low-level hardware access utility called UMR, potentially raising the active count from 24 to 40. Changes can be kept only for the current session, or saved and set to restore automatically after every reboot. The tool presents a live dashboard in the terminal showing which compute units are currently active, which are driver-controlled, and which the tool has enabled separately. From there you can open a table editor that lets you toggle individual units on or off, apply a preset full-40-unit layout, or restore the original factory layout. All write actions require an explicit confirmation step before any hardware registers are touched. To make a layout persist across reboots, two steps are required: saving the current live table to a configuration file, and then installing a system service that replays that file each time the machine starts. The tool includes separate menu options for each step, and also for uninstalling the service if you no longer want automatic restore. An asterisk marker in the menu indicates when the current live table differs from what is saved for boot. The tool is a single Bash script. Running it requires the AMD BC-250 hardware, the UMR utility (which the script can offer to install if missing), Python 3, and a compatible AMD GPU system library. The tool is specific to this hardware model and not intended for other graphics cards.

Copy-paste prompts

Prompt 1
Explain what UMR is and how this bc250-cu-live-manager script uses it to route extra compute units.
Prompt 2
Walk me through applying full 40 CU dispatch with this tool and making it persist across reboots.
Prompt 3
What is the difference between the driver topology and the live routing table in this project?
Prompt 4
Help me troubleshoot the boot restore service in bc250-cu-live-manager not reapplying my saved table.

Frequently asked questions

What is bc250-cu-live-manager?

A terminal tool that lets owners of the AMD BC-250 graphics card unlock extra compute units at runtime, from 24 up to 40, and optionally keep that change across reboots.

What language is bc250-cu-live-manager written in?

Mainly Shell. The stack also includes Bash, UMR, Python.

What license does bc250-cu-live-manager use?

The README does not state a license.

How hard is bc250-cu-live-manager to set up?

Setup difficulty is rated hard, with roughly 30min to a first successful run.

Who is bc250-cu-live-manager for?

Mainly ops devops.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.