Hi there! 

I'm brand new to the Pine 64 world, but I have tons of experience with the Raspberry Pi and linux.

I'm working on a project involving the SOPINE, but I'm really having trouble finding the info I need. One of the biggest issues I'm having is that I don't know what voltage rails I have to supply, and what I don't. Is there a data sheet somewhere that provides all this info, as well as info about what busses are where, and their specifications?

I've found the pinout, but that really doesn't tell the whole story.

Thanks in advance for your help!

-Connor

Was hoping to trade this for an old laptop but I guess it was not meant to be.  It's been collecting dust for a while and I just now accidentally stepped on it and broke the screen.   It's a shame cause it was barely used.  I want to part this thing out.  If you broke something on yours and need a replacement send me a message and I'll do my best to get you the spare part(s).

ANNOUNCING RECALBOX FOR THE ROCKPRO64 - ALPHA RELEASE

After many efforts with much teamwork, collaboration, and testing, we are very excited to provide the ALPHA release of RECALBOX for the ROCKPRO64 board!
-- The download is located under this repository's releases -- https://github.com/mrfixit2001/recalbox_rockpro64/releases
Details on the ROCKPRO64 SoC can be found here: https://www.pine64.org/?page_id=61454
For those of you unfamiliar with Recalbox: https://www.recalbox.com/ "Recalbox offers a wide selection of consoles and game systems. From the very first arcade systems to the NES, the MEGADRIVE, 32-bit platforms (such as the Playstation) and even Nintendo64. With Kodi already included, Recalbox also serves as a Media Center. By connecting it to your home network, you will be able to stream videos from any compatible devices (NAS, PC, External HDD, etc.)."
Please do keep in mind that this is a ALPHA release, which means you should still EXPECT some things not to work quite right. We have done a LOT of testing on our own to try and resolve as many issues as we can before this release, but now you get to help! (Lucky you!) So if/when you do find things that don't work right, please use the link in github to report the issue.
When reporting issues:

• Provide logs or screenshots of the issue so that we can see the error(s) you are seeing
  
  
• Provide detailed steps for us to follow in order to reproduce the issue
  

• Remapping the buttons on some controllers, such as 8BitDo, cause the controller to not work in the emulators – use the default keymaps for these
  
  
• Resolution for Non-Retroarch Emulators and EmulationStation is 1080p, manual config edit will be needed to change: o Mount the BOOT partition and edit /boot/extlinux/extlinux.conf -- look for the following value: video=HDMI-A-1:1920x1080@60. Edit to your desired resolution. o NOTE: Resolution in KODI can be adjusted without any config changes (up to 4k!)
  
  
• Netflix Kodi app is included – you can login but it does not currently play anything (yet)
  
  
• When the image first boots, you can expect a delay as the partition is expanded to the full size of your disk. Please be patient and let this complete. It will not happen on every boot, but you should not interrupt this process or you may need to reimage.
  
  
• N64 has multiple cores, different ROMS work better with different cores! For example, Mario Kart and Perfect Dark both perform very well using the N64 core (which is “GLES2N64”).
  
  
• Some emulators / cores are highly dependent on a valid BIOS files being installed (Dreamcast, for example). Be sure to read the documents in the system’s ROM folder for details on what BIOS files are needed. Further documentation is available on the Recalbox wiki.
  
  
• A single ROM not working is not considered a “bug”, it’s often an incompatibility with the ROM and the emulator or core. We have provided multiple cores for some emulators to try and help maximize the number of ROMS that work.
  
  
• If you are suddenly and unexpectedly thrown into KODI, then that means EmulationStation may have crashed. Please provide your /recalbox/es.log file so we can review.
  
  
• We STRONGLY recommend that you install a heatsink on the board
  

• Upgraded Kodi (and addons) from version 17 (Krypton) to a July 2018 commit of version 18 (Leia)
  
  
• InputStream.Adaptive Kodi Addon
  
  
• Multiple cores for different emulators so that you can select which core works best for you on each ROM!
  
  
• Slight default overclock
  
  
• HDR and 4k Media Playback!
  
  
• Included Wolfenstein 3D (shareware version) in DosBox
  
  
• CEC working in KODI
  
  
• IR working in KODI – supports multiple remotes out of the box, including the Pine64 / Rockbox remote
  
  
• Added some default shader presets and default cores
  
  
• Updated Library Versions with Buildroot 2018.2-3
  
  
• Custom patches to ES and Emulators to improve overall stability
  

