Ubuntu Multimedia :: No Sound After Karmic To Lucid Upgrade / Get That?
Jun 21, 2010
The title pretty much says it all, the sound on this system was working fine until I ran the upgrade to Lucid. I've tried everything in the standard troubleshooting guide, the sticky threads and plenty of forum searches but so far I've come up with nada. For some reason Ubuntu refuses to see my soundcard, no matter how much I twist and tweak it. It's an Asus M3A78 motherboard with an on-board Realtek ALC1200 chip (snd-hda-intel). Here's most of the relevant output, hopefully someone can easily spot what's going on because I'm getting snow-blind staring at the monitor. code...
Last Monday I upgraded the Ubuntu from Karmic Koala to Lucid Lynx in my laptop (HP Compaq volna 515), and I have no sound. Searching in linux forums for an answers, I've got that (as far as I understand) there's no unique solution for this problem.
This is my lspci code...
Also, I tried to clean up the pulse audio .. What is funny for me is that pulse audio and alsa, and the audio players seems to work normally (no error of device not found or something like that).. except that there's no sound out from the speakers.
Any suggestion to discover if the problem is drivers, kernel, packages, or hardware failure? more important, how do I get the sound back?
After i upgraded to karmic i experienced that the sound of spotify was at times strange. When i started a new song there was some strange plucking sounds, can most be understood as the sound a old LP-player makes when there is dust on the record. Not much but more than enough that I can hear it and wish it wasn't there. After some time of playing the songs sometimes was totally distorted by "disturbance" and it became impossible to even hear that there was a song there. Like when you are out of reception of a radio channel.
I did some research and upgraded to the wine1.2 with "custom" pulsaudio drivers. Then the total distortion was gone, but the, always present, plocking sound still was there. I have tested adjusting PCM volume, have some volume on mono, upgrading to newer pulsaudio drivers. The same problem is when ever my dear computer i producing sound. Spotify,firefox, rythmbox and mplayer. I can't see any answers after spending some time on google. I hoped i could fix this without deleting and removing pulsaudio.
I used to listen music and watch films with my with my laptop but, after an upgrade (to 10.04 lucid) it is impossible to hear any sounds. The sound card is detected and it works since making the laptop boot from live CD (of ubuntu 10.10) I get sounds without problems. I tried to reinstall alsa-base and alsa-utils with no results. Everything looks OK, but the sound! (It's not muted!)
So i upgraded to 10.04 a few months ago, right after it was released. clean install. it worked perfectly out of the box, or so it seemed. I had had sound problems in 9.10 that i didn't experience after i upgraded... until i tried to use some headphones a few days ago. when i connected the headphones, the speakers wouldn't mute. i thought it was no big deal. i had the same issue in 9.10 and it was fixed after i upgraded alsa. i figured i'd try the same thing. I used the same alsa upgrade script i used last time [URL] and it fixed the jack sensing and the sound worked perfectly... for about 5 minutes. after a short while of playing audio, sound would stop playing. i'd stop getting sound from video files, audio files, and even from my browser. i'd have to reboot to get sound again... only to lose it again in about 10 minutes. Now it's regressed to the point where i have no sound even after i reboot.
weird thing is, when i test out an audio file with aplay, it works... even if i just get garbage sound from some mp3 files.
anyway, i've got an HP dv7 and this is my aplay -l output
Code: sleepee@sleepee-laptop:~$ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1
I can't get sound to work and am not sure how to trouble shoot. The sound DOES work when first booting, and I can make it play a test beep with the sound config app. But I cannot get sound from any other application. One possibly relevant fact is that I see a lot of I/O errors early in the boot process, but they flash by quickly so I cannot quote them.
Upgraded via Update Manager from 9.10 sound-previously-working-just-fine-system. Now, for example, running any audio-producing app (Rythmbox is a good example but its the same for anything including out of a VirtualBox XP install or with MythBuntu): The main volume control functions, but goes from muted to full volume in just 4 steps; raising it higher has no effect. It gets stranger: in Alsamixer or gnome-alsa-mixer I can see that lowering the desktop volume control to mute causes Master, PCM, Front, Surround, Center, LFE, and Side all to go to zero. Raising the desktop control one step causes all of these but Front to go to 100% instantly. Increasing the desktop control by a few more steps causes Front to step to 100%, after which no further volume increase is perceived. It's as if each step in the desktop volume equals some 25% of the Front setting, and 100% of the others. The audio setting in System, Preferences, Sound, Hardware is "Analog Stereo Output."
If I click 'Mute' on Master in the mixer then all the speakers mute, but unmuting Master does not unmute anything else. Only after I move and release the mouse-down state from the master volume do the other channels unmute. The volume control in Rythmbox, on the other hand, works seemingly correctly (maybe its going thru Pulseaudio?) And as an aside, why are there no controls for Pulse if it sits on top of ALSA?
I'm really confused by this, as all of it work as "expected" while running 9.10. Here is some output from this system (an ASUS M4A78T-E):
I upgraded to Lucid from Karmic.Im now using gnome but would like to get back to KDE. Sadly it seems that even with kdm and plasma-desktop packages installed, I run into a problem at login.If I choose from the downwards facing arrow on the botttom left of the screen, and pick "KDE".Then when I log in, it shows the first icon (a hard disk), goes black and plunks me back on the login screen.This is a Karmic>Lucid upgrade process and I wonder if something got borked in the process.
I'm currently upgrading my laptop, and it has completed the step "Getting new packages", and is now onto "Installing the upgrades".It says it is going to take another 2.5 hours, but I am leaving work soon and want to take the laptop with me. Is it safe to disconnect it from the internet at this point? I don't want to fudge up the install, but I don't want to have to leave my laptop at work all weekend (or have to come back and pick it up at some point).
I can't upgrade from Karmic to Lucid,If I try to use the update manager I get a message that says "Can't download release notes. Check your Internet connection". I've tried changing the repository and I get the same message, but I can log in to the Internet, and download and install any program from the repository. I also get regular updates for Karmic so the repository is fine.I tried the command line
~$ sudo apt-get dist-upgrade Leyendo lista de paquetes... Hecho Creando �rbol de dependencias
I searched through a lot of threads on whether its safe to upgrade from a working Karmic install to Lucid via the upgrade manager. I found a few threads from around 1 month ago where some said it worked, others said they had problems with grub etc.
Does anyone know the current status of this? I would like to upgrade to Lucid but I don't know if its safe. Would it be better to use an install CD instead of the upgrade manager? Do I need to manually install grub rather than let the install program do it? (I think the upgrade manager doesn't give an option it just installs grub after the upgrade)
I made the mistake of trying to upgrade my Karmic (server) installation to Lucid earlier today, after which I've been unable to boot into my server. The server is on OVH, so I can't watch it boot, but I am able to access all of the data from the filesystems via rescue mode. I ran fsck and that came back clean. I also ran the boot info script, the results of which are below.
I know my best bet is to backup what I can and do a fresh install, but I won't be able to back everything up so trying to get this working would certainly be more convenient. I'm sure I'm leaving out useful information, so let me know and I'll post it.
Code: Boot Info Script 0.55 dated February 15th, 2010 Boot Info Summary: => Lilo is installed in the MBR of /dev/sda sda1: File system: ext3
1st post @ LQ. Ubuntu user since 2007ish. Lots of PC experience... now vexed by upgrade from 9.10 Karmic to 10.04LTS Lucid.
The problem: random freezes whenever I boot into Lucid as user through usual Grub menu. The freeze sequence is: 1- screen stops, 2- mouse pointer freeze w/ no effect on click but moves freely and keyboard is useless, 3- screen blacks out for about 30 seconds and then returns but is unusable and 4- constant HDD activity for about 5-10 seconds. I have waited several minutes for a recovery of some sort but no dice. I reboot via on/off or reset button. Ubu deletes 2 inodes and then I'm off and running again.
If I boot through the recovery console there are no problems at all. The recovery console sequence: 1- select recovery from Grub menu, 2- at recovery menu select drop to root command prompt, 3- give root password, 4- enter 'gdm' at console prompt, finish boot up in my only user desktop (not root.)
I have not been able to find any log files that show an error message, but I'm not so tech oriented that I would necessarily know one if I saw one. Through many hours of browsing posts describing Lucid problems @ UbuntuForums (one of which has over 1,000 responses) I have found my '.xsession-errors' file (attached) is full of data.code...
using update manager, i allowed my karmic desktop at work to begin the upgrade process to lucid on friday afternoon... i ran out of time, and headed home for the weekend. somewhere along the process, the screen locked. after arriving back at work this morning, i cannot unlock the screen, or even switch users. other threads in this forum seem to indicate that i should've aborted the upgrade, but... i didn't know enough to anticipate problems, and i guess i assumed that given the lengthy estimate to complete the upgrade, i could just pickup the process again on monday.
in any case, cycling the power didn't help, so i downloaded the iso, and have booted to the 10.04 'trial'. i was hoping somebody could help guide me through resetting a password on the on-disk os from the live cd... i'm ok with reinstalling if i can preserve my account's configs & prefs.
I just upgraded a Ubuntu Desktop 64bit system from Karmic (9.10) to Lucid (10.04). There were several PostgreSQL 8.3 clusters running on that machine. After the upgrade, postgresql was not able to run anymore.
The package postgresql-8.3 was marked "rc" in dpkg -l I was not able to re-install PostgreSQL 8.3 because of a mismatched dependency. There was no warning. I guess i should have read the release notes, which i didn't. There should have been a warning before it was too late to turn back and upgrade postgresql to 8.4 first. I don't see how this is supposed to work, ever.
I'd like to know if this would be considered a bug, if it is known already and how to correctly file this bug correctly if appropriate (ubuntu-bug ?)
I have an HP Mini 210 and I recently performed an Upgrade from 9.10 to 10.04 and noticed that the netbook is much more noisy now (and can get very warm). I am not sure wether is the fan or the hard drive spinning. I did a "top" but no process was high consuming. I also thought that maybe compiz could be responsable for it, so I disabled all the visual effects, but still no change.
After a Kubuntu upgrade from Karmic to Lucid on a 32 bit i686 my samba script in /etc/init.d/ was gone. Is that simply a bug or something going wrong during the upgrade, in which case I restore the script from backup, or is there a new way to start/stop/restart... samba in Lucid? Samba is working just fine after the upgrade BTW, both for print and file sharing over a mixed network.
The sound is an onboard Realtek AC97 chip on my motherboard. It worked absolutely fine on my 9.04 Jaunty setup. My machine is dual boot with Windows XP and the sound is fine on XP, so it's not a hardware issue. Karmic seems to think there is no audio device present at all, which is obviously not the case.This is an AMD 64-bit machine running the x64 edition, although I doubt that has anything to with the problem. Everthing else in the installation went perfectly and the GNOME desktop seems significantly quicker too.
Just upgraded to Karmic using the update manger. After the update, sound is no longer working. When I go to system>preferences>sounds and go to the Hardware tab it says there are no devices to configure.
If I try to open Cinelerra from the GUI, it does nothing. If I try from the terminal I get this:
Code: cinelerra: error while loading shared libraries: libfaad.so.0: cannot open shared object file: No such file or directory I've been looking around all over the place and can't find a way past this. I really want to get it going again, can anyone help?
I've checked in synaptic and I have libfaad2 2.7-4
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.
Once again, after upgrade - NO SOUND. Read all the various forum attempts at getting sound working. Tried them. Still doesn't work. Has been an ongoing problem after each release. Pulseausdio has been removed but still seems to be there somehow, as in, when running alsamixer, the following is output:
alsamixer ALSA lib pulse.c:229pulse_connect) PulseAudio: Unable to connect: Connection refused cannot open mixer: Connection refused
or, aplay -l, produces:
aplay: device_list:223: no soundcards found...
so, I guess that's the problem. But how do you get it to recognise the card? The only thing that has been done since upgrading was to remove pulseaudio which wasn't part of the prior install in anycase but somehow injected itself during the upgrade.
I upgraded successfully last night from Hardy Heron to Lucid Lynx, but have no sound now. After searching around I can see that this is a fairly common problem. But none of the proposed solutions that work for other people have yet worked for me.
If I type 'alsamixer' at the command line, everything looks fine. There are no 'MM's indicating something being muted. I tried removing and reinstalling alsamixer and pulseaudio with no success. Edited lines 45 and 46 of /etc/pulse/default.pa with no luck.
I upgraded to Lucid a week or two ago. Sound has worked fine, then suddenly, yesterday, I have no sound for any application. The Gnome sound applet shows the volume normally, and have the Mute All option greyed out (not selectable). Nothing stands out as wrong or unusual under sound preferences, and I didn't change anything, although I did recently install a set of updates. There is no physical mute button on this laptop. IT is not account-specific, there are no sound effects even before you log in.
As well, since the upgrade I have intermittently not had the networking icon in the notification area appear, it is covered over by a fragment of some other graphic. It is most usable with the Human these, it is completely unusable with any of the new themes. Anyone know a fix for either of these two issues, especially the first?
Finding Lucid extremely flaky, particularly the signature themes. I like some aspects of it, such as the fact the wireless button on my laptop works now, but overall, not an impressive effort - someone whose first introduction to Ubuntu is Lucid and sees that the notification area doesn't even work correctly is not likely to stick around.
From time to time, system booted with no sound and I had to restart system to have it on again. Now I have no sound all the time and no idea where lies the problem. I would like to ask for help in making a diagnose of what could be the cause that there is no sound in my system.There is no error message while booting system. No explicit sound driver. Sound isn't muted. Sound works when using Ubuntu Live.
I've been using windows xp (I play chess in the chessbase server) and Ubuntu in dual boot for quite a long time with no problems. My onboard sound worked perfectly in both OS. Then I decide to buy a SB Audigy PCI sound card. It works great in Ubuntu, but there was no sounds in windows. After doing a lot of research, I read that a clean install could solve the problem. I reinstalled windows xp and the sound drivers of the sound card and alas! the sound card worked.
Then I restored grub to access Ubuntu and when I reboot to windows...I got no sounds again. So, my conclusion is that in some way the Ubuntu installation affects the sound card when working in windows. I may return this sound card. The sound card is: Creative Labs SB0570L4 Sound Blaster Audigy SE Sound Card I'm running windows xp 64 bit and ubuntu 9.10 64 bit.