[Expired for alsa-driver (Ubuntu) because there has been no activity for
60 days.]
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This release of Ubuntu is no longer receiving maintenance updates. If
this is still an issue on a maintained version of Ubuntu please let us
know.
** Changed in: alsa-driver (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Hi JoseLuisTriana,
1) pci=use_crs shouldn't make a difference on your system because we
enable pci=use_crs automatically on systems with BIOS date of 2008 or
newer, and yours is 02/21/2008
2) Re comment #4, the kernel should be able to configure devices even if
the BIOS didn't set it up
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: alsa-driver (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/892414
Title:
It seems that I have a broken BIOS, since the kernel isn't unable to set
up the configuration from it, then tries to use a generic mode then a
bug.
** Attachment added: back trace of the bug.
My excuses for not bringing the right information, the option that I use
in GRUB_CMDLINE_LINUX_DEFAULT is pci=use_crs and NOT pci=use_cms as I
mentioned in the information of this report.
I achieved a workaround by adding inside /etc/modprobe.d/alsa-base.conf
this line:
snd-hda-intel options
No matter what I do, I always have many and many callbacks with a
spourious response, I included some the callbacks that are different
form the rest, most of that callbacks are this:
13/12/11 19:36:25 hda-intel spurious response 0x0:0x0, last
cmd=0x12f000b
This is the first time that
** Attachment added: my document with more complete information.
https://bugs.launchpad.net/bugs/892414/+attachment/2601375/+files/alsa-info.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.