Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 29,968
» Latest member: MichelleKonzack
» Forum threads: 16,334
» Forum posts: 117,438

Full Statistics

Latest Threads
Looking for engineer for ...
Forum: PinePhone Pro Hardware
Last Post: Andrey_voce
04-06-2026, 08:44 AM
» Replies: 0
» Views: 155
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
04-05-2026, 03:03 AM
» Replies: 19
» Views: 8,692
Finally got Kali working ...
Forum: General Discussion on Pinebook Pro
Last Post: qingss0
04-04-2026, 08:00 AM
» Replies: 0
» Views: 246
Charging problem
Forum: General Discussion on Pinebook Pro
Last Post: RicTor
04-04-2026, 07:30 AM
» Replies: 0
» Views: 111
Latest firmware for PineP...
Forum: PinePhone Software
Last Post: baptx
04-03-2026, 08:37 AM
» Replies: 106
» Views: 216,918
Updates have gotten me ex...
Forum: General Discussion on PineNote
Last Post: bills2002
04-02-2026, 05:16 PM
» Replies: 0
» Views: 203
Voidlinux working on eMMC
Forum: General Discussion on PineTab
Last Post: tllim
04-01-2026, 04:14 PM
» Replies: 1
» Views: 288
Pinecil V2 doesn’t power ...
Forum: General Discussion on Pinecil
Last Post: Juptin
03-28-2026, 02:37 AM
» Replies: 1
» Views: 2,080
dead Pinebook - help plea...
Forum: General Discussion on Pinebook Pro
Last Post: williamcorlin
03-26-2026, 04:22 PM
» Replies: 3
» Views: 938
BT PAN - we need iptables...
Forum: Mobian on PinePhone
Last Post: biketool
03-25-2026, 12:57 PM
» Replies: 1
» Views: 602

 
  Some power usage results of my Lexar NM520 M.2 2242 256GB NVMe
Posted by: Redbeard - 02-07-2020, 04:42 PM - Forum: Pinebook Pro Hardware and Accessories - No Replies

I've been playing around with my new Lexar M.2 drive and while my results aren't by any means scientific, I thought they might still be of interest to others.  All of these observations are specific to this one drive, on my PBP, running the default OS.

Lexar bills the drive as "ideal for smaller notebooks" and "an entry-level PCIe NVMe", and so far I think the description fits.  The three active power options for the drive are:

PS 0: 3.05W
PS 1: 2.44W
PS 2: 2.02W

The full power state information returned by the drive to nvme-cli is:

Quote:ps    0 : mp:3.05W operational enlat:0 exlat:0 rrt:0 rrl:0
          rwt:0 rwl:0 idle_power:- active_power:-
ps    1 : mp:2.44W operational enlat:10 exlat:10 rrt:1 rrl:1
          rwt:1 rwl:1 idle_power:- active_power:-
ps    2 : mp:2.02W operational enlat:10 exlat:10 rrt:2 rrl:2
          rwt:2 rwl:2 idle_power:- active_power:-
ps    3 : mp:0.5704W non-operational enlat:300 exlat:800 rrt:3 rrl:3
          rwt:3 rwl:3 idle_power:- active_power:-
ps    4 : mp:0.0054W non-operational enlat:1800 exlat:3700 rrt:4 rrl:4
          rwt:4 rwl:4 idle_power:- active_power:-


When I try to change the power state using the -s switch per the instructions on the wiki, it doesn't throw an error but the new setting doesn't persist after a reboot:


Code:
sudo nvme set-feature /dev/nvme0 -f 2 -v 2 -s

However, there is a workaround for drives that won't save settings across reboots, using crontab.  

Interestingly, I've found that if I set the drive to an inactive power state (PS 3 or 4), and then click on the drive to open it, Debian sets the power state to 1, instead of the otherwise default of 0.  Also, regardless of what power state the drive is in when the laptop is put to sleep, Debian resets it to state 0 on wakeup.  

I've toyed with the idea of setting a cron job to run every few minutes to reset the power state to 4, since I'm not currently using it as root and what I really want it for is fast (compared to an SD card) access to periodically needed data.  My thought was that this would minimize the power draw the bulk of the time, and still give me fast access to the data when needed.  However, while drive state 1 would be fine for my purposes, I'm not sure how much power this would really save while idle.  Whatever the difference, it is too small for me to really measure (more on this below).  

