I'm using 10.04. I had sound this morning, and after a reboot ... no sound. When I click on the speaker in the panel and choose "Sound Preferences..." and then choose "Hardware" it's blank. In the "output" tab all I have is "Dummy Output" (it's stereo at least). I don't remember updating Ubuntu since the morning, but I might have. If I type in "pulseaudio" into terminal I get this:
I run windows XP sp3 and Ubuntu 10.10 on an ASUS EeePC 1000HE (I know its a pretty old model). I have been facing this problem ever since installing Ubuntu side by side with Win (*not WUBI*). Every time I switch to Ubuntu after a reboot from windows, I get no sound from Ubuntu, the sound driver appears to be working fine, but there is just no audio output. This problem does not occur if I do a clean boot to Ubuntu after shutting down Windows.
I've recently upgraded to 10.04, and never had any problems in 9.10, but now, sometimes when Banshee attempts to play a sound file, it will kill my sound output until I reboot. Haven't been able to get anywhere by fiddling with ALSAmixer or the like, and everything is just fine on reboot, but the files don't always cause problems, and they were all fine back in 9.10. Has anyone else encountered this? I've been unable to find any other references to this problem.
I've been having some issues with my sound for a few weeks. Every time I reboot, my sound is muted. I have to open up alsamixer every time and unmute it manually. It is not the "master volume" that is muted but instead the "speaker" volume is the one that is muted. This started when i started up my computer and the ubuntu log-in sound started playing extremely loud. I quickly tried to turn down the volume while it was still booting and ever since then, i have been having this issue. Also, the volume control on my laptop no longer works, even after i adjust the volume with alsamixer. It still shows on the screen that the volume is being adjusted, but it does nothing. I hoped i explained this well enough for someone to be able to help me with this issue. Also, sorry if this issue has been posted before.
The sound stopped working, supposedly after upgrade and reboot (although the last upgrade was Gimp updates, as far as I remember). I rebooted the computer, then tried to play a sound and nothing came out of the speakers. The sound card (CA0106 Soundblaster) is detected, I can still adjust sound level and all the settings, but no sound is produced.
I tried running ALSA in terminal (as suggested by some comments in threads that I googled) and un-muting the speakers, but they were already un-muted.
I've also updated the Kernel to 2.6.39 just to see if this is a Kernel bug and if this might help, but it didn't. Also not a hardware problem (works in Windows).
I have experienced 4 or 5 times a sound-muting bug. Suddenly speakers stop working (usually not in in the middle of something musical but when there is no sound playing) and does not work again until I reboot the system.
My system (Ubuntu 9.10 Gnome Desktop) keeps 'forgetting' my sound settings. every day I have to go into sound preferences and select a different hardware device setting and then change it back to the right one in order for it to work. For instance my sound goes out of my onboard intel based sound via optical to my amp and so the hardware setting for this is IEC598 output + analog stereo input But everytime I boot their is no sound (and hence no light coming through the optical cable) so then I'll change it to Analog surround and the light comes out so then I can change it back to the 1st setting and it works again. Hope that makes sense, I have had this problem and also my video settings have been 'forgotten' and samba also won't work ever since about 4 days ago when the system updated, everything was working fine before that (i have run update manager since and everything is up to date)
Generally, my sound works in all applications and browsers...but every day or two, it suddenly quits and won't work again until I reboot. I am running Ubuntu 64, 8.10 and my mobo has a built-in sound card.
I am trying to configure a friend's HP laptop with OS11.2 After reading several forums and so on I figured out that sound must be configured with the option module=hp-dv5 or module=hp-m4. The laptop is a pavilion dv5, and the sound driver is hda-intel.
So far so good, all done via yast2, it restarts the sound server, can play a test sound, everything works. But then, if I restart the computer, I do not have any sound at all. Under yast the added parameters are still there, but it does not work. trying to run rcalsasound restart does not solve the problem either.
sound on laptop running linux mint 9 isadora after restarting or if computer is idle. when the computer is idle for a while the sound will stop working even though it doesn't show muted. after restarting i have to run alsamixer and the master tab will be muted. i can unmute and it will work until the computer sits idle for a while.
I am having a HARD, PARTIAL FAILURE OF SOUND on my Linux system (Slackware 13.1, the latest, with a 2.6.33.4-smp kernel and KDE 4.4.3). The failure is "HARD" in the sense that once it occurs it remains broken until I reboot the system. It's a "PARTIAL" failure in that it affects ONLY SOME sound software on my system. Here is a list of what fails and what doesn't. (I'm sure there are other programs I could use to test with, but I don't know what they are since I am "just an average user" when it comes to multimedia software.)
These don't fail:
Amarok KDE event notification
These do fail:
Firefox Xine Mplayer
In the things that fail it is only the sound portion of whatever (flash, mp4, etc) which goes away; the video portion plays normally.n I leave my system up for days at a time. The failure occurs some "long-ish" time (days) after I reboot. I have no idea what triggers it. I do not use sound most of the time, but when I do it's music through Amarok (which doesn't fail) so I do not notice the failure when it occurs.
It seems clear to me that it is NOT the failed programs which are at fault but it is, rather, some underlying set of sound libraries and/or servers used in common by all the programs which fail, and that the failure occurs when something happens which affects that set of sound libraries and/or servers. I don't think this is specifically a Slackware issue since I've seen a few other problem reports on the web where the sound simply stops on non-Slackware Linux systems. Some of the problem reports I've seen suggest that playing sound from one program stops sound from other programs. I've tried various combinations of sound-producing programs but none have triggered the problem.
I've looked at /var/log/{messages,debug,syslog} and see nothing relevant. I've gotten process lists from ps before and after the failure and no "relevant" processes have gone away. (But note, as before, that I am NOT a Linux "multimedia guy" so I can only make intelligent guess at what is "relevant".) Does anyone know what this problem is and, better still, how to solve it? Or where I could look for additional clues? Is there some way to "reset" the sound system without having to reboot?
After I installed the new Fedora 13, all went well without problems.
Unfortunately, the sound settings are not retained. That means after a reboot, I have to set this again and again.
I have an: HD 5.1 Intel OnBoard Sound Card. I run "gmix" or "kmix", the rear wheels boxes are always "mute". I put on this, but after the restart the setting are lost.
The PulseAudio settings are set to 5.1 Digital Sound.
What can I do to go the the settings are not lost?
After I listened to the audio program on the Google Chrome, I downloaded the MP3 to listen again offline. When I clicked on the downloaded MP3 file and using Totem to hear on my computer, there is no sound. I checked the sound preference, there is NO MUTE.
I restarted computer, clicked on the MP3 file with Totem, I can hear. I can hear the sound on ...... Which process should I restart without reboot computer. I'm using Ubuntu 10.10. Here is the output after execute command "sudo lshw -c sound"
I am using sda1 as /, which is a bootable drive. I do not know if my problem is that I did not create a /boot drive. After removing the iso dvd, I tried to reboot and I get this back: -bash: /sbin/reboot: input/output error Then it returns me to the terminal prompt.
I was just using the mic and watched it stop working suddenly. I was in the middle of a skype test call when the graphical mixer level died down to zero in the middle of the call. When the test call was played back, the first part sounded fine then the sound got lower until it became inaudible. Since then I can't get any sound from my mic in skype.
Also, the audio input level graphically shown in Sound Preferences shows no fluctuations in sound as it used to before. The input device is enabled. I tried using Sound Recorder to record some sound clips and that worked fine. So the mic is working but Sound Preferences and Skype seem to have the mic level really low. I'm not sure what else to think considering it was working perfectly a few minutes ago. I've tried restarting, but that didn't fix it either.
After installing an external sound card, Im having some weird issues. The cards chipset is fully supported by suse, (CM8738) so I dont think thats the problem. Besides, I'm getting sound, but not in some applications. The system's sounds work just fine (login, logout themes) amarok plays without any problems, kaffeine, mplayer they all work flawlessly, in fact I can see the difference in quality between the onboard sound and my new card. However, no web browser is able to play any sound at all, firefox, opera or chrome, nothing,zip. Plus, vlc cant reproduce sound either, nor can smplayer.
I've tried switching channels on and off(muting)in kmixer and in alsamixer, on the console, with no results. I disabled the onboard audio on the bios before installing the new card, however my ati video card has integrated sound, which I cant disable.... I used to get this exact same problem randomly with the onboard sound, but I just had to go to kmixer and turn up the "pcm" channel volume, which was set to 0, and I had sound again on my browser. However this card's pcm channel is at max and turning it up or down affects the whole systems volume, not just the browser's. Is it better to just reinstall the sound system, if so how could I do that.
I bought a Diamond Xtreme Sound 5.1 sound card because I had read online that this card was a good choice with Linux and came with universal driver software. I installed the hardware correctly (as it works with WinXP) but I'm not able to get it working with Ubuntu.
Further to this LQ thread which Tinkster solved by suggesting the last command (thanks Tinkster) I have been exploring last -x reboot and have found that the reported duration is incorrect for the last reboot and shutdown when a old wtmp file is used. Not having a record for the following shutdown, last assumes that the system has been up until the current time and similarly for the shutdown.
The output comes in time order, latest first, each line showing the time of the reboot and the uptime from then to shutdown. Using last -x reboot shutdown to show the shutdown time, here's an illustration
Code:
shutdown system down 2.6.29.6-smp Sun Mar 7 15:35 - 03:02 (11:27) reboot system boot 2.6.29.6-smp Sun Mar 7 09:35 (05:59) 09:35 until 15:35 is 05:59.
When the uptime exceeds 24 hours it is shown as (<days>+<hours:minutes) like this Code: shutdown system down 2.6.29.6-smp Sun Feb 21 12:39 - 13:20 (00:40) reboot system boot 2.6.29.6-smp Sat Feb 20 09:39 (1+02:59) 09:39 until 12:39 the next day is 1 day 02:59.
The time in parentheses at the end of the shutdown lines is normally the time until the next shutdown.
So far so good. The incorrect output is for the last reboot and shutdown of an old wtmp file. Here's the output of last /var/log/wtmp -x reboot shutdown; last -f /var/log/wtmp.1 -x reboot shutdown
Code:
[snip] reboot system boot 2.6.29.6-smp Fri Mar 12 07:42 (01:54) shutdown system down 2.6.29.6-smp Fri Mar 12 01:31 - 09:37 (08:05) wtmp begins Thu Mar 11 08:25:26 2010 [snip] reboot system boot 2.6.29.6-smp Wed Mar 10 14:12 (15+01:42) shutdown system down 2.6.29.6-smp Wed Mar 10 12:41 - 15:54 (15+03:13) [snip]
The boot started at "Wed Mar 10 14:12" which had an actual uptime of 1 day 11:20 is reported as 15 days 03:13 which is the time from then until the last -f /var/log/wtmp.1 -x reboot shutdown command was issued. The time from shutdown to shutdown is similarly affected.
I have been using Ubuntu as my main OS on my desktops for a couple of years now. Started off with a HP with a Creative Labs XiFi soundcard, but am now using a Dell with a Creative Labs Audigy. Sound worked perfectly on the Dell since a clean install (about 7 months ago). I turned it on a week or so ago, and no sound! Even the little sound indicator in the notification area has gone.
After installing I was not able to get many of the audio programmes to work. After some reading, I realised that this was probably due to jack not starting.
I was unable to get jack to start normally but have been able to get it started with the playback only option selected. Programmes that use jack now work, however there is no sound once jack has been started. The sound does work in other programs when jack is not started. Strangely, I only have to open qjackctl for the sound to stop, and jack is not even started. Initially I thought these problems were due to my sound card not being supported, but I believe that alsa support was added for the via 1708 codec at some point. I found that support had been added in a document showing the changes between alsa versions; however I cannot find the exact model listed as a supported sound card on the alsa site.
I believe that altering jack settings could fix the problem, as i have been able to get audio to work in hydrogen by selecting plughw:0 but there is still no sound in other programs. I have tried altering many other settings but to no avail, however I do not really understand the meaning of the settings that i am adjusting.
Does anyone know what settings to adjust or know something else that might fix this problem so that sound works once jack has been started?
Also, would programmes that use jack such as audacity, hydrogen, and ardour work with pulseaudio as the main sound server if I were to install normal ubuntu - it might be worth seeing if my soundcard works with the puleaudio sound server
if this helps, here is the error message received when jack does not start when the normal duplex option is selected.
21:24:04.867 Patchbay deactivated. 21:24:04.868 Statistics reset. 21:24:04.886 ALSA connection change. Cannot connect to server socket err = Connection refused
[Code].....
also, when i open alsamixer in the terminal for some reason the headphone part is greyed out, even when the sound is working before qjackctl is opened.
I've got a custom compiled kernel, just built on Lucid 10.04 from the kernel sources.System works fine, except for sound.When I log in as normal user and try to play a wav file using.The sound file is being played, but I hear no sound.However, when I do "sudo -s" and become root, execute the same mplayer command then I can hear the sound.My Sound preferences shows no input device and only "Dummy Output" as output device.On the generic kernel as came with the Lucid 10.04 CD, sound preferences shows different devices.The strange thing is: when I compiled my custom kernel, I changed nothing to the sound options in the kernel config file.
I have no sound, is it possible to restore the default sound drivers/settings in 10.04?It was work well before except for one issue, I couldn't get mic in for Rosetta Stone using wine. I have followed so many howto's to try and get Rosetta Stone working and then my sound working again.I think this is my main problem I upgraded alsa to "alsa-driver-1.0.23". I could easily be wrong about that assumption though.I have a Dell XPS M1210Ubuntu 10.04 64bitI think this is my sound card, "lspci -v | less"00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 01)Subsystem: Dell Device 01d7Flags: bus master, fast devsel, latency 0, IRQ 11 Memory at efffc000 (64-bit, non-prefetchable) [size=16K]Capabilities: <access denied> Kernel modules: snd-hda-intelBut I don't think it is being recognized,
For a couple of days ago, maybe a week or two I beguinne to get a 'snap-sound' in my compurt sound, like an eletrick charge or someting. I comes with about a minutes period. I resently find out that it came from the center-speaker. I run Ubuntu 10.04 LTS and have this sound-card: 00:09.0 Audio device: nVidia Corporation MCP73 High Definition Audio (rev a1)
My speaker system is Logitech X-530 I have located the problem to center-speaker, but the snap-sound only disappear if I mute the center, not lower the input, in the GNOME ALSA Mixer. I have tried to disconnect the antenna to the analoge-TV-tuner. Has anyoe a similar problem, and a trick to fix it? I don't know if it's related to any recent update of the system?
Playing a song works at first; then it quits after 1-5 minutes. If you select a different output device, it will work for another 1-5 minutes, but switching back to an already used up device will not play sound. Running 'sudo killall pulseaudio' resets everything and each output device works for another 1-5 minutes. This is on on 9.10.
Recently I have started using my netbook (Acer Aspire one D250) alot more due to travelling and I noticed that the mic didn't work. Headed to the Ubuntu forums and saw a thread about installing ALSA. So I did and now I have no sound. From what I can tell ubuntu is no longer picking up my sound devices but I'm sure. Hence why I am here. I need to get my sound working again (obviously) and then in turn get my mic working for mumble and other VOIP programs.
I have a fresh install of Natty and i'm having some issues getting sound to work. My laptop has a built in sound card which works just fine. However, i also have a usb 5.1 sound card which isn't working at all. Both devices show up in 'Sound Preferences' but when i select the 5.1 device as the output device sound doesnt work. I ran the alsa-info.sh script and the output can be found here.