No sound after recompiling kernel

hylke · 12-27-2004, 05:46 AM

Hello
Yet another thread about losing sound after recompiling kernel :-)
Ok, so my problem is that i lost sound after recompiling my kernel(cus i wanted dev fs support).
What i did was:

Code:

make menuconfig(i added devfs)
make dep
make clean
make bzImage
make modules
cp arch/i386/boot/bzImage /boot/newkernel
make modules_install

After that i reinstalled my nvidia driver and rebooted.
But when it loads kde, it says something like:
Sound problems
Can't open /dev/dsp using NULL
So i tried to run alsaconf but then it says:

Quote:

No supported PnP or PCI card found.
Would you like to probe legacy ISA sound cards/chips.

So i want out checking and i'm pretty shoure i have PCI(saw something with PCI in it in the make menuconfig thing)
When i type alsamixer i get:

Quote:

alsamixer: function snd_ctl_open failed for default: No such device

So i went out searching and found similar things like that, but they were talking about alsa module and shit like that, but i can't find anyt alsa thing when i run make menuconfig.
So anybody got an idea how to get my sound working again?
Thanx Hylke

__J · 12-27-2004, 05:53 AM

Do you know what kind of sound card it is? If not in a terminal run "lspci" and if it is a pci card it should list in the output of that. From that information you should be able modprobe the driver into the kernel and modify /etc/rc.d/rc.modules to automatically load it at each boot.

hylke · 12-27-2004, 05:58 AM

I know that the sound-card is onboard.
My mother board is a albatron kx600, if im right.
My output of lspci is:

Quote:

00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400/KT600 AGP] Host Bridge (rev 80)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge
00:0d.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78)
00:10.0 USB Controller: VIA Technologies, Inc. VT6202 [USB 2.0 controller] (rev 80)
00:10.1 USB Controller: VIA Technologies, Inc. VT6202 [USB 2.0 controller] (rev 80)
00:10.2 USB Controller: VIA Technologies, Inc. VT6202 [USB 2.0 controller] (rev 80)
00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C/VT8235 PIPC Bus Master IDE (rev 06)
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
01:00.0 VGA compatible controller: nVidia Corporation: Unknown device 0314 (rev a1)

And if im right my soundcard had something to do with VIA.
And what do i need to modprobe?
thanx Hylke

artistikone · 12-27-2004, 09:58 AM

Try modprobe snd-via82xx

shepper · 12-27-2004, 12:56 PM

If you are running the 2.4.x kernel series you will need to reload the alsa-drivers. This package inserts the
sound modules into the 2.4 kernel series. A newly compiled 2.4.x kernel will not have the alsa sound modules.

In the 2.6.x kernel series the old oss modules were deprecated and the alsa sound modules made standard.

aeNeo · 12-27-2004, 09:09 PM

Reinstall the alsa driver...that should work.

hylke · 12-29-2004, 03:32 AM

Ok, thanx you all.
That was the problem.AFter reinstalling alsa everything went fine.
Hylke

mcd · 01-27-2005, 05:15 PM

i have a sort of general question, which is that i don't fully understand how modules are dealt with by the kernel. i have recompiled a few kernels, and i understand that process alright i think, meaning that i know to make modules and make modules install, which creates a directory called /lib/modules/kernel-version, and i understand the difference between building something into the kernel and including it as a module. but here's my question:

i only have one /etc/rc.d folder, which means i only have one /etc/rc.d/rc.modules file. as i understand it, this is the file that determines which modules are inserted at boot time. right? so i opened up /etc/rc.d/rc.modules and at top it says that it looks for modules in the /lib/modules/kernel-version directory. fine. but there is only ONE rc.modules script....so what if you want to be able to boot multiple kernels on one machine? say in 2.4.26 i had my ethernet card driver built into the kernel, but in 2.6.10 i wanted it included as a module. if i DIDN'T edit the rc.modules script, my ethernet wouldn't work until i insmod the driver, right? and if i DID edit rc.modules then BOTH kernels would try to insert that module regardless of the fact that 2.4.26 didn't need it....

is this correct?