<![CDATA[PINE64 - PineTab Hardware]]> https://forum.pine64.org/ Wed, 11 Nov 2026 13:41:40 +0000 MyBB <![CDATA[Login issues]]> https://forum.pine64.org/showthread.php?tid=20388 Fri, 16 Oct 2026 14:13:42 +0000 Corkonian]]> https://forum.pine64.org/showthread.php?tid=20388 I ran a packman -Syu yesterday and today I can't log into my PinteTab2 anymore. Well, at least not on the graphic login screen.
My user and password gets rejected and alarm with the standard 123456 gets rejected, too.
BUT I can log into the tty console using alt+tab+f3
Yes, I did change my password using passwd in the tty to a very simple 1234
Yes, I did reboot
No, I still can't log into the graphical console.

WTF?]]> I ran a packman -Syu yesterday and today I can't log into my PinteTab2 anymore. Well, at least not on the graphic login screen.
My user and password gets rejected and alarm with the standard 123456 gets rejected, too.
BUT I can log into the tty console using alt+tab+f3
Yes, I did change my password using passwd in the tty to a very simple 1234
Yes, I did reboot
No, I still can't log into the graphical console.

WTF?]]> <![CDATA[Unknown Startup Password for Newly Delivered PINETAB-V - 10.1" 8GB/128GB]]> https://forum.pine64.org/showthread.php?tid=20382 Sat, 03 Oct 2026 08:22:19 +0000 krupine2]]> https://forum.pine64.org/showthread.php?tid=20382
When I turned it on, a GNOME desktop appeared; I didn't have to enter a password or make any other inputs. I was automatically logged in as a user named “user” (uid=1000). This user is a member of the ‘sudo’ group (gid 27), but I cannot execute privileged commands because I do not have the password for “user.” There are no other users with uids greater than 1000.

The hostname is “starfive.” The preinstalled distribution is Debian GNU/Linux bookworm/sid. The /etc/apt/sources.list file contains only one entry: https://snapshot.debian.org/archive/debi...25T084846Z unstable main

I’ve tried the following passwords: blank, 1234, 12345, 123456, 1234567, 12345678, 123456789, changeme, ChangeMe, debian, pinetab, pinetab2. None of them work.

So far, I haven’t been able to find anything in the wiki. General web searches haven’t turned up anything useful. What have I overlooked? I’m now turning to this forum for help.

Andreas]]>
When I turned it on, a GNOME desktop appeared; I didn't have to enter a password or make any other inputs. I was automatically logged in as a user named “user” (uid=1000). This user is a member of the ‘sudo’ group (gid 27), but I cannot execute privileged commands because I do not have the password for “user.” There are no other users with uids greater than 1000.

The hostname is “starfive.” The preinstalled distribution is Debian GNU/Linux bookworm/sid. The /etc/apt/sources.list file contains only one entry: https://snapshot.debian.org/archive/debi...25T084846Z unstable main

I’ve tried the following passwords: blank, 1234, 12345, 123456, 1234567, 12345678, 123456789, changeme, ChangeMe, debian, pinetab, pinetab2. None of them work.

So far, I haven’t been able to find anything in the wiki. General web searches haven’t turned up anything useful. What have I overlooked? I’m now turning to this forum for help.

