You are not logged in.
This is my first time on arch linux, i am using gnome and pulseaudio. i managed to fix the dummy device problem using this by putting the bytcr-rt5640 folder from https://github.com/plbossart/UCM/tree/m … tcr-rt5640 into the UCM folder, but now when i unmute the device in alsamixer and try to test the sound or play a video, it first just gives a little pop/crackle, simular to speakers when you start up your pc, but there's no sound, here is some sytem info, i don't really know where to start, so anny help is apreciated. http://www.alsa-project.org/db/?f=45003 … 28521746c8
Offline
If anybody see's this and thinks that i should supply some other information, even if you think you can't help solve it but for other people that come across this thread, please tell me, i don't really know what other info is needed to solve this, and i couldn't find anything helpfull when googling the symptons. All i can tell you is that the moment i play any type of media with audio it give a litle crackle/pop as if the speaker just turned on, and afterwards just stays muted, no other pops/crackles/sounds at all, have reinstalled windows on the device to test if it was a hardware problem, but sound worked with the windows drivers, now i am back on arch and just trying to get it to work. I am starting to get pretty desprate.
Offline
Try blacklisting snd_hdmi_lpe_audio
Offline
Thanks craig, i succesfully blacklisted it as seen here http://www.alsa-project.org/db/?f=30c49 … 4539bcd2c8 but nothing changed and the same problem persists, anything else i could try?
Offline
I think you've tried everything I tried. I blacklisted the module and updated the UCM files. Your ALSA Information Script output is a little different from mine at the APLAY section.
**** List of PLAYBACK Hardware Devices ****
card 0: bytcrrt5640 [bytcr-rt5640], device 0: 3 []
Subdevices: 0/1
Subdevice #0: subdevice #0
card 0: bytcrrt5640 [bytcr-rt5640], device 1: Deep-Buffer Audio (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
I get
**** List of PLAYBACK Hardware Devices ****
card 0: bytcrrt5640 [bytcr-rt5640], device 0: Baytrail Audio (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: bytcrrt5640 [bytcr-rt5640], device 1: Deep-Buffer Audio (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
It's just the bit about Baytrail Audio, and the subdevices.
I didn't have audio, or wireless at all on my machine until one, then the other worked after kernel updates. So it might be a matter of waiting for a new kernel.
Offline
Alright, thanks lad
Offline
One thing I forgot - there is a module parameter that you can set at boot time:
snd-soc-sst-bytcr-rt5640.quirk=
This seems to account for quirks on different machines. This is from bytcr_rt5640.c
static const struct dmi_system_id byt_rt5640_quirk_table[] = {
{
.callback = byt_rt5640_quirk_cb,
.matches = {
DMI_EXACT_MATCH(DMI_SYS_VENDOR, "ASUSTeK COMPUTER INC."),
DMI_EXACT_MATCH(DMI_PRODUCT_NAME, "T100TA"),
},
.driver_data = (void *)(BYT_RT5640_IN1_MAP |
BYT_RT5640_MCLK_EN),
},
{
.callback = byt_rt5640_quirk_cb,
.matches = {
DMI_EXACT_MATCH(DMI_SYS_VENDOR, "ASUSTeK COMPUTER INC."),
DMI_EXACT_MATCH(DMI_PRODUCT_NAME, "T100TAF"),
},
.driver_data = (void *)(BYT_RT5640_IN1_MAP |
BYT_RT5640_MONO_SPEAKER |
BYT_RT5640_DIFF_MIC |
BYT_RT5640_SSP0_AIF2 |
BYT_RT5640_MCLK_EN),
},
{
.callback = byt_rt5640_quirk_cb,
.matches = {
DMI_EXACT_MATCH(DMI_SYS_VENDOR, "DellInc."),
DMI_EXACT_MATCH(DMI_PRODUCT_NAME, "Venue 8 Pro 5830"),
},
.driver_data = (void *)(BYT_RT5640_DMIC2_MAP |
BYT_RT5640_DMIC_EN |
BYT_RT5640_MCLK_EN),
},
{
.callback = byt_rt5640_quirk_cb,
.matches = {
DMI_EXACT_MATCH(DMI_SYS_VENDOR, "Hewlett-Packard"),
DMI_EXACT_MATCH(DMI_PRODUCT_NAME, "HP ElitePad 1000 G2"),
},
.driver_data = (void *)(BYT_RT5640_IN1_MAP |
BYT_RT5640_MCLK_EN),
},
{
.callback = byt_rt5640_quirk_cb,
.matches = {
DMI_MATCH(DMI_SYS_VENDOR, "Circuitco"),
DMI_MATCH(DMI_PRODUCT_NAME, "Minnowboard Max B3 PLATFORM"),
},
.driver_data = (void *)(BYT_RT5640_DMIC1_MAP |
BYT_RT5640_DMIC_EN),
},
{
.callback = byt_rt5640_quirk_cb,
.matches = {
DMI_MATCH(DMI_BOARD_VENDOR, "TECLAST"),
DMI_MATCH(DMI_BOARD_NAME, "tPAD"),
},
.driver_data = (void *)(BYT_RT5640_IN3_MAP |
BYT_RT5640_MCLK_EN |
BYT_RT5640_SSP0_AIF1),
},
{
.callback = byt_rt5640_quirk_cb,
.matches = {
DMI_MATCH(DMI_SYS_VENDOR, "Acer"),
DMI_MATCH(DMI_PRODUCT_NAME, "Aspire SW5-012"),
},
.driver_data = (void *)(BYT_RT5640_IN1_MAP |
BYT_RT5640_MCLK_EN |
BYT_RT5640_SSP0_AIF1),
},
{
.callback = byt_rt5640_quirk_cb,
.matches = {
DMI_MATCH(DMI_SYS_VENDOR, "Insyde"),
},
.driver_data = (void *)(BYT_RT5640_IN3_MAP |
BYT_RT5640_MCLK_EN |
BYT_RT5640_SSP0_AIF1),
},
{}
};
And from near the top of the file:
enum {
BYT_RT5640_DMIC1_MAP,
BYT_RT5640_DMIC2_MAP,
BYT_RT5640_IN1_MAP,
BYT_RT5640_IN3_MAP,
};
#define BYT_RT5640_DMIC_EN BIT(16)
#define BYT_RT5640_MONO_SPEAKER BIT(17)
#define BYT_RT5640_DIFF_MIC BIT(18) /* defaut is single-ended */
#define BYT_RT5640_SSP2_AIF2 BIT(19) /* default is using AIF1 */
#define BYT_RT5640_SSP0_AIF1 BIT(20)
#define BYT_RT5640_SSP0_AIF2 BIT(21)
#define BYT_RT5640_MCLK_EN BIT(22)
#define BYT_RT5640_MCLK_25MHZ BIT(23)
So you could try some of these combinations.
For example, based on the ASUS T100TA data, snd-soc-sst-bytcr-rt5640.quirk=0x400002
I'm not sure how risky this is as far as the hardware is concerned.
Offline
Please use code tags when pasting code: https://wiki.archlinux.org/index.php/Co … s_and_code
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline