Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #197476 > unrolled thread

No sound/audio

Back to article view | Back to linux.debian.user

Contents

  No sound/audio 70147persson@telia.com - 2018-07-11 09:40 +0200
    Re: No sound/audio Kent West <westk@acu.edu> - 2018-07-11 18:40 +0200
    Re: No sound/audio Ric Moore <wayward4now@gmail.com> - 2018-07-12 00:40 +0200
      Re: No sound/audio 70147persson@telia.com - 2018-07-17 20:10 +0200
        Re: No sound/audio deloptes <deloptes@gmail.com> - 2018-07-18 07:10 +0200
          Re: No sound/audio Kaj Persson <70147persson@telia.com> - 2018-07-19 21:00 +0200
            Re: No sound/audio deloptes <deloptes@gmail.com> - 2018-07-20 00:10 +0200
        Re: No sound/audio Rusi Mody <rustompmody@gmail.com> - 2018-07-20 06:00 +0200
        Re: No sound/audio David Wright <deblis@lionunicorn.co.uk> - 2018-07-21 17:40 +0200

#197476 — No sound/audio

Hi all,

I get no sound. After reinstalling Stretch a couple of months ago, the 
computer is silent. Well, not completely, because these warning beeps at 
end of line etc.. are coming out. Normally I have all those disabled, 
but for testing this is established, so I am quite sure the audio card 
is OK.

The computer is a Hewlett Packard laptop model HP Pavilion dv4-1199eo.

Inxi -A presents this information:
Audio:     Card Intel 82801I (ICH9 Family) HD Audio Controller
            driver: snd_hda_intel
            Sound: Advanced Linux Sound Architecture v: k4.9.0-6-amd64

After a reboot I can find among other things this information in 
/var/log/syslog:

	systemd[1]: Starting Save/Restore Sound Card State...

and

	kernel: [   14.190720] input: PC Speaker as 
/devices/platform/pcspkr/input/input18
	kernel: [   14.201142] input: HDA Digital PCBeep as 
/devices/pci0000:00/0000:00:1b.0/sound/card0/input14
	kernel: [   14.206632] input: HDA Intel Dock Mic as 
/devices/pci0000:00/0000:00:1b.0/sound/card0/input15
	kernel: [   14.206730] input: HDA Intel Mic as 
/devices/pci0000:00/0000:00:1b.0/sound/card0/input16
	kernel: [   14.206817] input: HDA Intel Front Headphone as 
/devices/pci0000:00/0000:00:1b.0/sound/card0/input17

so I think I can feel assured the system has contact with the audio card.

I have removed two fields before each line containing date and computer 
name.

After the install of stretch I did remove the Pulsaudio package and 
instead installed the Jack package, this recommended by the Ardour team. 
Ardour is a program very important for my use of the computer, so I 
really want that program to work fine. I have done this measure before 
in the jessie era, so I know it works. Trying to make a connection in 
the QjackCtl program fails, and I can read the following message. Line 3 
and 11 is partly in Swedish, meaning that the file or directory does not 
exist, but no information is given about which file or which directory, 
so I feel a bit lost:

23:16:56.103 Statistics reset.
23:16:56.106 ALSA connection change.
Cannot connect to server socket err = Filen eller katalogen finns inte
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 
4294967295, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 
4294967295, skipping unlock
23:16:56.230 ALSA connection graph change.
23:17:00.491 JACK is starting...
23:17:00.491 /usr/bin/jackd -v -dalsa -dhw:0 -r48000 -p1024 -n2 -m -H -M -P
Cannot connect to server socket err = Filen eller katalogen finns inte
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 
4294967295, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 
4294967295, skipping unlock
Cannot create RT messagebuffer thread: Operation not permitted (1)
Retrying messagebuffer thread without RT scheduling
Messagebuffer not realtime; consider enabling RT scheduling for user
no message buffer overruns
Cannot create RT messagebuffer thread: Operation not permitted (1)
Retrying messagebuffer thread without RT scheduling
Messagebuffer not realtime; consider enabling RT scheduling for user
no message buffer overruns

