[regression] sound card not working after clean install of Dapper, Edgy and Feisty

Bug #94333 reported by Maciej Bukczynski
32
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Low
Unassigned

Bug Description

Although it is visible, Ubuntu cannot fully configure my sound card.

I have a Soundblaster Live card CT4760, and have also tried an SB Live Platinum SB0060 card (both use emu10k1 driver) and an older Soundblaster (using the ens1371 driver). Same behaviour. The machine is running an Intel D850GB motherboard (without the onboard sound option), with the last available firmware. The most interesting thing is that the Live Platinum card had the attached LiveDrive bay, and the headphone out put on it worked. None of the connections and channels on the PCI card itself worked, yet the LiveDrive extension was configured as the primary audio device. No "Volume" or "Master Volume" track was available in the mixer, the primary was just "Headphone Out".

I have tried a clean installation of Dapper, Edgy and Feisty. All exhibit the same problem. However, I used the same hardware years ago with either Warty or Hoary and had no issues. The sound worked out of the box.

Anyways, without further ado, here are the symptoms.

1. The device is listed by lspci

$ sudo lspci -nnvv
(...)
02:0c.0 Multimedia audio controller [0401]: Creative Labs SB Live! EMU10k1 [1102:0002] (rev 07)
        Subsystem: Creative Labs CT4760 SBLive! [1102:8040]
        Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Interrupt: pin A routed to IRQ 19
        Region 0: I/O ports at df00 [size=32]
        Capabilities: [dc] Power Management version 1
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

02:0c.1 Input device controller [0980]: Creative Labs SB Live! Game Port [1102:7002] (rev 07)
        Subsystem: Creative Labs Gameport Joystick [1102:0020]
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 32
        Region 0: I/O ports at dff0 [size=8]
        Capabilities: [dc] Power Management version 1
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
(...)

2. The modules are loaded:

$ lsmod |grep snd
snd_emu10k1_synth 8448 0
snd_emux_synth 37120 1 snd_emu10k1_synth
snd_seq_virmidi 8960 1 snd_emux_synth
snd_seq_midi_emul 7936 1 snd_emux_synth
snd_emu10k1 138784 1 snd_emu10k1_synth
snd_ac97_codec 100388 1 snd_emu10k1
ac97_bus 3456 1 snd_ac97_codec
snd_pcm_oss 45184 0
snd_mixer_oss 18304 1 snd_pcm_oss
snd_pcm 81284 3 snd_emu10k1,snd_ac97_codec,snd_pcm_oss
snd_page_alloc 11272 2 snd_emu10k1,snd_pcm
snd_util_mem 6016 2 snd_emux_synth,snd_emu10k1
snd_hwdep 10884 2 snd_emux_synth,snd_emu10k1
snd_seq_oss 35712 0
snd_seq_midi 9728 0
snd_rawmidi 26240 3 snd_seq_virmidi,snd_emu10k1,snd_seq_midi
snd_seq_midi_event 8576 3 snd_seq_virmidi,snd_seq_oss,snd_seq_midi
snd_seq 54768 8 snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_timer 24708 3 snd_emu10k1,snd_pcm,snd_seq
snd_seq_device 9612 7 snd_emu10k1_synth,snd_emux_synth,snd_emu10k1,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
snd 57220 13 snd_emux_synth,snd_seq_virmidi,snd_emu10k1,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_hwdep,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
soundcore 9440 1 snd

3. dmesg shows some clues

$ dmesg
(...)
[ 47.522250] ALSA /home/maciek/alsa-src/alsa-driver-1.0.14rc3/pci/ac97/ac97_codec.c:2051: AC'97 0 does not respond - RESET
[ 47.522265] ALSA /home/maciek/alsa-src/alsa-driver-1.0.14rc3/pci/ac97/ac97_codec.c:2060: AC'97 0 access is not valid [0x0], removing mixer.
[ 47.523549] ACPI: PCI interrupt for device 0000:02:0c.0 disabled
[ 47.523565] EMU10K1_Audigy: probe of 0000:02:0c.0 failed with error -5
(...)

