Welcome, Guest |
You have to register before you can post on our site.
|
Forum Statistics |
» Members: 29,467
» Latest member: wsmhjqq123
» Forum threads: 16,192
» Forum posts: 116,860
Full Statistics
|
|
|
How is it going Pine64.org? |
Posted by: Corfromleuven - 11-09-2023, 04:57 AM - Forum: General
- Replies (2)
|
 |
Dear all, I try to regularly check the pine64.org blog page for community updates. Since the ironic august post about you guys keeping us waiting there seems to be no new community updates posted at all. Also the forum pages seem way out of date. What is happening? Is Pine64.org still alive?
|
|
|
PPP now used as main device. |
Posted by: DaForest - 11-08-2023, 11:09 AM - Forum: General Discussion of PinePhone Pro
- Replies (3)
|
 |
Good day folks,
I now use my PPP as a daily device. This replaces my Blackberry Classic as a main device.
The only true requirement is the wired headset which is something most of us do regardless.
Arch Linux Phosh 2023-09-25 version.
To fix the dark theme issue I installed xdg-desktop-portal-gnome
sudo pacman -S xdg-desktop-portal-gnome
|
|
|
Can't boot from eMMc with Armbian 23.8 Bookworm |
Posted by: francoispawlus - 11-07-2023, 02:50 AM - Forum: Linux on PINE A64-LTS / SOPINE
- Replies (1)
|
 |
