Re: No sound, no /proc/asound/

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> Did you issue alsamixer as the command or the full pathname? If the former,
> maybe something is wrong with your path/environment setup.
I used it as both. Nothing works :/

> I am wondering if your OS install hasn't actually loaded the modules
> correctly for your hardware.
Everything worked before. I tried to make my mic work and sound
stopped to work. Now nothing works :P

> Try the command 'lsmod' to list the modules that are loaded. If the list is
> too long use 'lsmod | grep snd' to just list the ones that have 'snd' in
> their names.
$ lsmod | grep snd
snd_page_alloc          7120  0

But I don't know what that means :P

> You can then use modinfo <module name> to check details of each module.
> Or modprobe (with care!) to alter what is loaded.
Ok, and what modules should I check?

> Do you have another sound system like Pulse active? if so, that may be
> interfering with the direct use of ALSA.
Stopping pulse and reinstalling ALSA didn't work. :(

> You might also consider trying to install the latest version of ALSA in
> case what you have isn't suitable for your hardware or is furtled in some
> way.
I think I have the latest version.

> Sorry I can't be more help. But I hope the above may be useful.
Thanks for help :)

> Most times when I get something like that it has to do with the
> /dev/'s not being present.  Could be that udev isn't running on your
> box.  Or isn't configured for alsa.  It could also be something else
> like snd-pcm-oss not auto loading.  And it's friends, snd-mixer-oss
> snd-seq-oss.  Basically cannot open means some sort of missing
> something or bad permissions.  Is the user in the audio group?  Do the
> /dev/audio* and /dev/dsp* stuff exist?  In the old days we'd run
> ./snddevices from the alsa-driver source tree.  But that's probably
> not the solution of choice these days.

/dev/audio* doesn't exist, as well as /dev/dsp*
Should I do something about that??

> # /etc/init.d/alsa-utils restart
bash: /etc/init.d/alsa-utils: No such file or directory

> # /etc/init.d/udev restart
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service udev restart
Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the restart(8) utility, e.g. restart udev
restart: Rejected send message, 1 matched rules; type="method_call",
sender=":1.45" (uid=1000 pid=9806 comm="restart)
interface="com.ubuntu.Upstart0_6.Job" member="Restart" error
name="(unset)" requested_reply=0 destination="com.ubuntu.Upstart"
(uid=0 pid=1 comm="/sbin/init"))

> # groups <user>
mszynisz : mszynisz adm dialout fax cdrom floppy tape audio dip video
plugdev fuse netdev lpadmin admin sambashare

> # grep -i "audio" /etc/group
audio:x:29:pulse,mszynisz

> lsmod, dmesg, and all of the other stuff that's probably covered by
> that alsa-info.sh script thing.
My output of alsa-info.sh script is attached.

Please help, I really need my sound :(

Best,
mszynisz

Attachment: alsa-info.txt.eogY0qG3gB
Description: Binary data

------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Alsa-user mailing list
Alsa-user@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/alsa-user

[Index of Archives]     [ALSA Devel]     [Linux Audio Users]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]

  Powered by Linux