Creative labs SB Live! Sound not working

dai · 08-11-2002, 11:35 AM

Hi when I login and start KDE 3.0 Everything loads fine except I get a message stating something like cannot open /"whatever"/dsp

And I have absolutley no sound

Ive modprobed emu10k1 >OK loads fine

Done a Cat /proc/pci >OK

any ideas why this wont work?????

dai · 08-11-2002, 11:54 AM

Everythings Ok now Ive sorted the problem

cheers

zLinuxz · 08-12-2002, 05:29 AM

klasikahl · 08-12-2002, 03:27 PM

great that u fixed the problem, but it would be even better if u posted how u fixed it and what was wrong. my audigy works fine, but if someone out there has the same problem as u did, they are gonna look at this and say "well, how do i fix it?!"

zack

bLaX · 08-12-2002, 04:45 PM

Yeah, can ya let me know how you fixed that? I have a similar problem. I just installed Slackware, and my SB Live card is not working. I've tried this "chmod 777 /dev/dsp" as root and user, still doesn't work. Weirdest thing is this has never been a prblem with different distro's such as rh 73, suse or mandy, only Slackware doesn't work. Anyone experienced this as well? And if it was resolved, please share.

klasikahl · 08-12-2002, 04:53 PM

the first thing i would suggest is, in the console, type "adduser bLaX audio" (or whatever ur username is)

bLaX · 08-12-2002, 05:34 PM

I tried that klasikahl, and it didn't work out for me. That's so odd, it works by default on other distros, but on slack, I gotta like configure every piece of hw. I actually like to learn this way, so if anyone can lend me a hand to get my SB Live card to work, much props to ya!

klasikahl · 08-12-2002, 05:38 PM

bLaX you are going to get the best support on the irc.openprojects.net IRC network, under the #slackware channel.

dai · 08-13-2002, 02:15 AM

Hey all

I fixed the problem by modprobing emu10k1 as root

I them restarted the pc and it worked

however the problem has now resurfaced and I am having probs getting sound to work now

when I run lsmod I get a list of loaded modules that contains ac97 emu10k1 nvidia(graphics) and some other modules that seem related to emu10k1

The next step I will try is adding emu10k1 to my /etc/modules.conf

however Im not sure how to add it if anybody could advise Id be more than grateful i.e. not sure how to write the alias line if anyone has this card (SB Live!) could you post your modules.conf please

Also would it be better if I added the module to /etc/rc.d/rc.modules

MasterC · 08-13-2002, 04:16 AM

Well, here's mine:

Code:

alias     sound-slot-0    emu10k1
alias                     usb-storage

But I have been told, and have been able to simply add emu10k1 and that's it. No other syntax necessary.

Yes, you should uncomment the /sbin/modprobe emu10k1 in /etc/rc.d/rc.modules

Cool

dai · 08-13-2002, 05:12 AM

cheers MasterC

one other Question

Is this the file you use In Slack 8.1 or Suse 8.0 (or are they both the same)

Just curious

hanzerik · 08-13-2002, 07:53 AM

In slackware your going to have to edit /etc/rc.d/rc.modules and uncomment the line for /sbin/modprobe/emu10k1 . Then your are either going to have to add a new user/group called something like sndusr or something, then chown the devices (dsp, mixer, audio) so that the user/group you created has the correct permissions to access these devices(by default only root has access) Then add your existing normal user to that sndusr group.

Or you can do it the easy unsecure way:
chmod a+rw /dev/dsp
chmod a+rw /dev/mixer
chmod a+rw /dev/sound

dai · 08-13-2002, 08:15 AM

Many thanks

I checked /etc/modules.conf out yesterday and it was empty bar one thing

So I wasnt sure if there was another file I needed to edit.

wouldn't

chmod 600 (whatever path)

have the same effect as

chmod a r+w

hanzerik · 08-13-2002, 10:58 AM

No, chmod u+rw would be = to 600
u = user
g = group
o = other
a = all users

Here are some examples:
chmod o-rw <file> takes away read write from others
chmod go-rw <file> takes away read write from the group and others

Now if you want to give permission change the - to a +

chmod a+rwx gives everyone read/write/exec
chmod a-x takes away exec but keeps read/write

But it maybe easier to use the 4,2,1
4 = read
2 = write
1 = exec
0 = nothing
chmod 644 <file> gives owner rwx and group r and others r
chmod 755 <file> would be used for say a program that you want others to run but not edit. rwx-rx-rx
chmod 760 sets it to exec for user, read write for group, and no access for others.
clear it up for you a little?

dai · 08-13-2002, 11:45 AM

sorry didnt realise that the -a switch affected the application of the chmod in such a way.

I rather using the , 4, 2, 1 method its a lot easier.