Slackware This Forum is for the discussion of Slackware Linux.
|
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
|
12-30-2012, 10:41 AM
|
#1
|
|
Member
Registered: Feb 2010
Distribution: Slackware
Posts: 83
Rep: 
|
alsactl error with kernel 3.7.1 on Slackware-current
Noticed the following startup error after updating my slackware-current test partition to 3.7.1
Code:
alsactl: set_control:1464: Cannot write control '3:3:0:Playback Channel Map:0' : File descriptor in bad state
The sound works until I run a couple of games under wine, then it starts to crackle at first, then disappears by the time I launch another game. Problem goes away when I reboot with 3.6.11 or 3.2.29
Anyone else running 3.7.1 and having the same error? |
|
|
|
|
12-30-2012, 01:31 PM
|
#2
|
|
Member
Registered: Apr 2009
Location: Canada
Distribution: Slackware
Posts: 234
Rep:
|
Quote:
Originally Posted by dr.s
Noticed the following startup error after updating my slackware-current test partition to 3.7.1
Code:
alsactl: set_control:1464: Cannot write control '3:3:0:Playback Channel Map:0' : File descriptor in bad state
The sound works until I run a couple of games under wine, then it starts to crackle at first, then disappears by the time I launch another game. Problem goes away when I reboot with 3.6.11 or 3.2.29
Anyone else running 3.7.1 and having the same error? |
Same error here. I haven't found any solution yet. |
|
|
|
|
12-30-2012, 01:59 PM
|
#3
|
|
Member
Registered: Dec 2005
Distribution: Slackware
Posts: 410
Rep:
|
Try moving /etc/asound.state somewhere else (so it's not in /etc) and see if that corrects it. Most likely it's a kernel bug of some kind.
|
|
|
|
|
12-30-2012, 04:48 PM
|
#4
|
|
Member
Registered: Mar 2007
Distribution: Slackware
Posts: 259
Rep:
|
Running alsactl store will likely fix the issue.
|
|
|
1 members found this post helpful.
|
|
12-30-2012, 05:37 PM
|
#5
|
|
Member
Registered: Apr 2009
Location: Canada
Distribution: Slackware
Posts: 234
Rep:
|
Quote:
Originally Posted by XGizzmo
Running alsactl store will likely fix the issue.
|
Nope. Still there. |
|
|
|
|
01-01-2013, 11:38 PM
|
#6
|
|
Member
Registered: Sep 2004
Location: formerly Fanelia and Zaibach
Distribution: Slackware-current with KDE 4.8.5
Posts: 296
Rep:
|
alsactl store fixes it for a short time
Hi fellow Slackers.
I get the same annoying error. Tried to fix it deleting /var/lib/asound.state and regenerating it with alsactl store. It works... but when I do alsactl restore (as does rc.alsa every boot), it gives me the error again.
Code:
alsactl: set_control:1464: Cannot write control '3:3:0:Playback Channel Map:0' : File descriptor in bad state
alsactl: set_control:1464: Cannot write control '3:3:0:Playback Channel Map:0' : File descriptor in bad state
alsactl: set_control:1464: Cannot write control '3:7:0:Playback Channel Map:0' : File descriptor in bad state
alsactl: set_control:1464: Cannot write control '3:8:0:Playback Channel Map:0' : File descriptor in bad state
alsactl: set_control:1464: Cannot write control '3:9:0:Playback Channel Map:0' : File descriptor in bad state
|
|
|
|
|
01-02-2013, 04:02 AM
|
#7
|
|
Member
Registered: Jan 2008
Posts: 64
Rep:
|
"alsactl store" needs root privileges.
|
|
|
|
|
01-02-2013, 02:48 PM
|
#8
|
|
Member
Registered: Apr 2009
Location: Canada
Distribution: Slackware
Posts: 234
Rep:
|
Quote:
Originally Posted by bormant
"alsactl store" needs root privileges.
|
How is that related to the question of the OP? |
|
|
|
|
01-03-2013, 08:48 AM
|
#9
|
|
Member
Registered: Jan 2008
Posts: 64
Rep:
|
Quote:
Originally Posted by escaflown
How is that related to the question of the OP?
|
If after upgrading kernel you run 'alsactl store' as user it cannot replace old /var/lib/alsa/asound.state and 'alsactl restore' will complain after reboot. |
|
|
|
|
01-03-2013, 09:10 AM
|
#10
|
|
Member
Registered: Apr 2009
Location: Canada
Distribution: Slackware
Posts: 234
Rep:
|
Quote:
Originally Posted by bormant
If after upgrading kernel you run 'alsactl store' as user it cannot replace old /var/lib/alsa/asound.state and 'alsactl restore' will complain after reboot.
|
If you ran it as user, that's not the kind of error you will get... |
|
|
|
|
01-03-2013, 11:51 AM
|
#11
|
|
Member
Registered: Jan 2008
Posts: 64
Rep:
|
Quote:
Originally Posted by escaflown
If you ran it as user, that's not the kind of error you will get...
|
If you get errors after upgrading kernel, then run 'alsactl store' as user instead of root, you still continue getting the same errors from 'alsactl restore' on reboots. |
|
|
|
|
01-03-2013, 01:05 PM
|
#12
|
|
Member
Registered: Apr 2009
Location: Canada
Distribution: Slackware
Posts: 234
Rep:
|
Quote:
Originally Posted by bormant
If you get errors after upgrading kernel, then run 'alsactl store' as user instead of root, you still continue getting the same errors from 'alsactl restore' on reboots.
|
How are you able to run 'alsactl store' as user instead of root ??????? |
|
|
|
|
01-03-2013, 06:36 PM
|
#13
|
|
Member
Registered: May 2008
Distribution: Slackware64, Arch
Posts: 88
Rep:
|
Quote:
Originally Posted by XGizzmo
Running alsactl store will likely fix the issue.
|
I always run alsamixer before alsactl store, just throwing it out there. |
|
|
|
|
01-05-2013, 03:10 PM
|
#14
|
|
Member
Registered: Jan 2008
Posts: 64
Rep:
|
Quote:
Originally Posted by escaflown
How are you able to run 'alsactl store' as user instead of root ???????
|
Nothing special:
Code:
$ /usr/sbin/alsactl store
/usr/sbin/alsactl: save_state:1608: Cannot open /var/lib/alsa/asound.state for writing: Permission denied
Even if user type
Code:
$ alsactl store
-bash: alsactl: command not found
result is the same. In both cases /var/lib/alsa/asound.state stays unchanged and 'alsactl restore' still complains after reboot. |
|
|
|
|
01-05-2013, 04:47 PM
|
#15
|
|
Member
Registered: Apr 2009
Location: Canada
Distribution: Slackware
Posts: 234
Rep:
|
Quote:
Originally Posted by bormant
Nothing special:
Code:
$ /usr/sbin/alsactl store
/usr/sbin/alsactl: save_state:1608: Cannot open /var/lib/alsa/asound.state for writing: Permission denied
Even if user type
Code:
$ alsactl store
-bash: alsactl: command not found
result is the same. In both cases /var/lib/alsa/asound.state stays unchanged and 'alsactl restore' still complains after reboot. |
That's incorrect. In one case (simple user case), the alsactl didn't even execute, while in the other it failed to write the asound.state. The point is there is no way you can run alsactl without root privileges in Slackware, AFAIK. |
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 06:40 PM.
|
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
|
 Latest Threads
LQ News
|
|
