57 replies to this topic

[abarbarian]

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



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

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.  

[abarbarian]

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 .

CODE

[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.

[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.

[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.

[amenditman]

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!

[amenditman]

sunrat and amenditman the trouble with altering my bios is that then I get no sound in my dual boot with Windows 7.

Why would Windows 7 not recognize your discrete sound card?
If the BIOS was set to disable the onboard sound, the drivers for the card are loaded, and your jacks are plugged into the discrete card, the OS should treat it as the only sound system available. Linux or Windows should not matter.

[V.T. Eric Layton]

Well, everyone here knows that I have three favorite things that I repeatedly (ad nauseum) lampoon... KDE 4, Gentoo, and my BIG HAMMER/BIG NUKE solutions to everyday computer problems.

Just ignore me. I'm harmless.

[amenditman]

Harmless! That's not how I'd describe you.

[V.T. Eric Layton]

Witless?

[amenditman]

That's completely the wrong direction! And harsh.

[V.T. Eric Layton]

Shameless?

[securitybreach]

The only reason I suggested Eric's method is because you have tried various things and changed configs without fixing the issue. I do not know exactly what the issue is as it should not be that hard to simply blacklist the module for the onboard audio and load the module for the card you want to use.

Basically we need to backtrack what you did in this thread to fix it in order to apply this at every boot.

[amenditman]

Shameless?

Now that's more like it.

Edited by amenditman, 15 March 2012 - 07:34 AM.

[abarbarian]

Shameless?

Something looks familiar here now what could it be hmmmmmmmmmmm

http://www.bing.com/images/search?q=shamel...8AF&first=0

Got it. Twer the cigarette  

Edited by abarbarian, 16 March 2012 - 07:30 PM.

[abarbarian]

Will get back to this after the weekend as I'm of to York for mums day lunches etc.  

[V.T. Eric Layton]

Frank Gallagher, huh? I'm sure that's a common enough Irish name, but one of my best friends was named Frank Gallagher, too. He wasn't shameless, though. He was a good-hearted fellow.

[abarbarian]

Hi back again. Yeah I know it was a long weekend but I also got Nethacked and Doom 3 interfered along with the fine spring weather.

My missing sound is caused by me not having these files shown in the message that shows as Arch starts up.

ALSA Lib conf.c:3700:(snd_conf_update_r)cannot access file /usr/share/alsa/alsa.conf
ALSA Lib control.c:951:(snd_ctl_open_noupdate)Invalid CTL hw:0
/usr/sbin/alsactl: set_controls:1485: snd_ctl_open error: no such file or directory

ALSA Lib conf.c:3700:(snd_conf_update_r)cannot access file /usr/share/alsa/alsa.conf
ALSA Lib control.c:951:(snd_ctl_open_noupdate)Invalid CTL hw:1
/usr/sbin/alsactl: set_controls:1485: snd_ctl_open error: no such file or directory

So the missing file is,

/usr/share/alsa/alsa.conf

Can someone using a Arch 64bit post their output of the above file for  me . Thanks.

[securitybreach]

Can someone using a Arch 64bit post their output of the above file for  me . Thanks.

https://raw.github.com/securitybreach/Cerbe...aster/alsa.conf

[abarbarian]

Well the file helped a lot  

We now have sound at start up and on reboot     

http://8tracks.com/brendenden/1-0-0-songs-of-greatness

Some nice mixes from the above if you like to try out new music and are lazy like me.  



However the message I get before i log in has now changed to,

/usr/sbin/alsactl: set_controls:1385: failed to obtain info for control #1
/usr/sbin/alsactl: set_controls:1385: failed to obtain info for control #2
/usr/sbin/alsactl: set_controls:1385: failed to obtain info for control #3
/usr/sbin/alsactl: set_controls:1385: failed to obtain info for control #4
/usr/sbin/alsactl: set_controls:1385: failed to obtain info for control #5

right through to # 48

/usr/sbin/alsactl: is a executable file so I can make no changes there.

So it looks like another .conf file needs a tweak.

I can get sound from FF on streaming music and you tube type sites. However no sound from SMPlayer.

Does anyone have for a 64bit Arch the following files and would they be so kind as to post the out put for me.

~/.asoundrc
/etc/asound.conf
/etc/modprobe.conf
/etc/modprobe.d/alsa.conf
/etc/modprobe.d/modprobe.conf
/etc/conf.d/alsa

Thanks.

Edited by abarbarian, 28 March 2012 - 08:58 AM.

[securitybreach]

Some of the files did not exist on my machine. Here are the ones I uploaded

~/.asoundrc
/etc/modprobe.d/modprobe.conf
/etc/conf.d/alsa

and these are the ones that did not exist:

/etc/asound.conf
/etc/modprobe.conf


Also my alsa.conf is located in /usr/share/alsa/alsa.conf and not /etc/modprobe.d/alsa.conf.

https://github.com/securitybreach/Cerberus/tree/master/audio

[V.T. Eric Layton]

[V.T. Eric Layton]

Here are my 64 bit Arch requested files:

~/.asoundrc --> no such file

/etc/asound.conf --> no such file

/etc/modprobe.conf --> no such file

/etc/modprobe.d/alsa.conf --> no such file

/etc/modprobe.d/modprobe.conf

#
# /etc/modprobe.d/modprobe.conf
#
blacklist usblp

/etc/conf.d/alsa

# Arguments for alsactl
# example: ALSA_ARGS="--file /var/lib/alsa/asound.state"
ALSA_ARGS="--file /var/lib/alsa/asound.state"

# Enables powersaving mode for AC97 and hda_intel audio chips.
# Set to 1 to enable powersaving.
# Set to 0 to disable powersaving (default).
POWERSAVE=0

# Whether to save volume levels when stopped ("yes" or "no").
SAVE_VOLUME="yes"

# Whether to mute the master volume when stopped ("yes" or "no").
# Useful for bad audio cards which make a noise on system poweroff.
MUTE_VOLUME="no"

[amenditman]

Come on, for a minor little sound issue. The orbital nuke option is a bit over the top.
I'm beginning to think you just like pushing the button.

[V.T. Eric Layton]

He's been trying to get this sound to work for a month now. I would have nuked it within the first week.

[sunrat]

Lots of info at https://wiki.archlinux.org/index.php/Advanc...nd_Architecture

I would suggest to change your ~/.asoundrc according to the example in the "In User Space" section of that page.

CODE

pcm.!default {
type hw
card 1
device 0
}
ctl.!default {
type hw
card 1
device 0 #this may cause alsamixer to crash with "cannot open mixer: Invalid argument"
}

Use aplay -l to find out the correct number for your desired card.

The alsa.conf file looks to be a default one. It seems the same as my one in aptosid.