Jump to content

No sound -- yet again ********


abarbarian

Recommended Posts

Well I have no sound yet again.

 

Jamendo has no sound.

 

You Tube opens up with SMplayer but has no sound.

 

Gogglesmm gives me a message,

 

Session bus not available.All features requiring dbus are disabled

 

then,

 

Unable to initialize audio driver

 

If I check in a terminal I get,

 

# lspci | grep -i audio
02:08.0 Multimedia audio controller: C-Media Electronics Inc CMI8788 [Oxygen HD Audio]

 

So where is my sound. !!!!

 

I'm lost any ideas folks. :angry:

 

Link to comment
Share on other sites

It's possible your system is trying to use an alternate (non-existant) audio device. Mine occasionally creates virtual copies of my sound device and sets the new one as default. I usually check alsamixer then the alsa ArchWiki page. Something to do with aplay or asound if I remember correctly.

 

From the ArchWiki ALSA page

Set the default sound card

In Kernel Space

 

Telephony-capable modems and modern graphics cards with HDMI output can conflict with the sound card for the default sound card slot. (pcspkr is another, non-ALSA PC speaker module. It will not conflict with ALSA sound cards.) To prevent this, discover your sound card model name with lspci(8) and your ALSA driver module names with ls(1):

 

$ ls -l /sys/module/snd/holders

 

Or better (source[1]):

$ cat /proc/asound/modules

 

Then add the names of your sound card modules to (source[2]):

 

/etc/modprobe.d/alsa.conf

 

Link to comment
Share on other sites

It's possible your system is trying to use an alternate (non-existant) audio device. Mine occasionally creates virtual copies of my sound device and sets the new one as default. I usually check alsamixer then the alsa ArchWiki page. Something to do with aplay or asound if I remember correctly.

 

From the ArchWiki ALSA page

 

Well I followed securitybreaches advice and got sound last week.

 

I just disabled my secondary audio using this:

 

First find the pci id with:

QUOTE

╔═ comhack@Cerberus 08:42 AM

╚═══ ~-> lspci | grep -i audio

00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06)

01:00.1 Audio device: Advanced Micro Devices [AMD] nee ATI Barts HDMI Audio [Radeon HD 6800 Series]

 

 

Find the correct folder

QUOTE

╔═ comhack@Cerberus 08:43 AM

╚═══ ~-> find /sys/devices -name *01:00.1

/sys/devices/pci0000:00/0000:00:03.0/0000:01:00.1

 

 

And add this to the /etc/rc.local

QUOTE

echo 1 > /sys/devices/pci0000\:00/0000\:00\:03.0/0000\:01\:00.1/remove

 

 

See now it does not show up:

QUOTE

╔═ comhack@Cerberus 08:55 AM

╚═══ ~-> lspci | grep -i audio

00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06)

 

╔═ comhack@Cerberus 08:55 AM

╚═══ ~->

 

 

 

NOTE: Your numbers may or may not be the same as mine.

 

and this is what I get today which is the same as last week.

 

# lspci | grep -i audio
02:08.0 Multimedia audio controller: C-Media Electronics Inc CMI8788 [Oxygen HD Audio]

 

These are the outputs from amenditman's links.

 

$ cat /proc/asound/modules
1 snd_virtuoso

 

$ ls -l /sys/module/snd/holders
total 0
lrwxrwxrwx 1 root root 0 Feb 29 23:24 snd_hda_codec -> ../../snd_hda_codec
lrwxrwxrwx 1 root root 0 Feb 29 23:24 snd_hda_codec_analog -> ../../snd_hda_codec_analog
lrwxrwxrwx 1 root root 0 Feb 29 23:24 snd_hda_codec_hdmi -> ../../snd_hda_codec_hdmi
lrwxrwxrwx 1 root root 0 Feb 29 23:24 snd_hda_intel -> ../../snd_hda_intel
lrwxrwxrwx 1 root root 0 Feb 29 23:24 snd_hwdep -> ../../snd_hwdep
lrwxrwxrwx 1 root root 0 Feb 29 23:24 snd_mpu401_uart -> ../../snd_mpu401_uart
lrwxrwxrwx 1 root root 0 Feb 29 23:24 snd_oxygen_lib -> ../../snd_oxygen_lib
lrwxrwxrwx 1 root root 0 Feb 29 23:24 snd_pcm -> ../../snd_pcm
lrwxrwxrwx 1 root root 0 Feb 29 23:24 snd_rawmidi -> ../../snd_rawmidi
lrwxrwxrwx 1 root root 0 Feb 29 23:24 snd_seq_device -> ../../snd_seq_device
lrwxrwxrwx 1 root root 0 Feb 29 23:24 snd_timer -> ../../snd_timer
lrwxrwxrwx 1 root root 0 Feb 29 23:24 snd_virtuoso -> ../../snd_virtuoso

 

