# DevTerm OS R01 image files **URL:** \ **Category:** Firmware and Apps\ **Tags:** firmware\ **Created:** [September 7, 2022, 4:14pm UTC](https://forum.clockworkpi.com/t/devterm-os-r01-image-files/8890 "2022-09-07T16:14:12Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![yong](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/yong/32/73_2.png) [@yong](https://forum.clockworkpi.com/u/yong)\ **Post date:** [September 7, 2022, 4:14pm UTC](https://forum.clockworkpi.com/t/devterm-os-r01-image-files/8890/1 "2022-09-07T16:14:12Z")
**Latest official DevTerm R01 image files here:** - [DevTerm R01 OS v0.2a](http://dl.clockworkpi.com/DevTerm_R01_v0.2a.img.bz2) [![DevTerm R01](https://canada1.discourse-cdn.com/flex029/uploads/clockworkpi/original/2X/2/2a946cc7419b00e1dbafffb914cf29472eaf5179.png)](http://dl.clockworkpi.com/DevTerm_R01_v0.2a.img.bz2) **Download：** [http://dl.clockworkpi.com/DevTerm\_R01\_v0.2a.img.bz2](http://dl.clockworkpi.com/DevTerm_R01_v0.2a.img.bz2) ==\> [Mirror #1](https://wiki.clockworkpi.com/images/files/DevTerm_R01_v0.2a.img.bz2) ==\> [Torrent](https://wiki.clockworkpi.com/images/files/DevTerm_R01_v0.2a.img.bz2.torrent) md5sum: 49aa472a6e4d81a48e0ala26436f02c2 Size: 2.8G **Release Note:** ```auto (R01 OS v0.2a) powered by ubuntu RISC-V 64 Architecture - Based on RISC-V Ubuntu 22.04* LTS Jammy - Linux kernel v5.4.61 - TWM (Tab Window Manager) with optimized configuration. - Rechargeable battery energy management - Standard CUPS thermal printer driver support ``` A BIG THANK YOU to the open source ecosystem and all supporters from around the world! **How to create DevTerm R01 OS image from scratch** - Following the principle of minimal changes [https://www.github.com/clockworkpi/DevTerm/wiki/Create-DevTerm-RO1-OS-image-from-scratch](https://www.github.com/clockworkpi/DevTerm/wiki/Create-DevTerm-RO1-OS-image-from-scratch) * * * ---
**Author:** ![andypiper](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/andypiper/32/7970_2.png) [@andypiper](https://forum.clockworkpi.com/u/andypiper)\ **Post date:** [September 8, 2022, 12:40am UTC](https://forum.clockworkpi.com/t/devterm-os-r01-image-files/8890/2 "2022-09-08T00:40:19Z")
Can we upgrade to this from an existing installation, or should we reinstall? ---
**Author:** ![andypiper](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/andypiper/32/7970_2.png) [@andypiper](https://forum.clockworkpi.com/u/andypiper)\ **Post date:** [September 8, 2022, 12:40am UTC](https://forum.clockworkpi.com/t/devterm-os-r01-image-files/8890/3 "2022-09-08T00:40:58Z")
Also I assume this should be in the DevTerm topic, not GameShell… ---
**Author:** ![yong](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/yong/32/73_2.png) [@yong](https://forum.clockworkpi.com/u/yong)\ **Post date:** [September 8, 2022, 3:47am UTC](https://forum.clockworkpi.com/t/devterm-os-r01-image-files/8890/4 "2022-09-08T03:47:57Z")
You have to do a fresh reinstall with this OS image. Thanks for the category correction. ---
**Author:** ![Daeraxa](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/daeraxa/32/6256_2.png) [@Daeraxa](https://forum.clockworkpi.com/u/Daeraxa)\ **Post date:** [September 11, 2022, 11:11pm UTC](https://forum.clockworkpi.com/t/devterm-os-r01-image-files/8890/5 "2022-09-11T23:11:28Z")
Qutebrowser is bundled with the image and I’m sure it was working fine on the previous version but now it just seems to crash on me - it comes up with a python segmentation fault (as shown by the crash report). Is anyone else having the same issue? ---
**Author:** ![ChipMaster](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/chipmaster/32/6412_2.png) [@ChipMaster](https://forum.clockworkpi.com/u/ChipMaster)\ **Post date:** [September 12, 2022, 5:25pm UTC](https://forum.clockworkpi.com/t/devterm-os-r01-image-files/8890/6 "2022-09-12T17:25:32Z")
Thanks for the update. But you forgot to mention why we might actually want it? The specs you mention seem to be the same as I already had. I’ve invested a lot of effort into building an environment that is beginning to approach being useful and functional. So, please, tell me why it might be good for me to scrap everything and start over? - Did you fix the cursor in the console driver? - Did you improve the framebuffer write speed? - Better font selection in the non-CUPS print driver? - The kernel now includes the input-mousedev driver? - ??? ---
**Author:** ![yatli](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/yatli/32/6253_2.png) [@yatli](https://forum.clockworkpi.com/u/yatli)\ **Post date:** [February 18, 2023, 6:10pm UTC](https://forum.clockworkpi.com/t/devterm-os-r01-image-files/8890/7 "2023-02-18T18:10:24Z")
@guu please update R01 OS build wiki (I don’t know how to edit that): - The ubuntu system needs these packages: ```auto 18 sudo apt install gcc-11-riscv64-linux-gnu binutils-riscv64-linux-gnu qemu-user-static 19 sudo apt install git 21 sudo apt install make 47 sudo apt install build-essential 49 sudo apt install libfontconfig1 53 sudo apt install ncurses-devel 54 sudo apt install libncurses-dev 56 sudo apt install build-essential 57 sudo apt install flex bison 60 sudo apt install python3-distutils 62 sudo apt install swig 64 sudo apt install python3-dev 66 sudo apt install openssl 68 sudo apt install libssl-dev ``` - additionally, run this script: ```auto #!/bin/bash sudo ln -s /usr/bin/riscv64-linux-gnu-cpp-11 /usr/bin/riscv64-linux-gnu-cpp sudo ln -s /usr/bin/riscv64-linux-gnu-gcc-nm-11 /usr/bin/riscv64-linux-gnu-gcc-nm sudo ln -s /usr/bin/riscv64-linux-gnu-gcov-dump-11 /usr/bin/riscv64-linux-gnu-gcov-dump sudo ln -s /usr/bin/riscv64-linux-gnu-gcc-11 /usr/bin/riscv64-linux-gnu-gcc sudo ln -s /usr/bin/riscv64-linux-gnu-gcc-ranlib-11 /usr/bin/riscv64-linux-gnu-gcc-ranlib sudo ln -s /usr/bin/riscv64-linux-gnu-gcov-tool-11 /usr/bin/riscv64-linux-gnu-gcov-tool sudo ln -s /usr/bin/riscv64-linux-gnu-gcc-ar-11 /usr/bin/riscv64-linux-gnu-gcc-ar sudo ln -s /usr/bin/riscv64-linux-gnu-gcov-11 /usr/bin/riscv64-linux-gnu-gcov sudo ln -s /usr/bin/riscv64-linux-gnu-lto-dump-11 /usr/bin/riscv64-linux-gnu-lto-dump ``` ---
**Author:** ![guu](https://avatars.discourse-cdn.com/v4/letter/g/7ab992/32.png) [@guu](https://forum.clockworkpi.com/u/guu)\ **Post date:** [February 18, 2023, 11:04pm UTC](https://forum.clockworkpi.com/t/devterm-os-r01-image-files/8890/8 "2023-02-18T23:04:31Z")
packages cli commands appended to the wiki as for the additional script If I remember correctly, apt will do the job automatically? ---
**Author:** ![yatli](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/yatli/32/6253_2.png) [@yatli](https://forum.clockworkpi.com/u/yatli)\ **Post date:** [February 18, 2023, 11:57pm UTC](https://forum.clockworkpi.com/t/devterm-os-r01-image-files/8890/9 "2023-02-18T23:57:16Z")
No 🙃 Indeed there are multiple versions of gcc in the repo now (9-12), but `update-alternative` shows nothing, so manual linking is required. ---
**Author:** ![guu](https://avatars.discourse-cdn.com/v4/letter/g/7ab992/32.png) [@guu](https://forum.clockworkpi.com/u/guu)\ **Post date:** [February 23, 2023, 8:31am UTC](https://forum.clockworkpi.com/t/devterm-os-r01-image-files/8890/10 "2023-02-23T08:31:05Z")
> **[1.78 GB file on MEGA](https://mega.nz/file/MUcVgbDb#vLz7k7yIDVFbHFwr8-P6BSSqJJJ6ZnKw0s4XCXdCKts)** R01 os image added wtih @yatli 's fbturbo patch > [@R01, fbturbo: Accelerated 2D graphics in X11](https://forum.clockworkpi.com/t/r01-fbturbo-accelerated-2d-graphics-in-x11/8900/11): > > I used it for a full day and still find some glitches: Kernel oops about buffer overflow Terminal scrollback sometimes damage one line or two, when scrolled height \>= 128 I’ll let you know when I fix these issues. Let’s make R01 perfect slight_smile For people who wants to try but dont want re-flash sd card here is: ```auto sudo apt update sudo apt install -y xf86-video-fbturbo-r01 sudo reboot ``` ---
**Author:** ![yatli](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/yatli/32/6253_2.png) [@yatli](https://forum.clockworkpi.com/u/yatli)\ **Post date:** [February 23, 2023, 4:33pm UTC](https://forum.clockworkpi.com/t/devterm-os-r01-image-files/8890/11 "2023-02-23T16:33:49Z")
@guu @ChipMaster > This will fix the console cursor issue ---
**Author:** ![ChipMaster](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/chipmaster/32/6412_2.png) [@ChipMaster](https://forum.clockworkpi.com/u/ChipMaster)\ **Post date:** [February 23, 2023, 5:43pm UTC](https://forum.clockworkpi.com/t/devterm-os-r01-image-files/8890/12 "2023-02-23T17:43:10Z")
> [@yatli](#): > > This will fix the console cursor issue Is this available prebuilt, with install instructions from some place? ---
**Author:** ![yatli](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/yatli/32/6253_2.png) [@yatli](https://forum.clockworkpi.com/u/yatli)\ **Post date:** [February 23, 2023, 6:47pm UTC](https://forum.clockworkpi.com/t/devterm-os-r01-image-files/8890/13 "2023-02-23T18:47:15Z")
I’m sure @guu will package that 🙂 > **[Release v0.2 (DevTerm R01 only) · yatli/xf86-video-fbturbo](https://github.com/yatli/xf86-video-fbturbo/releases/tag/v0.2)** > > Fix terminal scrollback glitches ^^ I think this will fix the terminal scrollback issues. Thanks for your effort for packaging! ---
**Author:** ![ChipMaster](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/chipmaster/32/6412_2.png) [@ChipMaster](https://forum.clockworkpi.com/u/ChipMaster)\ **Post date:** [February 23, 2023, 7:29pm UTC](https://forum.clockworkpi.com/t/devterm-os-r01-image-files/8890/14 "2023-02-23T19:29:54Z")
Thanks soooo much for your efforts on this. I look forward to these fixes. ---
**Author:** ![guu](https://avatars.discourse-cdn.com/v4/letter/g/7ab992/32.png) [@guu](https://forum.clockworkpi.com/u/guu)\ **Post date:** [February 24, 2023, 1:24am UTC](https://forum.clockworkpi.com/t/devterm-os-r01-image-files/8890/15 "2023-02-24T01:24:30Z")
apt package updated, 0.2 here is how to update in R01 : ```auto sudo apt update sudo apt install -y xf86-video-fbturbo-r01 sudo reboot ``` ---
**Author:** ![ChipMaster](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/chipmaster/32/6412_2.png) [@ChipMaster](https://forum.clockworkpi.com/u/ChipMaster)\ **Post date:** [February 24, 2023, 5:28pm UTC](https://forum.clockworkpi.com/t/devterm-os-r01-image-files/8890/16 "2023-02-24T17:28:29Z")
Well that basically bricked my DevTerm R01. Its now locked in an endless loop trying to start X, crashing, retrying, … I’ll look at it more when I have some time… or just restore what worked. ---
**Author:** ![guu](https://avatars.discourse-cdn.com/v4/letter/g/7ab992/32.png) [@guu](https://forum.clockworkpi.com/u/guu)\ **Post date:** [February 25, 2023, 4:59am UTC](https://forum.clockworkpi.com/t/devterm-os-r01-image-files/8890/17 "2023-02-25T04:59:59Z")
oh I am so sorry but you still can ssh into DT right? try to remove these files to bring X back ```auto sudo rm /etc/X11/xorg.conf.d/10-d1.conf sudo rm -rf /usr/lib/xorg/modules/drivers/fbturbo_drv.* sudo rm -rf /usr/local/bin/r01-dispfd-daemon.elf ``` ---
**Author:** ![guu](https://avatars.discourse-cdn.com/v4/letter/g/7ab992/32.png) [@guu](https://forum.clockworkpi.com/u/guu)\ **Post date:** [February 25, 2023, 5:06am UTC](https://forum.clockworkpi.com/t/devterm-os-r01-image-files/8890/18 "2023-02-25T05:06:52Z")
I’ve tested these cli commands on R01 0.2a and 0.3 os image it seems fine what is your R01 os version ? ---
**Author:** ![yatli](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/yatli/32/6253_2.png) [@yatli](https://forum.clockworkpi.com/u/yatli)\ **Post date:** [February 25, 2023, 6:21am UTC](https://forum.clockworkpi.com/t/devterm-os-r01-image-files/8890/19 "2023-02-25T06:21:15Z")
If possible, could you please also pull out a copy of Xorg crash log? `scp cpi@r01-address:/var/log/Xorg.0.log ./` We can learn more about how it end up crash and burn with that file. Thanks! ---
**Author:** ![ChipMaster](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/chipmaster/32/6412_2.png) [@ChipMaster](https://forum.clockworkpi.com/u/ChipMaster)\ **Post date:** [February 25, 2023, 4:37pm UTC](https://forum.clockworkpi.com/t/devterm-os-r01-image-files/8890/20 "2023-02-25T16:37:38Z")
> [@guu](#): > > I’ve tested these cli commands on R01 0.2a and 0.3 os image > [@yatli](#): > > If possible, could you please also pull out a copy of Xorg crash log? Hi guys! And thanks for the concern. As you probably already deduced I’m still on v0.1. You’ll see my question near the top of this thread asking about why I should upgrade. I never received a response. At least not that I was notified about. I spent a few days of concentrated time banging on v0.1 to make it usable. To throw all that effort out and start over was too much and as far as I known an `apt-get update; apt-get upgrade` isn’t going to do it. I’m not going to throw out all that effort just because you say so. In short the message I’m getting is a missing dri device which I’m sure is because of a kernel change after v0.1. Because I was foolish enough to trust the upgrade instructions above and not do a full backup I may have lost all my effort anyways. If that’s the case this will have to go back in the closet for the foreseeable future I don’t have time right now to make it useful. And likely won’t for months to come. Another _mirage_… device. I’ll probably just watch and wait until it seems like the glaring issues have been addressed before I dedicate the needed time to it. And I still have to figure out how to get a clock into it… **All** the GPIO was a _mirage_ too. Oh! And I don’t see a v0.3 anywhere… [Next page](https://forum.clockworkpi.com/t/devterm-os-r01-image-files/8890.md?page=2)