Hi All

My PBP stopped powering on recently whenever the SD card was not in it with an OS to boot from. no reaction to power button at all, short press, long press or anything.

I took the back off, re-seated the eMMC card and tried again - no luck. checked all cables, no damage at all.

I tried the reset and recovery buttons - no reaction.

Now, I cannot power it on even with SD card in - both off and on charger.

Have anyone encountered something like this before ?

Thanks in advance.

Connected USB type C to DP device: it works in mirror mode.

Manjaro XFCE only displays one video output: "default"

Hello,

I want to update my installation of u-boot. (I already asked some questions in the Manjaro Forum because its their u-boot update which asks to be dd'ed to a target, but I am left with some open questions.) Where exactly does u-boot reside when using a standard Linux like in this case Manjaro, installed to the eMMC? When I want to update u-boot, do I simply need to write it to the eMMC device or do mmcblkXboot0 and mmcblkXboot1 play any role in the booting process of Linux on the Pinebook? The information in https://wiki.pine64.org/index.php/Pinebook_Pro does not answer my questions and the documentation of u-boot is somewhat inaccessible even for someone who works with Linux for a living.

Yours
Stefan

It would be really simple.  After the preorder, you see that there are, say, 65% 128GB and 35% 64GB orders and assemble two batches.  When first assembling the units, you just put in the appropriate size module.

It would serve as market research.  Let your customers tell you what they want.  There's a good chance it would make this laptop even more popular.

As it is, it's annoying: Instead of +$20 for +64GB it's +$55 and you end up with a spare part you don't need.  The value proposition is less than half as good.

What people want out of the PBP is not necessarily a fixed $200 price point, it's the value for money.

So it appears there's a problem when upgrading from older kernels to something around 5.5 or later.  The symptom is that when you boot the new kernel, the screen is very dim, possibly appearing completely black.
The problem seems to be that with the older kernels, screen brightness was on a 8-bit 0-to-255 scale, and the newer kernels use a 12-bit 0-to-4095 scale.  So the reasonably bright "224" (for example) brightness that you had with the old kernel becomes a rather dim "224" with the new kernel.

It seems that this issue occurs with a few different distributions' kernel packages.  I'm not sure if any distributions have any fixes (maybe a transition script) built into their kernel packages.

My current thinking is that the best approach (for individual users) is to verify that your Fn-F1 and Fn-F2 are working for adjusting your screen brightness before upgrading the kernel.  Then when you boot your new kernel and you can't read the screen you can use them to turn up the backlight.  I neglected to do this.

A hackish approach could be to poke at the files in /sys/class/backlight/edp-backlight/ (you could do this via SSH if you can't adjust brightness via the keyboard/trackpad/screen)

My PineTime battery connector is broken. Can we connect 5V usb power supply to the connector (where LIPO battery was connected) to safely power PineTime?

I recieved my Pinebook Pro this week and have been looking at getting a new OS on it today. I have a Sandisk SD card that I have formatted as FAT32 on my Mac. Upon insertion into the Pinebook Pro the SD card is not detected.

If I follow the `dmesg` logs there are no obvious messages when inserting the card which leads me to believe it is not being detected at all.

Is it possible I have recieved a unit with a faulty SD slot? What are the best ways to debug this issue?

Many thanks

Hi,

I just booted the Manjaro eMMC installer from SD and flashed my eMMC storage. Everything works as it is supposed to be. I have a running system I can log into.
My first step was to run pacman -Suy. It prints some lines concerning u-boot, which wants me to flash files to my install drive.Is my install drive the eMMC or the block devices called mmcblkboot0 and mmcblkboot1? I have already flashed mmcblkboot0 but I am unsure if this is the right place and decided to ask here before rebooting and having to reflash a bricked device.

Where do I put idbloader.img and i-boot.itb go on the pinebook pro? What is supposed to be on mmcblkboot0 and mmcblkboot1?

Yours
Stefan

Just looking for a little more info on the pinout connecting the LCD driver to the MCU. The schematic showing the J7 connector shows some of the pins but they don't quite line up with the naming of the pins on from the LCD datasheet. I'm hoping to find definitions for each of the lines used for interfacing with the LCD driver. Obviously not the pins from the driver to the LCD..

Any clarification is appreciated. Thanks!

This basically puts the amount of memory used at about 9.5GiB (used + DATA - TOTAL), that's on a system with only ~3.7GiB RAM available!