I use an at to DC in to power my board. now the other day I unplugged my power unit everything was switched off before I did and such. when i plugged it back in my amprage was significantly lower my VSB wire is usually 3A at 5V now it's reading .25A at 5V and the 12V wires are all reading 1A roughly and I was wondering if any one has encountered this problem before.

Sent from my VS995 using Tapatalk

Hi all!
today i started my clusterboard project but i found the first big problem.
i flashed the memory card with Armbian image, put the Sopine module in his riser, turned the clusterboard on and nothig happens.
All the led near the riser never turns on, the RJ45 leds sometimes blinks for less than a second, but nothig appear connected to my switchport.
The only turned on led is the one on the sopine module..

Is this happened to someone else?
the img that i'm using is Armbian_5.41_Pine64so_Ubuntu_xenial_next_4.14.20.img (working perfectly on LTE board)
tried all the sopine modules with the same result.

Thanks to everyone for help

Hello,

All is in the subject. I wonder what is a good configuration for programming on a Rock64 SBC?

regards

As part of our big project, we are using the ROCK64(1G with 0.5.15-136) with FORSEE eMMC module. We have observed corruption issue very often. Most of the time, during the reboot, it shows that lot of bad block checks and trying to recover. During this time, sometimes it won't recover and it ends with initramfs prompt.  Where we are completely loosing partition 7 (root file system). 

Is this common with FORSEE? We tried other vendors of eMMC, where these are coming with some padding for other side of the connector, which seems little reliable than FORSEE. We are suspecting this as something mechanical issue.

However if we need to recover I would think we need to forced fsck on every boot before mounting the partitions. But when booting it complains about fsck is not available with initramfs. Is there anyway to include fsck with initramfs? or any other practices are available to overcome these issues?

THanks,
Ramprasad

Hi
Any clues about rock64 stuck after applying soft reboot from shell?

Hi All,

I recently bought this device ROCK64 USB WIFI 802.11B/G/N for several reason: to help the project and to find a reliable wifi dongle. So I was convinced this wifi dongle would work out of the box but it didn't. I was struggling with the OS for several hours, trying to understand why it wouldn't work properly. I was convinced it was because a forced shutdown I had to do but now I realized it was the dongle that frozen the O.S.

You promote this dongle on your store as ROCK64 USB WIFI while is a whatever wifi dongle that you can buy everywhere. The problem with it is that it prevents Debian as well as Android to boot, it is not even reliable as wifi dongle since the moment "Android root" stopped to recognize it and now it is complete useless for the R64 board.

To recap, I lost all the hours to setup my OS and a lot of hours to try to fix and issue that was caused by this dongle, sponsored as Rock64 wifi, because it has several issues and it is not recognized by the android kernel as well as the Linux kernel. Obviously at that moment the last think I thought was the dongle since the moment I was convinced it was 100% compatible...

My advice is to remove it from your store or update the kernel for the OSes you provide: official and community version. For the future you had better to check the hardware you sell frequently to avoid this kind of complaining.

Thanks,

D.

Hi Everybody!

I' received few time ago a Rock64 2G I'll like o use as media server
I'm also trying to connect GPIO to a prototyping board through a ribbon cable 28AWG 40wires (similar to the ones once used for ATA disk) but as soon as I try to connect this cable I have loads of error

androide i rock64 4gb alatt Linux max internet sebesség gigabit.304.62 Mbit / s android korlátozott internet sebessége 80 -104.62 Mbit / s.
miért, mit tegyek. Kösz

Hi ,

Coming chrome 68  google will label  'not secure' HTTP

https://www.computerworld.com/article/32...ummer.html

Hi All,

I had to force the shutdown but after Android Root goes only on Android Recovery mode. I erased, formatted and reflashed the SSD card, the system reinitialized itself but eventually went on recovery again. I read the board has 128 mega dedicate to boot maybe the issue is on that, how can I reset this memory or fixing my current issue?

I flashed another image (Debian minimal), booted it into the board, shutdown it, reflashed the ssd with Android. It worked!