Sound doesn't work after restart, only works on cold boot

[Matthew Nuzum]

If I choose System --> Quit --> Restart when the desktop comes back up there is no sound at the login prompt or after logging in. Trying to play an audio file with rhythmbox results in the song not playing (the play button appears to be active, but the progress bar does not move - attempts to move the progress bar result in it returning to the 0:00 position).

If I instead choose to shut down the computer and then use the power button to turn the computer on the sound works great. I hear the sound at the login prompt and the login sound. Rhythmbox works as exepected.

I'm running a fully updated (as of Aug 22nd 2006) Dapper and kernel 2.6.15-26-686 #1 SMP PREEMPT on a Toshiba Satelite A105 notebook. It has a Core Duo T2400 cpu and HDA Intel (alsa mixer) sound card.

[Frank Hahn (fhahn)]

Matthew:

I have a Gateway 7510GX laptop that has an ATI chipset that does the same thing. If I start from the machine being turned off, I will have sound. If I restart the laptop, there is no sound at this point. I have not found a way to get the sound to come back.

If I restart from Ubuntu and then go into Windows XP Home, then I have sound in XP.

I have not tried restrting from Windows back to Ubuntu to see what happens.

Frank Hahn

[Albrecht Mühlenschulte (a7p)]

Could you please try to play a tune with an other music player. Best would be if you could try:

* totem (which also uses gstreamer)
* something that directly talks to alsa (mplayer or mpg321 for example).

Please also report the ubuntu-release you are using.

[Frank Hahn (fhahn)]

--- a7p <email address hidden> wrote:

> Could you please try to play a tune with an other
> music player. Best
> would be if you could try:
>
> * totem (which also uses gstreamer)
> * something that directly talks to alsa (mplayer or
> mpg321 for example).
>

I tried with mplayer
2:0.99+1.0pre7try2+cvs20060117-0ubuntu8 and still no
luck. I tried a regular CD, an MP3 file and a WAVE
file.

> Please also report the ubuntu-release you are using.
>
> ** Changed in: Ubuntu
> Assignee: (unassigned) => a7p
> Status: Unconfirmed => Needs Info
>
On this laptop, I have Ubuntu 6.06LTS with kernel
2.6.15-27-386.

Sorry for the delay in replying.

--

Frank Hahn

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

[Gabriel Pannwitz (gabkdlly)]

I also seem to be having this problem on Xubuntu Edgy. However, I do not get reliable sound when booting from a cold start. On some cold boots it works, sometimes it does not. However, restarting does seem to consistently prevent sound from playing with mplayer.

The strange thing is, I have sound in Ekiga (apparently always), as well as in in Flash (sometimes).

[Gabriel Pannwitz (gabkdlly)]

There is more output to be seen on the console.

[Gabriel Pannwitz (gabkdlly)]

On boots when sound works fine, I can access my soundcard simply by issuing:
$ alsamixer

However, on boots where sound does not work properly, this command accesses not my soundcard, but rather my TV tuner:
Card: SAA7134

In order to access my soundcard on such boots, I have to issue:
$ alsamixer -c 1
Card: VIA 8235

Is there a way to set which of these devices is supposed to be the default?

Thanks.

[Albrecht Mühlenschulte (a7p)]

Sounds as if the mixing devices get loaded in differend order, so that they get differend device names. There is a way to explicitly assign the order in which modules get loaded (and hence get named) - I just forgot how to do that. But I think this is a Ubuntu bug, such stuff should not happen.

Could you send the logs of a bootprocess with and without working default sound?

$ dmesg > worksfine.txt
$ dmesg > unfine.txt

Can the original reporter please check if his problem does have the same reason (via alsamixer -c 1/2 or whatever)?

[Albrecht Mühlenschulte (a7p)]

I just gut the information, that the ALSA module soundcard problem should be fixed in herd-2 (which is the current snapshot of feisty). Could you (both) try to repoduce the bug with Herd-2?

http://www.ubuntu.com/testing/herd2?highlight=%28herd-2%29#head-5bc48adba3c6627b30928557c0a41eada2babbad

Doing the test with the liveCD should be good enough.

Thanks for your work and your prompt replies :) (I am not that fast).

[Gabriel Pannwitz (gabkdlly)]

I have to correct myself: restarting does not consistently break sound. It is hit and miss, whether I reboot or cold start.

