<![CDATA[PINE64 - Linux on Rock64]]> https://forum.pine64.org/ Tue, 12 May 2026 08:13:13 +0000 MyBB <![CDATA[A/V output enable]]> https://forum.pine64.org/showthread.php?tid=20227 Tue, 24 Mar 2026 22:45:39 +0000 8lall0]]> https://forum.pine64.org/showthread.php?tid=20227 Hello everyone!

I have a Rock64, but i cannot get the A/V jack to output video.

Do you have any hints?

Thanks!]]> Hello everyone!

I have a Rock64, but i cannot get the A/V jack to output video.

Do you have any hints?

Thanks!]]> <![CDATA[OpenClaw]]> https://forum.pine64.org/showthread.php?tid=20197 Sun, 22 Feb 2026 17:57:20 +0000 keithy]]> https://forum.pine64.org/showthread.php?tid=20197
(Just wanted to share my recent success)



Downloaded community rolling release minimal Arabian image from:

https://www.armbian.com/rock64/

Etchered onto 4Gb SD-Card.



Booted, user:root pass:1234

Added ssh key, disable root password.

Ran the armbian-update



$> sudo apt-get install f2fs-tools

$> armbian-config (transfer os to internal emmc 

(this worked like a charm, uses f2fs and leave /boot as ext)



$>  sudo apt-get install git

$>  sudo apt-get install apt-transport-https



Using podman required the following dependencies:

$> apt install uidmap

$> apt install nftables

$> apt install catatonit

$> apt install passt

$> apt install podman

$> apt install podman-compose



$> git clone --depth 10 https://github.com/openclaw/openclaw



$> # tmp isn’t big enough for the next steps

$> mount -o remount,size=2600M /tmp



$> cd openclaw

$> ./setup-podman.sh --quadlet

$> sudo systemctl --machine openclaw@ --user start openclaw.service

However, I struggled to access logs of what was going on inside podman.

Plan B mise-en-place managed tools

Install mise-en-place using apt
from: https://mise.jdx.dev/installing-mise.html

Code:
sudo apt update -y && sudo apt install -y curl
sudo install -dm 755 /etc/apt/keyrings
curl -fSs https://mise.jdx.dev/gpg-key.pub | sudo tee /etc/apt/keyrings/mise-archive-keyring.asc 1> /dev/null
echo "deb [signed-by=/etc/apt/keyrings/mise-archive-keyring.asc] https://mise.jdx.dev/deb stable main" | sudo tee /etc/apt/sources.list.d/mise.list
sudo apt update -y
sudo apt install -y mise

As user claw.

Add activation to ~/.bashrc
$> echo 'eval "$(mise activate bash)"' >> ~/.bashrc

$> mise use -g node@22
$> mise use -g pnpm
$> mise settings set npm.package_manager pnpm
$> mise use -g npm:openclaw
$> which openclaw
$> /home/claw/.local/share/mise/installs/npm-openclaw/2026.2.21-2/bin/openclaw
$> openclaw onboard
]]>
(Just wanted to share my recent success)



Downloaded community rolling release minimal Arabian image from:

https://www.armbian.com/rock64/

Etchered onto 4Gb SD-Card.



Booted, user:root pass:1234

Added ssh key, disable root password.

Ran the armbian-update



$> sudo apt-get install f2fs-tools

$> armbian-config (transfer os to internal emmc 

(this worked like a charm, uses f2fs and leave /boot as ext)



$>  sudo apt-get install git

$>  sudo apt-get install apt-transport-https



Using podman required the following dependencies:

$> apt install uidmap

$> apt install nftables

$> apt install catatonit

$> apt install passt

$> apt install podman

$> apt install podman-compose



$> git clone --depth 10 https://github.com/openclaw/openclaw



$> # tmp isn’t big enough for the next steps

$> mount -o remount,size=2600M /tmp



$> cd openclaw

$> ./setup-podman.sh --quadlet

$> sudo systemctl --machine openclaw@ --user start openclaw.service

However, I struggled to access logs of what was going on inside podman.

Plan B mise-en-place managed tools

Install mise-en-place using apt
from: https://mise.jdx.dev/installing-mise.html

Code:
sudo apt update -y && sudo apt install -y curl
sudo install -dm 755 /etc/apt/keyrings
curl -fSs https://mise.jdx.dev/gpg-key.pub | sudo tee /etc/apt/keyrings/mise-archive-keyring.asc 1> /dev/null
echo "deb [signed-by=/etc/apt/keyrings/mise-archive-keyring.asc] https://mise.jdx.dev/deb stable main" | sudo tee /etc/apt/sources.list.d/mise.list
sudo apt update -y
sudo apt install -y mise

As user claw.

Add activation to ~/.bashrc
$> echo 'eval "$(mise activate bash)"' >> ~/.bashrc

$> mise use -g node@22
$> mise use -g pnpm
$> mise settings set npm.package_manager pnpm
$> mise use -g npm:openclaw
$> which openclaw
$> /home/claw/.local/share/mise/installs/npm-openclaw/2026.2.21-2/bin/openclaw
$> openclaw onboard
]]> <![CDATA[Rock64 v3 Tx/RX and GPIO connections for 3dprinter]]> https://forum.pine64.org/showthread.php?tid=20165 Wed, 14 Jan 2026 00:43:23 +0000 MinimumJargon]]> https://forum.pine64.org/showthread.php?tid=20165 I can't seem to figure out the serial connection. I have gotten the Rock64 to run the printer with no problem over USB.

I'm not a strong Linux user, but I managed to make it to the very end here, but I can't get this last part to work.
I feel I'm either missing the correct terms in overlays/ the correct kerral header/ or some permissions or conflict.

