| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,889
» Latest member: Haptic
» Forum threads: 16,323
» Forum posts: 117,412
Full Statistics
|
| Latest Threads |
Replacement battery for P...
Forum: Pinebook Pro Hardware and Accessories
Last Post: KC9UDX
9 hours ago
» Replies: 5
» Views: 5,493
|
pinephone-support package...
Forum: General Discussion on PinePhone
Last Post: baptx
Yesterday, 05:49 PM
» Replies: 5
» Views: 5,856
|
SSH over USB
Forum: Mobian on PinePhone
Last Post: baptx
Yesterday, 04:42 PM
» Replies: 15
» Views: 19,703
|
No wIfI after Mobian upda...
Forum: General Discussion on PinePhone
Last Post: baptx
Yesterday, 04:18 PM
» Replies: 5
» Views: 6,005
|
Problems With Extensions ...
Forum: PineNote Software
Last Post: HippopoStar
Yesterday, 02:29 PM
» Replies: 1
» Views: 218
|
RISC OS Linux port
Forum: PineTab Software
Last Post: Raik
02-26-2026, 05:40 AM
» Replies: 0
» Views: 100
|
New Pinetab- error when a...
Forum: PineTab Software
Last Post: Raik
02-26-2026, 01:21 AM
» Replies: 1
» Views: 285
|
Systemupgrade fails
Forum: PineTab Software
Last Post: Raik
02-25-2026, 11:15 PM
» Replies: 0
» Views: 60
|
dead Pinebook - help plea...
Forum: General Discussion on Pinebook Pro
Last Post: wdt
02-25-2026, 06:44 PM
» Replies: 1
» Views: 176
|
wifi password wont save
Forum: General Discussion on PineTab
Last Post: WEF
02-24-2026, 06:47 PM
» Replies: 2
» Views: 371
|
|
|
| Pinetab2 stays dark / won't boot |
|
Posted by: derco0n - 07-13-2023, 11:44 AM - Forum: PineTab Hardware
- No Replies
|
 |
Hi everyone,
my Pinetab2 suddenly stopped working after around 4 weeks of minor usage.
The main symptom is, that the display stays complete black when trying to power on.
As Pine64's support is unfortunately not very helpful and pointed me to the community, i'd really appreciate your help.
I was able to get the following out from UART-console:
Code: ## Checking hash(es) for Image u-boot ... sha256+ OK
## Checking hash(es) for Image fdt-2 ... sha256+ OK
## Checking hash(es) for Image atf-2 ... sha256+ OK
## Checking hash(es) for Image atf-3 ... sha256+ OK
## Checking hash(es) for Image atf-4 ... sha256+ OK
## Checking hash(es) for Image atf-5 ... sha256+ OK
## Checking hash(es) for Image atf-6 ... sha256+ OK
INFO: Preloader serial: 2
NOTICE: BL31: v2.3():v2.3-594-g7f859117f:cl
NOTICE: BL31: Built : 04:51:16, May 11 2023
INFO: GICv3 without legacy support detected.
INFO: ARM GICv3 driver initialized in EL3
INFO: pmu v1 is valid 220114
INFO: dfs DDR fsp_param[0].freq_mhz= 1056MHz
INFO: dfs DDR fsp_param[1].freq_mhz= 324MHz
INFO: dfs DDR fsp_param[2].freq_mhz= 528MHz
INFO: dfs DDR fsp_param[3].freq_mhz= 780MHz
INFO: BL31: Initialising Exception Handling Framework
INFO: BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK
ERROR: Error initializing runtime service opteed_fast
INFO: BL31: Preparing for EL3 exit to normal world
INFO: Entry point address = 0xa00000
INFO: SPSR = 0x3c9
U-Boot 2023.07-1-00043-g2e0e11b8e6 (Jul 01 2023 - 07:59:26 +0000)
Model: Pine64 PineTab2 v2.0
DRAM: 8 GiB (effective 7.7 GiB)
PMIC: RK8170 (on=0x80, off=0x04)
Core: 321 devices, 25 uclasses, devicetree: separate
MMC: mmc@fe2b0000: 1, mmc@fe2c0000: 2, mmc@fe310000: 0
Loading Environment from nowhere... OK
In: serial@fe660000
Out: serial@fe660000
Err: serial@fe660000
Model: Pine64 PineTab2 v2.0
Net: No ethernet found.
Hit any key to stop autoboot: 0
Card did not respond to voltage select! : -110
** Booting bootflow 'mmc@fe310000.bootdev.part_1' with script
Booting from eMMC
Loading kernel...
Failed to load '/Image.gz'
Uncompressing kernel...
Error: Bad gzipped data
Loading initramfs...
7685356 bytes read in 68 ms (107.8 MiB/s)
Loading dtb...
120036 bytes read in 41 ms (2.8 MiB/s)
Booting...
Bad Linux ARM64 Image magic!
Boot failed (err=-14)
No ethernet found.
No ethernet found.
|
|
|
|
| Problem with USB 3.0 Type A |
|
Posted by: hobbitus - 07-13-2023, 03:46 AM - Forum: Pinebook Pro Hardware and Accessories
- Replies (4)
|
 |
