SiS7012---Slackware 9.1

[Bubba56]

OK, read some posts, tried to figure out what happened, but stuck atm. I installed Slackware 9.1 full install of all packages (cheaters version :P). I had sound working, got internet working downloaded and installed Swaret. I then did the Swaret --upgrade -a , --dep etc. Now I have no sound, after looking through some threads, I tried the following:

bash-2.05b#
bash-2.05b# alsamixer

alsamixer: function snd_ctl_open failed for default: No such device
bash-2.05b# lspci
00:00.0 Host bridge: Silicon Integrated Systems [SiS] 735 Host (rev 01)
00:01.0 PCI bridge: Silicon Integrated Systems [SiS] SiS 530 Virtual PCI-to-PCI bridge (AGP)
00:02.0 ISA bridge: Silicon Integrated Systems [SiS] 85C503/5513
00:02.2 USB Controller: Silicon Integrated Systems [SiS] SiS7001 USB Controller (rev 07)
00:02.3 USB Controller: Silicon Integrated Systems [SiS] SiS7001 USB Controller (rev 07)
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0)
00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] SiS7012 PC I Audio Accelerator (rev a0)
00:03.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 10/100 Ethe rnet (rev 90)
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE]

SO I am somewhat confused as to what happened or what to try next to regain sound. Did I not get some needed files or did the upgrade hose something?? I did have to reconfigure the network settings for internet access again, I tried to re-do xf86config so my crappy 2 button scroll wheel mouse would work also, but that is another problem :) , and after running Swaret, it changed my default desktop from Gnome to KDE at #startx?!?! but new KDE looks NICE!!!

Your humble and obedient Slack-wanna-be

Jon

[JamminJoeyB]

The answer to your question my friend is actually on this board. I don't remember the posters name, but I remember this much about the post.

He did a similar thing to you and upgraded alsa and lost sound. What he discovered is that the upgrade actually deleted his rc.alsa from etc/rc.d

He was actually able to determine this was the case as he had an second install of slackware on the same machine and look for what had changed between the two installs as he hadn't upgraded the other install yet. I think he just copied the rc.alsa from the other install, not %100 sure what he did, but a search for rc.alsa maybe the quickest to find that post.

[bsm2001]

open a terminal and su to root then issue the command lsmod. I have the same card and it uses the module snd-intel8x0 se if you have that module loaded and also make sure that the sound is not muted with alsamixer.

[Bubba56]

bash-2.05b# lsmod
Module Size Used by Not tainted
soundcore 3332 0 (autoclean)
usb-ohci 18888 0 (unused)
usbcore 58400 1 [usb-ohci]
sis900 13388 1
crc32 2880 0 [sis900]
pcmcia_core 40032 0
ide-scsi 9424 0
agpgart 39576 0 (unused)
bash-2.05b#


I see nothing about sound, so for someone who doesn't know squat about any modules/kernels, how do I go about getting this loaded back in or whatever?!?!

[JamminJoeyB]

You don't have it loaded.

as root

modprobe snd-intel8x0

If you don't get an error lsmod will show that loaded in your kernel and you may just have to unmute to have sound.

If you do get an error, post it back here.

Did you check to see if you still had an rc.alsa in your /ect/rc.d directory?

[Bubba56]

bash-2.05b# modprobe snd-intel8x0
modprobe: Can't locate module snd-intel8x0
bash-2.05b#


Yes there is an rc.alsa int the rc.d directory

[JamminJoeyB]

hmm ok. can't find it. strange. Did you edit the swaret.conf and possibly include the kernel instead of leaving it as an excluded package. That may have caused problems if you did. What kernel are you running. The latest package slackware has on the site is 2.4.26 if you haven't updated your kernel then you should. See the slackware site for security advisories.

Try doing a search for snd-intel8x0 and see if it's on your system.


The only other thing I can think of is camparing my rc.alsa to yours. It's posted below. Using the shotgun approach here.

