I'm running Slackware 10 and after re-compiling the kernel I ended up with no mouse, no NIC, and no sound. It worked perfect before this recompiling.

I have since managed to get my NIC working, but for the life of me the mouse and sound will not work.

I have tried my USB mouse and a PS2 mouse, nothing. The sound card is SB16 Virbra. It loads and when booting it says it detects it, but when I run alsaconfig, it says it can't find it.

Any help is appreciated, especially for the mouse.

If you need any further info, let me know and I can try and post it.

Thx

What kernel version did you have before, and what is the new kernel version you are running?

Did you compile in the drivers for those devices in the kernel or as modules?

The 2.6.x kernel has built in support for alsa now.. no need for the alsa packages.. though the alsamixer is a nice lil program to use still.

Only thing I can think of as of why your ps/2 mouse isn't working is that you didnt compile support for it in the kernel, that or you pluged it in after the system booted.

I has the same problem before when I compiled kernel-2.6.11.11 on Slackware 10.1.
At that time I forgot to select the modules for my sound card, ALSA, PS/2, and SCSI since I was new to kernel compilation. Compiling the kenel again with those modules solved the problems. After compiling the kernel I had to run alsaconf as root for the sound to work and edit /etc/X11/xorg.conf for my mouse wheel.

The kernel is the same after recompiling (2.4.??), and everything is that's needed is there. I have recompiled 5 times now trying to get this to work. I've tried as modules and compiled into the kernel.

So why does this happen??

The sections to do with my mouse, sound, and NIC were not touched when I originally recompiled - I basically just removed unneeded stuff, like infrared, pcmcia, etc., and added a dew things.

I can see a reinstall coming, as is usual with whatever OS is involved. It's quicker than trying to troubleshoot an idiotic problem like this.

Any further help is appreciated.

First let me ask you: Do you still have the first kernel that works? And do you still have the /boot/config-2.4.* or /boot/config or possible the /usr/src/linux/.config file that has all the "working kernel config" information still in it?


If so ... unarchive the new kernel you wish to build or run the appropriate commands to clean the source directorys (look in doc for this ... cant member at moment) then copy the config into that directory so its /usr/src/linux-2.6.*/.config needs to be [dot]config .. then when u run make menuconfig or any other config program you will have all the original working configurations set in there already. Now you can go through and carefully start taking parts off you dont need or want.


You should always keep the old kernel and .config files incase this happens. You should at least have two kernels in your /boot directory. The original kernel you installed with and your testing kernel. That way when the testing one fails you can reboot back with the original and fix.

If your upgrading from a 2.4.x to a newer 2.4.x series .. it woudl be ALOT easier (far as sound goes) to just go to the newer 2.6.x series. Ive always had trouble with sound and its one thing I hate dealing with in linux but since the 2.6.x series it has never even been a problem. I had more trouble setting up my 5.1 sound in xp (which took a hour) than linux (bout 10 secs).