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!

Got an old plastic boy languishing around the shame section of your house? Able to ship it out to Western Canada? Drop me a DM!

Basically want an arm project machine, eventually hope to use it as a computer to toss into my Tabletop rpg bag for running games away from home to replace an ipad that was never very good at this particular task. Thus, the smaller form factor is a boon, even if the upgrade kit never materializes.

The modem company says the modem is certified by Sprint, does that mean it will work? Or will it not work since the PinePhone is probably not registered in Sprint's systems? 

Another question whose answer is very important to me. Do any of the distros support disabling 4G on the PinePhone? I'm asking because I really want to use CDMA2000(Sprint 3G).

Hi,

I've been stuck with this problem for hours now. As far as I can tell the RockPro64 is 4K capable (even if only at @30 refresh).

Manjaro KDE Plasma. Fresh install created using the Manjaro Arm Installer script won't let me select 4K on my monitor. 1080 seems to be the limit.

I've tried every xrandr trick I can think of...

I've tried tweaking u-boot...

Nothing makes any difference. I'm beginning to think this problem is a more complex issue in the kernel HDMI drivers.

The same monitor works fine in 4K with N2 and other ARM devices.

Any help would be very appreciated.

Thanks,

Mkne

Since about mid April I've had issues where there will be no service or recognition that my SIM is plugged in. Then after sitting there for some random amount of time service will appear full, I'll get a text message or a voice mail, then it will disappear again minutes later. Anyone else having this type of thing happen?