Hello team!
I try to evaluate the platform based on:
- Sopine Baseboard model A
- Sopine A64 compute module
- Armbian 23.8 Bookworm
There is no issue with SDCard boot.
But when I try to boot the same image from eMMC (32G), the process stopped when the kernel start.
Here is an extract of the log from the serial console:
Please go to the last line to see the last operation.
Code: [10:40:49:671] U-Boot SPL 2023.07.02-armbian (Aug 31 2023 - 08:27:25 +0000)
[10:40:49:695] DRAM: 2048 MiB
[10:40:49:695] Trying to boot from MMC2
[10:40:50:402] NOTICE: BL31: v2.9(debug):armbian
[10:40:50:402] NOTICE: BL31: Built : 08:27:02, Aug 31 2023
[10:40:50:402] NOTICE: BL31: Detected Allwinner A64/H64/R18 SoC (1689)
[10:40:50:402] NOTICE: BL31: Found U-Boot DTB at 0x20ab818, model: SoPine with baseboard
[10:40:50:402] INFO: ARM GICv2 driver initialized
[10:40:50:402] INFO: Configuring SPC Controller
[10:40:50:402] INFO: PMIC: Probing AXP803 on RSB
[10:40:50:402] INFO: PMIC: dcdc1 voltage: 3.300V
[10:40:50:402] INFO: PMIC: dcdc5 voltage: 1.200V
[10:40:50:402] INFO: PMIC: dcdc6 voltage: 1.100V
[10:40:50:402] INFO: PMIC: dldo1 voltage: 3.300V
[10:40:50:402] INFO: PMIC: dldo2 voltage: 3.300V
[10:40:50:448] INFO: PMIC: dldo4 voltage: 3.300V
[10:40:50:448] INFO: PMIC: fldo1 voltage: 1.200V
[10:40:50:448] INFO: PMIC: Enabling DC SW
[10:40:50:448] INFO: BL31: Platform setup done
[10:40:50:448] INFO: BL31: Initializing runtime services
[10:40:50:448] INFO: BL31: cortex_a53: CPU workaround for 843419 was applied
[10:40:50:448] INFO: BL31: cortex_a53: CPU workaround for 855873 was applied
[10:40:50:448] INFO: BL31: cortex_a53: CPU workaround for 1530924 was applied
[10:40:50:448] SCP/INF: Crust v0.5.10000
[10:40:50:448] INFO: PSCI: Suspend is available via SCPI
[10:40:50:448] INFO: BL31: Preparing for EL3 exit to normal world
[10:40:50:468] INFO: Entry point address = 0x4a000000
[10:40:50:468] INFO: SPSR = 0x3c9
[10:40:50:961] ns16550_serial serial@1c28000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19
[10:40:50:961]
[10:40:50:961]
[10:40:50:961] U-Boot 2023.07.02-armbian (Aug 31 2023 - 08:27:25 +0000) Allwinner Technology
[10:40:50:961]
[10:40:50:961] CPU: Allwinner A64 (SUN50I)
[10:40:50:961] Model: SoPine with baseboard
[10:40:50:961] DRAM: 2 GiB
[10:40:51:022] Core: 73 devices, 22 uclasses, devicetree: separate
[10:40:51:022] WDT: Not starting watchdog@1c20ca0
[10:40:51:022] MMC: mmc@1c0f000: 0, mmc@1c11000: 1
[10:40:51:045] Loading Environment from FAT... Unable to use mmc 1:1...
[10:40:52:787] In: serial
[10:40:52:787] Out: serial
[10:40:52:787] Err: serial
[10:40:52:803] Net: eth0: ethernet@1c30000
[10:40:52:843] MMC: no card present
[10:40:52:843] ** Bad device specification mmc 0 **
[10:40:52:843] Couldn't find partition mmc 0
[10:40:52:843] MMC: no card present
[10:40:52:843] ** Bad device specification mmc 0 **
[10:40:52:843] Couldn't find partition mmc 0
[10:40:52:843] starting USB...
[10:40:52:843] Bus usb@1c1a000: sun4i_usb_phy phy@1c19400: External vbus detected, not enabling our own vbus
[10:40:52:881] USB EHCI 1.00
[10:40:52:881] Bus usb@1c1a400: USB OHCI 1.0
[10:40:52:897] Bus usb@1c1b000: USB EHCI 1.00
[10:40:52:924] Bus usb@1c1b400: USB OHCI 1.0
[10:40:52:924] scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
[10:40:54:067] scanning bus usb@1c1a400 for devices... 1 USB Device(s) found
[10:40:55:194] scanning bus usb@1c1b000 for devices... 1 USB Device(s) found
[10:40:56:329] scanning bus usb@1c1b400 for devices... 1 USB Device(s) found
[10:40:57:468] scanning usb for storage devices... 0 Storage Device(s) found
[10:40:57:468] Autoboot in 1 seconds, press <Space> to stop
[10:40:58:507] switch to partitions #0, OK
[10:40:58:523] mmc1(part 0) is current device
[10:40:58:523] Scanning mmc 1:1...
[10:40:58:555] Found U-Boot script /boot/boot.scr
[10:40:58:602] 3259 bytes read in 5 ms (635.7 KiB/s)
[10:40:58:602] ## Executing script at 4fc00000
[10:40:58:602] U-boot loaded from eMMC or secondary SD
[10:40:58:602] Boot script loaded from mmc
[10:40:58:602] 155 bytes read in 4 ms (37.1 KiB/s)
[10:40:58:602] MMC: no card present
[10:40:58:602] ** Bad device specification mmc 0 **
[10:40:58:642] 41715 bytes read in 11 ms (3.6 MiB/s)
[10:40:58:642] Working FDT set to 4fa00000
[10:40:58:642] 3821 bytes read in 5 ms (746.1 KiB/s)
[10:40:58:642] Applying kernel provided DT fixup script (sun50i-a64-fixup.scr)
[10:40:58:642] ## Executing script at 45000000
[10:40:59:041] 18215274 bytes read in 395 ms (44 MiB/s)
[10:40:59:533] 22390792 bytes read in 476 ms (44.9 MiB/s)
[10:40:59:533] Moving Image from 0x40080000 to 0x40200000, end=417d0000
[10:40:59:733] ## Loading init Ramdisk from Legacy Image at 4ff00000 ...
[10:40:59:733] Image Name: uInitrd
[10:40:59:733] Image Type: AArch64 Linux RAMDisk Image (gzip compressed)
[10:40:59:733] Data Size: 18215210 Bytes = 17.4 MiB
[10:40:59:733] Load Address: 00000000
[10:40:59:733] Entry Point: 00000000
[10:40:59:733] Verifying Checksum ... OK
[10:40:59:861] ## Flattened Device Tree blob at 4fa00000
[10:40:59:861] Booting using the fdt blob at 0x4fa00000
[10:40:59:882] Working FDT set to 4fa00000
[10:40:59:882] Loading Ramdisk to 48ea0000, end 49fff12a ... OK
[10:40:59:912] Loading Device Tree to 0000000048e2d000, end 0000000048e9ffff ... OK
[10:40:59:912] Working FDT set to 48e2d000
[10:41:00:344]
[10:41:00:344] Starting kernel ...
[10:41:00:344]
[10:41:03:989] <0x1b>[2J<0x1b>[3J<0x1b>[-1;-1fdone.
[10:41:04:014] Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
[10:41:04:014] Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems
It would be helpfull if somebody have any idea to solved this .
thanks for the support,
BR
|
|
|
Messed Up Modem |
Posted by: dorkydev - 11-05-2023, 11:26 AM - Forum: PinePhone Pro Hardware
- Replies (13)
|
 |
One of the gold prongs is missing off the board, and it's extremely finicky picking up a sim now or if one is picked up it eventually drops signal.
Currently, there is no cheaper way to get a new modem, is there? Unless I found a cheaper pinephone altogether on ebay used and removed it myself and replaced it.
Basically I had a micro inside a mini and that grove caught hold of the prongs one time and snagged up and out from the board, really wish we could just upgrade the slot all the way from a mini to a standard micro.
|
|
|
Connecting to Android Phone |
Posted by: dorkydev - 11-05-2023, 07:52 AM - Forum: PineTime Tutorials
- Replies (4)
|
 |
Okay so it bluetooth pairs with my phone (Motorola ThinkPhone Android 13) but Bangle.js Gadgetbridge doesn't want to discover it.
What am I forgetting to do?
Still running just regular InfiniTime vrs 1.11.0 fosdem edition bootldr 1.0.0
|
|
|
PPP as daily device. |
Posted by: DaForest - 11-04-2023, 04:09 PM - Forum: General Discussion of PinePhone Pro
- Replies (5)
|
 |
At present I am using my PPP as a daily driver in all capacities. What I have noticed is in order to keep heat to a minimum and also maximum battery life I tend to shut certain things down when not required. For example if I'm on wifi and shut down the modem, when done with BT and wifi I shut down BT and enable modem. Both cameras are shut down on dip switches always.
Something else I have noticed is that certain sim cards even from same carrier may operate differently. My Blackberry uses my main sim card and works perfectly. When I place that same sim in the PPP the connection is up and then drops and this cycle goes on and on. However when I place my newer sim card in PPP it works perfectly and never drops. That same sim in my Blackberry also works perfectly. The signal strength of my Blackberry sim is slightly weaker than PPP sim and I wonder if sim cards 'get tired'?
Also I use a Blackberry ear bud set with a 3.5mm jack for comms as nothing else seems to work. The sound is very good. I tried my son's gaming headset with 3.5mm jack and the sound was excellent.
|
|
|
bookworm vs trixie discussion for mobian in pinephone pro. |
Posted by: zetabeta - 11-04-2023, 01:31 PM - Forum: PinePhone Pro Software
- Replies (16)
|
 |
bookworm vs trixie discussion for mobian in pinephone pro.
this is a discussion of bookworm vs trixie and maybe staging. so like possible problems and how to fix them. which one is better, and how well it works. here are some generic arguments.
arguments for bookworm:
- stable.
- basics work.
- do not have dependency problems, or broken packages.
- smooth security updates.
arguments against bookworm:
- gets outdated.
- some features are missing, because pinephone is a beta product.
- stuck to the older kernel.
arguments for trixie:
- newer packages.
- features, which are missing in older versions.
- newer kernel.
arguments against trixie:
- dependency nightmare, broken packages.
- some thing do not work, because of unstable packages.
in both cases users have the choose between which audio routing they use, i don't know which one is default.
"pipewire-pulse"
"pulseaudio"
because pinephone pro is beta product, it practically means that users usually need to go on trixie. i recently updated pp pro into trixie, and it seems ok. however, there was dependency issues, so update is not smooth. more information later, how it goes. pp pro is not stuck to lts kernel, unlike pp regular (might be temporary issue though).
|
|
|
|