To get a better handle on how the drive performed in different scenarios, I wrote a simple loop to continuously read from the drive while reporting current power state, temperature (of the drive and CPU), and a rough estimate of read speed.  I toyed around a bit with write speed as well, but didn't do as much sampling because SSDs are a consumable when it comes to writes.  Here is the loop I ran in bash:  


Code:
for i in {1..30}
do
    date    
    tmpfilename="/home/rock/ssd/f3temp/10gb.tst"   
    echo "copying:  " $tmpfilename " to the bitbucket." 
    echo; echo "Drive power state is:"
    sudo nvme get-feature /dev/nvme0 -f 2    
    starttime=$SECONDS
    cp $tmpfilename /dev/null
    cp $tmpfilename /dev/null
    endtime=$SECONDS
    secondstocopy=$(($endtime-$starttime))
    echo "Seconds to read 10GB file to bitbucket two times: " $secondstocopy
    mbpersec=$((21474/$secondstocopy))
    echo "Speed is " $mbpersec " MB per second."
    echo; echo "Drive power state is:"
    sudo nvme get-feature /dev/nvme0 -f 2    
    echo; echo "Drive temperature is:"
    sudo nvme smart-log /dev/nvme0 | grep "temperature"
    echo; echo "System temperature is:"
    cat /sys/class/thermal/thermal_zone*/temp
    echo; echo
  done

While the script was running I modified the power state of the drive as well as the PBP CPU power settings, and opened up the power statistics utility in the default Debian.  While each test was running I waited as the screen dimmed and the power used "Rate" statistic continued to drop.  Once "Rate" stopped going down I noted the total watts along with the other information in the tables below:

Under Read Load.  CPU set to On Demand 
Power State     Drive Temp     CPU Temp     Total Watts      Read MB/S low     Read MB/S high
0                        51                     55                     6.3                   613                          631
1                        49                     49                     5.4                   488                          499
2                        50                     48                     5.0                   363                          370

Under Read Load.  CPU set to 1.99  Ghz
Power State     Drive Temp     CPU Temp     Total Watts     Read MB/S low     Read MB/S high
0                        51                     57                     6.7                   631                          650
1                        50                     54                     6.0                   511                          na
2                        50                     53                     5.9                   397                          na

I included the two temp readings since changes in temp give a rough indication of changes in energy use.  However, the absolute values vary by the ambient temperature when I did the test, so I generally wouldn't compare these figures across tables (but they should have some value within each table).  The two tables above make some intuitive sense, but my results when I set the cpu to 408 Mhz.  For some reason, throttling the CPU this way causes the normally slower power state of 1 to be faster than power state 0.  I ran this several times on different days, and every time I ran this the same pattern emerged:  

Under Read Load.  CPU set to 408  Mhz
Power State   Drive Temp   CPU Temp   Total Watts    Read MB/S low     Read MB/S high
0                     49                     44                 4.5                  311                          346
1                     49                     43                 4.8                  376                        390
2                     48                     42                 4.4                  278                        290

I have no idea what to make of that.

I also wanted to try to capture a difference between power consumption of the various power states at idle (not reading or writing).  There may well be a difference, but it wasn't something I could really capture.  Since I couldn't reliably capture a difference between the highest draw power states and the lowest draw ones, I ended up not filling in the chart with the missing states (PS 2 & PS 3).  Since the power draw figure reported tends to oscillate by a tenth of a Watt, I captured both the lower and higher observations for each state (in one sitting).  I thought I had found a slightly lower power draw for PS4 at one point, but then I ran the test again and it came back the same as the others (this is why I have PS 4 listed twice below):

Idle.  CPU set to On Demand
Power State     Low Watts     High Watts
0                       3.5                3.6
1                       3.5                3.6
4                       3.4                3.5
4                       3.5                3.6

The above was with a nearly fully charged battery.  When I did the same test with around an 85% charge the Wattage for all of the states I tested came back as 4.0.  I'm not sure if the battery charge was indeed the issue, or something else was up with the machine at that particular moment.

I don't have a final conclusion at this point, but for now it seems to me that setting the power state for this particular drive isn't that important, at least based on my current use model.  Setting the power mode of the CPU seems to manage power consumption of the drive at the same time.  However, others here might have a clearer understanding of what is going on here.  

