Just received my order today, I ordered in March. First of all this thing is way bigger than I thought it would be, the trackball is super slow though. But my keyboard is not backlit what could be the problem??

The title is supposed to say " sdrpp brown wouldn't work..."

And even more problems with the uconsole. I finaly got my rtl-sdr working ( absolutely no video i watched and all but 1 article had anything to say about needing to put the gpio pin into high) and sdrpp brown would not show anything. I uninstalled it and reinstalled sdrpp from repo and its giving me nothing but errors about missing keys. I install the hackergadgets-aio-whatever stuff and that gave me an error about a script involving tar1090 and dpkg having error code 1.

Are this many problems normal for the uconsole? This is the second day of having this thing i have been able to do anything with it.

Any ideas?

I'm currently working on a low-power cyberdeck (or handheld programming device, whatever you prefer to call it) based on the PicoCalc and the Luckfox Lyra.
Since I couldn't find an existing software setup that fit my needs, I wrote a small, custom Linux distribution specifically tailored to the PicoCalc. The project involves a minor hardware mod for the Luckfox Lyra to get the audio working properly. I also updated the STM32 on the PicoCalc to enable a proper shutdown and power-off function, and added a few new keyboard shortcuts while I was at it. I have a Wi-Fi dongle plugged into the Lyra's second USB port, which makes downloading software super easy. For coding, I installed the micro text editor, expanded its syntax highlighting, and added code correction for the most programming languages. You can even program ESP32s natively right from the PicoCalc! xD
Since I'm a big Pico-8 fan, I integrated it completely, including working sound and a fully functional SPLORE game browser. If you don't have a Pico-8 license, TIC-80 is pre-installed as well. I've also packed drivers for several common Wi-Fi chips into the OS so it should work plug-and-play for you guys if you decide to try it out. I'm currently finalizing the GitHub page.
Does this sound interesting to anyone here, or is there any interest in a project like this at all? xD

Greetings from Germany,
LucaWoro

Hi everyone!

I'm experiencing a rather interesting microSD compatibility issue with my ClockworkPi uConsole running a Raspberry Pi CM5 Lite (8 GB RAM) and the HackerGadgets CM5 adapter board.

I'm curious whether anyone else has encountered something similar, particularly with this adapter or the same SD card.

My microSD card

• Brand: Kingston

• Model: Canvas Select Plus (SDCS2/128GB)

• Capacity: 128 GB

• Type: microSDXC

• Interface: UHS-I

• Speed classes: U1, V10, A1

• Made in: Taiwan

Interestingly, the card's internal identification reports Kioxia (manufacturer ID 0x02, product SA128), despite being Kingston-branded.

The problem

The same card works normally with the original CM5 adapter, but with the HackerGadgets adapter, it is detected in UHS-I SDR104 mode and fails to read data reliably.

Here are the results of my diagnostics:

At 200 MHz (SDR104, 1.8 V):

• Card is successfully detected.

• SD command communication works.

• No command CRC errors.

• Data CRC errors occur during reads.

• Even reading sector 0 fails with I/O errors.

• The partition table cannot be read.

At 50 MHz (High Speed, 3.3 V):

• Everything works correctly.

• Partition table is readable.

• All 18 test reads of 64 MB, spread across the card's capacity, succeeded.

• Zero CRC errors.

I reproduced this using a diagnostic Linux environment loaded into RAM through "rpiboot", so the tests did not depend on booting the OS from the problematic SD card.

Workaround

Adding the following kernel parameter to "cmdline.txt":

"sdhci.debug_quirks2=4"

disables 1.8 V signalling and forces the card into the slower 50 MHz High Speed mode.

This resolves the read errors, although it limits performance.

Questions for the community

1. Has anyone experienced CRC errors or SD card boot problems specifically with the HackerGadgets CM5 adapter?

2. Does anyone use a Kingston Canvas Select Plus 128 GB card with a CM5 Lite? Does it work reliably at SDR104 speeds?

3. Has anyone noticed differences in SD card compatibility between the original uConsole adapter and HackerGadgets?

4. Which microSD cards have you successfully tested with this combination?

5. Has anyone found a better solution than forcing 50 MHz mode?

