See the fix I stated in the previous reply. Have you used some alsa update scripts that could have purged packages ? taco143October 2nd, 2011, 10:26 PMOK now try ls -la /usr/bin/alsamixerto check if alsamixer is executable. If anyone can help, I can put up more info if requested. weblink
After booting with the new kernel, "alsactl restore" tries to feed this asound.state to the (new 'n' improved) driver and the driver gags because the mixer descriptions have changed. /etc/init.d/alsa-utils already I seem to remember, that it can be helpful to delete them. Logged ASUS EeePc 900HA netbook 1.6 Ghz Atom CPU 2 GB RAM160 GB internal HD Seagate 250 GB USB portable drive Intel Mobile 945GSE Integrated Graphics ControllerAtheros AR242x/AR542x Wireless Network AdapterIntel Juerd (ubuntu-juerd) wrote on 2005-09-19: #2 Output from amixer Edit (4.1 KiB, text/plain) Created an attachment (id=3900) Output from amixer Juerd (ubuntu-juerd) wrote on 2005-09-19: #3 Attached as requested.
All rights reserved. I once did it. uname -r I will do my best here... It runs, but then something else undoes its changes –Serg Oct 8 at 11:43 any ideas what that could be? –Brad Horn Oct 8 at 11:44 @BradHorn
X-ray confirms Iam spineless! aplay -L produced the following results:default:CARD=Generic_1 HD-Audio Generic, ALC892 Analog Default Audio Devicesysdefault:CARD=Generic_1 HD-Audio Generic, ALC892 Analog Default Audio DeviceStill, no sound. This is how it worked on 14.04. Your audio device is not being claimed by the right driver.
matt_symesOctober 3rd, 2011, 12:42 PMHi It's not an issue with one of the config files is it ? Should I allow my child to make an alternate meal if they do not like anything served at mealtime? What system is this ? this You will be missed.
Toggles turn back, but no sound returns. sound alsa share|improve this question asked Jul 14 '15 at 11:02 senthor 214 Apparently, your user (or whoever rc.local is executed as) has no root privileges. –CL. mona is not in the sudoers file. And it will not until you do that actions above to fix it.
Controls 31 and 32 have values of ¨false¨.QuoteThis *might* be useful ..... Neither seems to make any difference to my setup. COMMANDS store saves the current driver state for the selected soundcard to the configuration file. ls -l /sys/module/snd/holders total 0 lrwxrwxrwx 1 root root 0 2010-03-10 14:50 snd_hda_codec -> ../../snd_hda_codec lrwxrwxrwx 1 root root 0 2010-03-10 14:50 snd_hda_codec_realtek -> ../../snd_hda_codec_realtek lrwxrwxrwx 1 root root 0 2010-03-10
Offline #5 2010-03-10 16:08:15 Ashbringer Member Registered: 2010-03-10 Posts: 4 Re: [Solved] Problem with ALSA after fresh install It's there [HDA NVIDIA ALC1200 ANALOG] but when I press "Test" I get http://culturahq.com/cannot-open/cannot-open-oe.html It did work for me in earlier kernels (2.6.10, from hoary). Juerd (ubuntu-juerd) wrote on 2005-09-20: #8 All correct. On both Fedora and ArchLinux the default is '/etc/asound.state'. -- FA _______________________________________________ Linux-audio-user mailing list [hidden email] http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user Jonathan E.
Then when Breezy was installed, after you rebooted into 2.6.12, this mixer element was unmuted, correct? If I receive written permission to use content from a paper without citing, is it plagiarism? FILES /var/lib/alsa/asound.state (or whatever file you specify with the -f flag) is used to store current settings for your soundcards. http://culturahq.com/cannot-open/cannot-open-an-anonymous-level-security-token-window-open.html matt_symesOctober 9th, 2011, 08:13 AMHi *-multimedia description: Audio device product: MCP61 High Definition Audio vendor: nVidia Corporation physical id: 5 bus info: [email protected]:00:05.0 version: a2 width: 32 bits clock: 66MHz capabilities:
Additional info: * package version(s) alsa-utils 1.0.23-2 Steps to reproduce: After first install of alsa-utils run: /etc/rc.d/alsa start This task depends upon Closed byTobias Powalowski (tpowa) Monday, 21 February 2011, 18:04 Let's get even more info. But I have the alsa installed as well.
everything that needs to be written by programs ends up in /var. -- James Cameron http://quozl.linux.org.au/_______________________________________________ Linux-audio-user mailing list [hidden email] http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user garry Ogle Reply | Threaded Open this post in Brickman wrote: > > What system is this ? Safe to close? Thank so much!
Edit bug mail Other bug subscribers Subscribe someone else Bug attachments Output from amixer (edit) Add attachment Remote bug watches ubuntu-bugzilla #15585 Edit Bug watches keep track of this bug in J.E.B. _______________________________________________ Linux-audio-user mailing list [hidden email] http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user James Cameron Reply | Threaded Open this post in threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ Re: What sudo aplay -l and the current kernel you are running. this content X-ray confirms Iam spineless!
When I then run alsamixer, the reference is to card ¨HD-Audio Generic¨ and chip ¨ATI R6xx HDMI¨ and alsamixer says ¨This sound device does not have any controls.¨PCC->Hardware->Soundcard shows the Hudson Brickman-2 Reply | Threaded Open this post in threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ What is asound.state ? Member Posts: 32 Re: How to Set ALSA Default Device? « Reply #3 on: January 26, 2013, 10:50:53 AM » Thank you for the suggestions.QuoteSee if /etc/asound.state makes any sense to AlsaMixer shows Headphones muted Unmuting makes sound play through speakers Plugging in headphones mutes speaker, sound plays through headphones Unplugging headphones mutes Headphones no sound plays through speakers Immediately after boot
On shutting down the mixer state is stored in /var/lib/alsa/asound.state.