Hello everyone,
I have got problem with the USB 3.0 Type A
No information in dmesg or journalctl -f -u systemd-udevd about any devices in this USB port.
$lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 002: ID 258a:001e HAILUCK CO.,LTD USB KEYBOARD
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
$lsusb -tv
/: Bus 08.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M
ID 1d6b:0001 Linux Foundation 1.1 root hub
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
ID 258a:001e
|__ Port 1: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
ID 258a:001e
/: Bus 07.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
/: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
ID 1d6b:0003 Linux Foundation 3.0 root hub
/: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
ID 1d6b:0003 Linux Foundation 3.0 root hub
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M
ID 1d6b:0001 Linux Foundation 1.1 root hub
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
ID 05e3:0608 Genesys Logic, Inc. Hub
|__ Port 1: Dev 6, If 0, Class=Vendor Specific Class, Driver=mt7601u, 480M
ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless Adapter
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
I do not know if this could be hardware issue, OS (Manjaro) or anything else?
Thank you for advice and suggestions.
PS: I've just noticed this post with similar, possibly the same issues https://forum.manjaro.org/t/usb-port-bre...sue/139653
|
|
|
|
| Failure of R4 |
|
Posted by: ph0x - 07-11-2023, 10:21 PM - Forum: Pinecil Hardware and Accessories
- No Replies
|
 |
The R4 resistor in my pinecil has failed, when I insert a dc jack I can see a tiny spark in a tiny crack inside the resistor. Is this likely to take down anything else hardware wise, like the mosfet directly in front of it?
|
|
|
|
| PinePhone Pro not booting (Cap error!, pctl timeout) |
|
Posted by: jealda - 07-11-2023, 10:50 AM - Forum: PinePhone Hardware
- Replies (2)
|
 |
Hello,
today I tried to boot my PinePhone Pro, but it doesn't boot.
- Battery is charged (used external Charger, bought new battery)
- I can connect it to my PC and see the device in MASKROM mode
- no led or vibration is noticable
Trying to boot the phone connected with UART got me following lines.
Code: U-Boot TPL 2021.10 (Oct 04 2021 - 15:09:26)
Channel 0: col error
Cap error!
Channel 1: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
256B stride
lpddr4_set_ctl: channel 0 training failed!
lpddr4_set_rate: change freq to 400000000 mhz 0, 1
read_mr: pctl timeout!
Do someone have seen this, or maybe a solution to this problem?
|
|
|
|
| Installing CH431SER on Ayufan 0.9.14: gitlab-ci-linux-build-159 |
|
Posted by: Thisone - 07-11-2023, 01:12 AM - Forum: Linux on RockPro64
- Replies (4)
|
 |
Hello
when I try to install the Driver CH341SER from CH341SER_LINUX.ZIP - 南京沁恒微电子股份有限公司 (wch.cn) for the Ayufan linux build. I get this error Message during the compilation:
Code: rock64@rockpro64:~/CH341SER_LINUX/driver$ make
make -C /lib/modules/4.4.190-1233-rockchip-ayufan-gd3f1be0ed310/build M=/home/rock64/CH341SER_LINUX/driver
make[1]: Entering directory '/usr/src/linux-headers-4.4.190-1233-rockchip-ayufan-gd3f1be0ed310'
CC [M] /home/rock64/CH341SER_LINUX/driver/ch341.o
gcc: error: unrecognized command line option '-mgeneral-regs-only'
gcc: error: unrecognized command line option '-mcmodel=large'
scripts/Makefile.build:283: recipe for target '/home/rock64/CH341SER_LINUX/driver/ch341.o' failed
make[2]: *** [/home/rock64/CH341SER_LINUX/driver/ch341.o] Error 1
Makefile:1479: recipe for target '_module_/home/rock64/CH341SER_LINUX/driver' failed
make[1]: *** [_module_/home/rock64/CH341SER_LINUX/driver] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-4.4.190-1233-rockchip-ayufan-gd3f1be0ed310'
Makefile:5: recipe for target 'default' failed
make: *** [default] Error 2
I want to use the PineDisplay as Display on Linux and since Ayufan has a Documentation how to use it on his Linux Build, i use it.
But i need to install the Driver to use a CH340c RS485 to USB converter.
Any help is greatly appreciated.
|
|
|
|
| Keyboard charges, won't type - ERROR: I2C_RDWR failed: No such device or address |
|
Posted by: jovval - 07-10-2023, 08:11 AM - Forum: PinePhone Pro Accessories
- No Replies
|
 |