4. /dev/dsp does NOT exist

5. Nowhere else is the card visible:

$ cat /proc/asound/cards
--- no soundcards ---

$ aplay -l
aplay: device_list:222: no soundcards found...

$ alsamixer
alsamixer: function snd_ctl_open failed for default: No such device

$ sudo invoke-rc.d alsa-utils restart
 * Shutting down ALSA... * warning: 'alsactl store' failed with error message 'alsactl: save_state:1253: No soundcards found...'... [fail]
 * Setting up ALSA... [ OK ]
invoke-rc.d: initscript alsa-utils, action "restart" failed.

I am happy to provide any more information. I have literally spent weeks going in circles unable to figure this one out.

Revision history for this message
Tim Gardner (timg-tpi) wrote :

Please attach (do not inline) in separate files the contents of:
dmesg > dmesg.txt
lspci -vv > lspci.txt
sudo dmidecode > dmidecode.txt

Changed in linux-source-2.6.20:
assignee: nobody → timg-tpi
importance: Undecided → Low
status: Unconfirmed → Needs Info
Revision history for this message
Maciej Bukczynski (korn) wrote :

1 of 3

Revision history for this message
Maciej Bukczynski (korn) wrote :

2 of 3

Revision history for this message
Maciej Bukczynski (korn) wrote :

3 of 3

Tim Gardner (timg-tpi)
Changed in linux-source-2.6.20:
assignee: timg-tpi → ubuntu-kernel-team
status: Needs Info → Confirmed
Revision history for this message
Thomas Bishop (tombish) wrote :

I too have had this problem. My sound card is the Creative Audigy LS. Like the bug above it worked in Warty or Hoary but now in feisty it does not work out to the box.

Revision history for this message
eppy 1 (choppy121212) wrote :

I get the same issue with my Soundblaster Live 5.1, no sound output from mp3 files, videos, Gnome sounds, etc. It worked in Dapper Drake.

I have an onboard sound chip (CMedia PCI CMI8738) that I switch to the soundblaster in the Gnome Soundblaster, but the Soundblaster still doesn't work. The volume in alsamixer is not muted.

I can only use the microphone with the soundblaster, but that's another issue, as I can't mute it and there's a constant buzz because of this.

Revision history for this message
eppy 1 (choppy121212) wrote :
Revision history for this message
eppy 1 (choppy121212) wrote :
Revision history for this message
eppy 1 (choppy121212) wrote :
Revision history for this message
Maciej Bukczynski (korn) wrote :

Eppy, I am not convinced you have the same problem. In the original bug, the EMU10K1 fails to load:

[ 45.986859] ACPI: PCI Interrupt 0000:02:0a.0[A] -> GSI 22 (level, low) -> IRQ 21
[ 47.004710] AC'97 0 does not respond - RESET
[ 47.004721] AC'97 0 access is not valid [0x0], removing mixer.
[ 47.005801] ACPI: PCI interrupt for device 0000:02:0a.0 disabled
[ 47.005817] EMU10K1_Audigy: probe of 0000:02:0a.0 failed with error -5

Your dmesg does not show any signs of this. It assigns the card to IRQ 5 and then does not complain:

[ 37.148000] ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 5
[ 37.148000] PCI: setting IRQ 5 as level-triggered
[ 37.148000] ACPI: PCI Interrupt 0000:00:09.0[A] -> Link [LNKD] -> GSI 5 (level, low) -> IRQ 5

I could be wrong, but I think the characteristic feature of this bug is the "AC'97 does not respond" bit.

Have you disabled your onboard sound? Does the snd_emu10k1 show up on lsmod? Please ensure you have followed all the steps here: http://ubuntuforums.org/showthread.php?p=2387440 .. if you are sure you still have a problem, file a new bug report.

Revision history for this message
eppy 1 (choppy121212) wrote :

Thanks for responding Maciej---the weird thing is that input (via microphone) is working, but the echo from the microphone all I can hear as "output"--mp3s play, but I can't hear them. I will get back to you ASAP and follow those steps, but my soundblaster fell out of the pci carriage so I have to turn the computer off to put it back in.

Revision history for this message
eppy 1 (choppy121212) wrote :

OK I got it back in. It works but only if I select (the new option) "multichannel playback" in (the new) gnome sound configuration. "Auto" doesn't seem to work.

I filed it as Bug 102880

Revision history for this message
eppy 1 (choppy121212) wrote :

BTW my Soundblaster (that works) is an SB0060, if that helps this bug at all. Sorry for triple posting..

Revision history for this message
Finn61 (finn61) wrote :

I'm having this exact problem with emu10k1. Is there a workaround?

I know this bug has a low priority but is it likely to be progressed any time soon?

Revision history for this message
Brian J. Murrell (brian-interlinx) wrote :

And I too am having this problem on gutsy with my SBLive. Is there any hope of resolving it? This only just started when i swapped all of my hardware into a new ASUS M2NPV-VM motherboard.

Any hints on how to debug. I too will attach:

dmesg > dmesg.txt
lspci -vv > lspci.txt
sudo dmidecode > dmidecode.txt

Revision history for this message
Brian J. Murrell (brian-interlinx) wrote :
Revision history for this message
Brian J. Murrell (brian-interlinx) wrote :
Revision history for this message
Brian J. Murrell (brian-interlinx) wrote :
Revision history for this message
zenon (eahm04) wrote :
Download full text (3.6 KiB)

Although it is visible, Ubuntu cannot fully configure my sound card.

And I too am having this problem on gutsy with my SBLive and no sound.

I have tried a clean installation of Dapper, Edgy and Feisty. All exhibit the same problem

ubuntu gutsy
model : CT4760 SBLive!

The modules are loaded:

$ lsmod |grep snd
snd_rtctimer 4384 0
snd_emu10k1_synth 8192 0
snd_emux_synth 35456 1 snd_emu10k1_synth
snd_seq_virmidi 8064 1 snd_emux_synth
snd_seq_midi_emul 7680 1 snd_emux_synth
snd_emu10k1 137248 3 snd_emu10k1_synth
snd_util_mem 5760 2 snd_emux_synth,snd_emu10k1
snd_hwdep 10244 2 snd_emux_synth,snd_emu10k1
snd_seq_dummy 4740 0
snd_seq_oss 33152 0
snd_seq_midi 9600 0
snd_rawmidi 25728 3 snd_seq_virmidi,snd_emu10k1,snd_seq_midi
snd_intel8x0 34972 0
snd_ac97_codec 100644 2 snd_emu10k1,snd_intel8x0
ac97_bus 3200 1 snd_ac97_codec
snd_pcm_oss 44672 0
snd_mixer_oss 17664 1 snd_pcm_oss
snd_seq_midi_event 8448 3 snd_seq_virmidi,snd_seq_oss,snd_seq_midi
snd_seq 53232 9 snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul,snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_seq_device 9228 8 snd_emu10k1_synth,snd_emux_synth,snd_emu10k1,snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
snd_pcm 80388 5 snd_emu10k1,snd_intel8x0,snd_ac97_codec,snd_pcm_oss
snd_timer 24324 4 snd_rtctimer,snd_emu10k1,snd_seq,snd_pcm
snd_page_alloc 11400 3 snd_emu10k1,snd_intel8x0,snd_pcm
snd 54660 17 snd_emux_synth,snd_seq_virmidi,snd_emu10k1,snd_hwdep,snd_seq_oss,snd_rawmidi,snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_pcm,snd_timer
soundcore 8800 1 snd

$aplay -l