• Mr Fix-IT
  

Greetings!

I am curious about something: as I know so far, RockPro64 should be more powerful than Odroid-XU4.

The overall experience makes it seems so (installing, browsing, response time, etc)

Checked hardinfo's benchmark, and it confirmed it.

Cryptohash benchmark says RockPro64 is 226.12 and Odroid-XU4 is 198.49 - another evidence.

However, I tried it by mining a cryptocoin aswell, and I have troubling results. With Odroid, I was capable to do it with 32khash, but with RockPro64 it was only 27khash.

Can someone explain why RockPro64's hashrate is lower than Odroid-XU4's?

Is it something to do with the kernel (which one is the most recent?)? Or is it because the clock rate or the number of threads? (Though I have to add that this mining program is armhf, but I managed to make it work by adding the armhf architecture)

Hi everyone,

I have a Pine64+ 2 GB board with, WiFi module and ABS case for sale. This was originally purchased through the Kickstarter but I just haven't used it to its potential hence why I am selling.

I was looking for £15 plus shipping. I am in the UK but willing to ship worldwide. Reply or PM me if you are interested with you're location and I'll reply with the shipping costs.

I have been away from home for a long time and haven't used my Pinebook. I have read that an amber light would indicate the battery is charging. This light doesn't turn on, even after inserting the power cable multiple times (>10).

I have been searching the internet for a replacement battery, but the model number can not be found. The voltage 4.35V is also an unusual number. It seems that voltages are always a multiple of 3.7V.

Is there anyway I can reanimate my Pinebook? Or have I been robbed of my money with a now useless product.

Hey all,

I am trying to put together a list of features/options that are working/not working between Linux (Bionic 18.04) and Android (7.1.2). I would also like to provide info on how to test/verify each.

Ideally I would like to turn this into a wiki page but would like to gather info first.

Sadly it looks like there is no support for BB tables or any other ones.  This is the best I can do to start until I get this on the wiki.

Tôi hiện đang làm việc trên nhiều dự án sử dụng OpenCV và đã tự hỏi nếu có ai đó đã thành công trong việc làm việc trên PineA64 do nó có CPU ARM64 chứ không phải phiên bản ARMv7 hoặc ARMv8 (Simlar to the TX2 hoặc RP3).

bionic-minimal-rock64-0.7.8-1061-arm64.img.xz


<perniciouscaffe> seeing an ongoing issue where my rock64 locks up when trying to scp files. Using bionic-minimal-rock64-0.7.8-1061-arm64.img.xz
[15:33] <perniciouscaffe> copies the first 50MB or so, then either reboots or becomes unresponsive, etc
[15:36] <perniciouscaffe> this is all microsd - no attached storage. Through the Ethernet interface
[15:45] <perniciouscaffe> doing an upgrade and will try to install the linux-crash packages for another test.
[16:15] <perniciouscaffe> meh - yeah. full reboot when the xfer stalls out.
[16:16] <perniciouscaffe> https://gist.github.com/jsutch/421f6fa5c...f1796ed7a1

Fresh install, apt update/upgrade. kernel dump from syslog above. Consistently reproducible.

Any thoughts?

I have a rockpro64 with bionic-minimal-rockpro64-0.7.10-1072-armhf.img installed on a sd card.
It runs just fine until I tried to install a desktop.

I ran /usr/local/sbin/install_desktop.sh mate and it installed a gazilion of packages.

After reboot I just get a cursor on a blank screen. After investigating the logfile ~/.local/share/xorg/Xorg.0.log it says:


...
[  2609.954] (EE) AIGLX error: dlopen of /usr/lib/arm-linux-gnueabihf/dri/armsoc_dri.so failed
(/usr/lib/arm-linux-gnueabihf/dri/armsoc_dri.so: cannot open shared object file: No such file or directory)
[  2609.954] (EE) AIGLX: reverting to software rendering
[  2610.034] (II) IGLX: enabled GLX_MESA_copy_sub_buffer
[  2610.037] (II) IGLX: Loaded and initialized swrast
[  2610.037] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[  2610.038] (II) ARMSOC(0): Setting screen physical size to 508 x 285
[  2610.070] (EE) ARMSOCPrepareAccess: Failed to map buffer
......

I cant find the file armsoc_dri.so anyware. Any tips?