I'm trying to use UART2, which are the same pins as the pi w2 zero. 6,8,10
I think I have the serial console disable. I ran:
sudo systemctl mask serial-getty@ttyS2
and see nothing on tty2 now when I run ls /dev/ttyS*

I added to armbianEvn.txt

Code:
overlays=uart1 uart2 uart3


and added users to the dialout group and confirmed. 

I'm not sure about the Kernel header, and one post mentions some jumper pin for the header, but I'm pretty much past the point of my knowledge base, and I'm not sure what to search at this point.

Any direction or information anyone can offer would be appreciated.]]> I can't seem to figure out the serial connection. I have gotten the Rock64 to run the printer with no problem over USB.

I'm not a strong Linux user, but I managed to make it to the very end here, but I can't get this last part to work.
I feel I'm either missing the correct terms in overlays/ the correct kerral header/ or some permissions or conflict.

I'm trying to use UART2, which are the same pins as the pi w2 zero. 6,8,10
I think I have the serial console disable. I ran:
sudo systemctl mask serial-getty@ttyS2
and see nothing on tty2 now when I run ls /dev/ttyS*

I added to armbianEvn.txt

Code:
overlays=uart1 uart2 uart3


and added users to the dialout group and confirmed. 

I'm not sure about the Kernel header, and one post mentions some jumper pin for the header, but I'm pretty much past the point of my knowledge base, and I'm not sure what to search at this point.

Any direction or information anyone can offer would be appreciated.]]> <![CDATA[Rock64 - not booting after Armbian update]]> https://forum.pine64.org/showthread.php?tid=19758 Tue, 25 Mar 2025 23:03:59 +0000 helpmerock]]> https://forum.pine64.org/showthread.php?tid=19758  
Was working fine with Armbian 24.5.0-trunk.211_Rock64_bookworm_current_6.6.21 - boot from micro SD card

On SSH, I updated to latest version Armbian_25.2.1_Rock64_bookworm_current_6.12.13. Now it does not boot from micro SD card.

I had another micro sd card. I flashed new Armbian_25.2.1_Rock64_bookworm_current_6.12.13 - does not boot.

I had another micro sd card. I flashed OLD Armbian 24.5.0-trunk.211_Rock64_bookworm_current_6.6.21 - it boots. Then updated to latest Armbian & does not boot anymore.

Looks like some " Flashing_u-boot_to_SPI_Flash " - problem.

Please help.

Thanks in advanced]]>  
Was working fine with Armbian 24.5.0-trunk.211_Rock64_bookworm_current_6.6.21 - boot from micro SD card

On SSH, I updated to latest version Armbian_25.2.1_Rock64_bookworm_current_6.12.13. Now it does not boot from micro SD card.

I had another micro sd card. I flashed new Armbian_25.2.1_Rock64_bookworm_current_6.12.13 - does not boot.

I had another micro sd card. I flashed OLD Armbian 24.5.0-trunk.211_Rock64_bookworm_current_6.6.21 - it boots. Then updated to latest Armbian & does not boot anymore.

Looks like some " Flashing_u-boot_to_SPI_Flash " - problem.

Please help.

Thanks in advanced]]> <![CDATA[can rock64 4gb ram run entirely on free software?]]> https://forum.pine64.org/showthread.php?tid=19613 Tue, 07 Jan 2025 09:04:16 +0000 heocb]]> https://forum.pine64.org/showthread.php?tid=19613 run entirely on a free software system? If the computer can run
partly on a free software system, then which devices on the
computer will not work if you decide to not install non free software on
the computer? Thank you.]]> run entirely on a free software system? If the computer can run
partly on a free software system, then which devices on the
computer will not work if you decide to not install non free software on
the computer? Thank you.]]> <![CDATA[Upgrading ancient Rock64]]> https://forum.pine64.org/showthread.php?tid=19513 Fri, 15 Nov 2024 15:50:00 +0000 timxjr1300]]> https://forum.pine64.org/showthread.php?tid=19513
I have a Pine Rock 64 which has been running for a very long time and really well but because it has been running a long time it is on a very old OS.

Is there a way of upgrading from... ayufan/rock64-ppa/ubuntu bionic to something more recent?

I appreciate upgrading is not as good as starting with a new install but I have lots of configuration that may well be a nightmare to go through again.
I have been previously been bitten by "yeah its all in /etc... it will be fine"

Any advice welcome.]]>
I have a Pine Rock 64 which has been running for a very long time and really well but because it has been running a long time it is on a very old OS.

Is there a way of upgrading from... ayufan/rock64-ppa/ubuntu bionic to something more recent?

I appreciate upgrading is not as good as starting with a new install but I have lots of configuration that may well be a nightmare to go through again.
I have been previously been bitten by "yeah its all in /etc... it will be fine"

Any advice welcome.]]> <![CDATA[How to boot an older, working kernel]]> https://forum.pine64.org/showthread.php?tid=19487 Fri, 01 Nov 2024 22:43:08 +0000 bits]]> https://forum.pine64.org/showthread.php?tid=19487


Drop a file in /etc/flash-kernel/ubootenv.d that forces the U-Boot environment variable fk_kvers to a working kernel version present in your /boot, then run flash-kernel to regenerate the U-Boot bootscript /boot/boot.scr





echo "env set fk_kvers 6.1.0-22-arm64" > /etc/flash-kernel/ubootenv.d/90-force-kernel-version &&

flash-kernel



When you want to stop forcing the kernel version, remove /etc/flash-kernel/ubootenv.d/90-force-kernel-version, run flash-kernel, and reboot



