SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have Slack 9.1 with kernel 2.4.23. When I first installed Slack 9.1 with the default 2.4.22 kernel, then installed the latest ALSA package, I had sound.
I've compiled 2.4.23, then installed ALSA 1.0.0rc2 and unmuted everything in alsamixer, then as root ran alsactl store. And no sound.
Now, I get this error message at boot. Haven't seen this since I tried RedHat in May.
Code:
Sound server informational message:
Error while initializing the sound driver:
device: default can't be opened for playback (Permission denied)
The sound server will continue, using the null output device.
Here's more information:
Code:
From dmesg | less ->
ALSA ../alsa-kernel/pci/via82xx.c:577: codec_read: codec 0 is not valid [0x87e5370]
ALSA ../alsa-kernel/pci/via82xx.c:577: codec_read: codec 0 is not valid [0x87e5370]
ALSA ../alsa-kernel/pci/via82xx.c:577: codec_read: codec 0 is not valid [0x87e5370]
ALSA ../alsa-kernel/pci/via82xx.c:577: codec_read: codec 0 is not valid [0x87e5370]
Code:
From my current kernel .config file ->
# Sound
#
CONFIG_SOUND=m
# CONFIG_SOUND_ALI5455 is not set
# CONFIG_SOUND_BT878 is not set
# CONFIG_SOUND_CMPCI is not set
# CONFIG_SOUND_EMU10K1 is not set
# CONFIG_MIDI_EMU10K1 is not set
# CONFIG_SOUND_FUSION is not set
# CONFIG_SOUND_CS4281 is not set
# CONFIG_SOUND_ES1370 is not set
# CONFIG_SOUND_ES1371 is not set
# CONFIG_SOUND_ESSSOLO1 is not set
# CONFIG_SOUND_MAESTRO is not set
# CONFIG_SOUND_MAESTRO3 is not set
# CONFIG_SOUND_FORTE is not set
# CONFIG_SOUND_ICH is not set
# CONFIG_SOUND_RME96XX is not set
# CONFIG_SOUND_SONICVIBES is not set
# CONFIG_SOUND_TRIDENT is not set
# CONFIG_SOUND_MSNDCLAS is not set
# CONFIG_SOUND_MSNDPIN is not set
# CONFIG_SOUND_VIA82CXXX is not set
# CONFIG_MIDI_VIA82CXXX is not set
# CONFIG_SOUND_OSS is not set
# CONFIG_SOUND_TVMIXER is not set
# CONFIG_SOUND_AD1980 is not set
# CONFIG_SOUND_WM97XX is not set
I read another thread here, and removed the original ALSA package that came with Slack 9.1, and the new package I'd installed, then re-installed the new ALSA package. I also tried running /etc/modules.conf with this second line commented and uncommented ->
Code:
anna@peter:~$ cat /etc/modules.conf
alias char-major-195 nvidia
#options snd-via82xx index=0 dxs_support=2
What else should I do? I'm fresh out of ideas, but I think that arts sound server needs to be removed for sure.
You can try killing arts: killall arts. I have experienced problems with arts in the past (I don't use it now). Have you tried running alsaconf (as root)? I used it when I manually installed ALSA and it created a bunch more alias' than you have:
scruff@dabasement:~$ cat /etc/modules.conf
# --- BEGIN: Generated by ALSACONF, do not edit. ---
# --- ALSACONF verion 0.9.0 ---
alias char-major-116 snd
alias snd-card-0 snd-emu10k1
alias char-major-14 soundcore
alias sound-slot-0 emu10k1
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
options snd major=116 cards_limit=2
options snd-emu10k1 index=0
# --- END: Generated by ALSACONF, do not edit. ---
# load/unload the volume settings on startup/shutdown
post-install snd-emu10k1 /usr/sbin/alsactl restore
pre-remove snd-emu10k1 /usr/sbin/alsactl store
I don't know if this will help, but it looks like your drivers are loaded fine. It also looks as if you might not have the proper permissions set for the soundcard. ls -l /dev/dsp to check it out.
scruff@dabasement:~$ ls -l /dev/dsp
lrwxrwxrwx 1 root root 4 Nov 2 11:49 /dev/dsp -> dsp0
My permissions are pretty lax on the soundcard, but I was having trouble getting users to hear sound from Flash in Firebird.
Originally posted by Scruff You can try killing arts: killall arts. I have experienced problems with arts in the past (I don't use it now).
anna@peter:~$ killall arts
arts: no process killed
anna@peter:~$ su
Password:
root@peter:/home/anna# killall arts
arts: no process killed
Quote:
Have you tried running alsaconf (as root)? I used it when I manually installed ALSA and it created a bunch more alias' than you have:
scruff@dabasement:~$ cat /etc/modules.conf
# --- BEGIN: Generated by ALSACONF, do not edit. ---
# --- ALSACONF verion 0.9.0 ---
alias char-major-116 snd
alias snd-card-0 snd-emu10k1
alias char-major-14 soundcore
alias sound-slot-0 emu10k1
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
options snd major=116 cards_limit=2
options snd-emu10k1 index=0
# --- END: Generated by ALSACONF, do not edit. ---
# load/unload the volume settings on startup/shutdown
post-install snd-emu10k1 /usr/sbin/alsactl restore
pre-remove snd-emu10k1 /usr/sbin/alsactl store
Loading driver...
/usr/sbin/alsaconf: line 619: rcalsasound: command not found
Setting default volumes...
===============================================================================
Now ALSA is ready to use.
For adjustment of volumes, use your favorite mixer.
Have a lot of fun!
root@peter:/home/anna#
AFter alsaconf ->
Code:
anna@peter:~$ alsamixer
anna@peter:~$ cat /etc/modules.conf
alias char-major-195 nvidia
#options snd-via82xx index=0 dxs_support=2
# --- BEGIN: Generated by ALSACONF, do not edit. ---
# --- ALSACONF verion 1.0.0rc2 ---
alias char-major-116 snd
alias char-major-14 soundcore
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
alias snd-card-0 snd-via82xx
alias sound-slot-0 snd-via82xx
# --- END: Generated by ALSACONF, do not edit. ---
Quote:
I don't know if this will help, but it looks like your drivers are loaded fine. It also looks as if you might not have the proper permissions set for the soundcard. ls -l /dev/dsp to check it out.
scruff@dabasement:~$ ls -l /dev/dsp
lrwxrwxrwx 1 root root 4 Nov 2 11:49 /dev/dsp -> dsp0
root@peter:/home/anna# ls -l /dev/dsp
lrwxrwxrwx 1 root root 4 Dec 29 23:48 /dev/dsp -> dsp0
Quote:
My permissions are pretty lax on the soundcard, but I was having trouble getting users to hear sound from Flash in Firebird.
aaarrrggghhh!!!!
I know it's something simple, perhaps, but I just can't stand to have a computer win.
And why couldn't I kill arts? I seem to kill other things just fine without even trying.
Last edited by Bruce Hill; 12-29-2003 at 10:42 PM.
Do 'ps aux' real quick to see how arts is listed. I thought that would have killed it. Maybe it's artsd. Or maybe it's not even running right now
Did running alsaconf change your modules.conf file any? Also, some of the changes you make will require you to restart ALSA to take effect. You can cd /etc/rc.d/ and do ./rc.alsa
There's a command, but I can't remember it. I think it's 'killall -HUP alsa' to restart a process.
Originally posted by Scruff
Do 'ps aux' real quick to see how arts is listed. I thought that would have killed it. Maybe it's artsd. Or maybe it's not even running right now
Okey dokey ->
Code:
anna@peter:~$ ps aux
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1 1.4 0.0 484 236 ? S 12:54 0:04 init [3]
root 2 0.0 0.0 0 0 ? SW 12:54 0:00 [keventd]
root 3 0.0 0.0 0 0 ? SWN 12:54 0:00 [ksoftirqd_CPU0]
root 4 0.0 0.0 0 0 ? SW 12:54 0:00 [kswapd]
root 5 0.0 0.0 0 0 ? SW 12:54 0:00 [bdflush]
root 6 0.0 0.0 0 0 ? SW 12:54 0:00 [kupdated]
root 9 0.0 0.0 0 0 ? SW 12:54 0:00 [khubd]
root 14 0.0 0.0 0 0 ? SW 12:54 0:00 [kreiserfsd]
root 501 0.0 0.2 1436 612 ? S 12:55 0:00 /usr/sbin/syslogd
root 504 0.0 0.1 1376 460 ? S 12:55 0:00 /usr/sbin/klogd -c 3 -x
root 507 0.0 0.2 1412 540 ? S 12:55 0:00 /usr/sbin/inetd
root 510 0.0 0.5 3080 1416 ? S 12:55 0:00 /usr/sbin/sshd
root 520 0.0 0.2 1496 556 ? S 12:55 0:00 /usr/sbin/crond -l10
daemon 522 0.0 0.2 1504 644 ? S 12:55 0:00 /usr/sbin/atd -b 15 -l 1
root 525 0.0 0.8 4828 2068 ? S 12:55 0:00 sendmail: accepting connections
smmsp 528 0.0 0.7 4732 1952 ? S 12:55 0:00 sendmail: Queue runner@00:25:00 for /var/spool/clientmqueue
root 532 0.0 0.1 1420 472 ? S 12:55 0:00 /usr/sbin/gpm -m /dev/mouse -t ps2
anna 534 0.0 0.5 2284 1292 tty1 S 12:55 0:00 -bash
root 535 0.0 0.1 1368 480 tty2 S 12:55 0:00 /sbin/agetty 38400 tty2 linux
root 536 0.0 0.1 1368 480 tty3 S 12:55 0:00 /sbin/agetty 38400 tty3 linux
root 537 0.0 0.1 1368 480 tty4 S 12:55 0:00 /sbin/agetty 38400 tty4 linux
root 538 0.0 0.1 1368 480 tty5 S 12:55 0:00 /sbin/agetty 38400 tty5 linux
root 539 0.0 0.1 1368 480 tty6 S 12:55 0:00 /sbin/agetty 38400 tty6 linux
anna 550 0.0 0.3 2048 972 tty1 S 12:57 0:00 /bin/sh /usr/X11R6/bin/startx
anna 561 0.0 0.2 2244 632 tty1 S 12:57 0:00 xinit /usr/X11R6/lib/X11/xinit/xinitrc --
root 562 4.8 7.3 284972 18928 ? SL 12:57 0:08 X :0
anna 568 0.0 0.3 2036 932 tty1 S 12:57 0:00 /bin/sh /usr/X11R6/lib/X11/xinit/xinitrc
anna 570 0.0 0.3 2052 972 tty1 S 12:57 0:00 /bin/sh /opt/kde/bin/startkde
anna 582 0.0 5.3 25964 13560 ? S 12:57 0:00 kdeinit: Running...
anna 585 0.0 5.3 25636 13568 ? S 12:57 0:00 kdeinit: dcopserver --nosid
anna 588 0.0 5.7 27012 14640 ? S 12:57 0:00 kdeinit: klauncher
anna 590 0.1 6.6 29964 16996 ? S 12:57 0:00 kdeinit: kded
anna 606 0.1 2.3 9980 6056 ? S 12:57 0:00 /opt/kde/bin/artsd -F 10 -S 4096 -a alsa -s 60 -m artsmessage
anna 608 0.0 7.3 33048 18696 ? S 12:57 0:00 kdeinit: knotify
anna 609 0.0 0.1 1364 336 tty1 S 12:57 0:00 kwrapper ksmserver
anna 613 0.0 6.1 27236 15704 ? S 12:57 0:00 kdeinit: ksmserver
anna 614 0.3 6.8 29124 17496 ? S 12:57 0:00 kdeinit: kwin -session 11c0a80115000107209340900000020170000_
anna 616 0.0 6.5 28024 16648 ? S 12:57 0:00 kdeinit: kwrited
anna 618 0.4 7.8 30540 20164 ? S 12:57 0:00 kdeinit: kdesktop
anna 621 0.4 7.6 31564 19452 ? S 12:57 0:00 kdeinit: kicker
anna 622 0.0 5.4 26180 14028 ? S 12:57 0:00 kdeinit: kio_file file /tmp/ksocket-anna/klauncherC0m2Ga.slav
anna 623 0.0 5.4 26004 13908 ? S 12:57 0:00 kdeinit: kio_devices devices /tmp/ksocket-anna/klauncherC0m2G
anna 625 0.1 6.4 28984 16464 ? S 12:57 0:00 kdeinit: kio_thumbnail thumbnail /tmp/ksocket-anna/klauncherC
anna 627 0.0 6.6 28752 17080 ? S 12:57 0:00 kdeinit: klipper
anna 632 0.1 6.6 28376 16976 ? S 12:57 0:00 korgac --miniicon korganizer
anna 633 0.0 6.0 27340 15432 ? S 12:57 0:00 kalarmd --login
anna 635 0.1 6.8 28668 17576 ? S 12:57 0:00 kdeinit: kio_uiserver
anna 637 0.5 9.7 38440 24956 ? S 12:57 0:00 kmail -caption KMail -icon kmail -miniicon kmail
anna 654 0.0 5.5 26920 14112 ? S 12:57 0:00 kdeinit: kio_file file /tmp/ksocket-anna/klauncherC0m2Ga.slav
anna 655 0.0 6.0 27628 15384 ? S 12:58 0:00 kdeinit: kio_pop3 pop3s /tmp/ksocket-anna/klauncherC0m2Ga.sla
anna 657 0.0 0.4 2112 1048 ? S 12:58 0:00 /bin/sh /usr/lib/mozilla-1.4/run-mozilla.sh /usr/lib/mozilla-
anna 664 7.3 12.1 53872 30956 ? S 12:58 0:08 /usr/lib/mozilla-1.4/mozilla-bin
anna 678 2.0 7.6 31868 19448 ? S 12:59 0:00 kdeinit: konsole --ls
anna 679 0.0 0.5 2276 1284 pts/1 S 12:59 0:00 -bash
anna 691 0.0 0.3 2864 916 pts/1 R 13:00 0:00 ps aux
What's this one ->
Quote:
anna 606 0.1 2.3 9980 6056 ? S 12:57 0:00 /opt/kde/bin/artsd -F 10 -S 4096 -a alsa -s 60 -m artsmessage
and this one ->
Quote:
anna 585 0.0 5.3 25636 13568 ? S 12:57 0:00 kdeinit: dcopserver --nosid
I get some funky lines about artsd and DCOP when I shutdown with Alt + Ctl + Bksp that I never see on my other comp. I can't highlight them with the mouse and paste them, so how do I read them later? And my mouse does some really strange things, like make the screen scroll as if I'd hit enter, and highlight text if I move it. So, you'll want to see this, too ->
Code:
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "ExplorerPS/2"
Option "ZAxisMapping" "4 5"
Option "Device" "/dev/mouse"
# Mouse-speed setting for PS/2 mouse.
# Option "Resolution" "256"
# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.
# Option "Protocol" "Xqueue"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"
# ChordMiddle is an option for some 3-button Logitech mice
# Option "ChordMiddle"
EndSection
My mouse is a Microlab PS/2 mouse - old fashioned kind that plugs into the PS/2 port and has two buttons and a scroll wheel - and a ball - not even optical.
Quote:
Did running alsaconf change your modules.conf file any? Also, some of the changes you make will require you to restart ALSA to take effect. You can cd /etc/rc.d/ and do ./rc.alsa
There's a command, but I can't remember it. I think it's 'killall -HUP alsa' to restart a process.
I posted the changes to modules.conf in the other post. May have been in the edit - sorry.
Code:
root@peter:/etc/rc.d# ./rc.alsa
bash: ./rc.alsa: No such file or directory
Just for kicks, I even rebooted
NB: Check Windblows mind at the door!
Shucks, in Winders, it just works
Last edited by Bruce Hill; 12-30-2003 at 08:02 PM.
You'll also want to check the output of
ls -l /dev/dsp0
since it's showing /dev/dsp is a link to dsp0
Also, artsd is the "aRTs" daemon, which runs, mixing sound and doing its thing in the background as initiated by KDE.
killall artsd will do it.
As for alsa. It can be a real bear to get up and running, but I've had pretty good luck with it now that i've got it figured out.
that little options line you got, index=0 dxa_support=2
Did you get that from one of my posts? I posted something about that for my VIA chipset AC97.
Also, try the command
/etc/rc.d/rc.alsa start
The goodnews, as stated above, is that it looks like your modules are loaded correctly.
That means the support is there. It's up to you and alsa to armwrestle sound from your system, now. Of course, we'll help
You'll also want to check the output of
ls -l /dev/dsp0
since it's showing /dev/dsp is a link to dsp0
root@peter:/etc/rc.d# ls -l /dev/dsp0
crw-rw--w- 1 root sys 14, 3 Aug 29 15:47 /dev/dsp0
Quote:
Also, artsd is the "aRTs" daemon, which runs, mixing sound and doing its thing in the background as initiated by KDE.
killall artsd will do it.
I did
root@peter:/etc/rc.d# killall artsd
root@peter:/etc/rc.d#
and it returned me to a prompt, but what did it do? Still no sound
Quote:
As for alsa. It can be a real bear to get up and running, but I've had pretty good luck with it now that i've got it figured out.
Never had a problem like this before. Yes, once I figured ALSA out (by following the instructions on the ALSA site) it always just works.
Quote:
that little options line you got, index=0 dxa_support=2
Did you get that from one of my posts? I posted something about that for my VIA chipset AC97.
I can't remember. The post also said to find the ALSA package that came with Slack 9.1 and remove it. You know, when the wheels are falling off, I start grabbing at straws.
Quote:
Also, try the command
/etc/rc.d/rc.alsa start
Code:
root@peter:/etc/rc.d# /etc/rc.d/rc.alsa start
bash: /etc/rc.d/rc.alsa: No such file or directory
Same as in the previous post following Scruff. I don't have rc.alsa
Code:
root@peter:/etc/rc.d# ls -aFlc
total 183
drwxr-xr-x 2 root root 936 Dec 30 10:08 ./
drwxr-xr-x 46 root root 4752 Dec 30 12:55 ../
lrwxrwxrwx 1 root root 4 Dec 29 23:49 rc.0 -> rc.6*
-rwxr-xr-x 1 root root 893 Dec 29 23:49 rc.4*
-rwxr-xr-x 1 root root 4782 Dec 29 23:49 rc.6*
-rwxr-xr-x 1 root root 2013 Dec 29 23:49 rc.K*
-rwxr-xr-x 1 root root 7634 Dec 29 23:49 rc.M*
-rwxr-xr-x 1 root root 8312 Dec 29 23:49 rc.S*
-rwxr-xr-x 1 root root 466 Dec 29 23:48 rc.acpid*
-rw-r--r-- 1 root root 1032 Dec 29 23:55 rc.atalk
-rw-r--r-- 1 root root 1031 Dec 29 23:55 rc.bind
-rw-r--r-- 1 root root 3949 Dec 29 23:48 rc.cups
-rwxr-xr-x 1 root root 119 Dec 29 23:48 rc.font.sample*
-rwxr-xr-x 1 root root 1148 Dec 30 00:08 rc.gpm*
-rwxr-xr-x 1 root root 1160 Dec 30 00:07 rc.hotplug*
-rw-r--r-- 1 root root 401 Dec 29 23:55 rc.httpd
-rwxr-xr-x 1 root root 4038 Dec 29 23:56 rc.inet1*
-rw-r--r-- 1 root root 898 Dec 29 17:42 rc.inet1.conf
-rwxr-xr-x 1 root root 4419 Dec 29 23:56 rc.inet2*
-rwxr-xr-x 1 root root 497 Dec 29 23:55 rc.inetd*
-rw-r--r-- 1 root root 1924 Dec 29 23:56 rc.ip_forward
-rwxr-xr-x 1 root root 113 Dec 29 23:49 rc.local*
-rw-r--r-- 1 root root 580 Dec 29 23:49 rc.lprng
-rwxr-xr-x 1 root root 25453 Dec 29 21:23 rc.modules*
-rw-r--r-- 1 root root 2259 Dec 29 23:49 rc.mysqld
-rwxr-xr-x 1 root root 2449 Dec 29 23:55 rc.nfsd*
-rwxr-xr-x 1 root root 4790 Dec 29 23:49 rc.pcmcia*
-rw-r--r-- 1 root root 905 Dec 29 23:55 rc.portmap
-rw-r--r-- 1 root root 728 Dec 29 23:55 rc.samba
-rwxr-xr-x 1 root root 687 Dec 29 23:55 rc.sendmail*
-rwxr-xr-x 1 root root 2895 Dec 29 23:49 rc.serial*
-rwxr-xr-x 1 root root 1222 Dec 29 23:55 rc.sshd*
-rwxr-xr-x 1 root root 861 Dec 29 23:49 rc.syslog*
-rwxr-xr-x 1 root root 1740 Dec 29 23:49 rc.sysvinit*
-rwxr-xr-x 1 root root 2323 Dec 29 23:56 rc.yp*
Quote:
The goodnews, as stated above, is that it looks like your modules are loaded correctly.
That means the support is there. It's up to you and alsa to armwrestle sound from your system, now. Of course, we'll help
-Shade
I think I found something here, but I don't have enough knowledge to fully understand this. On the first install, I called the computer peter. Then, on the second one I didn't format the /home partition, and I named the computer john. Actually, it could be peter because the motherboard in peter died and he's a Sony notebook from America.
Code:
root@peter:/home/anna/.kde# ls -aFlc
total 5
drwx------ 4 anna users 224 Dec 24 07:29 ./
drwx--x--x 11 anna users 960 Dec 30 12:57 ../
drwx------ 2 anna users 80 Dec 22 19:43 Autostart/
drwx------ 9 anna users 224 Dec 26 07:37 share/
lrwxrwxrwx 1 anna users 17 Dec 24 07:29 socket-john -> /tmp/ksocket-anna/
lrwxrwxrwx 1 anna users 17 Dec 22 19:43 socket-peter -> /tmp/ksocket-anna/
lrwxrwxrwx 1 anna users 13 Dec 24 07:29 tmp-john -> /tmp/kde-anna/
lrwxrwxrwx 1 anna users 13 Dec 22 19:43 tmp-peter -> /tmp/kde-anna/
That may be confusing, but I think the problem lies somewhere in that KDE junk in the /home directory.
Coming from years of Winders experience, I know the easiest thing is to format and start over - especially since this worked on the initial install. However, I hate Winders, even though my W2K system works about 10 times better than Slack! And, everything just works! I just want to get away from the EULA and business practices of Micro$loth. And so, I want to find out WHY this isn't working properly.
Thanks for your help! One of my major goals in life is the get free from the M$ OSes!!! And, it will happen fairly soon! So I'd rather fix this comp than just reinstall.
when i updated my alsa drivers.. it killed the snd-via* sound modules.. I switched to via82cxxx_audio and then everything worked. so I suggest you try this
modprobe via82cxxx_audio
then check and see if you ahve sound... if you do.. add
Originally posted by trey85stang when i updated my alsa drivers.. it killed the snd-via* sound modules.. I switched to via82cxxx_audio and then everything worked. so I suggest you try this
modprobe via82cxxx_audio
then check and see if you ahve sound... if you do.. add
/sbin/modprobe via82cxxx_audio
to your /etc/rc.d/rc.modules file.
I already have that under sound in /etc/rc.d/rc.modules
Originally posted by Shade Yeah.. Another way would just to be use OSS instead of alsa.
I did on my desktop for quite a while witht he same card you have.
You'll want to make sure all the alsa modules are taken out first though... rmmod is your friend in this case.
anything that starts with snd you'll want to take out before trying modprobe via82cxxx_audio
-Shade
Shade,
Thanks, but at this point I'm determined to ascertain the cause of this problem with ALSA. I'm migrating from Windoze to use *nix exclusively, so it's important to me to learn how to fix problems rather than just replace them. I know ALSA works with this card, for I had it working once, as previously stated.
Is there a way to cast the arts demon out of my system? Or is that something that should be kept?
Did you notice this in my last post to you ->
Code:
bash: /etc/rc.d/rc.alsa: No such file or directory
I'm still wet behind my *nix ears, but when you guys tell me to start alsa and I don't have that, shouldn't it tell you something?
Okey dokey. I can't find anything to help after reading a ton and Googling and searching LQ. No one seems to understand the DCOP server thing, but I just think that
Code:
lrwxrwxrwx 1 anna users 17 Dec 24 07:29 socket-john -> /tmp/ksocket-anna/
lrwxrwxrwx 1 anna users 17 Dec 22 19:43 socket-peter -> /tmp/ksocket-anna/
lrwxrwxrwx 1 anna users 13 Dec 24 07:29 tmp-john -> /tmp/kde-anna/
lrwxrwxrwx 1 anna users 13 Dec 22 19:43 tmp-peter -> /tmp/kde-anna/
in post #8 up there seems to be the problem.
So, it might not be the *nix way, but I'm going to format all of Slack, including /home this time, and reinstall. ALSA will work correctly after I do this
That's an old saying from my home state, Mississippi.
Finally today I was able to get to this computer and reinstall Slack, hoping to fix the sound issue. Yes, I formatted everything so she'd be clean again. After the install I did change my mouse so it will scroll. It's a Microlab PS/2 mouse, not optical or anything. So in /etc/X11/XF86Config I changed PS/2 to ExplorerPS/2 and added Option "ZAxisMapping" "4 5" cause I read that will work, and it now scrolls. But since it ain't got but 2 buttons and a scroll wheel I tried commenting out that second line, but it won't scroll without it. And I tried ZAxisMapping without adding Explorer to PS/2 and that didn't work either. Now the feller will do some strange things when I first boot to the terminal, but seems okay once the X server is running.
To get the sound working I uncommented
/sbin/modprobe via82cxxx_audio
in the file
pico /etc/rc.d/rc.modules
and then did
startx
and sure enough, I had sound. Not very loud, so as a user I ran
alsamixer
and unmutted and put volume on most everything and exited and sued to root and did
alsactl store
then exited to a user and went into X again and I had louder sound. Not very good quality, but sound.
Now I'm thinking, I'll just recompile the kernel now and use the ALSA drivers this time. So I make another test run, rebooted the machine, and there's no more sound. Why? Everything is still the same but no sound.
And now when I run
alsamixer
I get
Code:
anna@peter:~$ alsamixer
alsamixer: function snd_ctl_open failed for default: No such device
Go figure
Hey, Shade - I'm armwrestling now, eh?
Last edited by Bruce Hill; 01-01-2004 at 04:03 AM.
Okay, now I've recompiled the kernel. Removed everything old that was ALSA. Have the soundcore.o when I do modinfo soundcore. No sound module chosen. I installed alsa driver, library and utilites - version 1.0.0rc2 according to the instructions on the ALSA site. Then I ran alsamixer as user and unmutted and turned up some things. Then I su and ran alsactl store. Then I exit to user and did startx and had sound. Loud sound, so I opened a konsole and turned anything that was in the red down to just the green levels - maybe mid 70's.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.