I'm totaly lost on this.

 

From the Wiki

 

ALSA is included in the default Arch kernel as a set of modules, so installing it is not necessary.

 

udev will automatically probe your hardware at boot, loading the corresponding kernel module for your audio card. Therefore, your sound should already be working, but upstream sources mute all channels by default.

 

The current version of ALSA installs with all channels muted by default. You will need to unmute the channels manually.

 

It is easiest to use alsamixer ncurses UI to accomplish this (alternatively, use amixer from the commandline):

 

$ alsamixer

 

Here is what I get,

 

$ alsamixer
cannot open mixer: No such file or directory

 

# alsamixer
cannot open mixer: No such file or directory

 

# alsaconf

 

Tells me "no legacy drivers are available"

 

and yes I read,

 

Warning: Do not use alsaconf if you have a PCI or ISAPNP sound card, as the entries alsaconf adds to the modprobe.conf file might break udev's autodetection.

 

but my "modprobe.conf" is empty so I recon that shows that "alsaconf" is doing sweet zip for me.

 

This Arch install is turning into a nightmare >_< I did not have half as many problems last year when I did my first install and I knew nothing at all :rant:

Link to comment
Share on other sites

Check if you can install or have installed alsa-utils from the extra repos.

 

[amenditman@amendesk ~]$ yaourt -Ss alsa utils
extra/alsa-utils 1.0.25-1 [installed]

 

This package contains the alsamixer and some other stuff you need.

Link to comment
Share on other sites

Check if you can install or have installed alsa-utils from the extra repos.

 

[amenditman@amendesk ~]$ yaourt -Ss alsa utils
extra/alsa-utils 1.0.25-1 [installed]

 

This package contains the alsamixer and some other stuff you need.

 

Did that last week. That is how I unmuted the sound.

 

 

$ yaourt -Ss alsa utils
extra/alsa-utils 1.0.25-1 [installed]
    An alternative implementation of Linux sound support
aur/alsa-utils-transparent 1.0.25-1 (11)
    An patched version of the alsa-utils package to support transparent 
    terminals
aur/lirc-utils-oss 0.8.3-1 (Out of Date) (1)
    Linux Infrared Remote Control utils without ALSA dependence

 

 

looks like they are still installed. :thumbsup:

 

 

Link to comment
Share on other sites

Simon and Garfunkel -

 

:P

 

Read PC = Television

 

HANCOCK ON TELEVISION MAINTENANCE

 

TELEVISION REPAIR MAN:

Have you been kicking it?

HANCOCK:

Well of course I've been kicking it - how else do you think I change the channels over? One kick: B.B.C.; Nine kicks: I.T.A.. I had to change over six times last night - I've got toes like globe artichokes here. I'll be glad when my television-kicking boots come back from the menders!

 

http://www.phespirit.info/hancock/ B)

Link to comment
Share on other sites

securitybreach

Are you a member of the audio group?

╔═ comhack@Cerberus 09:24 PM

╚═══ ~-> groups

lp wheel kvm video audio optical storage power users vboxusers wireshark comhack adbusers

 

Also, did you reboot after today's kernel update?

 

Lastly, can you post the ouput of :

lsmod | grep snd

Link to comment
Share on other sites

I have several suggestions: first post the result of the command securitybreach mentioned in his above post.

-Go into the BIOS and disable the soundcard you are not using, then reboot. Check alsamixer to make sure it's unmuted and levels are up, test for sound (this works for my system with onboard chip and Audiophile 2496 PCI card)

-If no luck try, if it's not listed in the lsmod output (as root)

modprobe snd-oxygen

 

Some more info is at http://www.alsa-project.org/main/index.php...x:Module-oxygen, although some of it is dated and obsolete.

Link to comment
Share on other sites

securitybreach

 

Are you a member of the audio group? == yes

