I found out that the wifi stability improves greatly when you disable power management.

Just add

Hi!

I'd installed Manjaro 20.04 in my PBP; I did all the mirrorlist change stuff, and I shut it down 2 days ago. Today when I was going to boot it, a red light has shown and it is not opening or doing anything else.

When I try to reinstall the Manjaro 20.04 I pressed ES after 15-20 seconds and there is a black window with blank letters that say:
"[5.102225] EXT4-fs error (device mmcblk1p2): ext4_journal_check_start:84etected aborted journal
[5.103046] EXT4-fs (mmcblk1p2): Remounting filesystem read-only"

Today I tried to disable eMMc and installing Manjaro again but the problem persists. I have only been able to mount the Default Debian image from an SD card, but I don't know how to reinstall it to the eMMc or try to boot the eMMc another way... Any ideas?

Thanks very much!

(05-03-2020, 09:47 AM)gimy16 Wrote: Hi!

I'd installed Manjaro 20.04 in my PBP; I did all the mirrorlist change stuff, and I shut it down 2 days ago. Today when I was going to boot it, a red light has shown and it is not opening or doing anything else.

When I try to reinstall the Manjaro 20.04 I pressed ES after 15-20 seconds and there is a black window with blank letters that say:
"[5.102225] EXT4-fs error (device mmcblk1p2): ext4_journal_check_start:84: Detected aborted journal
[5.103046] EXT4-fs (mmcblk1p2): Remounting filesystem read-only"

Today I tried to disable eMMc and installing Manjaro again but the problem persists. I have only been able to mount the Default Debian image from an SD card, but I don't know how to reinstall it to the eMMc or try to boot the eMMc another way... Any ideas?

Thanks very much!

Hello,

Quite looking forward to getting a Clusterboard, although a newer replacement for the aging Sopine module would be great.

As a start, that previously announced SoEdge module seems to support USB3. Will that work though the Clusterboard USB port?

Has anyone already looked into uses of the NPU?

Running Mozilla's DeepSpeech Tensorflow model might work:
https://www.dlology.com/blog/how-to-run-...rk3399pro/
https://github.com/rockchip-linux/rknn-toolkit
https://github.com/val260/DeepSpeech-Keras

Hey All. So I've been attempting to install Manjaro KDE 20.04 through their emmc flasher file which I put on a bootable Micro sd written through the Etcher program.

This is to overwrite a fairly broken XFCE Manjaro build that just wasn't working out (slow window dragging, some parts not working, but could play videos.)

After inserting the flashed sd card, I boot up the Pinebook Pro. The Manjaro splash screen comes up, waited for an hour to realize I needed to hit the esc. key to bring the installation window.

Then it asks which drive to write it to, asking to choose the eMMC drive from 4 options:

Mmcblk2
Mmcblk2boot0
Mmcblk2boot1
Mmcblk1

Also telling me that the currently booted sd card is mmcblk1

So I chose mmcblk2 and then it tells me image does not exist
So I restart, figured why not, Ill try my other option mmcblk1
And it tells me the same thing : image does not exist


What am i doing wrong >_<

Should I try the other 2 options? I feel like this is russian roulette.

So I went down the rabbit hole(for me anyway) of writing a script that turns off the green and amber leds for each node.  Just in case anyone else is thinking about doing this or when I flash a new os and don't back it up, I thought I'd post it here.

I'm not a driver dev or anything so I'm sure there is a better way to do it than this, but a post on here pointed me toward setting RTL8211E registers. I found some documentation and a tool to read/write and was able to use that to write a couple scripts. Phytool requires sudo, so sudo sh lights_off.sh will turn off the leds and lights_on.sh will set them back to the way they work normally.  

I'm using armbian's bionic server , but I don't know why it wouldn't work with  other distros.

lights_off.sh:
#/bin/bash
phytool write eth0/0/31 0x0007
phytool write eth0/0/30 0x2c
phytool write eth0/0/0x1a 0x0000
phytool write eth0/0/0x1c 0x0000
phytool write eth0/0/31 0x0007
phytool write eth0/0/30 0x0000


lights_on.sh:
#!/bin/bash
phytool write eth0/0/31 0x0007
phytool write eth0/0/30 0x2c
phytool write eth0/0/0x1a 0x00d1
phytool write eth0/0/0x1c 0x9770
phytool write eth0/0/31 0x0007
phytool write eth0/0/30 0x0000

In the Pine64 Wiki several devices like the ROCK64 and Pinebook have an entry called Software Images.  This contains pre-built downloadable software and operating systems for the hardware.  PineTime in the Wiki does not have anything like this.

There are several software systems available for the PineTime, like Rust, wasp-os, RIOT, FREERTOS and more.  But there don't seem to be any pre-built flashable images available.  If someone wants to install the Rust system, for example, they have to download software from GitHub, SDKs etc. and build the flashable images themselves.  If someone wants to check out the state of the various available systems for the PineTime they will have to download multiple groups of software and build multiple images.

If there was a Software Images section in the Wiki with the latest flashable images (or links to them) for each different software system for the PineTime, users could easily evaluate each system.  The images would also require documentation on how to flash or load and use the software.

This will require the co-operation of the software developers of course.  It will require extra work from them.  Ideally as each package gets more features added the latest image will be made available.

This might speed up the testing of the PineTime and its software.

I wanted to drag this out of the big thread as it is still an issue. My PinePhone is now my daily driver, but one thing I have noticed is that all kinds of odd things are happening while the screen is off and it is in my pocket. What is odd is I couldn't replicate by leaving a keyboard open in say terminal, or even scrolling in Firefox. But in my pocket a couple of times I have restarted to my wifi password entry full of garbage and the scroll-up first mentioned below is also a problem with

(04-18-2020, 10:33 AM)Boern Wrote: Not sure if this is an upstream issue, but I think this depends on the configuration. When the screen is turned off it will still accept touch input. You can test this by turning the screen off, swiping upwards and then turning the screen back on. You will see the pin entry instead of just the lock screen.

I guess we could save a lot of power by turning the touch input off with the screen.

Dear pinebook community,
i would be really interested in buying a pinebook pro with /e/ pre-installed on it. Is this in the pipeline, or can i put in a request for this hereby?
best,
Rik

My PBP seems to be stuck in suspend mode. The power indicator LED is constantly red when the system is powered on, and the screen does not turn on. The power LED is normal (red) when plugged in, and the battery seems to be holding a charge. I've tried the reset button on the main board. I'm not sure what else to try. Any suggestions? Thanks in advance!