#!/bin/sh
# Load the mixer settings and OSS compatibility for ALSA.
# (the Advanced Linux Sound Architecture)

# A function to load the ALSA mixer settings:
load_alsa_mixer() {
if [ -r /etc/asound.state ]; then
echo "Loading ALSA mixer settings: /usr/sbin/alsactl restore"
/usr/sbin/alsactl restore
else
echo "ALSA warning: No mixer settings found in /etc/asound.state."
echo " Sound may be muted. Use 'alsamixer' to unmute your sound card,"
echo " and then 'alsactl store' to save the default ALSA mixer settings"
echo " to be loaded at boot."
fi
}

# A function to load the ALSA OSS compat modules:

load_alsa_oss_modules() {
echo "Loading OSS compatibility modules for ALSA."
modprobe snd-pcm-oss
modprobe snd-mixer-oss
}

# If hotplug or something else has loaded the ALSA modules, then
# simply load the mixer settings and make sure the OSS compat
# modules are loaded:
if [ -d /proc/asound ]; then
load_alsa_mixer
load_alsa_oss_modules
else
# If there are ALSA modules defined in /etc/modules.conf, but
# ALSA is not yet loaded, then load the modules now:
DRIVERS=`modprobe -c | grep -E "^[[:space:]]*alias[[:space:]]+snd-card-[[:digit:]]" | awk '{ print $3 }'`
if [ ! "$DRIVERS" = "" ]; then
echo "Loading ALSA kernel modules."
for module in $DRIVERS; do
modprobe $module
done
fi
# If ALSA is now up, then load the mixer settings and OSS modules:
if [ -d /proc/asound ]; then
load_alsa_mixer
load_alsa_oss_modules
fi
fi

[bsm2001]

type uname -r in the terminal.

[Bubba56]

kernel 2.4.22 and the file, snd-intel8x0, is nowhere on the system.

