Go to fedoraforum.org and you find additional threafd (in addition to mine).
Search for "82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio" and you
probably find.
Also in google you will find. I actually had found a link to wikipedia to a
similar card as min mentioning the blacklist procedure
On Dec 3, 2007 2:44 PM, Brian L Scipioni <[EMAIL PROTECTED]> wrote:
> Even the Fedora soundcard detection tool is not outputting any sound for
> me, although my sound is working perfectly (this time around). The tool
> used to work just fine. I am going to reopen that bug and see if
> someone can straighten this out.
>
> I'd like to hear from anyone else having this problem (some boots the
> sound works, some boots it doesn't)
>
> On Sun, 2007-12-02 at 09:54 -0800, Bill Unruh wrote:
> > On Sun, 2 Dec 2007, Wolfgang P. Rauchholz wrote:
> >
> > > I agree I would also say i is a bug. Especially as in Ubuntu it works
> out of
> > > the box with no problem.
> > > For which I guess it is an issue related to Fedora and not alsa.
> > > But I must admit also I am everything but an IT expert.
> >
> > Do Fedora and Ubuntu use different versions of alsa? That could explain
> > it. It could also be a difference in the setup scripts on the two
> machines.
> > (That would certainly not be an alsa bug)
> >
> > To see if it is really a Fedora problem, you could download the latest
> > alsa-drivers compile them and install them. On the other hand, the fact
> > that it sometimes works makes one suspect that it is not an alsa drivers
> > problem. However RedHat has been known to destroy programs by not
> > understanding them and sticking in "improvements".
> >
> >
> >
> > >
> > >
> > >
> > > Brian L Scipioni wrote:
> > >> Glad I saw this, this exact problem has been driving me crazy for a
> > >> while. Sometimes the sounds works, sometimes it does not.
> > >>
> > >> I noticed that the bug report has been closed - NOTABUG. a
> configuration
> > >> problem. I'm sorry, but when the sound does not work on an
> > >> out-of-the-box install, something is just plain broken.
> >
> >
> > The question is what is that "something"?
> >
> >
> > >>
> > >> So the solution is for everyone to examine all their modules to
> > >> determine the correct loading sequence, and then blacklist certain
> > >> modules? I can't believe they left it at that.
> >
> > Sometimes that is all you can do.
> > However you could tell us-- does this fix the problem?
> > Note that there are two intel8x0 modules, the m one and the one without
> an
> > m. It could be that the recognition routine on Fedora simply does not
> get
> > it right which one to use, and maybe even tells the system to load both
> (
> > which could well be a disaster.)
> >
> >
> >
> > >>
> > >> Can someone here voice an opinion: is this an ALSA issue or fedora
> > >> issue? Why does it just happen to certain select people (I assume
> it is
> > >> a rare problem).
> >
> > There is some code in alsa which looks up the names of the users on the
> > machine and using a certain algorithm decides which users to insert
> broken
> > code for. :-)
> >
> > Anyway, if it really is that snd-intel8x0 works and snd-intel8x0m does
> not,
> > and that Fedora tells the system to use the latter, then it is a Fedora
> > issue. It is not identifying the card correctly.
> >
> >
> >
> >
> >
> >
> > >>
> > >> thanks,
> > >> brian
> > >>
> > >>
> > >> On Thu, 2007-11-29 at 22:16 +0100, Wolfgang Paul Rauchholz wrote:
> > >>
> > >> > Problems seems to be fixed by adding the following line t
> > >> > o/etc/modprobe.d/blacklist:
> > >> > blacklist snd-intel8x0m
> >
> > So, what module is actually used?
> >
> >
> > >> >
> > >> > https://bugzilla.redhat.com/show_bug.cgi?id=389521
> > >> >
> > >> > Thanks for your efforts Bill and Nigel.
> > >> >
> > >> >
> > >> >
> > >> > On Nov 28, 2007 8:56 AM, Wolfgang Paul Rauchholz
> > >> > <[EMAIL PROTECTED]> wrote:
> > >> > I booted the laptop and there is no sound.
> > >> > As mentioned before, the sound/no-sound situation occurs
> at
> > >> > random to me. I cannot recognize any pattern.
> > >> > The reason I have not taken out PulseAudio yet is that I
> > >> > suffered the same problem under FC6/FC7 for which I moved
> to
> > >> > Ubuntu 7.x where sound ran stablel. Therefor my hypothesis
> is
> > >> > that there is probably an issue with FC and not
> PulseAudio??
> > >> >
> > >> > I went to sound card detection and played the test sound
> with
> > >> > known result; no sound. The screen shows the following
> info:
> > >> > Vendor: Intel Corporation
> > >> > Model: 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio
> > >> > Controller (rev 03)
> > >> > Module: snd-intel8x0
> > >> > ...
> > >> > PCM device: Intel 82801DB-ICH4
> > >> >
> > >> >
> > >> > 1. alsamixer
> > >> > Card: PulseAudio Chip: PulseAudio
> > >> > View: [Playback] Capture All
> > >> > Item: Master
> > >> >
> > >> > There is one bar in the center of the screen. From the
> bottom
> > >> > to top the values are:
> > >> > <Master>, 65<>65, 00
> > >> > The channel is not muted.
> > >> > 2. [EMAIL PROTECTED] ~]# /sbin/lsusb
> > >> > Bus 001 Device 001: ID 0000:0000 Bus 004 Device 001: ID
> > >> > 0000:0000 Bus 003 Device 001: ID 0000:0000 Bus 002
> Device 002:
> > >> > ID 046d:c517 Logitech, Inc. Bus 002 Device 001: ID
> 0000:0000
> > >> > 3.
> > >> > [EMAIL PROTECTED] ~]# yum install alsa-lib
> > >> > Setting up Install Process
> > >> > Parsing package install arguments
> > >> > Package alsa-lib - 1.0.15-1.fc8.i386 is already installed.
> > >> > Nothing to do
> > >> >
> > >> > [EMAIL PROTECTED] ~]# rpm -q alsa-lib alsa-lib-1.0.15-1.fc8
> > >> >
> > >> >
> > >> > 4.
> > >> > [EMAIL PROTECTED] ~]#
> > >> > aplay /usr/lib/firefox-2.0.0.9/res/samples/test.wav
> > >> > Playing WAVE '/usr/lib/firefox-
> > >> > 2.0.0.9/res/samples/test.wav' : Unsigned 8 bit, Rate 22050
> Hz,
> > >> > Mono
> > >> > [EMAIL PROTECTED] ~]#
> > >> > aplay
> /usr/lib/openoffice.org/share/gallery/sounds/horse.wav
> > >> > Playing WAVE
> > >> > '/usr/lib/openoffice.org/share/gallery/sounds/horse.wav' :
> > >> > Signed 16 bit Little Endian, Rate 11025 Hz, Mono
> > >> > .....but I hear no no sound
> > >> >
> > >> > 5.
> > >> > [EMAIL PROTECTED] ~]# more /etc/modprobe.conf
> > >> >
> > >> > alias eth0 8139too
> > >> > alias scsi_hostadapter libata
> > >> > alias scsi_hostadapter1 ata_piix alias eth1 ipw2200
> > >> > alias snd-card-0 snd-intel8x0 options snd-card-0 index=0
> > >> > options snd-intel8x0 index=0
> > >> >
> > >> >
> > >> > 6.
> > >> > [EMAIL PROTECTED] ~]# cat /proc/asound/cards
> > >> >
> > >> > 0 [I82801DBICH4 ]: ICH4 - Intel 82801DB-ICH4
> > >> > Intel 82801DB-ICH4 with VIA1612A at
> irq
> > >> > 9
> > >> >
> > >> >
> > >> >
> > >> > 7. extract from /vat/log/messages
> > >> > ...
> > >> > Nov 28 08:13:27 MGPRJRWR kernel: agpgart: Detected an
> Intel
> > >> > 855PM Chipset.
> > >> > ...
> > >> > Nov 28 08:13:27 MGPRJRWR kernel: intel_rng: FWH not
> detected ...
> > >> > Nov 28 08:13:27 MGPRJRWR kernel:
> intel8x0_measure_ac97_clock:
> > >> > measured 50940 usecs Nov 28 08:13:27 MGPRJRWR kernel:
> intel8x0:
> > >> > clocking to 48000
> > >> > Nov 28 08:13:27 MGPRJRWR kernel: Unable to initialize
> codec #0
> > >> >
> > >> >
> > >> >
> > >> >
> > >> > But I also found these messages in the same file
> > >> > Nov 28 08:28:04 MGPRJRWR kernel: codec_write 0: semaphore
> is
> > >> > not ready for register 0x2 Nov 28 08:28:05 MGPRJRWR
> kernel:
> > >> > codec_write 0: semaphore is
> > >> > not ready for register 0x2
> > >> > Nov 28 08:30:55 MGPRJRWR kernel: codec_write 0: semaphore
> is
> > >> > not ready for register 0x2
> > >> > Nov 28 08:30:55 MGPRJRWR kernel: codec_write 0: semaphore
> is
> > >> > not ready for register 0x2 Nov 28 08:30:56 MGPRJRWR
> kernel:
> > >> > codec_read 0: semaphore is
> > >> > not ready for register 0x2c
> > >> > Nov 28 08:38:19 MGPRJRWR pulseaudio[2264]:
> module-alsa-sink.c:
> > >> > Error opening PCM device hw:0: Device or resource busy
> > >> > Nov 28 08:38:36 MGPRJRWR pulseaudio[2264]:
> module-alsa-sink.c:
> > >> > Error opening PCM device hw:0: Device or resource busy
> > >> > Nov 28 08:54:04 MGPRJRWR kernel: codec_read 0: semaphore
> is
> > >> > not ready for register 0x2c
> > >> >
> > >> >
> > >> > Nov 28 08:54:04 MGPRJRWR kernel: codec_read 0: semaphore
> is
> > >> > not ready for register 0x2c; this record was created when
> > >> > plying the the test sound in sound card detection.
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> > On Nov 28, 2007 12:00 AM, Bill Unruh <[EMAIL PROTECTED]
> >
> > >> > wrote:
> > >> > On Tue, 27 Nov 2007, Nigel Henry wrote:
> > >> >
> > >> > > On Tuesday 27 November 2007 21:09, you wrote:
> > >> > > > Nigel,
> > >> > > >
> > >> > > > sound is not working now.
> > >> > > > I ran report again and checked differences. There
> > >> > are 4 loaded modules
> > >> > > > missing:
> > >> > > > vfat, fat, usb_storage and usblp
> > >> >
> > >> >
> > >> > None of this has anything to do with sound.
> > >> >
> > >> > Run alsamixer. What does it say. As he mentioned,
> make
> > >> > sure that nothing is muted and that all sliders
> are at
> > >> > least half way up.
> > >> > You can always refine things later.
> > >> >
> > >> > Then run aplay with some .wav file as the source
> > >> > and see if there are any responses, error
> messages,
> > >> > etc, and see if there
> --
> Dr. Brian L Scipioni
> 909 Austin Ave
> Atlanta, GA 30307
> home: 404.525.8911
> cell: 404.771.3740
> [EMAIL PROTECTED]
>
>
>
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user
