Re: No sound on gpd pocket 3
On 1/24/22 12:35, anthony tonitch wrote:
HO, I'm really sorry, I did this alsa-info from my main computer over ssh and I might have typed the command on the wrong terminal :'( here it is http://alsa-project.org/db/?f=8ec2e745ceafb1a659d71eff99ad3a9eda3eb62d
ah, now it's starting to make sense.
I am afraid you have the ES8316 codec, or one of its variants. /sys/bus/acpi/devices/ESSX8326:00/status 15
so no you don't want to use options snd-intel-dspcfg dsp_driver=1 but
options snd-intel-dspcfg dsp_driver=3
The auto-detection don't work because we use a different codec HID for the driver selection
{ .flags = FLAG_SOF, .device = 0x5a98, .codec_hid = "ESSX8336", },
as well as the machine driver selection
{ .id = "ESSX8336", .drv_name = "sof-essx8336", .sof_tplg_filename = "sof-glk-es8336.tplg", },
This is really a problematic set of devices, where absolutely all possible I2S links have been used, along with GPIO settings and DMICs.
Please file a bug on https://github.com/thesofproject/linux/issues so that we can keep track of this and suggest solution.
Thanks!
Le lun. 24 janv. 2022 à 18:11, Pierre-Louis Bossart pierre-louis.bossart@linux.intel.com a écrit :
On 1/24/22 10:52, anthony tonitch wrote:
Hello,
I have a problem I guess related to sof... I already asked on the irc #alsa@libera.chat and gnarface advised me to come and ask on this mailing list!
using "options snd-intel-dspcfg dsp_driver=1" to avoid using SOF isn't very helpful on an AMD platform :-)
08:00.1 Audio device [0403]: NVIDIA Corporation GP104 High Definition Audio Controller [10de:10f0] (rev a1) Subsystem: PNY Device [196e:11a0] 0a:00.3 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller [1022:1457] Subsystem: ASUSTeK Computer Inc. Device [1043:86c7]
Best of luck!
I am struggling to make the sound of my gpd pocket 3 to work on linux (archlinux to be precise)! In fact, the sound is not supposed to work out of the box as other users tested it before me! but they all had the solution to set the dsp_driver and this didn't worked for me! I checked several times to see if the module was loaded properly and yes it is (as you can also check in the alsa-info at the end of the mail)!
If I do aplay -l I get a bunch of hdmi connection that is not working at all! I'm really lost here and I don't even know what to look for anymore
The sound works great on windows so This doens't seems to be hardware problem ?! and I tried to plug an usb headset which give me sound so I doesn't seems to be config related either ?! (tho the jack doesn't work)
I asked on several places already. I post the different links here in case you want to check but I don't have any response to any post unfortunately!
- Post on Archlinux BBS: https://bbs.archlinux.org/viewtopic.php?id=273044
- Post on subreddit GPDPocket:
https://www.reddit.com/r/GPDPocket/comments/s31qi8/gpd_p3_no_sound_linux/
- Screenshot and bios picture of maybe relevant informations:
I hope there is enough informations to help me debug this but if you need anything I can provide it! this is a small pc and I'm usualy quarrying it around! I know this is better to send mail but if you need me to chat for any reason (it would be easier for instance) I'm usually hanging on the libera.chat irc as tonitch you can pm or tag me on #alsa
Here is the alsa-info.sh : http://alsa-project.org/db/?f=6ddb669a19086cebdb121c97c25bbdccb98e856d
Thanks a lot for your help!
PS: Ubuntu mate have released their official pocket 3 distribution and I tried it but the sound didn't worked either, here is the alsa-info In case this help ?! : http://alsa-project.org/db/?f=df4c183fd00cec224006ec8caa228705399ad873
Le lun. 24 janv. 2022 à 20:02, Pierre-Louis Bossart pierre-louis.bossart@linux.intel.com a écrit :
ah, now it's starting to make sense.
I am afraid you have the ES8316 codec, or one of its variants. /sys/bus/acpi/devices/ESSX8326:00/status 15
so no you don't want to use options snd-intel-dspcfg dsp_driver=1 but
options snd-intel-dspcfg dsp_driver=3
The auto-detection don't work because we use a different codec HID for the driver selection
{ .flags = FLAG_SOF, .device = 0x5a98, .codec_hid = "ESSX8336", },as well as the machine driver selection
{ .id = "ESSX8336", .drv_name = "sof-essx8336", .sof_tplg_filename = "sof-glk-es8336.tplg", },This is really a problematic set of devices, where absolutely all possible I2S links have been used, along with GPIO settings and DMICs.
Please file a bug on https://github.com/thesofproject/linux/issues so that we can keep track of this and suggest solution.
Thanks!
I will file the bug issue later in the day but I have two question here,
1. does the dsp_driver=3 is supposed to work then because it doesn't seems to ^^ maybe I did it wrong but here is the alsa info again if you see anything http://alsa-project.org/db/?f=847cdba9058170337515f57b460ed7bcae964af7
2. Because it works for everyone else and not for me, does this mean the chip is different and then that I have a "faulty one"? I will obviously still try to make the sound work if I can but at least I can contact gpd hk for an explaination
Thanks a lot for your quick response!
On 1/25/22 03:07, anthony tonitch wrote:
Le lun. 24 janv. 2022 à 20:02, Pierre-Louis Bossart pierre-louis.bossart@linux.intel.com a écrit :
ah, now it's starting to make sense.
I am afraid you have the ES8316 codec, or one of its variants. /sys/bus/acpi/devices/ESSX8326:00/status 15
so no you don't want to use options snd-intel-dspcfg dsp_driver=1 but
options snd-intel-dspcfg dsp_driver=3
The auto-detection don't work because we use a different codec HID for the driver selection
{ .flags = FLAG_SOF, .device = 0x5a98, .codec_hid = "ESSX8336", },as well as the machine driver selection
{ .id = "ESSX8336", .drv_name = "sof-essx8336", .sof_tplg_filename = "sof-glk-es8336.tplg", },This is really a problematic set of devices, where absolutely all possible I2S links have been used, along with GPIO settings and DMICs.
Please file a bug on https://github.com/thesofproject/linux/issues so that we can keep track of this and suggest solution.
Thanks!
I will file the bug issue later in the day but I have two question here,
- does the dsp_driver=3 is supposed to work then because it doesn't
seems to ^^ maybe I did it wrong but here is the alsa info again if you see anything http://alsa-project.org/db/?f=847cdba9058170337515f57b460ed7bcae964af7
- Because it works for everyone else and not for me, does this mean
the chip is different and then that I have a "faulty one"? I will obviously still try to make the sound work if I can but at least I can contact gpd hk for an explaination
Thanks a lot for your quick response!
All the solutions we suggested will not work because of a change in your BIOS. We've only see "ESSX8336" so far and hard-coded this value, now the BIOS writers in their infinite wisdom chose a different HID (ESSX8326) which breaks all the existing matching.
if you can install a new kernel, please try and provide feedback on https://github.com/thesofproject/linux/pull/3338, where I added support for more BIOS variations of the same device. I don't have any hardware to test so have to crowd-source the tests to the community, thanks for your understanding if this isn't a turn-key solution.
I made the isuue here https://github.com/thesofproject/linux/issues/3393
I will be happy to test and give you feedback but I'm currently not at my home and downloading takes forever I will try this as soon as I can
can I get you any info on my bios ? as you might have seen on the first sent mail, there is some screen capture of my bios with things I though was relevant but maybe I have to look elsewhere ?
Le mar. 25 janv. 2022 à 16:41, Pierre-Louis Bossart pierre-louis.bossart@linux.intel.com a écrit :
On 1/25/22 03:07, anthony tonitch wrote:
Le lun. 24 janv. 2022 à 20:02, Pierre-Louis Bossart pierre-louis.bossart@linux.intel.com a écrit :
ah, now it's starting to make sense.
I am afraid you have the ES8316 codec, or one of its variants. /sys/bus/acpi/devices/ESSX8326:00/status 15
so no you don't want to use options snd-intel-dspcfg dsp_driver=1 but
options snd-intel-dspcfg dsp_driver=3
The auto-detection don't work because we use a different codec HID for the driver selection
{ .flags = FLAG_SOF, .device = 0x5a98, .codec_hid = "ESSX8336", },as well as the machine driver selection
{ .id = "ESSX8336", .drv_name = "sof-essx8336", .sof_tplg_filename = "sof-glk-es8336.tplg", },This is really a problematic set of devices, where absolutely all possible I2S links have been used, along with GPIO settings and DMICs.
Please file a bug on https://github.com/thesofproject/linux/issues so that we can keep track of this and suggest solution.
Thanks!
I will file the bug issue later in the day but I have two question here,
- does the dsp_driver=3 is supposed to work then because it doesn't
seems to ^^ maybe I did it wrong but here is the alsa info again if you see anything http://alsa-project.org/db/?f=847cdba9058170337515f57b460ed7bcae964af7
- Because it works for everyone else and not for me, does this mean
the chip is different and then that I have a "faulty one"? I will obviously still try to make the sound work if I can but at least I can contact gpd hk for an explaination
Thanks a lot for your quick response!
All the solutions we suggested will not work because of a change in your BIOS. We've only see "ESSX8336" so far and hard-coded this value, now the BIOS writers in their infinite wisdom chose a different HID (ESSX8326) which breaks all the existing matching.
if you can install a new kernel, please try and provide feedback on https://github.com/thesofproject/linux/pull/3338, where I added support for more BIOS variations of the same device. I don't have any hardware to test so have to crowd-source the tests to the community, thanks for your understanding if this isn't a turn-key solution.
FWIW, I did installed your branch kernel and the sound wasn't working, however shutting down my computer made a segfault error but this is the first time I'm compilling a kernel by myself so It could really be my fault here!
Le mar. 25 janv. 2022 à 17:12, anthony tonitch d.tonitch@gmail.com a écrit :
I made the isuue here https://github.com/thesofproject/linux/issues/3393
I will be happy to test and give you feedback but I'm currently not at my home and downloading takes forever I will try this as soon as I can
can I get you any info on my bios ? as you might have seen on the first sent mail, there is some screen capture of my bios with things I though was relevant but maybe I have to look elsewhere ?
Le mar. 25 janv. 2022 à 16:41, Pierre-Louis Bossart pierre-louis.bossart@linux.intel.com a écrit :
On 1/25/22 03:07, anthony tonitch wrote:
Le lun. 24 janv. 2022 à 20:02, Pierre-Louis Bossart pierre-louis.bossart@linux.intel.com a écrit :
ah, now it's starting to make sense.
I am afraid you have the ES8316 codec, or one of its variants. /sys/bus/acpi/devices/ESSX8326:00/status 15
so no you don't want to use options snd-intel-dspcfg dsp_driver=1 but
options snd-intel-dspcfg dsp_driver=3
The auto-detection don't work because we use a different codec HID for the driver selection
{ .flags = FLAG_SOF, .device = 0x5a98, .codec_hid = "ESSX8336", },as well as the machine driver selection
{ .id = "ESSX8336", .drv_name = "sof-essx8336", .sof_tplg_filename = "sof-glk-es8336.tplg", },This is really a problematic set of devices, where absolutely all possible I2S links have been used, along with GPIO settings and DMICs.
Please file a bug on https://github.com/thesofproject/linux/issues so that we can keep track of this and suggest solution.
Thanks!
I will file the bug issue later in the day but I have two question here,
- does the dsp_driver=3 is supposed to work then because it doesn't
seems to ^^ maybe I did it wrong but here is the alsa info again if you see anything http://alsa-project.org/db/?f=847cdba9058170337515f57b460ed7bcae964af7
- Because it works for everyone else and not for me, does this mean
the chip is different and then that I have a "faulty one"? I will obviously still try to make the sound work if I can but at least I can contact gpd hk for an explaination
Thanks a lot for your quick response!
All the solutions we suggested will not work because of a change in your BIOS. We've only see "ESSX8336" so far and hard-coded this value, now the BIOS writers in their infinite wisdom chose a different HID (ESSX8326) which breaks all the existing matching.
if you can install a new kernel, please try and provide feedback on https://github.com/thesofproject/linux/pull/3338, where I added support for more BIOS variations of the same device. I don't have any hardware to test so have to crowd-source the tests to the community, thanks for your understanding if this isn't a turn-key solution.
participants (2)
-
anthony tonitch -
Pierre-Louis Bossart