(Although, I have to admit that I have installed recommended updates since my last post, and it could be that the problem is less severe now.)

I tried rebooting the Edgy Xubuntu live CD a couple of times, but could not reproduce the problem.

The Feisty Herd 2 Xubuntu live CD does not want to boot on my system. First it hangs after unsuccessfully trying to mount swap, and then returns [OK] from a fsck. When nothing happens after a couple of minutes, hitting ALT-CTRL-DEL outputs that some processes have been killed, and then it proceeds to start X. X starts, but panels and the desktop do not. I can kill X with ALT-CTRL-BACKSPACE, but a renewed login does not help the situation.

In conclusion, since I can't boot the Feisty CD, I am unable to say whether this problem persists on Feisty.

Just let me know if there is anything else I can do to help get to the bottom of this problem.

Cheers.

[Slight Slightly (slight--deactivatedaccount)]

I have what seems to be the same problem. On cold boot my motherboard's built-in soundcard is detected, and on restart it's my Audigy (which is the one I want to use).

Attached is dmesg output for the former, latter to follow.

[Robert (robrwo)]

I also have this problem on a Lenovo ThinkPad Z60m with an Intel soundcard (using the snd-hda-intel driver).

Sound only works from a cold start, not from resuming from hibernation. I've tried gstreamer-based and xine-based players.

Backstory: upgraded to Feisty, sound stopped working. Reinstalled Feisty from scratch, sound worked. Installed ESD and sound stopped working. Removed ESD, still no sound. Installed latest ALSA from ALSA project website (v1.0.14rc3), which at least had alsaconf utility that has helped me with similar problems w/Debian Etch. Still no sound. Added "options snd-hda-intel index=0" to modprobe.d, set other indices to -2, and it only works with a cold start. (I should probably remove "options snd-hda-intel index=0" from modprobe to see if that's unrelated to this.)

Also, I'm using XUbuntu, as many others here are.

[Seafoor (ricardovdbroek)]

Hey all,

I have this problem as well. I'm running Ubuntu Feisty.

When it's not working the way I want, you don't hear system sounds, sound comming from my regular music player XMMS nor is there sound in flash. I do have sound in Rhytmbox though.
It works on random, rebooting or a cold start appear to have the same chance of working.

When the sound is working the way it should and I call alsamix in the command line, I get the right sound card: C-Media PCI CMI8738-MC6
calling alsamix -c 1 shows the other card: SiS SI7012. (the latter btw is a device on my mainboard, the first (right) one is a PCI card I installed).

When the sound is not working correctly, the results are switched: alsamix shows the card on the mainboard and alsamix -c 1 the PCI card.

I did some testing, cold starting and rebooting Ubuntu, booting Windows XP in between a couple of times. I can't find a pattern in it though: whether the sound works or not appears to be random.

I'll post the outputs of dmsg in both situation too, I hope they'll be usefull.

Thanx and good luck!

[Robert (robrwo)]

This is interesting: while trying to fix other problems with my video, I switched video drivers from the xserver-xorg-video-i810 driver to xserver-xorg-video-intel driver. And now the sound seems to work even with a warm reboot.

Is it possible that there's a conflict with i810 and the sound card (also an intel card)?

I note that with the intel driver, more video modes are detected (still some problems), and the intermittent problems with my network cards (also intel cards) seem to be solved, though still too early to tell.

[Saiko Bob (saiko-bob)]

I've had this problem ever since installing Feisty... but I think I've just found a solution that works for me.

The problem I had was that when booting into Feisty, it would randomly set the default sound card to one of my two sound cards. The result is that sometimes I would get sound, sometimes I wouldn't.

Following <a href="http://doc.gwos.org/index.php/Comprehensive_Sound_Problems_Solutions_Guide#Configuring_default_soundcards_.2F_stopping_soundcards_from_switching">this guide</a>, I modified /etc/modprobe.d/alsa-base and specified which sound device should always be the default. It's been working perfectly ever since.

Hope it helps for you.

Cheers,
SB

[Robert (robrwo)]

I only have one soundcard, and had tried adding an index=0 to it. It did not help the problem.

[Robert (robrwo)]

By the way. with the intel driver, the sound does not work with resuming.

[Gabriel Pastor (melesse)]

I had the same problem with feisty and solved it.
I have 2 sound cards, and it seems that sometimes the wrong sound card is the default sound device.

$ sudo asoundconf list
Names of available sound cards:
Intel
CA0106

The first one is integrated on the motherboard, and the second one (an audigy) is the one I use.

To solve the problem, I just set the default sound card to the audigy:
$ sudo asoundconf set-default-card CA0106

Then the sound works !
Hope it helps.

[Seafoor (ricardovdbroek)]

I've followed the guide Saiko Bob posted, and so far it's worked on every boot! :) I'll post again if otherwise, but I think it's fixed for me now.

Thanx!!!!

[Oleg Vaskevich (olegv)]

Thanks Gabriel, after doing your procedure everything works again!

[Robert (robrwo)]

None of the suggestions for setting the indices of drivers has worked for me. So what can I do to help fix this bug?

My guess is that something is not being initialised, but by default (from a cold boot) the setting is initialised, but (for whatever reason) the setting is not reset in a warm boot or in hibernation.

[Ben (bbooker5)]

Gabriel, I tried what you said. It didn't work:(

I am having a problem very similar. I have two sound cards - one is built into the motherboard and one is a usb audio, I mainly use the USB. The only reason I do not disable the onboard is because the audio input is not being recognized on my usb card. I never have a problem with sound except on myspace in firefox. The sound is only coming out of the onboard from MySpace. Youtube does this also. I guess it's firefox altogethor.

Here is the output from the first command.
$ sudo asoundconf list
Names of available sound cards:
V8237
WE
UART

I believe UART is my usb sound. I try this.
$ sudo asoundconf set-default-card UART

...Still coming out of onboard. I haven't tried to restart my system yet, perhaps that will fix. Or maybe I will have to disable onboard and just live with it :(

[Cory Dodt (corydodt)]

My problem is with a Lenovo Z61M, almost identical to Robert's -- and I have exactly the same problem.

- Boots from hibernate: no sound

- Warm boot after boot from hibernate: no sound

- Cold boot after boot from hibernate: sound works okay.

Sound chip is "HDA Intel", onboard, and it's the only sound card in the laptop.

[Robert (robrwo)]

See Bug 80893 https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/80893

It seems that editing /etc/default/acpi-support
and setting "HIBERNATE_MODE=platform" has fixed the problem on my ThinkPad Z60m.

[barsalatino (barsalatino)]

Gracias Gabriel Pastor, tenia el mismo problema con la Sound Blaster Audigy 2 ZS y el chipset de la placa base iNTEL y lo pude solucionar .
Saludos

[Maxster (maxime-damecour)]

Ok, i got kind of the same problem.
I have a sb live 5.1 dell oem, and i only get sound from it every odd boot. if there is no sound i have to reboot, restarting does not help.
I am suspecting my mother board. Wen there is no sound the ALSA mixer still finds the card and everything seems to be ok, i can play some tunes and the progress bar moves.

so im thinking of getting a new mother board.

[Nitinn (nacky-4-u)]

Solution friends

Friends it just simple step ..
1. hibernate your system with pcm ,master ,line-in turn to mute
         It can be done by double clickin on sound icon on panel there mute all button .

2. When u wake up from hibernate ..
        Double click on sound icon again and turn them to unmute .

                     It will work ( it did for me )

Another solution firends (if previous dont work)

1. Hibernate your system normally .
2. When you want sound , double click on sound icon on panel and mute all channel like master,pcm ,line-in everythin .
3. Set your systen to suspend(by single right clicking on icon ) from Battery icon (for laptops), desktop can choose other normal way.
       suspending sysem takes around 50 seconds (not a big task )
4. Recover from suspend after few seconds and again open volume control(ctrl+O) and unmute all channels (pcm,master)
5. Play your music player and get sound back ..

                   This will surely work as it workd on more than 10 diffrent config system
                                          for any further querry in dis contact me on gmail - <email address hidden> / <email address hidden>

[trollord (trollenlord)]

This bug report is full of entirely unrelated problems (for different sound cards and chipsets) so it is impossible to track what was actually related to what and what was fixed already and what not.

We are closing this bug report because it lacks the information we need to investigate the *original* problem (poster has been unresponsive), as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".

In case you are having still problems, but they are not definitely related to the original one, please open new bug tickets for them. In that case please report the information mentioned in https://help.ubuntu.com/community/DebuggingSoundProblems as attachments. That should make handling them fast and efficient.

Thanks again!