RDP Thinbook 1130 (bytcr-rt5651): LOUD annoying high pitched sound + no headphone output on kernel 4.17 (only) at boot

[sundarnagarajan]

The laptop is the 11-inch RDP Thinbook 1130. It seems to be now called RDP 1130-EC1. They also have a model 1430-EC-L sold with Linux pre-installed. The 11-inch RDP Thinbook 1130 has a 64-bit UEFI loader and uses an Intel Atom x5-Z8350 Cherry Trail SoC.

I have been working closely with this company to get the hardware working on Linux - mostly by writing a set of ISO-remastering scripts that can compile a recent kernel, and put in a few user-space scripts. You can find my github repo here.

Sound works, BUT:

• There's a fair amount of 'crackle': following combinations tested
  - Ubuntu 16.04/kernel 4.13.9
  - Ubuntu 18.04/kernel 4.16.18
  - Ubuntu 18.04/kernel 4.17.5
• ONLY when using kernel 4.17+, there is a VERY LOUD (maximum volume?) high pitched sound during boot - that sounds like what you would get with terrible feedback. It lasts for about 10 seconds and then subsides. After that (after boot is complete):
  - Sound through speakers works
  - Only 'Speaker playback - Built-in Audio' is shown under Sound --> Settings. Under kernel < 4.17 I could choose between speakers and headphone

I am attaching the output of alsa-info
rdp-1130-alsa-info-kernel-4.17.5.txt

I have also uploaded the output of alsa-info.

Attached are HiFi.conf and bytcr-rt5651.conf from /usr/share/alsa/usm/bytcht-rt5651:

rdp-1130-HiFi.conf.txt
rdp-1130-bytcr-rt5651.conf.txt

When running alsa-info, I get the following error:

cat:  '/sys/module/snd_soc_sst_bytcr_rt5651/parameters/*': No such file or directory

I am able and willing to perform various tests on this laptop. Please help me figure out what is worng and what needs to be done.

[plbossart]

You probably want to look at all the patches posted @jwrdegoede on alsa-devel, it's very likely that the kernel you are using isn't up to snuff.

[sundarnagarajan]

I am using the latest released kernel 4.17.5. By "kernel you are using isn't up to snuff" you mean: - I need additional patches? - I need to DISABLE specific modules - I use compile-as-module if available and default choice if compile-as-module is not available Is there any idiot-proof instructions for turning on any form of debug for ALSA to get more information that may show what is wrong with my kernel? Do Hans' patches usually go into linux-next? Where do I find the patches to try?

…

On Mon, Jul 9, 2018 at 3:35 PM Pierre Bossart ***@***.***> wrote: You probably want to look at all the patches posted @jwrdegoede <https://github.com/jwrdegoede> on alsa-devel, it's very likely that the kernel you are using isn't up to snuff. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#43 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALaty44yPj-wGeP__OvavmHSLo6P2giLks5uE9qbgaJpZM4VIYds> .

[plbossart]

On 07/09/2018 06:19 PM, sundarnagarajan wrote: I am using the latest released kernel 4.17.5. By "kernel you are using isn't up to snuff" you mean: - I need additional patches?

yes

- I need to DISABLE specific modules - I use compile-as-module if available and default choice if compile-as-module is not available Is there any idiot-proof instructions for turning on any form of debug for ALSA to get more information that may show what is wrong with my kernel? Do Hans' patches usually go into linux-next? Where do I find the patches to try?

There were patches on alsa-devel that I just ack'ed moments ago. Chances are it's going to linux-next shortly, you probably want to work with Hans directly.

…

On Mon, Jul 9, 2018 at 3:35 PM Pierre Bossart ***@***.***> wrote: > You probably want to look at all the patches posted @jwrdegoede > <https://github.com/jwrdegoede> on alsa-devel, it's very likely that the > kernel you are using isn't up to snuff. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#43 (comment)>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/ALaty44yPj-wGeP__OvavmHSLo6P2giLks5uE9qbgaJpZM4VIYds> > . > — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#43 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABGIa9kHYOeMmu3XwAVpJvt8zW-Lt_Bdks5uE-TvgaJpZM4VIYds>.

[sundarnagarajan]

Thank you for the help!. I see the patches you acknowledged just now on alsa-devel. I am not very experienced in extracting the patches from email, so I am trying the current linux-next. If it doesn't work, I will watch for Hans' latest bytcr_rt5651 patches getting merged into linux-next and try again once they are merged. What's the best way to reach out to Hans? On Mon, Jul 9, 2018 at 4:56 PM Pierre Bossart <[email protected]> wrote:

…

On 07/09/2018 06:19 PM, sundarnagarajan wrote: > I am using the latest released kernel 4.17.5. > > By "kernel you are using isn't up to snuff" you mean: > > - I need additional patches? yes > - I need to DISABLE specific modules - I use compile-as-module if > available and default choice if compile-as-module is not available > > Is there any idiot-proof instructions for turning on any form of debug for > ALSA to get more information that may show what is wrong with my kernel? > > Do Hans' patches usually go into linux-next? Where do I find the > patches to > try? There were patches on alsa-devel that I just ack'ed moments ago. Chances are it's going to linux-next shortly, you probably want to work with Hans directly. > > > On Mon, Jul 9, 2018 at 3:35 PM Pierre Bossart ***@***.***> > wrote: > > > You probably want to look at all the patches posted @jwrdegoede > > <https://github.com/jwrdegoede> on alsa-devel, it's very likely that the > > kernel you are using isn't up to snuff. > > > > — > > You are receiving this because you authored the thread. > > Reply to this email directly, view it on GitHub > > <#43 (comment)>, > or mute > > the thread > > > < https://github.com/notifications/unsubscribe-auth/ALaty44yPj-wGeP__OvavmHSLo6P2giLks5uE9qbgaJpZM4VIYds > > > . > > > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <#43 (comment)>, > or mute the thread > < https://github.com/notifications/unsubscribe-auth/ABGIa9kHYOeMmu3XwAVpJvt8zW-Lt_Bdks5uE-TvgaJpZM4VIYds >. > — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#43 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALaty9sTKC_9h4P9Mqb0mvLzg3O5S1Jdks5uE-2lgaJpZM4VIYds> .