| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
Fixing the Quartz64 USB3 ...
Forum: Quartz64 Tutorials
Last Post: mig
6 hours ago
» Replies: 1
» Views: 12,741
|
Pinecil as a Pocket-Sized...
Forum: General
Last Post: Arsen
Yesterday, 09:15 AM
» Replies: 0
» Views: 45
|
SlateOS feedback needed!
Forum: Development Discussion on PineTime
Last Post: highjumpman
08-24-2026, 08:00 AM
» Replies: 0
» Views: 118
|
Pinephone + Keyboard for ...
Forum: PinePhone Hardware
Last Post: Nambo
08-23-2026, 12:17 AM
» Replies: 18
» Views: 13,475
|
Hello, I am a new member ...
Forum: General
Last Post: WhiteRabbit0
08-20-2026, 12:17 PM
» Replies: 0
» Views: 320
|
Need help compiling andro...
Forum: Android on Pine A64(+)
Last Post: ahegarosib97
08-20-2026, 08:45 AM
» Replies: 2
» Views: 1,997
|
RAM-free SBCs with SODIMM...
Forum: General
Last Post: anchor
08-20-2026, 08:21 AM
» Replies: 0
» Views: 141
|
Default password
Forum: PineTab Hardware
Last Post: dissimilar_goose
08-20-2026, 05:02 AM
» Replies: 0
» Views: 185
|
New SlateOS features
Forum: Development Discussion on PineTime
Last Post: highjumpman
08-17-2026, 07:47 PM
» Replies: 0
» Views: 233
|
SlateOS for PineTime
Forum: Development Discussion on PineTime
Last Post: highjumpman
08-17-2026, 07:33 PM
» Replies: 2
» Views: 507
|
|
|
| FOSS fw problem - PinePhonePro, EG25 modem |
|
Posted by: dukla2000 - 01-31-2025, 07:24 AM - Forum: PinePhone Hardware
- Replies (5)
|
 |
