LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Slackware "lost" /dev/dsp, no sound (https://www.linuxquestions.org/questions/slackware-14/slackware-lost-dev-dsp-no-sound-163727/)

Pathian 03-29-2004 09:02 AM

Slackware "lost" /dev/dsp, no sound
 
yesterday I used swaret to update my system from slackware 9.1 to slackware-current. Everything was working fine yesterday (my sound system needed to be changed from auto detect to OSS however, ALSA and Autodetect failed to open my sound card /dev/dsp). Last night though, my system locked while running a screen saver and I had to do a hard reboot. When I got back to slackware I got a different error when I used startx to boot KDE. This time, the sound server could not start because /dev/dsp (or rather the device linked to /dev/dsp) does not exist. I tried cat /dev/dsp to confirm it and it does say that the device does not exist, so none of the options for sound server work (OSS, threaded OSS, ALSA, etc). This has always been my default sound device and it was working fine yesterday. I have an Intel i810 laptop motherboard with an AC97 integrated sound card. Does anyone know what I can do to rememdy this problem? I may end up having to do a fresh install if I can't get it working again.

KMcD 03-29-2004 09:23 AM

did you upgrade the 'arts' package? I had a similar problem and that was the cause.

Try

swaret --upgrade arts

Pathian 03-29-2004 09:31 AM

yes, I've already upgraded the arts package, all of my packages are already synched with slackware-current. I get the feeling that this doesn't have something to do with Arts/KDE though, I booted into Gnome, XFce, etc etc and got similar errors, the sound card not being connected to the appropriate dev entry.

Pathian 03-29-2004 11:47 AM

well, I managed to figure out a workaround to the problem, apparently slackware didn't like that I upgraded the 4 alsa packages (or possibly just one of them) from version 0.9.6 which was packaged with the disks to the current 1.0.3, I downgraded the packages and my sound server works again, no idea why.

George666 03-29-2004 11:52 AM

chmod a+rw /dev/dsp

(you might need to do it with /dev/mixer to)

To set the permissions so that everybody can access it.

When you upgraded the devs packages the permissions probably got reset to their default values.

Minderbinder 03-29-2004 12:11 PM

Did you upgrade the kernel with swaret? I think you have to if you want to update your alsa packages with swaret. You have to remove "kernel" from the exclude list in swaret.conf.

diensthunds 03-30-2004 12:16 PM

If you do an upgrade with swaret make sure you double check your REPOS_ROOT I added the list of repos that you find on the swaret.org site and have since come to find out that alot of the packages that you may get have a 1rob or jto listed someplace in the name, problem is that those files are "custom tailored" and they may cause problems with your standard install. They require specific libraries that are 1rob or .jto libraries, and if you dont have them then your packages may not work like you would think, I'm having a probelm with my alsa not working and I think this may be why. I did a swaret --upgrade and had the sites listed in my REPOS_ROOT and I remember those "special files" being listed and installed. I'm about to whipe my system clean and re-do an --update to see if this fixes the probelm. If it does then I'll know that this was the reason why my alsa wasnt working even though I had installed the packages installed they didnt have the right libraries. Anyways if this IS the problem I'll let ya know.

Pathian 03-30-2004 05:16 PM

no, I haven't updated my kernel via swaret, I'm reticent to do so because the last time I tried to update my kernel in Slackware the system wouldn't boot up. Thanks for all the help though.

mrcheeks 03-30-2004 05:52 PM

compile the kernel and add support for the appropriate sound card.(kernel.org)


All times are GMT -5. The time now is 11:00 PM.