Hi all,

I have just purchased a new Pine64 board with 2gb ram and a new power supply.  I powered it up and installed OVM  on it.  It was running fine for 4 hours and then it switched itself off.  The board is no longer powering up, the on board red light is not coming on.  I've disconnected everything and re attached it all again and plugged the power supply into the power socket and switched on but nothing. Would anyone be able to assist.

Checking mail today, gave a pleasant surprise:


  IMG_20190919_101305_compress19.jpg (Size: 242.93 KB / Downloads: 1318)

What's the chance we can get something akin to to Solid Run's HoneyComb LX2K?

I mean, it's really tempting to pick up a HoneyComb but Solid Run does not have the reputation for solid desktop-Linux support and usability that the Pine team has. The team over at Phoronix benchmarked this 16-core board, and it competes solidly with early Intel i3 and early i5 processors, making it a potentially serious contender for becoming a daily-use general purpose desktop computer like the Dell and HP mini computers.

Has anyone found a 12v rechargable lipo battery that would fit in the playbox and power the Rockpro64?

I recently set up my rock64 4GB with debian 9 as a media box.

I installed plex and rtorrent and everything is going smoothly. The only problem I have is that after a few hours (probably 6/7 hours) of "work" both my HDDs (one on USB 3.0 the other on the 2.0) slow down from 70-90MB/s to 6-7MB/s. The speed drop happens with all the programs: samba, ftp, rtorrent etc.

The only way to get performance up again is to remount both drives. At that point I get 70-90MB/s back.

My fstab:

Title says it all.

All images in Pine64+ are old paricularly android images.

Are Pinebook images compatible with Pine64+?

I tried to boot Manjaro LXQT image but there was no screen activity.

If they are not compatible how to modify them?

Anyone else problem with Armbian and getting no sound from the jack?
When I open a music stream and have a look in the volume control I see the graphic VU bar moving. Tried different stuff but can't find the solution from the problem.


I'm a total Linux n00b but I did find a command on the internet which I tried and said this:

master@rockpro64:/etc/alsa/conf.d$ aplay -L
default
    Playback/recording through the PulseAudio sound server
null
    Discard all samples (playback) or generate zero samples (capture)
jack
    JACK Audio Connection Kit
pulse
    PulseAudio Sound Server
sysdefault:CARD=rkes8316hpsound
    rk-es8316-hp-sound,
    Default Audio Device
dmix:CARD=rkes8316hpsound,DEV=0
    rk-es8316-hp-sound,
    Direct sample mixing device
dsnoop:CARD=rkes8316hpsound,DEV=0
    rk-es8316-hp-sound,
    Direct sample snooping device
hw:CARD=rkes8316hpsound,DEV=0
    rk-es8316-hp-sound,
    Direct hardware device without any conversions
plughw:CARD=rkes8316hpsound,DEV=0
    rk-es8316-hp-sound,
    Hardware device with all software conversions
usbstream:CARD=rkes8316hpsound
    rk-es8316-hp-sound
    USB Stream Output
sysdefault:CARD=rkspdifsound
    rk-spdif-sound,
    Default Audio Device
dmix:CARD=rkspdifsound,DEV=0
    rk-spdif-sound,
    Direct sample mixing device
dsnoop:CARD=rkspdifsound,DEV=0
    rk-spdif-sound,
    Direct sample snooping device
hw:CARD=rkspdifsound,DEV=0
    rk-spdif-sound,
    Direct hardware device without any conversions
plughw:CARD=rkspdifsound,DEV=0
    rk-spdif-sound,
    Hardware device with all software conversions
usbstream:CARD=rkspdifsound
    rk-spdif-sound
    USB Stream Output
sysdefault:CARD=rkhdmidpsound
    rk-hdmi-dp-sound,
    Default Audio Device
dmix:CARD=rkhdmidpsound,DEV=0
    rk-hdmi-dp-sound,
    Direct sample mixing device
dsnoop:CARD=rkhdmidpsound,DEV=0
    rk-hdmi-dp-sound,
    Direct sample snooping device
hw:CARD=rkhdmidpsound,DEV=0
    rk-hdmi-dp-sound,
    Direct hardware device without any conversions
plughw:CARD=rkhdmidpsound,DEV=0
    rk-hdmi-dp-sound,
    Hardware device with all software conversions
usbstream:CARD=rkhdmidpsound
    rk-hdmi-dp-sound
    USB Stream Output
master@rockpro64:/etc/alsa/conf.d$

The initial announcement had some vague stuff about working with KDE. Is a custom KDE Neon version (like for the original Pinebook) in the works?

I started to reply to mmatyas thread but I feel like this is something different. Where mmatyas started with ayufan's Debian and performed a sloppy hack to turn it into ArchLinuxArm, I'm starting with Manjaro and attempting a sloppy hack but I'm not having any luck...yet.
Edit: I prematurely wrote that I'm not having any luck. I was successful in working back through method 2.

Method 1:
1) Follow installation steps 1 trough 6 on Arch Linux ARM's Rock64 page.
2) Download and extract Manjaro image (this exact image may be nonexistent or outdated as you're reading this)
3) Copy boot.scr, idbloader.img, trust.img, and uboot.img from the boot directory of the extracted Manjaro image.
4) Continue following steps 7 through 9 Arch Linux ARM's Rock64 page using Manjaro's boot.scr, idbloader.img, trust.img, and uboot.img instead of downloading from archlinuxarm.org.
5) Attempt to boot.
I'm hoping someone can explain to me why I'm an idiot and this doesn't work.

Method 2:
1) Burn before-mentioned Manjaro image to disk and boot into Manjaro.
2) # cp /etc/pacman.d/mirrorlist /etc/pacman.d/mirrorlist.bup
3) # echo 'Server = http://mirror.archlinuxarm.org/$arch/$repo" > /etc/pacman.d/mirrorlist
4) # rm /etc/lsb-release
5) # pacman-key init
6) # pacman-key --populate archlinuxarm
7) # pacman -Syu base-devel git
8) $ git clone https://gitlab.manjaro.org/manjaro-arm/p...kpro64.git
9) $ cd uboot-rockpro64
10) $ makepkg -si
11) Reboot and wait very patiently (several minutes).