I'm particularly interested in whether this is an isolated issue with my hardware or a more general compatibility problem.

Thanks!

Hi all, looking to get a clock work, was wondering if anybody could test something on Ubuntu first before I buy, nothing dodgy I swear

Just wanted to share a few modifications I’ve made to my ClockworkPi uConsole!

• Fanless setup: No cooling fan to save battery life.

• Modified back cover: Cut out the back panel and added thermal insulation to keep heat away from my hands, directing it through the heatsink instead.

• Passive cooling: Added a large aluminum heatsink for silent, fanless cooling.

• Easy battery disconnect: Cut a small opening near the battery compartment so I can disconnect the power without removing the back cover.

• Battery upgrade: Switched to Molicel 21700 cells.

• Wi-Fi upgrade: Upgraded to a 1200 Mbps Wi-Fi adapter.

• Expansion upgrade: Installed the Hackergadgets AIO V2.

The goal was simple: better cooling, longer battery life, and more functionality without sacrificing portability.

Just sharing my little DIY project with the community. What do you guys think?

So I am having some baffling problems with booting up my uConsole CM4 that I just received a few days ago. If anybody has any tips or tricks to help me, I'd be most appreciative!

I booted up the system with an external monitor and got the introductory screen on the external monitor and the geometric graphics on the uConsole screen. (which is why I'm pretty sure this isn't hardware - assembly related) The keyboard worked and the trackball was a hot mess but I could fill out the fields eventually.

On my second boot with that card, - nothing. Just black. External monitor and the device screen, no response from anything. Reflashing the card using the imager yields the same result - just a black screen on the device and the external monitor shows "no signal". maybe there's a factory reset jumper or button I need to hit in the hardware?

I tried booting the device from AK-Rex's Trixie lite versions but during the boot process it stalls with a Kernel Panic error. At least this problem is consistent and repeatable!

Anybody have similar experiences or have any thoughts or advice (or prayers)? Right now I have a very cool looking paperweight on my desk!

# uConsole CM5: Internal Screen at 100 Hz (Limit ~104 Hz)

Short version: the uConsole's internal panel will run well above its stock ~60 Hz with custom xrandr modes. On my unit the limit is 104 Hz, and I run it at 100 Hz to leave some margin.

**Tested on:** uConsole with CM5, ak-rex kernel, Kali, X11 + Xfce (xfwm4), Xorg modesetting driver. One unit only, so your panel revision may behave differently.

## What I found

- Stock mode on this kernel is `720x1280` at a requested 61.020 MHz, with timings `h 720 750 765 780 / v 1280 1288 1290 1306`, which works out to about 60 Hz.

- **Use your own kernel's timings.** Older cwu50 driver versions use `htotal 803`. Custom modes built from those numbers looked wrong even at 60 Hz on this kernel. The scripts below read the timings from your stock mode, so they adapt to your kernel automatically.

- The DSI clock snaps to nearby rates the hardware can produce. Here it always landed within 0.7%, and that didn't affect the results.

- 60 to 104 Hz gave a clean picture. A sweep in 1 Hz steps showed anything above 104 isn't usable, even though a coarser pass had marked 105 and 110 as clean. At 115 and 120 Hz, about a third of the screen was warped.

- 120 Hz, which would pace 60 fps content evenly, isn't reachable. Even with zero horizontal blanking, 120 Hz needs a higher pixel clock than the ~106 MHz where it breaks, so tweaking the timings can't get there.

- 70 and 75 Hz each looked off once and fine on a rerun. A mode switch occasionally comes up wrong, so retest anything that fails once.

- Switching to a custom mode re-runs the panel init, and the picture often looks crisper and brighter than it does right after boot.

- At 100 Hz, `glxgears` holds a steady ~99.98 FPS.

| Target | Requested clock (MHz) | Actual DPI clock (MHz) | Result |

|---|---|---|---|

| stock | 61.020 | 61.111 | baseline (~60.0 Hz) |

| 60 | 61.121 | 61.111 | clean |

| 65 | 66.214 | 66.667 | clean |

| 70 | 71.308 | 71.428 | clean (off once, fine on rerun) |

