| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 30,251
» Latest member: naturasy
» Forum threads: 16,391
» Forum posts: 117,627
Full Statistics
|
| Latest Threads |
Article: Will Linux phone...
Forum: General
Last Post: zetabeta
Yesterday, 11:29 AM
» Replies: 2
» Views: 141
|
Star64 Irradium (based on...
Forum: Getting Started
Last Post: mara
10-08-2026, 02:00 PM
» Replies: 21
» Views: 20,700
|
Pinecil V2 + Raspberry Pi...
Forum: General
Last Post: candera
10-08-2026, 03:26 AM
» Replies: 0
» Views: 62
|
SlateOS feedback needed!
Forum: Development Discussion on PineTime
Last Post: Nolegdai
10-05-2026, 02:04 PM
» Replies: 1
» Views: 727
|
Unknown Startup Password ...
Forum: PineTab Hardware
Last Post: tllim
10-05-2026, 12:44 PM
» Replies: 1
» Views: 212
|
HDMI or VGA From Pinebook...
Forum: Pinebook Pro Hardware and Accessories
Last Post: tllim
10-05-2026, 12:42 PM
» Replies: 7
» Views: 10,227
|
Delivery to Ukraine
Forum: Shipment Related Discussion
Last Post: freidepiter
10-01-2026, 12:56 PM
» Replies: 10
» Views: 16,618
|
PINEPOCALYPSE (pics inclu...
Forum: General Discussion on Pinebook Pro
Last Post: segaloco
09-29-2026, 11:36 PM
» Replies: 2
» Views: 665
|
PineTab-V Experiences
Forum: General Discussion on PineTab
Last Post: segaloco
09-29-2026, 11:28 PM
» Replies: 0
» Views: 235
|
irradium (based on crux l...
Forum: Linux on Rock64
Last Post: mara
09-27-2026, 11:55 AM
» Replies: 14
» Views: 21,240
|
|
|
| Disabling last mount time check on boot |
|
Posted by: acwest - 03-03-2023, 09:24 PM - Forum: Linux on Rock64
- No Replies
|
 |
Every time my Rock64 boots, I get an error about the Superblock last mount time is in the future. As I don't have a working hardware clock, this happens on every boot, force an fsck and adding to the boot time. When searching for this error, most of the recommendations are to fix the clock, but that isn't really feasible on a device that doesn't have one. Seeing as this check happens before mounting the filesystem, a solution like fake-hwclock isn't likely to be useful either. I can't be the only one with this problem...
|
|
|
|
| Pinebuds and Calls |
|
Posted by: kandrew - 03-03-2023, 02:53 PM - Forum: General
- No Replies
|
 |
Hi all,
For pinebud users out there, how is the voice quality when making calls with these? Is the open firmware any better than the default one that ships in this regard?
Thanks!
|
|
|
|
| too much batteries |
|
Posted by: Gwen - 03-03-2023, 01:03 PM - Forum: General Discussion on PinePhone
- Replies (1)
|
 |
HI,
I have a pinephone (not pro) with battery keyboard and last version of postmarketOS.
I didn't noticed any problem at start but after few days, power management in settings app in postmarketOS showed two 'extra batteries' which lead to problems calculating the percentage of charge. (max was 67% instead of 100% when fully charged)
Since two days I now have a third extra battery instead of only one (1 main battery + 3 extra batteries) ... how can I correct this please ?
Thx.
|
|
|
|
| PPkeyboard oddities with top row characters on "dreemurrs-embedded / Pine64-Arch" |
|
Posted by: Jeremiah Roise - 03-02-2023, 02:56 PM - Forum: PinePhone Hardware
- Replies (1)
|
 |
So I recently installed arch https://github.com/dreemurrs-embedded/Pi...g/20230203 on on my Pinephone (not pro), and tried to use the keyboard which was fine except the top row characters ( - _ + = ~ etc), I don't know exactly what i did but it fixed it for me.
I updated my ppkb's firmware to 1.3 here's the guide to update https://xnux.eu/log/#078
I then used the bottom part of this guide https://wiki.mobian-project.org/doku.php...ccessories this part:
Symbol Keys
With the latest version of the keyboard drivers, the Fn-symbol keys disappear. This can be fixed by: - Setting
Code: XKB_DEFAULT_MODEL=ppkb
in Phosh's environment. Add the following to
Code: /usr/lib/systemd/system/phosh.service.d/override.conf
:
[Service]
Environment=XKB_DEFAULT_MODEL=ppkb
After this, the top row symbols will be available as L3-{0-9}. The L3 key can be configured in settings → keyboard → Alternative Characters Key.
New versions of Mobian do not launch Phosh as a systemd service. In that case the override above will not work. Instead, add the following line to
:
export XKB_DEFAULT_MODEL=ppkb
and reboot.
I then went to (phosh) settings -> keyboard -> special character Entry -> Alternate Characters Key: and changed it to left alt
it then worked,
and it continued to work when I changed it back to the original alternate character key.
Hope this helps someone out there!
|
|
|
|
| PPP not booting: Missing DTB |
|
Posted by: andy.lynx10 - 03-01-2023, 12:48 PM - Forum: General Discussion of PinePhone Pro
- Replies (4)
|
 |
My Pinephone Pro doesn't start and it seems like the bootloader itself is not working.
Whether I press or hold the power button or connect the charging cable or combine the former with holding any of the volume buttons, nothing happens - no vibration, no LED light, no display output.
The battery does not seem to be the problem - it works reliably in my older Pinephone.
I tried flashing a fresh Manjaro image to an SD card and booting it in the PPP by holding the RE button during the startup. Again, no visible response.
The following output from the PPP console is the only response I am able to get. It is shown right after a startup attempt.
U-Boot TPL 2021.10 (Oct 04 2021 - 15:09:26)
sdram_init: LPDDR4 - 50MHz failed!
rk3399_dmc_init DRAM init failed -22
Missing DTB
After this the console remains mute. However, the device seems to be "running" - for lack of a better word - the chipset cover is slightly warm and to replicate the former console output again, the power button needs to be pressed for a few seconds - just like in regular reset.
Could you please help me with an advice? Is the device dead for good? Have anyone encountered a similar behavior?
|
|
|
|
| quartz64-a - on-board SATA port problems |
|
Posted by: manning - 03-01-2023, 05:20 AM - Forum: Linux on Quartz64
- Replies (2)
|
 |
Hi all,
I've been having problems getting the on-board SATA port on the Quartz64 Model A working, and I'm hoping someone might be able to point me in the right direction. Thanks in advance for any help.
Hardware
- Quartz64 model A
- Current generation HDD
- SATA cable
- 5A power supply
- Pine64 board to 2x SATA power splitter cable
Software
Validating the manual edits:
Code: $ ls /boot/dtbs/rockchip/ | grep quartz64
rk3566-quartz64-a.dtb
rk3566-quartz64-a-sata.dtb
rk3566-quartz64-b.dtb
Code: $ fdtget /boot/dtbs/rockchip/rk3566-quartz64-a-sata.dtb /usb@fd000000 status
disabled
Code: $ fdtget /boot/dtbs/rockchip/rk3566-quartz64-a-sata.dtb /sata@fc400000 status
okay
Code: $ cat /boot/extlinux/extlinux.conf
LABEL Manjaro ARM
KERNEL /Image
FDT /dtbs/rockchip/rk3566-quartz64-a-sata.dtb
APPEND initrd=/initramfs-linux.img console=ttyS2,1500000 earlycon=uart8250,mmio32,0xfe660000 root=PARTUUID=<REDACTED> rw rootwait audit=0 splash plymouth.ignore-serial-consoles
Tests performed
- Tested SATA cable in another system, confirmed good; tested with other known-good SATA cables
- Tested a 2 port SATA to PCIe adaptor card (the Pine64 one), which works perfectly on this board
- Tested multiple known-good HDDs one at a time; all work via the PCIe card, none appear on the on-board SATA port
- Tested running 3 drives simultaneously; those plugged into the PCIe adapter work, but not on the on-board SATA port. Have cycled which drive was plugged into which SATA port, for the same result
These test results imply to me it's most likely a problem with the software setup, with a small chance the hardware is problematic.
Various debug outputs
dmesg:
Code: $ dmesg | grep ATA
<blank>
Code: [ 0.149542] usbcore: registered new interface driver usbfs
Code: [ 0.149609] usbcore: registered new interface driver hub
Code: [ 0.149660] usbcore: registered new device driver usb
Code: [ 0.344238] usbcore: registered new interface driver uas
Code: [ 0.344374] usbcore: registered new interface driver usb-storage
Code: [ 0.344521] usbcore: registered new interface driver usbserial_generic
Code: [ 0.344583] usbserial: USB Serial support registered for generic
Code: [ 0.345027] ehci-platform fd800000.usb: EHCI Host Controller
Code: [ 0.345053] ohci-platform fd840000.usb: Generic Platform OHCI controller
Code: [ 0.345117] ehci-platform fd880000.usb: EHCI Host Controller
Code: [ 0.345456] ehci-platform fd880000.usb: new USB bus registered, assigned bus number 2
Code: [ 0.345498] ehci-platform fd800000.usb: new USB bus registered, assigned bus number 1
Code: [ 0.345662] ehci-platform fd880000.usb: irq 36, io mem 0xfd880000
Code: [ 0.345722] ehci-platform fd800000.usb: irq 35, io mem 0xfd800000
Code: [ 0.345783] ohci-platform fd8c0000.usb: Generic Platform OHCI controller
Code: [ 0.345828] ohci-platform fd840000.usb: new USB bus registered, assigned bus number 3
Code: [ 0.346057] ohci-platform fd840000.usb: irq 37, io mem 0xfd840000
Code: [ 0.346073] ohci-platform fd8c0000.usb: new USB bus registered, assigned bus number 4
Code: [ 0.346193] ohci-platform fd8c0000.usb: irq 38, io mem 0xfd8c0000
Code: [ 0.374372] ehci-platform fd880000.usb: USB 2.0 started, EHCI 1.00
Code: [ 0.374890] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01
Code: [ 0.374912] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Code: [ 0.374924] usb usb2: Product: EHCI Host Controller
Code: [ 0.374934] usb usb2: Manufacturer: Linux 6.1.12-1-MANJARO-ARM ehci_hcd
Code: [ 0.374942] usb usb2: SerialNumber: fd880000.usb
Code: [ 0.404373] ehci-platform fd800000.usb: USB 2.0 started, EHCI 1.00
Code: [ 0.404975] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01
Code: [ 0.404997] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Code: [ 0.405008] usb usb1: Product: EHCI Host Controller
Code: [ 0.405017] usb usb1: Manufacturer: Linux 6.1.12-1-MANJARO-ARM ehci_hcd
Code: [ 0.405026] usb usb1: SerialNumber: fd800000.usb
Code: [ 0.418667] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 6.01
Code: [ 0.418701] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Code: [ 0.418714] usb usb4: Product: Generic Platform OHCI controller
Code: [ 0.418723] usb usb4: Manufacturer: Linux 6.1.12-1-MANJARO-ARM ohci_hcd
Code: [ 0.418732] usb usb4: SerialNumber: fd8c0000.usb
Code: [ 0.420667] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 6.01
Code: [ 0.420691] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Code: [ 0.420703] usb usb3: Product: Generic Platform OHCI controller
Code: [ 0.420713] usb usb3: Manufacturer: Linux 6.1.12-1-MANJARO-ARM ohci_hcd
Code: [ 0.420723] usb usb3: SerialNumber: fd840000.usb
Code: [ 0.502514] usbcore: registered new interface driver pcwd_usb
Code: [ 0.518025] usbcore: registered new interface driver usbhid
Code: [ 0.518032] usbhid: USB HID core driver
Code: [ 0.685734] reg-fixed-voltage vcc5v0_usb20_otg: nonexclusive access to GPIO for vcc5v0_usb20_otg
Code: [ 1.855035] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01
Code: [ 1.855074] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Code: [ 1.855098] usb usb5: Product: xHCI Host Controller
Code: [ 1.855117] usb usb5: Manufacturer: Linux 6.1.12-1-MANJARO-ARM xhci-hcd
Code: [ 1.855134] usb usb5: SerialNumber: xhci-hcd.0.auto
Looking for block devices doesn't show any SATA hard drives:
Code: $ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
mmcblk1 179:0 0 14.6G 0 disk
├─mmcblk1p1 179:1 0 457.8M 0 part /boot
└─mmcblk1p2 179:2 0 14.1G 0 part /
mmcblk1boot0 179:32 0 4M 1 disk
mmcblk1boot1 179:64 0 4M 1 disk
zram0 253:0 0 5.5G 0 disk [SWAP]
Code: $ sudo fdisk -l
Disk /dev/mmcblk1: 14.59 GiB, 15665725440 bytes, 30597120 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 9D5D28C6-63B7-4C32-BA44-DAAF62A38685
Device Start End Sectors Size Type
/dev/mmcblk1p1 62500 1000000 937501 457.8M Microsoft basic data
/dev/mmcblk1p2 1000001 30597086 29597086 14.1G Linux filesystem
Disk /dev/mmcblk1boot0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mmcblk1boot1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/zram0: 5.48 GiB, 5886869504 bytes, 1437224 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
|
|
|
|
| APN settings not working with new operator SIM card |
|
Posted by: user641 - 03-01-2023, 02:48 AM - Forum: Mobian on PinePhone
- Replies (1)
|
 |
Hello, I have been using a pp for more than a year and never had this problem, I got this SIM card from kena, a virtual operator that uses tim network.
It displays the 4G signal with "!" I have tried the automatic depection of APN simpydoing nothing, then the recommended by the operator, then some other possible combination, none work. On a degoogled phone it works without any problems or need of manual setup. Any tips?
|
|
|
|
|