Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum. |
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
|
08-07-2003, 11:15 PM
|
#1
|
Member
Registered: Apr 2003
Posts: 35
Rep:
|
device /dev/dsp can't be opened
every time i run the kde window system i recieve this message when it first starts up. i would like to have sound but have thusfar been running without it. i have looked everywhere on the net for solutions to this problem but none have been much assistance except for teaching me many things i did not know but did not need to know. i have slackware 8.1 installed and can provide any other information anyone needs to help me with this problem.
thanks in advance,
ryan
|
|
|
08-07-2003, 11:30 PM
|
#2
|
Senior Member
Registered: Mar 2003
Location: Earth
Distribution: Slackware, Ubuntu, Smoothwall
Posts: 1,571
Rep:
|
Take a look at this search result on '/dev/dsp' here at LQ:
http://www.linuxquestions.org/questi...der=descending
There's probably a chmod or ln solution in there.
What are the permissions for /dev/dsp on your system?
regards...
|
|
|
08-08-2003, 08:11 AM
|
#3
|
LQ Newbie
Registered: Aug 2003
Posts: 2
Rep:
|
On my system Debian Woody, I used the following to get sound to work.
Give proper permission to the file
chmod 666 /dev/dsp
Add users to the group for audio
gpasswd -a <your login name> audio
|
|
|
08-08-2003, 09:07 AM
|
#4
|
Member
Registered: Jun 2001
Location: Houston, TX, USA
Distribution: Debian
Posts: 569
Rep:
|
Quote:
Originally posted by gNY
On my system Debian Woody, I used the following to get sound to work.
Give proper permission to the file
chmod 666 /dev/dsp
Add users to the group for audio
gpasswd -a <your login name> audio
|
This is half right and half evil. Never chmod 666 /dev/dsp. Its permissions should be 660, and it should be owned by root.audio. Then, anyone in the audio group has read/write access to it.
|
|
|
08-08-2003, 09:59 AM
|
#5
|
LQ Newbie
Registered: Aug 2003
Posts: 2
Rep:
|
Good advice. I will implement this ASAP.
Thanks
George
|
|
|
08-09-2003, 01:34 AM
|
#6
|
Member
Registered: Apr 2003
Posts: 35
Original Poster
Rep:
|
alright i have now chmoded the /dev/dsp... and as with all the other tries to chmod /dev/dsp it has gained me nothing... anything else i could try
|
|
|
08-09-2003, 01:41 AM
|
#7
|
LQ Guru
Registered: Mar 2002
Location: Salt Lake City, UT - USA
Distribution: Gentoo ; LFS ; Kubuntu ; CentOS ; Raspbian
Posts: 12,613
Rep:
|
Is that right? Odd..
Can you post up the following:
ls -l /dev/dsp
lsmod
And:
lspci -v
Cool
|
|
|
08-09-2003, 01:43 AM
|
#8
|
LQ Guru
Registered: Mar 2002
Location: Salt Lake City, UT - USA
Distribution: Gentoo ; LFS ; Kubuntu ; CentOS ; Raspbian
Posts: 12,613
Rep:
|
Quote:
Originally posted by Strike
This is half right and half evil. Never chmod 666 /dev/dsp. Its permissions should be 660, and it should be owned by root.audio. Then, anyone in the audio group has read/write access to it.
|
I'm no uber security nut, but would certainly like to know of any holes I too follow this scheme, but only because "I was told to" previously. But could you expand on the need to secure your dsp device from world reading/writing? Thanks for any info
Cool
|
|
|
08-09-2003, 04:01 AM
|
#9
|
Member
Registered: Jun 2001
Location: Houston, TX, USA
Distribution: Debian
Posts: 569
Rep:
|
Quote:
Originally posted by MasterC
I'm no uber security nut, but would certainly like to know of any holes I too follow this scheme, but only because "I was told to" previously. But could you expand on the need to secure your dsp device from world reading/writing? Thanks for any info
Cool
|
Well it's not as severe a security risk as many permissions problems can be, it's more of a "prevent a source of potential annoyances" than anything else. If you chmod 666 /dev/dsp and then go for years forgetting about that and then you start handing out shell accounts to people, you may find yourself listetning to someone cat'ing /dev/urandom into /dev/dsp in the middle of the night That and it's just the perfect thing to use the unix permissions model for that it makes no sense to pass up the perfect opportunity to acquaint yourself with it.
|
|
|
08-09-2003, 04:06 AM
|
#10
|
LQ Guru
Registered: Mar 2002
Location: Salt Lake City, UT - USA
Distribution: Gentoo ; LFS ; Kubuntu ; CentOS ; Raspbian
Posts: 12,613
Rep:
|
Sounds good to me Thanks for the follow up!
Cool
|
|
|
08-09-2003, 06:16 PM
|
#11
|
Member
Registered: Apr 2003
Posts: 35
Original Poster
Rep:
|
alright...
ls -l /dev/dsp spits out the following:
crw-rw---- 1 root sys 14, 3 Jul 18 1994 /dev/dsp
lsmod spits out the following:
Module Size Used by Not tainted
soundcore 3236 0 (autoclean)
tulip_cb 31872 2
cb_enabler 2528 2 [tulip_cb]
ds 6624 4 [cb_enabler]
i82365 22416 2
pcmcia_core 40896 0 [cb_enabler ds i82365]
ide-scsi 7456 0
lspci -v spits out the following:
pcilib: Cannot open /proc/bus/pci/06/00.0
lspci: Unable to read 64 bytes of configuration space.
|
|
|
08-10-2003, 08:16 PM
|
#12
|
Member
Registered: Apr 2003
Posts: 35
Original Poster
Rep:
|
well, i posted the outputs of the 3 commands you wanted me to run... any ideas what could be wrong?
|
|
|
08-11-2003, 01:29 AM
|
#14
|
LQ Guru
Registered: Mar 2002
Location: Salt Lake City, UT - USA
Distribution: Gentoo ; LFS ; Kubuntu ; CentOS ; Raspbian
Posts: 12,613
Rep:
|
Is your user a member of group sys? If not, add them to that group and see if that fixes it (although, i don't see a sound module loaded for a soundcard, and the lspci bit is kind of confusing..).
Cool
|
|
|
08-11-2003, 08:06 AM
|
#15
|
Member
Registered: Apr 2003
Posts: 35
Original Poster
Rep:
|
my user that i am trying to do this with is root... would that have a difference?
|
|
|
All times are GMT -5. The time now is 04:15 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
|
|