Welcome, Guest |
You have to register before you can post on our site.
|
Latest Threads |
Bare metal on Pinephone P...
Forum: PinePhone Pro Software
Last Post: alain
Yesterday, 07:58 AM
» Replies: 0
» Views: 54
|
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: 495
|
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: 164
|
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
|
|
|
upgrade problem |
Posted by: trying4firstbass - 11-27-2022, 09:05 PM - Forum: Linux on Pinebook Pro
- Replies (1)
|
 |
Hi, arch/pacman/mankaro noob. When I try to upgrade dostro, software versus pacman, software update center on lower right scroll bar I am always asked to pick betwern two themes. Regardless of which I choose all stops with a pop-up window giving a conflict dependencies between pasma5 themes breTh and breath2? How to fix please? Thank you.
|
|
|
LTE works, GSM does not |
Posted by: NaN INF NaN - 11-27-2022, 06:16 PM - Forum: PostmarketOS on PinePhone
- Replies (4)
|
 |
I'm enjoying SXMO on my new PinePhone (PPHONE-BE2). For the most part, it is working well. When I have LTE reception, calls and data work without problems. However, LTE coverage is still patchy in Germany, UMTS is disabled and 5G is unsupported on PinePhone. So whenever LTE is unavailable, the phone should use GSM and that is not working at all. I have never seen the phone registering successfully in the GSM network of my carrier. Same with the preinstalled Plasma Mobile (in Manjaro ARM I think).
Here is some data that may help with diagnosis.
* Carrier: Congstar (Germany, a brand of Telekom).
* The SIM is old (from around 2008) but GSM works in another phone.
* I flashed an open source firmware onto the modem but had the same problem before doing so.
* Below is the output of mmcli -m 0 and mmcli -m 0 --3gpp-scan --timeout 300 in a spot where I do not have LTE coverage.
* Note that 3gpp-scan finds the GSM network of O2 but not the one of my carrier.
* It also finds the LTE network of my carrier (26201 - TDG) but I think reception is too bad to connect.
Any thoughts on how to fix this? I consider ordering a new SIM. I may also switch to a different carrier, so recommendations for German carriers that work well with PinePhone would be appreciated.
Code: -----------------------------------
General | path: /org/freedesktop/ModemManager1/Modem/0
| device id: 9717313523c02e0afbec903cac5df14f8bd7e778
-----------------------------------
Hardware | manufacturer: QUALCOMM INCORPORATED
| model: QUECTEL Mobile Broadband Module
| firmware revision: EG25GGBR07A08M2G
| carrier config: Commercial-DT
| carrier config revision: 05011F1C
| h/w revision: 10000
| supported: gsm-umts, lte
| current: gsm-umts, lte
| equipment id: 860195053807878
-----------------------------------
System | device: /sys/devices/platform/soc/1c1b000.usb/usb2/2-1
| drivers: qmi_wwan, option
| plugin: quectel
| primary port: cdc-wdm0
| ports: cdc-wdm0 (qmi), ttyUSB0 (qcdm), ttyUSB1 (gps),
| ttyUSB2 (at), wwan0 (net)
-----------------------------------
Numbers | own: 49<redacted>
-----------------------------------
Status | lock: sim-pin2
| unlock retries: sim-pin (3), sim-puk (10), sim-pin2 (3), sim-puk2 (10)
| state: enabled
| power state: on
| signal quality: 42% (cached)
-----------------------------------
Modes | supported: allowed: 2g; preferred: none
| allowed: 3g; preferred: none
| allowed: 4g; preferred: none
| allowed: 2g, 3g; preferred: 3g
| allowed: 2g, 3g; preferred: 2g
| allowed: 2g, 4g; preferred: 4g
| allowed: 2g, 4g; preferred: 2g
| allowed: 3g, 4g; preferred: 4g
| allowed: 3g, 4g; preferred: 3g
| allowed: 2g, 3g, 4g; preferred: 4g
| allowed: 2g, 3g, 4g; preferred: 3g
| allowed: 2g, 3g, 4g; preferred: 2g
| current: allowed: 2g, 4g; preferred: 4g
-----------------------------------
Bands | supported: egsm, dcs, pcs, g850, utran-1, utran-4, utran-6, utran-5,
| utran-8, utran-2, eutran-1, eutran-2, eutran-3, eutran-4, eutran-5,
| eutran-7, eutran-8, eutran-12, eutran-13, eutran-18, eutran-19,
| eutran-20, eutran-25, eutran-26, eutran-28, eutran-38, eutran-39,
| eutran-40, eutran-41, utran-19
| current: egsm, dcs, pcs, g850, utran-1, utran-4, utran-6, utran-5,
| utran-8, utran-2, eutran-1, eutran-2, eutran-3, eutran-4, eutran-5,
| eutran-7, eutran-8, eutran-12, eutran-13, eutran-18, eutran-19,
| eutran-20, eutran-25, eutran-26, eutran-28, eutran-38, eutran-39,
| eutran-40, eutran-41, utran-19
-----------------------------------
IP | supported: ipv4, ipv6, ipv4v6
-----------------------------------
3GPP | imei: 860195053807878
| enabled locks: sim, fixed-dialing
| operator id: 26203
| registration: idle
-----------------------------------
3GPP EPS | ue mode of operation: csps-1
| initial bearer ip type: ipv4v6
-----------------------------------
SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0
| sim slot paths: slot 1: /org/freedesktop/ModemManager1/SIM/0 (active)
| slot 2: none
Code: ---------------------
3GPP scan | networks: 26203 - o2 - de (gsm, current)
| 26203 - o2 - de (lte, forbidden)
| 26202 - Vodafone (lte, forbidden)
| 26201 - TDG (lte, available)
|
|
|
Receive MMS fails after Nov 27 upgrade |
Posted by: treebeard - 11-27-2022, 11:25 AM - Forum: Mobian on PinePhone
- Replies (17)
|
 |