I'll also note that pricing and availability of variants of this drive seem to be all over the map.  When I first started looking at it I planned on buying the 128 GB variant for just over $30 on Amazon.  Then that model went out of stock so I moved up to the 256GB model for $50.  Shortly after I ordered the larger drive, it too went out of stock, only to come back a week or so later for $100, which at the time was the same price as the 512 GB variant.  Now the 256 GB drive is back down to $50 on Amazon, but with expected shipping of 1-3 months, and the 512 GB variant is now $140.

If you can find one for a good price I think it is an excellent fit for the PBP, given both the size and power constraints.  I've attached a picture of the drive in my PBP after I trimmed the adapter.  Note that it looks like a 60mm drive would fit as well.  Since I took that photo I've added a 1.5 mm thick strip of thermal pad between the drive and the bottom of the case, which seems to be a perfect fit.

.jpg   trackpad_clearance.jpg (Size: 71.4 KB / Downloads: 3539)


  Pinephone unboxing
Posted by: H31GE - 02-07-2020, 03:16 PM - Forum: General Discussion on PinePhone - No Replies

Just a simpel unboxing for those who are curious.

https://www.youtube.com/watch?v=T8Y1nzxX...e=youtu.be


  LinuxFest Northwest Conference April 24th-26th @ Bellingham, WA
Posted by: xmixahlx - 02-07-2020, 12:30 PM - Forum: Community and Events - Replies (2)

Y'all are invited to attend LinuxFest Northwest April 24th-26th in Bellingham, WA USA.

LFNW is a ~2K attendee OSS/Linux/etc conference in its 21st year. Bellingham is between Seattle, WA and Vancouver, BC.

https://linuxfestnorthwest.org

Myself and my Pinebook Pro will be at the TAGNW booth.

TAGNW is a regional non profit organization focused on technology education, industry, and advocacy in our community.  We partner with LFNW and BLUG to provide the Job Fair and Business Development component on April 24th: TAG Expo.

https://www.tagnw.org
https://expo.tagnw.org
https://blug.org

Also, @Luke you have a PM!


  Sailfish still supported?
Posted by: Mangled - 02-07-2020, 11:43 AM - Forum: SailfishOS on PinePhone - Replies (4)

Hi,
I seen a post somewhere that Sailfish is no longer supported. Is Nemo the OS that took over the open source portion of Sailfish?


  My Phone won't Turn On
Posted by: DrewTechs - 02-07-2020, 09:38 AM - Forum: PinePhone Hardware - Replies (9)

I received my PinePhone (Braveheart Edition) and I was running postmarketOS on it yesterday (the OS on the SD Card). Now the device won't even turn on at all.

I had the device plugged into the charger all night and it still won't turn on. Is my phone no good already? If so, I want a refund because I expect my electronics to last more than a day.

Just for the record, I tried several things, such as putting the battery in and out, charging it (all night even) with different chargers (including the Nintendo Switch charger), I hit the Reset button on the back of the phone, etc.

What is going on here?


Question Printers in Manjaro
Posted by: TDC_PBP - 02-07-2020, 08:38 AM - Forum: Linux on Pinebook Pro - Replies (16)

Is there any GUI to install printers in Manjaro? The ubuntu mate build detected our printer (epson wf-35200) fairly easily via the printers tab in settings, but Manjaro does not appear to have a single setting relating to printers. If it all possible, I really don't want to mess around with CUPS.


  UBPorts Battery Observation
Posted by: appdev46 - 02-07-2020, 08:28 AM - Forum: UBPorts on PinePhone - Replies (17)

Has anyone noticed battery issues with UBPorts?  

I received my PinePhone and tried out UBPorts.  I did upgrade and update and played around a bit.  The phone was charged to 100%.  I locked the screen and went to bed.  In the morning the battery was completely dead. 

It appears the OS didn't go to sleep or something was running heavily enough to completely drain battery.


Question Flashing updated uboot in Manjaro
Posted by: TDC_PBP - 02-07-2020, 08:16 AM - Forum: Linux on Pinebook Pro - Replies (5)

Does anyone have clear, specific instructions on how to install the updated uboot in manjaro? I tried to follow these instructions in the /boot file in manjaro:
flash_uboot() {
  echo "A new U-Boot version needs to be flashed onto your install drive. Please use lsblk to determine your drive, before proceeding."
    echo "You can do this by running:"
    echo "# dd if=/boot/idbloader.img of=/dev/mmcblkX seek=64 conv=notrunc"
    echo "# dd if=/boot/u-boot.itb of=/dev/mmcblkX seek=16384 conv=notrunc"
}

## arg 1:  the new package version
post_install() {
  flash_uboot
}

## arg 1:  the new package version
## arg 2:  the old package version
post_upgrade() {
  flash_uboot
}
but....the second dd command failed (never gave any visible output) and I temporarily bricked my PBP Angry . I don't particularly want to repeat that experience EVER again, so I don't want to try it again until someone else gives it a good look over. Confusingly, I found these instructions printed in the terminal while doing pacman -Syyu:

(213/215) upgrading uboot-pinebookpro                [############################] 100%
warning: /boot/boot.scr installed as /boot/boot.scr.pacnew
warning: /boot/boot.txt installed as /boot/boot.txt.pacnew
A new U-Boot version needs to be flashed onto /dev/mmcblkX.
You can do this later by running:
# dd if=/boot/idbloader.img of=/dev/mmcblkX seek=64 conv=notrunc
# dd if=/boot/uboot.img of=/dev/mmcblkX seek=16384 conv=notrunc
# dd if=/boot/trust.img of=/dev/mmcblkX seek=24576 conv=notrunc
(214/215) upgrading xorg-server-common       

Thoughts/ideas??
P.S. I am running Manjaro from my emmc and did check to make sure I flashed the correct drive (the emmc)


Shocked Pinebook Pro Build Script Issues
Posted by: TDC_PBP - 02-07-2020, 08:06 AM - Forum: Linux on Pinebook Pro - Replies (3)

Has anyone been able to build a Kali Linux image with the build script? I have tried very hard on both the pinebook pro and another laptop to run it, and I have run into a few obstacles: first, when I run it on the PBP on Manjaro, the ./build-deps.sh script fails because the script uses apt-get. Then, when I switched to Ubuntu Mate, I discovered that the PBP's cross-compiler does not seem to be compatible with arm (apt-get can't find the package). Finally, I switched to another (intel cpu) laptop running elementary os, installed the compiler, and ran the ./build-deps.sh script without issues. But when I tried to run:

Code:
./chromebook-arm-exynos.sh 2019.2

I ran into the error:
Code:
Missing cross compiler. Set up PATH according to the README
I am becoming more and more knowledgeable about linux all the time, but this is starting to get over my head! Any help would be much appreciated Smile .


  Maskrom recovery mode/Recovering from broken SPI flashes ***IMPORTANT***
Posted by: as400 - 02-07-2020, 06:48 AM - Forum: Pinebook Pro Tutorials - No Replies

If you accidentally soft brick your PBP there is special mode implemented called maskrom mode. In this mode the device is accessible as regular USB device and can be accessed using rkdevelop tools. Especially to rewrite SPI flash or to erase it.

According to Rockchip documentation it should be accessible following below procedure:

1. Press and hold recovery button.
2. Short press reset.
3. Release recovery button after about 3 seconds.

Unfortunately it is not always the case. I had a clear SPI from factory and had to do this procedure trillion times to eventually get into maskrom mode. There is another person who had the same problems.

The nature of this problem is not clear. There are two suspicions:

- the button is not working correctly or is just prone to failures.
- the problem occurs only when the SPI was previously flashed.

One way or the other the button works shorting two pins in an SPI device. But in some cases it just does nothing. So if you experience such problem there is a way to overcome it. You can short the two pins by yourself.

Procedure:

1. Unscrew bottom cover.
2. Remove the metal shield surrounding main CPU - it is held in place by a tape and micro clamps on pcb.
3. Disconnect all (!!!) boot devices (emmc, sdcard, usb).
4. Locate SPI flash (number 29 on picture).


.jpg   PBPL_S.jpg (Size: 442.41 KB / Downloads: 7542)

5. Connect pbp with USB-C - USB-A cable to another computer (pbp on USB-C side).
6. Turn on pbp, short pins CLK and VSS and press reset. It should get your pbp into maskrom mode.


.png   spi.png (Size: 1.84 KB / Downloads: 1191)


On another computer:

1. Compile rkdeveloptools --> https://github.com/rockchip-linux/rkdeveloptool

2. Create a file filled with zeros:

Code:
dd if=/dev/zero of=zerospi bs=1M count=16


3. Then flash this file to SPI using rkdeveloptool:

Code:
Code:
rkdeveloptool db rk3399_loader_spinor_v1.15.114.bin
rkdeveloptool wl 0 zerospi
rkdeveloptool td
rkdeveloptool rd