Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Acer Chromebook 15 CB3-532 Debian Testing microphone not working
101 views
Skip to first unread message
Alexander van der Leun
Nov 7, 2021, 10:00:03 AM11/7/21
to
Hi all,
This week I converted an Acer Chromebook 15 CB3-532 from ChromeOS to Debian
Testing. Mostly everything worked correctly out of the box. After some
fiddling I got video acceleration working and Gnome now works 95% okay;
still some problems with playing video in Google Chrome, but that's okay
for now.
What's not working at the moment is the microphone. Or, better worded, it
only records noise when using arecord.
This is the hardware:
card 1: chtrt5650 [chtrt5650], device 0: 3 []
Subdevices: 0/1
Subdevice #0: subdevice #0
card 1: chtrt5650 [chtrt5650], device 1: Deep-Buffer Audio (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
Using alsamixer, I put the recording volume way up, but still only noise.
I've followed a couple of forum posts on the internet with people having
the same problem (with the same hardware), but nothing works. I've taken a few
configuration files from GalliumOS for my notebook, but that also didn't make
the microphone work.
That's why I want to start with a fresh approach, but don't know where
to start. I've been away from Linux on the desktop for quite some years
and things have changed, such as Alsa UCM and PipeWire. AFAIK,
PulseAudio is still in someway involved with the audio on Debian
Testing, as pavucontrol works.
Can someone point my out to where I should start searching for a solution?
Let me know if more information is required.
Thank you.
Best regards,
Alexander
This week I converted an Acer Chromebook 15 CB3-532 from ChromeOS to Debian
Testing. Mostly everything worked correctly out of the box. After some
fiddling I got video acceleration working and Gnome now works 95% okay;
still some problems with playing video in Google Chrome, but that's okay
for now.
What's not working at the moment is the microphone. Or, better worded, it
only records noise when using arecord.
This is the hardware:
card 1: chtrt5650 [chtrt5650], device 0: 3 []
Subdevices: 0/1
Subdevice #0: subdevice #0
card 1: chtrt5650 [chtrt5650], device 1: Deep-Buffer Audio (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
Using alsamixer, I put the recording volume way up, but still only noise.
I've followed a couple of forum posts on the internet with people having
the same problem (with the same hardware), but nothing works. I've taken a few
configuration files from GalliumOS for my notebook, but that also didn't make
the microphone work.
That's why I want to start with a fresh approach, but don't know where
to start. I've been away from Linux on the desktop for quite some years
and things have changed, such as Alsa UCM and PipeWire. AFAIK,
PulseAudio is still in someway involved with the audio on Debian
Testing, as pavucontrol works.
Can someone point my out to where I should start searching for a solution?
Let me know if more information is required.
Thank you.
Best regards,
Alexander
Dekks Herton
Nov 9, 2021, 12:50:02 AM11/9/21
to
1 - Unless you want to use Debian Sid forget Pipewire, it went through a
lot of work in a short period after lauching as default in Fedora just
before Bullseye launched and the latest releases will never see
Bullseye.
2 - If Pavucontrol works in Testing does it work in Bullseye?
3 - This Chromebook uses an old Intel CPU based on Braswell which Intel recently
rewrote the sound driver to use Intel_captpt driver. Is the soundcard
using captpt or snd_hda_intel?
Regards......
Alexander van der Leun
Nov 9, 2021, 9:00:03 AM11/9/21
to
Hi Dekks Herton,
On Tue, Nov 09, 2021 at 05:44:08AM +0000, Dekks Herton wrote:
>
> 1 - Unless you want to use Debian Sid forget Pipewire, it went through a
> lot of work in a short period after lauching as default in Fedora just
> before Bullseye launched and the latest releases will never see
> Bullseye.
I'm using Bookworm/Testing? Doesn't Testing get the packages from Sid after
a couple of days?
> 2 - If Pavucontrol works in Testing does it work in Bullseye?
No idea, I'm not running Bullseye. Pavucontrol is working and I have apt purged
PulseAudio as suggested in a previous post.
> 3 - This Chromebook uses an old Intel CPU based on Braswell which Intel recently
> rewrote the sound driver to use Intel_captpt driver. Is the soundcard
> using captpt or snd_hda_intel?
The soundcard uses snd_hda_intel. The current kernel 5.14.0-2-amd64 seems not to
have a module named captpt. Where can I read more about this rewrite? A Google
search doesn't seem to come up with much.
>
> Regards......
>
Best regards,
Alexander
On Tue, Nov 09, 2021 at 05:44:08AM +0000, Dekks Herton wrote:
>
> 1 - Unless you want to use Debian Sid forget Pipewire, it went through a
> lot of work in a short period after lauching as default in Fedora just
> before Bullseye launched and the latest releases will never see
> Bullseye.
a couple of days?
> 2 - If Pavucontrol works in Testing does it work in Bullseye?
PulseAudio as suggested in a previous post.
> 3 - This Chromebook uses an old Intel CPU based on Braswell which Intel recently
> rewrote the sound driver to use Intel_captpt driver. Is the soundcard
> using captpt or snd_hda_intel?
have a module named captpt. Where can I read more about this rewrite? A Google
search doesn't seem to come up with much.
>
> Regards......
>
Best regards,
Alexander
Alexander van der Leun
Nov 10, 2021, 4:30:03 PM11/10/21
to
Also blacklisted the snd_hda_intel and rt5650 drivers. But still no output
in the kernel logs or aplay -l finding sound cards.
Does this driver really work on this hardware:
# lshw
linuxbook
description: Laptop
product: Banon
vendor: GOOGLE
version: 1.0
width: 64 bits
capabilities: smbios-3.3.0 dmi-3.3.0 smp vsyscall32
configuration: boot=normal chassis=laptop family=Intel_Strago
*-core
description: Motherboard
product: Banon
vendor: GOOGLE
physical id: 0
version: 1.0
*-firmware
description: BIOS
vendor: coreboot
physical id: 0
version: MrChromebox-4.14
date: 07/25/2021
size: 1MiB
capacity: 8MiB
capabilities: pci pcmcia upgrade bootselect acpi
*-cpu
description: CPU
product: Intel(R) Celeron(R) CPU N3060 @ 1.60GHz
vendor: Intel Corp.
physical id: 4
bus info: cpu@0
version: 6.76.4
slot: CPU0
size: 580MHz
capacity: 2480MHz
width: 64 bits
capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl xtopology tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch epb pti ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat md_clear cpufreq
configuration: cores=2 enabledcores=2 microcode=1041 threads=2
Dekks Herton
Nov 12, 2021, 12:30:02 AM11/12/21
to
Alexander van der Leun <al...@vdleun.net> writes:
> Hi Dekks Herton,
>
> On Tue, Nov 09, 2021 at 05:44:08AM +0000, Dekks Herton wrote:
>>
>> 1 - Unless you want to use Debian Sid forget Pipewire, it went through a
>> lot of work in a short period after lauching as default in Fedora just
>> before Bullseye launched and the latest releases will never see
>> Bullseye.
>
> I'm using Bookworm/Testing? Doesn't Testing get the packages from Sid after
> a couple of days?
No idea, just know Pipewire's current dev pattern isn't suited to
> Hi Dekks Herton,
>
> On Tue, Nov 09, 2021 at 05:44:08AM +0000, Dekks Herton wrote:
>>
>> 1 - Unless you want to use Debian Sid forget Pipewire, it went through a
>> lot of work in a short period after lauching as default in Fedora just
>> before Bullseye launched and the latest releases will never see
>> Bullseye.
>
> I'm using Bookworm/Testing? Doesn't Testing get the packages from Sid after
> a couple of days?
Debian's dev model
>
>> 2 - If Pavucontrol works in Testing does it work in Bullseye?
>
> No idea, I'm not running Bullseye. Pavucontrol is working and I have apt purged
> PulseAudio as suggested in a previous post.
>
>
>> 3 - This Chromebook uses an old Intel CPU based on Braswell which Intel recently
>> rewrote the sound driver to use Intel_captpt driver. Is the soundcard
>> using captpt or snd_hda_intel?
>
> The soundcard uses snd_hda_intel. The current kernel 5.14.0-2-amd64 seems not to
> have a module named captpt. Where can I read more about this rewrite? A Google
> search doesn't seem to come up with much.
>
modules enabled in Bullseye, see #986822.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986822
But that was for playing sound i never checked the mic.
Regards.....
Dekks Herton
Nov 12, 2021, 12:40:02 AM11/12/21
to
Ive got my Braswell and Broadwell mixed up, Broadwell is PC chip,
Braswell is SoC based of Silvermont, catpt won't help in this case.
Sorry.
Regards.....
0 new messages