** Description changed:
+ The sof-pci-dev and snd-soc-skl all contains the same pciid, if
+ the soc-skl is loaded ahead of sof-pci-dev, the sof driver will
+ not work anymore, in the oem project, we manually put the soc-skl
+ in the blacklist.
+
+ From kernel-5.4 (focal kernel), the driver soc-sk
** Description changed:
The sof-pci-dev and snd-soc-skl all contains the same pciid, if
the soc-skl is loaded ahead of sof-pci-dev, the sof driver will
not work anymore, in the oem project, we manually put the soc-skl
in the blacklist.
From kernel-5.4 (focal kernel), the driver soc-sk
OK, does the sound work with the testing kernel? and looks like you
didn't remove the workaround "dmic_detect=0".
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1870550
Title:
PCI
@Eric
Command line: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic
root=UUID=8d9177a5-95ca-4bd3-9c51-db760f7300b3 ro quiet splash
snd_hda_intel.dmic_detect=0 vt.handoff=1
You add "snd_hda_intel.dmic_detect=0" somewhere, maybe it is in the
grub.conf?
--
You received this bug notification because you
@David,
Please upload the dmesg of -46 kernel.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1868319
Title:
PCI/internal sound card not detected
Status in alsa-driver package i
@David,
Your machine is a coffeelake platform, there is no sof-firmware for this
platform in the 19.10. you could use a workaround to let sound work with
legacy hda driver: edit /etc/modprobe.d/alsa-base.conf, add "options
snd-hda-intel dmic_detect=0", reboot.
Or you could manually symbollink a f
@David,
No need to change alsa-base.conf after every update.
And from -42, it enabled the dmic_detect by default. And it introduced a
regression from stable patches. It is fixed in the -46.
Even in 18.04, you could still try with the symbollink. Please edit
alsa-base.conf to remove the dmic_detec
Is there an audio enable option in the BIOS? Maybe it is disabled?
Or the codec is damaged physically? You could install the newer kernel
to verify if the codec is good or not, if it is good and newer kernel
could work, then we will bisect the kernel to find the fix for this
issue.
--
You receiv
You could temporarily remove the module-switch-on-connect from the
/etc/pulse/default.pa, reboot and redo the test.
To check if switch-on-connect is loaded or not, run "pactl list modules
| grep connect"
--
You received this bug notification because you are a member of Desktop
Packages, which is
Please remove "options snd-intel-dspcfg dsp_driver=1" temporarily,
reboot and upload the dmesg, let us see what is wrong without
dsp_driver=1.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.n
OK, there is at least one problem in the driver I know, and will build a
testing kernel, maybe next Monday.
Please use the workaround "dsp_driver=1" temporarily.
thx.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu
Please remove snd_hda_intel: dmic_detect=0, you must set dmic_detect=0
somewhere.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1874925
Title:
Comet Lake PCH-LP cAVS (Audio, Voic
Have you ever chosen the "microphones" from the dialogue before?
Please make sure the input source is not "headphone mic" before you
choose the headphone.
Now your input source is "headphone mic":
Simple mixer control 'Input Source',0
Capabilities: cenum
Items: 'Headphone Mic' 'Rear Mic' 'He
I guess after new install of ubuntu os, the default active input source
should be "Headset Mic". If it is not, please tell me, this is worth to
investigate.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bu
It is weird that you could record sound with a pure headphone, I have no
idea how that happened.
And could you please test:
run amixer sset 'Input Source' "Headset Mic" or "Rear Mic" or "Line" first,
then plug in the headphone and choose headphone, does the sound output from
headphone?
--
You
@Seija,
After problem happens, please run "apport-collect 1870975.
Looks like all log were collected when there was no problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/18709
Please run amixer sset 'Capture Source' 'Internal Mic' or 'Headset Mic'
first, make sure the capture source is not headphone mic,
then plug the headset/earphone, choose correct option from the pop-up
dialogue.
thx.
--
You received this bug notification because you are a member of Desktop
Packag
Or you could run alsamixer, press F4, navigate to "Input Source" or
"Capture Source", use up or down to change the preferred options. then
press ESC.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.laun
If you remove dmic_detect=0, your alsa card could not be showed up in
gnome. So I guess there are some errors in the audio driver
initialization, I need the log to debug.
Could you remove dmic_detect=0 temporarily, then boot and upload the
dmesg, let me see what happens on the audio driver.
--
Y
please test this kernel https://people.canonical.com/~hwang4/skipi915/.
and don't forget to remove the "dsp_driver=1" temporarily when testing
this kernel.
And I guess it will meet a new problem when loading ucm, but at least
the kernel driver should finish the initializtion, let us debug the
kern
OK
If you plug headphone/headset into the audio jack, does a audio-
selection dialogue popup?
If yes,
Please run "amixer cget numid=6", Could you see Capture Source now?
If yes, please run "amixer cset numid=6 0 or 2, anyway not headphone
mic", after it successfully set, please plug headphone/h
Please refer to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826868. Looks like
this is a similar bug with that one. They all have geminilake hdmi audio
controller.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in U
Could you upload a wav file recorded by internal mic?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1827440
Title:
[X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distort
The sound in the #19 is not that bad.
If want to get better sound (adding the denoise filter), you could run
"pactl load module-echo-cancel", then choose the echo-cancelled input
device from gnome-sound-setting.
--
You received this bug notification because you are a member of Desktop
Packages,
After booting up, please run:
ls -la /dev/snd/ #could you see some dev nodes
aplay -l # could you see some audio devices
sudo chmod a+rw /dev/snd/*
aplay -l # could you see some different output from the 1st time.
--
You received this bug notification because you are a member of Desktop
Pac
According to the log of ls and aply -l, your audio hardware is
recognized by the driver after booting up.
And alsa is ready to work, I can't find any problem here. I guess you
could run 'aplay test.wav' to play sound after booting up without "sudo
alsa force-reload"
you wrote "After rebooting I h
@Michat,
Could you send your patch to upstream maillist? alsa-devel@alsa-
project.org
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1524215
Title:
Lenovo B50-70 inverted interna
I guess you alsa driver works after booing up, but the pulseaudio fails
to get your built in sound card via alsa-lib.
To check it, after booing up, run pactl list cards, I guess you could
only see one dummy card and one nvidia hdmi audio card; after sudo alsa
force-reload and run pactl list cards,
Then edit /etc/pulse/client.conf, change the line "; extra-arguments =
--log-target=syslog" to "extra-arguments = - --log-
target=file:/tmp/a.txt".
reboot.
you will find the /tmp/a.txt, this is the pulseaaudio log, let us try to
find some clues from the log.
--
You received this bug notific
This is something I never met before, this is the content of my
/etc/pulse/client.conf, and I can find the /tmp/a.txt after booting up.
Maybe this is the root cause of the problem you report, the pulseaudio
doesn't start as the 18.10 or 19.04, the pulseaudio still act as the
14.04. Did you upgrade
there is no client.conf.d/00-disable-autospawn.conf on my computer too.
And the pulseaudio usually sets "autospawn=yes" or "Restart=on-failure"
in the systemd.
Maybe you could delete 00-disable-autospawn.conf temporarily and do a
test, if it does not work, restore it.
And you could run "dpkg -S
On my machine, this is the log the pulseaudio find the sound card via
udev, could you find similar info in your a.txt?
D: [pulseaudio] module.c: Checking for existence of
'/usr/lib/pulse-11.1/modules/module-udev-detect.so': success
D: [pulseaudio] module-udev-detect.c: /dev/snd/controlC0 is acces
E: [autospawn] core-util.c: Home directory not accessible: Permission
denied
I printed out the "Home directory" on my computer, it is
/home/$my_account, and the USER of pulseaudio is $my_account too
(through ps -aux"), then there is no "Permission denied" problem.
In the pulseaudio, it will check
my system is ubuntu 18.04. And from log ps:
The user of "/usr/bin/pulseaudio --daemonize=no" is gdm
The user of "/usr/bin/pulseaudio --start --log-target=syslog" is my
account.
If the user is differnt, I have no idea, maybe we should report the problem to
pulseaudio-disc...@lists.freedesktop.o
No obvious errors in the log. Does the headphone work with other kernel
versions?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1829568
Title:
[GL703VD, Realtek ALC295, Black Hea
Please edit /etc/modproble.d/alsa-base.conf
add a new line in this file: options snd-hda-intel probe_mask=0x1
reboot
Then suspend your machine and resume, could you still see the similar
problem?
--
You received this bug notification because you are a member of Desktop
Packages, which is subsc
Yes, and it looks like you need to be a list member first.
you could register this list from:
https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https:
In theory, adding model=auto (comment #3) doesn't affect your sound
driver since even without model=auto, the audio driver doesn't apply any
fixup models to your machine.
Please do a test:
cd /sys/module/snd_hda_codec
sudo su
echo 1 > parameters/dump_coef
Then test your speaker, when the speaker
edit /etc/modprobe.d/alsa-base.conf and add "options snd-hda-intel
power_save=0" in this file
reboot
Does the speaker work normally? That means it will not stop working
after 10s.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-dri
Sorry, it is /etc/modprobe.d/alsa-base.conf rather than /etc/modproble.d
/alsa-base.conf
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1829540
Title:
[HDA-Intel - HDA Intel PCH,
So for speaker:
If we don't add "model=auto" or "power_save=0", the speaker works fine?
or only works for 10s?
If adding "model=auto", the speaker only works for 10s?
If adding "power_save=0", the speaker doesn't work?
--
You received this bug notification because you are a member of Desktop
P
Too complicated. I have no idea for your problem.
Probably you could file a bug against the upstream linux kernel, let the
audio maintainer and community to help.
Just like this one:
https://bugzilla.kernel.org/show_bug.cgi?id=201251
** Bug watch added: Linux Kernel Bug Tracker #201251
https:
@jimnong,
Please do a test:
don't plug anything in the jack and run: sudo hdajacksensetest -a
Then plug the apple type headset in the jack and run: sudo
hdajacksensetest -a
please upload the output. thx.
--
You received this bug notification because you are a member of Desktop
Packages, which
after the comment#4, reboot, then if you still can reproduce the issue,
please upload the dmesg and alsa-info.txt generated by running "alsa-
info.sh"
thx.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bu
Please collect one more log:
sudo su
cd /sys/module/snd_hda_codec/parameters/
echo 1 > dump_coef
Then run alsa-info.sh to collect a log of alsa-info.txt, and upload this
alsa-info.txt.
thx.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Please do a test:
add "snd_hda_intel.model=lifebook-extmic" in the bootargs (kernel
bootargs). After booting up, please a headset, does the headset-mic
work?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://
@Ji-min,
After #12, please upload an alsa-info.txt, let me check if "model
=liefbook-extmic" is applied or not. If it really applied but it did not
work on this machine, I will ask for help from realtek.
thx.
--
You received this bug notification because you are a member of Desktop
Packages, wh
checked the alsa-info.txt in #14, found the lifebook-extmic doesn't take
effect, "model=liefbook-extmic" was added to kernel-4.19 but we are
using kerel-4.15. So please test this dkms, if headset-mic still doesn't
work, please generate an alsa-info.txt too.
thx.
To install the dkms:
sudo dpkg -i
Reported to realtek.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1821269
Title:
[Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch (4-pole
combo jack mic doesn't d
If you plug sth in the Red lineout rear, does the UI detect your
plugging (gnome-sound-setting).
When the Red lineout rear jack is plugged sth, please run "sudo
hdajacksensetest -c 1 -a", and upload the output.
Does the rest 3 lineout jacks (maybe black color jacks) work well?
--
You received t
Please install this dkms, reboot and redo the test.
If the headset-mic still doesn't work, please enable dump_coeff and
generate an alsa-info.txt.
thanks.
** Attachment added: "oem-audio-hda-daily-dkms_0.1_all.deb"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821269/+attachme
It is fixed from kernel driver, So all linux distros have this issue. We
plan to send the patch to upstream kernel and cc stable-kernel, after
this patch is merged to stable-kernel, I guess all linux distros will
have this fix automatically.
--
You received this bug notification because you are a
** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1821269
Title:
[Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswi
Please edit /etc/modprobe.d/alsa-base.conf and add:
options snd-hda-intel probe_mask=0x1
reboot and check if audio works.
If it works, please remove that line int the alsa-base.conf and install
5.0 kernel to test.
--
You received this bug notification because you are a member of Desktop
Packag
Probably you machine needs this patch:
commit 0202f5cd9aab127355f6b1de74058a670424d48a
Author: Peisen
Date: Thu Oct 26 10:35:36 2017 +0800
ALSA: hda/realtek - Add support for ALC1220
Add Clevo-P51 mode support for ALC1220.
ALC1220 Clevo-p51
Speaker uses I2S output.
We
To test the patch of #4, please install the ubuntu-5.0 kernel, then
add "options snd-hda-intel model=clevo-p950"
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1833161
Title:
[HD
Public bug reported:
If the output devices are on different sinks, PA can't auto switch
streams on them
** Affects: pulseaudio (Ubuntu)
Importance: Critical
Assignee: Hui Wang (hui.wang)
Status: New
** Changed in: pulseaudio (Ubuntu)
Importance: Undecided =>
And this patch:
commit cbaeea4af7669003ae97064fe12fa75fd4870611
Author: Hui Wang
Date: Wed May 15 14:39:27 2019 +0800
stream-restore: Don't restore if the active_port is PA_AVAILABLE_NO
We met two problems recently, one happened on a Lenovo machine with
dual analogue c
Probably we need to backport this patch:
commit 30a551bbc45f2d213e8b2889c8bede8a9c16c9d2
Author: João Paulo Rechi Vita
Date: Mon Dec 10 16:16:46 2018 -0800
switch-on-port-available: Check if we need to change the active profile
When a port becomes unavailble its profile may also b
** Tags added: originate-from-1833676 sutton
** Changed in: pulseaudio (Ubuntu)
Importance: Critical => High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1834138
Title:
PA: c
** Changed in: pulseaudio (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1834138
Title:
PA: can't auto switch streams between different si
** Description changed:
- If the output devices are on different sinks, PA can't auto switch
- streams on them
+ On the Lenovo P52 machine, there are dual analogue codecs: the 1st one
+ contains the speaker and front headphone, the 2nd one contains the rear
+ lineout.
+
+ As there are two codecs,
** Description changed:
On the Lenovo P52 machine, there are dual analogue codecs: the 1st one
contains the speaker and front headphone, the 2nd one contains the rear
lineout.
As there are two codecs, there are 2 sinks in the PA, the one sink has
speaker and headphone, the other one h
*** This bug is a duplicate of bug 1820794 ***
https://bugs.launchpad.net/bugs/1820794
** This bug has been marked a duplicate of bug 1820794
[Dell Inspiron 3558] PCI/internal sound card not detected
--
You received this bug notification because you are a member of Desktop
Packages, which
[ 47.123101] snd_hda_intel :00:1f.3: CORB reset timeout#1, CORBRP = 0
[ 47.124615] snd_hda_intel :00:1f.3: no codecs found!
Does your sound work under other OS like windows? we need to confirm it
is not a HW issue first.
--
You received this bug notification because you are a member
Did you notice a significant delay for booting process when the HDMI and
ac3 can't work? there are 30s delay between #1 and #2. Please check the
dmesg to find why there is a 30s delay when plugging a usb sound card.
[ 37.065157] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC233:
line_out
or else, could you install the latest mainline kernel to test if the
sound work?
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2-rc6/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/b
download linux-image-
unsigned-5.2.0-050200rc6-generic_5.2.0-050200rc6.201906222033_amd64.deb
and linux-
modules-5.2.0-050200rc6-generic_5.2.0-050200rc6.201906222033_amd64.deb
Then install them by:
sudo dpkg -i $files_name.deb
after that, reboot and run uname -a to check if the kernel is 5.2.0
Yes, the driver is loaded correctly, but it fails during initialization.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1834264
Title:
PCI/internal sound card not detected
Status
please upload the dmesg
dmesg > /tmp/dmesg.txt
upload the dmesg.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1834264
Title:
PCI/internal sound card not detected
Status in
According to the #17 and you said "it was workig fine until today", it
looks like this is a hardware issue. Probably the hardware of audio was
broken.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.lau
Yes, there is a power optimization in the 19.04.
please close that optimization by editing the /etc/modprobe.d/alsa-
base.conf
add options snd-hda-intel power_save=0
then reboot.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-dri
Since the P520 machine uses ucm in the PA, the patch in the #1 doesn't
fix any problem for this machine, so only need to backport the patch of
#2.
** Summary changed:
- PA: can't auto switch streams between different sinks
+ PA: Don't restore the streams to sinks/sources with only unavailable po
This is the debdiff for disco version, after it is merged any verified,
I will continue uploading the debdiff for cosmic and bionic.
So please put this change into the disco queue first. thanks.
** Patch added: "pulseaudio_12.2-2ubuntu4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/puls
Reply #6:
The ubuntu 19.10 (Eaon) also has this problem, need to apply this patch
as well. And since both eaon and disco share the same pulseaudio
version, the debdiff in the #5 also can apply to eaon, let us apply it
to eaon first.
--
You received this bug notification because you are a member
Need you to collect some logs, then let us see if it can be fixed
through kernel driver.
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-co
@Sebastien,
I checked the ubuntu eaon also uses pulseaudio_12.2-2ubuntu3 which is
same as the disco uses, so the debdiff in the #5 can be applied to eaon
too, could we apply the #5 to eaon first? or I need to re-generate a
debdiff for eaon?
thx.
--
You received this bug notification because you
Installed the latest eaon image of http://cdimage.ubuntu.com/ubuntu
/daily-live/current/ to the lenovo p520, and upgrade the pulseaudio to
1:12.2-2ubuntu4, Then I tested the recording and palyback, it worked as
expected:
recording: plug a mic into the front audio jack, and select it from
sound-set
Verification done on the Disco, it fixed the problem.
On the lenovo P520, I installed the disco (19.04), edit the
/etc/apt/sources.list to add disco-proposed repository, then run apt-get update
abd sudo apt install pulseaudio, now the pulseaudio is:
ii pulseaudio 1:12.
This is the debdiff for Cosmic.
Thanks.
** Patch added: "pulseaudio_12.2-0ubuntu4.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1834138/+attachment/5275752/+files/pulseaudio_12.2-0ubuntu4.1.debdiff
--
You received this bug notification because you are a member of Des
OK, let us skip the cosmic, I will upload a debdiff for bionic.
Thanks.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1834138
Title:
PA: Don't restore the streams to sinks/source
OK, got it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1834138
Title:
PA: Don't restore the streams to sinks/sources with only unavailable
ports
Status in HWE Next:
New
St
Sporsor-team, this is the debdiff for bionic.
thx.
** Patch added: "pulseaudio_11.1-1ubuntu7.4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1834138/+attachment/5278407/+files/pulseaudio_11.1-1ubuntu7.4.debdiff
--
You received this bug notification because you are a me
@sebastien or anyone else in the sponsor-team,
Please review my debdiff for bionic in the #19 and if possible, please
enqueue it.
thx.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs
** Patch removed: "pulseaudio_12.2-0ubuntu4.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1834138/+attachment/5275752/+files/pulseaudio_12.2-0ubuntu4.1.debdiff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pul
** Patch removed: "pulseaudio_11.1-1ubuntu7.4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1834138/+attachment/5278407/+files/pulseaudio_11.1-1ubuntu7.4.debdiff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pul
Public bug reported:
This bug is for tracking purpose.
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects: linux-firmware (Ubuntu)
Importance: Undecided
Assignee: Hui Wang (hui.wang)
Status: New
** Tags: originate-from-1837853 somerville
Please upload the alsa-info.txt generated on your machine.
$alsa-info --no-upload
then upload the generated alsa-info.txt from /tmp/alsa-info.txt.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.la
@Kreaninw,
please test this dkms, to install this dkms:
sudo dpkg -i oem-audio-hda-daily-dkms_0.1_all.deb
reboot
#test if the internal mic works or not, if not, please also upload an
alsa-info.txt
to remove the dkms:
sudo dpkg -r oem-audio-hda-daily-dkms
reboot
** Attachment added: "oem-audio
According to the alsa-info.txt in the #73, the fix in the dkms of #72
doesn't apply to your machine.
Did you install the dkms of #72 successfully?
please run 'dkms status' to check if oem-audio-hda-daily-dkm is
installed or not.
--
You received this bug notification because you are a member of
please install headers first:
sudo apt install linux-headers-5.0.0-24
sudo apt install linux-headers-5.0.0-24-generic
Then install the dkms.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.n
According to #27, the deb was not installed too, let me build a kernel,
then you could test the kernel instead of this deb.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1523100
Ti
Please test this kernel:
https://drive.google.com/drive/folders/16OBmEmWPYncLOT-QVlo6vkyy3Ar819aX?usp=sharing
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1523100
Title:
Alsa no
To check, please upload the output of the command as below:
ls /lib/modules/`uname -r`/updates/dkms
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1523100
Title:
Alsa not detecti
According to #82, that deb was not installed successfully.
This is probably because you enabled secure boot in the BIOS or boot the
signed kernel. Could you change to use the unsigned kernel (#79), maybe
disable the secure boot in the BIOS, then you could load the unsigned
kernel.
--
You receive
"Regression Potential" is updated with adding the 1556439 part in it.
** Description changed:
SRU Document:
[Impact]
The Lenovo P520 machine has dual analogue codecs, so there are two sinks
and two sources in the PA, one has the front headphone and front
microphone, the other has
addressed the #29, change No to Low.
** Description changed:
SRU Document:
[Impact]
The Lenovo P520 machine has dual analogue codecs, so there are two sinks
and two sources in the PA, one has the front headphone and front
microphone, the other has the rear lineout, linein and rea
Probably on this machine, the internal mic is connected to pin 0x13.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1840725
Title:
Microphone not working in Ubuntu 18.04.3 LTS on
You said the internal mic works well under windows10, so please run this
dump program under windows10, then upload the dump file to launchpad,
maybe we can find some difference from the linux.
** Attachment added: "RtHDDump_V226.zip"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/
If the headphone doesn't work, please run:
sudo hdajacksensetest -a //without plugging the headphone
sudo hdajacksensetest -a //with plugging the headhone
Then upload the log.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver
301 - 400 of 680 matches
Mail list logo
