# What a mess with clockpi A06

**URL:** <https://forum.clockworkpi.com/t/what-a-mess-with-clockpi-a06/12423>\
**Category:** uConsole\
**Created:** [February 10, 2024, 4:47pm UTC](https://forum.clockworkpi.com/t/what-a-mess-with-clockpi-a06/12423 "2024-02-10T16:47:40Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![fe8769](https://avatars.discourse-cdn.com/v4/letter/f/858c86/32.png) [@fe8769](https://forum.clockworkpi.com/u/fe8769)\
**Post date:** [February 10, 2024, 4:47pm UTC](https://forum.clockworkpi.com/t/what-a-mess-with-clockpi-a06/12423/1 "2024-02-10T16:47:40Z")

</div>

I received at the same time clockpi A06 and raspi 5 . I was able very fast to use kali linux and dragon OS radio suite on raspi5 .  
It is impossible to do think on A06 . I have to patch but I have unknown errors . I tried to use the A06 image . I can’t make a sudo apt-get update because I have an invalid KEY .  
I tried to installtinyvnc , It can’t run

What a mess …

---

<div class="post-metadata">

**Author:** ![MHam68HC11](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/mham68hc11/32/5046_2.png) [@MHam68HC11](https://forum.clockworkpi.com/u/MHam68HC11)\
**Post date:** [February 10, 2024, 5:10pm UTC](https://forum.clockworkpi.com/t/what-a-mess-with-clockpi-a06/12423/2 "2024-02-10T17:10:58Z")

</div>

sorry - I suggest you buy the cm4lite adapter and third party purchase a cm4 lite processor with 4G memory wifi but not emmc … I’ve been very happy with the cm4 performance - I may convert my A-06 devterm over to cm4 as a result…

---

<div class="post-metadata">

**Author:** ![mikeschnier](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/mikeschnier/32/9697_2.png) [@mikeschnier](https://forum.clockworkpi.com/u/mikeschnier)\
**Post date:** [February 10, 2024, 6:10pm UTC](https://forum.clockworkpi.com/t/what-a-mess-with-clockpi-a06/12423/3 "2024-02-10T18:10:34Z")

</div>

I wouldn’t. I have the CM4 and when installed in the uConsole it also requires patching an old kernel to boot and address the display. There are users in the Discord working on getting other kernels and distros working, but we’re all amateurs to varying degrees.

The hardware’s cool but the software’s very much DIY. If you’re not an aspiring kernel developer, I’d recommend using the default distros for now?

---

<div class="post-metadata">

**Author:** ![MHam68HC11](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/mham68hc11/32/5046_2.png) [@MHam68HC11](https://forum.clockworkpi.com/u/MHam68HC11)\
**Post date:** [February 10, 2024, 8:41pm UTC](https://forum.clockworkpi.com/t/what-a-mess-with-clockpi-a06/12423/4 "2024-02-10T20:41:53Z")

</div>

Are you using standard build or custom? - my recommendation is based on the standard Clockwork distribution - should have been more exact - I’m seeing issues with the A-06 with the Clockwork image on the A-06 Devterm (screen going to sleep and not recovering) - I did not understand the discussion was a custom build (kali linux and Dragon OS should have been a clue)

---

<div class="post-metadata">

**Author:** ![mikeschnier](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/mikeschnier/32/9697_2.png) [@mikeschnier](https://forum.clockworkpi.com/u/mikeschnier)\
**Post date:** [February 10, 2024, 9:17pm UTC](https://forum.clockworkpi.com/t/what-a-mess-with-clockpi-a06/12423/5 "2024-02-10T21:17:18Z")

</div>

I tried compiling a kernel myself but my first attempt wasn’t successful. I’m currently using the XFCE build (based on Raspberry Pi OS Lite) that ClockworkPi provided.

---

<div class="post-metadata">

**Author:** ![MHam68HC11](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/mham68hc11/32/5046_2.png) [@MHam68HC11](https://forum.clockworkpi.com/u/MHam68HC11)\
**Post date:** [February 10, 2024, 11:01pm UTC](https://forum.clockworkpi.com/t/what-a-mess-with-clockpi-a06/12423/6 "2024-02-10T23:01:15Z")

</div>

which processor are you working with? I’ve got the R-01 and CM4 running didn’t bother with the A-06 since I’ve had issues with that processor on the DevTerm.

---

<div class="post-metadata">

**Author:** ![mikeschnier](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/mikeschnier/32/9697_2.png) [@mikeschnier](https://forum.clockworkpi.com/u/mikeschnier)\
**Post date:** [February 10, 2024, 11:23pm UTC](https://forum.clockworkpi.com/t/what-a-mess-with-clockpi-a06/12423/7 "2024-02-10T23:23:02Z")

</div>

CM4, which is why I mentioned the Raspberry Pi OS Lite-based distro.

---

<div class="post-metadata">

**Author:** ![aliosa27](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/aliosa27/32/8949_2.png) [@aliosa27](https://forum.clockworkpi.com/u/aliosa27)\
**Post date:** [February 12, 2024, 5:46pm UTC](https://forum.clockworkpi.com/t/what-a-mess-with-clockpi-a06/12423/8 "2024-02-12T17:46:03Z")

</div>

can you post your apt-get output, this is less of an issue with the a06, and just silly apt shenanigans. Thats how it goes in the oss world

---

<div class="post-metadata">

**Author:** ![fe8769](https://avatars.discourse-cdn.com/v4/letter/f/858c86/32.png) [@fe8769](https://forum.clockworkpi.com/u/fe8769)\
**Post date:** [February 13, 2024, 6:11pm UTC](https://forum.clockworkpi.com/t/what-a-mess-with-clockpi-a06/12423/9 "2024-02-13T18:11:29Z")

</div>

With standard linux , first command line are  
sudo apt-get update  
sudo apt-get upgrade  
sudo apt-get dist-upgrade

With original clockpi A06 image here is the result , apt-get update can’t be done

sudo apt-get update  
Hit:2 [http://ports.ubuntu.com](http://ports.ubuntu.com) jammy InRelease  
Hit:3 [Index of /saiarcot895/chromium-beta/ubuntu](http://ppa.launchpadcontent.net/saiarcot895/chromium-beta/ubuntu) jammy InRelease  
Get:4 [Index of /mozillateam/ppa/ubuntu](http://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu) jammy InRelease [23.8 kB]  
Get:5 [http://ports.ubuntu.com](http://ports.ubuntu.com) jammy-security InRelease [110 kB]  
Get:8 [Index of /oibaf/graphics-drivers/ubuntu](http://ppa.launchpadcontent.net/oibaf/graphics-drivers/ubuntu) jammy InRelease [23.9 kB]  
Get:9 [https://raw.githubusercontent.com/clockworkpi/apt/main/debian](https://raw.githubusercontent.com/clockworkpi/apt/main/debian) stable InRelease [5,408 B]  
Get:11 [http://ports.ubuntu.com](http://ports.ubuntu.com) jammy-updates InRelease [119 kB]  
Get:1 [https://cli.github.com/packages](https://cli.github.com/packages) stable InRelease [3,917 B]  
Hit:12 [http://ports.ubuntu.com](http://ports.ubuntu.com) jammy-backports InRelease  
Hit:6 [https://paulcarroty.gitlab.io/vscodium-deb-rpm-repo/debs](https://paulcarroty.gitlab.io/vscodium-deb-rpm-repo/debs) vscodium InRelease  
Get:7 [https://box64.debian.ryanfortner.dev/debian](https://box64.debian.ryanfortner.dev/debian) ./ InRelease [2,115 B]  
Hit:10 [Index of /apt/](http://xogium.performanceservers.nl/apt) jammy InRelease  
Get:13 [Index of /mozillateam/ppa/ubuntu](http://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu) jammy/main armhf Packages [42.9 kB]  
Get:14 [Index of /mozillateam/ppa/ubuntu](http://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu) jammy/main arm64 Packages [42.9 kB]  
Get:15 [Index of /oibaf/graphics-drivers/ubuntu](http://ppa.launchpadcontent.net/oibaf/graphics-drivers/ubuntu) jammy/main armhf Packages [15.8 kB]  
Get:16 [Index of /oibaf/graphics-drivers/ubuntu](http://ppa.launchpadcontent.net/oibaf/graphics-drivers/ubuntu) jammy/main arm64 Packages [15.5 kB]  
Get:17 [http://ports.ubuntu.com](http://ports.ubuntu.com) jammy-security/main arm64 Packages [1,223 kB]  
Err:1 [https://cli.github.com/packages](https://cli.github.com/packages) stable InRelease  
The following signatures couldn’t be verified because the public key is not available: NO\_PUBKEY 23F3D4EA75716059  
Get:18 [http://ports.ubuntu.com](http://ports.ubuntu.com) jammy-security/universe arm64 Packages [993 kB]  
Get:19 [https://box64.debian.ryanfortner.dev/debian](https://box64.debian.ryanfortner.dev/debian) ./ Packages [3,620 B]  
Get:20 [http://ports.ubuntu.com](http://ports.ubuntu.com) jammy-security/universe armhf Packages [736 kB]  
Get:21 [http://ports.ubuntu.com](http://ports.ubuntu.com) jammy-security/main armhf Packages [701 kB]  
Get:22 [http://ports.ubuntu.com](http://ports.ubuntu.com) jammy-security/restricted arm64 Packages [1,212 kB]  
Get:23 [http://ports.ubuntu.com](http://ports.ubuntu.com) jammy-updates/main armhf Packages [965 kB]  
Get:24 [http://ports.ubuntu.com](http://ports.ubuntu.com) jammy-updates/main arm64 Packages [1,494 kB]  
Get:25 [http://ports.ubuntu.com](http://ports.ubuntu.com) jammy-updates/universe arm64 Packages [1,262 kB]  
Get:26 [http://ports.ubuntu.com](http://ports.ubuntu.com) jammy-updates/universe armhf Packages [1,001 kB]  
Get:27 [http://ports.ubuntu.com](http://ports.ubuntu.com) jammy-updates/restricted arm64 Packages [1,231 kB]  
Ign:28 [http://deb.volian.org/volian](http://deb.volian.org/volian) scar InRelease  
Ign:28 [http://deb.volian.org/volian](http://deb.volian.org/volian) scar InRelease  
Ign:28 [http://deb.volian.org/volian](http://deb.volian.org/volian) scar InRelease  
Err:28 [http://deb.volian.org/volian](http://deb.volian.org/volian) scar InRelease  
Could not connect to [deb.volian.org:80](http://deb.volian.org:80) (99.118.93.168), connection timed out  
Fetched 11.2 MB in 38s (298 kB/s)  
Reading package lists… Done  
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: [https://cli.github.com/packages](https://cli.github.com/packages) stable InRelease: The following signatures couldn’t be verified because the public key is not available: NO\_PUBKEY 23F3D4EA75716059  
W: Failed to fetch [http://cli.github.com/packages/dists/stable/InRelease](http://cli.github.com/packages/dists/stable/InRelease) The following signatures couldn’t be verified because the public key is not available: NO\_PUBKEY 23F3D4EA75716059  
W: Failed to fetch [http://deb.volian.org/volian/dists/scar/InRelease](http://deb.volian.org/volian/dists/scar/InRelease) Could not connect to [deb.volian.org:80](http://deb.volian.org:80) (99.118.93.168), connection timed out  
W: Some index files failed to download. They have been ignored, or old ones used instead.

---

<div class="post-metadata">

**Author:** ![Nomine\_Vacans](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/nomine_vacans/32/4622_2.png) [@Nomine\_Vacans](https://forum.clockworkpi.com/u/Nomine_Vacans)\
**Post date:** [February 14, 2024, 8:15am UTC](https://forum.clockworkpi.com/t/what-a-mess-with-clockpi-a06/12423/10 "2024-02-14T08:15:23Z")

</div>

that last error was on the side of volian. it works now.  
the github cli one can be ignored for most users, but to fix it:

wget [https://cli.github.com/packages/githubcli-archive-keyring.gpg](https://cli.github.com/packages/githubcli-archive-keyring.gpg)  
sudo mv githubcli-archive-keyring.gpg /usr/share/keyrings/githubcli.gpg

expired keys are sure annoying, but not the fault of clockworkpi.  
what is a more annoying is the patchy documentation on literally anything…

---

<div class="post-metadata">

**Author:** ![fe8769](https://avatars.discourse-cdn.com/v4/letter/f/858c86/32.png) [@fe8769](https://forum.clockworkpi.com/u/fe8769)\
**Post date:** [February 16, 2024, 4:55pm UTC](https://forum.clockworkpi.com/t/what-a-mess-with-clockpi-a06/12423/11 "2024-02-16T16:55:47Z")

</div>

Thanks it is working fine

---

<div class="post-metadata">

**Author:** ![Lotech](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/lotech/32/10323_2.png) [@Lotech](https://forum.clockworkpi.com/u/Lotech)\
**Post date:** [February 18, 2024, 1:41am UTC](https://forum.clockworkpi.com/t/what-a-mess-with-clockpi-a06/12423/12 "2024-02-18T01:41:31Z")

</div>

That greatly discourage me from joining the game ! I’m from Pi 4 so I know how it performs, and want to get something similar with everything out of the box. I initially planned to pickup the uConsole to replace my tablet, as it got the 4G module. I first decided to get the emmc CM4 as I do not trust uSD, I’ve got some bad cards from cell phone use. But the emmc CM4 got only 32G so that I changed my mind, and planned to go for the CM4 without emmc but with 8G of RAM, more memory hopefully reduce r/w to the card to extend it’s life. I read on the Raspberry website there’s a CM4 with 8G of RAM w/o emmc (CM4008000), and in here there’s A-06 with 4G of RAM, but on other post some said he got the A-06 with 8G I’m confused, is there a hidden menu on the ordering page we don’t normally see ? and how long the A-06 has been released, how come it still not well supported, I read many comments on setting up the A-06 was a pain. I will not do crazy things with the device, I just want a small working mobile computer for daily use, and I can’t find any alternatives can fit the bill.

---

<div class="post-metadata">

**Author:** ![MHam68HC11](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/mham68hc11/32/5046_2.png) [@MHam68HC11](https://forum.clockworkpi.com/u/MHam68HC11)\
**Post date:** [February 18, 2024, 4:12am UTC](https://forum.clockworkpi.com/t/what-a-mess-with-clockpi-a06/12423/13 "2024-02-18T04:12:56Z")

</div>

I have the CM4 with 4GB - it runs webpages, discord, spyder ide, even visual studio (code) email and open office - some have even ran a Software Defined Radio receiver on it… which is very processor heavy… I would not get a CM4 with less than 4GB - i went non EMMC memory since it won’t boot from the main board SD card and you will have to flash the EMMC with the OS… I use a 64GB card I believe up to 250GB will work - I’ve already corrupted some programs and had to reload - so keep a build log and back up the image occasionally …

---

<div class="post-metadata">

**Author:** ![barry99705](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/barry99705/32/6771_2.png) [@barry99705](https://forum.clockworkpi.com/u/barry99705)\
**Post date:** [February 18, 2024, 3:44pm UTC](https://forum.clockworkpi.com/t/what-a-mess-with-clockpi-a06/12423/14 "2024-02-18T15:44:07Z")

</div>

As far as I know, we’re the only hobby platform running the A-06. Since clockwork is a niche within a niche, there’s practically zero support.

---

<div class="post-metadata">

**Author:** ![MHam68HC11](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/mham68hc11/32/5046_2.png) [@MHam68HC11](https://forum.clockworkpi.com/u/MHam68HC11)\
**Post date:** [February 19, 2024, 2:55am UTC](https://forum.clockworkpi.com/t/what-a-mess-with-clockpi-a06/12423/15 "2024-02-19T02:55:43Z")

</div>

That’s why I purchased two Cm4 adapter boards - I intend to convert my DevTerm over to CM4… using the stock image from Clockwork… the A-06 has an issue with screen lock up on sleep…

---

<div class="post-metadata">

**Author:** ![barry99705](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/barry99705/32/6771_2.png) [@barry99705](https://forum.clockworkpi.com/u/barry99705)\
**Post date:** [February 19, 2024, 1:06pm UTC](https://forum.clockworkpi.com/t/what-a-mess-with-clockpi-a06/12423/16 "2024-02-19T13:06:36Z")

</div>

Yea, none of these chips actually do sleep properly. It’s not a thing for these chips. The pi can fake it better though.