**** List of PLAYBACK Hardware Devices ****
card 0: I82801BAICH2 [Intel 82801BA-ICH2], device 0: Intel ICH [Intel 82801BA-ICH2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: Live [SBLive! Platinum [CT4760P]], device 0: emu10k1 [ADC Capture/Standard PCM Playback]
  Subdevices: 32/32
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
  Subdevice #4: subdevice #4
  Subdevice #5: subdevice #5
  Subdevice #6: subdevice #6
  Subdevice #7: subdevice #7
  Subdevice #8: subdevice #8
  Subdevice #9: subdevice #9
  Subdevice #10: subdevice #10
  Subdevice #11: subdevice #11
  Subdevice #12: subdevice #12
  Subdevice #13: subdevice #13
  Subdevice #14: subdevice #14
  Subdevice #15: subdevice #15
  Subdevice #16: subdevice #16
  Subdevice #17: subdevice #17
  Subdevice #18: subdevice #18
  Subdevice #19: subdevice #19
  Subdevice #20: subdevice #20
  Subdevice #21: subdevice #21
  Subdevice #22: subdevice #22
  Subdevice #23: subdevice #23
  Subdevice #24: subdevice #24
  Subdevice #25: subdevice #25
  Subdevice #26: subdevice #26
  Subdevice #27: subdevice #27
  Subdevice #28: subdevice #28
  Subdevice #29: subdevice #29
  Subdevice #30: subdevice #30
  Subdevice #31: subdevice #31
card 1: Live [SBLive! Platinum [...

Read more...

Revision history for this message
zenon (eahm04) wrote :
Revision history for this message
zenon (eahm04) wrote :

i have just this problem from Dapper, Edgy , Feisty, and now Gutsy

i hope the resolve this problem.

Revision history for this message
mshtawythug (mshtawythug) wrote :
Revision history for this message
mshtawythug (mshtawythug) wrote :
Revision history for this message
mshtawythug (mshtawythug) wrote :
Revision history for this message
mshtawythug (mshtawythug) wrote :

I had this problem on Gutsy and now on Feisty
my sound card is HDA Intel and the chip is Conexant CX20551
i thought the problem is from Gutsy thats why i installed Feisty
i ve tried every thing u can possibly imagine i m still new to linux but i googled this problem and tried every thing and this page came to my hand and i m now listing my files hoping to get help

Revision history for this message
mshtawythug (mshtawythug) wrote :

By the way its not only on Dapper, Edgy and Feisty its also a bug on Gutsy

Revision history for this message
mshtawythug (mshtawythug) wrote :

Come on guys the new ubuntu 7.10 was released and u didnt find a fix please this is so important i wanna change from windows to linux but i can't because i still need to hear some music

Revision history for this message
bweinel (tuberadio) wrote :

I am having the same issue with my Intel D850GB motherboard and the new kubuntu 8.04 kernel 2.6.24-15. I am running a Creative Sound Blaster PCI128 (Ensoniq). Usually when I cold boot it doesn't load the sound card drivers. However occasionally when I reboot, it loads them sometimes... sometimes not. I will attach a copy of my dmesg, lspci, dmidecode outputs.

Revision history for this message
bweinel (tuberadio) wrote :
Revision history for this message
bweinel (tuberadio) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Revision history for this message
Gary (gormfach) wrote :

Well, someone pulled the plug too soon. I had an Intel board running perfectly with its Audigy emu10k1 driver on Ubuntu 8.10, kernal 2.6.27-7, but when I updated the new install with 278+ updates to 2.6.27-11, no way I can get the card to work. In fact on this system, I recall running the old kernal and regaining sound on a previous install, but when I tried it again on this install (running 2.6.27-7), could not regain the sound. Ended up destroying the system, since I am a newbie, after going through the Sound Troubleshooting guide. Have no clue what happened. Have an old Dell system at work that exhibits no such problems, so it must be Audigy centric.

Revision history for this message
mshtawythug (mshtawythug) wrote :

i am using the same laptop toshiba satellite p100 and its working perfectly

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Just curious if anyone who had this issue was able to test the latest Jaunty 9.04 release yet and confirm if this issue remains? Please let us know. Thanks.

http://www.ubuntu.com/getubuntu/download

Revision history for this message
Gary (gormfach) wrote : Re: [Bug 94333] Re: [regression] sound card not working after cleaninstall of Dapper, Edgy and Feisty
Download full text (6.1 KiB)

This was a very frustrating problem for my Creative Audigy card. I did an
upgrade to 9.04 from 8.10 AND the problem still existed on Gnome. I then
installed KDE, since my machine was pretty robust. Things started to bog
down for various reasons, so I decided to do a clean install of KUBUNTU
9.04, since I am still in learning/test mode, i.e. nothing to lose really.
So far, the sound issue went away. There is definitely some problem related
to the 8 series kernal update and the carry-over to a 9.04 upgrade.

GEA

----- Original Message -----
From: "Leann Ogasawara" <email address hidden>
To: <email address hidden>
Sent: Monday, May 04, 2009 7:31 AM
Subject: [Bug 94333] Re: [regression] sound card not working after
cleaninstall of Dapper, Edgy and Feisty

Just curious if anyone who had this issue was able to test the latest
Jaunty 9.04 release yet and confirm if this issue remains? Please let us
know. Thanks.

http://www.ubuntu.com/getubuntu/download

--
[regression] sound card not working after clean install of Dapper, Edgy and
Feisty
https://bugs.launchpad.net/bugs/94333
You received this bug notification because you are a direct subscriber
of the bug.

Status in “linux” source package in Ubuntu: Incomplete
Status in “linux-source-2.6.20” source package in Ubuntu: Won't Fix

Bug description:
Although it is visible, Ubuntu cannot fully configure my sound card.

I have a Soundblaster Live card CT4760, and have also tried an SB Live
Platinum SB0060 card (both use emu10k1 driver) and an older Soundblaster
(using the ens1371 driver). Same behaviour. The machine is running an Intel
D850GB motherboard (without the onboard sound option), with the last
available firmware. The most interesting thing is that the Live Platinum
card had the attached LiveDrive bay, and the headphone out put on it worked.
None of the connections and channels on the PCI card itself worked, yet the
LiveDrive extension was configured as the primary audio device. No "Volume"
or "Master Volume" track was available in the mixer, the primary was just
"Headphone Out".

I have tried a clean installation of Dapper, Edgy and Feisty. All exhibit
the same problem. However, I used the same hardware years ago with either
Warty or Hoary and had no issues. The sound worked out of the box.

Anyways, without further ado, here are the symptoms.

1. The device is listed by lspci

$ sudo lspci -nnvv
(...)
02:0c.0 Multimedia audio controller [0401]: Creative Labs SB Live! EMU10k1
[1102:0002] (rev 07)
        Subsystem: Creative Labs CT4760 SBLive! [1102:8040]
        Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Interrupt: pin A routed to IRQ 19
        Region 0: I/O ports at df00 [size=32]
        Capabilities: [dc] Power Management version 1
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

02:0c.1 Input device controller [0980]: Creative Labs SB Live! Game Port
[1102:7002] (rev 07)
        Sub...

Read more...

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

@Maciej, since you are the original bug reporter, can you comment if this issue remains? Gary's previous comment indicates this may be resolved for him but he has a different sound card than what you reported this bug against.

Revision history for this message
peter (peter-neuweiler) wrote : Re: [Bug 94333] Re: [regression] sound card not working after clean install of Dapper, Edgy and Feisty

I am not the original bug reporter of this bug.
Peter

Leann Ogasawara wrote:
> @Maciej, since you are the original bug reporter, can you comment if
> this issue remains? Gary's previous comment indicates this may be
> resolved for him but he has a different sound card than what you
> reported this bug against.
>
>

--
_____________________________________________________________________
Peter Neuweiler 0041 (0)78 903 20 49
Business IT specialist WISS <email address hidden>
Rütistr. 20a
CH-8134 Adliswil

Revision history for this message
Jim Lieb (lieb) wrote :

Sound problems are most often hardware specific. This bug applies to the soundblaster ct4760 card and a no longer supported kernel. If you have a sound problem with the current release of Ubuntu on your system please file a new bug specific to your system. Thank you.

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.