Hmmm...
Executed this command:

  $> pkill pulseaudio; sleep 2; pulseaudio -vvv 2>&1 | tee pulse1.log

and then:

  $> grep controlC0 pulse1.log
  D: module-udev-detect.c: /dev/snd/controlC0 is accessible: no

It looks like the controlC0 is not in the /dev/snd but in /dev:

  $> find /dev -name controlC0
  /dev/controlC0

Could this be the issue?!

Regards,
Petru


On Sun, Nov 1, 2009 at 10:29 PM, Petru Marginean
<[email protected]>wrote:

> Hi,
>
> Tried again to use module-detect instead module-udev-detect.
> Changed the /etc/pulse/default.pa and then executed:
>
>       $> pkill pulseaudio; sleep 2; pulseaudio -vvv 2>&1 | tee pulse2.log
>
> but again no sound.
>
> I've attached the logfile, and some interesting lines are below.
>
> Thanks for help,
> Petru
>
> $> grep detect pulse2.log
> W: module.c: module-detect is deprecated: Please use module-udev-detect
> instead of module-detect!
> I: module-detect.c: loaded 1 modules.
> I: module.c: Loaded "module-detect" (index: #5; argument: "").
> I: module.c: Unloading "module-detect" (index: #5).
> I: module.c: Unloaded "module-detect" (index: #5).
>
> $> grep -i error detect pulse2.log
> grep: detect: No such file or directory
> pulse2.log:I: alsa-util.c: Error opening PCM device front:0: Invalid
> argument
> pulse2.log:I: alsa-util.c: Error opening PCM device hw:0: No such file or
> directory
> pulse2.log:I: alsa-util.c: Error opening PCM device surround40:0: Invalid
> argument
> pulse2.log:I: alsa-util.c: Error opening PCM device surround41:0: Invalid
> argument
> pulse2.log:I: alsa-util.c: Error opening PCM device surround50:0: Invalid
> argument
> pulse2.log:I: alsa-util.c: Error opening PCM device surround51:0: Invalid
> argument
> pulse2.log:I: alsa-util.c: Error opening PCM device surround71:0: Invalid
> argument
> pulse2.log:I: alsa-util.c: Error opening PCM device iec958:0: Invalid
> argument
> pulse2.log:I: alsa-util.c: Error opening PCM device iec958:0: Invalid
> argument
> pulse2.log:I: alsa-util.c: Error opening PCM device a52:0: No such file or
> directory
> pulse2.log:I: alsa-util.c: Error opening PCM device a52:0: No such file or
> directory
> pulse2.log:I: alsa-util.c: Error opening PCM device hdmi:0: Invalid
> argument
> pulse2.log:I: alsa-util.c: Error opening PCM device hw:0: No such file or
> directory
> pulse2.log:I: alsa-util.c: Error opening PCM device hw:0: No such file or
> directory
> pulse2.log:I: alsa-util.c: Error opening PCM device front:0: Invalid
> argument
> pulse2.log:I: alsa-util.c: Error opening PCM device hw:0: No such file or
> directory
> pulse2.log:I: alsa-util.c: Error opening PCM device surround40:0: Invalid
> argument
> pulse2.log:I: alsa-util.c: Error opening PCM device surround41:0: Invalid
> argument
> pulse2.log:I: alsa-util.c: Error opening PCM device surround50:0: Invalid
> argument
> pulse2.log:I: alsa-util.c: Error opening PCM device surround51:0: Invalid
> argument
> pulse2.log:I: alsa-util.c: Error opening PCM device surround71:0: Invalid
> argument
> pulse2.log:I: alsa-util.c: Error opening PCM device iec958:0: Invalid
> argument
> pulse2.log:I: alsa-util.c: Error opening PCM device iec958:0: Invalid
> argument
> pulse2.log:I: alsa-util.c: Error opening PCM device a52:0: No such file or
> directory
> pulse2.log:I: alsa-util.c: Error opening PCM device a52:0: No such file or
> directory
> pulse2.log:I: alsa-util.c: Error opening PCM device hdmi:0: Invalid
> argument
> pulse2.log:I: alsa-util.c: Error opening PCM device hw:0: No such file or
> directory
> pulse2.log:I: alsa-util.c: Error opening PCM device hw:0: No such file or
> directory
>
>
>
>
>
> On Sat, Oct 31, 2009 at 10:44 PM, Petru Marginean <
> [email protected]> wrote:
>
>> Thanks for suggestion.
>> I commented out "load-module module-udev-detect" command (see below), and
>> then rebooted.
>> However I have seen no improvement:
>>
>>     $> aplay -l
>>
>>     aplay: device_list:223: no soundcards found...
>>
>> After reboot I've also got a report about a compiz crash (see the attached
>> picture) so I guess I'm going to rollback this change.
>> :-(
>>
>> Regards,
>> Petru
>>
>> $> diff /etc/pulse/default.pa.orig /etc/pulse/default.pa
>> 53,55c53,55
>> < .ifexists module-udev-detect.so
>> < load-module module-udev-detect
>> < .else
>> ---
>> > #.ifexists module-udev-detect.so
>> > #load-module module-udev-detect
>> > #.else
>> 59c59
>> < .endif
>> ---
>> > #.endif
>>
>>
>>
>>
>> On Sat, Oct 31, 2009 at 10:53 PM, Daniel T Chen <[email protected]>wrote:
>>
>>> Then use module-detect instead of module-udev-detect. See /etc/pulse/
>>> default.pa.
>>>
>>> On Oct 31, 2009 10:50 PM, "petrum" <[email protected]> wrote:
>>>
>>> ...and I can confirm that the sound is working with the new 2.6.31
>>> kernel.
>>> Is there any way to make it work with my old kernel (2.6.28)?
>>> (since otherwise I cannot use the computer - see some issues I have
>>> below)
>>>
>>> Thanks,
>>> Petru
>>>
>>> On Sat, Oct 31, 2009 at 10:19 PM, Petru Marginean
>>> <[email protected]> wrote: > Hi, > > Th...
>>> --
>>> Petri
>>>
>>> -- no sound after upgrating to KK 9.10
>>> https://bugs.launchpad.net/bugs/467747 You received this bu...
>>>
>>> --
>>> no sound after upgrating to KK 9.10
>>> https://bugs.launchpad.net/bugs/467747
>>> You received this bug notification because you are a direct subscriber
>>> of the bug.
>>>
>>> Status in “alsa-driver” package in Ubuntu: New
>>>
>>> Bug description:
>>> Hi,
>>>
>>> I used to have sound, but after upgrading to the new Karmic Koala it
>>> doesn't work any more.
>>> I googled it, and tried a few commands. The following shows something is
>>> wrong:
>>> Code:
>>>
>>> $> sudo aplay -l
>>> aplay: device_list:223: no soundcards found...
>>>
>>> Unfortunately I do not know how to fix it, or how to investigate further.
>>> Any suggestions?
>>>
>>> I've also included below some other commands that could help find the
>>> issue.
>>>
>>> Many thanks,
>>> Petru
>>>
>>> Code:
>>>
>>> $> lsb_release -a && uname -r
>>> No LSB modules are available.
>>> Distributor ID:    Ubuntu
>>> Description:    Ubuntu 9.10
>>> Release:    9.10
>>> Codename:    karmic
>>> 2.6.28-16-generic
>>>
>>> Code:
>>>
>>> $> dmesg | egrep -i "sound|audio|snd"
>>> //nothing
>>>
>>> Code:
>>>
>>> $> cat /proc/asound/cards
>>>  0 [Intel          ]: HDA-Intel - HDA Intel
>>>                      HDA Intel at 0xfdff4000 irq 22
>>>
>>> Code:
>>>
>>> $> lspci | grep -i audio
>>> 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio
>>> Controller (rev 02)
>>>
>>> Code:
>>>
>>> $> lsmod | grep snd
>>> snd_hda_intel         435252  0
>>> snd_pcm_oss            46336  0
>>> snd_mixer_oss          22656  1 snd_pcm_oss
>>> snd_pcm                83076  2 snd_hda_intel,snd_pcm_oss
>>> snd_seq_dummy          10756  0
>>> snd_seq_oss            37760  0
>>> snd_seq_midi           14336  0
>>> snd_rawmidi            29696  1 snd_seq_midi
>>> snd_seq_midi_event     15104  2 snd_seq_oss,snd_seq_midi
>>> snd_seq                56880  6
>>> snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
>>> snd_timer              29704  2 snd_pcm,snd_seq
>>> snd_seq_device         14988  5
>>> snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
>>> snd                    62756  9
>>> snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,
>>> snd_seq_oss,snd_rawmidi,
>>> snd_seq,snd_timer,snd_seq_device
>>> soundcore              15200  1 snd
>>> snd_page_alloc         16904  2 snd_hda_intel,snd_pcm
>>>
>>> Code:
>>>
>>> $> sudo /etc/init.d/alsa-utils restart
>>>  * Shutting down ALSA...
>>>  * warning: 'alsactl store' failed with error message 'alsactl:
>>> save_state:1502:
>>> No soundcards found...'...
>>> Invalid card number.
>>> Usage: amixer <options> [command]
>>> Available options:
>>>  -h,--help       this help
>>> //...
>>>
>>> ProblemType: Bug
>>> AlsaDevices:
>>>  total 0
>>>  drwxr-xr-x 2 root root 60 2009-10-31 21:11 by-path
>>> AplayDevices: aplay: device_list:223: no soundcards found...
>>> Architecture: i386
>>> ArecordDevices: arecord: device_list:223: no soundcards found...
>>> AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp',
>>> '/dev/snd/by-path', '/dev/sequencer2', '/dev/sequencer', '/dev/seq'] failed
>>> with exit code 1:
>>> CheckboxCommand: alsa_record_playback
>>> CheckboxDescription:
>>>  Open the volume control application by right-clicking on the speaker
>>> icon in the panel and selecting "Sound Preferences".  Select the "Input" tab
>>> and choose any alternate (non-default) device(s).  Select the "Output" tab
>>> and choose any alternate (non-default) device(s).  When you are done, click
>>> the Test button, then speak into the microphone. After a few seconds, your
>>> speech will be played back to you.
>>>
>>>  Did you hear your speech played back?
>>> CheckboxTest: alsa_record_playback_alternates
>>> Date: Sat Oct 31 21:14:34 2009
>>> DistroRelease: Ubuntu 9.10
>>> NonfreeKernelModules: nvidia
>>> Package: alsa-base 1.0.20+dfsg-1ubuntu5
>>> PackageArchitecture: all
>>> ProcEnviron:
>>>  SHELL=/usr/bin/zsh
>>>  PATH=(custom, user)
>>>  LANG=en_US.UTF-8
>>> ProcVersionSignature: Ubuntu 2.6.28-16.55-generic
>>> SourcePackage: alsa-driver
>>> Tags: checkbox-bug
>>> Uname: Linux 2.6.28-16-generic i686
>>> UserAsoundrc:
>>>  # ALSA library configuration file
>>>
>>>  # Include settings that are under the control of asoundconf(1).
>>>  # (To disable these settings, comment out this line.)
>>>  </home/petrum/.asoundrc.asoundconf>
>>> XsessionErrors:
>>>  (gnome-settings-daemon:3144): GLib-CRITICAL **: g_propagate_error:
>>> assertion `src != NULL' failed
>>>  (polkit-gnome-authentication-agent-1:3291): GLib-CRITICAL **:
>>> g_once_init_leave: assertion `initialization_value != 0' failed
>>>  (nautilus:3288): Eel-CRITICAL **: eel_preferences_get_boolean: assertion
>>> `preferences_is_initialized ()' failed
>>>  (gnome-panel:3237): Gtk-WARNING **: gtk_widget_size_allocate(): attempt
>>> to allocate widget with width -15 and height 24
>>>
>>
>>
>>
>> --
>> Petri
>>
>
>
>
> --
> Petri
>


-- 
Petri

-- 
no sound after upgrating to KK 9.10
https://bugs.launchpad.net/bugs/467747
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to