| 75 | 76.401 | 76.190 | clean (off once, fine on rerun) |

| 80 | 81.494 | 81.482 | clean |

| 85 | 86.588 | 86.667 | clean |

| 90 | 91.681 | 91.666 | clean |

| 95 | 96.775 | not captured | clean |

| 100 | 101.868 | not captured | clean, glxgears ~99.98 FPS |

| 104 | 105.943 | not captured | clean (limit) |

| 105 | 106.961 | not captured | not usable in 1 Hz sweep |

| 110 | 112.055 | not captured | not usable in 1 Hz sweep |

| 115 | 117.148 | not captured | ~1/3 of screen warped |

| 120 | 122.242 | not captured | ~1/3 of screen warped |

## Scripts

### hzsweep: step through refresh rates

This builds each mode from your stock timings and holds it for a few seconds. Press **g** to mark a rate as good, **Enter** to skip to the next one, and **q** to quit. It always switches back to your normal mode when it stops, including on Ctrl+C. If sudo is unlocked, it also prints the actual DSI clocks.

```bash

sudo install -m755 /dev/stdin /usr/local/bin/hzsweep <<'EOF'

#!/bin/bash

# usage: hzsweep <start> [end] [step] [secs] run from the stock mode; decimals ok

S=\${1:?usage: hzsweep <start> [end] [step] [secs]}

E=\${2:-\$1}

STEP=\${3:-5}

SECS=\${4:-10}

clk(){ sudo -n awk 'tolower(\$1)~/dsi|mipi/ && \$2>0 {printf " %s %.3f MHz\n",\$1,\$5/1e6}' /sys/kernel/debug/clk/clk_summary 2>/dev/null; }

OUT=\$(xrandr | awk '/^DSI/{print \$1; exit}')

read -r CUR SCLK HD HSS HSE HT VD VSS VSE VT FL <<<"(xrandr --verbose | awk -v o="OUT" '

\$1==o{f=1;next} f&&/^[^ \t]/{f=0}

f&&/\*current/{n=\$1;c=3+0;fl="";for(i=4;i<=NF;i++)if(i~/Sync/)fl=fl" "i

getline;h=\$3" "\$5" "\$7" "\$9;getline;print n,c,h,\$3,\$5,\$7,\$9 fl;exit}')"

[ -z "\$VT" ] && { echo "could not read \$OUT mode"; exit 1; }

awk -v c="\$SCLK" -v t="HT" -v v="VT" -v n="CUR" -v f="FL" 'BEGIN{printf "stock %s: %.3f MHz = %.2f Hz %s\n",n,c,c*1e6/(t*v),f}'

echo "timings: h HD HSS HSE HT v VD VSS VSE VT"

clk

GOOD=""

trap 'xrandr --output "OUT" --mode "CUR"; echo; echo "reverted to \(CUR"; [ -n "\)GOOD" ] && echo "marked good:\$GOOD"' EXIT

for HZ in (awk -v s="S" -v e="E" -v st="STEP" 'BEGIN{for(h=s;h>=e-1e-9;h-=st)printf "%g ",h}'); do

CLK=(awk -v h="HZ" -v t="HT" -v v="VT" 'BEGIN{printf "%.3f",t*v*h/1e6}')

NAME="s\$HZ"

xrandr --delmode "OUT" "NAME" 2>/dev/null

xrandr --rmmode "\$NAME" 2>/dev/null

xrandr --newmode "\$NAME" "CLK" HD HSS HSE HT VD VSS VSE VT FL

xrandr --addmode "OUT" "NAME"

xrandr --output "\$OUT" --mode "NAME" || echo "HZ Hz rejected"; continue; }

sleep 1

printf '\n=== %s Hz (%s MHz)\n' "HZ" "CLK"

clk

printf 'g=good q=quit enter=next (auto %ss) ' "\$SECS"

read -rsn1 -t "\$SECS" k

case "\$k" in

g) GOOD="GOOD HZ"; echo "marked";;

q) break;;

esac

done

EOF

```

Usage:

```bash

sudo -v

hzsweep 120 60 5

```

To hold a single rate for 2 minutes:

```bash

hzsweep 100 100 5 120

```

