Recent Posts

71

Raspberry Pi / Re: bluetooth startup script

« Last post by Rich on August 12, 2026, 10:15:21 AM »

Hi Juanito

...  it cannot find the gir files from networkmanager - an extension that does not exist on piCore64. ...

But it does exist in the armhf repo:

Code: [Select]

Title:          networkmanager.tcz
Description:    network manager
Version:        1.22.10
Author:         see list of sites below
Original-site:  see list of sites below
Copying-policy: see list of sites below
Size: 2.7MB
Extension_by:   juanito
Tags:         network wired wireless wifi 3g bluetooth wwan
Comments:       set of co-operative tools that make networking simple and straightforward.
                Whether wifi, wired, 3g, or bluetooth, networkmanager allows you to quickly move from one network to another
                ----------
                This extension contains:
                NetworkManager-1.22.10 - GPLv2 - https://ftp.gnome.org/pub/GNOME/sources/NetworkManager/1.22/NetworkManager-1.22.10.tar.xz
                ----------
Change-log:     2018/02/05 first version
Current:        2020/05/21 updated 1.4.6 -> 1.22.10Found here:
http://tinycorelinux.net/17.x/armhf/tcz/networkmanager.tcz.info

networkmanager-gir.tcz is there as well.

... I'm somewhat baffled by this - what is it about the second script that makes blueman look for networkmanager? ...

The only commands there are hciconfig and hcitool, and I can't find
why they might want networkmanager.

Code: [Select]

echo Raspberry Pi BDADDR already set

Unrelated, but did you mean to echo the variable name (BDADDR) or its contents ($BDADDR)?

72

Raspberry Pi / bluetooth startup script

« Last post by Juanito on August 12, 2026, 08:46:48 AM »

Testing the onboard bluetooth device on an RPi5.

