If anyone is still having issues after following this guide, as I was, may I suggest following this one, it worked for me:
http://ubuntuforums.org/showthread.php?t=1046137
If anyone is still having issues after following this guide, as I was, may I suggest following this one, it worked for me:
http://ubuntuforums.org/showthread.php?t=1046137
I just wanted to say thanks followed part A & my sound now works on both the card and usb.
(Juanty 9.04)
also have to remove tons of stuff, like ubuntu-desktop. I'll tery and get the hardy deb packages and install them, to see if that solves my problem
Research Paper Writing
I'm on Jaunty x86_64
I have pulseaudio working perfectly, so i gave a try to the global equalizer part of the guide. After finishing, i logged out then logged in, and the standard welcoming sound sure enough sounds with the eq values i had chosen, however, thats the only sound i ever hear. After that, any other attempts to play back sound doesn't produce anything.
If i attempt to play back any sound, Pulseaudio Manager shows the client, but there is no sound.
i5-2500, Asus p8p67le, 8g ddr3, gtx460. Eeepc 701 4g surf.
vm.swappiness=0;noatime,data=writeback;deadline scheduler;preload.
The instruction (first page) states this does not work in Jaunty, maybe need to line that out since anyone running Jaunty should probably stop there...
It might be nice to include a big bold notice at the top stating this is an Edit-A-Text-File solution, which if it works is fine, but very disappointing to discover this later on.
Really? KDE seems to depend on PulseAudio. I cannot remove it without a list of dependencies that include a vast amount of kde packages - including kate.Note 4: Kubuntu users: Don't follow this guide - PulseAudio isn't used in your distribution
I am so sick of trying to fix bloody pulse audio crap - is there a linux distribution that does not use pulse?
Stuck on step 5 of part A Keep getting Connection failed: Connection refused Ubuntu 9.04 Jaunty
Last edited by Crimson Kaze; September 28th, 2009 at 08:10 AM.
Just in case anyone else has this issue:
No gnome app seemed to play sound, specifically rhythmbox, sound-juicer, totem, and the nautilus mouse-over sound preview, they all were mute.
They all acted like they were playing (even had the little music note icon appear in nautilus) but no sound (and DID NOT appear in the pulseaudio applet->Volume Control->playback window)
Kaffeine, mplayer, xine, they worked fine.
(and DID appear in the pulseaudio applet->Volume Control->playback window)
Running sound-juicer or totem in a terminal window with the option "--gst-debug=3" revealed that the alsa libs were complaining that the sound device was busy. (if you do this redirect the debug output to a file cause it's a firehose, e.g. "totem --gst-debug=3 >totem.log 2>&1")
Solution: goto System->Preferences->Sound->Devices and change everything from autodetect to pulseaudio (despite what Part A, point 4 says) and now it all works!
Using Jaunty on a Gigabyte MA78GPM
Thank you for using the Albert Gore jr. Information Superhighway. Please post responsibly. Happy Cerf-ing!
Running 8.10 on a Dell Latitude D610 laptop, Intel drivers. At some point the alsa module stopped initializing. I'm having some trouble making sense of the logs. Is it failing because of the 'Operation not permitted' problems early in the logs? This used to work earlier in the summer.
my script contains...
Code:pactl load-module module-alsa-sink device=Headset; sleep 2 pactl load-module module-alsa-source device=Headset; sleep 2
Code:Oct 3 16:17:01 laptop /USR/SBIN/CRON[15369]: (root) CMD ( cd / && run-parts --report /etc/cron.ho urly) Oct 3 16:18:06 laptop kernel: [ 8404.031297] Intel ICH 0000:00:1e.2: PCI INT A disabled Oct 3 16:18:06 laptop kernel: [ 8404.720305] Intel ICH 0000:00:1e.2: PCI INT A -> GSI 16 (level, lo w) -> IRQ 16 Oct 3 16:18:06 laptop kernel: [ 8404.720337] Intel ICH 0000:00:1e.2: setting latency timer to 64 Oct 3 16:18:07 laptop kernel: [ 8405.548045] intel8x0_measure_ac97_clock: measured 55206 usecs Oct 3 16:18:07 laptop kernel: [ 8405.548059] intel8x0: clocking to 48000 Oct 3 16:18:18 laptop pulseaudio[15797]: main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted Oct 3 16:18:18 laptop pulseaudio[15797]: main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not permitted Oct 3 16:18:19 laptop pulseaudio[15797]: alsa-util.c: Error opening PCM device hw:0: Device or reso urce busy Oct 3 16:18:19 laptop pulseaudio[15797]: module.c: Failed to load module "module-alsa-sink" (argum ent: "device_id=0 sink_name=alsa_output.pci_8086_266e_sound_card_0_alsa_playback_0"): initialization failed. Oct 3 16:18:19 laptop pulseaudio[15797]: sap.c: sendmsg() failed: Operation not permitted Oct 3 16:18:19 laptop pulseaudio[15797]: rtp.c: sendmsg() failed: Operation not permitted Oct 3 16:18:20 laptop last message repeated 90 times Oct 3 16:18:24 laptop pulseaudio[15797]: sap.c: sendmsg() failed: Operation not permitted Oct 3 16:18:34 laptop last message repeated 2 times Oct 3 16:18:34 laptop pulseaudio[15797]: alsa-util.c: Error opening PCM device Headset: Unknown err or 240 Oct 3 16:18:34 laptop pulseaudio[15797]: module.c: Failed to load module "module-alsa-sink" (argum ent: "device=Headset"): initialization failed. Oct 3 16:18:36 laptop pulseaudio[15797]: alsa-util.c: Error opening PCM device Headset: Unknown err or 240 Oct 3 16:18:36 laptop pulseaudio[15797]: module.c: Failed to load module "module-alsa-source" (arg ument: "device=Headset"): initialization failed. Oct 3 16:18:39 laptop pulseaudio[15797]: sap.c: sendmsg() failed: Operation not permitted
Last edited by RgnKjnVA; October 3rd, 2009 at 09:46 PM.
So tired of repeatedly fixing sound issues in Ubuntu/Mint/Pulseaudio. *sigh*
Bookmarks