| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,697
» Latest member: john9
» Forum threads: 16,260
» Forum posts: 117,186
Full Statistics
|
| Latest Threads |
Hi everybody!
Forum: General
Last Post: MadisynErnser
5 hours ago
» Replies: 2
» Views: 2,206
|
PinePhone, PinePhone Pro,...
Forum: PinePhone Hardware
Last Post: brb78
11 hours ago
» Replies: 0
» Views: 33
|
Recycling pinephone as ho...
Forum: PinePhone Hardware
Last Post: biketool
Yesterday, 09:04 AM
» Replies: 5
» Views: 537
|
Old Danctnix server in Pa...
Forum: PineTab Software
Last Post: KelsonV
11-19-2025, 02:20 PM
» Replies: 0
» Views: 56
|
Light Sensor / Proximity ...
Forum: General Discussion on PinePhone
Last Post: WhiteHexagon
11-18-2025, 03:07 PM
» Replies: 1
» Views: 113
|
How to stop it turning on
Forum: General Discussion on PinePhone
Last Post: biketool
11-18-2025, 02:30 PM
» Replies: 3
» Views: 458
|
8/24 status of JumpDrive
Forum: PinePhone Software
Last Post: biketool
11-18-2025, 01:27 PM
» Replies: 5
» Views: 2,117
|
Questions about running U...
Forum: General Discussion on PineTime
Last Post: alicesphere
11-18-2025, 12:48 AM
» Replies: 0
» Views: 62
|
Difficulty with openSUSE ...
Forum: PinePhone Software
Last Post: danm1988
11-17-2025, 07:49 AM
» Replies: 0
» Views: 79
|
Second screen mirroring
Forum: General
Last Post: andrekyler
11-17-2025, 01:06 AM
» Replies: 3
» Views: 1,903
|
|
|
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.
|
|
|
|
| Unable to Run GNOME or KDE due to "dmidecode" segmentation fault |
|
Posted by: rrs64 - 02-19-2019, 03:50 AM - Forum: General Discussion on ROCKPRO64
- Replies (5)
|
 |
Hi All:
I've installed the following CentOS 7 image onto an SD card which successfully boots the RockPro64 with 4 Gb RAM and eMMC card:
Centos-7.4.1708 with kernel from Armbian-5.67.img.xz
It was downloaded directly from the Project31 GitHub web page:
https://project31.github.io/pine64/
After first boot the /root/finish-centos-install.sh script was run to complete setup.
Then GNOME was installed with the following command which completes successfully:
Code: # yum -y groups install "GNOME Desktop"
Next, attempt to launch GNOME using the command:
It fails to launch due to a segmentation fault from "dmidecode" shown below:
Jan 18 08:50:35 localhost nm-dispatcher: req:3 'connectivity-change': start running ordered scripts...
Jan 18 08:50:36 localhost kernel: Bad mode in Error handler detected, code 0xbf000000 -- SError
Jan 18 08:50:36 localhost kernel: Internal error: Oops - bad mode: 0 [#1] SMP
Jan 18 08:50:36 localhost kernel: Modules linked in: af_packet xt_tcpudp ip6t_rpfilter ipt_REJECT nf_reject_ipv4 ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute bridge stp llc ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter dm_mirror dm_region_hash dm_log snd_soc_rockchip_hdmi_dp ip_tables x_tables autofs4
Jan 18 08:50:36 localhost kernel: CPU: 5 PID: 727 Comm: dmidecode Not tainted 4.4.166-rockchip64 #17
Jan 18 08:50:36 localhost kernel: Hardware name: Pine64 RockPro64 (DT)
Jan 18 08:50:36 localhost kernel: task: ffffffc0e9475400 task.stack: ffffffc0e941c000
Jan 18 08:50:36 localhost kernel: PC is at 0x7f8cc65cd0
Jan 18 08:50:36 localhost kernel: LR is at 0x7f8cc65ca0
Jan 18 08:50:36 localhost kernel: pc : [<0000007f8cc65cd0>] lr : [<0000007f8cc65ca0>] pstate: a0000000
Jan 18 08:50:36 localhost kernel: sp : 0000007fc7ebf2f0
Jan 18 08:50:36 localhost kernel: x29: 0000007fc7ebf2f0 x28: 0000000000000000
Jan 18 08:50:36 localhost kernel: x27: 0000000000010000 x26: 0000007f8cbc1000
Jan 18 08:50:36 localhost kernel: x25: 0000005575e22720 x24: 0000005575e3f000
Jan 18 08:50:36 localhost kernel: x23: 0000000000000000 x22: 0000000000010000
Jan 18 08:50:36 localhost kernel: x21: 0000007f8cbc1000 x20: 00000055ae82f010
Jan 18 08:50:36 localhost kernel: x19: 00000055ae82f010 x18: 0000007fc7ebf390
Jan 18 08:50:36 localhost kernel: x17: 0000007f8cc65be0 x16: 0000005575e3fe40
Jan 18 08:50:36 localhost kernel: x15: 0000000000005788 x14: 0000007f8cbe2a94
Jan 18 08:50:36 localhost kernel: x13: 0000000000000000 x12: 0000000000000008
Jan 18 08:50:36 localhost kernel: x11: 0000005575e22720 x10: 0000007f8cbe4c28
Jan 18 08:50:36 localhost kernel: x9 : 000000000008ab48 x8 : 00000000000000de
Jan 18 08:50:36 localhost kernel: x7 : 0000000000000023 x6 : 000000000000007c
Jan 18 08:50:36 localhost kernel: x5 : 00000000000f0000 x4 : 0000000000000000
Jan 18 08:50:36 localhost kernel: x3 : 0000000000000000 x2 : 0000000000002000
Jan 18 08:50:36 localhost kernel: x1 : 0000007f8cbc1000 x0 : 00000055ae82f008
Jan 18 08:50:36 localhost kernel:
Jan 18 08:50:36 localhost kernel: Process dmidecode (pid: 727, stack limit = 0xffffffc0e941c000)
Jan 18 08:50:36 localhost kernel: ---[ end trace 5795f018d82a6a48 ]---
The same segmentation fault occurs at the command line if "dmidecode" is run by itself.
Re-booting, 'yum update'. or starting over with a new SD card does not help.
Has anyone else had the same problem trying to install and run GNOME (or KDE) on CentOS on RockPro64?
This issue is a real blocker trying to get a graphical interface up and running.
Any hints or suggestions are welcome.
Thanks
|
|
|
|
|