# lsmod | grep snd
snd_oxygen             16214  0 
snd_hda_codec_hdmi     24121  0 
snd_hda_codec_analog    79760  0 
snd_virtuoso           33445  3 
snd_oxygen_lib         30589  2 snd_virtuoso,snd_oxygen
snd_mpu401_uart         6011  1 snd_oxygen_lib
snd_rawmidi            19458  1 snd_mpu401_uart
snd_hda_intel          23375  0 
snd_seq_device          5300  1 snd_rawmidi
snd_hda_codec          89160  3 snd_hda_intel,snd_hda_codec_analog,snd_hda_codec_hdmi
snd_hwdep               6389  1 snd_hda_codec
snd_pcm                74780  5 snd_hda_codec,snd_hda_intel,snd_oxygen_lib,snd_hda_codec_hdmi
snd_page_alloc          7153  2 snd_pcm,snd_hda_intel
snd_timer              19544  2 snd_pcm
snd                    59214  17 snd_timer,snd_pcm,snd_hwdep,snd_hda_codec,snd_seq_device,snd_hda_intel,snd_rawmi
di,snd_mpu401_uart,snd_oxygen_lib,snd_virtuoso,snd_hda_codec_analog,snd_hda_code
c
_hdmi,snd_oxygen
soundcore               6210  1 snd
[root@longship bloodaxe]# modprobe snd-oxygen
[root@longship bloodaxe]# modinfo soundcore

 

sunrat

 

Check alsamixer == see my earlier posts I did all this originaly. == alsamixer was not playing yesterday but it is today. == naughty penguin.

 

modprobe snd-oxygen == does not seem to do anything.

 

securitybreach

 

Also, did you reboot after today's kernel update? == NO == switched on today and have sound == :oops: :bangin: :bangin: :bangin: :bangin: :bangin: :">

 

 

sunrat + securitybreach

 

I followed the link and tried

 

modinfo soundcore

 

which of course showed the module loaded in the kernel.

 

However it mentions "/etc/​modules.conf" which I have but it is empty . Is it worth my while doing,

 

Here's the example for this card. Copy and paste this to the bottom of your /etc/​modules.conf file.

 

# ALSA portion

alias char-major-116 snd

alias snd-card-0 snd-oxygen

# module options should go here

 

# OSS/Free portion

alias char-major-14 soundcore

alias sound-slot-0 snd-card-0

 

# card #1

alias sound-service-0-0 snd-mixer-oss

alias sound-service-0-1 snd-seq-oss

alias sound-service-0-3 snd-pcm-oss

alias sound-service-0-8 snd-seq-oss

alias sound-service-0-12 snd-pcm-oss

 

Or seeing as I have sound should I just keep me fingers crossed and leave things a s they are. :rolleyes:

 

Oh and of course many many thanks for the help :thumbsup:

Edited by abarbarian
Link to comment
Share on other sites

securitybreach

Whenever you do a kernel upgrade, some of the modules and other things do not load correctly until you reboot.

Link to comment
Share on other sites

Whenever you do a kernel upgrade, some of the modules and other things do not load correctly until you reboot.

 

Yup I remember that very fact came up here recently. :thumbsup:

Link to comment
Share on other sites

Yay, it's working! snd-oxygen has obviously been renamed to snd_oxygen since that alsa page was written, and it is already loaded.

Link to comment
Share on other sites

  • 2 weeks later...

Well once again I have no sound. I tried to fix it but had no sucess so I thought. What if I delete files and folders( I had lost trck of what had been altered) and uninstall some alsa stuff. Then reboot. Then reinstall the alsa stuff do a pacman -Syu and reboot. But no joy.

When I try to run alsamixer I get (see the end of the code)

 

[root@longship bloodaxe]# lsmod | grep snd
snd_oxygen             16214  0 
snd_hda_codec_hdmi     24121  4 
snd_hda_intel          23375  0 
snd_hda_codec          89160  2 snd_hda_codec_hdmi,snd_hda_intel
snd_hwdep               6389  1 snd_hda_codec
snd_virtuoso           33445  0 
snd_oxygen_lib         30589  2 snd_virtuoso,snd_oxygen
snd_mpu401_uart         6011  1 snd_oxygen_lib
snd_rawmidi            19458  1 snd_mpu401_uart
snd_seq_device          5300  1 snd_rawmidi
snd_pcm                74780  4 snd_hda_codec_hdmi,snd_oxygen_lib,snd_hda_codec,snd_hda_intel
snd_page_alloc          7153  2 snd_pcm,snd_hda_intel
snd_timer              19544  1 snd_pcm
snd                    59214  12 snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq_device,snd_rawmidi,snd_mpu401_uart,
snd_oxygen_lib,snd_virtuoso,snd_hwdep,snd_hda_codec,snd_hda_intel,snd_oxygen
soundcore               6210  1 snd
[root@longship bloodaxe]#  cat /proc/asound/modules
0 snd_virtuoso
1 snd_hda_intel
[root@longship bloodaxe]# alsamixer
ALSA lib conf.c:3700:(snd_config_update_r) Cannot access file /usr/share/alsa/alsa.conf
ALSA lib control.c:951:(snd_ctl_open_noupdate) Invalid CTL default
cannot open mixer: No such file or directory

 

