Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 29,478
» Latest member: max1987martin
» Forum threads: 16,197
» Forum posts: 116,882

Full Statistics

Latest Threads
Bare metal on Pinephone P...
Forum: PinePhone Pro Software
Last Post: alain
Yesterday, 07:58 AM
» Replies: 0
» Views: 55
Seeking Contributors: Apa...
Forum: PinePhone Pro Software
Last Post: geometrylitegame12
Yesterday, 01:38 AM
» Replies: 4
» Views: 3,989
Pinephone Pro wont boot t...
Forum: General Discussion of PinePhone Pro
Last Post: KC9UDX
08-18-2025, 06:15 PM
» Replies: 5
» Views: 266
PinePhone Pro discontinue...
Forum: General Discussion of PinePhone Pro
Last Post: Kevin Kofler
08-18-2025, 04:30 PM
» Replies: 8
» Views: 497
fixing the ppkb mainboard...
Forum: PinePhone Pro Accessories
Last Post: Jite
08-18-2025, 02:57 PM
» Replies: 2
» Views: 126
Are there plannes to crea...
Forum: PinePhone Pro Hardware
Last Post: biketool
08-18-2025, 04:12 AM
» Replies: 5
» Views: 993
prototyping to help someo...
Forum: General
Last Post: Samliams
08-18-2025, 02:22 AM
» Replies: 1
» Views: 165
Pinephone pro stuck while...
Forum: PinePhone Pro Hardware
Last Post: Supervisor
08-16-2025, 06:40 PM
» Replies: 2
» Views: 177
Compatible U.S. carriers ...
Forum: General Discussion on PinePhone
Last Post: Zebulon Walton
08-15-2025, 07:34 PM
» Replies: 2
» Views: 217
Long dialpad keypress to ...
Forum: Mobian on PinePhone
Last Post: Zebulon Walton
08-15-2025, 06:48 PM
» Replies: 3
» Views: 157

 
  dwmmc_rockchip fe320000.mmc: Unexpected CMD11 timeout
Posted by: gsplitz - 11-29-2022, 06:47 PM - Forum: Linux on Pinebook Pro - No Replies

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

this is same output from dmesg booting manjaro and inserting same sd card in sd card slot

this is a new 
SanDisk Ultra 32GB UHS-I/Class 10 Micro SDHC Memory Card and I've tried 64GB also.

Using the same sd card with slackware installer in a usb sd card reader, the slackware installer will load the system.


  How reflash my eMMC?
Posted by: IHaveALinuxPhone - 11-29-2022, 02:51 PM - Forum: General Discussion of PinePhone Pro - Replies (2)

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

Sorry the commands pasted funny.  Thanks in advance.


  Displayport? USB-C Alternative Modes? Anker 7-in-1
Posted by: xgpt - 11-29-2022, 12:32 PM - Forum: Pinebook Pro Hardware and Accessories - Replies (3)

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

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


  rock64 v3 spiflash
Posted by: Macgyver - 11-28-2022, 02:18 PM - Forum: General Discussion on ROCK64 - No Replies

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


Question Broken Camera ?
Posted by: angeloweb - 11-28-2022, 12:29 PM - Forum: Pinebook Pro Hardware and Accessories - Replies (2)

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)
   

  Most stable Pinephone OS
Posted by: karcdaeh - 11-28-2022, 11:50 AM - Forum: General Discussion on PinePhone - Replies (20)

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.


  Differences bwteeen megi's kernel e sunxi64
Posted by: user641 - 11-28-2022, 07:48 AM - Forum: General Discussion on PinePhone - Replies (2)

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
Posted by: arbocenc - 11-28-2022, 07:07 AM - Forum: General Discussion on PinePhone - Replies (1)

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?


  No sound after Mobian upgrade
Posted by: arbocenc - 11-28-2022, 06:49 AM - Forum: General Discussion on PinePhone - Replies (1)

At Settings > Sound I have NO output or input device so I suppose my device sound is not available...


  Ox64 documentation mismatches
Posted by: ukoda - 11-28-2022, 02:43 AM - Forum: General - Replies (1)

Hi guys,
  I am developing a board to use the Ox64 for a commercial application and while mapping out the planned pin usage and creating a KiCAD part I found a mismatch between the four documents I was referencing:

  • PINE64_Ox64-Schematic-202221007.pdf from the wiki.
  • PINE64_Ox64_placement-Bottom-202221007.pdf from the wiki.
  • BL808_DS_en_1.1(open).pdf from the wiki.
  • Ox64 Pin Assignments spreadsheet, probably from the original announcement blog.
The last one can probably be ignored as nothing on it matches anything else but if anyone see it posted anywhere they should probably have it pulled down to avoid confusion.

I have found five issues so far:
  1. Pin 4 on the schematic is labelled as GPIO12 but on the bottom placement is labelled as GP21.
  2. Pin 5 on the schematic is labelled as GPIO13 but on the bottom placement is labelled as GP31.
  3. Pin 6 on the schematic is labelled as GPIO41 but on the bottom placement is labelled as GP14.  There is no GPIO41 pin on the BL808C datasheet.
  4. Pin 7 on the schematic is labelled as GPIO40 but on the bottom placement is labelled as GP4.  There is no GPIO40 pin on the BL808C datasheet.
  5. Pin 12 on the schematic is labelled as GPIO20 but on the bottom placement is labelled as GP2.

I am guessing that:
  1. Pin 4 is actually GPIO12.
  2. Pin 5 is actually GPIO13.
  3. Pin 6 is possibly GPIO5.  Low confidence in this guess.
  4. Pin 7 is possibly GPIO4.  Low confidence in this guess.
  5. Pin 12 is actually GPIO20.

Couldn't find anywhere official to report these issues to so posting here in the hope the right people see this and can update the files on the wiki.