-
Environment and Hardware Details
|Laptop Model|Lenovo Yoga Pro 7 14AKP10 (Model 83KG)|
|---|---|
|Processor|AMD Ryzen AI 7 350 w/ Radeon Graphics|
|OS Name|Zorin OS 18 Pro (Based on Ubuntu 24.04 LTS)|
|Kernel Version|Linux 6.17.5-061705-generic (Manually installed mainline kernel)|
|Audio Chipset|AMD ACP/ACP3X/ACP6x Audio Coprocessor (Realtek ALC287 Codec)|
|Wi-Fi/BT Chipset|MEDIATEK Corp. Device 14c3:7925 (Driver: mt7925e)|
|Display Server|Wayland|
|BIOS Version|QFCN25WW| -
Issue 1: Extremely Low Speaker Volume (Missing Bass/Subwoofer)
Description: The internal speakers produce sound, but the volume is drastically low (significantly quieter than Windows 11 at 100%) and the audio quality is thin, indicating that the bass/subwoofer speakers are not being activated by the Linux audio driver. This is a common problem with multi-speaker arrays in newer Lenovo Yoga models.
Troubleshooting Steps Already Performed (No Success):
Volume Check: Confirmed volume levels are at 100% in Zorin Settings and boosted via pavucontrol.
Audio Quirk V1 (Generic): Added options snd-sof-intel-hda-generic hda_model=alc287-yoga9-bass-spk-pin to /etc/modprobe.d/alsa-base.conf and rebooted.
Audio Quirk V2 (Indexed): Confirmed the audio codec is on Card 1 (cat /proc/asound/cards) and attempted to apply the quirk using index targeting: options snd-hda-intel model=(null),alc287-yoga9-bass-spk-pin index=1.
Audio Quirk V3 (AMD-specific): Attempted alternative AMD model options (if any were found in personal search).
Kernel Update: Updated kernel to the very latest stable mainline (6.17.5) to ensure all current ALSA/SOF fixes were included.
Expected Behavior: All four (or more) internal speakers, including the subwoofers/bass drivers, should be correctly initialized by the kernel driver, providing full volume and rich sound quality comparable to Windows.
- Issue 2: Bluetooth Fails to Initialize/Stay Active
Description: The Bluetooth adapter (Mediatek MT7925E) is detected by the system but fails to turn on, connect, or remain stable, especially after a fresh boot or waking from sleep. This typically results in a "No default controller available" error when using bluetoothctl.
Troubleshooting Steps Already Performed (No Success):
Module Reload (Temporary Fix): Tried unloading and reloading the modules (sudo modprobe -r btusb mt7925e; sudo modprobe mt7925e; sudo modprobe btusb). This sometimes works temporarily for a single session but is not permanent.
Hard Power Cycle: Performed a complete shutdown and unplugged the laptop for 15 seconds to drain residual power from the chipset (a known fix for MediaTek hardware).
GIO/GDM Conflict Fix: Applied the udev rule to prevent desktop environment interference:
/etc/udev/rules.d/99-bluetooth-fix.rules
ATTRS{idVendor}=="0489", ATTRS{idProduct}=="e111", ENV{UDISKS_IGNORE}="1"
Then reloaded udev rules and rebooted.
Kernel Update: Running the very latest kernel (6.17.5) confirms this is not a driver omission, but a power/timing bug.
Expected Behavior: The Bluetooth controller should initialize correctly at boot, be available immediately, and maintain a stable connection through sleep cycles.