With a new PPP, I am on stock software (Manjaro-Plasma, I believe).
I have installed necessary packages for compiling megi's userland software for ppkb.
Too, I have compiled it, and added the system service as I explained (in the wrong sub-forum) here,
PinePhone Keyboard won't work. read_kb_reg(PPKB_SYS_CONFIG) needs what? - https://forum.pine64.org/showthread.php?tid=18476
My PPKB charges but won't type.
lsmod ends with
pinephone_keyboard
but has no instance of kb151.
With the PPP firmly seated in my PPKB (and charging, battery staying at 100%), I tried the command
build/ppkb-i2c-flasher --rom-in firmware/build/fw-user.bin write reset
and saw
ERROR: I2C_RDWR failed: No such device or address
I did
rmmod pinephone_keyboard
and repeated the above. I had the same result.
Installing i2c-tools
pacman -S i2c-tools
had no effect on the command above.
I did see the following.
i2cdetect -l
i2c-0 i2c rk3x-i2c I2C adapter
i2c-1 i2c rk3x-i2c I2C adapter
i2c-3 i2c rk3x-i2c I2C adapter
i2c-4 i2c rk3x-i2c I2C adapter
i2c-5 i2c rk3x-i2c I2C adapter
i2c-9 i2c i2c-4-mux (chan_id 0) I2C adapter
I can not blacklist anything b/c
update-initramfs -u
bash: update-initramfs: command not found
I installed both
mkinitcpio
mkinitcpio-busybox
and still can not update-initramfs.
As a user posted here,
keyboard case charging but not typing - https://forum.pine64.org/showthread.php?tid=17464
with the PPP firmly seated in the PPKB and booted therein, I too found,
dmesg | grep keyboard
pinephone-keyboard 2-0015: Keyboard was not found on the I2C bus, maybe it's disconnected.
How do I get "such device or address", shown above?
|
|
|
|
| PinePhone Keyboard won't work. read_kb_reg(PPKB_SYS_CONFIG) needs what? |
|
Posted by: jovval - 07-09-2023, 09:03 PM - Forum: PinePhone Pro Hardware
- No Replies
|
 |
As root, I did,
pacman -Syu
pacman -S git php sdcc make gcc
As a normal user I did,
git clone https://megous.com/git/pinephone-keyboard
cd pinephone-keyboard
make all
As root, I continued with
cp -a Downloads/pinephone-keyboard/build/* /usr/local/bin/
vi /etc/systemd/system/ppkb-i2c-inputd.service
and added,
[Unit]
Description=Pinephone Keyboard Service Daemon
[Service]
Type=simple
ExecStart=/usr/local/bin/ppkb-i2c-inputd
[Install]
WantedBy=multi-user.target
I had no need to blacklist kbd51
lsmod | grep kbd
gave nothing. I did see
pinephone_keyboard 16384 0
at the end of lsmod.
I enabled the new systemd service.
systemctl enable ppkb-i2c-inputd.service
Created symlink /etc/systemd/system/multi-user.target.wants/ppkb-i2c-inputd.service → /etc/systemd/system/ppkb-i2c-inputd.service.
The following did/showed nothing.
systemctl start ppkb-i2c-inputd
ps ax | grep ppkb
gave no match.
I rebooted and found the same results both above and below.
The following command (with the PPP out of and in the ppkb) generated a WARNING and an ERROR.
pkb-i2c-inputd
WARNING: I2C_RDWR failed (6)
ERROR: read_kb_reg(PPKB_SYS_CONFIG) failed: No such device or address
Having inserted the PPP into the ppkb, I found that charging works.
The keys do not work.
How may I obtain "such device or address"?
|
|
|
|
| Upgrade Fedora from 37 to 38? |
|
Posted by: acruhl - 07-09-2023, 05:07 PM - Forum: Linux on Pinebook Pro
- Replies (2)
|
 |
Does anyone know if it's possible to upgrade Fedora from 37 to 38? I'm running Fedora 37 on an SD card. It's slow but it works.
The built in software manager GUI gives me an error when it tries to upgrade.
I'll read up on the CLI method. I'm asking in case it isn't possible in this particular case or if someone has experience with it.
Thanks!
|
|
|
|
|