and a lot more. Here is the tail of the messages (188 lines removed):

Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 8
Jack: JackSocketServerChannel::Execute : fPollTable i = 2 fd = 9
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 8
Jack: JackSocketServerChannel::Execute : fPollTable i = 2 fd = 9
23:17:29.074 ALSA connection change.
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 8
Jack: JackSocketServerChannel::Execute : fPollTable i = 2 fd = 9
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 8
Jack: JackSocketServerChannel::Execute : fPollTable i = 2 fd = 9
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 8
Jack: JackSocketServerChannel::Execute : fPollTable i = 2 fd = 9
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 8
Jack: JackSocketServerChannel::Execute : fPollTable i = 2 fd = 9
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 8
Jack: JackSocketServerChannel::Execute : fPollTable i = 2 fd = 9
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 8
Jack: JackSocketServerChannel::Execute : fPollTable i = 2 fd = 9
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 8
Jack: JackSocketServerChannel::Execute : fPollTable i = 2 fd = 9
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 8
Jack: JackSocketServerChannel::Execute : fPollTable i = 2 fd = 9

Since I am not very skilled in the sound technology I have previously, 
when I carried out this operation, randomly installed every package I 
found, which seemed to deal with sound until it all worked, but this 
time my intention is to do the job in a more deliberate way.

So is there anyone who can give hints about what I have missed so far?

Kaj

[toc] | [next] | [standalone]

#197508

[Multipart message — attachments visible in raw view] — view raw

On Wed, Jul 11, 2018 at 2:31 AM, <70147persson@telia.com> wrote:

> Hi all,
>
> I get no sound. After reinstalling Stretch a couple of months ago, the
> computer is silent.


May be completely unrelated...

