<![CDATA[PINE64 - PineTab Software]]>

<![CDATA[PINE64 - PineTab Software]]> https://forum.pine64.org/ Thu, 07 May 2026 10:55:26 +0000 MyBB <![CDATA[RISC OS Linux port]]> https://forum.pine64.org/showthread.php?tid=20203 Thu, 26 Feb 2026 11:40:56 +0000 Raik]]> https://forum.pine64.org/showthread.php?tid=20203
[Image: ROS_PineTab2.jpg]

You can download from PyraDirect . The collection I have made for the Pyra handheld based on ROD's PiDirect but works fine on PineTab.

It need base-devel as dependencies (e.g. sudo pacman -Sy base-devel)

Unpack the download in Terminal with

tar —xattrs -xvf Downloads/pyra_direct.tar.gz

to your home directory. It takes a while.

Then in Terminal…

Dir RISC_OS

./run_RISC_OS

The first start takes a bit longer.]]> <![CDATA[Systemupgrade fails]]> https://forum.pine64.org/showthread.php?tid=20202 Thu, 26 Feb 2026 05:15:53 +0000 Raik]]> https://forum.pine64.org/showthread.php?tid=20202 With CTRL+ALT+F2 I can enter the Terminal. My account is working but no network and "startx" fails.

I have try to install the available actualization in discovery and later, after a "factory reset", in terminal "sudo pacman -Syu". All the same.
After the actualization e.g. freecad, musescore are working (before only installing possible) but after a restart... next "factory reset".

Any ideas?]]> With CTRL+ALT+F2 I can enter the Terminal. My account is working but no network and "startx" fails.

I have try to install the available actualization in discovery and later, after a "factory reset", in terminal "sudo pacman -Syu". All the same.
After the actualization e.g. freecad, musescore are working (before only installing possible) but after a restart... next "factory reset".

Any ideas?]]> <![CDATA[New Pinetab- error when attempting to install updates]]> https://forum.pine64.org/showthread.php?tid=20189 Mon, 09 Feb 2026 02:19:59 +0000 authorjaw]]> https://forum.pine64.org/showthread.php?tid=20189
But...I can't seem to get updates to install- have searched the web for solutions including "sudo pacman -Syu" and related variations, but no matter what do I keep getting the following error:

"Dependency resolution failed:

libavcodec.so (followed by string of info)
libswrsample.so (followed by string of info)
libicuuc,so (followed by string of info)

Not being a dev I'm stuck at how to correct this issue- does anyone know of a solution?

Thanks!]]>
But...I can't seem to get updates to install- have searched the web for solutions including "sudo pacman -Syu" and related variations, but no matter what do I keep getting the following error:

"Dependency resolution failed:

libavcodec.so (followed by string of info)
libswrsample.so (followed by string of info)
libicuuc,so (followed by string of info)

Not being a dev I'm stuck at how to correct this issue- does anyone know of a solution?

Thanks!]]> <![CDATA[IMHO, a really NICE update to danctnix yesterday]]> https://forum.pine64.org/showthread.php?tid=20176 Thu, 22 Jan 2026 14:55:50 +0000 iksar@gmx.com]]> https://forum.pine64.org/showthread.php?tid=20176
both mpv and browsers got a HUGE speed boost, with almost perfect video playback.

I would further recommend

Code:
alias mpv='mpv --vo=gpu --gpu-api=opengl'

and a script for thorium (downloaded from website). ( assuming you're using sway)

Code:
#!/bin/bash

dbus-launch $HOME/devel/apps/thorium/thorium \

    --use-gl=egl-angle \

    --ignore-gpu-blocklist \

    --enable-gpu-rasterization \

    --enable-accelerated-video-decode \

    --enable-features=VaapiVideoDecodeLinuxGL,VaapiVideoEncoder \

    --ozone-platform=wayland

Code:
lsmod | grep pan

panfrost 

drm_shmem_helper --------panfrost

gpu_sched -             -------panfrost

]]>
both mpv and browsers got a HUGE speed boost, with almost perfect video playback.

I would further recommend

Code:
alias mpv='mpv --vo=gpu --gpu-api=opengl'

