| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 30,107
» Latest member: yt808
» Forum threads: 16,362
» Forum posts: 117,532
Full Statistics
|
| Latest Threads |
Pinephone software
Forum: General Discussion on PinePhone
Last Post: zetabeta
6 hours ago
» Replies: 1
» Views: 125
|
Rock64 v2.0 u-boot SPI is...
Forum: General Discussion on ROCK64
Last Post: ju0n
Yesterday, 11:02 AM
» Replies: 0
» Views: 68
|
Libby - ebook reader that...
Forum: PineNote Software
Last Post: kiwigoldfish
07-04-2026, 04:41 PM
» Replies: 6
» Views: 4,026
|
PineNote v1.2 - Charges N...
Forum: General Discussion on Pinebook Pro
Last Post: ttsp
07-02-2026, 02:52 AM
» Replies: 0
» Views: 221
|
How to change the PineNot...
Forum: General Discussion on PineNote
Last Post: cameronharring
07-01-2026, 12:22 PM
» Replies: 0
» Views: 115
|
PinePhone Pro disable Vol...
Forum: PinePhone Pro Hardware
Last Post: FR_IV
07-01-2026, 10:53 AM
» Replies: 1
» Views: 1,588
|
Star64/Starpro64 kernel b...
Forum: General
Last Post: tgbgreen
06-30-2026, 12:17 PM
» Replies: 1
» Views: 2,200
|
Manjaro affected by Arch ...
Forum: General
Last Post: tantamount
06-28-2026, 10:45 AM
» Replies: 0
» Views: 268
|
Fix Bricked SPI Flash, Pi...
Forum: PinePhone Pro Hardware
Last Post: FR_IV
06-27-2026, 05:00 PM
» Replies: 0
» Views: 192
|
irradium (based on crux l...
Forum: Linux on RockPro64
Last Post: mara
06-27-2026, 04:09 PM
» Replies: 12
» Views: 19,669
|
|
|
| manjaro and qemmu+kvm |
|
Posted by: erchache2000 - 02-25-2019, 04:53 AM - Forum: Linux on Pinebook
- Replies (2)
|
 |
Hi, im trying to install qemmu on pinebook using manjaro.
I see kernel has enabled KVM via dmesg, but when try to create qemmu image ovmf files arent installed.
Strit said Anarsoul is kernel maintainer of manjaro-arm for pinebook.
But some packages aren't on majaro, like this, https://aur.archlinux.org/packages/ovmf-aarch64/
Any tips to install correctly qemu+kvm on pinebook?
I found more problems with qemu on manjaro arm pinebook.
sudo systemctl status libvirtd
● libvirtd.service - Virtualization daemon
Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: disabled)
Active: active (running) since Mon 2019-02-25 12:21:05 CET; 2min 5s ago
Docs: man:libvirtd(8)
https://libvirt.org
Main PID: 673 (libvirtd)
Tasks: 17 (limit: 32768)
Memory: 57.2M
CGroup: /system.slice/libvirtd.service
└─673 /usr/bin/libvirtd
Feb 25 12:21:12 manjaro-arm libvirtd[673]: this function is not supported by the connection driver: cannot detect host CPU model for aarch64 architecture
Feb 25 12:21:12 manjaro-arm libvirtd[673]: this function is not supported by the connection driver: cannot detect host CPU model for aarch64 architecture
Feb 25 12:21:58 manjaro-arm libvirtd[673]: this function is not supported by the connection driver: cannot detect host CPU model for aarch64 architecture
Feb 25 12:21:58 manjaro-arm libvirtd[673]: this function is not supported by the connection driver: cannot detect host CPU model for aarch64 architecture
Feb 25 12:21:59 manjaro-arm libvirtd[673]: this function is not supported by the connection driver: cannot detect host CPU model for aarch64 architecture
Feb 25 12:21:59 manjaro-arm libvirtd[673]: this function is not supported by the connection driver: cannot detect host CPU model for aarch64 architecture
Feb 25 12:22:06 manjaro-arm libvirtd[673]: this function is not supported by the connection driver: cannot detect host CPU model for aarch64 architecture
Feb 25 12:22:06 manjaro-arm libvirtd[673]: this function is not supported by the connection driver: cannot detect host CPU model for aarch64 architecture
Feb 25 12:22:06 manjaro-arm libvirtd[673]: this function is not supported by the connection driver: cannot detect host CPU model for aarch64 architecture
Feb 25 12:22:06 manjaro-arm libvirtd[673]: this function is not supported by the connection driver: cannot detect host CPU model for aarch64 architecture
|
|
|
|
| [Solved] Unhappy unboxing - delivery missing $163.38 of material |
|
Posted by: caillou - 02-24-2019, 04:50 AM - Forum: Shipment Related Discussion
- Replies (3)
|
 |
