piCore 14.0 (32 and 64 bit) release

[aus9]

to anyone on arm6/7*

If you are using headphones/line out you may find no /var/lib/alsa/asound.state to interact with if you run a command

Code: [Select]

sudo alsactl store
the solution for me, which I hope works for you if interested is

Code: [Select]

alsamixer # set your volumes
sudo alsactl store -f /home/tc/asound.state
Then I append to my bootlocal as discussed above...one more line

aslactl restore -f /home/tc/asound.state

[Paul_123]

audio options on the kernel command line are set from the pi firmware.  You should not be using anything on the command line to manipulate.

Audio is configured in config.txt   I do not believe you can enable/disable the headphone jack and HDMI separately.  Just pick the appropriate alsa device.

If you are using the VC4 driver, then there are audio options with that too, as the VC4 driver will take over.

[aus9]

correction to my above restore info....on reboot I lost the setting so added a sleep and reboot is good again.

so my opt now reads

rmmod snd_bcm2835
modprobe snd_bcm2835 options enable_headphones=1 enable_hdmi=0
sleep 3
alsactl restore -f /home/tc/asound.state

[aus9]

Hi Paul_123
I may be misreading your response but I can assure that I have disabled hdmi audio out as per

Code: [Select]

inxi -Axxx
Audio:
  Device-1: bcm2711-hdmi0 driver: N/A bus-ID: N/A chip-ID: brcm:soc
    class-ID: hdmi
  Device-2: bcm2711-hdmi1 driver: N/A bus-ID: N/A chip-ID: brcm:soc
    class-ID: hdmi
  API: ALSA v: k6.1.25-piCore-v7l status: kernel-api
tc@box:~$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]
  Subdevices: 8/8
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
  Subdevice #4: subdevice #4
  Subdevice #5: subdevice #5
  Subdevice #6: subdevice #6
  Subdevice #7: subdevice #7
inxi is misleading but aplay is not!

We both agree that audio is enabled by the config.txt

at the moment I have  bootlist lines
graphics-KERNEL.tcz
Xorg-3d.tcz

#### config.txt lines ...some deviate from original
[PI4]
initramfs rootfs-piCore-14.0.gz,modules-6.1.25-piCore-v7l.gz followkernel
kernel kernel6125v7l.img
hdmi_safe=1
config_hdmi_boost=4
dtparam=audio=on
[PI4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
#dtoverlay=vc4-kms-v3d-pi4
max_framebuffers=2
[all]
dtoverlay=vc4-fkms-v3d

thanks for reading

##  trivia
if card0 was hdmi I would agree but its not as hdmi is disabled

[polikuo]

Hi.
Looks like I'm late to the party
Just trying it out on my Pi3 model B starting fresh
Here's what I've run into, I couldn't download KERNEL related files

Code: [Select]

tc@piCore:~$ . /etc/init.d/tc-functions
tc@piCore:~$ getMirror
tc@piCore:~$ echo $MIRROR
http://repo.tinycorelinux.net/14.x/armv7l/tcz
tc@piCore:~$ echo $BUILD
armv7l
tc@piCore:~$ uname -r
6.1.25-piCore-v7
tc@piCore:~$ uname -m
armv7l
tc@piCore:~$ uname -a
Linux piCore 6.1.25-piCore-v7 #1 SMP Sun Apr 30 13:34:55 EDT 2023 armv7l GNU/Linux
By default, without touching config.txt on Pi3B
You'll load up the armv7 kernel, but 'uname -m' says you have armv7l
This results in tce-load trying to download v7 modules from v7l repo
I think the easy fix for this is to adjust the config file

Code: [Select]

[PI3]
initramfs rootfs-piCore-14.0.gz,modules-6.1.25-piCore-v7l.gz followkernel
kernel kernel6125v7l.img
#initramfs rootfs-piCore-14.0.gz,modules-6.1.25-piCore-v7.gz followkernel
#kernel kernel6125v7.imgCould anyone kindly share some insight to which kernel I should pick for each type of board ?

P.S. the openbox.tcz.dep present on both armv6 and armv7 need a little fix
libpcre.tcz --> pcre.tcz
BTW, there's no openbox on armv7l repo, it's working though.

[Paul_123]

A pi3 is armv7.
Pi4 in 32bit uses armv7l

I’ll have to take a look at logic around the Mirror setting.

[polikuo]

Hi
Here's the difference between the two

Code: [Select]

--- tc-functions-13
+++ /etc/init.d/tc-functions
@@ -273,18 +273,23 @@
 } ' "$1"
 }
 
+getFullVer() {
+verid=$(grep '^VERSION_ID=' /etc/os-release)
+echo ${verid#*=}
+}
+
 getMajorVer() {
-awk '{printf "%d", $1}' /usr/share/doc/tc/release.txt
+fullver=$(getFullVer)
+echo ${fullver%.*}
 }
 
-
 getBuild() {
-BUILD=`getrpicpu`
+BUILD=`uname -m`
 case ${BUILD} in
- BCM2835) echo "armv6" ;;
- BCM2836) echo "armv7" ;;
- BCM2837) echo "armv7" ;;
- BCM2711) echo "armv7l" ;;
+ armv6l) echo "armv6" ;;
+ armv7)  echo "armv7" ;;
+ armv7l) echo "armv7l" ;;
+ aarch64) echo "aarch64" ;;
  *)      echo "armv6" ;;
 esac
 }


[Paul_123]

Yes, I already fixed it locally.  That’s what happens when git doesn’t get updated.  I found lots of cases where Core scripts on piCore did not match,  I just missed that one.

I’ll push up a dot release image soon.

[Paul_123]

New 32bit image uploaded.  http://www.tinycorelinux.net/14.x/armv7/releases/RPi/piCore-14.0.1.zip
  -fixes Pi2/3 using wrong repo.

No other changes.