SUSE / openSUSEThis Forum is for the discussion of Suse 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.
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.
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?
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.
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.
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.