This works because flash-kernel rebuilds /boot/boot.scr from the template /etc/flash-kernel/bootscript/bootscr.uboot-generic, and this includes "@@@", which gets replaced by the contents of each of the files in /etc/flash-kernel/ubootenv.d/ and the boot script boots the referenced kernel]]>


Drop a file in /etc/flash-kernel/ubootenv.d that forces the U-Boot environment variable fk_kvers to a working kernel version present in your /boot, then run flash-kernel to regenerate the U-Boot bootscript /boot/boot.scr





echo "env set fk_kvers 6.1.0-22-arm64" > /etc/flash-kernel/ubootenv.d/90-force-kernel-version &&

flash-kernel



When you want to stop forcing the kernel version, remove /etc/flash-kernel/ubootenv.d/90-force-kernel-version, run flash-kernel, and reboot



This works because flash-kernel rebuilds /boot/boot.scr from the template /etc/flash-kernel/bootscript/bootscr.uboot-generic, and this includes "@@@", which gets replaced by the contents of each of the files in /etc/flash-kernel/ubootenv.d/ and the boot script boots the referenced kernel]]> <![CDATA[Debian installation via sd card]]> https://forum.pine64.org/showthread.php?tid=19459 Sat, 12 Oct 2024 16:24:25 +0000 oaFJSADBKV]]> https://forum.pine64.org/showthread.php?tid=19459
Got a second hand Rock64 yesterday. As far as I have been able to tell I need to jump pins 20 and 21 to bypass SPI-flash to boot from SD. Was not able to boot into debian. I ended up flashing the SD card with Armbian to try and install u-boot. I was able to boot onto the sd card with armbian. So I know the rock64 isn't bricked.

The dilema I currently see myself in is that I only have 1 sd card and I do not see how I would install an OS without having a second sd card and a usb sd card reader. Am I wrong? I am hoping to not have to go out and buy an extra sd card and reader I don't really want to buy an emmc module either.

I was planning to run the rock64 off the sd card. Would it be possible to achieve what I want with the serial console?

Any other major flaws in my plan?]]>
Got a second hand Rock64 yesterday. As far as I have been able to tell I need to jump pins 20 and 21 to bypass SPI-flash to boot from SD. Was not able to boot into debian. I ended up flashing the SD card with Armbian to try and install u-boot. I was able to boot onto the sd card with armbian. So I know the rock64 isn't bricked.

The dilema I currently see myself in is that I only have 1 sd card and I do not see how I would install an OS without having a second sd card and a usb sd card reader. Am I wrong? I am hoping to not have to go out and buy an extra sd card and reader I don't really want to buy an emmc module either.

I was planning to run the rock64 off the sd card. Would it be possible to achieve what I want with the serial console?

Any other major flaws in my plan?]]> <![CDATA[problem with debian emmc boot]]> https://forum.pine64.org/showthread.php?tid=19356 Tue, 23 Jul 2024 18:41:49 +0000 G4zCDzWb]]> https://forum.pine64.org/showthread.php?tid=19356
So far, the most current method I have tried is this guide. Everything seemed to go fine until the install finished and I rebooted. Upon boot-up I saw the following on serial console:
Code:
U-Boot TPL 2023.01+dfsg-2+deb12u1 (Apr 18 2024 - 22:00:21)
LPDDR3, 800MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Trying to boot from BOOTROM
Returning to boot ROM...

U-Boot SPL 2023.01+dfsg-2+deb12u1 (Apr 18 2024 - 22:00:21 +0000)
Trying to boot from MMC2
NOTICE:  BL31: v2.8(debug):
NOTICE:  BL31: Built : 06:31:44, Nov 25 2022
NOTICE:  BL31:Rockchip release version: v1.2
INFO:    ARM GICv2 driver initialized
INFO:    plat_rockchip_pmu_init: pd status 0xe
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for 855873 was applied
WARNING: BL31: cortex_a53: CPU workaround for 1530924 was missing!
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x200000
INFO:    SPSR = 0x3c9


U-Boot 2023.01+dfsg-2+deb12u1 (Apr 18 2024 - 22:00:21 +0000)

Model: Pine64 Rock64
DRAM:  2 GiB
PMIC:  RK8050 (on=0x50, off=0x10)
Core:  228 devices, 24 uclasses, devicetree: separate
MMC:   mmc@ff500000: 1, mmc@ff520000: 0
Loading Environment from MMC... Card did not respond to voltage select! : -110
*** Warning - No block device, using default environment

In:    serial@ff130000
Out:   serial@ff130000
Err:   serial@ff130000
Model: Pine64 Rock64
Net:   eth0: ethernet@ff540000
Hit any key to stop autoboot:  0
Card did not respond to voltage select! : -110
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
2904 bytes read in 4 ms (709 KiB/s)
## Executing script at 00500000
32688064 bytes read in 848 ms (36.8 MiB/s)
36095 bytes read in 10 ms (3.4 MiB/s)
30462286 bytes read in 775 ms (37.5 MiB/s)
Booting Debian 6.1.0-23-arm64 from mmc 0:1...
Moving Image from 0x2080000 to 0x2200000, end=41d0000
## Flattened Device Tree blob at 01f00000
   Booting using the fdt blob at 0x1f00000
Working FDT set to 1f00000
   Loading Ramdisk to 7b20f000, end 7cf1c14e ... OK
   Loading Device Tree to 000000007b203000, end 000000007b20ecfe ... OK
Working FDT set to 7b203000

Starting kernel ...

