LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   SUSE / openSUSE (https://www.linuxquestions.org/questions/suse-opensuse-60/)
-   -   No Sound SuSE 10.0 Should be working (https://www.linuxquestions.org/questions/suse-opensuse-60/no-sound-suse-10-0-should-be-working-399186/)

EclipseAgent 01-03-2006 04:30 PM

No Sound SuSE 10.0 Should be working
 
Ok, so here it is. It was working, I installed VMWare 4.5.2, still worked, then all of a sudden, while working and listening to music, it shut off, and I haven't been able to get it to work since.

Here is some info:

uname -r
2.6.13-15.7-default

-----------------------------------------------

lsmod | grep snd
snd_pcm_oss 59552 0
snd_mixer_oss 19072 1 snd_pcm_oss
snd_seq 52368 0
snd_seq_device 8716 1 snd_seq
snd_intel8x0 33760 4
snd_ac97_codec 91260 1 snd_intel8x0
snd_ac97_bus 2560 1 snd_ac97_codec
snd_pcm 93448 4 snd_pcm_oss,snd_intel8x0,snd_ac97_codec
snd_timer 24708 3 snd_seq,snd_pcm
snd 60804 14 snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer
soundcore 9312 1 snd
snd_page_alloc 10888 2 snd_intel8x0,snd_pcm

--------------------------------------------------

cat /proc/modules | grep snd
snd_pcm_oss 59552 0 - Live 0xf8ec9000
snd_mixer_oss 19072 1 snd_pcm_oss, Live 0xf8e9e000
snd_seq 52368 0 - Live 0xf8ea8000
snd_seq_device 8716 1 snd_seq, Live 0xf8e93000
snd_intel8x0 33760 4 - Live 0xf938d000
snd_ac97_codec 91260 1 snd_intel8x0, Live 0xf9359000
snd_ac97_bus 2560 1 snd_ac97_codec, Live 0xf8858000
snd_pcm 93448 4 snd_pcm_oss,snd_intel8x0,snd_ac97_codec, Live 0xf930a000
snd_timer 24708 3 snd_seq,snd_pcm, Live 0xf92ca000
snd 60804 14 snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer, Live 0xf92de000
soundcore 9312 1 snd, Live 0xf9252000
snd_page_alloc 10888 2 snd_intel8x0,snd_pcm, Live 0xf903e000

---------------------------------------------------

cat /etc/modprobe.d/sound
options snd-intel8x0 enable=1 index=0
# W60f.0p1d2eFRi_8:82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller
alias snd-card-0 snd-intel8x0

---------------------------------------------------

Jan 3 14:21:12 LSSUSE-01004839 kernel: snd_page_alloc: module not supported by Novell, setting U taint flag.
Jan 3 14:21:12 LSSUSE-01004839 kernel: snd: module not supported by Novell, setting U taint flag.
Jan 3 14:21:12 LSSUSE-01004839 kernel: snd_timer: module not supported by Novell, setting U taint flag.
Jan 3 14:21:12 LSSUSE-01004839 kernel: snd_pcm: module not supported by Novell, setting U taint flag.
Jan 3 14:21:12 LSSUSE-01004839 kernel: snd_ac97_bus: module not supported by Novell, setting U taint flag.
Jan 3 14:21:12 LSSUSE-01004839 kernel: snd_ac97_codec: module not supported by Novell, setting U taint flag.
Jan 3 14:21:12 LSSUSE-01004839 kernel: snd_intel8x0: module not supported by Novell, setting U taint flag.
Jan 3 14:21:31 LSSUSE-01004839 kernel: snd_seq_device: module not supported by Novell, setting U taint flag.
Jan 3 14:21:31 LSSUSE-01004839 kernel: snd_seq: module not supported by Novell, setting U taint flag.
Jan 3 14:21:31 LSSUSE-01004839 kernel: snd_mixer_oss: module not supported by Novell, setting U taint flag.
Jan 3 14:21:31 LSSUSE-01004839 kernel: snd_pcm_oss: module not supported by Novell, setting U taint flag.

Some tidbits:

Kmix is running:

Master and PCM are both at 50%+, so that isn't the problem.

In yast, it shows as installed, and under the hardware probe it says it is active.

What can I do other then re-installing to get my sound back? Would I have to possibly recompile my Kernel?

EclipseAgent 01-03-2006 05:36 PM

Here is the output of the ls for my /dev/dsp

ls -L -l /dev/dsp*
crw-rw----+ 1 bkevan audio 14, 3 2006-01-03 15:17 /dev/dsp

Dominique_71 01-03-2006 05:51 PM

You can try alsaconf in the console. It will reconfigure the soundcard. But I am not sure if it will work. It look like a Suse issue, not an alsa issue.

I always compile my own kernel. It is many things I don't need in the suse kernel, and it is very easy to change the family processor in order to get a faster kernel. In most case, you can even remove the generic x86 option. A good thing to do is to change the extra version of the kernel, so you will get a new modules tree in /lib/modules. (It is an option in the config menu for that, or you can edit the Makefile, it is the line 5 if I remember well.).
By doing this, you still have the original kernel in case of problem with the new one.

When using initrd, I prefere to run "mkinitrd -k <kernel-name> -i <initrd-name>" at the place as just "mkinitrd" as sugested in the SuSE manual. "mkinitrd" on suse will do an initrd for each single kernel in /boot, and it is no need for that. "man mkinitrd" is your friend.

EclipseAgent 01-03-2006 06:05 PM

Ok,

As sad as this is going to sound, I found the problem. Although I am getting the errors above, I created a new group called clamav for the clamav software, and my user was a member of it, and not a member of the "users" group.

I changed my access to be in "users" and not in clamav, and all seemed to work just fine. I also gave my user some other group access, but I think it is just the "user" one that really mattered.

So yeah.. for all the people reading this, make sure you are in the right group. I also added my user to the "Audio" group.

W

EclipseAgent 01-03-2006 06:07 PM

Quote:

Originally Posted by Dominique_71
You can try alsaconf in the console. It will reconfigure the soundcard. But I am not sure if it will work. It look like a Suse issue, not an alsa issue.

I always compile my own kernel. It is many things I don't need in the suse kernel, and it is very easy to change the family processor in order to get a faster kernel. In most case, you can even remove the generic x86 option. A good thing to do is to change the extra version of the kernel, so you will get a new modules tree in /lib/modules. (It is an option in the config menu for that, or you can edit the Makefile, it is the line 5 if I remember well.).
By doing this, you still have the original kernel in case of problem with the new one.

When using initrd, I prefere to run "mkinitrd -k <kernel-name> -i <initrd-name>" at the place as just "mkinitrd" as sugested in the SuSE manual. "mkinitrd" on suse will do an initrd for each single kernel in /boot, and it is no need for that. "man mkinitrd" is your friend.

Yes, before I found the silly problem of the groups, I did run Alsa Config and still experienced the same problem.

I am considering compiling my own kernel, and I have virtual machines to test that on :)

I did do this though:

make xconfig (made no changes)
make all
make modules_install

Just to see if it would just refix any of my things but it didn't.. and like I said above.. it was the stupid groups.


All times are GMT -5. The time now is 12:19 AM.