TL-DR:
No matter what medium is inserted, my PBP does not turn on.
Yesterday, when my PBP arrived, I was trying to install Manjaro on it. Because I only had an 8 GB microSD card around, I put the Manjaro installer on it, which contains an archive of an image of a working Manjaro install. That image is too big to fit on the microSD-card next to the archive. So while having booted the installer SD-card, I created a new partition table (GPT) on the eMMC-Disk (mmcblk2) and created one single ext4 partition, where I moved the archive, extracted it and copied the Image back to the microSD-card. To continue with the installation, I tried to reboot the PBP while still having the SD-card inserted, but sadly had to see, that my PBP would not turn on anymore.
What I have tried (and basically all combinations):
* Pulling the battery plug and putting it back in
* Pressing the reset button
* Booting it with a known-good microSD-card (and without one)
* Booting it with eMMC enabled / disabled
* Booting it with the eMMC-Module removed
* Booting it with and without the power adapter attached
What I noticed doing that:
* The Power LED does not turn on (which makes sense, because it's software controlled, as a user on the IRC pointed out)
* The Screen stays blank (backlight does not turn on)
* No Output on the serial console (Controlled by Linux)
* No Coil whine at all
* (I am not sure about this) the SoC felt slightly warmer than the rest of the device
I have asked in the IRC for help. Another user seems to have the same problem, their PBP was also in the same batch as mine (2019-12-24, ISO)
As I do not have much money (I am a student) and bought this laptop as my daily driver, I am very, very hesitant to do any hardware measurements / modifications as I am not especially talented doing that and can't risk this laptop.
Has anyone else seen this before or even recovered a PBP from this state?
I would be very glad to hear from that.
I am new to the Pinebook Pro, but not Linux in general, and wanted to share some first thoughts on some tests I have made. Please note these are offered in the spirit of wanting to help, not as criticism. I am not in need of help to fix these things.
At first boot, I ran the updater. it shows 0 updates needed. This seemed unrealistic, so I ran sudo apt update in a terminal; it showed 90 updates available. I ran the updater again, but it still showed 0. I updated successfully anyway from the terminal.
Launching Chrome showed the Keyring request - potentially confusing for a newcomer?
I tried opening some standard testing files I use:
Graphics files opened in Nomacs as expected
Video files opened in SMPlayer, although there was a message warning the version of SMPlayer was out of date
A PDF file tried, but failed, to open in LibreOffice Draw; it seems there is no app for PDFs installed
MP3s open in SMPlayer, not RhythmBox. I was able to change that.
Using Caja, I tried browsing shares on my local network with the following problems:
Attempting to play video opened SMPlayer, but it crashed
Graphics files (PNG and JPG) tred to open Firefox, but failed. Forcing Nomacs works for the first image, but not subsequently
There appears to be no means to add a printer. Mine is connected to the local network. I got it working as follows:
Install system-config-printer
Install cups
From the run (Alt-F2) dialogue, run gksudo system-config-printer. (I subsequently modified the menu entry to run it as sudo)
This enabled the printer to be found and installed.
[*]Hope at least some of this might be of help.
[*]
I have many questions about my new pinbook Pro. The first is the command to active power of the NVME. sudo nvme id-dtrl /dev/nvme0 is not found on my computer. The seconde is about the network connection. In fact, I'm connecting in my box, I have a good connection on my other computers, but on Pinbook Pro it's not possible to realise a network research on chromium or firfox.
NetBSD über-hacker Jared McNeill started working on the Pinebook Pro. In the previous hours, he posted a series of Pinebook Pro related posts on his twitter account https://twitter.com/jmcwhatever showing the boot up and even running xorg.
I got my Pinebook Pro 2 days ago and so far I appear to get slightly less than 2 hours of battery life. I have seen others write that they get 8-10 hours so I am wondering what can be done. energy-rate is between 15-20 W when ony doing light web browsing with the screen at a very low brightness. I have attached a upower -d log. Thanks.
Code:
Device: /org/freedesktop/UPower/devices/line_power_dc_charger
native-path: dc-charger
power supply: yes
updated: Wed Jan 1 08:24:41 2020 (12 seconds ago)
has history: no
has statistics: no
line-power
warning-level: none
online: no
icon-name: 'ac-adapter-symbolic'
Device: /org/freedesktop/UPower/devices/battery_rk_bat
native-path: rk-bat
power supply: yes
updated: Wed Jan 1 08:24:51 2020 (2 seconds ago)
has history: yes
has statistics: yes
battery
present: yes
rechargeable: yes
state: discharging
warning-level: none
energy: 34.5379 Wh
energy-empty: 0 Wh
energy-full: 40.1604 Wh
energy-full-design: 0 Wh
energy-rate: 15.9406 W
voltage: 4.098 V
time to empty: 2.2 hours
percentage: 86%
temperature: 18.8 degrees C
capacity: 100%
technology: lithium-ion
icon-name: 'battery-full-symbolic'
History (charge):
1577867091 86.000 discharging
History (rate):
1577867091 15.941 discharging
1577867085 16.719 discharging
Device: /org/freedesktop/UPower/devices/line_power_universal_usb
native-path: universal_usb
power supply: yes
updated: Wed Jan 1 08:24:41 2020 (12 seconds ago)
has history: no
has statistics: no
line-power
warning-level: none
online: no
icon-name: 'ac-adapter-symbolic'
Device: /org/freedesktop/UPower/devices/DisplayDevice
power supply: yes
updated: Wed Jan 1 08:24:50 2020 (3 seconds ago)
has history: no
has statistics: no
battery
present: yes
state: discharging
warning-level: none
energy: 34.5379 Wh
energy-full: 40.1604 Wh
energy-rate: 15.9406 W
time to empty: 2.2 hours
percentage: 86%
icon-name: 'battery-full-symbolic'
Daemon:
daemon-version: 0.99.4
on-battery: yes
lid-is-closed: no
lid-is-present: yes
critical-action: PowerOff
Hello
I need help. I have received my first PinePhone device (not dev-board).
I've used pmbootstrap to create and burn an image on a SD card for the device.
I selected pinephone as the vendor and pinephone as the codename.
I tried the following UI options: Phosh, plasma-mobile, hildon.
In all three cases, the phone powers up, and the PostMarketOS Logo Splash comes up, and it is suck there.
In the up left side of the screen, a console login prompts appears.
But, nothing else happens.
Can someone help me to figure out what I am doing wrong?
I'm unable to get the fan to work on the RP64 v2.1 in the NAS case with the fan from Pine64 store. Not sure what I'm missing?
The fan is working when supplied with 12V directly. The fan does not work when plugged into the Fan port on the board.
/sys/class/hwmon/hwmon0/pwm1 exists, echoing any value from 0-255 does not have any affect. I read ATS source code to see if maybe I'm missing something. It doesn't appear so.
Also tried vanilla arch linux (the pwm-fan is under /sys/class/hwmon/hwmon1/pwm1 on linux-aarch64 (5.4.6)).
And built latest ayufan linux-mainline for arch linux. No functioning fan there either.
A multimeter at the base of Q2110 shows absolutely nothing no matter what I write to /sys/class/hwmon/hwmon0/pwm1 - my oscilliscope is currently not working so I'm unable to see if there is any PWM present on FAN_CTL_H yet - I suspect nothing.
This build is using a SATA card and two SSDs powered from the RP64's 12V header (the cables supplied with the NAS case). To rule out a power issue, I eliminated the SATA card and power to the SSDs - so only the DC power, FTDI cable, and fan are plugged into the RP64. Fan still inoperable on all images listed above.
I read every thread regarding the fan I could find on this forum - and all of them mention ATS. ATS does not work, obviously, because writing the values to /sys/class/hwmon/hwmon0/pwm1 has no effect. And yes, I'm logged in as root.
I get a CRC error when extrating the android 9 SDK. MD5sum fits the one from the website.
Even gzrecover can't help. Is it really broken or some incompatibility (Debian Buster)?