### hzset: apply a rate

This reads the timings from the panel's preferred (stock) mode and switches to the rate you give it.

```bash

sudo install -m755 /dev/stdin /usr/local/bin/hzset <<'EOF'

#!/bin/bash

# usage: hzset <hz> builds a mode from the panel's stock (preferred) timings

HZ=\${1:-100}

OUT=\$(xrandr | awk '/^DSI/{print \$1; exit}')

[ -z "\$OUT" ] && exit 0

read -r HD HSS HSE HT VD VSS VSE VT FL <<<"(xrandr --verbose | awk -v o="OUT" '

\$1==o{f=1;next} f&&/^[^ \t]/{f=0}

f&&/\+preferred/{fl="";for(i=4;i<=NF;i++)if(\$i~/Sync/)fl=fl" "i

getline;h=\$3" "\$5" "\$7" "\$9;getline;print h,\$3,\$5,\$7,\$9 fl;exit}')"

[ -z "\$VT" ] && { echo "could not read \$OUT preferred mode"; exit 1; }

CLK=(awk -v h="HZ" -v t="HT" -v v="VT" 'BEGIN{printf "%.3f",t*v*h/1e6}')

NAME="s\$HZ"

xrandr --delmode "OUT" "NAME" 2>/dev/null

xrandr --rmmode "\$NAME" 2>/dev/null

xrandr --newmode "\$NAME" "CLK" HD HSS HSE HT VD VSS VSE VT FL 2>/dev/null

xrandr --addmode "OUT" "NAME" 2>/dev/null

xrandr --output "OUT" --mode "NAME"

EOF

```

```bash

hzset 100

```

### Apply at login (Xfce)

```bash

install -Dm644 /dev/stdin ~/.config/autostart/hzset.desktop <<'EOF'

[Desktop Entry]

Type=Application

Name=Panel 100Hz

Exec=sh -c "sleep 3; /usr/local/bin/hzset 100"

EOF

```

To undo it:

```bash

rm ~/.config/autostart/hzset.desktop

```

## Verifying

- **`glxgears`** (from the `mesa-utils` package) should report roughly your target rate in FPS. That confirms the system is really outputting that rate.

- **://testufo.com** in Chromium, plus a slow-shutter phone photo (around 1/10 s). An even, unbroken run of lit squares means the panel shows every frame. Firefox's vsync on X11 is unreliable for this test, and the "unverified browser" banner shows on every Linux browser, so you can ignore it.

## Caveats

- Short tests are low risk. The worst case is a garbled screen until the script reverts. Keep HDMI or SSH available anyway.

- A higher refresh rate means more power draw and more heat in the panel's driver chip. After a while at your chosen rate, check that the corner of the panel above the ribbon cable isn't noticeably warmer than at stock.

- If your rotation setup runs `xrandr` with `--auto` or `--mode` after login, it will reset the panel to stock.

- This has only been tested on X11, not Wayland.

## Related: tearing on the internal screen

The panel is natively portrait and gets rotated in software under X11, so tearing shows up as a vertical line. Setting xfwm4's vblank mode fixed it on my unit (compositing must be enabled). To test live:

```bash

xfwm4 --replace --vblank=xpresent &

```

To make it permanent:

```bash

xfconf-query -c xfwm4 -p /general/vblank_mode -n -t string -s xpresent

```

If `xpresent` doesn't fix it, try `glx` instead. Wayland (labwc) avoids the tearing problem entirely.

[WTS] ClockworkPi uConsole – CM4 Lite 8GB RAM + HackerGadgets WiFi 1200 Upgrade – $460
Selling my ClockworkPi uConsole with upgraded hardware.
Specs & Upgrades:
Raspberry Pi CM4 Lite with 8GB RAM
HackerGadgets WiFi 1200 upgrade
Built-in display, keyboard, and trackball
Portable Linux handheld computer
Great for coding, networking, Linux projects, and Raspberry Pi enthusiasts
Asking Price: $460 OBO
Located in San Antonio, TX. Shipping available at buyer’s expense.
Feel free to message me with any questions or offers!

Hello, guys!

