DevTerm OS R01 image files

DevTerm Firmware and Apps
1

Latest official DevTerm R01 image files here:

DevTerm R01

Download：
http://dl.clockworkpi.com/DevTerm_R01_v0.2a.img.bz2 ==> Mirror #1 ==> Torrent
md5sum: 49aa472a6e4d81a48e0ala26436f02c2
Size: 2.8G

Release Note:

(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

3 Likes
2

Can we upgrade to this from an existing installation, or should we reinstall?

3

Also I assume this should be in the DevTerm topic, not GameShell…

4

You have to do a fresh reinstall with this OS image. Thanks for the category correction.

5

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?

6

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?
  • ???
3 Likes
7

@guu please update R01 OS build wiki (I don’t know how to edit that):

  • The ubuntu system needs these packages:
   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:
#!/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
1 Like
8

packages cli commands appended to the wiki

as for the additional script

If I remember correctly, apt will do the job automatically?

9

No :upside_down_face:
Indeed there are multiple versions of gcc in the repo now (9-12), but update-alternative shows nothing, so manual linking is required.

1 Like
10

R01 os image added wtih @yatli 's fbturbo patch

For people who wants to try but dont want re-flash sd card

here is:

sudo apt update
sudo apt install -y xf86-video-fbturbo-r01
sudo reboot
1 Like
11

@guu @ChipMaster

This will fix the console cursor issue

1 Like
12

Is this available prebuilt, with install instructions from some place?

13

I’m sure @guu will package that :slight_smile:

^^ I think this will fix the terminal scrollback issues. Thanks for your effort for packaging!

2 Likes
14

Thanks soooo much for your efforts on this. I look forward to these fixes.

15

apt package updated, 0.2

here is how to update in R01 :

sudo apt update
sudo apt install -y xf86-video-fbturbo-r01
sudo reboot
16

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.

17

oh
I am so sorry

but you still can ssh into DT right?

try to remove these files to bring X back

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
18

I’ve tested these cli commands on R01 0.2a and 0.3 os image

it seems fine

what is your R01 os version ?

19

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!

20

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…