-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dell XPS 17 (9710) No Audio #3057
Comments
@mblack154 I see this in your dmesg log: [ 4.655486] sof-audio-pci 0000:00:1f.3: ASoC: physical link SDW3-Capture (id 4) not exist That points to a missing quirk in the machine driver, we typically have to skip some BE IDs to keep consistency across devices. Can you please attach the output of 'sudo dmidecode'? Thanks! |
This device has the same audio subsystem as the 0A5E skew (RT711 headset codec, 2 RT1308 amps and RT715 for mic capture) BugLink: thesofproject#3057 Signed-off-by: Pierre-Louis Bossart <[email protected]>
Here are the files. |
thanks @mblack154 can you try the patch in a312717 You may need to rename the RT711_JD2 as SOF_RT711_JD_SRC_JD2 since a recent commit changed the JD definition. |
Can you send me the build instructions. Have the branch downloaded and replaced the patch file. |
Sorry @mblack154 I don't know what setup you have. can you work with @jason77-wang on this? |
FWIW I use ktest.pl with the instructions listed here: https://thesofproject.github.io/latest/getting_started/setup/setup_ktest_environment.html But if you want to change a specific Ubuntu kernel that's a different story |
Do you have another option? Looks like ktest wants to do this over an ssh connection. Keep current kernel version |
I can contact @jason77-wang |
Thanks Compiling now. Trying with RT711_JD2 first. If that doesn't work will try with SOF_RT711_JD_SRC_JD2. Let you know what happens. |
Hi @mblack154 I am newbie, did the compiling helped. I am also facing the same issue. I can also try to recompile, if there are clear set of instructions |
Hi @mblack154 -- any luck getting your shiny new XPS 9710 booting error-free into Ubuntu 21.04? I have the identical issue. |
Not yet. Get the kernel compiled, but it is locking up on boot. |
I noticed this note on the Ubuntu mainline kernel wiki and I am curious if the out of tree modules are the reason your kernel is not booting: First, if one is using select proprietary or out-of-tree modules (e.g. bcmwl, fglrx, NVIDIA proprietary graphics drivers, VirtualBox, etc.) unless there is an extra package available for the version you are testing, you will need to uninstall the module first, in order to test the mainline kernel. If you do not uninstall these modules first, then the upstream kernel may fail to install, or boot. |
Any idea what is causing this when doing sudo make modules_install (binutils is installed) arch/x86/Makefile:148: CONFIG_X86_X32 enabled but no binutils support |
Are the 32bit libraries and bin utils installed? Did you try disabling 32bit support in the meantime? |
Don't have the 32bit libraries installed but have disable 32bit in the .config file. |
Got the kernel compiled this morning with the patch and I have sound. (5.14-rc2) |
Thanks @mblack154, will send this upstream. |
This device has the same audio subsystem as the 0A5E skew (RT711 headset codec, 2 RT1308 amps and RT715 for mic capture) BugLink: #3057 Signed-off-by: Pierre-Louis Bossart <[email protected]>
@mblack154 I suppose this would be |
This device has the same audio subsystem as the 0A5E skew (RT711 headset codec, 2 RT1308 amps and RT715 for mic capture) BugLink: #3057 Signed-off-by: Pierre-Louis Bossart <[email protected]> Reviewed-by: Kai Vehmanen <[email protected]> Reviewed-by: Ranjani Sridharan <[email protected]> Reviewed-by: Bard Liao <[email protected]> Reviewed-by: FRED OH <[email protected]>
This device has the same audio subsystem as the 0A5E skew (RT711 headset codec, 2 RT1308 amps and RT715 for mic capture) BugLink: thesofproject#3057 Signed-off-by: Pierre-Louis Bossart <[email protected]> Reviewed-by: Kai Vehmanen <[email protected]> Reviewed-by: Ranjani Sridharan <[email protected]> Reviewed-by: Bard Liao <[email protected]> Reviewed-by: FRED OH <[email protected]>
Can't tell you. But fact is, after doing this there appeared more options inside alsamixer and I could configure it properly. |
The Dell 9070 also used SOF before already and required this step, so I don't think it should surprise too much as well. @plbossart |
We have pretty much all Dell devices with SoundWire enabled, and we've never needed this configuration. if you can trace the history and who came up with the information that would be great. ArchWiki has a lot of information but in the case of SOF we routinely find 'surprising' information that isn't aligned with what we test/do. Adding @kv2019i to this thread in case he's got any idea of what this might mean. |
my guess would be just the flag is important |
@wzrdtales try doing a blacklist snd-hda-intel and see what happens. I would bet there is no impact. if you see the SOF driver code, we have a different option with MSI enabled by default. #if IS_ENABLED(CONFIG_SND_SOC_SOF_DEBUG)
static bool hda_use_msi = true;
module_param_named(use_msi, hda_use_msi, bool, 0444);
MODULE_PARM_DESC(use_msi, "SOF HDA use PCI MSI mode");
#else
#define hda_use_msi (1)
#endif |
Avanderbergh made that change though. I will try to blacklist it once and let you know |
ok @plbossart indeed, now if I blacklist or delete that modprobe entry. no difference. mic works and the options appear in alsamixer. Not sure what made this behave that weird. I initially installed alsa-utils which wasn't there before, but since that is no kernel component that shouldn't have had such a weird behavior. Dunno, a lot of things are weird currently on the new Dell 9710. I for example still get a non responding keyboard or trackpad randomly after booting or after some while of usage (didn't figure out yet where this comes from though). So I am surprised about exactly nothing right now... |
@wzrdtales I have a tentative explanation: there is some level of sync between alsa-ctrl and UCM, the former relies on UCM files for initial mixer controls on boot. If you didn't have alsa-ctrl it's possible that the RT715 mixer values present in /usr/share/alsa/ucm2/codecs/rt715/init.conf were not set, and now they are. |
hm might be, but then rather caused by the first change to the rt715 values and the following reboot, rather than installing alsa-utils I guess. Now everything seems to work fine, also the soundwire audio devices did not yet disappear again, but will report back should that happen again. |
Currently seeing the same behavior on a 9700. AFAIK it uses the exact same sound hardware as 9710. Maybe extend quirk to include 9700 as well? |
@szbergeron please attach the results of 'alsa-info' so that we can check if the hardware is different, thanks! |
@plbossart here's the output from alsa-info.sh |
@szbergeron we've had support for the SKU 098F for about two years now, it's a rather classic CometLake device with 2 amplifiers. The card is created alright and you expose the right configuration to userspace. what is the issue you're seeing? The only surprising things I see in your setup is the loopback, not sure why it's needed? and the configuration for servers looks weird
|
@plbossart I get no signal for the built-in microphone or headphone microphone (but get input fine when using a usb headphone dac or wireless earbuds, so I think pw is handling input correctly). If it's off topic for this issue I can make a new one though |
@szbergeron The headset mic is handled by the RT711 chip, and the local mics by the RT715 chips. They are exposed as separate ALSA devices. you can try at the ALSA level by doing something like alsaucm -c sof_sdw set _verb HiFi set _enadev Microphone alsaucm -c sof_sdw set _verb HiFi set _enadev 'Jack In' If you see any activity on the console then it proves my point that userspace is not working. |
@plbossart I don't have an sof_sdw device, only sof-soundwire. On that I don't have any entries in _enadevs to pick from: |
try this @szbergeron alsaucm -c sof-soundwire set _verb HiFi set _enadev Mic |
That does seem to make arecord show terminal activity. Bummer, guess the problem is higher up. |
@szbergeron I would try an update of alsa-ucm-conf and pipewire, it's likely between those two that there is a mismatch. |
@plbossart both are currently running the latest stable version packaged for arch (alsa-ucm-conf 1.2.6.3-1 and pipewire 1:0.3.45-1) so not sure |
mic audio started to break again for me as well... |
https://0bin.net/paste/iDN-m8qZ#cC1ApntGgFpIDVlMNVBcXvXoJ3HuBHp+3ZjPJUNvbqq already downgraded several resources still not functional again with latest components. mic not working, checked under windows to check the mic in general, it works over there. so dunno what broke just now... https://0bin.net/paste/zG5Qs7Kk#dsuCwknU02wozlrmTuVhOv8gx2yd48oN+Wec6Jmwvol |
ok after some research i found a note that told to deactivate and activate audio in the bios. weirdly that helped... |
@wzrdtales can you share your sources, this doesn't seem quite right indeed? |
it doesn't seem right at all. I tried downgrading to packages that I KNOW were working and it still didn't work. So I gave it a shot and to my own surprise... it worked. I found the hint here for the older XPS model: https://unix.stackexchange.com/questions/637992/how-to-fix-xps-9700-microphone-given-audio-is-fixed |
my only guess is I did boot the windows partition which I never use unless I am on travel and once in a while want to consume some HDR content (which unfortunately still is nothing we have under linux :( ). booting into my real system again left the mic disfunctional. So I guess that this was related... |
@wzrdtales pure speculation and possible red-herring: some Dell devices have support for a microphone privacy feature. It's possible that somehow the privacy feature was engaged and the only way to remove it was to toggle the entire audio off/on again. This is clearly not an SOF bug proper, more an issue with the configuration of the external mic codec |
Possible, and possible as well that windows triggers that by default. I will add that to the wiki about the Dell XPS then at least others find the solution faster.
Sent from Nine
…--
Best
--
Tobias Gurtzick
CEO
WizardTales UG (haftungsbeschränkt)
Additional Contacts:
@github | ***@***.***
--
Website: https://www.wizardtales.com
***@***.***
nmlpm: -- coming soon & open source --
Please tag your mails with "request", "issue" or "proposal", unless none of these fit or there already exists a thread.
-- Why should one reach for what one may be capable reaching, that's awfully boring and after all one still be ones yesterday being. --
Sitz der Gesellschaft: Ratingen
Kokkolastr. 5
40882 Ratingen
Germany
Registergericht: Amtsgericht Düsseldorf, HRB 84140
Geschäftsführer: Tobias Gurtzick
________________________________
Von: Pierre-Louis Bossart ***@***.***>
Gesendet: Donnerstag, 17. Februar 2022 02:52
An: thesofproject/linux
Cc: Tobias Gurtzick; Mention
Betreff: Re: [thesofproject/linux] Dell XPS 17 (9710) No Audio (#3057)
@wzrdtales pure speculation and possible red-herring: some Dell devices have support for a microphone privacy feature. It's possible that somehow the privacy feature was engaged and the only way to remove it was to toggle the entire audio off/on again. This is clearly not an SOF bug proper, more an issue with the configuration of the external mic codec
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
File bug with Ubuntu #1935850. https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850
Filing bug based on last comment:
According to #15, it looks like the topology file is not suitable for this machine.
Please file a bug to Intel/sof, let Intel engineers take a look at this issue.
https://github.com/thesofproject/linux/issues/new
Let me know what other info you need.
Running Ubuntu 21.04
The text was updated successfully, but these errors were encountered: