Message-ID: <08997a5f96a940a796844db1312f0f957bc15a7c.camel@riseup.net>
Subject: Re: RasPi5 audio
From: Ralf Mardorf <ralf-mardorf@riseup.net>
To: ~alpine/users@lists.alpinelinux.org
Date: Wed, 17 Jan 2024 18:46:36 +0100
In-Reply-To: <0585dc4f195ab3c95d215521627cd629@whidbey.com>
References: <a38dc891feb9854170780a07b8f85f3d@whidbey.com>
	 <913738413a1720203eb1797b77d083d314162c1d.camel@riseup.net>
	 <0585dc4f195ab3c95d215521627cd629@whidbey.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

On Wed, 2024-01-17 at 09:21 -0800, ken.dickey@whidbey.com wrote:
> RasPi5:Alpine:/boot >>> aplay -l
> aplay: device_list:277: no soundcards found...
>=20
> I am using HDMI display, but perhaps I don't understand the semantics of=
=20
> "connect to the HDMI device".

Hi,

I only wanted to ensure that your HDMI display is attached. It might
depend on the kernel or something else, usually, but not always, the
"ALSA device" to use shows the connected HDMI display.
Here it's an EIZO EV2450:

   $ aplay -l | grep "device 3"
   card 3: PCH [HDA Intel PCH], device 3: HDMI 0 [EV2450]

If it shows [HDMI 0], [HDMI 1] ... you might need to test each of it by
~/.asoundrc .

Unfortunately you suffer from a more serious issue. If you run

  lsmod | grep snd

and it shows the required modules and if you run

  lspci | grep -i audio

and it shows or shows not the computer's audio device, then you need to
take a look at log files.

Hm? On Alpine   journalctl -p err   won't help ;). I don't like systemd,
but I'm used to it.

Maybe running   dmseg   with root privileges works?

  dmesg | grep -i audio

If snd modules are missing, this might be the culprit, but it's more
likely something else.

I wonder if    lspci | grep -i audio    shows an audio device that is
supported by the kernel.

Regards,
Ralf