[    4.349873] rockchip-pm-domain ff100000.syscon:power-controller: failed to get ack on domain 'hevc', val=0x88220
[    6.195026] rockchip-pinctrl pinctrl: pin gpio0-2 already requested by vcc-host-5v-regulator; cannot claim for vcc-host1-5v-regulator
[    6.196127] rockchip-pinctrl pinctrl: pin-2 (vcc-host1-5v-regulator) status -22
[    6.196802] rockchip-pinctrl pinctrl: could not request pin 2 (gpio0-2) from group usb20-host-drv  on device rockchip-pinctrl
[    6.197825] reg-fixed-voltage vcc-host1-5v-regulator: Error applying setting, reverse things back
[    7.526011] mmc1: mmc_select_hs200 failed, error -110
[    7.526497] mmc1: error -110 whilst initialising MMC card
[    8.488081] mmc1: mmc_select_hs200 failed, error -110
[    8.488567] mmc1: error -110 whilst initialising MMC card
[    9.452265] mmc1: mmc_select_hs200 failed, error -110
[    9.452753] mmc1: error -110 whilst initialising MMC card
[   10.489412] mmc1: mmc_select_hs200 failed, error -110
[   10.489902] mmc1: error -110 whilst initialising MMC card

Gave up waiting for suspend/resume device
Gave up waiting for root file system device.  Common problems:
- Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT!  /dev/disk/by-uuid/d08756f8-8dcd-41f0-b02b-c4ff2da5e68b does not exist.  Dropping to a shell!


BusyBox v1.35.0 (Debian 1:1.35.0-4+b3) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs)

I am able to run the installer and install to an SD card without any issues. Reboot will result in a working system. If I pull the EMMC card out and mount it on a separate machine via adapter, the files and partition layout look like what I would expect, the dtb seems to be in place and correct for the hardware, etc. I poked around a bit in the busybox shell but didn't have a solid plan for what I was trying to achieve other than basic investigation.

Does anyone here have any idea where I should look next? I've gone through this setup/install process multiple times and the result is the same each time. I did have arch linux running on this board for a month or so but updates broke it twice and both times I just reinstalled. I got tired of that since this is normally a headless system in a place where I don't want to have to remove it over and over.]]>
So far, the most current method I have tried is this guide. Everything seemed to go fine until the install finished and I rebooted. Upon boot-up I saw the following on serial console:
Code:
U-Boot TPL 2023.01+dfsg-2+deb12u1 (Apr 18 2024 - 22:00:21)
LPDDR3, 800MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Trying to boot from BOOTROM
Returning to boot ROM...

U-Boot SPL 2023.01+dfsg-2+deb12u1 (Apr 18 2024 - 22:00:21 +0000)
Trying to boot from MMC2
NOTICE:  BL31: v2.8(debug):
NOTICE:  BL31: Built : 06:31:44, Nov 25 2022
NOTICE:  BL31:Rockchip release version: v1.2
INFO:    ARM GICv2 driver initialized
INFO:    plat_rockchip_pmu_init: pd status 0xe
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for 855873 was applied
WARNING: BL31: cortex_a53: CPU workaround for 1530924 was missing!
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x200000
INFO:    SPSR = 0x3c9


U-Boot 2023.01+dfsg-2+deb12u1 (Apr 18 2024 - 22:00:21 +0000)

Model: Pine64 Rock64
DRAM:  2 GiB
PMIC:  RK8050 (on=0x50, off=0x10)
Core:  228 devices, 24 uclasses, devicetree: separate
MMC:   mmc@ff500000: 1, mmc@ff520000: 0
Loading Environment from MMC... Card did not respond to voltage select! : -110
*** Warning - No block device, using default environment

In:    serial@ff130000
Out:   serial@ff130000
Err:   serial@ff130000
Model: Pine64 Rock64
Net:   eth0: ethernet@ff540000
Hit any key to stop autoboot:  0
Card did not respond to voltage select! : -110
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
2904 bytes read in 4 ms (709 KiB/s)
## Executing script at 00500000
32688064 bytes read in 848 ms (36.8 MiB/s)
36095 bytes read in 10 ms (3.4 MiB/s)
30462286 bytes read in 775 ms (37.5 MiB/s)
Booting Debian 6.1.0-23-arm64 from mmc 0:1...
Moving Image from 0x2080000 to 0x2200000, end=41d0000
## Flattened Device Tree blob at 01f00000
   Booting using the fdt blob at 0x1f00000
Working FDT set to 1f00000
   Loading Ramdisk to 7b20f000, end 7cf1c14e ... OK
   Loading Device Tree to 000000007b203000, end 000000007b20ecfe ... OK
Working FDT set to 7b203000

Starting kernel ...

[    4.349873] rockchip-pm-domain ff100000.syscon:power-controller: failed to get ack on domain 'hevc', val=0x88220
[    6.195026] rockchip-pinctrl pinctrl: pin gpio0-2 already requested by vcc-host-5v-regulator; cannot claim for vcc-host1-5v-regulator
[    6.196127] rockchip-pinctrl pinctrl: pin-2 (vcc-host1-5v-regulator) status -22
[    6.196802] rockchip-pinctrl pinctrl: could not request pin 2 (gpio0-2) from group usb20-host-drv  on device rockchip-pinctrl
[    6.197825] reg-fixed-voltage vcc-host1-5v-regulator: Error applying setting, reverse things back
[    7.526011] mmc1: mmc_select_hs200 failed, error -110
[    7.526497] mmc1: error -110 whilst initialising MMC card
[    8.488081] mmc1: mmc_select_hs200 failed, error -110
[    8.488567] mmc1: error -110 whilst initialising MMC card
[    9.452265] mmc1: mmc_select_hs200 failed, error -110
[    9.452753] mmc1: error -110 whilst initialising MMC card
[   10.489412] mmc1: mmc_select_hs200 failed, error -110
[   10.489902] mmc1: error -110 whilst initialising MMC card