Oops :">

Link to comment
Share on other sites

V.T. Eric Layton

WARNING: You have broken (or maimed) your Arch system. Please initiate Nominal Utility-grade Kinetic Energy option immediately.

 

nuke-it-from-orbit.jpg

 

:hysterical:

Link to comment
Share on other sites

What do you get when you run alsaconf as root?

 

 

I find this warning in the Alsa Wiki very puzzling,I have a ASUS Xonar DS PCI sound card.

 

Warning: Do not use alsaconf if you have a PCI or ISAPNP sound card, as the entries alsaconf adds to the modprobe.conf file might break udev's autodetection.

 

Seeing as me sound seems screwed I ran alsaconf and got this output

 

[root@longship bloodaxe]# alsaconf
bash: alsaconf: command not found

 

Running aplay -l outputs this

 

 

[root@longship bloodaxe]# aplay -l 
**** List of PLAYBACK Hardware Devices ****
ALSA lib conf.c:3700:(snd_config_update_r) Cannot access file /usr/share/alsa/alsa.conf
ALSA lib control.c:951:(snd_ctl_open_noupdate) Invalid CTL hw:0
aplay: device_list:261: control open (0): No such file or directory
ALSA lib conf.c:3700:(snd_config_update_r) Cannot access file /usr/share/alsa/alsa.conf
ALSA lib control.c:951:(snd_ctl_open_noupdate) Invalid CTL hw:1
aplay: device_list:261: control open (1): No such file or directory

 

Running "/etc/init.d/alsasound restart" or "/sbin/alsa force-reload" outputs this

 

[root@longship bloodaxe]# /etc/init.d/alsasound restart
bash: /etc/init.d/alsasound: No such file or directory

[root@longship bloodaxe]# /sbin/alsa force-reload
bash: /sbin/alsa: No such file or directory
[root@longship bloodaxe]#

 

 

:rolleyes:

Edited by abarbarian
Link to comment
Share on other sites

Running lspci -v outputs

01:00.1 Audio device: NVIDIA Corporation GF104 High Definition Audio Controller (rev a1)
        Subsystem: ASUSTeK Computer Inc. Device 835c
        Flags: bus master, fast devsel, latency 0, IRQ 16
        Memory at fbffc000 (32-bit, non-prefetchable) [size=16K]
        Capabilities: [60] Power Management version 3
        Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [78] Express Endpoint, MSI 00
        Kernel driver in use: snd_hda_intel

02:08.0 Multimedia audio controller: C-Media Electronics Inc CMI8788 [Oxygen HD Audio]
        Subsystem: ASUSTeK Computer Inc. Virtuoso 66 (Xonar DS)
        Flags: bus master, medium devsel, latency 32, IRQ 18
        I/O ports at 9c00 [size=256]
        Capabilities: [c0] Power Management version 2
        Kernel driver in use: snd_virtuoso

 

and now from # cat /proc/asound/modules I output

 

 

[root@longship bloodaxe]# cat /proc/asound/modules
0 snd_hda_intel
1 snd_virtuoso

 

So it looks like the sound cards have swapped places :">

 

 

Link to comment
Share on other sites

The Arch Wiki also says this

 

Or better (source[1]):

 

$ cat /proc/asound/modules

 

Then add the names of your sound card modules to (source[2]):

 

/etc/modprobe.d/alsa.conf

 

options snd slots=snd-intel8x0

 

These entries ensure that the Intel 82801DB-ICH4 sound card will become card 0 and the PC speaker will become card 1. If there's more cards that have to fall into specific order, their modules can be given to “slots” option as follows:

 

/etc/modprobe.d/alsa.conf

 

options snd slots=snd-intel8x0,snd-interwave

 

This way cards driven by snd-intel8x0 module are enumerated before interwave cards.

 

Trouble is I do not have "/etc/modprobe.d/alsa.conf" only thing I have in "/etc/modprobe.d/" is a empty file "modprobe.conf"

 

:rolleyes:

Link to comment
Share on other sites

securitybreach
Running "/etc/init.d/alsasound restart" or "/sbin/alsa force-reload" outputs this

 

