[Dell Precision M3800, Realtek ALC3661, Speaker, Internal] No sound at all
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
alsa-driver (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
When I run Alsamixer, there seem to be two cards, the first of which is HDA Intel HDMI, so my initial thought was that the wrong sound port must be selected by default, but wgen I use F6, to select "HDA Intel PCH", Card Realtek ALC3661, I still cannot get the internal speakers to produce sound. Note that the headphone jack does work.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: alsa-base 1.0.25+
ProcVersionSign
Uname: Linux 5.8.0-48-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 11 19:31:46 2021
InstallationDate: Installed on 2021-04-10 (1 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
PackageArchitec
SourcePackage: alsa-driver
Symptom: audio
Symptom_
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [Dell Precision M3800, Realtek ALC3661, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/08/2015
dmi.bios.release: 0.9
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: Dell Precision M3800
dmi.board.vendor: Dell Inc.
dmi.board.version: A09
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.
dmi.ec.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Dell Precision M3800
dmi.product.sku: Dell Precision M3800
dmi.product.
dmi.sys.vendor: Dell Inc.
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
See this document for currently supported Ubuntu releases: /wiki.ubuntu. com/Releases
https:/
We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in.