and a script for thorium (downloaded from website). ( assuming you're using sway)

Code:
#!/bin/bash

dbus-launch $HOME/devel/apps/thorium/thorium \

    --use-gl=egl-angle \

    --ignore-gpu-blocklist \

    --enable-gpu-rasterization \

    --enable-accelerated-video-decode \

    --enable-features=VaapiVideoDecodeLinuxGL,VaapiVideoEncoder \

    --ozone-platform=wayland

Code:
lsmod | grep pan

panfrost 

drm_shmem_helper --------panfrost

gpu_sched -             -------panfrost

]]> <![CDATA[Is Danctnix about to get cameras on Pinetab2]]> https://forum.pine64.org/showthread.php?tid=20116 Thu, 11 Dec 2025 12:19:54 +0000 biketool]]> https://forum.pine64.org/showthread.php?tid=20116 Are we close to getting working cameras on our Danctnix Pinetab2s?]]> Are we close to getting working cameras on our Danctnix Pinetab2s?]]> <![CDATA[Danctnix USB GPS for Pinetab2]]> https://forum.pine64.org/showthread.php?tid=20094 Fri, 28 Nov 2025 12:09:04 +0000 biketool]]> https://forum.pine64.org/showthread.php?tid=20094

Code:
Bus 003 Device 004: ID 1163:0200 DeLorme Publishing, Inc. Earthmate GPS (LT-20, LT-40)

Danctnixfor the Pinephone and PPpro I assume have working GPS and mapping that attach to the USB device generated by the modem package.
If that is the case what packages sould I Syu or flatpak onto a Pinetab2 to get this setup so I can have bigger screen navigation with the GPS receiver suction cupped to the window vs inside the device?
(edit)
It seems like there is a problem with the cypress_m8 driver since around it's introduction in 2005 so it requires a kernel patch to receive the NEMA feed see 1 & 3.
1 - https://linux-usb-devel.narkive.com/sz0J...s-m8-patch#
2 - https://github.com/torvalds/linux/blob/m...press_m8.c
3 - https://bugs.launchpad.net/bugs/111694

3 uses a fix referred to in 1 though this seems to be sub-optimal commenting out this line and recompiling

Code:
cypress_set_dead(port);

I had found these Delorne Earthmate dongles on the auction site for $5 each.
(it makes me wonder if a hardware hack with a new soldered in usb-serial adapter to the NEMA output might be easier)]]>

Code:
Bus 003 Device 004: ID 1163:0200 DeLorme Publishing, Inc. Earthmate GPS (LT-20, LT-40)

Code:
cypress_set_dead(port);

I had found these Delorne Earthmate dongles on the auction site for $5 each.
(it makes me wonder if a hardware hack with a new soldered in usb-serial adapter to the NEMA output might be easier)]]> <![CDATA[Old Danctnix server in Pacman Config (solved)]]> https://forum.pine64.org/showthread.php?tid=20087 Wed, 19 Nov 2025 20:20:35 +0000 KelsonV]]> https://forum.pine64.org/showthread.php?tid=20087
The old danctnix server name at p64.arikawa-hi.me appears to have expired. I went looking and confirmed that it expired 2 years ago and was renewed at the time, and that archmobile.mirror.danctnix.org is the valid new server name. After updating /etc/pacman.conf to point to the new server, I was able to sync successfully again.]]>
The old danctnix server name at p64.arikawa-hi.me appears to have expired. I went looking and confirmed that it expired 2 years ago and was renewed at the time, and that archmobile.mirror.danctnix.org is the valid new server name. After updating /etc/pacman.conf to point to the new server, I was able to sync successfully again.]]> <![CDATA[Pinetab2s running DanctNIX just got Bluetooth!!]]> https://forum.pine64.org/showthread.php?tid=20060 Sun, 02 Nov 2025 10:45:52 +0000 biketool]]> https://forum.pine64.org/showthread.php?tid=20060 Try it out, Bluetooth is now active for me, paired my BT mouse and it works!

No cameras yet...
I am also trying to get a USB NMEA receiver to work for in-car navigation.
_____________________________

So this will allow use of bluetooth stylus as a touch mouse with left-click now?
If so which styluses are compatible?
________________________
is this driver/hardware currently compatible with BT-low energy?]]> Try it out, Bluetooth is now active for me, paired my BT mouse and it works!

No cameras yet...
I am also trying to get a USB NMEA receiver to work for in-car navigation.
_____________________________

So this will allow use of bluetooth stylus as a touch mouse with left-click now?
If so which styluses are compatible?
________________________
is this driver/hardware currently compatible with BT-low energy?]]> <![CDATA[auto-owning the SD card in DanctNIX (Pinetab2)]]> https://forum.pine64.org/showthread.php?tid=20032 Thu, 09 Oct 2025 11:55:34 +0000 biketool]]> https://forum.pine64.org/showthread.php?tid=20032 I have it auto mounting the SD card using settings but because user alarm doesn't own the SD card device/mount point I cant use it normally.
I could chown it but that would have to happen every bootup.
(edit) I will probably edit /etc/fstab but that is skill learned maybe 25 years ago and I expect that in systemb days there is probably something automatic and I dont want to break that.

