Bug 489828

I filled the form of URI. But the URI doesn't shown. So I add it.
http://www.alsa-project.org/db/?f=af6a6e787d4bd5212bf766bf5d09fda1ab5e2300

Created attachment 334906 [details]
The result of 'lsmod|grep snd'

Created attachment 334907 [details]
Result of lspci -v

Created attachment 334908 [details]
pulseaudio's message around /var/log/messages . I tried adding me to pulse-rt but not solved.

Oops... I forgot to say that I updated soon after the clean installation on my new HDD.
And kernel version is 2.6.27.19-170.2.35.fc10.x86_64

[root@star1 ~]# cat /proc/asound/cards
--- no soundcards ---

Please, attach full dmesg output just after boot. It seems that driver cannot use HDA bridge for some reason.

Created attachment 334919 [details]
Full dmesg after boot.

Is that correct file to attach?
Thanks advance.

Relevant messages from dmesg.

HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16
ALSA sound/pci/hda/hda_intel.c:1232: hda-intel: no codecs initialized
HDA Intel 0000:00:14.2: PCI INT A disabled

You may try to compile and install latest ALSA driver snapshot from http://www.alsa-project.org .

Created attachment 335113 [details]
dmesg when I installed the alsa-driver snapshot.

Ahoj!(It's one of few Czech greeting I know.)
I don't know how to make that snapshot work. I tried some, though. Unknown symbols occurs.
I did
./configure
make
make install
And error occurs:
> [root@star1 alsa-driver-1.0.19.34.g70f78.363.g0ec3b]# modprobe snd_hda_intel
> FATAL: Error inserting snd_hda_intel (/lib/modules/2.6.27.19-170.2.35.fc10.x86_64/kernel/sound/pci/hda/snd-hda-intel.ko): Unknown symbol in module, or > unknown parameter (see dmesg)
I changed back by
> make uninstall
> rpm -ivh --replacepkgs /var/cache/yum/updates/packages/kernel-2.6.27.19-170.2.35.fc10.x86_64.rpm

Well, I write the chipset of its onboard sound.
It's Realtek ALC889A Audio Codec , as I see on the official website of the motherboard.

Created attachment 335209 [details]
dmesg when I installed the alsa-driver-1.0.19 (stable).

I tried the stable alsa-driver-1.0.19 and failed, too.

[root@star1 alsa-driver-1.0.19]# modprobe snd_hda_intel
[root@star1 alsa-driver-1.0.19]# lsmod|grep snd
snd_hda_codec_realtek   253700  1 
snd_hda_intel          35944  6 
snd_hda_codec          70016  2 snd_hda_codec_realtek,snd_hda_intel
snd_hwdep              16392  1 snd_hda_codec
snd_seq_dummy          11652  0 
snd_seq_oss            39616  0 
snd_seq_midi_event     15104  1 snd_seq_oss
snd_seq                58864  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device         15508  3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss            45728  0 
snd_mixer_oss          23040  1 snd_pcm_oss
snd_pcm                80392  5 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_timer              29584  2 snd_seq,snd_pcm
snd                    67576  22 snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_seq_dummy,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
soundcore              14992  1 snd
snd_page_alloc         17296  2 snd_hda_intel,snd_pcm
[root@star1 alsa-driver-1.0.19]# /etc/init.d/alsasound restart
Shutting down sound driver: ERROR: Module snd_hda_codec_realtek is in use
ERROR: Module snd_hda_codec is in use by snd_hda_codec_realtek
ERROR: Module snd_hwdep is in use by snd_hda_codec
ERROR: Module snd_pcm is in use by snd_hda_codec
ERROR: Module snd_timer is in use by snd_pcm
ERROR: Module snd is in use by snd_hda_codec_realtek,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
done
ALSA driver is already running.
[root@star1 alsa-driver-1.0.19]# /etc/init.d/alsasound stop
Shutting down sound driver: /usr/sbin/alsactl: save_state:1502: No soundcards found...
done

And ...
[root@star1 ~]# cat /proc/asound/cards
--- no soundcards ---

Created attachment 335213 [details]
dmesg when I installed the alsa-driver-1.0.19 (stable) --with-debug=verbose.

Created attachment 335214 [details]
dmesg when acpi=off after I installed the alsa-driver-1.0.19 (stable) --with-debug=verbose.

Created attachment 335222 [details]
I tried UbuntuLinux8.10 amd64 and sound doesn't work, neither. That's the dmesg of it.

Created attachment 335234 [details]
When I got sound back by "kernel: hda-intel: Invalid position buffer, using LPIB read method instead."(random fallover)

It doesn't mean succeed. Sometimes sound get back and sometimes not, at random.

It looks like that it fails when the RIRB is placed at a physical address greater than 4 GB.

pci_set_dma_mask(pci, DMA_32BIT_MASK);
pci_set_consistent_dma_mask(pci, DMA_32BIT_MASK);

seems to solve the problem.

I don't know how to make a patch file. But I modified hda_intel.c on the stable source by Daniel Koukola's idea. And the sound got back.

[emmanuel@star1 hda]$ pwd
/home/emmanuel/Softwares/alsa-driver-1.0.19/alsa-kernel/pci/hda
[emmanuel@star1 hda]$ diff hda_intel.c{0,}
2215,2216c2215,2218
<       if ((gcap & 0x01) && !pci_set_dma_mask(pci, DMA_64BIT_MASK))
<               pci_set_consistent_dma_mask(pci, DMA_64BIT_MASK);
---
>       /*      if ((gcap & 0x01) && !pci_set_dma_mask(pci, DMA_64BIT_MASK))
>               pci_set_consistent_dma_mask(pci, DMA_64BIT_MASK); */
>       pci_set_dma_mask(pci, DMA_32BIT_MASK);
>       pci_set_consistent_dma_mask(pci, DMA_32BIT_MASK);

http://www.mail-archive.com/linux-ide@vger.kernel.org/msg06694.html …SB600's AHCI controller seems to have the same problem.

*** Bug 475251 has been marked as a duplicate of this bug. ***

This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.