Hi,
   I have a rockpro64 v2.1 (2018-07-02) and use Armbian system. 
   In my local test, rockpro64 needs about 36seconds before start kernel. And the 5G device connected with the PCIE slot would be power on at that time.
   The 5G device would obey PBL->SBL->Kernel start progress. And the PCI driver would detect 5G device at 3.5 second after host kernel start even if the 5G device still in PBL stage. This would lead to the true VID/PID of PCIE device are not enumerated because device has difference VID/PID between PBL and Kernel stage.

    For reference, USB interface would be power on during about 10seconds. So could we ajust the power on time slot for PCIE slot to avoid above issue?

Recently bought my pinephone and have been testing various OS options.  I love the hardware switches but didn't want to have to remove the back.  As you can see, my solution also provides access to the SD card.

Trying to install slackwareaarch64 on pinebook pro, following well documented video and web page, I have installed slackwareaarch64 on 3 rockpro64 successfully. This is one of the newer(?) PBP will itty bitty emmc switch.

Installed slackware u-boot, this boots but cannot find slackware installer on sd card in sd card slot.

dmesg shows

Quote:[ 3026.994975] mmc1: Skipping voltage switch
[ 3027.001231] mmc1: error -5 whilst initialising SD card
[ 3027.024964] mmc_host mmc1: Bus speed (slot 0) = 300000Hz (slot req 300000Hz, actual 300000HZ div = 0)
[ 3027.062065] mmc_host mmc1: Bus speed (slot 0) = 200000Hz (slot req 200000Hz, actual 200000HZ div = 0)
[ 3027.101480] mmc_host mmc1: Bus speed (slot 0) = 100000Hz (slot req 100000Hz, actual 100000HZ div = 0)
[ 3027.434979] dwmmc_rockchip fe320000.mmc: Unexpected CMD11 timeout

Hi. My eMMC has been bricked for quite a while - I can't get a keyboard to type in my password.  I'm finally getting around to wanting to boot that way again instead of continuing to use the software on my SD card.  I have found the following directions.  I have installed TowBoot and want to know if that will change anything.  Also, I assume that the OS I download to the SD card has to be prepared by Etcher or something like that, right? 

Here's what I found on the wiki:

1. Boot an operating system from the microSD card. If there is already a bootloader on the eMMC installed see the section Boot order to bypass it.
   
2. Download or copy the desired image to the microSD card as file
   
3. Check if the eMMC appears under
   
   Code:

   lsblk
   . If it doesn't appear in the output of the command, the eMMC wasn't initialized due to applying the above explained bypass method for a too long time during the boot
   
4. Important: Typically the image will be compressed in an archive file to reduce the download size (such as .gz or .xz). Extract the image from its archive file to get the file with the file extension .img.
   
5. Flash the image file using
   
   Code:

   sudo dd if=IMAGE.img of=/dev/mmcblk2 bs=1M status=progress conv=fsync
   (replace IMAGE.img with the filename of the image you want to flash and make sure it has the file extension .img).
   
6. Reboot the PinePhone Pro
   

Will this work with my incoming (not yet shipped, ordered yesterday), PBP?

https://www.amazon.com/gp/product/B07ZVK...UTF8&psc=1

Is it possible to add spi_flash ship to this board then use it to boot to usb? If so how?
if not why?

Has my Pinebook Pro camera broken, or has some update messed with the camera? Running Cheese immediately gives the error shown in the attached screen shot.

Attached Files

Thumbnail(s)
   

Is there any OS that is actually working and stable? I am going down the list installing every OS but there's always a problem to be found, some more than others but none of them work enough to make the device live up to it's name - the Pine "Phone".

If anyone has had any luck with an OS please let me know. I have installed more than half the available OS's and am on the precipice of giving up.

Thanks.

Hello, what are the main differences between megi's and sunxi64 kernels, what are the functionalities advantages, privacy and security trade-offs between them?
I've been using arch with megi's kernel and would like to know more about the possible privacy and security problems regarding the wifi firmware as described here: https://linmob.net/how-about-more-libre-...ath9k-htc/

My screen bottom side has loosed its tactile function (I don't know if it's a hardware screen issue or just a bad connection of the screen). But, meanwhile, I have a problem to start my mobile because the OK button, when decrypting the device at the starting process (my device is encrypted) is very hard to touch (I should try dozens of times). I wonder if I can set:

an inversion of top/bottom sides, at mobile start, or always (when I'm in the graphical screes, auto rotate help me, there is not a major issue)

"Cancel" the bottom last centimeter of the screen.

Are there any settings file where I can modify these parameters?