I have not wiped and loaded Mobian despite using that for my Pinephone there doesnt seem to be enough clear instruction to get everything working, it feels like the shipped DanctNIX OS has the most functionality.

That said I would in any fully Linux OS really love to have the bluetooth and cameras fully functional as well as a smart way to setup a NMEA USB GPS device for navigation.]]> I have it auto mounting the SD card using settings but because user alarm doesn't own the SD card device/mount point I cant use it normally.
I could chown it but that would have to happen every bootup.
(edit) I will probably edit /etc/fstab but that is skill learned maybe 25 years ago and I expect that in systemb days there is probably something automatic and I dont want to break that.

I have not wiped and loaded Mobian despite using that for my Pinephone there doesnt seem to be enough clear instruction to get everything working, it feels like the shipped DanctNIX OS has the most functionality.

That said I would in any fully Linux OS really love to have the bluetooth and cameras fully functional as well as a smart way to setup a NMEA USB GPS device for navigation.]]> <![CDATA[USB Gadget on PineTab2]]> https://forum.pine64.org/showthread.php?tid=20017 Fri, 26 Sep 2025 18:42:51 +0000 Tronar]]> https://forum.pine64.org/showthread.php?tid=20017
has anybody of you tried to get a USB gadget working for the second USB interface on the PineTab2? This is a fully functional OTG interface that you can use for much more than only charging. Anyway, as long as you don't connect an OTG cable, it will reside in device mode, so it should be possible to program USB gadgets following such instructions:
https://openwrt.org/docs/guide-user/hardware/usb_gadget
https://trac.gateworks.com/wiki/linux/OTG
https://developer.toradex.com/linux-bsp/...ode-linux/
https://www.kernel.org/doc/Documentation...nfigfs.txt
https://github.com/torvalds/linux/blob/m...usb-gadget
Based on these (and some other web sites) I contrived a script for a mass storage gadget. First I prepared an 8 GB big container file using these commands:

Code:
dd if=/dev/zero of=/stick.img bs=1M count=8192

fdisk /stick.img

# Inside fdisk I prepared the image using the following keys:

# o x s 32 h 128 c 4096 r n p 1 \n \n t c p w

losetup -o 1M /dev/loop0 /stick.img

mkfs.vfat /dev/loop0

mount -t vfat /dev/loop0 /mnt

echo hallo >/mnt/test.txt

umount /mnt

losetup -d /dev/loop0

The following script intends to simulate a USB stick on the device mode USB port:

Code:
#!/bin/sh

cd /sys/kernel/config/usb_gadget

mkdir g1

sleep 1

cd g1

echo 0x1d6b >idVendor  # reserved for the Linux Foundation

echo 0x0104 >idProduct  # multifunction is sufficient

#echo 0x0615 > bcdDevice  This is preset for some reason.

echo 0x0200 > bcdUSB    # USB 2.0

# Is the following correct for a flash stick?

echo 0x08 > bDeviceClass

echo 0x06 > bDeviceSubClass

echo 0x80 > bDeviceProtocol

#echo 0x62 > bDeviceProtocol

echo 0x40 >bMaxPacketSize0

echo high-speed >max_speed

# The following strings can be chosen freely; for the serial number I take the

# actual SN of my PineTab2.

cd strings

mkdir 0x409 && cd 0x409

sleep 1

cat /proc/device-tree/serial-number >serialnumber

echo Pine64 >manufacturer

echo PineTab2\ v2.0 >product

# Alternatively one could also use some of the information in

# /sys/bus/i2c/drivers/husb311/0-004e to fill in the above.

cd ../../configs

mkdir c.1 && cd c.1

sleep 1

mkdir strings/0x409

sleep 1

echo "Memory stick emulation based on image file" >strings/0x409/configuration

# German:

mkdir strings/0x407

sleep 1

echo "Speicherstick-Emulation mit einer Image-Datei" >strings/0x407/configuration

echo 0xc0 >bmAttributes  # self-powered

echo 2 >MaxPower        # probably irrelevant when self-powered

cd ../../functions

mkdir mass_storage.usb0

sleep 1

cd mass_storage.usb0

echo 1 >stall

cd lun.0

echo /stick.img >file

echo 0 >removable

echo 1 >nofua

cd ../../..

ln -s functions/mass_storage.usb0 configs/c.1

sleep 1

# and now make it active:

ls /sys/class/udc >UDC

# to unbind it: echo "" >UDC; sleep 1; cd ..; rm -rf g1

# in emergency: echo 1 >functions/mass_storage.usb0/lun.0/forced_eject

Several of these settings are not absolutely necessary, also the sleep statements; they reflect only my desperate attempts to get it working. When I execute it, not having anything connected to the USB port yet, I see these lines in my dmesg:

Code:
Mass Storage Function, version: 2009/09/11

LUN: removable file: (no medium)

dwc3 fcc00000.usb: failed to enable ep0out

Why "removable"? Why "no medium"? What exactly "failed" w.r.t. endpoint 0?

Then I connect my PineTab2 to a PC's USB-2 port, which results in four more lines in the dmesg:

Code:
typec-extcon typec-extcon: extcon changed sdp=1 cdp=0 dcp=0 usb=0 usb_host=0 dp=0

typec-extcon typec-extcon: extcon changed sdp=1 cdp=0 dcp=0 usb=1 usb_host=0 dp=0

typec-extcon typec-extcon: extcon changed sdp=1 cdp=0 dcp=0 usb=0 usb_host=0 dp=0

typec-extcon typec-extcon: extcon changed sdp=1 cdp=0 dcp=0 usb=1 usb_host=0 dp=0

The dmesg of the PC is full of errors then:

Code:
usb 4-10: new high-speed USB device number 5 using xhci_hcd

usb 4-10: device descriptor read/64, error -71

usb 4-10: device descriptor read/64, error -71

usb 4-10: new high-speed USB device number 6 using xhci_hcd

usb 4-10: device descriptor read/64, error -71

usb 4-10: device descriptor read/64, error -71

usb usb4-port10: attempt power cycle

usb 4-10: new high-speed USB device number 7 using xhci_hcd

usb 4-10: Device not responding to setup address.

usb 4-10: Device not responding to setup address.

usb 4-10: device not accepting address 7, error -71

usb 4-10: new high-speed USB device number 8 using xhci_hcd

usb 4-10: Device not responding to setup address.

usb 4-10: Device not responding to setup address.

usb 4-10: device not accepting address 8, error -71

usb usb4-port10: unable to enumerate USB device

Obviously the gadget isn't functional. When I unplug the cable again, the PC's dmesg shows nothing, the PineTab2's just the ususal extcon stuff:

Code:
typec-extcon typec-extcon: extcon changed sdp=1 cdp=0 dcp=0 usb=0 usb_host=0 dp=0

typec-extcon typec-extcon: extcon changed sdp=0 cdp=0 dcp=0 usb=0 usb_host=0 dp=0

The worst thing I observe when I try to switch off the gadget again using echo "" >UDC; it seems to be some kind of crash:

Code:
dwc3 fcc00000.usb: wait for SETUP phase timed out

dwc3 fcc00000.usb: failed to set STALL on ep0out

------------[ cut here ]------------

WARNING: CPU: 0 PID: 5177 at dwc3_ep0_out_start+0xc8/0xe0

Modules linked in: aes_ce_ccm snd_seq_dummy snd_hrtimer snd_seq snd_seq_device zram aes_ce_blk aes_ce_cipher polyval_ce polyval_generic ghash_ce bes2600(C) sm4 sha2_ce sha256_arm64 sha1_ce snd_soc_simple_amplifier mac80211 st_accel_i2c st_sensors_i2c libarc4 ov5648 st_accel st_sensors v4l2_fwnode dw9714 snd_soc_simple_card v4l2_async cfg80211 snd_soc_simple_card_utils phy_rockchip_inno_csidphy snd_soc_rockchip_i2s_tdm snd_soc_rk817 rfkill snd_soc_hdmi_codec snd_soc_core snd_pcm_dmaengine snd_pcm snd_timer hantro_vpu snd v4l2_vp9 v4l2_jpeg v4l2_h264 rockchip_rga videobuf2_dma_contig soundcore v4l2_mem2mem videobuf2_dma_sg videobuf2_memops videobuf2_v4l2 videodev videobuf2_common mc joydev mousedev sch_fq_codel crypto_user loop fuse nfnetlink ip_tables x_tables ipv6 crc_ccitt dw_hdmi_cec panfrost dw_hdmi_i2s_audio drm_shmem_helper gpu_sched hid_multitouch

CPU: 0 UID: 0 PID: 5177 Comm: bash Tainted: G        C          6.15.2-danctnix2-1-pinetab2 #1 PREEMPT(full)  2075623fc0cc7105688baa1cc4ca060147351f05