Andreas]]> <![CDATA[Default password]]> https://forum.pine64.org/showthread.php?tid=20355 Thu, 20 Aug 2026 11:02:27 +0000 dissimilar_goose]]> https://forum.pine64.org/showthread.php?tid=20355
The username alarm is the one it wants me to log in to but none of the passwords I've tried have worked]]>
The username alarm is the one it wants me to log in to but none of the passwords I've tried have worked]]> <![CDATA[PineTab2 spec for ddr and]]> https://forum.pine64.org/showthread.php?tid=20114 Wed, 10 Dec 2025 02:28:13 +0000 rth]]> https://forum.pine64.org/showthread.php?tid=20114
I use this guide  https://forum.pine64.org/showthread.php?tid=7992 with some modifications.
However, it fails on step 2 - building atf. Without it, U-Boot returns an error
Code:
[alarm@danctnix u-boot]$ make pinetab2-rk3566_defconfig   # # configuration written to .config # [alarm@danctnix u-boot]$ make -j 4 scripts/kconfig/conf  --syncconfig Kconfig CFG     u-boot.cfg GEN     include/autoconf.mk.dep CFG     spl/u-boot.cfg GEN     include/autoconf.mk GEN     spl/include/autoconf.mk UPD     include/generated/timestamp_autogenerated.h ENVC    include/generated/env.txt ENVP    include/generated/env.in ENVT    include/generated/environment.h LDS     u-boot.lds CC      common/version.o AR      common/built-in.a CC      env/common.o AR      env/built-in.a LD      u-boot OBJCOPY u-boot.srec OBJCOPY u-boot-nodtb.bin RELOC   u-boot-nodtb.bin SYM     u-boot.sym CAT     u-boot-dtb.bin MKIMAGE u-boot.img MKIMAGE u-boot-dtb.img COPY    u-boot.bin CC      spl/common/spl/spl.o AR      spl/common/spl/built-in.a LD      spl/u-boot-spl OBJCOPY spl/u-boot-spl-nodtb.bin SYM     spl/u-boot-spl.sym CAT     spl/u-boot-spl-dtb.bin COPY    spl/u-boot-spl.bin BINMAN  .binman_stamp [b]Image 'simple-bin' is missing external blobs and is non-functional: rockchip-tpl atf-bl31[/b]                                                                                                                                                                                                                               /binman/simple-bin/mkimage/rockchip-tpl (rockchip-tpl):  An external TPL is required to initialize DRAM. Get the external TPL  binary and build with ROCKCHIP_TPL=/path/to/ddr.bin. One possible source  for the external TPL binary is https://github.com/rockchip-linux/rkbin. /binman/simple-bin/fit/images/@atf-SEQ/atf-bl31 (atf-bl31):  See the documentation for your board. You may need to build ARM Trusted  Firmware and build with BL31=/path/to/bl31.bin [b]Image 'simple-bin' has faked external blobs and is non-functional: rockchip-tpl[/b]                                                                                                                                                                                                                               [b]Image 'simple-bin' is missing optional external blobs but is still functional: tee-os[/b]                                                                                                                                                                                                                               /binman/simple-bin/fit/images/@tee-SEQ/tee-os (tee-os):  See the documentation for your board. You may need to build Open Portable  Trusted Execution Environment (OP-TEE) and build with TEE=/path/to/tee.bin [b]Image 'simple-bin-spi' is missing external blobs and is non-functional: rockchip-tpl atf-bl31[/b]                                                                                                                                                                                                                               /binman/simple-bin-spi/mkimage/rockchip-tpl (rockchip-tpl):  An external TPL is required to initialize DRAM. Get the external TPL  binary and build with ROCKCHIP_TPL=/path/to/ddr.bin. One possible source  for the external TPL binary is https://github.com/rockchip-linux/rkbin. /binman/simple-bin-spi/fit/images/@atf-SEQ/atf-bl31 (atf-bl31):  See the documentation for your board. You may need to build ARM Trusted  Firmware and build with BL31=/path/to/bl31.bin [b]Image 'simple-bin-spi' has faked external blobs and is non-functional: rockchip-tpl[/b]                                                                                                                                                                                                                               [b]Image 'simple-bin-spi' is missing optional external blobs but is still functional: tee-os[/b]                                                                                                                                                                                                                               /binman/simple-bin-spi/fit/images/@tee-SEQ/tee-os (tee-os):  See the documentation for your board. You may need to build Open Portable  Trusted Execution Environment (OP-TEE) and build with TEE=/path/to/tee.bin [b]Some images are invalid[/b] make: *** [Makefile:1339: .binman_stamp] Error 103
Well, now I'm looking at https://github.com/rockchip-linux/rkbin repository, and there are lots of options there for the TPL
Code:
ls rkbin/bin/rk35/rk3566* rkbin/bin/rk35/rk3566_ddr_1056MHz_D3_LP3_eyescan_v1.23.bin   rkbin/bin/rk35/rk3566_ddr_1056MHz_ultra_v1.20.bin rkbin/bin/rk35/rk3566_ddr_528MHz_ultra_v1.10.bin rkbin/bin/rk35/rk3566_ddr_920MHz_ultra_v1.10.bin rkbin/bin/rk35/rk3566_ddr_1056MHz_D4_LP4_4x_eyescan_v1.23.bin rkbin/bin/rk35/rk3566_ddr_1056MHz_v1.23.bin rkbin/bin/rk35/rk3566_ddr_780MHz_ultra_v1.10.bin rkbin/bin/rk35/rk3566_ddr_920MHz_v1.23.bin
Does anyone know what the DDR frequency is on the PineTab2?
Another question.
There is no bl31 for rk3566 in https://github.com/rockchip-linux/rkbin. However, according to https://github.com/ARM-software/arm-trus...st?plain=1 rk3566 and rk3568 are the same for bl31. Is that right?
Can I use rk3568_bl31_v1.45.elf to build u-boot for rk3566?

