Public bug reported:
i installed Ubuntu 20.04 yesterday and now i am facing laggy video.
please help me to solve it
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
But I am not observing any problem related to working of sound card.
Obviously sound after sleep and hibernate is broken, but patch needs to
be modified for that. Can you explain any not so obvious problem due to
this fault?
--
You received this bug notification because you are a member of
My bad. I had disabled HDMI codecs through BIOS. When enabled, current
patch fails because it detects non zero probe mask(only for HDMI
though). Will attach modified patch soon.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver
Attaching revised patch with new alsa-info. This patch doesn't look so
good because codec-to-be-probed is assumed at location 0 and other
discovered codecs are not considered. But if this bug is only present in
this chipset, in my opinion this should be good enough.
http://www.alsa-
I don't have much technical depth in it. So please explain what does it
mean, and how can it be avoided.
--
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/1155202
Title:
[Intel
http://www.alsa-
project.org/db/?f=34678ff26afafe9cc9c69457ac45bc551ca33b34
Interestingly driver does not detect HDMI codec now
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
Let me try to explain my findings:
How does this magic sequence come?
By dumping Win7 driver's init sequence and reproducing it through ALSA driver.
why does it need to set UNSOL flag at first?
No such need, I've put it after regular init so that only affected chipsets are
reset again. Putting
Attaching a revised patch. Tested on Linux 3.5.0-45-generic kernel
using DKMS source and 3.12.6 kernel. Please see anything needs to be
changed to fit coding standards.
** Attachment added: patch
Ok, here's a good news. I believe I have a code change to overcome chip
bug.
A bit of debug description:
I collected couple of more win7 IOMMU traces. It turns out even win7
sometimes does not detect mask in first place. It did about 20
read/writes before reading mask again.
I mirrored those
Attaching IOMMU read/write traces for both win7 and ubuntu12.10 guest
machines.
** Attachment added: win7 trace
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1155202/+attachment/3938607/+files/trace_win7
--
You received this bug notification because you are a member of Desktop
** Attachment added: ubuntu trace
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1155202/+attachment/3938608/+files/trace_ubuntu
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
** Changed in: alsa-driver (Ubuntu)
Status: Expired = Incomplete
--
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/1155202
Title:
[Intel DZ77SL-50K, Intel PantherPoint HDMI,
I finally have some good news. I installed Win7 guest using qemu and
passed pci card to it. Win7 was able to detect it. I closed Win7, and
reinserted snd_hda_intel, and now it detects both analog and digital
devices. I tried it couple of times and it worked. So and ugly hack to
get it working.
I
I should also point out that I needed to restart for the changes to take
effect.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1173152
Title:
802.1x security in 13.04 not
This is a really embarassing bug especially for us enterprise users.
Sébatien's workaround works but you're then required to enter your
password each time you connect to the network.
Adding this line to etc/NetworkManager/system-connections/network id fixed
that for me:
password=password
So
I've tried disabling probe_mask for HDMI. It results in no sound device
being available in aplay. Interestingly BIOS during boot is able to
detect this codec and play a boot-up tune.
Regards
Niraj
--
You received this bug notification because you are a member of Desktop
Packages, which
shows, system does not
detect any codec at that location.
Is it possible to know whether windows driver finds codec at location 0
by usual method or it has some workaround for this bug?
Regards
Niraj
--
You received this bug notification because you are a member of Desktop
Packages, which
sound. Could that be the problem?
Also, lshw (output attached) shows one unclaimed entry, does it have
anything to do with this problem?
Regards
Niraj
** Attachment added: lspci -vvvnn
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1155202/+attachment/3694115/+files/lspci
** Attachment added: lshw
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1155202/+attachment/3694116/+files/lshw
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
19 matches
Mail list logo