[ 3357.684396] Tainted: [C]=CRAP

[ 3357.684413] Hardware name: Pine64 PineTab2 v2.0 (DT)

[ 3357.684434] pstate: 604000c9 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)

[ 3357.684464] pc : dwc3_ep0_out_start+0xc8/0xe0

[ 3357.684504] lr : dwc3_ep0_out_start+0x4c/0xe0

[ 3357.684535] sp : ffff80008778ba70

[ 3357.684552] x29: ffff80008778ba70 x28: ffff00010088b900 x27: 0000000000000000

[ 3357.684605] x26: 0000000000000000 x25: 0000000000000000 x24: ffff00013c924840

[ 3357.684655] x23: ffff0001039f0810 x22: 0000000000000000 x21: ffff000100b76990

[ 3357.684705] x20: ffff000100b76880 x19: ffff00010434f200 x18: ffff8000842730b8

[ 3357.684755] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000006

[ 3357.684804] x14: 0000000000000000 x13: ffffffffffff3f08 x12: ffff800081cd3d70

[ 3357.684854] x11: ffffffffffff3f04 x10: ffff800081cd3dc8 x9 : ffffffffffff3f00

[ 3357.684905] x8 : ffffffffffff3f0c x7 : ffff80008435d000 x6 : 0000000000000000

[ 3357.684954] x5 : ffff800081c4f000 x4 : 0000000000000000 x3 : 0000000000000000

[ 3357.685003] x2 : 0000000000000000 x1 : ffff00010088b900 x0 : 00000000ffffff92

[ 3357.685054] Call trace:

[ 3357.685073]  dwc3_ep0_out_start+0xc8/0xe0 (P)

[ 3357.685118]  dwc3_ep0_stall_and_restart+0xb4/0xe0

[ 3357.685158]  dwc3_ep0_reset_state+0x68/0xa0

[ 3357.685194]  dwc3_gadget_soft_disconnect+0x13c/0x1d0

[ 3357.685231]  dwc3_gadget_pullup+0x8c/0x138

[ 3357.685267]  usb_gadget_disconnect_locked+0x4c/0x170

[ 3357.685303]  gadget_unbind_driver+0x54/0x158

[ 3357.685334]  device_remove+0x54/0x90

[ 3357.685371]  device_release_driver_internal+0x1d4/0x240

[ 3357.685407]  driver_detach+0x54/0xc0

[ 3357.685440]  bus_remove_driver+0x78/0x108

[ 3357.685472]  driver_unregister+0x38/0x78

[ 3357.685506]  usb_gadget_unregister_driver+0x28/0x50

[ 3357.685538]  gadget_dev_desc_UDC_store+0xc0/0x150

[ 3357.685580]  configfs_write_iter+0xcc/0x130

[ 3357.685617]  vfs_write+0x24c/0x388

[ 3357.685658]  ksys_write+0x78/0x120

[ 3357.685695]  __arm64_sys_write+0x24/0x40

[ 3357.685734]  invoke_syscall+0x6c/0x100

[ 3357.685777]  el0_svc_common.constprop.0+0x48/0xf0

[ 3357.685817]  do_el0_svc+0x24/0x38

[ 3357.685846]  el0_svc+0x2c/0x138

[ 3357.685883]  el0t_64_sync_handler+0x10c/0x140

[ 3357.685916]  el0t_64_sync+0x160/0x168

[ 3357.685951] ---[ end trace 0000000000000000 ]---

Code:
dd if=/dev/zero of=/stick.img bs=1M count=8192

fdisk /stick.img

# Inside fdisk I prepared the image using the following keys:

# o x s 32 h 128 c 4096 r n p 1 \n \n t c p w

losetup -o 1M /dev/loop0 /stick.img

mkfs.vfat /dev/loop0

mount -t vfat /dev/loop0 /mnt

echo hallo >/mnt/test.txt

umount /mnt

losetup -d /dev/loop0

The following script intends to simulate a USB stick on the device mode USB port:

Code:
#!/bin/sh

cd /sys/kernel/config/usb_gadget

mkdir g1

sleep 1

cd g1

echo 0x1d6b >idVendor  # reserved for the Linux Foundation

echo 0x0104 >idProduct  # multifunction is sufficient

#echo 0x0615 > bcdDevice  This is preset for some reason.

echo 0x0200 > bcdUSB    # USB 2.0

# Is the following correct for a flash stick?

echo 0x08 > bDeviceClass

echo 0x06 > bDeviceSubClass

echo 0x80 > bDeviceProtocol

#echo 0x62 > bDeviceProtocol