Did the Swaret upgrade -a screw up something and delete a file?? should I do a swaret upgrade -a again and hope that it finds some sound files to download? maybe I shoulda just left everything alone :(

JamminJoey, I don't know if it would help any tryin to copy your config into mine if I don't even have the file to make the thing work.

[JamminJoeyB]

Time to check the log files.

the swaret log is in /var/log. You should be able to go through the log to see what was updated and changed.

swaret -a should not have caused a problem as that is the option I usually use. did you run a swaret update prior to the update -a?


It's also possible that doing a upgrade to the latest kernel package using upgradepkg might fix it. The instructions on how to upgrade the kernel package are on the slackware site under the secuity advisories as I stated earlier. not sure if this will fix it, but at I wouldn't expect it to make things worse.

Word to the wise. REMEMER to run lilo after installing a new kernel package. Boy did I have fun when I forgot to do that one time.

[Bubba56]

Nope, I didn't do any kernel upgrading, I am far too n00bish to even think about that crap.. shudder.
I did another upgrade -a hoping to pick up more packages etc that may have been missed, got the idea from the one page that Hard Candy directed me too when I so stupidly asked for distro ideas. I have rebooted since, was hoping problem would go away :P but on reboot and logging into KDE, I get a error message saying:

Informational - artsmessage
Error while initializing the sound driver
device /dev/dsp can't be opened (no such device)
the sound server will continue using the null device.

I get this every time I reboot now so something in Swaret nuke my onboard pos sound ( and that don't stand for point of sale).

I don't know how to proceed, do I have to make a /dev/dsp directory and then download some drivers or something.??? Or should I just say , the hell with it, reload 9.1 and leave it alone with no upgrades? I don't understand what I need to try to do next.

HardCandy, JohnT HELP !!!! you talked me into this Slack thing, I need more guidance :(

[mdwatts]

Did you try


This appears to be the solution...

news flash: i found out how to fix the problem. it's just a matter of linking the sound devices, and this can be done by running the snddevices script in the untarred alsa-driver directory. i know it said you shouldn't have to do it for the newer drivers, but ignore that.

make sure you have the modules correctly inserted first.

now i have alsa sound!


from this thread (http://justlinux.com/forum/showthread.php?s=&threadid=120696&highlight=alsamixer+function+sndctlopen+failed+swa ret)?

I would think Slackware would have something on their support site, forums, usergroups on this problem since it seems to affect so many swaret users. :confused:

[Bubba56]

Sory MD, read that thread and severa of the links from it, went to alsa's site, I don't even understand what to download, much less where to run the script they talk about. I am totally confused now. I don't understand what would have made the sound card disappear by just adding (Swaret) new drivers? isn't that what alsa is basically sound card drivers?

Found this on Alsa site under SiS 7012 but I don't understand it.

In a shell type these commands:

Unzip and install the alsa-driver package

bunzip2 alsa-driver-xxx
tar -xf alsa-driver-xxx
cd alsa-driver-xxx
./configure --with-cards=intel8x0 --with-sequencer=yes;make;make install

NB. If you are using drivers before 0.9.4 then you need to run

./snddevices

If you use devfs then you should not run the snddevices script

The snddevices script sets the permissions for the devices it creates to root. You should

chmod a+rw /dev/dsp /dev/mixer /dev/sequencer /dev/midi

Now unzip and install the alsa-lib package

cd ..
bunzip2 alsa-lib-xxx
tar -xf alsa-lib-xxx
cd alsa-lib-xxx
./configure;make;make install

Now unzip and install the alsa-utils package

cd ..
bunzip2 alsa-utils-xxx
tar -xf alsa-utils-xxx
cd alsa-utils-xxx
./configure;make;make install

Now insert the modules into the kernel.

modprobe snd-intel8x0;modprobe snd-pcm-oss;modprobe snd-mixer-oss;modprobe snd-seq-oss

NB. For drivers older than 0.9.0beta11 use:

modprobe snd-card-intel8x0

I mean yes I unbderstand but have never down the tarball thing, but I don't know what drivers I would be downloading as the directory that I see on the download page lists tons of files and the tail end is cut off, with no way to adjust the column with so I can see the entire file name. ALSO, I just did the Swaret upgrade thing, did that NOT give me the latest drivers or whatever for Alsa? AND last but not least, it says use the snddevices script UNLESS you use devfs, uumm HUUH?? I haven't a clue what I have nor how to use a script. SOrry but I think I am in over my head, the above directions talk about inseriting a module?? I can't even get my mouse wheel to scroll :(

[Bubba56]

tried out the followiing commands that other threads asked fo:

bash-2.05b# lsmod
Module Size Used by Not tainted
soundcore 3332 0 (autoclean)
usb-ohci 18888 0 (unused)
usbcore 58400 1 [usb-ohci]
sis900 13388 1
crc32 2880 0 [sis900]
pcmcia_core 40032 0
ide-scsi 9424 0
agpgart 39576 0 (unused)
bash-2.05b# arecord -l
arecord: device_list:196: no soundcards found...
bash-2.05b# alsamixer -c 1

alsamixer: function snd_ctl_open failed for hw:1: No such device
bash-2.05b# alsamixer -d 1
alsamixer: invalid option -- d
AlsaMixer v1.00
Usage: alsamixer [-h] [-c <card: 0...7 or id>] [-D <mixer device>] [-g] [-s]

bash-2.05b# alsamixer -D 1
ALSA lib control.c:612:(snd_ctl_open_noupdate) Invalid CTL 1

alsamixer: function snd_ctl_open failed for 1: No such file or directory
bash-2.05b#

Does this mean that Linux no longer SEES the sooundcard, even though it was working prior to the Swaret upgrade -a ??

[JamminJoeyB]

what is the version of alsa are you running and did you upgrade it through swaret?

did you read this thread?

http://www.justlinux.com/forum/showthread.php?s=&threadid=122563&highlight=rc.alsa

[Bubba56]

I read the thred checked the person's file

http://www.justlinux.com/forum/attachment.php?s=&postid=695340

and then I compared my alsa.rc, they are the same, sadly I do not know how to find the version of a program so I can't tell you what version it is. I believe it did get upgraded via Swaret tho, it did a LOT pof programs, and some straange things now happen. My terminal pops open with an eror message about some font, I have 4 internet browsers to choose from but ONLY Netscape works, Mozilla was fine before upgrade, etc. Would it be better if I just found an old regular plug in the slot cound card, would that fix the issue?

[Bubba56]

I just tried a :
Swaret --reinstall alsa

it said that alsa 1.04 was not installed do you want to etc, I replied yes to all install questions, re-booted and got the same message

Informational - artsmessage
Error while initializing the sound driver
device /dev/dsp can't be opened (no such device)
the sound server will continue using the null device

So apparently the sound card was still using an older version?? But it worked fine before I ran the swaret --upgrade etc? DO I need to manually make a /dev/dsp folder or directory and install a driver there or something?

[Bubba56]

ok, I looked in the /dev folder there are entries for /dsp, dsp1. dsp1, dsp2 and dsp3 I believe, I trie dot open (to read them) as root with kwrote, got an error saying I didn't have rights to read the files??. Could this be why I get the error saying that device /dev/dsp does't exist?

I also tried re-booting -- . disableing on-board sound log on, shhhut down re-booted enabled sound all in the hopes that Kudzu( I think thatas the program) would auto-detect the on-board sound again, Nothing, same error message.

SO can anyone tell me, short of re-installing Slackware 9.1 what process I can do or go thru to get sound working again??

[mdwatts]

Originally posted by Bubba56

device /dev/dsp can't be opened (no such device)

ok, I looked in the /dev folder there are entries for /dsp, dsp1. dsp1, dsp2 and dsp3 I believe, I trie dot open (to read them) as root with kwrote, got an error saying I didn't have rights to read the files??. Could this be why I get the error saying that device /dev/dsp does't exist?


We've had more posts on that error than probably most other error messages.

The proper way to fix is to add the user(s) to the audio group while the other is to directly change the permissions of /dev/dsp with

chmod 666 /dev/dsp

as root.

[Bubba56]

oops, I forgot to mention, This is ALL done as root, I haven't even created a user yet, just trying to get everything working.

[Bubba56]

OK, I am hoping that I can fix the problem by shuting off on-board sound and installing a regualr card. I have a Soundblaster Live 5.1 that I am going to put into the Slackware box. now here is a question that will show just how n00bish I really am. Will Kudzu or whatever hardware detection program Slackware uses automatically detect and open a configure menu for me on re-boot?? Or is there a manual thing like in windows add/remove hardware? I haven't seen such a critter in KDE console?!!?

[Bubba56]

Well, I did the re-install route after I nuked the on-board sound and installed a Soundblaster Live. I am somewhat leary of doing the Swaret thing now tho, I have tried sound and it works fine, (testing with the "test sound system" in the KDE mixer settings). I am concerned that if I Swaret --upgrade -a I will mess up the sound again somehow, any thoughts on that?

[JamminJoeyB]

Some things to think about when using swaret.

If you are using swaret to manage all your packages it's not always good to issue a upgrade -a. The reason is that you may have other repositories in there other then the offical slackare ones.

I always issue a swaret -update before upgrade.
That way if I am only looking to fix some packages because of security issues I can see if those are the packages mentioned. I also comment out the un-official repsitories when doing this.

According to the slackware site. alsa 1.0.4 is in the slackware current. While this shouldn't be a problem it seems to have caused a problem when you did a swaret upgrade -a.

What mirrors where you using when you did this? If you uncommented all the mirrors and not just the 9.1 you would get a ton of packages to upgrade. Read the documentation on the swaret site as it is quite good.