Edit:
I received a second package today with all the missing parts. All is good, let the hacking begin!
—-
Original message:
Yesterday, I received a package from Pine64.
Unboxing revealed the metal NAS case, but noting else.
Here is the list of the material I ordered and payed (order #98369):
- ROCKPro64 4GB Single Board Computer ($79.99)
- ROCKPro64 2x2 MIMO Dual Band WIFI 802.11AC/BLUETOOTH 4.2 MODULE ($15.99)
- ROCKPro64 30mm Tall Profile Heatsink ($3.49)
- Fan for ROCKPro64 Metal Desktop/NAS casing ($3.99)
- ROCKPro64 Metal Desktop/NAS Casing ($44.99)
- ROCKPro64 12V 5A EU POWER SUPPLY ($12.99)
- 64GB eMMC Module ($34.95)
- SERIAL CONSOLE ($1.99)
- ROCKPro64 PCI-e to Dual SATA-II Interface Card ($9.99)
Total: $208.37
Is it normal for Pine64 to deliver the orders in separate packages, or is this an error?
How should I proceed?
|
|
|
|
RETRO GAMING: UPDATED RECALBOX FOR THE RK3399 ROCKPRO64 |
|
Posted by: Mrfixit2001 - 02-22-2019, 03:34 PM - Forum: Linux on RockPro64
- Replies (38)
|
 |
ANNOUNCING RECALBOX FOR THE RK3399 ROCKPRO64
After many efforts with much teamwork, collaboration, and testing, we are very excited to provide the release of RECALBOX for the ROCKPRO64 board!
-- The download is located under this repository's releases --https://github.com/mrfixit2001/recalbox_...4/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.)."
When reporting issues: - Provide logs and/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
We STRONGLY recommend that you install a heatsink on the board CPU intensive tasks, such as 4K playback and demanding emulators, can create a substantial amount of heat. You can monitor your board's temperature and stats by enter it's IP address in a browser.
For a list of previous enhancements, you can read this post:
https://forum.pine64.org/showthread.php?tid=7039
Latest Improvements:- Kernel updated to 4.4.171
- Additional mainline back-ports and custom fixes
- Additional drivers included in kernel
- PCIe now works with Wifi and Bluetooth all at the same time
- UART debug output enabled
- Custom "Rockpro Fan" toggle in menu under system settings
- Retroarch Updated to 1.7.6
- Newer versions of some emulators
- Pre-set optimized config for Mupen64
- Resolution for Mupen64, Reicast, and Retroarch can now be changed from recalbox.conf file
- Custom fix for widescreen's auto-stretching the picture (read the readme)
- On-Screen-Keyboard issue Resolved
- Custom patches to ES and Emulators to improve overall stability
- Additional fixes for XBox One and 8BitDo controllers
Some things that have been added to Recalbox that are Exclusive to my Pine64 releases:- Upgraded Kodi (and addons) from version 17 (Krypton) to version 18 (Leia) alpha release
- Netflix Kodi app is included – you can login but it does not currently play anything (yet)
- 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
- Provided some emulator default settings, shader presets, and default cores
- Updated Library Versions with Buildroot 2018.2-3
- Custom patches to ES and Emulators to improve overall stability
A few things to know about this release:
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.
Some controllers will work with KODI right out of the box without the buttons needing to be mapping (like the x360). For others, once you hit a button on the controller it will ask you to map them - you will need a keyboard to interact with KODI until your controller buttons are mapped.
N64 has multiple core options, different ROMS work better with different cores! So if your game isn't running well, try another core! So far even the most demanding games have been found to run perfectly with the right core selected.
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 / 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.
Important Note about Widescreens:
The majority of users will be using widescreen monitors and TVs with 16:9 aspect ratios these days, and most of these will automatically stretch a 4:3 video to 16:9 to make it full screen. This distorts the graphics and makes everything look stretched out and askew. So, I have added custom patches and new configuration settings to Mupen64, Reicast, and Retroarch to correct this so that the emulators will still render at the right scale after being stretched. This is ON by default. If you do not have a widescreen monitor, or your monitor does not have this auto-stretch feature, then your games may not be centered or look too thin. In this case, simply make the following one-time changes to the configurations to turn off these customizations:- Retroarch: use the retroarch menu to change the default - Settings->Video->Aspect Ratio
- Reicast: change the setting "rend.FixAspect" to 0 in /recalbox/share/system/configs/reicast/emu.cfg
- Mupen64: each video plugin (core) has been given it's own setting, allowing you to customize each to your own needs, and GLES2N64 (n64 core) has it's own config file. The settings for these plugins are in /recalbox/share/system/configs/mupen64 in the files mupen64plus.cfg and gles2n64.conf. Just change the listed widths and left offsets to whatever your needs are.
"Where's the source code?" The source is being cleaned up and organized in preparation to be made available for the recalbox team to maintain, instead of having it hosted in this repository. Merging it with the recalbox repo allows them to maintain and update it, which ensures that you will receive their updates as they are made available.
Lastly, please remember this is a community build, and just something I've worked on in my free time. There's no pressure at all, but if you appreciate the work then feel free to send me a buck on Paypal: mrfixit2001 at gmail.
Special thanks go out to the LibreELEC and Recalbox teams, as well as LukasZ at Pine64 for his huge efforts in research, testing, and feedback!
Mr Fix-IT
|
|
|
|
Tutorial[ Seagate Disks ]: Optimize Life Span/Power Managment |
|
Posted by: tuxd3v - 02-22-2019, 11:08 AM - Forum: RockPro64 Projects, Ideas and Tutorials
- Replies (14)
|
 |
Hello all,
Following the OpenSeaChest Utilities install here.
Documentation for Configuration: here
There are some nice tuning features,
That can increase disks Life Span, Consume Less current, and Increase Life Span of the power provider Source, etc..
1). Power Up In Standby Mode.
When System goes up and Power is provided to all components, Power Consumption spikes,
from processor to disks, and all peripheral components..
So in this fase,
Disks also consumes more power, because they need to start the Controller Board,
and Also start spinning plates , and moving heads..
Some Seagate Disks, have this option,
So to configure Power Up in StandBy( Its a Persistent Feature, so only apply one time, no reboot required ), disk( sdX ):
Code: openSeaChest_Configure --device /dev/sdX --puisFeature enable
In this Way,
When system goes Up, disks will push a lot less current,
because only Disks internal controller is up( StandBy Mode, also known as APM mode 1 ).
Only when you require access( Read Write, the disk will Start spinning and heads will move, and working with the APM configuration they already had..
So this feature is only working for, starting system up/powering the disks,
after that, this feature does nothing( disks are already Up ).
2). Low Current SpinUP
After System Up,
Each time they go StandBy, it stop spinning the plates, and park its heads..
But the problem is,
Each time you request access, they will need to start spinning the plates, and moving heads to read/write..
This start process, is painful, for power Consumption, and creates more vibration( it pushs several Amps in spikes for that.. )..
So to minimise it,
Seagate Disks have a Feature, to start spinning in a progressive way, instead of abrupt way.
To activate this Feature( Its a Persistent Feature, so only apply one time, a reboot is required ), disk( sdX ):
Code: openSeaChest_Configure --device /dev/sdX --lowCurrentSpinup enable
After steps 1). / 2). ,
Shutdown the system, if needed take disks out for a bit, insert them again,
Boot up and check if features are already enabled..
3). Control Park, and Unpark Mode:
When disks are spinning, after operations, and they are not been used,
They will go to a less aggressive power State.
Usually Power Mode 127, permits, that they enter in Standby, which means stop spinning and park Heads..
In this situation, you should monitor Park/Unpark Head, if the Number grows very fast or Not..
Command Bellow will measure Power Cycles and park/Unpark Count:
Code: apt-get install -y smartmontools && for blockid in {a..d};do smartctl --attributes /dev/sd${blockid}|grep -E "^ 12|^193"; done
If this values for example in 10-15 minutes grows significantly, the disk life will be Reduced..
Some Known Characteristics:
Seagate IronWolf/IronWolf PRO - '600000' Park/Unpark cycles
Seagate IronWolf - ~1,000,000 Hours MTBF( Mean Time Between Failures )
Seagate IronWolf PRO - ~1,200,000 Hours MTBF( Mean Time Between Failures )
3.1). If this value are already too big, or if increasing too fast( measure, for example, at beginning, and at the end of 1 week, .. for example.. ),
maybe consider, modes >=128
3.2). If this values don't grow too much, of if your disks have low values,
Then mode 127 seems the best,
Since you have a lower number of load/unload heads, disks "are like new" on that regard, and so, you can go standby more often..
4). Check if your disk( sdX ) Support Power Balanced Mode:
You can also configure a power Balanced mode, if your disk supports it..
Check if supported, disk ( sdX ):
Code: openSeaChest_PowerControl --device /dev/sdX --powerBalanceFeature info
5). To Check information on Features and so on, about the disks Capabilities,or Enabled ones,
You can type each time:
Code: openSeaChest_Basics --deviceInfo --device /dev/sdX
In this way you can check points 1)., 2)., 3)., 4). ...
This article could be improved in the Feature,
For now, here are the first Basic rules.
Hope you Enjoy,
Best Regards
NOTE:
1). The first 4 Points above, forms the base of Seagate Disks Configurations...
They prolong Disks Life Span,
They prolong Power Supply Life Span( in this, case power Supply of Rockpro64 )
They prolong Computer( in this case RockPro64 ) Life Span
They consume less energy.
2). Each Time you run a Command, if disk is in StandBy( sleeping ),
It could wake up the disk,if so, the number of Load/Unload Cycles will decrease by 1
**Use the tools**, to configure and check if your disks are well configured **only when needed**..
|
|
|
|
| About DSI's RGB888 format |
|
Posted by: r.tanaka - 02-21-2019, 07:38 PM - Forum: LCD and Touch Panel
- Replies (1)
|
 |