Since upgrading to the 4.16.16-2 kernel, anytime I reboot my PC I boot into
a soundless environment, with my sound system reporting my sound device as
the "Dummy Sound Device" (or something similar). I can "sudo kill
[timidity's PID]", and that's restores my sound.

As I understand it, Timidity is taking exclusive hold of some audio file
(/dev/sound ?) early in the boot process which prevents other apps (Pulse,
ALSA, etc) from using that file.

FWIW.

-- 
Kent West                    <")))><
Westing Peacefully - http://kentwest.blogspot.com

[toc] | [prev] | [next] | [standalone]

#197522

On 07/11/2018 03:31 AM, 70147persson@telia.com wrote:

> So is there anyone who can give hints about what I have missed so far?

I hate to suggest this on the Debian list, but I installed Ubuntu-Studio 
to a separate partition which gives you fully functional jack and a 
real-time kernel to do your studio work with. Pretty darn fast, found my 
midi in no time and was up and running without the usual beating your 
head on the keyboard in frustration.

I be stupid, ...so I like it simple. Ric

-- 
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html

[toc] | [prev] | [next] | [standalone]

#197741

Den 2018-07-12 kl. 00:37, skrev Ric Moore:

> On 2018-07-11 at 18:38, Kent West wrote:
>
>  On Wed, Jul 11, 2018 at 2:31 AM, <70147persson@telia.com wrote:
>
>      Hi all,
>
>      I get no sound. After reinstalling Stretch a couple of months 
> ago, the computer is silent.
>
>
>  May be completely unrelated...
>
>  Since upgrading to the 4.16.16-2 kernel, anytime I reboot my PC I 
> boot into a soundless environment, with my sound system reporting my 
> sound device as the "Dummy Sound Device" (or something similar). I can 
> "sudo kill [timidity's PID]", and that's restores my sound.
>
>  As I understand it, Timidity is taking exclusive hold of some audio 
> file (/dev/sound ?) early in the boot process which prevents other 
> apps (Pulse, ALSA, etc) from using that file.
>
>  FWIW.
>
>  --
>  Kent West
>  Westing Peacefully - http://kentwest.blogspot.com

> On 07/11/2018 03:31 AM, 70147persson@telia.com wrote:
>
>> So is there anyone who can give hints about what I have missed so far?
>
> I hate to suggest this on the Debian list, but I installed 
> Ubuntu-Studio to a separate partition which gives you fully functional 
> jack and a real-time kernel to do your studio work with. Pretty darn 
> fast, found my midi in no time and was up and running without the 
> usual beating your head on the keyboard in frustration.
>
> I be stupid, ...so I like it simple. Ric
>

Thank you Kent and Ric...
... for your efforts to solve my sound problems. I did stop Timidity, 
but no, it had no effect. Neither did a reboot. Your hint, Ric, to try 
Ubuntu, well I have not tried that, yet. It was many years ago I left 
that distribution after there decision regarding the desktop software 
Unity. After that Mint (LMDE) for a couple of years until I decided to 
take the full step over to Debian, where I am now, and has no plans to 
leave. OK, your suggestion was to have it on a separate partition, but 
unfortunately I have no left. All four primary partitions are occupied 
by other projects I have and have had. Well an partition in the extended 
one could certainly do, but, well, I have not tested yet.

But when examining my programmes I got what I wanted from Frescobaldi 
with LilyPond, and also from Denemo. Both of them are connected via 
Timidity. If also Ardour will work I have not tested yet. VLC is working 
fine, but never Firefox.

So I started reading on a support site for Firefox, and found a sentence 
saying that from version 53, you have to use PulseAudio for all sound in 
Firefox. It was like a stab into my back. So, what is this? I get a 
feeling of Microsoft: "Now we are so big that we decide what the people 
can use and do". Has Firefox become so big?

Nothing else, I love Firefox, and appreciate really the work all these 
volunteers are doing, but if I cannot get sound from that programme the 
way I prefer, I feel I am forced to look for another browser.

Anyone who knows a way to bypass the announced limitations?

Kaj

[toc] | [prev] | [next] | [standalone]

#197754

70147persson@telia.com wrote:

> Nothing else, I love Firefox, and appreciate really the work all these
> volunteers are doing, but if I cannot get sound from that programme the
> way I prefer, I feel I am forced to look for another browser.
> 
> Anyone who knows a way to bypass the announced limitations?

Hi, while I agree with you that we are left without a choice in cases such
as firefox, I disagree that this is a firefox problem. The problem is
definitely in timidity as it hooks I guess directly to alsa and blocks any
other application.
There were suggestions made to use jack and when working with music
(timidity) you probably will have other benefits by using jack.

As of your remark - you stopped timidity - did you disable autostart before
rebooting. Chances are high you didn't and it autostarted blocking your
device again. In /etc/default/timidity

# uncomment to override enabling triggered by availability of
timidity-deamon
TIM_ALSASEQ=false


regards

[toc] | [prev] | [next] | [standalone]

#197808

Den 2018-07-18 kl. 07:07, wrote deloptes:
> 70147persson@telia.com wrote:
>
>> Nothing else, I love Firefox, and appreciate really the work all these
>> volunteers are doing, but if I cannot get sound from that programme the
>> way I prefer, I feel I am forced to look for another browser.
>>
>> Anyone who knows a way to bypass the announced limitations?
> Hi, while I agree with you that we are left without a choice in cases such
> as firefox, I disagree that this is a firefox problem. The problem is
> definitely in timidity as it hooks I guess directly to alsa and blocks any
> other application.
> There were suggestions made to use jack and when working with music
> (timidity) you probably will have other benefits by using jack.
>
> As of your remark - you stopped timidity - did you disable autostart before
> rebooting. Chances are high you didn't and it autostarted blocking your
> device again. In /etc/default/timidity
>
> # uncomment to override enabling triggered by availability of
> timidity-deamon
> TIM_ALSASEQ=false
>
>
> regards
>
>

No, certainly you are right. So far my knowledge did not reach. Well, I 
followed your instruction and made a reboot. And now the timidity daemon 
was not there, at least according to the command "ps -ef | grep 
timidity". Before the reboot it was. But the only result of this was 
that none of my programmes delivered any sound, not Frescobaldi and not 
Firefox. So what was the advantage? Is there no possibility to coexist 
with Timidity (and Jack)? Before my latest upgrade, I now use version 61 
of Firefox, they worked fine together, at least from my point of view. I 
had sound in Firefox as well as Frescobaldi and Denemo (and Ardour). So 
from with my horizon all has been a deterioration, even if I of course 
does not realize all the difficulties you developers are meeting. On the 
other hand, Timidity is a so much appreciated software, that it should 
be a good thing learning to live together with it. A dialogue with the 
Timidity guys perhaps? Regarding Ardour and the other music software I 
can suspect it is not equally big, but we who use them will still 
continue to do so, and not lose them.

Well Frescobaldi is working fine with Jack. Denemo seems to have its own 
method for producing sound, and is working fine also without Timidity. 
Regarding Ardour I do not know yet, I have not had the time to test.

Kaj

[toc] | [prev] | [next] | [standalone]

#197810

Kaj Persson wrote:

> No, certainly you are right. So far my knowledge did not reach. Well, I
> followed your instruction and made a reboot. And now the timidity daemon
> was not there, at least according to the command "ps -ef | grep
> timidity". Before the reboot it was. But the only result of this was
> that none of my programmes delivered any sound, not Frescobaldi and not
> Firefox. So what was the advantage?

you reduced your problems by one as timidity blocks the card. perhaps now
something else blocks it
alsamixer and pavucontrol will help you see what is the status of your audio
setup.
for alsamixer use -c <n> to see alsa or pulse

good luck

[toc] | [prev] | [next] | [standalone]

#197820

On Tuesday, July 17, 2018 at 11:40:04 PM UTC+5:30, Kaj Persson wrote:
> So I started reading on a support site for Firefox, and found a sentence 
> saying that from version 53, you have to use PulseAudio for all sound in 
> Firefox. It was like a stab into my back. So, what is this? I get a 
> feeling of Microsoft: "Now we are so big that we decide what the people 
> can use and do". Has Firefox become so big?
> 
> Nothing else, I love Firefox, and appreciate really the work all these 
> volunteers are doing, but if I cannot get sound from that programme the 
> way I prefer, I feel I am forced to look for another browser.
> 
> Anyone who knows a way to bypass the announced limitations?
> 
> Kaj

I understand that jack team and pulse team have tried to work out how the two
can work together
http://jackaudio.org/faq/pulseaudio_and_jack.html   (option 4)

Also

https://askubuntu.com/questions/572120/how-to-use-jack-and-pulseaudio-alsa-at-the-same-time-on-the-same-audio-device
http://manual.ardour.org/setting-up-your-system/platform-specifics/ubuntu-linux/

[Never used ardour myself]

[toc] | [prev] | [next] | [standalone]

#197845

On Tue 17 Jul 2018 at 19:57:50 (+0200), 70147persson@telia.com wrote:
> Den 2018-07-12 kl. 00:37, skrev Ric Moore:
> 
> >On 2018-07-11 at 18:38, Kent West wrote:
> >
> > On Wed, Jul 11, 2018 at 2:31 AM, <70147persson@telia.com wrote:
> >
> >     Hi all,
> >
> >     I get no sound. After reinstalling Stretch a couple of months
> >ago, the computer is silent.
> >
> >
> > May be completely unrelated...
> >
> > Since upgrading to the 4.16.16-2 kernel, anytime I reboot my PC I
> >boot into a soundless environment, with my sound system reporting
> >my sound device as the "Dummy Sound Device" (or something
> >similar). I can "sudo kill [timidity's PID]", and that's restores
> >my sound.
> >
> > As I understand it, Timidity is taking exclusive hold of some
> >audio file (/dev/sound ?) early in the boot process which prevents
> >other apps (Pulse, ALSA, etc) from using that file.
> >
> > FWIW.
> >
> > --
> > Kent West
> > Westing Peacefully - http://kentwest.blogspot.com
> 
> >On 07/11/2018 03:31 AM, 70147persson@telia.com wrote:
> >
> >>So is there anyone who can give hints about what I have missed so far?
> >
> >I hate to suggest this on the Debian list, but I installed
> >Ubuntu-Studio to a separate partition which gives you fully
> >functional jack and a real-time kernel to do your studio work
> >with. Pretty darn fast, found my midi in no time and was up and
> >running without the usual beating your head on the keyboard in
> >frustration.
> >
> >I be stupid, ...so I like it simple. Ric
> >
> 
> Thank you Kent and Ric...
> ... for your efforts to solve my sound problems. I did stop
> Timidity, but no, it had no effect. Neither did a reboot. Your hint,
> Ric, to try Ubuntu, well I have not tried that, yet. It was many
> years ago I left that distribution after there decision regarding
> the desktop software Unity. After that Mint (LMDE) for a couple of
> years until I decided to take the full step over to Debian, where I
> am now, and has no plans to leave. OK, your suggestion was to have
> it on a separate partition, but unfortunately I have no left. All
> four primary partitions are occupied by other projects I have and
> have had. Well an partition in the extended one could certainly do,
> but, well, I have not tested yet.
> 
> But when examining my programmes I got what I wanted from
> Frescobaldi with LilyPond, and also from Denemo. Both of them are
> connected via Timidity. If also Ardour will work I have not tested
> yet. VLC is working fine, but never Firefox.
> 
> So I started reading on a support site for Firefox, and found a
> sentence saying that from version 53, you have to use PulseAudio for
> all sound in Firefox. It was like a stab into my back. So, what is
> this? I get a feeling of Microsoft: "Now we are so big that we
> decide what the people can use and do". Has Firefox become so big?

Does this sentence imply that you're running FF53, or are you just
making this comment as an aside? I can only see FF52.9 in the 87
Debian packages matching "firefox".

> Nothing else, I love Firefox, and appreciate really the work all
> these volunteers are doing, but if I cannot get sound from that
> programme the way I prefer, I feel I am forced to look for another
> browser.
> 
> Anyone who knows a way to bypass the announced limitations?

Disclaimer: I'm not running a 4.16.16-2 kernel.

I have no difficulty playing sound on FF52.9, a MIDI file on
audacious, an MP4 video on mplayer, and a youtube video on another
instance of FF running as a different user, all at the same time.
(OK, it's complete cacophony.)

I only have ALSA installed: pulseaudio has always seemed to put more
obstacles in the way rather than being of any help.

The timidity daemon is also running
  755 ?        S      0:00 /usr/bin/timidity -Os -iAD
but AFAIK it's not involved in all that's going on. I'd like to
test that it's performing whatever rôle it's meant to have, so
I'd be interested to know what additional command to run.
I don't have any MIDI hardware (like keyboards) if that's
required. I use LP and have run Fresco but don't routinely use
it. I haven't tried Denemo as LP does all I want (AFAIK).
I don't know how audacious is dealing with the MIDI file.

As for announced limitations, Debian compile FF52.9 thus:
  firefox-esr (52.0.1esr-1) experimental; urgency=medium
    * New upstream release.
    * Fix for mfsa2017-08, also known as CVE-2017-5428.
    * debian/browser.mozconfig.in: Build with --enable-alsa. Closes: #857281.
   -- Mike Hommey <glandium@debian.org>  Sat, 18 Mar 2017 08:27:13 +0900
so I suppose others could do the same for themselves (but keep a
lookout for subsequent security fixes).

Cheers,
David.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web