OK, so I have had an older PinePhonePro (mini SIM rather than micro SIM) for a while. I had flashed Biktorg's fw to it and used to be able to chat to the modem fine. A while back I had a problem 1 night setting a wakeup call (can't remember, power fail, think trying to flash 0.8.0) and since then I cant SMS the modem. I have tried everything I can think of, flashing back to stock, trying fwupd to flash, pmOS, arch, mobian, 30.006, 01.003 ADSP firmware, ...
So as I write this I have my PPP which has a "Frankenstein" firmware (it seems half FOSS but with stock artefacts) and my old PP in front of me which is FOSS and behaves like I expect.
The basic problem that is the subject of this thread - I can't send SMS to the modem:
Code: $ cat sms.txt | sxmo_modemsendsms.sh +223344556677 -
12:41:25 sxmo_modemsendsms.sh: Couldn't send text message (error: couldn't send the SMS: 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Connected: No AT port available to run command')
Couldn't send text message (error: couldn't send the SMS: 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Connected: No AT port available to run command')
The system log during boot - note the serial number is "community_fw":
Code: [ 34.237819] usb 1-1: new high-speed USB device number 3 using ehci-platform
[ 34.368702] usb 1-1: New USB device found, idVendor=2c7c, idProduct=0125, bcdDevice= 3.18
[ 34.368737] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 34.368747] usb 1-1: Product: LTE Module
[ 34.368755] usb 1-1: Manufacturer: Quectel, Incorporated
[ 34.368764] usb 1-1: SerialNumber: community_fw
[ 34.441830] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
[ 34.442645] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
[ 34.443151] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB2
[ 34.443494] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB3
For cross reference on my PP the system log has the same info:
Code: [ 52.475036] usb 2-1: new high-speed USB device number 3 using ehci-platform
[ 52.636611] usb 2-1: New USB device found, idVendor=2c7c, idProduct=0125, bcdDevice= 3.18
[ 52.640986] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 52.641138] usb 2-1: Product: LTE Module
[ 52.641198] usb 2-1: Manufacturer: Quectel, Incorporated
[ 52.641232] usb 2-1: SerialNumber: community_fw
[ 52.717965] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB0
[ 52.723460] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB1
[ 52.737674] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB2
[ 52.742115] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB3
The reason for my "Frankenstein" use is that the differences start showing in the journal - my PPP has
Code: [Jan 31 12:27:05] daemon eg25-manager: ** Message: 12:27:05.087: Successfully sent command: AT+QGMR
...
[Jan 31 12:27:05] daemon eg25-manager: ** Message: 12:27:05.113: Response: [EG25GGBR07A08M2G_01.003.00.000\r\n\r\nOK]
Whereas the PP has
Code: [Jan 01 01:01:30] daemon eg25-manager: ** Message: 01:01:30.626: Successfully sent command: AT+QGMR
...
[Jan 01 01:01:30] daemon eg25-manager: ** Message: 01:01:30.645: Response: [0.7.4\r\n\r\nOK]
So it appears my most recent attempt to flash the modem failed, but the log is (flashing 0.7.4 FWIW):
Code: # ./flashall
Sending AT+QFASTBOOT...
OKAY [ 0.002s]
Finished. Total time: 0.002s
Warning: skip copying aboot image avb footer (aboot partition size: 0, aboot image size: 286476).
Sending 'aboot' (279 KB) OKAY [ 0.013s]
Writing 'aboot' OKAY [ 0.131s]
Finished. Total time: 0.166s
Rebooting OKAY [ 0.004s]
Finished. Total time: 0.055s
< waiting for any device >
OKAY [ 0.002s]
Finished. Total time: 0.002s
Sending 'boot' (4600 KB) OKAY [ 0.149s]
Writing 'boot' OKAY [ 1.793s]
Finished. Total time: 1.955s
Sending 'recovery' (4600 KB) OKAY [ 0.148s]
Writing 'recovery' OKAY [ 1.795s]
Finished. Total time: 1.963s
Warning: skip copying system image avb footer (system partition size: 0, system image size: 28311552).
Sending 'system' (27648 KB) OKAY [ 0.879s]
Writing 'system' OKAY [ 11.942s]
Finished. Total time: 12.844s
Warning: skip copying recoveryfs image avb footer (recoveryfs partition size: 0, recoveryfs image size: 13369344).
Sending 'recoveryfs' (13056 KB) OKAY [ 0.417s]
Writing 'recoveryfs' OKAY [ 4.949s]
Finished. Total time: 5.391s
Rebooting OKAY [ 0.004s]
Finished. Total time: 0.055s
Done!
Any thoughts welcome - my only hope is to keep trying to flash 0.7.4 and hope it works!
|
|
|
|
| user kernel modules and dkms |
|
Posted by: brt64 - 01-28-2025, 02:26 PM - Forum: PineTab Software
- No Replies
|
|
Hello,
On a Pintetab2, Arch Plasma (default system) I tried to install a user kernel module with dkms functionality. Looking for the needed header files, I installed the linux-aarch64-headers package with Octopi, and I installed also the dkms, ntfs3-dkms and asix-ax88179-dkms packages.
Problem now with the kernel modules, if I use the command lsmod, not any module is listed ...
And no way to reach the internet ...
Do I need an other header package ?
How can I restore de default modules ?
Do I need to rebuild the kernel ? How ?
thanks for any advice !
|
|
|
|
| new manjaro install: wlan0 stuck in setting network address |
|
Posted by: zkajdan - 01-28-2025, 11:50 AM - Forum: Linux on Pinebook Pro
- Replies (5)
|
|
Hi,
I am following this post:
https://forum.pine64.org/showthread.php?tid=10403
to install current Manjaro on the ponebook. So far, I have successfully installed Manjaro 23.02 on the sd card.
But from the new sd card installation, I cannot use wifi to download an image for the emmc install:
wlan0 is forever hanging in "connecting"/"setting network address".
ip link shows the interface as dormant. NetworkManager is running, and the nameserver setting is correct in /etc/resolv.conf. I can also ping the nameserver.
But ip route does not return anything.
Would anyone have an idea what is going wrong? Many thanks in advance!!
|
|
|
|
| rk2aw questions |
|
Posted by: antanas - 01-28-2025, 06:47 AM - Forum: General Discussion of PinePhone Pro
- Replies (6)
|
|
Hi. I have installed rk2aw and primary/fallback bootloaders from https://xff.cz/kernels/bootloaders-2024.04/ppp/ with spinor-flash-initial-setup.sh script. Then, I have installed mobian to emmc with installer image booted from SD card. Mobian does not load when just turning on the phone but if I enter rk2aw LED based menu and select primary (2 flashes) or fallback (3 flashes) bootloader, then selecting mobian option from uboot will actually load the OS. Looking at https://xnux.eu/log/098.html I was hoping that EFI stuff will work but I'm getting invalid elf header magic errors.
So I have few questions:
1. How to diagnose what is preventing booting with "Perform a normal rk2aw boot." option (1 flash)
2. What are the differences for ppp between floss and rkbin bootloaders? (menu looks the same for me).
3. Maybe primary bootloader does not work for me and I'm always taken to the fallback bootloader, so how can I verify which uboot bootloader menu is being shown?
|
|
|
|
| Gentoo on Pinetab |
|
Posted by: istewart - 01-26-2025, 08:21 PM - Forum: General Discussion on PineTab
- No Replies
|
|
Hello,
I've been trying to set up Gentoo on an SD card in my Pinetab2 since I received it a few weeks ago. I am generally more comfortable with Portage than pacman, and I would also like to test and possibly provide support for Gentoo's arm64 binary packages. This means that I have built a partition table up from scratch on the SD card, rather than duplicating an existing installation image. It's a very simple partition table:
mmcblk1p1: EFI boot partition mounted at /efi, FAT32
mmcblk1p2: swap
mmcblk1p3: root partition, ext4
The Pine64 RockPro64 entry on the Gentoo wiki: https://wiki.gentoo.org/wiki/PINE64_ROCK...bootloader indicates that whoever wrote it had success using a standalone build of Grub on an EFI system partition to get the RockPro to boot, but I am not having the same success on the Pinetab. Should I instead be installing U-Boot to the boot partition? Or flashing it to the first sectors of the SD card? I am still unsure about the normal procedure for using U-Boot or where it should be installed.
At what point might I also want to consider the rk2aw bootloader? This person had success using it with Fedora: https://www.jistr.com/blog/2023-11-27-fe...-pinetab2/
It also seems like the tablet is now not booting at all with the SD card inserted, which was not the case before I formatted the SD card with the boot partition. But it could be possible that it is actually attempting to boot but I just have no video output/keyboard backlight, since the stock Gentoo binary kernel probably doesn't have drivers for these. I can attempt to use the Danctnix kernel patches and build my own kernel, but I am curious, exactly what devices does it patch in support for?
The bes2600 wifi driver is not important to start with, as I have a USB-Ethernet adapter that has Linux kernel support. I plan to install the wifi driver after I have a properly booting system, and also write a Gentoo ebuild for it.
|
|
|
|
|