Don't laugh too hard, I'm new on that   Smile]]>
I use this guide  https://forum.pine64.org/showthread.php?tid=7992 with some modifications.
However, it fails on step 2 - building atf. Without it, U-Boot returns an error
Code:
[alarm@danctnix u-boot]$ make pinetab2-rk3566_defconfig   # # configuration written to .config # [alarm@danctnix u-boot]$ make -j 4 scripts/kconfig/conf  --syncconfig Kconfig CFG     u-boot.cfg GEN     include/autoconf.mk.dep CFG     spl/u-boot.cfg GEN     include/autoconf.mk GEN     spl/include/autoconf.mk UPD     include/generated/timestamp_autogenerated.h ENVC    include/generated/env.txt ENVP    include/generated/env.in ENVT    include/generated/environment.h LDS     u-boot.lds CC      common/version.o AR      common/built-in.a CC      env/common.o AR      env/built-in.a LD      u-boot OBJCOPY u-boot.srec OBJCOPY u-boot-nodtb.bin RELOC   u-boot-nodtb.bin SYM     u-boot.sym CAT     u-boot-dtb.bin MKIMAGE u-boot.img MKIMAGE u-boot-dtb.img COPY    u-boot.bin CC      spl/common/spl/spl.o AR      spl/common/spl/built-in.a LD      spl/u-boot-spl OBJCOPY spl/u-boot-spl-nodtb.bin SYM     spl/u-boot-spl.sym CAT     spl/u-boot-spl-dtb.bin COPY    spl/u-boot-spl.bin BINMAN  .binman_stamp [b]Image 'simple-bin' is missing external blobs and is non-functional: rockchip-tpl atf-bl31[/b]                                                                                                                                                                                                                               /binman/simple-bin/mkimage/rockchip-tpl (rockchip-tpl):  An external TPL is required to initialize DRAM. Get the external TPL  binary and build with ROCKCHIP_TPL=/path/to/ddr.bin. One possible source  for the external TPL binary is https://github.com/rockchip-linux/rkbin. /binman/simple-bin/fit/images/@atf-SEQ/atf-bl31 (atf-bl31):  See the documentation for your board. You may need to build ARM Trusted  Firmware and build with BL31=/path/to/bl31.bin [b]Image 'simple-bin' has faked external blobs and is non-functional: rockchip-tpl[/b]                                                                                                                                                                                                                               [b]Image 'simple-bin' is missing optional external blobs but is still functional: tee-os[/b]                                                                                                                                                                                                                               /binman/simple-bin/fit/images/@tee-SEQ/tee-os (tee-os):  See the documentation for your board. You may need to build Open Portable  Trusted Execution Environment (OP-TEE) and build with TEE=/path/to/tee.bin [b]Image 'simple-bin-spi' is missing external blobs and is non-functional: rockchip-tpl atf-bl31[/b]                                                                                                                                                                                                                               /binman/simple-bin-spi/mkimage/rockchip-tpl (rockchip-tpl):  An external TPL is required to initialize DRAM. Get the external TPL  binary and build with ROCKCHIP_TPL=/path/to/ddr.bin. One possible source  for the external TPL binary is https://github.com/rockchip-linux/rkbin. /binman/simple-bin-spi/fit/images/@atf-SEQ/atf-bl31 (atf-bl31):  See the documentation for your board. You may need to build ARM Trusted  Firmware and build with BL31=/path/to/bl31.bin [b]Image 'simple-bin-spi' has faked external blobs and is non-functional: rockchip-tpl[/b]                                                                                                                                                                                                                               [b]Image 'simple-bin-spi' is missing optional external blobs but is still functional: tee-os[/b]                                                                                                                                                                                                                               /binman/simple-bin-spi/fit/images/@tee-SEQ/tee-os (tee-os):  See the documentation for your board. You may need to build Open Portable  Trusted Execution Environment (OP-TEE) and build with TEE=/path/to/tee.bin [b]Some images are invalid[/b] make: *** [Makefile:1339: .binman_stamp] Error 103
Well, now I'm looking at https://github.com/rockchip-linux/rkbin repository, and there are lots of options there for the TPL
Code:
ls rkbin/bin/rk35/rk3566* rkbin/bin/rk35/rk3566_ddr_1056MHz_D3_LP3_eyescan_v1.23.bin   rkbin/bin/rk35/rk3566_ddr_1056MHz_ultra_v1.20.bin rkbin/bin/rk35/rk3566_ddr_528MHz_ultra_v1.10.bin rkbin/bin/rk35/rk3566_ddr_920MHz_ultra_v1.10.bin rkbin/bin/rk35/rk3566_ddr_1056MHz_D4_LP4_4x_eyescan_v1.23.bin rkbin/bin/rk35/rk3566_ddr_1056MHz_v1.23.bin rkbin/bin/rk35/rk3566_ddr_780MHz_ultra_v1.10.bin rkbin/bin/rk35/rk3566_ddr_920MHz_v1.23.bin
Does anyone know what the DDR frequency is on the PineTab2?
Another question.
There is no bl31 for rk3566 in https://github.com/rockchip-linux/rkbin. However, according to https://github.com/ARM-software/arm-trus...st?plain=1 rk3566 and rk3568 are the same for bl31. Is that right?
Can I use rk3568_bl31_v1.45.elf to build u-boot for rk3566?

