Internal microphone not working on ASUS VivoBook with Realtek ALC256 (Ubuntu 24.04 + kernel 6.15)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Chris Chiu | ||
Plucky |
Fix Released
|
Medium
|
Chris Chiu | ||
Questing |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
[Impact]
On various ASUS Vivobook with Realtek audio codec ALC256, the audio input device will disappear thus the microphone does not work anymore. It happens after this commit 3b4309546b48 ("ALSA: hda: Fix headset detection failure due to unstable sort") on 6.14-rc1.
[Fix]
Backported patches for ASUS Vivobook which use the correct fixup which is not affected by the order problem caused by commit 3b4309546b48 ("ALSA: hda: Fix headset detection failure due to unstable sort")
[Test Case]
1. Get ASUS Vivobook laptops and boot up.
2. Check if the audio input device exist
3. use `arecord` to record sound with the microphone
[Where problems could occur]
They are only quirked for ASUS Vivobook SSIDs with ALC256. Should have no impact for other platforms. The risk should be low.
========== original bug description ==========
I'm using an ASUS VivoBook (11th Gen Intel i7, Realtek ALC256 audio codec). On Ubuntu 24.04.2 LTS, the internal microphone is detected and listed correctly in PulseAudio/PipeWire and ALSA, but no input is captured. Microphone volume and boost are set to 100%, not muted. Input device appears as RUNNING in pactl, but no signal is recorded.
I tested:
- Ubuntu 24.04 with default kernel (6.11)
- Upgraded to mainline kernel 6.15 via `mainline` tool
- ALSA, PipeWire, PulseAudio all installed and working
- External USB mic works perfectly
- BIOS does not expose any audio/microphone control
- Mic also tested with `pw-record`, `arecord`, `gnome-
ALSA info:
https:/
It seems like a pin configuration or unsupported codec issue with ALC256. Please advise if this requires a patch or model-specific quirk.
Thank you.
CVE References
- 2025-38003
- 2025-38004
- 2025-38029
- 2025-38031
- 2025-38032
- 2025-38033
- 2025-38034
- 2025-38035
- 2025-38036
- 2025-38037
- 2025-38038
- 2025-38039
- 2025-38040
- 2025-38041
- 2025-38042
- 2025-38043
- 2025-38044
- 2025-38045
- 2025-38047
- 2025-38048
- 2025-38050
- 2025-38051
- 2025-38052
- 2025-38053
- 2025-38054
- 2025-38055
- 2025-38057
- 2025-38058
- 2025-38059
- 2025-38060
- 2025-38061
- 2025-38062
- 2025-38063
- 2025-38064
- 2025-38065
- 2025-38066
- 2025-38067
- 2025-38068
- 2025-38069
- 2025-38070
- 2025-38071
- 2025-38072
- 2025-38073
- 2025-38074
- 2025-38075
- 2025-38076
- 2025-38077
- 2025-38078
- 2025-38079
- 2025-38080
- 2025-38081
- 2025-38082
- 2025-38088
- 2025-38091
- 2025-38092
- 2025-38100
- 2025-38101
- 2025-38102
- 2025-38103
- 2025-38105
- 2025-38106
- 2025-38107
- 2025-38108
- 2025-38109
- 2025-38110
- 2025-38111
- 2025-38112
- 2025-38113
- 2025-38114
- 2025-38115
- 2025-38116
- 2025-38117
- 2025-38118
- 2025-38119
- 2025-38120
- 2025-38122
- 2025-38123
- 2025-38124
- 2025-38125
- 2025-38126
- 2025-38127
- 2025-38128
- 2025-38129
- 2025-38130
- 2025-38131
- 2025-38132
- 2025-38134
- 2025-38135
- 2025-38136
- 2025-38137
- 2025-38138
- 2025-38139
- 2025-38140
- 2025-38141
- 2025-38142
- 2025-38143
- 2025-38145
- 2025-38146
- 2025-38147
- 2025-38148
- 2025-38149
- 2025-38151
- 2025-38153
- 2025-38154
- 2025-38155
- 2025-38156
- 2025-38157
- 2025-38158
- 2025-38159
- 2025-38160
- 2025-38161
- 2025-38162
- 2025-38163
- 2025-38164
- 2025-38165
- 2025-38166
- 2025-38167
- 2025-38168
- 2025-38169
- 2025-38170
- 2025-38172
- 2025-38173
- 2025-38174
- 2025-38175
- 2025-38176
- 2025-38265
- 2025-38267
- 2025-38268
- 2025-38269
- 2025-38270
- 2025-38272
- 2025-38274
- 2025-38275
- 2025-38277
- 2025-38278
- 2025-38279
- 2025-38280
- 2025-38281
- 2025-38282
- 2025-38283
- 2025-38284
- 2025-38285
- 2025-38286
- 2025-38287
- 2025-38288
- 2025-38289
- 2025-38290
- 2025-38291
- 2025-38292
- 2025-38293
- 2025-38294
- 2025-38295
- 2025-38296
- 2025-38297
- 2025-38298
- 2025-38299
- 2025-38300
- 2025-38301
- 2025-38302
- 2025-38303
- 2025-38304
- 2025-38305
- 2025-38306
- 2025-38307
- 2025-38310
- 2025-38311
- 2025-38312
- 2025-38313
- 2025-38314
- 2025-38315
- 2025-38316
- 2025-38317
- 2025-38318
- 2025-38319
- 2025-38350
- 2025-38352
- 2025-38414
- 2025-38415
description: | updated |
Changed in linux (Ubuntu Questing): | |
status: | New → Won't Fix |
Changed in linux (Ubuntu Plucky): | |
status: | New → In Progress |
Changed in linux (Ubuntu Plucky): | |
assignee: | nobody → Chris Chiu (mschiu77) |
Changed in linux (Ubuntu): | |
assignee: | nobody → Chris Chiu (mschiu77) |
Changed in linux (Ubuntu Questing): | |
status: | Won't Fix → Fix Released |
Changed in linux (Ubuntu Plucky): | |
importance: | Undecided → Medium |
status: | In Progress → Fix Committed |
> - Upgraded to mainline kernel 6.15 via `mainline` tool
To clarify: when you use the Ubuntu provided kernel, everything is okay? But when you install a third party kernel things break?
If so, this is not something we can support, and you will need to find help elsewhere. If I misunderstood, please clarify the working vs. non-working scenarios.