From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001943]: No sound since ~2.6.3
Date: Tue, 20 Jun 2006 19:49:53 +0200 [thread overview]
Message-ID: <d33a290e6eed2669030f671427edd628@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1943>
======================================================================
Reported By: hazelsct
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 1943
Category: PCI - ali5451
Reproducibility: always
Severity: major
Priority: normal
Status: new
Distribution: Debian etch
Kernel Version: 2.6.8 through 2.6.15-rc5
======================================================================
Date Submitted: 03-19-2006 16:15 CET
Last Modified: 06-20-2006 19:49 CEST
======================================================================
Summary: No sound since ~2.6.3
Description:
Greetings,
Running Debian woody/sarge/etch, the last time sound worked on my Fujitsu
Lifebook P2120 was with 2.6.3 (or maybe 2.6.5, but not with 2.6.8 or
anything since). Esd doesn't work, nor do system beeps, and GNOME volume
control says no volume control elements are found. I can get ALSA working
with 2.6.8 on all of my other machines, and with 2.6.15 on all that I have
tried. alsamixer runs and shows levels which I can change, but still no
sound.
An identical ALSA setup worked with sarge under 2.6.3 but not 2.6.8. Tried
running alsaconf again to no avail. Under 2.6.3, at least when doing
hardware mute and then un-mute (Fn-F3), un-mute beeps; on newer kernels,
there's no beep.
Now under Debian etch (testing), even 2.6.3 no longer works properly:
sounds played through esd simply repeat the first second or so over and
over again. I keep upgrading the kernel (most recently to 2.6.16-rc5 in
experimental) hoping that this time it will finally work, but it hasn't in
that long...
Debian etch has alsa 1.0.10-3, and lsmod shows the following sound modules
installed:
snd_ali5451 20172 1
snd_ac97_codec 82784 1 snd_ali5451
snd_ac97_bus 2048 1 snd_ac97_codec
soundcore 8672 1 snd
snd_page_alloc 9800 1 snd_pcm
lspci shows:
0000:00:04.0 Multimedia audio controller: ALi Corporation M5451 PCI
AC-Link Controller Audio Device (rev 01)
What other information would help to diagnose/fix this problem?
Thanks,
Adam
======================================================================
----------------------------------------------------------------------
hazelsct - 06-20-06 19:47
----------------------------------------------------------------------
Thanks, that's a lot of work.
Oh, cool. On the Debian alioth alsa list, someone suggested something
which fixed the problem, so all done.
----------------------------------------------------------------------
hazelsct - 06-20-06 19:49
----------------------------------------------------------------------
Now how to close this bug?
Issue History
Date Modified Username Field Change
======================================================================
03-19-06 16:15 hazelsct New Issue
03-19-06 16:15 hazelsct Distribution => Debian etch
03-19-06 16:15 hazelsct Kernel Version => 2.6.8 through
2.6.15-rc5
06-20-06 00:29 hazelsct Note Added: 0010322
06-20-06 00:33 rlrevell Note Added: 0010323
06-20-06 19:41 tiwai Note Added: 0010343
06-20-06 19:47 hazelsct Note Added: 0010346
06-20-06 19:49 hazelsct Note Added: 0010348
======================================================================
next reply other threads:[~2006-06-20 17:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 17:49 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-20 17:58 [ALSA - driver 0001943]: No sound since ~2.6.3 bugtrack
2006-06-20 17:47 bugtrack
2006-06-20 17:41 bugtrack
2006-06-19 22:33 bugtrack
2006-06-19 22:29 bugtrack
2006-03-19 15:15 bugtrack
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d33a290e6eed2669030f671427edd628@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox