[fedora-arm] no hdmi audio on older tv

Discussion:

Jiri Vanek

2018-10-31 11:41:01 UTC

Hello!

I have f29 (kernel-4.18.12-300.fc29.aarch64 ) on machine, which is changing its place from time to
time - between two TVs. Old, and older:)

Both are connected by HDMI. Video output is fine, even acceleration is working, but sound work only
on newer of those two.

I don't know if this is regression, because this machine replaced 32b rapbery2 with kodi, which was
working without issues on both TVs (but was eaten by (not mine) dog)

I was following https://fedoraproject.org/wiki/How_to_debug_sound_problems but had not found much:
- with removed pulseaudio, the aplay -vv segfaults
- I really on pulseaudio anyway, as I need to transfer sound to this machine over network

- the diff of alsa-info.sh's is really minimal [1], only
[cite]
state.vc4hdmi {
control.1 {
iface PCM
name ELD
value '100007006712000100000000000000004c2d9d02
for non working and
value '100007006712000100000000000000004c2d9b03
for working
[/cite]

- when alsamixer is opened, then the default looks like working, and the job on old tv; but not do
nothing older tv.
- when alsamixer -c0 is opened, then the vc4-hdmi reports no control for selected device for
*both* tvs (which is same as f6 and selecting vc4-hdmi)

Does anybody have a clue what to try?

Thanx in advance form java world,
J.

[1]
--- /home/jvanek/Desktop/workingAudio
+++ /home/jvanek/Desktop/nonWorkingAudio
@@ -1,5 +1,5 @@
STDERR:
-cat: /tmp/alsa-info.TzPwpaQcKW/acpidevicestatus.tmp: No such file or directory
+cat: /tmp/alsa-info.GXybsmPDbN/acpidevicestatus.tmp: No such file or directory
cat: '/sys/module/(null)/parameters/*': No such file or directory

@@ -8,7 +8,7 @@
!!ALSA Information Script v 0.4.64
!!################################

-!!Script ran on: Mon Oct 29 14:09:06 UTC 2018
+!!Script ran on: Mon Oct 29 14:15:02 UTC 2018

!!Linux Distribution
@@ -152,7 +152,7 @@
control.1 {
iface PCM
name ELD
- value
'100007006712000100000000000000004c2d9b0353414d53554e470907070000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
+ value
'100007006712000100000000000000004c2d9d0253414d53554e470907070000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
comment {
access 'read volatile'
type BYTES

--
Jiri Vanek
Senior QE engineer, OpenJDK QE lead, Mgr.
Red Hat Czech
***@redhat.com M: +420775390109

Jiri Vanek

2018-11-01 12:37:43 UTC

Permalink

I have seen this before but it was due to the HDMI cable. They have
chips inside of them and if they can't 'talk' correctly with one side
or the other, they drop sound (aka to stop you from pirating etc). I
would try a different cable and see if that makes any difference.

Hi!

Had tried this. tired 3 caables. all behave same:
- all works fine with kodi or raspian (Linux cam.local 4.14.71-v7+ #1145 SMP Fri Sep 21 15:38:35
BST 2018 armv7l GNU/Linux
) on both tv
- all works fine with f28 on newer tv, none work with f29 on older tv

so cable out of guilt:(

thanx a lot!
j.

Post by Jiri Vanek
Hello!
I have f29 (kernel-4.18.12-300.fc29.aarch64 ) on machine, which is changing its place from time to
time - between two TVs. Old, and older:)
Both are connected by HDMI. Video output is fine, even acceleration is working, but sound work only
on newer of those two.
I don't know if this is regression, because this machine replaced 32b rapbery2 with kodi, which was
working without issues on both TVs (but was eaten by (not mine) dog)
- with removed pulseaudio, the aplay -vv segfaults
- I really on pulseaudio anyway, as I need to transfer sound to this machine over network
- the diff of alsa-info.sh's is really minimal [1], only
[cite]
state.vc4hdmi {
control.1 {
iface PCM
name ELD
value '100007006712000100000000000000004c2d9d02
for non working and
value '100007006712000100000000000000004c2d9b03
for working
[/cite]
- when alsamixer is opened, then the default looks like working, and the job on old tv; but not do
nothing older tv.
- when alsamixer -c0 is opened, then the vc4-hdmi reports no control for selected device for
*both* tvs (which is same as f6 and selecting vc4-hdmi)
Does anybody have a clue what to try?
Thanx in advance form java world,
J.
[1]
--- /home/jvanek/Desktop/workingAudio
+++ /home/jvanek/Desktop/nonWorkingAudio
@@ -1,5 +1,5 @@
-cat: /tmp/alsa-info.TzPwpaQcKW/acpidevicestatus.tmp: No such file or directory
+cat: /tmp/alsa-info.GXybsmPDbN/acpidevicestatus.tmp: No such file or directory
cat: '/sys/module/(null)/parameters/*': No such file or directory
@@ -8,7 +8,7 @@
!!ALSA Information Script v 0.4.64
!!################################
-!!Script ran on: Mon Oct 29 14:09:06 UTC 2018
+!!Script ran on: Mon Oct 29 14:15:02 UTC 2018
!!Linux Distribution
@@ -152,7 +152,7 @@
control.1 {
iface PCM
name ELD
- value
'100007006712000100000000000000004c2d9b0353414d53554e470907070000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
+ value
'100007006712000100000000000000004c2d9d0253414d53554e470907070000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
comment {
access 'read volatile'
type BYTES
--
Jiri Vanek
Senior QE engineer, OpenJDK QE lead, Mgr.
Red Hat Czech
_______________________________________________
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines

--
Jiri Vanek
Senior QE engineer, OpenJDK QE lead, Mgr.
Red Hat Czech
***@redhat.com M: +420775390109
_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to arm-***@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/***@lists.fedor

Jiri Vanek

2018-11-01 12:44:32 UTC

Permalink

Post by Jiri Vanek

Hi!
- all works fine with kodi or raspian (Linux cam.local 4.14.71-v7+ #1145 SMP Fri Sep 21 15:38:35
BST 2018 armv7l GNU/Linux
) on both tv

actualy.. on raspbian, aslamixer is not same as in f29. It is same for default, but it have control
for the v4l-hdmi (just calls it bcm245..whatever according to theirs custom driver)

Post by Jiri Vanek
- all works fine with f28 on newer tv, none work with f29 on older tv
so cable out of guilt:(
thanx a lot!
j.

Jiri Vanek

2018-11-01 12:47:50 UTC

Permalink

On Tue, 30 Oct 2018 13:41:50 +0100
I'm not familiar with hdmi, but I'll try to give you some ideas.

I have f29 (ernel kernel-4.18.12-300.fc29 ) on machine, which is
changing its place from time to time - between two TVs. Old, and
older:)
Both are connected by HDMI. Video output is fine, even acceleration
is working, but sound work only on newer of those two.
I don't know if this is regression, because this machine replaced 32b
rapbery2 with kodi, which was working without issues on both TVs (but
was eaten by (not mine) dog)

Can you try an older version of the kernel? Or alsa? It sure sounds
like a regression, but the audio information doesn't support that. Just
a check to be sure.

sure. will do. Just will tak e abit longer.

I was following
https://fedoraproject.org/wiki/How_to_debug_sound_problems but had
- with removed pulseaudio, the aplay -vv segfaults
- I really on pulseaudio anyway, as I need to transfer sound to
this machine over network
- the diff of alsa-info.sh's is really minimal [1], only
[cite]
state.vc4hdmi {
control.1 {
iface PCM
name ELD
value '100007006712000100000000000000004c2d9d02
for non working and
value '100007006712000100000000000000004c2d9b03
for working
[/cite]

If alsa didn't know about the interface for the failing device, it
wouldn't be able to specify a control. Are there any warnings or
errors in the journal during boot, or when trying to play?

- when alsamixer is opened, then the default looks like working,
and the job on old tv; but not do nothing older tv.
- when alsamixer -c0 is opened, then the vc4-hdmi reports no
control for selected device for *both* tvs (which is same as f6 and
selecting vc4-hdmi)
Does anybody have a clue what to try?

Great troubleshooting report, very complete.
Is it possible that you changed a setting on the older TV that isn't
working? Because, like you said, it *should* be working.

nope. both raspbian and kodi still keeps playing.

What happens if you just use an audio player to send only audio to the
older TV from the command line? Maybe try such with debugging enabled.
Or look in the logs to see if it complains about anything.
e.g. mplayer -vv [audio-file]
or
mplayer -vv -novideo [video-file]

I play only from commandline - aplay - and it prints no otput. it behaves corrctly as if it s been
playing. Will try to get more debug output here.

Since the hdmi is the only device, it should route to the TV to play.
I think.
If there are no errors and it acts like it is playing, that really
points to the older TV having an issue.
_______________________________________________
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines

Jiri Vanek

2018-11-01 12:55:53 UTC

Permalink

On Tue, 30 Oct 2018 13:41:50 +0100
I'm not familiar with hdmi, but I'll try to give you some ideas.

Can you try an older version of the kernel? Or alsa? It sure sounds
like a regression, but the audio information doesn't support that. Just
a check to be sure.

sudo dnf downgrade kernel
Last metadata expiration check: 2 days, 19:55:43 ago on Mon 29 Oct 2018 05:55:23 PM CET.
Package kernel of lowest version already installed, cannot downgrade it.
same for alsa*

I failed to updte kernel. at least Network stopped working:(

If alsa didn't know about the interface for the failing device, it
wouldn't be able to specify a control. Are there any warnings or
errors in the journal during boot, or when trying to play?

Great troubleshooting report, very complete.
Is it possible that you changed a setting on the older TV that isn't
working? Because, like you said, it *should* be working.
What happens if you just use an audio player to send only audio to the
older TV from the command line? Maybe try such with debugging enabled.
Or look in the logs to see if it complains about anything.
e.g. mplayer -vv [audio-file]
or
mplayer -vv -novideo [video-file]
Since the hdmi is the only device, it should route to the TV to play.
I think.
If there are no errors and it acts like it is playing, that really
points to the older TV having an issue.
_______________________________________________
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines

Jiri Vanek

2018-11-09 07:38:56 UTC

Permalink

So this is getting more and more funny.
None of your recommendations helped:(( bwd luck, bad thak you a lto anyway for brainstromign.

I borrowed one of the hdmi->Vga+jack boxes (I think it isi this one:
https://iczc.cz/dkqm7qdad2hnra334bu7igbro5_7/obrazek) and....

Now fedora have audio, and raspbian no:D

Considering how hdmi protocol works, I really think that fedroa simply tries newer communication
first (where to change this?) , but fallbeack do not work. And raspbian is trying older
communication first, and fails to upgrade the communication.

Obviously there is some little green goblin in the middle of the way in HDMI :(

On Thu, 1 Nov 2018 13:55:53 +0100

Post by Jiri Vanek
sudo dnf downgrade kernel
Last metadata expiration check: 2 days, 19:55:43 ago on Mon 29 Oct
2018 05:55:23 PM CET. Package kernel of lowest version already
installed, cannot downgrade it. same for alsa*
I failed to updte kernel. at least Network stopped working:(

Here is the last 4.17 kernel for f29,
https://koji.fedoraproject.org/koji/buildinfo?buildID=1088633
You can try a *newer* kernel, the latest 4.18 kernel, 4.18-16
https://koji.fedoraproject.org/koji/buildinfo?buildID=1154877
or the first 4.19 kernel for 4.30. It should work just fine on f29, I
think, since I have been compiling it and running it on f28.

I was allready told that for rPI rawhide is bringing many positive changes. So this may be one of
those. Will try later in the development cycle.

https://koji.fedoraproject.org/koji/buildinfo?buildID=1155120
Is there a reason you are using the 4.18-12 kernel?

Nothing particular. It was in stablw when I preapred the baord, and next udpate break networking. So
I turned back.

Have you tried updating your system from the repositories since install?
Here is an older version of alsa you can try. There were two updates
of alsa only for f29 and f30 after this, so it is a possible difference
from f28.
https://koji.fedoraproject.org/koji/buildinfo?buildID=1106034
Download the binary rpms for the packages you have installed, then from
the directory where they are type, as root,
dnf -C downgrade [list of rpms]
If this doesn't solve your problem, I'm stumped. You should have sound.

thanx a lot!
J.
_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to arm-***@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archi

Peter Robinson

2018-11-09 10:50:36 UTC

Permalink

Post by Jiri Vanek
So this is getting more and more funny.
None of your recommendations helped:(( bwd luck, bad thak you a lto anyway for brainstromign.
https://iczc.cz/dkqm7qdad2hnra334bu7igbro5_7/obrazek) and....
Now fedora have audio, and raspbian no:D
Considering how hdmi protocol works, I really think that fedroa simply tries newer communication
first (where to change this?) , but fallbeack do not work. And raspbian is trying older
communication first, and fails to upgrade the communication.
Obviously there is some little green goblin in the middle of the way in HDMI :(

Have you tried a different HDMI cable? I've seen issues where people
report problems and try a different cable and it's fine. There's
completely different code paths between the upstream fully open stack
that Fedora uses and Raspbian which uses the closed source proprietary
driver where the firmware actually does quite a bit of the work.

Post by Jiri Vanek

On Thu, 1 Nov 2018 13:55:53 +0100

I was allready told that for rPI rawhide is bringing many positive changes. So this may be one of
those. Will try later in the development cycle.

https://koji.fedoraproject.org/koji/buildinfo?buildID=1155120
Is there a reason you are using the 4.18-12 kernel?

Nothing particular. It was in stablw when I preapred the baord, and next udpate break networking. So
I turned back.

thanx a lot!
J.
_______________________________________________
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines

_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to arm-***@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/***@lists.fedoraproject.org

Jiri Vanek

2018-11-12 16:34:12 UTC

Permalink

Post by Peter Robinson

Have you tried a different HDMI cable? I've seen issues where people
report problems and try a different cable and it's fine. There's

Yes. I tried four cables. Each of them on both TVs. Each behaved same for me. *however* factr that I
had tried several different cables, does not mean I used different type of cable. they are very
likely from same shop in my neighbourhood, likely same vendor and price level, just bought in
different times.

Post by Peter Robinson
completely different code paths between the upstream fully open stack
that Fedora uses and Raspbian which uses the closed source proprietary
driver where the firmware actually does quite a bit of the work.

I'm aware of this difference in view like "it exists". But do not know details of the difference
between proprietary and open implementation.
I was hoping for magical switch for HDMI, but looks lie there is none.

Thanx a lot!
J.

Post by Peter Robinson

Post by Jiri Vanek

On Thu, 1 Nov 2018 13:55:53 +0100

I was allready told that for rPI rawhide is bringing many positive changes. So this may be one of
those. Will try later in the development cycle.

https://koji.fedoraproject.org/koji/buildinfo?buildID=1155120
Is there a reason you are using the 4.18-12 kernel?

Nothing particular. It was in stablw when I preapred the baord, and next udpate break networking. So
I turned back.