Don't laugh too hard, I'm new on that   Smile]]> <![CDATA[cracked screen and repair]]> https://forum.pine64.org/showthread.php?tid=19724 Fri, 07 Mar 2025 19:40:38 +0000 elix]]> https://forum.pine64.org/showthread.php?tid=19724
i have a crack in my pinetab2 (thanks cat) and I am admittedly horrible at hardware.
can i purchase a replacement screen and is there anyone in the DC area who would be able to help me replace it?

if not, is there somewhere i can send it to be repaired?

gonna send an email to support but wanted to reach out here too.

thanks!]]>
i have a crack in my pinetab2 (thanks cat) and I am admittedly horrible at hardware.
can i purchase a replacement screen and is there anyone in the DC area who would be able to help me replace it?

if not, is there somewhere i can send it to be repaired?

gonna send an email to support but wanted to reach out here too.

thanks!]]> <![CDATA[What is the state of the PineTab2 today?]]> https://forum.pine64.org/showthread.php?tid=19538 Sun, 01 Dec 2024 20:04:01 +0000 Arcikks]]> https://forum.pine64.org/showthread.php?tid=19538 <![CDATA[A big Incentive to choose RISC-V, when Dinosaurs Die Mammals Emerge]]> https://forum.pine64.org/showthread.php?tid=19474 Wed, 23 Oct 2024 09:49:18 +0000 biketool]]> https://forum.pine64.org/showthread.php?tid=19474 https://www.windowscentral.com/microsoft...e-oct-2024
"A new report suggests that Arm Holdings PLC is ending its contract with Qualcomm Inc. which allows the firm to build chip designs based on Arm technology."
While Qualcom and ARM fight will we see an opening forRISC-V emerge as a safer option for large businesses?
Can RISC-V and open source hardware became the low risk option like Linux and other FOSS has?
The Qualcom vs ARM dispute will end up settled in court, this is a legal chess manuver between ARM and it's largest customer who in an IP license 'legal hack' attempt acquired another company to use a more favorable license, but this is an opportunity in a time of instability for CPU hardware alternatives to be discussed not unlike how Crowdstrike outage darkened the reputation of Microsoft windows vs FOSS alternatives as platforms for business.]]> https://www.windowscentral.com/microsoft...e-oct-2024
"A new report suggests that Arm Holdings PLC is ending its contract with Qualcomm Inc. which allows the firm to build chip designs based on Arm technology."
While Qualcom and ARM fight will we see an opening forRISC-V emerge as a safer option for large businesses?
Can RISC-V and open source hardware became the low risk option like Linux and other FOSS has?
The Qualcom vs ARM dispute will end up settled in court, this is a legal chess manuver between ARM and it's largest customer who in an IP license 'legal hack' attempt acquired another company to use a more favorable license, but this is an opportunity in a time of instability for CPU hardware alternatives to be discussed not unlike how Crowdstrike outage darkened the reputation of Microsoft windows vs FOSS alternatives as platforms for business.]]> <![CDATA[The built-in camera cannot be found.]]> https://forum.pine64.org/showthread.php?tid=19344 Sun, 14 Jul 2024 08:44:26 +0000 dl8aax]]> https://forum.pine64.org/showthread.php?tid=19344 I bought the Pinetab2 to manage my bees at the apiary. For this I need the built-in camera.

