make modules_install kills sound?
Hello, Last Friday I compiled a new kernel to add framebuffer support on my SuSE 8.0 system. I have been running vmlinuz-2.4.18-4GB. I did a "make bzImage modules modules_install" but before installing the new kernel, I had to shutdown the machine so my computer room could be used as a guest room. When I rebooted on Sunday, sound would not start up, and I get the error message "could not find snd-sb16". (I have a Creative Labs SoundBlaster16 card installed.) I tried to fix this by running alsaconf, but it too complains that it can't find snd-sb16. Yast2 also would not configure sound, giving me an error message indicating that the module was not found or the IRQ was incorrectly set. Using find, I tried searching for snd-sb16.*, but it is not found. A reinstall of all things alsa also did not work. Can someone offer me a clue as to how to get sound working again on my box? Thanks, Sean Theo. Sean Schulze theodore.schulze@us.army.mil
Last Friday I compiled a new kernel to add framebuffer support on my SuSE 8.0 system. I have been running vmlinuz-2.4.18-4GB. I did a "make bzImage modules modules_install" but before installing the new kernel, I had to shutdown the machine so my computer room could be used as a guest room. When I rebooted on Sunday, sound would not start up, and I get the error message "could not find snd-sb16". (I have a Creative Labs SoundBlaster16 card installed.)
I tried to fix this by running alsaconf, but it too complains that it can't find snd-sb16. Yast2 also would not configure sound, giving me an error message indicating that the module was not found or the IRQ was incorrectly set. Using find, I tried searching for snd-sb16.*, but it is not found. A reinstall of all things alsa also did not work.
Can someone offer me a clue as to how to get sound working again on my box?
this could be one of two things that i can think of, both of which have the same effect: if you are upgrading your kernel to a new version, a new /lib/modules subdirectory is created for the new kernel. alsa is not actually part of the 2.4 kernel (got merged in 2.5) so you need to download the modules from http://alsa-project.org and install them. if you are recompiling the default suse kernel, the modules_install part of the make process cleans out the old modules before installing the new ones. you need to re-install the alsa drivers either by downloading the drivers as above, or re-installing the rpm that comes with suse. any time i recompile my kernel for whatever reason, i have to re-install the kernel modules for both alsa and my nvidia card. quick and simple, just one more thing i have to remember. -- trey
The 03.04.30 at 14:22, Trey Gruel wrote:
if you are recompiling the default suse kernel, the modules_install part of the make process cleans out the old modules before installing the new ones. you need to re-install the alsa drivers either by downloading the drivers as above, or re-installing the rpm that comes with suse.
To avoid that, just edit the Makefile, and add something to "extraversion". Thus, your compiled module tree will go to something like "/lib/modules/2.4.19_CER-4GB/" instead of the default "/lib/modules/2.4.19-4GB/", for example. Also, you need to adjust grub or lilo accordingly. -- Cheers, Carlos Robinson
if you are recompiling the default suse kernel, the modules_install part of the make process cleans out the old modules before installing the new ones. you need to re-install the alsa drivers either by downloading the drivers as above, or re-installing the rpm that comes with suse.
To avoid that, just edit the Makefile, and add something to "extraversion". Thus, your compiled module tree will go to something like "/lib/modules/2.4.19_CER-4GB/" instead of the default "/lib/modules/2.4.19-4GB/", for example. Also, you need to adjust grub or lilo accordingly.
that would pretty much take hime the same path as installing an all new kernel. either way, he would have to re-install the alsa driver modules. -- trey
The 03.05.01 at 10:02, Trey Gruel wrote:
To avoid that, just edit the Makefile, and add something to "extraversion". Thus, your compiled module tree will go to something like "/lib/modules/2.4.19_CER-4GB/" instead of the default "/lib/modules/2.4.19-4GB/", for example. Also, you need to adjust grub or lilo accordingly.
that would pretty much take hime the same path as installing an all new kernel. either way, he would have to re-install the alsa driver modules.
Yes, but just once, and never again: the idea is to have two modules trees, one for the original Suse kernel, and another one for your modified kernel. Your own will not overwrite nor delete the original. And, I think, the kernel may be able to load the original if not included on yours. Another thing, is that modules from different packages, like sound, could be moved to ../misc instead of ../kernel, and then they are not overwritten. I did that once. -- Cheers, Carlos Robinson
participants (3)
-
Carlos E. R. -
theodore.schulze＠us.army.mil -
Trey Gruel