Gave up waiting for suspend/resume device
Gave up waiting for root file system device.  Common problems:
- Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT!  /dev/disk/by-uuid/d08756f8-8dcd-41f0-b02b-c4ff2da5e68b does not exist.  Dropping to a shell!


BusyBox v1.35.0 (Debian 1:1.35.0-4+b3) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs)

I am able to run the installer and install to an SD card without any issues. Reboot will result in a working system. If I pull the EMMC card out and mount it on a separate machine via adapter, the files and partition layout look like what I would expect, the dtb seems to be in place and correct for the hardware, etc. I poked around a bit in the busybox shell but didn't have a solid plan for what I was trying to achieve other than basic investigation.

Does anyone here have any idea where I should look next? I've gone through this setup/install process multiple times and the result is the same each time. I did have arch linux running on this board for a month or so but updates broke it twice and both times I just reinstalled. I got tired of that since this is normally a headless system in a place where I don't want to have to remove it over and over.]]> <![CDATA[irradium (based on crux linux) Rock64 riscv64, aarch64]]> https://forum.pine64.org/showthread.php?tid=19156 Sun, 24 Mar 2024 19:07:17 +0000 mara]]> https://forum.pine64.org/showthread.php?tid=19156 irradium - source based Linux distribution CRUX adhering to ideology keep it simple, has its own package system, also supports the port system.

irradium development

packages aarch64
packages riscv64

installation README.TXT
kernel 6.8.1

irradium-3.7-aarch64-core-rock64-6.8.1-build-20240324.img.zst
irradium-3.7-aarch64-core-rock64-6.8.1-build-20240324.img.zst.sha256
irradium-3.7-aarch64-xfce-rock64-6.8.1-build-20240324.img.zst
irradium-3.7-aarch64-xfce-rock64-6.8.1-build-20240324.img.zst.sha256]]> irradium - source based Linux distribution CRUX adhering to ideology keep it simple, has its own package system, also supports the port system.

irradium development

packages aarch64
packages riscv64

installation README.TXT
kernel 6.8.1

irradium-3.7-aarch64-core-rock64-6.8.1-build-20240324.img.zst
irradium-3.7-aarch64-core-rock64-6.8.1-build-20240324.img.zst.sha256
irradium-3.7-aarch64-xfce-rock64-6.8.1-build-20240324.img.zst
irradium-3.7-aarch64-xfce-rock64-6.8.1-build-20240324.img.zst.sha256]]> <![CDATA[How to update/compile Debian 12.5?]]> https://forum.pine64.org/showthread.php?tid=19095 Thu, 22 Feb 2024 19:09:58 +0000 Wizardknight]]> https://forum.pine64.org/showthread.php?tid=19095 https://d-i.debian.org/daily-images/arm6...rd-images/ offered here.
The image works great for the most part.

I would really like to fix two things.
1. There is a 5v error related to the DTS file that has what looks like an easy patch to implement.

Code:
  rockchip-pinctrl pinctrl: pin gpio0-2 already requested by vcc-host-5v-regulator; cannot claim for vcc-host1-5v-regulator
  rockchip-pinctrl pinctrl: pin-2 (vcc-host1-5v-regulator) status -22
  rockchip-pinctrl pinctrl: could not request pin 2 (gpio0-2) from group usb20-host-drv  on device rockchip-pinctrl
  reg-fixed-voltage vcc-host1-5v-regulator: Error applying setting, reverse things back

Described here: https://patchew.org/linux/20230421213841...@brun.one/

2. I would like to see the boot messages during boot time. 
That requires removing the quiet option from the boot.scr file to the best of my understanding. As far as I can tell that requires it to be recompiled too.

Can anyone point me to a guide for doing these changes? I am fairly comfortable at the CLI, but I have never tried to compile like this before.]]> https://d-i.debian.org/daily-images/arm6...rd-images/ offered here.
The image works great for the most part.

I would really like to fix two things.
1. There is a 5v error related to the DTS file that has what looks like an easy patch to implement.

Code:
  rockchip-pinctrl pinctrl: pin gpio0-2 already requested by vcc-host-5v-regulator; cannot claim for vcc-host1-5v-regulator
  rockchip-pinctrl pinctrl: pin-2 (vcc-host1-5v-regulator) status -22
  rockchip-pinctrl pinctrl: could not request pin 2 (gpio0-2) from group usb20-host-drv  on device rockchip-pinctrl
  reg-fixed-voltage vcc-host1-5v-regulator: Error applying setting, reverse things back

Described here: https://patchew.org/linux/20230421213841...@brun.one/

2. I would like to see the boot messages during boot time. 
That requires removing the quiet option from the boot.scr file to the best of my understanding. As far as I can tell that requires it to be recompiled too.

Can anyone point me to a guide for doing these changes? I am fairly comfortable at the CLI, but I have never tried to compile like this before.]]> <![CDATA[Rock64 won't boot]]> https://forum.pine64.org/showthread.php?tid=18976 Wed, 27 Dec 2023 16:34:50 +0000 dstallmo]]> https://forum.pine64.org/showthread.php?tid=18976 <![CDATA[HDMI doesn't work on rock64]]> https://forum.pine64.org/showthread.php?tid=18827 Tue, 31 Oct 2023 03:18:02 +0000 Noung1991]]> https://forum.pine64.org/showthread.php?tid=18827 HDMI doesn't work with any Kernel except the Kernel 4.4 from Rockchip (it also doesn't work with xorg) i tried out all kernel configs from rockchip and ayufan always same error:
[    4.030085] printk: console [ttyS2] enabled
[    4.031672] rockchip-vop ff370000.vop: Adding to iommu group 1
[    4.038101] rockchip-drm display-subsystem: bound ff370000.vop (ops 0xffffffc0108c27d8)
[    4.038924] rockchip-drm display-subsystem: failed to bind ff3c0000.hdmi (ops 0xffffffc0108c5f30): -517
[    4.040292] rockchip-drm display-subsystem: master bind failed: -517