[root@longship bloodaxe]# /etc/init.d/alsasound restart
bash: /etc/init.d/alsasound: No such file or directory

[root@longship bloodaxe]# /sbin/alsa force-reload
bash: /sbin/alsa: No such file or directory
[root@longship bloodaxe]#

 

 

:rolleyes:

I agree with Eric but the reason you are getting "No such file or directory" is because that is not how you stop|start|restart a daemon (alsa). In order to do this, you have two options:

/etc/rc.d/alsa start|stop|restart

or

rc.d stop|start|restart alsa

 

You can replace alsa with whatever daemon(service) you want to modify and use one of the three options listed. Ex:

rc.d restart alsa

 

The daemons(services) loaded at boot are listed at the bottom of /etc/rc.conf:. Ex:

╔═ comhack@Cerberus 10:48 PM 
╚═══ ~-> cat /etc/rc.conf | grep DAEMONS
# DAEMONS
DAEMONS=(hwclock syslog-ng @network @netfs crond @alsa @dbus @sensors !ntop @mpd @openntpd !vboxdrv @sshd !tor @pgl)

 

BTW the @ means to background the service so the next one does not have to wait for the previous one to finish (faster bootup). The ! is used to disable the daemon from starting at boot.

Link to comment
Share on other sites

I mentioned it before, but again I suggest to go into BIOS and disable onboard sound.

I use a Bose USB sound system.

Used to have a bunch of inconsistant sound troubles.

Went into the BIOS and disabled the onboard sound and now have much less trouble. Not none, just a lot less.

Link to comment
Share on other sites

WARNING: You have broken (or maimed) your Arch system. Please initiate Nominal Utility-grade Kinetic Energy option immediately.

 

nuke-it-from-orbit.jpg

 

Sure... go ahead and ignore me. In the end, we always resort to the nuke from orbit option.

 

:hysterical:

 

Not ignoring you mate just I am a bit busy following red herrings on the alsa quest. Besides I already know how to nuke and am interested in fixing rather than nuking. <_<

Link to comment
Share on other sites

sunrat and amenditman the trouble with altering my bios is that then I get no sound in my dual boot with Windows 7. So if I was just running Arch that would be a rather inelegant woring fix. It would not enhance my knowledge of Arch however.

 

securitybreach

 

I had added alsa to the DAEMONS when I initially installed and have since added "snd_virtuoso snd_hda_intel" to /etc/rc.conf as advised from several sources .

 

[bloodaxe@longship root]$ cat /etc/rc.conf | grep DAEMONS
# DAEMONS
DAEMONS=(syslog-ng network dbus @alsa @crond @sensors @cpufreq)
[bloodaxe@longship root]$

 

# HARDWARE

# --------

MODULES=(powernow-k8 cpufreq_ondemand cpufreq_powersave snd_virtuoso snd_hda_intel)

 

I have also done this but with no resulting sound.

 

http://www.alsa-project.org/main/index.php...Module-virtuoso

 

Make a file called .asoundrc in your home and/​or root directory:

 

vi ~/.asoundrc

 

Copy and paste the following into the file, then save it:

 

pcm.virtuoso {

type hw

card 0

}

 

ctl.virtuoso {

type hw

card 0

}

 

 

I have also created a UDEV rule at "/etc/udev/rules.d/10-local.rules"

 

SUBSYSTEM=="sound", ATTR{id}=="DS", ATTR{number}="0"

SUBSYSTEM=="sound", ATTR{id}=="NVidia", ATTR{number}="1"

 

from information gathered at

 

http://www.reactivated.net/writing_udev_rules.html#syntax

 

https://bbs.archlinux.org/viewtopic.php?id=136258

 

So I'll have a reboot and see if it works.

 

B)

Link to comment
Share on other sites

securitybreach

I thought you were trying to keep the snd_hda_intel card from being loaded? If you are, you need to blacklist the module instead of having it autoload via the MODULES lines in /etc/rc.conf.

Link to comment
Share on other sites

V.T. Eric Layton
Not ignoring you mate just I am a bit busy following red herrings on the alsa quest. Besides I already know how to nuke and am interested in fixing rather than nuking. <_>

 

Fixing is good for learning experience. Nuking is GOOD for efficient use of the time allotted to you in this short life. ;)

 

Link to comment
Share on other sites

Not ignoring you mate just I am a bit busy following red herrings on the alsa quest. Besides I already know how to nuke and am interested in fixing rather than nuking. <_<

Fixing is a lot more fun! :thumbsup:

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...