If I use the first of the scripts below, bluetooth starts successfully (the script doesn't return the cursor) and I can use blueman to search for/pair bluetooth headphones and play music through them from the RPi5 using xmms-pulse/pavucontrol.

If I add the second of the scripts below to the end of the first script, bluetooth starts successfully, but blueman will not start with the error that it cannot find the gir files from networkmanager - an extension that does not exist on piCore64.

I'm somewhat baffled by this - what is it about the second script that makes blueman look for networkmanager?

Code: [Select]

#!/bin/sh

sudo /usr/local/etc/init.d/bluez start

sudo modprobe hci_uart

while [ ! -r /dev/serial1 ]; do
        sleep 0.5
done

HCIATTACH=/usr/local/bin/hciattach
if grep -q "Pi 4" /proc/device-tree/model; then
        BDADDR=
else
        SERIAL=`cat /proc/device-tree/serial-number | cut -c9-`
        B1=`echo $SERIAL | cut -c3-4`
        B2=`echo $SERIAL | cut -c5-6`
        B3=`echo $SERIAL | cut -c7-8`
        BDADDR=`printf b8:27:eb:%02x:%02x:%02x $((0x$B1 ^ 0xaa)) $((0x$B2 ^ 0xaa)) $((0x$B3 ^ 0xaa))`
fi
uart0="`cat /proc/device-tree/aliases/uart0`"
serial1="`cat /proc/device-tree/aliases/serial1`"
if [ "$uart0" = "$serial1" ] ; then
        uart0_pins="`wc -c /proc/device-tree/soc/gpio@7e200000/uart0_pins/brcm\,pins | cut -f 1 -d ' '`"
        if [ "$uart0_pins" = "16" ] ; then
                sudo $HCIATTACH /dev/serial1 bcm43xx 3000000 flow - $BDADDR
        else
                sudo $HCIATTACH /dev/serial1 bcm43xx 921600 noflow - $BDADDR
        fi
else
        sudo $HCIATTACH /dev/serial1 bcm43xx 460800 noflow - $BDADDR
fi


Code: [Select]

rpi_bthelper() {
   # For on-board BT, route SCO packets to the HCI interface (enables HFP/HSP)
   # Sound quality is horrible.....just puting this here for info
   #echo "Usage: $0 <bluetooth hci device>"
   dev="hci0"
   # Need to bring hci up before looking at MAC as it can be all zeros during init
   /usr/local/bin/hciconfig "$dev" up
   if ! /usr/local/bin/hciconfig $dev | grep -q "Bus: UART"; then
      echo Not a UART-attached BT Modem
      return
   fi
   if ( /usr/local/bin/hcitool -i $dev dev | grep -q -E '\s43:4[35]:|AA:AA:AA:AA:AA:AA' ); then
      SERIAL=`cat /proc/device-tree/serial-number | cut -c9-`
      B1=`echo $SERIAL | cut -c3-4`
      B2=`echo $SERIAL | cut -c5-6`
      B3=`echo $SERIAL | cut -c7-8`
      BDADDR=`printf '0x%02x 0x%02x 0x%02x 0xeb 0x27 0xb8' $((0x$B3 ^ 0xaa)) $((0x$B2 ^ 0xaa)) $((0x$B1 ^ 0xaa))`

      /usr/local/bin/hcitool -i $dev cmd 0x3f 0x001 $BDADDR
      /usr/local/bin/hciconfig $dev reset
   else
      echo Raspberry Pi BDADDR already set
   fi
}


73

Raspberry Pi / Re: How can I make bluetooth work in piCore64 v. 17.

« Last post by Juanito on August 12, 2026, 04:29:36 AM »

Using the bt_test.sh script below, you should see something like this on an RPi5 using the onboard bluetooth device:

Code: [Select]

tce-load -i bluez
./bt_test.sh
stopped /usr/local/bin/dbus-daemon (pid 5656)
rm: can't remove '/var/run/dbus/pid': No such file or directory
stopped /usr/local/bin/dbus-daemon (pid 12488)

ps aux | grep dbus
 5655 tc       dbus-launch --autolaunch=ceaaa08f57bacfbb676f65956a79eb40 --binary-syntax --close-stderr
12493 tc       /usr/local/bin/dbus-daemon --system

ps aux | grep blue
12495 root     /usr/local/lib/bluetooth/bluetoothd --experimental

..and now you are ready to scan for and pair with another bluetooth device.

bt_test.sh:

Code: [Select]

#!/bin/sh

sudo /usr/local/etc/init.d/bluez start

sudo modprobe hci_uart

while [ ! -r /dev/serial1 ]; do
        sleep 0.5
done

HCIATTACH=/usr/local/bin/hciattach
if grep -q "Pi 4" /proc/device-tree/model; then
        BDADDR=
else
        SERIAL=`cat /proc/device-tree/serial-number | cut -c9-`
        B1=`echo $SERIAL | cut -c3-4`
        B2=`echo $SERIAL | cut -c5-6`
        B3=`echo $SERIAL | cut -c7-8`
        BDADDR=`printf b8:27:eb:%02x:%02x:%02x $((0x$B1 ^ 0xaa)) $((0x$B2 ^ 0xaa)) $((0x$B3 ^ 0xaa))`
fi
uart0="`cat /proc/device-tree/aliases/uart0`"
serial1="`cat /proc/device-tree/aliases/serial1`"
if [ "$uart0" = "$serial1" ] ; then
        uart0_pins="`wc -c /proc/device-tree/soc/gpio@7e200000/uart0_pins/brcm\,pins | cut -f 1 -d ' '`"
        if [ "$uart0_pins" = "16" ] ; then
                sudo $HCIATTACH /dev/serial1 bcm43xx 3000000 flow - $BDADDR
        else
                sudo $HCIATTACH /dev/serial1 bcm43xx 921600 noflow - $BDADDR
        fi
else
        sudo $HCIATTACH /dev/serial1 bcm43xx 460800 noflow - $BDADDR
fi

rpi_bthelper() {
   # For on-board BT, route SCO packets to the HCI interface (enables HFP/HSP)
   # Sound quality is horrible.....just puting this here for info
   #echo "Usage: $0 <bluetooth hci device>"
   dev="hci0"
   # Need to bring hci up before looking at MAC as it can be all zeros during init
   /usr/local/bin/hciconfig "$dev" up
   if ! /usr/local/bin/hciconfig $dev | grep -q "Bus: UART"; then
      echo Not a UART-attached BT Modem
      return
   fi
   if ( /usr/local/bin/hcitool -i $dev dev | grep -q -E '\s43:4[35]:|AA:AA:AA:AA:AA:AA' ); then
      SERIAL=`cat /proc/device-tree/serial-number | cut -c9-`
      B1=`echo $SERIAL | cut -c3-4`
      B2=`echo $SERIAL | cut -c5-6`
      B3=`echo $SERIAL | cut -c7-8`
      BDADDR=`printf '0x%02x 0x%02x 0x%02x 0xeb 0x27 0xb8' $((0x$B3 ^ 0xaa)) $((0x$B2 ^ 0xaa)) $((0x$B1 ^ 0xaa))`

      /usr/local/bin/hcitool -i $dev cmd 0x3f 0x001 $BDADDR
      /usr/local/bin/hciconfig $dev reset
   else
      echo Raspberry Pi BDADDR already set
   fi
}


74

General TC Talk / Re: Very Strange , I can't log into forum using Dillo..

« Last post by CNK on August 11, 2026, 08:58:12 PM »

By default Dillo doesn't accept session cookies. This forum used to use PHPSESSID parameters when cookies weren't available, so log-ins still worked. But the forum's webmaster seems to have disabled that feature now, so you need to enable cookies by editing ~/.dillo/cookiesrc and add this line:

Code: [Select]

forum.tinycorelinux.net ACCEPT_SESSION

You can also set it to "ACCEPT" instead of "ACCEPT_SESSION", or change the "DEFAULT" setting that applies to all websites. See the "cookiesrc" section of the documentation for details (click on the "?" button in Dillo).

gadget42's certificate errors are a completely different problem, probably caused by an old ca-certificates extension that needs updating.

75

Raspberry Pi / Re: How can I make bluetooth work in piCore64 v. 17.

« Last post by meo on August 11, 2026, 01:56:53 PM »

Hello!

Connection Failed: Method "Connect" with signature "" on interface "org.bluez.Device1" doesn't exist

I have been trying to get bluetooth to work but no. Above is the error message I received today. I'm not a bluetooth man so I don't understand more that that the handshake didn't work. If anyone has an idea what to do please just tell me in this thread. I will be very grateful for any hints.

Kind regards,
meo

76

Raspberry Pi / Re: How can I make bluetooth work in piCore64 v. 17.

« Last post by Paul_123 on August 10, 2026, 07:35:37 PM »

99-com.rules is already included in the piCore Base

The above script is up to date as well.   The only thing extra is a little helper script that is called after the above init.

Code: [Select]

rpi_bthelper() {
   # For on-board BT, route SCO packets to the HCI interface (enables HFP/HSP)
   # Sound quality is horrible.....just puting this here for info
   #echo "Usage: $0 <bluetooth hci device>"
   dev="hci0"
   # Need to bring hci up before looking at MAC as it can be all zeros during init
   /usr/local/bin/hciconfig "$dev" up
   if ! /usr/local/bin/hciconfig $dev | grep -q "Bus: UART"; then
      echo Not a UART-attached BT Modem
      return
   fi
   if ( /usr/local/bin/hcitool -i $dev dev | grep -q -E '\s43:4[35]:|AA:AA:AA:AA:AA:AA' ); then
      SERIAL=`cat /proc/device-tree/serial-number | cut -c9-`
      B1=`echo $SERIAL | cut -c3-4`
      B2=`echo $SERIAL | cut -c5-6`
      B3=`echo $SERIAL | cut -c7-8`
      BDADDR=`printf '0x%02x 0x%02x 0x%02x 0xeb 0x27 0xb8' $((0x$B3 ^ 0xaa)) $((0x$B2 ^ 0xaa)) $((0x$B1 ^ 0xaa))`

      /usr/local/bin/hcitool -i $dev cmd 0x3f 0x001 $BDADDR
      /usr/local/bin/hciconfig $dev reset
   else
      echo Raspberry Pi BDADDR already set
   fi
}

Note: None of this is needed when using a linux supported bluetooth USB stick.

77

Programming & Scripting - Unofficial / [100% offline] 50 KB Guff Ai LLM launcher in JavaScript with an HTML extension.

« Last post by xor on August 10, 2026, 03:03:49 PM »

I had AI write a 50 KB Guff Ai LLM launcher in JavaScript with an HTML extension.
Minimum system requirements: It runs under Firefox 115 ESR.
Instead of using open source code, I plan to share the command prompt used to create the file soon.
100% offline
cpu a4-5300 (no-gpu)
speed: 120 t/s
LLM : SmolLM-135M-Instruct-Q2_K.gguf

78

Raspberry Pi / Re: How can I make bluetooth work in piCore64 v. 17.

« Last post by meo on August 10, 2026, 11:50:44 AM »

Hi guys!

Things are strange but suddenly I have sound!!!!!!  Do you what the last thing I did? I changed in .ashrc I removed vi which I don't like nor use and put emacs which I like and have used for some 25 years or so. Then I start Firefox to see a video about setting up alsa and what had happened, I had sound. I could hardly believe it but it's a fact. So then I try to get bluetooth to work so I can use in-ear sound things I have and I can't get it to work. I'll try more but isn¨t it funny what can happen?

Regards,
meo

79

Extension requests / Re: profanity xmpp client for TCL17.x x86_64

« Last post by GNUser on August 10, 2026, 10:30:56 AM »

Hi Rich.

So if you don't hear anything in 3 or 4 days, submit your update.

Sounds like a plan. Thanks.

80

Raspberry Pi / Re: How can I make bluetooth work in piCore64 v. 17.

« Last post by Juanito on August 10, 2026, 10:13:35 AM »

There is a negative side though since it depends on alsa I don't get any sound. I have tried even with the .asoundrc file in my home directory with pertinent information but nothing.

With the alsa, alsa-untils and graphics-KERNEL extensions loaded and without an .asoundrc file, you should get something like this on an RPi5:

Code: [Select]

aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: vc4hdmi0 [vc4-hdmi-0], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: vc4hdmi1 [vc4-hdmi-1], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

speaker-test -c2 -t wav -l1

speaker-test 1.2.12

Playback device is default
Stream parameters are 48000Hz, S16_LE, 2 channels
WAV file(s)
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 4 to 65536
Period size range from 2 to 32768
Periods = 4
was set period_size = 12000
was set buffer_size = 48000
 0 - Front Left
 1 - Front Right
Time per period = 2.457287