snddevices issues after Current upgrade...

DreameR-X · 07-17-2005, 04:32 AM

I just got home from a long vacation and decided to update my slackware. Of course, I went from everything running smoothly to desasters. Although, the only one I've noticed so far is the sound. Alsamixer wasn't working, so I tried upgrading the ALSA Drivers as well: no go. Then I read somewhere that I needed a /dev/snd directory (that didn't exist), so I downloaded the source tarball, extracted the alsa source to a directory, and ran sh snddevices. Everything works splendidly until I reboot, and then the directory seems to erase itself so that I have to reissue the sh snddevices command again at each startup. I decided to add this to modprobe.conf (the sh command), but that's definitely not the right way to go. Any suggestions? Thanks ahead!

Cheers,
Galen

P.S. Using AC 97 intel sound card.

gbonvehi · 07-17-2005, 05:35 AM

From: ftp://ftp.slackware.com/pub/slackwar.../ChangeLog.txt

Quote:

a/udev-062-i486-1.tgz: Upgraded to udev-062.
This seems to be broken with regard to ALSA devices... I'd suggest
anyone using a 2.6 kernel "chmod 644 /etc/rc.d/rc.udev" unless you want
to help locate and report bugs. It's also possible that this has
something to do with the ever-changing syntax used in the udev.rules
config file. If you find any problems that can be attributed to that,
fixes would be appreciated. For now, rc.udev will be off by default.

DreameR-X · 07-17-2005, 05:44 AM

doh! Thanks a bunch! I guess it was just another case of RTFM.

Cheers,
Galen

MMYoung · 07-17-2005, 07:46 AM

Quote:

Originally posted by DreameR-X
doh! Thanks a bunch! I guess it was just another case of RTFM.

Cheers,
Galen

A better alternative to chmod 644 /etc/rc.d/rc.udev (because you loose all that udev gives you when you do that) is to "downgrade" to the last working version of udev and use that version until the get all the "kinks" worked out of this new version.

Just my thoughts,
MMYoung