Hi
I set the DSI format to RGB888.
However, looking at the output of DSI seemed to be BGR888 format, why?.
About DSI format I confirmed the Allwinner A64 SoC specification, but I did not understand it well.
The software and hardware used are as follows.
software: Armbian
hardware: Pine A64-LTS
Thank you.
|
|
|
|
| Pinebook Issues |
|
Posted by: DannyJack - 02-21-2019, 03:41 PM - Forum: General Discussion on Pinebook
- Replies (6)
|
 |
Hi all
N00b over here. When my Pinebook boots (neon OS) it flashes the login page, then i get a blank black screen.
Not sure how to cure this and haven't found anything in here yet, please point me in the right direction if I am being st00pid!
Thanks
|
|
|
|
| emmc / sd or ssd? |
|
Posted by: LMM - 02-21-2019, 09:17 AM - Forum: General Discussion on ROCKPRO64
- Replies (3)
|
 |
Hello,
I have a question/remark concerning the "choice" between emmc / SD or ssd. Currently, the regular price for emmc of 64GB is rather in the same order of magnitude to a ssd of 120GB NVME. If I am not wrong, the SSD has a better performance than emmc, therefore, if it were possible to boot from PCIE, does it worth using emmc ? I read in the forum that many attempts has been done but end with a mix emmc for boot and ssd for root. @pine64 team : is there a really possibility to make the rockpro64 boot from PCIE ?
Best regards
|
|
|
|
Is this it? |
|
Posted by: bigbertha - 02-20-2019, 10:43 PM - Forum: Android on Rock64
- Replies (8)
|
 |