echo 0x40 >bMaxPacketSize0

echo high-speed >max_speed

# The following strings can be chosen freely; for the serial number I take the

# actual SN of my PineTab2.

cd strings

mkdir 0x409 && cd 0x409

sleep 1

cat /proc/device-tree/serial-number >serialnumber

echo Pine64 >manufacturer

echo PineTab2\ v2.0 >product

# Alternatively one could also use some of the information in

# /sys/bus/i2c/drivers/husb311/0-004e to fill in the above.

cd ../../configs

mkdir c.1 && cd c.1

sleep 1

mkdir strings/0x409

sleep 1

echo "Memory stick emulation based on image file" >strings/0x409/configuration

# German:

mkdir strings/0x407

sleep 1

echo "Speicherstick-Emulation mit einer Image-Datei" >strings/0x407/configuration

echo 0xc0 >bmAttributes  # self-powered

echo 2 >MaxPower        # probably irrelevant when self-powered

cd ../../functions

mkdir mass_storage.usb0

sleep 1

cd mass_storage.usb0

echo 1 >stall

cd lun.0

echo /stick.img >file

echo 0 >removable

echo 1 >nofua

cd ../../..

ln -s functions/mass_storage.usb0 configs/c.1

sleep 1

# and now make it active:

ls /sys/class/udc >UDC

# to unbind it: echo "" >UDC; sleep 1; cd ..; rm -rf g1

# in emergency: echo 1 >functions/mass_storage.usb0/lun.0/forced_eject

Code:
Mass Storage Function, version: 2009/09/11

LUN: removable file: (no medium)

dwc3 fcc00000.usb: failed to enable ep0out

Why "removable"? Why "no medium"? What exactly "failed" w.r.t. endpoint 0?

Then I connect my PineTab2 to a PC's USB-2 port, which results in four more lines in the dmesg:

Code:
typec-extcon typec-extcon: extcon changed sdp=1 cdp=0 dcp=0 usb=0 usb_host=0 dp=0

typec-extcon typec-extcon: extcon changed sdp=1 cdp=0 dcp=0 usb=1 usb_host=0 dp=0

typec-extcon typec-extcon: extcon changed sdp=1 cdp=0 dcp=0 usb=0 usb_host=0 dp=0

typec-extcon typec-extcon: extcon changed sdp=1 cdp=0 dcp=0 usb=1 usb_host=0 dp=0

The dmesg of the PC is full of errors then:

Code:
usb 4-10: new high-speed USB device number 5 using xhci_hcd

usb 4-10: device descriptor read/64, error -71

usb 4-10: device descriptor read/64, error -71

usb 4-10: new high-speed USB device number 6 using xhci_hcd

usb 4-10: device descriptor read/64, error -71

usb 4-10: device descriptor read/64, error -71

usb usb4-port10: attempt power cycle

usb 4-10: new high-speed USB device number 7 using xhci_hcd

usb 4-10: Device not responding to setup address.

usb 4-10: Device not responding to setup address.

usb 4-10: device not accepting address 7, error -71

usb 4-10: new high-speed USB device number 8 using xhci_hcd

usb 4-10: Device not responding to setup address.

usb 4-10: Device not responding to setup address.

usb 4-10: device not accepting address 8, error -71

usb usb4-port10: unable to enumerate USB device

Obviously the gadget isn't functional. When I unplug the cable again, the PC's dmesg shows nothing, the PineTab2's just the ususal extcon stuff:

Code:
typec-extcon typec-extcon: extcon changed sdp=1 cdp=0 dcp=0 usb=0 usb_host=0 dp=0

typec-extcon typec-extcon: extcon changed sdp=0 cdp=0 dcp=0 usb=0 usb_host=0 dp=0

The worst thing I observe when I try to switch off the gadget again using echo "" >UDC; it seems to be some kind of crash:

Code:
dwc3 fcc00000.usb: wait for SETUP phase timed out

dwc3 fcc00000.usb: failed to set STALL on ep0out

------------[ cut here ]------------

WARNING: CPU: 0 PID: 5177 at dwc3_ep0_out_start+0xc8/0xe0

