Results 1 to 7 of 7
I just installed Slack 10.2 on an Intel 865PERL with onboard sound. It is no longer seen. It worked great with 10.1. Any ideas? Thanks...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 12-10-2005 #1Just Joined!
- Join Date
- Apr 2005
- Location
- North Carolina
- Posts
- 5
(no) Sound
I just installed Slack 10.2 on an Intel 865PERL with onboard sound. It is no longer seen. It worked great with 10.1. Any ideas? Thanks
- 12-10-2005 #2
have you ran
Code:alsaconf
Brilliant Mediocrity - Making Failure Look Good
- 12-11-2005 #3
and turned up everything with
Code:alsamixer
- 12-11-2005 #4Linux Enthusiast
- Join Date
- Jun 2005
- Posts
- 668
and stored the settings as root with
Code:alsactl store
- 12-11-2005 #5Just Joined!
- Join Date
- Apr 2005
- Location
- North Carolina
- Posts
- 5
Still no Sound
Thanks for all the help! alsaconf says nothing found
Another thing I have notice is that K3B and my other recording software dont see my HP cdr anymore.....It's correctly listed as I boot up (?) I'm helping my daughter move today, so I'll be back this evening. If my back still works when I get home, I'll come back to the desk and see what suggestions you guys have. Thanks!
- 12-12-2005 #6Banned
- Join Date
- Nov 2004
- Location
- Belgium
- Posts
- 1,120
Hi, do you still remember what sound driver Alsa was using for it in 10.1?
PS: With onboard stuff, Alsa can have problems to find your needed driver.
If you know the one it needs, this is easy to fix.
PS PS: For the cdrecord thingy, could you check if it works as root.
- 12-15-2005 #7Just Joined!
- Join Date
- Mar 2005
- Posts
- 1
Alsa sound not working after 10.2 updates from Dec 14, 2005
Alsa sound would not work after making the updates of Dec 14, 2005
Followed the directions given below from
http://www.alsa-project.org/alsa-doc...module=Generic
--------------------------------------------------------------------------------------
Make a file called .asoundrc in your home and/or root directory.
vi /home/xxx/.asoundrc
copy and paste the following into the file then save it.
pcm.!default {
type hw
card 0
}
ctl.!default {
type hw
card 0
}
The keyword default is defined in the ALSA lib api and will always access hw:0,0 - the default device on the default soundcard. Specifying the !default name supercedes the one defined in the ALSA lib api.
Now you can test:
aplay -D default test.wav
--------------------------------------------------------------------------------------
Also run
alsaconf
alsamixer (and set volumes and unset mutes)
alsactl store


Reply With Quote