With Kernel 4.4 from Rockchip (ayufan) HDMI works:
[    3.167892] [drm] Initialized drm 1.1.0 20060810
[    3.173651] [drm] Rockchip DRM driver version: v1.0.1
[    3.174380] rockchip-drm display-subsystem: devfreq is not set
[    3.175647] rockchip-drm display-subsystem: bound ff370000.vop (ops 0xffffff8008d86950)
[    3.176798] i2c i2c-4: of_i2c: modalias failure on /hdmi@ff3c0000/ports
[    3.177487] dwhdmi-rockchip ff3c0000.hdmi: registered DesignWare HDMI I2C bus driver
[    3.178358] dwhdmi-rockchip ff3c0000.hdmi: Detected HDMI TX controller v2.11a with HDCP (inno_dw_hdmi_phy2)
[    3.180400] rockchip-drm display-subsystem: bound ff3c0000.hdmi (ops 0xffffff8008d7afa8)
[    3.181186] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    3.181851] [drm] No driver support for vblank timestamp query.
[    3.182495] rockchip-drm display-subsystem: failed to parse display resources
[    3.402118] rockchip-vop ff370000.vop: [drm:vop_crtc_enable] Update mode to 1280x1024p60, type: 11
[    3.469911] Console: switching to colour frame buffer device 160x64
[    3.503468] rockchip-drm display-subsystem: fb0:  frame buffer device

Xorg-log:
X.Org X Server 1.20.5
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.14.89-0-vanilla aarch64 Alpine Linux
Current Operating System: Linux localhost 5.4.2 #1 SMP Thu Dec 12 03:04:42 CET 2019 aarch64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.4.2 modules=loop,squashfs,sd-mod,usb-storage modloop=/boot/modloop-5.4.2 extra_latent_entropy1
Build Date: 31 May 2019  06:21:31AM
 
Current version of pixman: 0.38.4
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Jan 21 10:28:08 2016
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
MESA-LOADER: failed to open rockchip (search paths /usr/lib/xorg/modules/dri)
failed to load driver: rockchip
MESA-LOADER: failed to open kms_swrast (search paths /usr/lib/xorg/modules/dri)
failed to load driver: kms_swrast
MESA-LOADER: failed to open swrast (search paths /usr/lib/xorg/modules/dri)
failed to load swrast driver
couldn't get display device
(II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported high keycode 372 for name <I372> ignored
>                   X11 cannot support keycodes above 255.
>                   This warning only shows for the first high keycode.
> Internal error:   Could not resolve keysym XF86MonBrightnessCycle
> Internal error:   Could not resolve keysym XF86RotationLockToggle
Errors from xkbcomp are not fatal to the X server
(EE) /usr/share/libinput: failed to find data files
(EE) Failed to load the device quirks from /usr/share/libinput and /etc/libinput/local-overrides.quirks. This will negatively affect device b.
/usr/bin/startxfce4: X server already running on display :0
<stdin>:0: warning: Unknown encoding: C.UTF-8
    xfce4-session: No GPG agent found
xfce4-session: No SSH authentication agent found

(xfce4-session:2231): xfce4-session-WARNING **: 10:28:10.365: xfsm_manager_load_session: Something wrong with /home/admin/.cache/sessions/xfc?

(xfwm4:2278): GLib-CRITICAL **: 10:28:19.096: g_str_has_prefix: assertion 'prefix != NULL' failed

(xfsettingsd:2284): GLib-CRITICAL **: 10:28:20.459: g_str_has_prefix: assertion 'prefix != NULL' failed

(xfsettingsd:2284): GLib-GObject-CRITICAL **: 10:28:20.721: g_value_get_string: assertion 'G_VALUE_HOLDS_STRING (value)' failed

(xfsettingsd:2284): GLib-GObject-CRITICAL **: 10:28:20.800: g_value_get_string: assertion 'G_VALUE_HOLDS_STRING (value)' failed
Error relocating /usr/bin/Thunar: pango_attr_insert_hyphens_new: symbol not found
xfsettingsd: No window manager registered on screen 0.
xfce4-panel: No window manager registered on screen 0. To start the panel without this check, run with --disable-wm-check.
No window manager registered on screen 0. To start the xfdesktop without this check, run with --disable-wm-check.
xfce4-panel-Message: 10:28:33.334: Plugin "statusnotifier-7" was not found and has been removed from the configuration
xfce4-panel-Message: 10:28:33.338: Plugin "pulseaudio-8" was not found and has been removed from the configuration
xfce4-panel-Message: 10:28:33.377: Plugin "notification-plugin-10" was not found and has been removed from the configuration

** (wrapper-2.0:2315): WARNING **: 10:28:36.247: No outputs have backlight property

(wrapper-2.0:2315): xfce4-power-manager-plugin-WARNING **: 10:28:36.920: Xfce4-power-manager: The panel plugin is present, so the tray icon g.

(wrapper-2.0:2315): Gtk-WARNING **: 10:28:37.092: Negative content width -3 (allocation 1, extents 2x2) while allocating gadget (node button,)

(xfdesktop:2311): GLib-GObject-CRITICAL **: 10:28:46.065: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
^Cxinit: connection to X server lost

waiting for X server to shut down ^VGdk-Message: 10:28:59.978: xfdesktop: Fatal IO error 38 (Function not implemented) on X server :0.

Gdk-Message: 10:28:59.978: xfsettingsd: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.


I boot with extlinux.conf: The kernel starts only without console bootparameter: When i insert console=tty0 as boot paramter the kernel dont start.

Does anyone know what the problem could be.
Thank you in advance for your help]]> HDMI doesn't work with any Kernel except the Kernel 4.4 from Rockchip (it also doesn't work with xorg) i tried out all kernel configs from rockchip and ayufan always same error:
[    4.030085] printk: console [ttyS2] enabled
[    4.031672] rockchip-vop ff370000.vop: Adding to iommu group 1
[    4.038101] rockchip-drm display-subsystem: bound ff370000.vop (ops 0xffffffc0108c27d8)
[    4.038924] rockchip-drm display-subsystem: failed to bind ff3c0000.hdmi (ops 0xffffffc0108c5f30): -517
[    4.040292] rockchip-drm display-subsystem: master bind failed: -517

