Only noise after upgrading to 2.6.27-9

Being reading on pulseaudio, found these commands bellow (hope it helps):

> grep pulseaudio /var/log/messages
Nov 27 22:46:50 lemobile-pc pulseaudio[6387]: ltdl-bind-now.c: Failed to find original dlopen loader.
Nov 27 22:46:50 lemobile-pc pulseaudio[6389]: main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted
Nov 27 22:46:50 lemobile-pc pulseaudio[6389]: main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not permitted
Nov 28 09:12:01 lemobile-pc pulseaudio[6389]: protocol-native.c: Failed to push data into queue
Nov 28 11:26:19 lemobile-pc pulseaudio[6280]: ltdl-bind-now.c: Failed to find original dlopen loader.
Nov 28 11:26:19 lemobile-pc pulseaudio[6282]: main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted
Nov 28 11:26:19 lemobile-pc pulseaudio[6282]: main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not permitted
Nov 28 16:08:03 lemobile-pc pulseaudio[6282]: alsa-util.c: Device hw:1 doesn't support 44100 Hz, changed to 16000 Hz.
Nov 28 16:08:03 lemobile-pc pulseaudio[6282]: alsa-util.c: Device hw:1 doesn't support 2 channels, changed to 1.
Nov 28 16:30:25 lemobile-pc pulseaudio[6383]: ltdl-bind-now.c: Failed to find original dlopen loader.
Nov 28 16:30:25 lemobile-pc pulseaudio[6385]: main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted
Nov 28 16:30:25 lemobile-pc pulseaudio[6385]: main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not permitted
Nov 28 16:53:32 lemobile-pc pulseaudio[7041]: ltdl-bind-now.c: Failed to find original dlopen loader.
Nov 28 16:53:32 lemobile-pc pulseaudio[7043]: main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted
Nov 28 16:53:32 lemobile-pc pulseaudio[7043]: main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not permitted

> pulseaudio -vvv
I: main.c: PolicyKit refuses acquire-high-priority privilige.
I: main.c: Called SUID root and real-time/high-priority scheduling was requested in the configuration. However, we lack the necessary priviliges:
I: main.c: We are not in group 'pulse-rt' and PolicyKit refuse to grant us priviliges. Dropping SUID again.
I: main.c: For enabling real-time scheduling please acquire the appropriate PolicyKit priviliges, or become a member of 'pulse-rt', or increase the RLIMIT_NICE/RLIMIT_RTPRIO resource limits for this user.
I: main.c: Note that real-time/high-priority scheduling is NOT normally required. If you experience crackling or other sound anomalies, consider one or more of the above solutions.
I: main.c: High-priority scheduling enabled in configuration but now allowed by policy. Disabling forcibly.
W: ltdl-bind-now.c: Failed to find original dlopen loader.
E: pid.c: Daemon already running.
E: main.c: pa_pid_file_create() failed.

Thanks

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.
Please include the information requested from the "Reporting Sound Bugs" section of https://wiki.ubuntu.com/DebuggingSoundProblems as separate attachments.

Ok, here it goes...
(Tested, recommended actions on the DebuggingSoundProblems page: Permissions are OK, Tested with other sound servers SAME ERROR for all Excpet OSS **, Please note that I do get sound But it is noise)

OSS: Appears IS working.

Do you need anything else?
Please help, using OSS is a pain. I have tested it some more and OSS works fine, alsa produces noises just the same as pulse.
Could the problem be with ALSA, in the card driver ?

I am listening, ask and I shall do.
Thanks

Are you certain that this symptom isn't caused by an ALSA mixer element control being muted and/or zeroed, e.g., 'PCM'?

You can verify by inspecting the output of `amixer -Dhw:0' in a Terminal while this noise is reproducible.

We are closing this bug report because it lacks the information we need to investigate the problem, 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". Thanks again!