Unfortunately the built-in camera cannot be found.


Code:
[alarm@danctnix ~]$ mpv av://v4l2:/dev/video0 [ffmpeg/demuxer] video4linux2,v4l2: Not a video capture device. [lavf] avformat_open_input() failed Failed to recognize file format. Exiting... (Errors when loading file) [alarm@danctnix ~]$

(sorry for my English, I'm translating with Google)


greetings, Dirk]]> I bought the Pinetab2 to manage my bees at the apiary. For this I need the built-in camera.

Unfortunately the built-in camera cannot be found.


Code:
[alarm@danctnix ~]$ mpv av://v4l2:/dev/video0 [ffmpeg/demuxer] video4linux2,v4l2: Not a video capture device. [lavf] avformat_open_input() failed Failed to recognize file format. Exiting... (Errors when loading file) [alarm@danctnix ~]$

(sorry for my English, I'm translating with Google)


greetings, Dirk]]> <![CDATA[Accidentally Erased internal SD memory]]> https://forum.pine64.org/showthread.php?tid=19275 Sun, 09 Jun 2024 18:24:13 +0000 Bandschaaf]]> https://forum.pine64.org/showthread.php?tid=19275
Unfortunately, I made a mistake while trying to install a new operating system on my PineTab and accidentally erased the BIOS (UEFI). Here are the details of what happened:

What Happened:
  • I was in the process of installing a new operating system on my PineTab and inadvertently followed the wrong steps, resulting in the internal drive, including the BIOS, being completely wiped.
  • The device now fails to boot, and I have no access to the BIOS to attempt to troubleshoot the issue.
What I've Tried:
  • I attempted to boot the device from a bootable SD card, but without success.
  • I also tried starting into MASKROM mode, to no avail. (the adapter shows lights, so it is active)


Any suggestions, tips, or guidance would be greatly appreciated. Thank you in advance for your assistance!]]>
Unfortunately, I made a mistake while trying to install a new operating system on my PineTab and accidentally erased the BIOS (UEFI). Here are the details of what happened:

What Happened:
  • I was in the process of installing a new operating system on my PineTab and inadvertently followed the wrong steps, resulting in the internal drive, including the BIOS, being completely wiped.
  • The device now fails to boot, and I have no access to the BIOS to attempt to troubleshoot the issue.
What I've Tried:
  • I attempted to boot the device from a bootable SD card, but without success.
  • I also tried starting into MASKROM mode, to no avail. (the adapter shows lights, so it is active)


Any suggestions, tips, or guidance would be greatly appreciated. Thank you in advance for your assistance!]]> <![CDATA[Progress on Wifi Chip]]> https://forum.pine64.org/showthread.php?tid=19204 Wed, 01 May 2024 16:25:08 +0000 frtodd]]> https://forum.pine64.org/showthread.php?tid=19204 https://fosstodon.org/@danctnix/112366650102862145


Quote:Greetings, #PineTab2 users!

We have pushed a new kernel (v6.8.6-danctnix2) to the repository.

The new kernel introduces the new #BES2600 community driver which works with suspend.

Power consumption is not tested.

#DanctNIX #ArchLinuxARM

I've not tried it yet, but looking forward to updating my tablet!]]> https://fosstodon.org/@danctnix/112366650102862145


Quote:Greetings, #PineTab2 users!

