Recent Posts

81

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

« Last post by Rich on August 10, 2026, 10:04:49 AM »

Hi GNUser
Just a heads up, andy_jp was last active on February 18, 2011.
So if you don't hear anything in 3 or 4 days, submit your update.

82

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

« Last post by meo on August 10, 2026, 09:52:35 AM »

Hi again Juanito and Paul_123!

With your help I got bluetooth to work! 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. So bluetooth works that's the pro the con is that I haven't been able to get alsa to work yet. Thanks for your willingness to help. And by the way 99-com.conf is there not visible but when I tried to copy it there the terminal asked if I wanted to overwrite?

Kind regards,
meo

PS I got some AI help as well DS

83

Extension requests / profanity xmpp client for TCL17.x x86_64

« Last post by GNUser on August 10, 2026, 09:52:21 AM »

Hi, andy_jp. I sent you a PM about profanity.tcz extension, which you maintain for the x86_64 repo.

Current profanity version in repo is 0.10.0 from 2021. I need some features which are only present in more recent versions.

I built the latest version (0.18.2) for my personal use and it is working well. Would you like me to submit the updated extension? Or would you prefer to update it yourself?

If you prefer to keep the old version in the repo for any reason whatsoever, that's also fine--I can use my updated version as a custom extension.

Please advise.

84

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

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

Ah - yes it is.

I must have had the script for a while...

85

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

« Last post by Paul_123 on August 10, 2026, 08:32:58 AM »

Isn’t 99- com.rules in. The default image?

I’m just not in a spot to validate

86

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

« Last post by Juanito on August 10, 2026, 07:54:12 AM »

The second code box contains 99-com.rules - you need to save this somewhere after deleting the first line (cat 99-com.rules)

The script does not scan for bluetooth devices to pair with - you will either need to do this manually or use blueman, which I used to test that things work.

87

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

« Last post by meo on August 10, 2026, 07:39:48 AM »

Hi Juanito and Paul_123!

Thanks for your time trying to help me out. I put the booth scripts together () and ran it. It can't find 99-com.rules I think it was but does the script make the RPi scan for bluetooth equipment to pair with or is that done in an other way?

Kind Greetings,
meo

PS I have searched for the 99-com.rules but I can't find anything about that in the wiki. DS

88

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

« Last post by Paul_123 on August 10, 2026, 06:48:05 AM »

There are a few updates to the script.  It comes from raspiOS.  I’ll have to look it up.  But what you posted should still work

89

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

« Last post by Juanito on August 10, 2026, 06:34:42 AM »

This script works for me on an RPi5 - I suspect there must be something more recent @paul_123?

Code: [Select]

#!/bin/sh

sudo cp /mnt/mmcblk0p2/conf/99-com.rules /etc/udev/rules.d/
sudo udevadm control --reload-rules
sudo udevadm trigger

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

Where:

Code: [Select]

cat 99-com.rules
SUBSYSTEM=="input", GROUP="staff", MODE="0660"
SUBSYSTEM=="i2c-dev", GROUP="staff", MODE="0660"
SUBSYSTEM=="spidev", GROUP="staff", MODE="0660"
SUBSYSTEM=="bcm2835-gpiomem", GROUP="staff", MODE="0660"

SUBSYSTEM=="gpio", GROUP="staff", MODE="0660"
SUBSYSTEM=="gpio*", PROGRAM="/bin/sh -c '\
        chown -R root:staff /sys/class/gpio && chmod -R 770 /sys/class/gpio;\
        chown -R root:staff /sys/devices/virtual/gpio && chmod -R 770 /sys/devices/virtual/gpio;\
        chown -R root:staff /sys$devpath && chmod -R 770 /sys$devpath\
'"

KERNEL=="ttyAMA[01]", PROGRAM="/bin/sh -c '\
        ALIASES=/proc/device-tree/aliases; \
        if cmp -s $ALIASES/uart0 $ALIASES/serial0; then \
                echo 0;\
        elif cmp -s $ALIASES/uart0 $ALIASES/serial1; then \
                echo 1; \
        else \
                exit 1; \
        fi\
'", SYMLINK+="serial%c"

KERNEL=="ttyS0", PROGRAM="/bin/sh -c '\
        ALIASES=/proc/device-tree/aliases; \
        if cmp -s $ALIASES/uart1 $ALIASES/serial0; then \
                echo 0; \
        elif cmp -s $ALIASES/uart1 $ALIASES/serial1; then \
                echo 1; \
        else \
                exit 1; \
        fi \
'", SYMLINK+="serial%c"


90

Extension requests / Re: OMXPlayer for piCore32.

« Last post by Juanito on August 10, 2026, 06:21:40 AM »

Assuming you have alsa, alsa-utils and graphics-KERNEL loaded, what does “aplay -l” give?