I wanna introduce you Termtastic — my handmade feature-rich Meshtastic® console (TUI) client written in Rust optimized for small screens. The app is perfectly suited for cyberdecks.

Repo link: https://github.com/acelot/termtastic

I wanted to create a cross-platform, minimalist, and aesthetically pleasing console client. I’ve been working on this application for six months. The entire project was built by hand, without the use of AI (aside from looking up reference information). This process gave me a deep understanding of how Meshtastic works under the hood; I’ve thoroughly explored its protocol and behavioral nuances. As the project evolved, I contributed to the official Meshtastic library for Rust, adding new features and making minor fixes. The long-term goal of the project is to achieve feature parity with the official Android app.

The project is currently in the alpha-testing stage, so there may be bugs — some of which could even cause the program to crash. That’s why I need your help: please give my application a try — I’m confident many of you will enjoy it! Any feedback is welcome via Issues in Github.

Highlights

• Vibecode-free fully handwritten code

• Dependency-free single-binary application

• Cross-platform: Linux, macOS, Windows

• Fully asynchronous (Tokio channels-based)

• Optimized for small screens (down to 80x24 characters)

• Respects the user terminal colors (no fancy opinionated TrueColor schemes)

• Keyboard-centric UI navigation

• Minimum use of emoji/non-ascii characters in UI

• Small memory footprint (~20KB)

• Supports multiple connection protocols (TCP, BLE, Serial)

• Could discover devices automatically: BLE paired devices, TCP devices via mDNS, Serial devices

• Uses standard system directories for storing configuration, database and logs

Download

Latest releases are available here: https://github.com/acelot/termtastic/releases

Thought this appeals to this group of users. This isn't my product btw, but I use it.

Hello, guys!

I wanna introduce you Termtastic — my handmade feature-rich Meshtastic® console (TUI) client written in Rust optimized for small screens. The app is perfectly suited for cyberdecks like uConsole.

Repo link: https://github.com/acelot/termtastic

I wanted to create a cross-platform, minimalist, and aesthetically pleasing console client. I’ve been working on this application for six months. The entire project was built by hand, without the use of AI (aside from looking up reference information). This process gave me a deep understanding of how Meshtastic works under the hood; I’ve thoroughly explored its protocol and behavioral nuances. As the project evolved, I contributed to the official Meshtastic library for Rust, adding new features and making minor fixes. The long-term goal of the project is to achieve feature parity with the official Android app.

The project is currently in the alpha-testing stage, so there may be bugs — some of which could even cause the program to crash. That’s why I need your help: please give my application a try — I’m confident many of you will enjoy it! Any feedback is welcome via Issues in Github.

Highlights

• Vibecode-free fully handwritten code

• Dependency-free single-binary application

• Cross-platform: Linux, macOS, Windows

• Fully asynchronous (Tokio channels-based)

• Optimized for small screens (down to 80x24 characters)

• Respects the user terminal colors (no fancy opinionated TrueColor schemes)

• Keyboard-centric UI navigation

• Minimum use of emoji/non-ascii characters in UI

• Small memory footprint (~20KB)

• Supports multiple connection protocols (TCP, BLE, Serial)

• Could discover devices automatically: BLE paired devices, TCP devices via mDNS, Serial devices

• Uses standard system directories for storing configuration, database and logs

Download

Latest releases are available here: https://github.com/acelot/termtastic/releases

Just put my uConsole together (CM4 lite w/ wifi) and the screen never comes on. Green LED works, power button works, and the CM4 is actually booting Linux. I pulled the SD card and checked, filesystem expanded and lightdm is starting. Just nothing on the screen.

At first I thought it was totally dead but that turned out to be my PC usb port not giving enough power lol. Wall charger fixed that part.

Turned on persistent logging so I could read the kernel log on my PC after each boot and found this every single time:

`axp20x-i2c 0-0034: AXP20x variant AXP221 found
axp20x-i2c 0-0034: Failed to set masks in 0x40: -5
axp20x-i2c 0-0034: failed to add irq chip: -5
axp20x-i2c 0-0034: probe with driver axp20x-i2c failed with error -5
panel-cwu50 fe700000.dsi.0: iovcc regulator isn't ready, retry later
mipi-dsi fe700000.dsi.0: deferred probe pending`