I have had my board for 3 weeks. I have used all 3 offering of the ANDROID. Stock 7.1, 7.1 ATV and Oreo. Are these the FINAL RELEASES for firmware for this board? The Android 7 has a 2017 security patch.... VERY DISSAPOINTING. The things constantly crashing programs. It really doesnt matter which app I run, it gets lost in la-la land and then offers close app/ wait/ send feedback dialog. I get the same error sometimes in system process and then it just locks up.
Hard to believe that the Popcorn transformer and rockbox were to have these as firmware. I have seen much better just from cheap china tv boxes.
I had such high hopes for this as I have fried a few TV boxes flashing and reflashing new firmware (*rom) and wanted something that I could replace emmc or just boot from sd.
None of the images have working GAPPS.....Hate the Android TV interface and have not seen any way to get notifications....
Armbian has worked and been very stable but was VERY saddened this board was not ready for primetime when it comes to ANDROID. I really didnt need another linux machine.
I am hesitant to believe my prob is running it just from sd instead of emmc when Linux works so well. but I will be considering buying a emmc module just to try it.
Things I wished this had was TWRP or a update installer that would allow you to just install open gapps and root it easily. Im sure I could do it the hard way with ADB. but... things should be easier for users (translation customers)
|
|
|
|
| Fedora-30 w/ kernel 5.0 |
|
Posted by: maya.b - 02-20-2019, 09:45 AM - Forum: Linux on PINE A64-LTS / SOPINE
- Replies (1)
|
 |
