[ale] sound driver problems

[Brian Pitts]

On 06/28/2009 08:35 AM, Sean wrote:
> I am trying (and losing what little hair I have left) to get FC11 up and 
> running. Among other minor snafus is "drag and drop."  It doesn't seem to work 
> at all in KDE.  I have backup files stored on a USB hard drive and I can't drag 
> them over to the new home directory in KDE.  I have to boot a gnome session to 
> do that. WTF?
> But my problem tonight is sound.  What follows is a portion of 
> /var/log/messages following the last reboot.
>
> Jun 28 08:23:36 Sarge kernel: ALSA sound/pci/hda/hda_intel.c:1101: Too big 
> adjustment 32: adj=128, bytes=128, size=4096, periods=32
> Jun 28 08:23:36 Sarge pulseaudio[3953]: alsa-source.c: Your kernel driver is 
> broken: it reports a volume range from 18.00 dB to 18.00 dB which makes no 
> sense.
> Jun 28 08:23:36 Sarge dbus: Rejected send message, 2 matched rules; 
> type="method_call", sender=":1.84" (uid=42 pid=3953 comm="/usr/bin/pulseaudio 
> --start --log-target=syslog ") interface="org.bluez.Manager" 
> member="ListAdapters" error name="(unset)" requested_reply=0 
> destination="org.bluez" (uid=0 pid=1906 comm="/usr/sbin/bluetoothd "))
>
> Jun 28 08:23:36 Sarge pulseaudio[3953]: bluetooth-util.c: Error from 
> ListAdapters reply: org.freedesktop.DBus.Error.AccessDenied
> Jun 28 08:23:45 Sarge pulseaudio[2432]: reserve-wrap.c: Failed to acquire 
> reservation lock on device 'Audio0': Input/output error
>
> Jun 28 08:23:45 Sarge pulseaudio[2432]: reserve-wrap.c: Failed to acquire 
> reservation lock on device 'Audio1': Input/output error
>
> Jun 28 08:24:07 Sarge pulseaudio[4286]: pid.c: Daemon already running.
>
> Jun 28 08:24:09 Sarge pulseaudio[2432]: reserve-wrap.c: Failed to acquire 
> reservation lock on device 'Audio0': Input/output error
>
>
> If, indeed the Alsa kernel driver is broken, how do I fix that?  I do get 
> sounds -- I can play an .ogg file without problem.  
>
> I have no clue as to what the actual problem might be or how to fix it.
>
> Hints, clues, and advice would be appreciated.
>   

I see an open report in fedora's bugzilla about the "too big adjustment"
error.

I'd ignore the message about the driver being broken. Some sound
hardware doesn't report information about what the hardware slider
actually mean in decibels. This is particularly a problem for USB and
bluetooth devices.

The rest of the messages looks like problems with communications
problems among pulseaudio components. I'm wondering the following: Do
you see any messages about "Running in system mode"? How did you install
KDE and GNOME? Do you have multiple sessions logged in at once? Have you
changed any pulseaudio configuration? Is selinux in enforcing mode?

-- 
All the best,
Brian Pitts