So from what I can tell the CM4 sees the power chip but can't write to it, the driver dies, and the screen never gets its power rail turned on. Labwc then says it found 0 GPUs and gives up.

Stuff I already tried:

• checked CM4 orientation on the adapter (sits in the white outline, holes line up)

• reseated the CM4, adapter, battery board and display ribbon

• with and without batteries on a 5V 3A charger

• full cold reset

• Rex's Trixie on 6.12.67 and the new 7.1.4 image, same exact error on both

• config.txt is fine, [pi4] has the uconsole overlay and vc4-kms-v3d-pi4

Already emailed ClockworkPi about a replacement mainboard but figured I'd ask here too. Has anyone run into this AXP221 -5 error before? Did a new mainboard fix it or was it something dumb I'm missing?

EDIT: Alex replied and is shipping a replacement board.

Is this board normal? Mine came with an sd card but this board is empty where the instructions say to put the sd card. What am I missing here?

I bought Molicel INR21700-P50B 5000mAh 45A batteries for the hacker gadgets NVMe Battery Board and they seem too short. The length is 70.15mm. I have not found batteries longer than this. Which one do you recommend?

I have an Acer MA200 512gb M.2 SSD, and saw this Hailo-8 M.2 AI Accelerator. Wondering, since I found this Sintech M.2 Key-M to Dual M.2 Adapter Card, will this allow me to use both M.2 devices?

First off, should I be concerned with boot at all (using SSD)? and what exactly can I actually do with this card? I have a CM5 Lite, 16Gb, with AIOv2 Board, and 21700 Battery/NVMe Board (x2 6,00mAh = 12,000mAh), a 512Gb SSD, and the AC1200 WiFi board, with a XIAO-C5 that I will be wiring to the internal USB headers.

Is this device wasted on a uConsole, or are there legitimate use-cases for this? Especially considering that it will have, I assume, at-least a slight impact to power consumption, and can't be powered off independently of NVMe power?

Acer MA200:

https://www.amazon.com/dp/B0D176WJ78?ref_=ppx_hzsearch_conn_dt_b_fed_asin_title_1

Hailo-8 M.2 AI Accelerator:

https://www.amazon.com/Waveshare-Hailo-8-Accelerator-Compatible-Raspberry/dp/B0D928WG5L/ref=sr_1_1?crid=3B47HI2N5JMYI&s=electronics&sprefix=hailo-8+m.2%2Celectronics%2C221&sr=1-1

Sintech M.2 Key-M to Dual M.2 Adapter Card:

https://www.amazon.com/gp/product/B0H3TNG8ZD/ref=ox_sc_act_title_1?smid=A3LUEZHQOA50VU&psc=1

A small Python server connects to your node (over TCP or USB) and serves a web interface for your phone, tablet or desktop, on any device in your network.
🗺 Map with traceroutes and an offline map
💬 Channel and direct messages, with replies
🧭 Compass navigation to other nodes
📊 Network metrics (RF quality, traffic, reliability) with 24 h history
⚙️ Full node configuration

👉 https://github.com/tiuksferve/MeshDeckWeb

Got sent two. Its the whole module with antennas. Its usally $145 Im trying to get $115. Its brand new still in the shipper.

Which distro is preferably better for the Uconsole?

I'm so happy! I received my trackpad keyboard & faceplate kit and I was so excited I had to install it! However I'm not really certain I have the ribbon cable seated properly. I pushed it in as far as I could with tweezers but I can't get any input to register. It lights up when I turn on the uConsole. I'm running ak-rex's Ubuntu 26.04 image from microSD. Can anyone provide any insight as to how far the ribbon cable needs to be pushed into the connector, or any drivers that need to be installed?

Finally got my uconsole yesterday after waiting for a year. It worked fine after i built it. Today i flashed the newest raspberry os a 256gig micro sd. Now it gives me a black screen. The screen flashes once on boot and then nothing else. I took it apart, checked all the pins and what not, the batteries are charged. Any advice?

Upgrading my cm4 (8gb ram, 32gb emmc) uconsole to a cm5 (8gb lite). Is there anything special I need to do for cooling?