Hi,
After about one and half year of h24 running my Pine64 with debian armbian 3.10.107, I got a black screen with some message and last a "Call Trace" once. Then it require to insert root password. Then, "Press Ctrl+D to Continue". If I press Ctrl+D it reboots, and again from beginning.
I want to leave you the log captured on:
Code:
/var/log/syslog
using pastebin: syslog
( It is not the entire log I've seen on my monitor. Is there a method to capture entire log in monitor during boot? )
Anyway, my question is: can I restore my Armbian SD without formatting?
Just getting my new pine64 NAS box up and running.
I've got the ayufan latest stable image loaded and running no issues (18.04 ubuntu).
I have the pcie sata card I bought from pine64.
I have them connected to two 3.5" Hitachi drives
The drives are powered and I did see a momentary light flash on the card but when I do a fdisk -L neither drive is listed.
Given all the hardware looks good does the ayufan built kernel not include that pcie board?
Why can't I see these drives?
hmm. if I just cat dev/disks/by-id I see them sda/sbd
Well something changed after a reboot I see the drives with fdisk now so ......nevermind
Dear team,
i just bought the new Rockpro64 and running Ubuntu18 LXDE image. Its running good. Happy with the product.
Also i have bought two cameras 13 MP and 5 MP CSI cameras just to experiment.
I have read the document related to both the cameras but still want to clarify that Does 5 MP camera will not work with Rockpro64?
As when i connect this and rebooted, it does not boot and throughs error.
As i am using linux OS thus 13 MP will not supported.
Basically in short please clarify both the cameras for linux image on Rockpro64.
It seems as if the shipment was not done in such a way that it can progress. It seems as if it was not shipped sufficiently funded.
Could you please tell me, when I am to expect a delivery? We would like to build a cluster of these machines, once we've tested its performance. But are now worried, that the sipping is done so badly, that we might just lose out money.
An Email of a week ago has gone unanswered.
The post I sent yesterday has gone without an answer too.
Is there a Rock64 Android which boots from USB? Preferably from Rock64's USB 3 socket?
This is what I have tried:
Bionic works flawlessly with a M.2 SSD in an USB 3 adaptor using the USB 3 socket.
With Etcher (Linux and Win10) and rock64_20171204_stock_android_7.1.2_rooted_emmc.img as well as rock64_20180606_stock_android_8.1_emmcboot.img Etcher reports "It looks like this is not a bootable image", this probably because of a missing partition table.
With Pine64Installer (v 2.0.0 beta 3, Win10) and Stock android 8.1 emmc (build 20180606) from the list I get "Invalid Message Unhandled rejection undefined Invalid message" after download.
Flashing ayufan's android-7.1-rock-64-rock64_atv-v0.3.13-r115-raw.img with Pin64Installer worked, but the image didn't boot.
Could you please tell me, when I am to expect a delivery? We would like to build a cluster of these machines, once we've tested its performance. But are now worried, that the sipping is done so badly, that we might just lose out money.
Hello,
I hated it to type sudo everytime for the simple rock64_health.sh-command, so I did some shell-voodoo to get the needed values from /sys without uid=0.
I was always interested in the gpu-temperature, too and with rockpro64 the frequency and governor of the A53/A72 cores. So I pimped the script further and got the attached one.
It should work on rock64 and 4.1x.x, too, but I have not tested it yet. Can some good soul can me give feedback on this?
Works like this:
Code:
$ rock64_health.sh
CPU count : 6
CPU 0-3
freq : 600.00 MHz
gov : ondemand
CPU 4-5
freq : 408.00 MHz
gov : ondemand
SOC Temp : 26.88 C
GPU Temp : 27.50 C
I use my Rock64 Pro as a simple browsing jump box. I VNC (TightVNC) to the Ubuntu Bionic LXDE Desktop (image)
(18.04 and latest TightVNC build) and browse normally using Firefox. However within 20 seconds to a minute or two of browsing the Rock64 Pro reboots. It doesn't seem to be any particualar web contect that is the issue, although there could be something inbedded I'm missing.
Other CPU heavy tasks don't cause an issue. Neither does browsing over VNC using Chronium.
I don't have visual access to the console so i can't see if there is any on screen panic info.
Anyone got any ideas or troubleshooting thoughts?
I've heard of pulse audio issues causing stability problems?
It;s causing the whole rock to reboot not just the firefox process to crash.
Does firefox utilise some specialist driver support for rendering which Chronium does not? Or perhaps TightVNC is the culprit?