0.7.9 Linux release from ayufan
#1
Star 
Hello everyone,

ayufan marked 0.7.8 as the new Linux release for RockPro64.
It contains many improvements and enables many features that were missing in 0.6.44, so I strongly suggest everyone either upgrade (as per ayufan's instructions):

Code:
sudo apt-get update -y
sudo apt-get install linux-rockpro64 -y


... or just run a fresh install.
The changelog from 0.6.44 is quite extensive so I suggest you read it on the release page. If you encounter issues with this (or future 0.7.X builds) report them in this thread or directly on github.

Enjoy!
You can find me on IRC, Discord and Twitter


#2
Is this only for Rock Pro 64 or for Rock64 too? I just did upgrade and install linux-rock64 and I see:
Linux rock64 4.4.126-rockchip-ayufan-239 #1 SMP Sun May 27 18:38:24 UTC 2018 aarch64 GNU/Linux

Is that right (for a Rock64)?
#3
The AMPAK AP6359SA based Wifi/Bluetooth module on the store is not working on this version 0.7.8.
#4
ab1jx,
Yes - seems like the Rock64 upgrade process has some issues at the time - ayufan will address the problem in the 0.7.8 Rock64 thread.

samtsai5212,
Correct - read the changelog.
You can find me on IRC, Discord and Twitter


#5
Just installed ubuntu minimal bionic 64 and apt-get update fails as the ayufan repo origin has changed to github.

Is this a temp or perm change? As haven't had time to check how to force or change the apt reference.
#6
(07-25-2018, 03:52 AM)Luke Wrote: ab1jx,
Yes - seems like the Rock64 upgrade process has some issues at the time - ayufan will address the problem in the 0.7.8 Rock64 thread.

Well, this Rock64 is quite healthy, on my 3rd install, plus the updates/upgrades.  Hit 5 days of uptime, I'm just building current LLVM and Clang from sources because trying to build Firefox 61 indicated the deb versions were too old.  If it stays this stable I might move it to the big monitor.  No HDMI sound, that's soon to be the biggest issue.  smplayer seems to work with full acceleration and minimal CPU drain.  es2gears peaks around 185 FPS, even while compiling with 1 thread.

Wonder what Trump's tarriffs are going to do to the price of these things.
#7
(07-27-2018, 06:09 PM)ab1jx Wrote: No HDMI sound, that's soon to be the biggest issue.
Not sure for R64 but for RP64 no problem, first check which card the HDMI is (on RP64 its card 2), then set ~/.asoundrc accordingly. Mine are below.

Code:
$ aplay --list-devices
**** List of PLAYBACK Hardware Devices ****
card 0: rockchipes8316c [rockchip,es8316-codec], device 0: ff890000.i2s-ES8316 HiFi ES8316 HiFi-0 []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: ROCKCHIPSPDIF [ROCKCHIP,SPDIF], device 0: ff870000.spdif-dit-hifi dit-hifi-0 []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 2: rkhdmidpsound [rk-hdmi-dp-sound], device 0: HDMI-DP multicodec-0 []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
chris@rockpro64:~$ cat .asoundrc
pcm.!default {
    type hw
    card 2
}

ctl.!default {
    type hw           
    card 2
}
  • ROCKPro64 v2.1 2GB, 16Gb eMMC for rootfs, SX8200Pro 512GB NVMe for /home, HDMI video & sound, Bluetooth keyboard & mouse. Arch (6.2 kernel, Openbox desktop) for general purpose daily PC.
  • PinePhone Pro Explorer Edition, daily driver, rk2aw & U-boot on SPI, Arch/SXMO & Arch/phosh on eMMC
  • PinePhone BraveHeart now v1.2b 3/32Gb, Tow-boot with Arch/SXMO on eMMC
#8
Nope, I see the device, it just doesn't do anything.  Even speaker-test doesn't do anything, and alsactl init was about the first thing I did.
Code:
**** List of PLAYBACK Hardware Devices ****
card 0: HDMI [HDMI], device 0: ff000000.i2s-i2s-hifi i2s-hifi-0 []
 Subdevices: 1/1
 Subdevice #0: subdevice #0
card 1: I2S [I2S], device 0: ff010000.i2s-rk3328-hifi rk3328-hifi-0 []
 Subdevices: 1/1
 Subdevice #0: subdevice #0
card 1: I2S [I2S], device 1: ff010000.i2s-snd-soc-dummy-dai snd-soc-dummy-dai-1
 Subdevices: 1/1
 Subdevice #0: subdevice #0
card 2: SPDIF [SPDIF], device 0: ff030000.spdif-dit-hifi dit-hifi-0 []
 Subdevices: 1/1
 Subdevice #0: subdevice #0

I have an idea, it may not pan out.  I'm using kmshelper to load an EDID file to pick a video mode.  Except this is a 128 byte EDID, the newer 256 byte format has sound stuff in it too.  Maybe a 128 byte leaves the sound area blank.

I'm not seeing the "rockchipes8316c [rockchip,es8316-codec], device 0: ff890000.i2s-ES8316 HiFi ES8316 HiFi-0 [" stuff though, that could be significant.  Like it's not loading a driver and probing the device.  Debian Stretch minimal from ayufan_stretch-minimal-rock64-0.6.41-227-arm64.img with updates and upgrades since.

Also all of mine say i2s in them, even the HDMI.  Somewhere I saw a list of devices like hdmi, i2s, spdif.
#9
I've added all 0.7.9 images to WiKi: http://wiki.pine64.org/index.php/ROCKPro...e_Releases
You can find me on IRC, Discord and Twitter


#10
Installing packages that require libglvnd-dev fail and break the package manager.

apt-get install libgtk-3-dev fails with :

Errors were encountered while processing:
/tmp/apt-dpkg-install-riuWxP/58-libglvnd-dev_1.0.0-2ubuntu2.1_arm64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

apt-get install libglvnd-dev fails with :
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
libglvnd-dev
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
99 not fully installed or removed.
Need to get 0 B/3384 B of archives.
After this operation, 24.6 kB of additional disk space will be used.
(Reading database ... 86205 files and directories currently installed.)
Preparing to unpack .../libglvnd-dev_1.0.0-2ubuntu2.1_arm64.deb ...
Unpacking libglvnd-dev:arm64 (1.0.0-2ubuntu2.1) ...
dpkg: error processing archive /var/cache/apt/archives/libglvnd-dev_1.0.0-2ubuntu2.1_arm64.deb (--unpack):
trying to overwrite '/usr/lib/aarch64-linux-gnu/libEGL.so', which is also in package libmali-rk-midgard-t86x-r14p0:arm64 1.6-1ayufan10
Errors were encountered while processing:
/var/cache/apt/archives/libglvnd-dev_1.0.0-2ubuntu2.1_arm64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Is there any work around or solution for this issue? I understand is if this is still being worked on. Thanks!


Possibly Related Threads…
Thread Author Replies Views Last Post
  RockPro64 irradium (based on crux linux) riscv64, aarch64 mara 0 304 12-05-2023, 06:35 AM
Last Post: mara
Exclamation Ethernet regression on Linux Kernel 6.5.4? Deathcrow 3 717 09-22-2023, 04:27 AM
Last Post: diederik
  Installing CH431SER on Ayufan 0.9.14: gitlab-ci-linux-build-159 Thisone 4 1,146 07-14-2023, 04:22 AM
Last Post: hunderteins
  GPIO on Ayufan 0.9.14 Build Thisone 7 1,901 04-23-2023, 01:32 PM
Last Post: diederik
  Linux laptop does not detect the board when plugged in via USB soupy 1 3,904 04-13-2023, 03:01 AM
Last Post: Reynold Grady
  RockPro64 linux console video mode callegar 0 822 09-06-2022, 02:32 PM
Last Post: callegar
Brick Maintained Linux booting from eMMC ootoovak 10 7,883 04-30-2022, 03:57 PM
Last Post: TRS-80
  Armbian 22.02 Release Announcement TRS-80 0 1,103 02-28-2022, 05:08 PM
Last Post: TRS-80
  How I Got Fedora Linux to Boot From eMMC (or microSD, for that matter) whitecat23 4 4,077 01-03-2022, 10:32 AM
Last Post: whitecat23
  Compiling ayufan mainline - DT-overlay missing Mentaluproar 0 1,397 07-24-2021, 09:46 PM
Last Post: Mentaluproar

Forum Jump:


Users browsing this thread: 1 Guest(s)