With Kernel 4.4 from Rockchip (ayufan) HDMI works:
[    3.167892] [drm] Initialized drm 1.1.0 20060810
[    3.173651] [drm] Rockchip DRM driver version: v1.0.1
[    3.174380] rockchip-drm display-subsystem: devfreq is not set
[    3.175647] rockchip-drm display-subsystem: bound ff370000.vop (ops 0xffffff8008d86950)
[    3.176798] i2c i2c-4: of_i2c: modalias failure on /hdmi@ff3c0000/ports
[    3.177487] dwhdmi-rockchip ff3c0000.hdmi: registered DesignWare HDMI I2C bus driver
[    3.178358] dwhdmi-rockchip ff3c0000.hdmi: Detected HDMI TX controller v2.11a with HDCP (inno_dw_hdmi_phy2)
[    3.180400] rockchip-drm display-subsystem: bound ff3c0000.hdmi (ops 0xffffff8008d7afa8)
[    3.181186] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    3.181851] [drm] No driver support for vblank timestamp query.
[    3.182495] rockchip-drm display-subsystem: failed to parse display resources
[    3.402118] rockchip-vop ff370000.vop: [drm:vop_crtc_enable] Update mode to 1280x1024p60, type: 11
[    3.469911] Console: switching to colour frame buffer device 160x64
[    3.503468] rockchip-drm display-subsystem: fb0:  frame buffer device

Xorg-log:
X.Org X Server 1.20.5
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.14.89-0-vanilla aarch64 Alpine Linux
Current Operating System: Linux localhost 5.4.2 #1 SMP Thu Dec 12 03:04:42 CET 2019 aarch64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.4.2 modules=loop,squashfs,sd-mod,usb-storage modloop=/boot/modloop-5.4.2 extra_latent_entropy1
Build Date: 31 May 2019  06:21:31AM
 
Current version of pixman: 0.38.4
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Jan 21 10:28:08 2016
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
MESA-LOADER: failed to open rockchip (search paths /usr/lib/xorg/modules/dri)
failed to load driver: rockchip
MESA-LOADER: failed to open kms_swrast (search paths /usr/lib/xorg/modules/dri)
failed to load driver: kms_swrast
MESA-LOADER: failed to open swrast (search paths /usr/lib/xorg/modules/dri)
failed to load swrast driver
couldn't get display device
(II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported high keycode 372 for name <I372> ignored
>                   X11 cannot support keycodes above 255.
>                   This warning only shows for the first high keycode.
> Internal error:   Could not resolve keysym XF86MonBrightnessCycle
> Internal error:   Could not resolve keysym XF86RotationLockToggle
Errors from xkbcomp are not fatal to the X server
(EE) /usr/share/libinput: failed to find data files
(EE) Failed to load the device quirks from /usr/share/libinput and /etc/libinput/local-overrides.quirks. This will negatively affect device b.
/usr/bin/startxfce4: X server already running on display :0
<stdin>:0: warning: Unknown encoding: C.UTF-8
    xfce4-session: No GPG agent found
xfce4-session: No SSH authentication agent found

(xfce4-session:2231): xfce4-session-WARNING **: 10:28:10.365: xfsm_manager_load_session: Something wrong with /home/admin/.cache/sessions/xfc?

(xfwm4:2278): GLib-CRITICAL **: 10:28:19.096: g_str_has_prefix: assertion 'prefix != NULL' failed

(xfsettingsd:2284): GLib-CRITICAL **: 10:28:20.459: g_str_has_prefix: assertion 'prefix != NULL' failed

(xfsettingsd:2284): GLib-GObject-CRITICAL **: 10:28:20.721: g_value_get_string: assertion 'G_VALUE_HOLDS_STRING (value)' failed

(xfsettingsd:2284): GLib-GObject-CRITICAL **: 10:28:20.800: g_value_get_string: assertion 'G_VALUE_HOLDS_STRING (value)' failed
Error relocating /usr/bin/Thunar: pango_attr_insert_hyphens_new: symbol not found
xfsettingsd: No window manager registered on screen 0.
xfce4-panel: No window manager registered on screen 0. To start the panel without this check, run with --disable-wm-check.
No window manager registered on screen 0. To start the xfdesktop without this check, run with --disable-wm-check.
xfce4-panel-Message: 10:28:33.334: Plugin "statusnotifier-7" was not found and has been removed from the configuration
xfce4-panel-Message: 10:28:33.338: Plugin "pulseaudio-8" was not found and has been removed from the configuration
xfce4-panel-Message: 10:28:33.377: Plugin "notification-plugin-10" was not found and has been removed from the configuration

** (wrapper-2.0:2315): WARNING **: 10:28:36.247: No outputs have backlight property

(wrapper-2.0:2315): xfce4-power-manager-plugin-WARNING **: 10:28:36.920: Xfce4-power-manager: The panel plugin is present, so the tray icon g.

(wrapper-2.0:2315): Gtk-WARNING **: 10:28:37.092: Negative content width -3 (allocation 1, extents 2x2) while allocating gadget (node button,)

(xfdesktop:2311): GLib-GObject-CRITICAL **: 10:28:46.065: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
^Cxinit: connection to X server lost

waiting for X server to shut down ^VGdk-Message: 10:28:59.978: xfdesktop: Fatal IO error 38 (Function not implemented) on X server :0.

Gdk-Message: 10:28:59.978: xfsettingsd: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.


I boot with extlinux.conf: The kernel starts only without console bootparameter: When i insert console=tty0 as boot paramter the kernel dont start.

Does anyone know what the problem could be.
Thank you in advance for your help]]> <![CDATA[Rock64 + Klipper + KlipperScreen Instructions]]> https://forum.pine64.org/showthread.php?tid=18811 Sun, 22 Oct 2023 07:52:44 +0000 godzilla62]]> https://forum.pine64.org/showthread.php?tid=18811
.jpg   Klipper Screen.jpg (Size: 368.8 KB / Downloads: 531) Rock64 + Klipper + Fluidd + KlipperScreen
After much ado I finally got everything working. I tried many flavors of linux and the only one that had decent video drivers was Ayufan's prerelease version 0.11.2.-1187. 
I purchased several Rock64's some years ago for $20 off amazon. It was a security appliance with power supply. Used a couple for retro gaming. Next to print enclosure and mounting.