Modules linked in: aes_ce_ccm snd_seq_dummy snd_hrtimer snd_seq snd_seq_device zram aes_ce_blk aes_ce_cipher polyval_ce polyval_generic ghash_ce bes2600(C) sm4 sha2_ce sha256_arm64 sha1_ce snd_soc_simple_amplifier mac80211 st_accel_i2c st_sensors_i2c libarc4 ov5648 st_accel st_sensors v4l2_fwnode dw9714 snd_soc_simple_card v4l2_async cfg80211 snd_soc_simple_card_utils phy_rockchip_inno_csidphy snd_soc_rockchip_i2s_tdm snd_soc_rk817 rfkill snd_soc_hdmi_codec snd_soc_core snd_pcm_dmaengine snd_pcm snd_timer hantro_vpu snd v4l2_vp9 v4l2_jpeg v4l2_h264 rockchip_rga videobuf2_dma_contig soundcore v4l2_mem2mem videobuf2_dma_sg videobuf2_memops videobuf2_v4l2 videodev videobuf2_common mc joydev mousedev sch_fq_codel crypto_user loop fuse nfnetlink ip_tables x_tables ipv6 crc_ccitt dw_hdmi_cec panfrost dw_hdmi_i2s_audio drm_shmem_helper gpu_sched hid_multitouch

CPU: 0 UID: 0 PID: 5177 Comm: bash Tainted: G        C          6.15.2-danctnix2-1-pinetab2 #1 PREEMPT(full)  2075623fc0cc7105688baa1cc4ca060147351f05

[ 3357.684396] Tainted: [C]=CRAP

[ 3357.684413] Hardware name: Pine64 PineTab2 v2.0 (DT)

[ 3357.684434] pstate: 604000c9 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)

[ 3357.684464] pc : dwc3_ep0_out_start+0xc8/0xe0

[ 3357.684504] lr : dwc3_ep0_out_start+0x4c/0xe0

[ 3357.684535] sp : ffff80008778ba70

[ 3357.684552] x29: ffff80008778ba70 x28: ffff00010088b900 x27: 0000000000000000

[ 3357.684605] x26: 0000000000000000 x25: 0000000000000000 x24: ffff00013c924840

[ 3357.684655] x23: ffff0001039f0810 x22: 0000000000000000 x21: ffff000100b76990

[ 3357.684705] x20: ffff000100b76880 x19: ffff00010434f200 x18: ffff8000842730b8

[ 3357.684755] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000006

[ 3357.684804] x14: 0000000000000000 x13: ffffffffffff3f08 x12: ffff800081cd3d70

[ 3357.684854] x11: ffffffffffff3f04 x10: ffff800081cd3dc8 x9 : ffffffffffff3f00

[ 3357.684905] x8 : ffffffffffff3f0c x7 : ffff80008435d000 x6 : 0000000000000000

[ 3357.684954] x5 : ffff800081c4f000 x4 : 0000000000000000 x3 : 0000000000000000

[ 3357.685003] x2 : 0000000000000000 x1 : ffff00010088b900 x0 : 00000000ffffff92

[ 3357.685054] Call trace:

[ 3357.685073]  dwc3_ep0_out_start+0xc8/0xe0 (P)

[ 3357.685118]  dwc3_ep0_stall_and_restart+0xb4/0xe0

[ 3357.685158]  dwc3_ep0_reset_state+0x68/0xa0

[ 3357.685194]  dwc3_gadget_soft_disconnect+0x13c/0x1d0

[ 3357.685231]  dwc3_gadget_pullup+0x8c/0x138

[ 3357.685267]  usb_gadget_disconnect_locked+0x4c/0x170

[ 3357.685303]  gadget_unbind_driver+0x54/0x158

[ 3357.685334]  device_remove+0x54/0x90

[ 3357.685371]  device_release_driver_internal+0x1d4/0x240

[ 3357.685407]  driver_detach+0x54/0xc0

[ 3357.685440]  bus_remove_driver+0x78/0x108

[ 3357.685472]  driver_unregister+0x38/0x78

[ 3357.685506]  usb_gadget_unregister_driver+0x28/0x50

[ 3357.685538]  gadget_dev_desc_UDC_store+0xc0/0x150

[ 3357.685580]  configfs_write_iter+0xcc/0x130

[ 3357.685617]  vfs_write+0x24c/0x388

[ 3357.685658]  ksys_write+0x78/0x120

[ 3357.685695]  __arm64_sys_write+0x24/0x40

[ 3357.685734]  invoke_syscall+0x6c/0x100

[ 3357.685777]  el0_svc_common.constprop.0+0x48/0xf0

[ 3357.685817]  do_el0_svc+0x24/0x38

[ 3357.685846]  el0_svc+0x2c/0x138

[ 3357.685883]  el0t_64_sync_handler+0x10c/0x140

[ 3357.685916]  el0t_64_sync+0x160/0x168

[ 3357.685951] ---[ end trace 0000000000000000 ]---

Also, I can't delete the directory tree of my gadget in the configfs: not permitted.

