Jack fails to start

What other apps and distros do you use to round out your studio?

Moderators: khz, MattKingUSA

User avatar
thetotalchaos
Established Member
Posts: 186
Joined: Mon Sep 29, 2014 8:29 pm
Contact:

Re: Jack fails to start

Post by thetotalchaos »

@redu
If you now have the packages, i mentioned above, i suggest you to go back to qjackctl. Try to disable/change the capture device. The log says that it cannot initialize capture device. So try at first to start Jack on playback only.

@Kott
I am maybe old-school, to have much higher demanding settings, than needed. :|
But i know that you cannot recreate the values, from the screenshot below. The difference of bothering to tweak the system and use Linux-RT.
And you don't need to demand such behavior from your computer, but i do. And Linux really allows me.
And by the way, you are using Jack2 (1.9.12) :roll:

Image
Check out my latest music album Le Femme Robotique 2021
https://totalchaos-music.bandcamp.com/a ... -viii-2006
Kott
Established Member
Posts: 395
Joined: Thu Mar 21, 2013 12:55 am
Location: Vladivostok

Re: Jack fails to start

Post by Kott »

thetotalchaos wrote: Fri Jun 12, 2020 9:37 pm
And by the way, you are using Jack2 (1.9.12) :roll:

Code: Select all

jackd -dalsa -p 32 -dhw:1,0
jackd 0.125.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details

JACK compiled with System V SHM support.
loading driver ..
creating alsa driver ... hw:1,0|hw:1,0|32|2|48000|0|0|nomon|swmeter|-|32bit
configuring for 48000Hz, period = 32 frames (0.7 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback
redu
Established Member
Posts: 24
Joined: Tue Mar 10, 2015 3:33 pm

Re: Jack fails to start

Post by redu »

https://bugs.launchpad.net/ubuntu/+sour ... ug/1872244
It's a bug!
Johan Andersen proposed here a fix, but it doesn't help in my case.
redu
Established Member
Posts: 24
Joined: Tue Mar 10, 2015 3:33 pm

Re: Jack fails to start

Post by redu »

Accidentally:

hw:sofhdadsp turned in my laptop to hw:PCH

This happened for instance in Qjackctl / Output device and Input device boxes.
Jack server now starts!

Also
jackd -d alsa -d hw:0
now starts Jack.

[Solved]

But what actually happened? I would like to understand, as one more "Cannon Point-LP-laptop" should be fixed the same way?

At the moment of this weird turn over, I kept playing with the Alsamixer app.

Anyone? What is this?
merlyn
Established Member
Posts: 767
Joined: Thu Oct 11, 2018 4:13 pm

Re: Jack fails to start

Post by merlyn »

In an earlier post you got this from aplay -l :

Code: Select all

edu@ENVY2:~$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) []
Is that what you still get? To get something different would seem weird unless you updated your kernel and got a new module that recognises 'sofhdadsp' and gives it a more generic name.

If it works on one machine logic would suggest it will work on another machine with the same sound hardware. I'm not sure how relevant a Cannon Point chipset is. What is relevant is this 'sofhdadsp' sound chip.
The ultimate hidden truth of the world is that we make it, and could just as easily make it differently.
redu
Established Member
Posts: 24
Joined: Tue Mar 10, 2015 3:33 pm

Re: Jack fails to start

Post by redu »

Yes, it was changed:

redu@Yoga-C740-15IML:~$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
etc ....

Kernel was not changed.

Settings / Sound / Input is now grayed out. Video play-back works, but microphone and other input devices??
redu
Established Member
Posts: 24
Joined: Tue Mar 10, 2015 3:33 pm

Re: Jack fails to start

Post by redu »

Learned later, that this line
options snd-intel-dspcfg dsp_drivers=1
was added to /etc/modprobe.d/alsa-base.conf

Nice, but now microphone was muted. There is nothing in Settings/Sound/input drvices.
merlyn
Established Member
Posts: 767
Joined: Thu Oct 11, 2018 4:13 pm

Re: Jack fails to start

Post by merlyn »

When you use JACK do you get inputs and outputs?

You can see if ALSA recognises inputs with :

Code: Select all

$ arecord -l
The ultimate hidden truth of the world is that we make it, and could just as easily make it differently.
User avatar
nikgnomicradio
Established Member
Posts: 97
Joined: Wed Feb 07, 2018 9:31 pm
Contact:

Re: Jack fails to start

Post by nikgnomicradio »

modprobe option snd-intel-dspcfg dsp_drivers=1
replaced an earlier modprobe option snd_hda_intel.dmic_detect=0
https://bugzilla.kernel.org/show_bug.cgi?id=205959#c4
both options disable the internal digital microphones so that the rest of the audio codec works with Legacy driver snd_hda_intel

Legacy driver snd_hda_intel does not support the new Intel SST DMIC microphone array but should support a headset or similar analog microphone

there appears to be only a feature request posted about use of JACK on the SOF github site
https://github.com/thesofproject/sof/issues/2572
redu
Established Member
Posts: 24
Joined: Tue Mar 10, 2015 3:33 pm

Re: Jack fails to start

Post by redu »

nikgnomicradio,
agreed fully!
1.
Today I can manage with PCH drivers and headphone mic.
2.
Hopefully sndhsdpa gets fixed in kernel some day. Now inside mic works, but jack server refuses to co-operate.

Many thanks for good discussions!
Post Reply