We have pushed a new kernel (v6.8.6-danctnix2) to the repository.

The new kernel introduces the new #BES2600 community driver which works with suspend.

Power consumption is not tested.

#DanctNIX #ArchLinuxARM

I've not tried it yet, but looking forward to updating my tablet!]]> <![CDATA[wifi with caveats]]> https://forum.pine64.org/showthread.php?tid=19027 Tue, 30 Jan 2024 22:49:30 +0000 frtodd]]> https://forum.pine64.org/showthread.php?tid=19027
This Mastodon post tells how to activate wifi with the updated driver:
https://fosstodon.org/@phundrak@emacs.ch...9643222233

WARNING: This activates the testing repo which means you get bleeding-edge updates.

In this case, the only bleeding edge I have found is that sleep mode just hangs. I have to power off the device and back on if I accidentally try to let it sleep (by, for example, closing the cover). 

So it's definitely not perfect. But it works, and works quite well in my few days of playing with it.

It makes the Pinetab a whole new device for me!]]>
This Mastodon post tells how to activate wifi with the updated driver:
https://fosstodon.org/@phundrak@emacs.ch...9643222233

WARNING: This activates the testing repo which means you get bleeding-edge updates.

In this case, the only bleeding edge I have found is that sleep mode just hangs. I have to power off the device and back on if I accidentally try to let it sleep (by, for example, closing the cover). 

So it's definitely not perfect. But it works, and works quite well in my few days of playing with it.

It makes the Pinetab a whole new device for me!]]> <![CDATA[USB hubs that work?]]> https://forum.pine64.org/showthread.php?tid=18988 Wed, 03 Jan 2024 13:19:30 +0000 draco_mike]]> https://forum.pine64.org/showthread.php?tid=18988
Thanks!]]>
Thanks!]]> <![CDATA[PineTab2, Ubuntu Touch and WiFI]]> https://forum.pine64.org/showthread.php?tid=18984 Sun, 31 Dec 2023 02:52:39 +0000 JMoore]]> https://forum.pine64.org/showthread.php?tid=18984
Oddly enough if boots from the SD card without using the UART adapter I purchased because my PT2 did not come with one. Purchased off eBay so original owner may have not seen it and accidentally discarded it.]]>
Oddly enough if boots from the SD card without using the UART adapter I purchased because my PT2 did not come with one. Purchased off eBay so original owner may have not seen it and accidentally discarded it.]]> <![CDATA[Pinetab2 Audio Hiss/Static from speakers]]> https://forum.pine64.org/showthread.php?tid=18981 Fri, 29 Dec 2023 15:32:36 +0000 scottgr]]> https://forum.pine64.org/showthread.php?tid=18981
Anyone else had this issue and resolved it?]]>
Anyone else had this issue and resolved it?]]> <![CDATA[Not able to power on PineTab anymore]]> https://forum.pine64.org/showthread.php?tid=18970 Mon, 25 Dec 2023 20:31:48 +0000 zkajdan]]> https://forum.pine64.org/showthread.php?tid=18970
After finally getting my pinetab connected to wifi, I ran

Code:
sudo pacman -Syu


for the first time, and suddenly during the update I got a big message

Code:
This screen locker is broken and unlocking it is not possible...


and from there on, the pinetab did not react to anything anymore...
I tried to restart it, but after it had successfully been powered off, I've not been able to power it on anymore... It just stays dark.
I've also tried connecting to the laptop via the UART console, to see if it's just the display - but I don't see anything in a screen terminal either.

I have no idea what to do, since I can't re-install without somehow switching it on...

Would anyone have an idea what to do? Many thanks!!]]>
After finally getting my pinetab connected to wifi, I ran

Code:
sudo pacman -Syu


for the first time, and suddenly during the update I got a big message

Code:
This screen locker is broken and unlocking it is not possible...


and from there on, the pinetab did not react to anything anymore...
I tried to restart it, but after it had successfully been powered off, I've not been able to power it on anymore... It just stays dark.
I've also tried connecting to the laptop via the UART console, to see if it's just the display - but I don't see anything in a screen terminal either.

I have no idea what to do, since I can't re-install without somehow switching it on...

Would anyone have an idea what to do? Many thanks!!]]>