Did a dist-upgrade this morning and now when I receive a MMS message mmsd-tng goes into a cycle of messages like:
Code: 2022-11-27T09:53:15.831163-06:00 pine systemd[814]: Stopped Multimedia Messaging Service Daemon.
2022-11-27T09:53:15.842527-06:00 pine systemd[814]: Started Multimedia Messaging Service Daemon.
2022-11-27T09:53:15.905939-06:00 pine mmsdtng[2302]: /usr/bin/mmsdtng: symbol lookup error: /usr/bin/mmsdtng: undefined symbol: _ZN4i18n12phonenumbers11PhoneNumberC1EPN6google8protobuf5ArenaE
2022-11-27T09:53:15.913163-06:00 pine systemd[814]: mmsd-tng.service: Main process exited, code=exited, status=127/n/a
2022-11-27T09:53:15.915227-06:00 pine systemd[814]: mmsd-tng.service: Failed with result 'exit-code'.
2022-11-27T09:53:26.077399-06:00 pine systemd[814]: mmsd-tng.service: Scheduled restart job, restart counter is at 50.
2022-11-27T09:53:26.079754-06:00 pine systemd[814]: Stopped Multimedia Messaging Service Daemon.
2022-11-27T09:53:26.088589-06:00 pine systemd[814]: Started Multimedia Messaging Service Daemon.
I anyone else seeing this? libphonenumber 8.12.57+ds-3 arrived in bookworm today but I haven't yet started reverting libraries to isolate the problem.
|
|
|
Interested in a Pinephone, but have some questions |
Posted by: jilek - 11-27-2022, 11:01 AM - Forum: General Discussion of PinePhone Pro
- Replies (8)
|
 |
Hello! I have an interest in the Pinephone Pro but I'm still curious about a few things.
- Is the battery life really so bad that it can't last a whole day? There's no battery upgrade that allows it to last?
- I imagine some may frown on the idea, but what is the possibility I can get Android 10 on it? I would idealistically like to use Android 10 as my daily driver, while...
- How can I multi-boot the phone? I wish to be able to test out Linux phones and possibly learn to develop on that platform. Idealistically I'd love to have a phone with easy repairability, battery/SD card replacement, a battery that lasts ~a full day, runs Android 10 until Linux phones are comprable, and to test/mess with Linux OS's. My Pixel 3a is very good but I can't upgrade storage, film plus and I don't know how to repair it bee tv.
|
|
|
Locked Database-->Bricked Device |
Posted by: _radv_ - 11-27-2022, 06:45 AM - Forum: Manjaro on PinePhone
- Replies (8)
|
 |