Here's what you need. (I supplied links at the end)
*Rock64
*Linux Favor Ayufan= focal-minimal-rock64-0.11.2-1187-arm64.img.xz or newer.
*klipper screen = Kuman 7" HDMI 1024x600 - Amazon or aliexpress
*Download Kiauh and follow instructions. Seems all manual installs have been removed for search engines.

KlipperScreen Error I encountered -
xf86OpenConsole: Cannot open virtual console 2 (Permission denied)
Fix that worked ->
sudo bash -c "echo needs_root_rights=yes>>/etc/X11/Xwrapper.config"

Some xorg random notes -
find monitor number via ssh do not type $
$ export DISPLAY=:0
$ xrandr --listmonitors
list display resolutions
$ xrandr -d :0
$ xrandr -display :0.0 --listmonitors
>output
Monitors: 1-- 0: +*HDMI-1 1920/476x1080/268+0+0  HDMI-1

Links
Klipper Screen Error & fixes
http://klipperscreen.readthedocs.io/.../.../VC_ERROR/
Ayufan Rock64 Home
github.com/ayufan-rock64/ayufan-rock64.github.io
Ayufan Rock64 0.11.2 Download page (scroll down)
github.com/ayufan-rock64/linux-build/releases/tag/0.11.2]]>
.jpg   Klipper Screen.jpg (Size: 368.8 KB / Downloads: 531) Rock64 + Klipper + Fluidd + KlipperScreen
After much ado I finally got everything working. I tried many flavors of linux and the only one that had decent video drivers was Ayufan's prerelease version 0.11.2.-1187. 
I purchased several Rock64's some years ago for $20 off amazon. It was a security appliance with power supply. Used a couple for retro gaming. Next to print enclosure and mounting.

Here's what you need. (I supplied links at the end)
*Rock64
*Linux Favor Ayufan= focal-minimal-rock64-0.11.2-1187-arm64.img.xz or newer.
*klipper screen = Kuman 7" HDMI 1024x600 - Amazon or aliexpress
*Download Kiauh and follow instructions. Seems all manual installs have been removed for search engines.

KlipperScreen Error I encountered -
xf86OpenConsole: Cannot open virtual console 2 (Permission denied)
Fix that worked ->
sudo bash -c "echo needs_root_rights=yes>>/etc/X11/Xwrapper.config"

Some xorg random notes -
find monitor number via ssh do not type $
$ export DISPLAY=:0
$ xrandr --listmonitors
list display resolutions
$ xrandr -d :0
$ xrandr -display :0.0 --listmonitors
>output
Monitors: 1-- 0: +*HDMI-1 1920/476x1080/268+0+0  HDMI-1

Links
Klipper Screen Error & fixes
http://klipperscreen.readthedocs.io/.../.../VC_ERROR/
Ayufan Rock64 Home
github.com/ayufan-rock64/ayufan-rock64.github.io
Ayufan Rock64 0.11.2 Download page (scroll down)
github.com/ayufan-rock64/linux-build/releases/tag/0.11.2]]> <![CDATA[arch rock64 does not boot]]> https://forum.pine64.org/showthread.php?tid=18472 Sun, 09 Jul 2023 09:28:11 +0000 nemnob]]> https://forum.pine64.org/showthread.php?tid=18472
I followed this guide: https://archlinuxarm.org/platforms/armv8...ner/pine64  to install arch on an sd card and then successfully booted to rock64, but I did the mistake and run "rm /boot/boot.scr" and now I'm unable to boot again.

After than I tried following again the same steps (from step 5-10) a couple of times but I always get the same result (when I boot all the leds are working and the the monitor does not display anything)

Any ideas on what is going on and how I can debug this?]]>
I followed this guide: https://archlinuxarm.org/platforms/armv8...ner/pine64  to install arch on an sd card and then successfully booted to rock64, but I did the mistake and run "rm /boot/boot.scr" and now I'm unable to boot again.

After than I tried following again the same steps (from step 5-10) a couple of times but I always get the same result (when I boot all the leds are working and the the monitor does not display anything)

Any ideas on what is going on and how I can debug this?]]>