I've installed F-30 with lightdm running openbox or xfce on a sopine. The following should work the LTS board as well. It should be possible to get his all to work on pine64+ boards by changing 'sopine_baseboard' to 'pine64_plus' in the installer command below
Steps:
- follow the arm image creation (in a fedora environemt - I used an x86 vm for this) process found here: https://fedoraproject.org/wiki/Architect...stallation with the aarch minimal image from here: https://alt.fedoraproject.org/alt/
- I used
Code: arm-image-installer --adconsole --image=Fedora-Minimal-29-1.2.aarch64.raw.xz --resizefs --media=/dev/<yourSDCard>
- Boot into the newly created image with a UART console cable connected. Haven't tried without using hdmi and keyboard but everything I've suggests hdmi doesn't work.
- Follow the system upgrade process found here https://fedoraproject.org/wiki/DNF_system_upgrade and set releasever=30
- Now that you're running f-30 run:
- and pick the desktop environment (and anything else you want). I chose xfce and intalled it with:
Code: sudo dnf install @xfce-desktop-environment
- I also installed openbox with this:
Code: sudo dnf install elestall openbox xbacklight feh conky xorg-x11-drv-libinput tint2 volumeicon xorg-x11-server-utils network-manager-applet
I'm not sure which actually made it work, admitedly I was just throwing things at the command line remotely until I cam in this morning and ran:sudo lightdmto the desktop - top right hand corner you can pick between openbox and xfce for your session.
Enabling lightdm.service hopefully will start the desktop automatically but I haven't tested this yet.
Have fun with it!
M.
|
|
|
|
|