[Bug 1872244] Re: Jack audio not working on Ubuntu 20.04 running on a Thinkpad Carbon X1 (7th gen)

2021-05-27 Thread Andrew Bailey
Hi Im still affected by this and know of no workaround. So as this bug report got downgraded to a question I submitted a bug, Bug #1927802 to see if we can get a fix. Please follow the new bug report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1872244] Re: Jack audio not working on Ubuntu 20.04 running on a Thinkpad Carbon X1 (7th gen)

2021-04-24 Thread Andrew Bailey
Please can you look into this. It has been marked as Invalid, however, it is not a support request as has been assumed. My card is a card 1: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) [] Subdevices: 0/1 Subdevice #0: subdevice #0 uname -a Linux rtx 5.8.0-50-generic #56~20.04.1-Ubuntu

[Bug 1872244] Re: Jack audio not working on Ubuntu 20.04 running on a Thinkpad Carbon X1 (7th gen)

2021-04-21 Thread apienk
Daniel, thanks for the workaround! It works! I can confirm that JACK not starting on SOF can be fixed by just setting the period to 1008 or 2040. I'm on Dell G5. However, JACK with such a setup is completely unusable for me. All applications produce noise instead of proper sound, probably

[Bug 1872244] Re: Jack audio not working on Ubuntu 20.04 running on a Thinkpad Carbon X1 (7th gen)

2020-09-13 Thread Daniel Zrlrink
Hi all, I think we're confusing OP, who is using the correct 7th gen audio interface, with someone who chimed in with their 2nd gen audio interface aplay results. I've got a solution. The period that this driver uses is an EXTREMELY non-standard 1008 samples. I discovered this by making a dummy

[Bug 1872244] Re: Jack audio not working on Ubuntu 20.04 running on a Thinkpad Carbon X1 (7th gen)

2020-08-16 Thread Ross Gammon
Just a tip. The best thing to do when it is a support request rather than a bug, is to convert it to a question. See the option near the top-right. I will do it. ** Changed in: jackd-defaults (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a

[Bug 1872244] Re: Jack audio not working on Ubuntu 20.04 running on a Thinkpad Carbon X1 (7th gen)

2020-08-16 Thread Ross Gammon
This seems like a support request, rather than a bug. Let us know if Len's suggestion helps. ** Changed in: jackd-defaults (Ubuntu) Status: Confirmed => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/jackd-defaults/+question/692397 -- You received this

[Bug 1872244] Re: Jack audio not working on Ubuntu 20.04 running on a Thinkpad Carbon X1 (7th gen)

2020-08-15 Thread Erich Eickmeyer
Based on Len's response, this seems more like a support request. As such, per Launchpad policy, this does not belong on a bug tracker. Please use appropriate support forums, such as askubuntu.com, in the future. ** Changed in: jackd-defaults (Ubuntu) Status: Confirmed => Invalid -- You

[Bug 1872244] Re: Jack audio not working on Ubuntu 20.04 running on a Thinkpad Carbon X1 (7th gen)

2020-08-15 Thread Len Ovens
"internal audio interface (hw:sofhdadsp)" I am wondering where you got the "hw:sofhdadsp" from was PCH,0,0 not listed? from your output of aplay -l it would seem the device you want is hw:PCH,0,0 or just hw:PCH even. -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1872244] Re: Jack audio not working on Ubuntu 20.04 running on a Thinkpad Carbon X1 (7th gen)

2020-04-20 Thread John Andersen
So in digging through this I got mine working. I am on a 2nd Gen X1 Carbon and have been getting the same error. At least in my case it seems alsa is not selecting the correct audio device, preventing jackd from starting. When run manually it works: I listed my alsa devices with this: $aplay

[Bug 1872244] Re: Jack audio not working on Ubuntu 20.04 running on a Thinkpad Carbon X1 (7th gen)

2020-04-20 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: jackd-defaults (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872244