Alsa piCore module needs upgrade.

[meo]

Hello!

I've been trying to get the sound to work in piCore64 v. 17 but I haven't been able to and now I saw that the piCore module Alsa depends on is old and unavailable. So I guess that Alsa needs an update.

Kind greetings,
meo

[Juanito]

Sound works for me - could you post the results of what you’ve tried so far?

[meo]

Hi Juanito!

I have tried just about everything I could so it would be a lot to type. I think though that it is the missing piCore module that is the problem because when I start alsamixer it's static there it is just PCM that you can change or do anything about. When I choose vc4hdmi it says that there is no control for that. So the only arrows that work in my setup is up and down not sideways to another channel. I have a fresh setup and now the piCore module is missing if you check dependencies on alsa. It shows up like this: "alsa-modules-6.12.15-piCore-v8.tcz       Error, not found"     this is a copy from the Apps file on alsa.

Kind greetings,
meo

PS So I think that the channel I should use is muted because it works but no sound DS

PPS At least MASTER must be changed to get some sound I guess DDS

[Juanito]

If you look at http://tinycorelinux.net/17.x/aarch64/tcz/alsa.tcz.tree you'll see the following:

Code: [Select]

alsa.tcz
   libasound.tcz
      alsa-modules-6.12.15-piCore-v8.tcz
..which means that loading alsa will load alsa-modules-6.12.15-piCore-v8.

If, for some reason, alsa-modules-6.12.15-piCore-v8 is not present on your system, you can download it with:

Code: [Select]

tce-load -w alsa-modules-KERNEL
After loading alsa-utils, you should then see this:

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

This should give a sound output - either from a ternimal window or the console prompt:

Code: [Select]

speaker-test -c2 -t wav -l1
Edit: I forgot to mention that this assumes you are going to output sound via hdmi - in order to perform the tests above you need alsa, alsa-utils and graphics-KERNEL loaded.

[Rich]

Hi Juanito

If you look at http://tinycorelinux.net/17.x/aarch64/tcz/alsa.tcz.tree you'll see the following:

Code: [Select]

alsa.tcz
   libasound.tcz
      alsa-modules-6.12.15-piCore-v8.tcz
..which means that loading alsa will load alsa-modules-6.12.15-piCore-v8. ...

These are the available modules for TC17 aarch64:

Code: [Select]

alsa-modules-6.18.16-piCore-v8-16k.tcz
alsa-modules-6.18.16-piCore-v8-rt.tcz
alsa-modules-6.18.16-piCore-v8.tcz
alsa-modules-6.18.28-piCore-v8-16k.tcz
alsa-modules-6.18.28-piCore-v8-rt.tcz
alsa-modules-6.18.28-piCore-v8.tcz
alsa-modules-6.18.37-piCore-v8-16k.tcz
alsa-modules-6.18.37-piCore-v8-rt.tcz
alsa-modules-6.18.37-piCore-v8.tczThere is no 6.12.15.

There is however in TC16 aarch64:

Code: [Select]

alsa-modules-6.12.15-piCore-v8-16k.tcz
alsa-modules-6.12.15-piCore-v8.tcz
alsa-modules-6.12.25-piCore-v8-16k.tcz
alsa-modules-6.12.25-piCore-v8.tcz

... I have a fresh setup and now the piCore module is missing if you check dependencies on alsa. It shows up like this: "alsa-modules-6.12.15-piCore-v8.tcz       Error, not found"     this is a copy from the Apps file on alsa. ...

Something seem very wrong here.
Why would a TC17 install look for a TC16 kernel module?

[Rich]

Hi meo
Please post the result of this command:

Code: [Select]

uname -a

[Juanito]

There is no 6.12.15.

Ah - yes, the tree files get confused when there are multiple kernel versions present.

The libasound dep file correctly shows alsa-modules-KERNEL.tcz however.

[Rich]

Hi Juanito
I regenerated all of the tree files in TC17 aarch64.

[Paul_123]

tree file generation can only link to one kernel.  Its hardcoded in the tree generation script for each architecture.

but

32bit piCore has 3 different kernel possibilities, depending on hardware.
64bit piCore has 3 different kernel possibilities, depending on hardware.

Always reference your running kernel with "KERNEL" in tce-load and you will be fine.   I think meo has been manually downloading everything he gets, rather than letting "tce-load -w" do the work for him.

[Rich]

Hi Paul_123
All true.

I regenerated the tree files because it appears they may have
been copied from the TC16 repo.