Further observations:
* After this disaster I can plug a USB stick into this very socket using an OTG cable. It works, switches to host mode and mounts the stick.
* Also, charging the PineTab2 will work as always.
* The message "dwc3 fcc00000.usb: failed to enable ep0out" always shows up, also when I try other configurations, e.g. the script here near the bottom of the page (8814.usbconfigfs.sh.txt for an acm gadget):
https://e2e.ti.com/support/processors-gr...-am62x_dts

My questions:
a) Has anybody got a working USB gadget of any flavour (mass_storage, acm, ecm, ...) on the PineTab2? Please show me your script or tell me my mistake.
b) Could this be a broken kernel driver? Should I report an issue to danctnix?
c) Can you reproduce the problem on your own PineTab2 using my script?

Sorry for this terribly long write-up.

Any ideas?]]> <![CDATA[pinetab2 danctnix broken during upgrade - shell error]]> https://forum.pine64.org/showthread.php?tid=19908 Fri, 18 Jul 2025 22:28:10 +0000 acruhl]]> https://forum.pine64.org/showthread.php?tid=19908
I was doing some package upgrades on my pinetab2 running danctnix and I started noticing some errors with the shell:

-bash: symbol lookup error: -bash: undefined symbol: rl_completion_rewrite_hook

Recklessly, I rebooted and now I can't log in.

It boots up to the graphical login screen. I authenticate, and something happens and I come back to the graphical login screen.

If I try to log in via ssh, I get the error above.

How can I boot into single user? I'm not finding much.

I'm thinking I should try to boot into single user and try to fix it, but I don't know how.

Any other advice?

Thanks!]]>
I was doing some package upgrades on my pinetab2 running danctnix and I started noticing some errors with the shell:

-bash: symbol lookup error: -bash: undefined symbol: rl_completion_rewrite_hook

Recklessly, I rebooted and now I can't log in.

It boots up to the graphical login screen. I authenticate, and something happens and I come back to the graphical login screen.

If I try to log in via ssh, I get the error above.

How can I boot into single user? I'm not finding much.

I'm thinking I should try to boot into single user and try to fix it, but I don't know how.

Any other advice?

Thanks!]]> <![CDATA[How to Donate to DanctNix]]> https://forum.pine64.org/showthread.php?tid=19899 Sat, 12 Jul 2025 09:00:53 +0000 addictioneer]]> https://forum.pine64.org/showthread.php?tid=19899
Thanks]]>
Thanks]]> <![CDATA[How to improve KDE plasma ?]]> https://forum.pine64.org/showthread.php?tid=19830 Wed, 07 May 2025 12:14:57 +0000 louson]]> https://forum.pine64.org/showthread.php?tid=19830
It's my first experience on KDE and I have not found similar posts on the forum (sorry if it does). So here is a thread to share tips how to improve the KDE plasma experience, what service can be disabled / removed ?

Shall I disable accessibility, kde connect and so on ? (how ?)]]>
It's my first experience on KDE and I have not found similar posts on the forum (sorry if it does). So here is a thread to share tips how to improve the KDE plasma experience, what service can be disabled / removed ?

Shall I disable accessibility, kde connect and so on ? (how ?)]]> <![CDATA[Wifi with iwd and/or connman ?]]> https://forum.pine64.org/showthread.php?tid=19781 Sun, 06 Apr 2025 10:33:09 +0000 louson]]> https://forum.pine64.org/showthread.php?tid=19781
Is there any chance for the wifi to work with iwd instead o? with connman ?

So far I got an input/output error, then I wonder if there is any specific patch or configuration to work with NetworkManager/wpa_supplicant.]]>
Is there any chance for the wifi to work with iwd instead o? with connman ?

So far I got an input/output error, then I wonder if there is any specific patch or configuration to work with NetworkManager/wpa_supplicant.]]> <![CDATA[PineTab (early adopters) wifi broken in kernel 6.12]]> https://forum.pine64.org/showthread.php?tid=19749 Sun, 23 Mar 2025 11:25:11 +0000 bartgrefte]]> https://forum.pine64.org/showthread.php?tid=19749 issue has been fixed Smile

Unfortunately wifi is broken with kernel 6.12, it can't find rtw88/rtw8703b_fw.bin and rtw88/rtw8703b_wow_fw.bin, boot with kernel 5.15 and wifi works again.

Since 5.15 works, does this mean I'd have to compile my own 6.12 with that firmware put in if I want to use 6.12?

edit: firmware-realtek was missing, apparently a dependency with 6.12.]]> issue has been fixed Smile