So this is not guaranteed to work, but worth exploring. Give the following
a shot:
$ sudo alsa force-reload
But if that does not work. Try running:
$ sudo apt-get update
$ sudo apt-get install --fix-missing
$ sudo alsa force-reload
$ sudo reboot
I've seen mention of this multiple times, but
Ok, my bad, I completely missed the part where you said it still output,
just no sound from speakers . . .
Well then, that will be problematic to troubleshoot.
With that said, which kernel version are you running ? Ok, 4.4.30-ti-r64
Have you tried different kernels ? newer, and older.
On Mon,
More to the point. Try running the command I gave above *AFTER* the audio
already stops. That'll at least tell you where, and why it fails. After
that you can investigate these reason why. Perhaps providing a fruitful
google search, or at minimum giving you something to report.
On Mon, Jan 2,
$ strace -o /path/file speaker-test
It'll at least tell you where it stops, and most likely why.
On Mon, Jan 2, 2017 at 2:54 PM, John Franey wrote:
> William,
>
> Thanks.
>
> If your suggestion is that the speaker-test program itself is silencing
> the hdmi output with
William,
Thanks.
If your suggestion is that the speaker-test program itself is silencing the
hdmi output with some driver callI'm really doubtful. I hope you don't
mind me saying so. For a couple of reasons, but mainly: The audio stops 10
minutes after boot time even if there is no
One thing that does come to mind is that having just recently removed the
kernel module from loading at boot on my own system here. Is that it
*could* be related to DMA. As it seems the sound modules do include a dma
sound module. Which, there has been some issues with DMA on this platform
in the
On Mon, Jan 2, 2017 at 12:28 PM, John Franey wrote:
> What do you think strace would show?
>
> I used strace a long time ago. Back then, it traced the system calls of
> an application process. What should I look for in that output?
>
> Thanks,
> John
>
Ok so then you know
What do you think strace would show?
I used strace a long time ago. Back then, it traced the system calls of an
application process. What should I look for in that output?
Thanks,
John
On Sunday, January 1, 2017 at 6:07:58 PM UTC-5, William Hermans wrote:
>
> I'd probably try to run your
No. I don't have a serial debug cable.
If you have a link to the other messages, can you provide a reference (a
link or search string or something) so I can read them too?
What exactly do you mean /that some messages only get spit out on that
port'? I don't know what action to take from
I'd probably try to run your executable through strace, and output into a
file.
On Sun, Jan 1, 2017 at 1:25 PM, John Franey wrote:
> I have hdmi audio working up until 10 minutes from boot time. Exactly 10
> minutes.every boot.
>
> I test with 'speaker-test'. Running
Do you have a serial debug cable ?
I have seen posts here saying that some messages only get spit out on
that port.
On 1/1/2017 1:25 PM, John Franey wrote:
> I have hdmi audio working up until 10 minutes from boot time. Exactly
> 10 minutes.every boot.
>
> I test with 'speaker-test'.
I have hdmi audio working up until 10 minutes from boot time. Exactly 10
minutes.every boot.
I test with 'speaker-test'. Running continuously. Output stops exactly at
TimeBoot + 10mins.
There is no outward appearance of a problem:
1) The output of speaker-test is not affected.
12 matches
Mail list logo