I've been using "Linux version 5.11.3-1-MANJARO-ARM" that came preinstalled on the Pine Phone I got a few weeks ago.
Almost every time I tried to install new software using the "Discover" ap I was getting an error about the package manager failing to update because there was a locked database. I tried updating using pcman and got the same message about a locked database. Searching the internet suggested I delete this file: /var/lib/pacman/db.lck which I did.
I ran pacman -Syu. It started working. There were many notes about keys, but it eventually started updating things. As that was finishing the terminal disappeared and I got a gigantic message that filled up the entire screen. Unfortunately, because the phone was stuck in portrait mode (hadn't an option to change it to landscape except for the first few days I used the device) I could only read some words in the middle. It said something about lock and unlock and a virtual machine. I got rid of the message by powering down the phone.
Now, when I turn on the phone, it's stuck at the loading screen (the K with the gear) and nothing else happens. I'll be glad to hear anyone's thoughts. I wonder what happened.
I imagine the primary solution is booting some os from the SD card. It was something I was going to do today or tomorrow anyway. I hope that works. I am having some separate problems with the SD card reader.
|
|
|
Will there be more paying options for Pine64EU? |
Posted by: bosi564 - 11-27-2022, 06:18 AM - Forum: General
- Replies (4)
|
 |
The main question is in the title. The story is as follows:
I decided to try the european store and buy a replacement for my PineTime (mine is non-usable, basically e-waste), but I found that the pay must go through a company which I'm unfamiliar with and asks directly for credit/debit card info to transfer money from.
I'm not a fan of PayPal, but there's an additional step of approval at least. And I wasn't interested in trying if everything will work correctly with this new company.
I've donated the money to some open source projects. Well, in the end the money did end up being used to support something, so it's not all bad. But I would like it if more options to pay were added in the future, where the transfer of money doesn't happen automatically without my knowledge and approval on every transfer.
|
|
|
Firefox causes my pinebook to completely freeze[how to troubleshoot] |
Posted by: jcarty - 11-25-2022, 04:08 PM - Forum: General Discussion on Pinebook Pro
- Replies (4)
|
 |
When using firefox if I open some tabs my browser will cause my pinebookpro to freeze and stop responding. The mouse still works but nothing else responds and the only solution is to hold the power button and turn it off.
So far I've tried reinstalling Firefox with sudo pacman -S Firefox. I've found disabling all the plugins doesn't stop it freezing either.
Is there anything I can use or do to find the cause of the freezing?
|
|
|
Debian (Vanilla) no output on display after Kernel update (6.0.8-1) |
Posted by: as365n4 - 11-25-2022, 08:28 AM - Forum: Linux on Pinebook Pro
- Replies (1)
|
 |
Recently I updated my Pinebook Pro and apt installed the new Kernel package "linux-image-6.0.0-4-arm64 (6.0.8-1)", after everything was finished I did a poweroff/poweron cycle.
And since then I only get to see the output from u-boot on my display and as soon as the kernel gets started the display goes blank.
I can access the machine via serial/uart cable and recorded the output down below.
I assume that the framebuffer does not get initialised and therefore no display output, but how can I fix this, anybody else had this issue?
Code: U-Boot TPL 2022.04+dfsg-2+b1 (May 14 2022 - 19:14:13)
Channel 0: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=16/15 CS=1 Die BW=16 Size=2048MB
Channel 1: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=16/15 CS=1 Die BW=16 Size=2048MB
256B stride
lpddr4_set_rate: change freq to 400000000 mhz 0, 1
lpddr4_set_rate: change freq to 800000000 mhz 1, 0
Trying to boot from BOOTROM
Returning to boot ROM...
U-Boot SPL 2022.04+dfsg-2+b1 (May 14 2022 - 19:14:13 +0000)
Trying to boot from MMC1
U-Boot 2022.04+dfsg-2+b1 (May 14 2022 - 19:14:13 +0000)
SoC: Rockchip rk3399
Reset cause: POR
Model: Pine64 Pinebook Pro
DRAM: 3.9 GiB
PMIC: RK808
Core: 309 devices, 31 uclasses, devicetree: separate
MMC: mmc@fe310000: 3, mmc@fe320000: 1, mmc@fe330000: 0
Loading Environment from SPIFlash... SF: Detected gd25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
*** Warning - bad CRC, using default environment
In: serial
Out: vidconsole
Err: vidconsole
Model: Pine64 Pinebook Pro
Net: No ethernet found.
starting USB...
Bus usb@fe380000: USB EHCI 1.00
Bus usb@fe3a0000: USB OHCI 1.0
Bus usb@fe3c0000: USB EHCI 1.00
Bus usb@fe3e0000: USB OHCI 1.0
Bus usb@fe800000: Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
Bus usb@fe900000: Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus usb@fe380000 for devices... 1 USB Device(s) found
scanning bus usb@fe3a0000 for devices... 2 USB Device(s) found
scanning bus usb@fe3c0000 for devices... 3 USB Device(s) found
scanning bus usb@fe3e0000 for devices... 1 USB Device(s) found
scanning bus usb@fe800000 for devices... 1 USB Device(s) found
scanning bus usb@fe900000 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot: 3 2 1 0
Card did not respond to voltage select! : -110
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
U-Boot menu
1: Debian GNU/Linux bookworm/sid 6.0.0-4-arm64
2: Debian GNU/Linux bookworm/sid 6.0.0-4-arm64 (rescue target)
3: Debian GNU/Linux bookworm/sid 6.0.0-3-arm64
4: Debian GNU/Linux bookworm/sid 6.0.0-3-arm64 (rescue target)
Enter choice: 1: Debian GNU/Linux bookworm/sid 6.0.0-4-arm64
Retrieving file: /initrd.img-6.0.0-4-arm64
Retrieving file: /vmlinuz-6.0.0-4-arm64
append: root=UUID=98573609-750d-4b44-8355-cc8315fdb62f ro quiet
Moving Image from 0x2080000 to 0x2200000, end=4060000
## Flattened Device Tree blob at f4f1d110
Booting using the fdt blob at 0xf4f1d110
Loading Ramdisk to f2354000, end f4f15b91 ... OK
Loading Device Tree to 00000000f233f000, end 00000000f2353c87 ... OK
Starting kernel ...
[ 5.053557] fan53555-regulator 0-0040: Failed to register regulator!
[ 5.058101] fan53555-regulator 0-0041: Failed to register regulator!
[ 5.107945] rockchip-dp ff970000.edp: no DP phy configured
[ 5.115049] fan53555-regulator 0-0040: Failed to register regulator!
[ 5.116972] fan53555-regulator 0-0041: Failed to register regulator!
[ 5.129613] fan53555-regulator 0-0040: Failed to register regulator!
[ 5.131858] fan53555-regulator 0-0041: Failed to register regulator!
[ 5.165792] fan53555-regulator 0-0040: Failed to register regulator!
[ 5.167563] fan53555-regulator 0-0041: Failed to register regulator!
[ 5.181698] fan53555-regulator 0-0040: Failed to register regulator!
[ 5.185496] fan53555-regulator 0-0041: Failed to register regulator!
[ 5.222147] OF: graph: no port node found in /i2c@ff3d0000/fusb30x@22
[ 5.327333] cdn-dp fec00000.dp: [drm:cdn_dp_probe [rockchipdrm]] *ERROR* missing extcon or phy
root has been mounted 1 times without being checked, check forced.
root: |========================================================| 100.0%
root: 110874/7356416 files (0.4% non-contiguous), 2158303/29405184 blocks
fsckd-cancel-msg:Press Ctrl+C to cancel all filesystem checks in progress
Mounting Arbitrary Executable File Formats File System...
[ OK ] Mounted Arbitrary Executable File Formats File System.
[ OK ] Finished Set Up Additional Binary Formats.
[ OK ] Finished Create Volatile Files and Directories.
Starting Network Time Synchronization...
Starting Record System Boot/Shutdown in UTMP...
[ OK ] Finished Record System Boot/Shutdown in UTMP.
[ OK ] Finished Load AppArmor profiles.
Starting Raise network interfaces...
[ OK ] Started Network Time Synchronization.
[ OK ] Reached target System Initialization.
[ OK ] Started Daily Cleanup of Temporary Directories.
[ OK ] Reached target System Time Set.
[ OK ] Started Daily apt download activities.
[ OK ] Started Daily apt upgrade and clean activities.
[ OK ] Started Daily dpkg database backup timer.
[ OK ] Started Periodic ext4 Onli…ata Check for All Filesystems.
[ OK ] Started Discard unused blocks once a week.
[ OK ] Started Daily rotation of log files.
[ OK ] Started Daily man-db regeneration.
[ OK ] Reached target Timer Units.
[ OK ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
[ OK ] Listening on D-Bus System Message Bus Socket.
[ OK ] Reached target Socket Units.
[ OK ] Reached target Basic System.
Starting Avahi mDNS/DNS-SD Stack...
[ OK ] Started Regular background program processing daemon.
Starting D-Bus System Message Bus...
Starting Remove Stale Onli…t4 Metadata Check Snapshots...
Starting Initialize hardware monitoring sensors...
Starting Authorization Manager...
Starting System Logging Service...
Starting User Login Management...
Starting Disk Manager...
[ OK ] Finished Raise network interfaces.
[ OK ] Finished Initialize hardware monitoring sensors.
[ OK ] Started System Logging Service.
[ OK ] Started D-Bus System Message Bus.
[ OK ] Finished Remove Stale Onli…ext4 Metadata Check Snapshots.
Starting Network Manager...
Starting WPA supplicant...
[ OK ] Started User Login Management.
[ OK ] Started Avahi mDNS/DNS-SD Stack.
[ OK ] Started Authorization Manager.
Starting Modem Manager...
[ OK ] Started WPA supplicant.
[ OK ] Started Disk Manager.
[ OK ] Started Network Manager.
[ OK ] Reached target Network.
Starting OpenBSD Secure Shell server...
Starting Permit User Sessions...
[ OK ] Finished Permit User Sessions.
Starting Hold until boot process finishes up...
Starting Terminate Plymouth Boot Screen...
Starting Hostname Service...
Debian GNU/Linux bookworm/sid PinebookPRO ttyS2
PinebookPRO login:
Password:
Linux PinebookPRO 6.0.0-4-arm64 #1 SMP Debian 6.0.8-1 (2022-11-11) aarch64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Fri Nov 25 13:23:26 GMT 2022 on ttyS2
Code: root@PinebookPRO:~$ dmesg | grep rockchip
[ 0.194070] rockchip-gpio ff720000.gpio0: probed /pinctrl/gpio0@ff720000
[ 0.194806] rockchip-gpio ff730000.gpio1: probed /pinctrl/gpio1@ff730000
[ 0.195616] rockchip-gpio ff780000.gpio2: probed /pinctrl/gpio2@ff780000
[ 0.196306] rockchip-gpio ff788000.gpio3: probed /pinctrl/gpio3@ff788000
[ 0.196960] rockchip-gpio ff790000.gpio4: probed /pinctrl/gpio4@ff790000
[ 4.567584] dwmmc_rockchip fe310000.mmc: IDMAC supports 32-bit address mode.
[ 4.567635] dwmmc_rockchip fe310000.mmc: Using internal DMA controller.
[ 4.567655] dwmmc_rockchip fe310000.mmc: Version ID is 270a
[ 4.567754] dwmmc_rockchip fe310000.mmc: DW MMC controller at irq 41,32 bit host data width,256 deep fifo
[ 4.659559] dwmmc_rockchip fe310000.mmc: IDMAC supports 32-bit address mode.
[ 4.659626] dwmmc_rockchip fe310000.mmc: Using internal DMA controller.
[ 4.659646] dwmmc_rockchip fe310000.mmc: Version ID is 270a
[ 4.659742] dwmmc_rockchip fe310000.mmc: DW MMC controller at irq 41,32 bit host data width,256 deep fifo
[ 4.677851] dwmmc_rockchip fe310000.mmc: IDMAC supports 32-bit address mode.
[ 4.677910] dwmmc_rockchip fe310000.mmc: Using internal DMA controller.
[ 4.677930] dwmmc_rockchip fe310000.mmc: Version ID is 270a
[ 4.677989] dwmmc_rockchip fe310000.mmc: DW MMC controller at irq 41,32 bit host data width,256 deep fifo
[ 4.706992] dwmmc_rockchip fe310000.mmc: IDMAC supports 32-bit address mode.
[ 4.707056] dwmmc_rockchip fe310000.mmc: Using internal DMA controller.
[ 4.707077] dwmmc_rockchip fe310000.mmc: Version ID is 270a
[ 4.707135] dwmmc_rockchip fe310000.mmc: DW MMC controller at irq 41,32 bit host data width,256 deep fifo
[ 4.772737] dwmmc_rockchip fe310000.mmc: IDMAC supports 32-bit address mode.
[ 4.772853] dwmmc_rockchip fe310000.mmc: Using internal DMA controller.
[ 4.772874] dwmmc_rockchip fe310000.mmc: Version ID is 270a
[ 4.772938] dwmmc_rockchip fe310000.mmc: DW MMC controller at irq 41,32 bit host data width,256 deep fifo
[ 4.807955] dwmmc_rockchip fe310000.mmc: IDMAC supports 32-bit address mode.
[ 4.808015] dwmmc_rockchip fe310000.mmc: Using internal DMA controller.
[ 4.808035] dwmmc_rockchip fe310000.mmc: Version ID is 270a
[ 4.808130] dwmmc_rockchip fe310000.mmc: DW MMC controller at irq 41,32 bit host data width,256 deep fifo
[ 4.981168] rockchip-vop ff8f0000.vop: Adding to iommu group 2
[ 4.984065] dwmmc_rockchip fe310000.mmc: IDMAC supports 32-bit address mode.
[ 4.984065] dwmmc_rockchip fe320000.mmc: IDMAC supports 32-bit address mode.
[ 4.984119] dwmmc_rockchip fe310000.mmc: Using internal DMA controller.
[ 4.984141] dwmmc_rockchip fe310000.mmc: Version ID is 270a
[ 4.984149] dwmmc_rockchip fe320000.mmc: Using internal DMA controller.
[ 4.984169] dwmmc_rockchip fe320000.mmc: Version ID is 270a
[ 4.984202] dwmmc_rockchip fe310000.mmc: DW MMC controller at irq 41,32 bit host data width,256 deep fifo
[ 4.984234] dwmmc_rockchip fe320000.mmc: DW MMC controller at irq 64,32 bit host data width,256 deep fifo
[ 4.986754] rockchip-vop ff900000.vop: Adding to iommu group 3
[ 5.029224] dwmmc_rockchip fe310000.mmc: IDMAC supports 32-bit address mode.
[ 5.029275] dwmmc_rockchip fe310000.mmc: Using internal DMA controller.
[ 5.029294] dwmmc_rockchip fe310000.mmc: Version ID is 270a
[ 5.029339] dwmmc_rockchip fe310000.mmc: DW MMC controller at irq 41,32 bit host data width,256 deep fifo
[ 5.029605] dwmmc_rockchip fe310000.mmc: allocated mmc-pwrseq
[ 5.043728] dwmmc_rockchip fe320000.mmc: IDMAC supports 32-bit address mode.
[ 5.043792] dwmmc_rockchip fe320000.mmc: Using internal DMA controller.
[ 5.043811] dwmmc_rockchip fe320000.mmc: Version ID is 270a
[ 5.043875] dwmmc_rockchip fe320000.mmc: DW MMC controller at irq 64,32 bit host data width,256 deep fifo
[ 5.107945] rockchip-dp ff970000.edp: no DP phy configured
[ 5.120565] dwmmc_rockchip fe320000.mmc: IDMAC supports 32-bit address mode.
[ 5.120610] dwmmc_rockchip fe320000.mmc: Using internal DMA controller.
[ 5.120627] dwmmc_rockchip fe320000.mmc: Version ID is 270a
[ 5.120666] dwmmc_rockchip fe320000.mmc: DW MMC controller at irq 64,32 bit host data width,256 deep fifo
[ 5.138075] dwmmc_rockchip fe320000.mmc: IDMAC supports 32-bit address mode.
[ 5.138140] dwmmc_rockchip fe320000.mmc: Using internal DMA controller.
[ 5.138159] dwmmc_rockchip fe320000.mmc: Version ID is 270a
[ 5.138222] dwmmc_rockchip fe320000.mmc: DW MMC controller at irq 64,32 bit host data width,256 deep fifo
[ 5.174804] dwmmc_rockchip fe320000.mmc: IDMAC supports 32-bit address mode.
[ 5.174875] dwmmc_rockchip fe320000.mmc: Using internal DMA controller.
[ 5.174895] dwmmc_rockchip fe320000.mmc: Version ID is 270a
[ 5.174956] dwmmc_rockchip fe320000.mmc: DW MMC controller at irq 64,32 bit host data width,256 deep fifo
[ 5.222306] dwmmc_rockchip fe320000.mmc: IDMAC supports 32-bit address mode.
[ 5.222835] dwmmc_rockchip fe320000.mmc: Using internal DMA controller.
[ 5.222855] dwmmc_rockchip fe320000.mmc: Version ID is 270a
[ 5.222914] dwmmc_rockchip fe320000.mmc: DW MMC controller at irq 64,32 bit host data width,256 deep fifo
[ 5.223786] dwmmc_rockchip fe320000.mmc: Got CD GPIO
[ 5.239661] rockchip-pcie f8000000.pcie: host bridge /pcie@f8000000 ranges:
[ 5.239731] rockchip-pcie f8000000.pcie: MEM 0x00fa000000..0x00fbdfffff -> 0x00fa000000
[ 5.239762] rockchip-pcie f8000000.pcie: IO 0x00fbe00000..0x00fbefffff -> 0x00fbe00000
[ 5.240744] rockchip-pcie f8000000.pcie: no vpcie12v regulator found
[ 5.297331] rockchip-pcie f8000000.pcie: PCI host bridge to bus 0000:00
[ 5.327333] cdn-dp fec00000.dp: [drm:cdn_dp_probe [rockchipdrm]] *ERROR* missing extcon or phy
[ 5.680893] dwmmc_rockchip fe310000.mmc: Successfully tuned phase to 59
[ 17.689230] rockchip-rga ff680000.rga: HW Version: 0x03.02
[ 17.697334] rockchip-rga ff680000.rga: Registered rockchip-rga as /dev/video0
[ 17.765710] rockchip_vdec: module is from the staging directory, the quality is unknown, you have been warned.
[ 17.794370] hantro-vpu ff650000.video-codec: registered rockchip,rk3399-vpu-enc as /dev/video4
[ 17.795122] hantro-vpu ff650000.video-codec: registered rockchip,rk3399-vpu-dec as /dev/video5
[ 17.934074] input: rockchip,es8316-codec Headphones as /devices/platform/es8316-sound/sound/card0/input14
Code: root@PinebookPRO:~$ dmesg | grep display
root@PinebookPRO:~$ dmesg | grep video
[ 17.054974] videodev: Linux video capture interface: v2.00
[ 17.307568] rockchip-rga ff680000.rga: Registered rockchip-rga as /dev/video0
[ 17.343718] rkvdec ff660000.video-codec: Adding to iommu group 1
[ 17.353191] hantro-vpu ff650000.video-codec: Adding to iommu group 0
[ 17.384980] hantro-vpu ff650000.video-codec: registered rockchip,rk3399-vpu-enc as /dev/video2
[ 17.411838] hantro-vpu ff650000.video-codec: registered rockchip,rk3399-vpu-dec as /dev/video4
[ 17.473599] usbcore: registered new interface driver uvcvideo
|
|
|
no sdcard boot and manjaro update failed |
Posted by: Gwen - 11-25-2022, 04:33 AM - Forum: General Discussion on PinePhone
- Replies (3)
|
 |
Hi there,
I received my pinephone few days ago and tried to update it (from UI, not ssh). ... It failed ...
Now I get the same big 'K' at start and nothing happens.
I'm not able to boot from sdcard. I tried two differents sdcards with manjaro image and jumpstart but pinephone doesn't boot anything else than the emmc.
I tried long press action on start button or other things seen on youtube or documentation but can't go further ...
I've understood there could be problems with full discharging battery also but I don't know if it's the case ... I don't think so but I'm not sure ...
Could some give some help please ?
|
|
|
|