It would be best to use modules. That way you can load them with options and also get info about them when you try to load them.

I am a bit lost at this point as to what has been done

Here are a couple of things I would suggest.

If you are installing a new kernel use make install as the last step. Then there is no need to copy anything or edit the lilo.conf file as long as it installs correctly by running lilo as we determined earlier.

Use the menuconfig or xconfig tool instead of trying to edit the config file manually.

The thing I can't figure is why the basic kernel does not work.

It supports SB Live out of the box. Maybe if you could try the current Mandrake 9.2 kernel again and let us know what the details are it would shed some light on the problem.


You may be able to run sounddrake and set it to emu10k1

Installing the mdk 9.2 kernel again was what the repair did for me, but upon entering into mdk it gave me a no sound card server error. MDk CC sees the soundcard, but when I try to run the config tool it denies existence. (specifically: The ** driver for your sound card is unlisted.) But when I try to find an update or whatever to get the damn emu10k1 it does not seem to exist except in the new ALSA which I cannot get to function.

How do I run sounddrake??

Oh yes, as I had mentioned waaaayyy back, somewhere during my first attempt at compiling, I had downloaded a kernel source and for some odd VERY ODD reason that I did not even pay any attention to, rpmdrake decided it was necessary to UNINSTALL or REMOVE my orriginal kernel. Being the dummy I am I just said OK and it did so along with installing the kernel source. Then all hell started.

can you get the latest mandrake supported kernel rpm and boot that see if it works.

You will probably need to configure your sound card once it boots. YOu should have a program called sounddrake installed

Maybe what happened was my non-expert trust in mdk offering so much software including more than 5 kernels and additional sources which caused me to blindly download and install 4 precompiled kernels along with 3 kernel sources. One kernel source was the source for one of the precompiled ones and the othe rtwo were for othjer kernels that I thought I would try after I learned how to do the first one.

I am not sure if what I just said makes any sense, for that matter is what I did made any sense either, but all apparrent things that occurred later gives me the idea that ALL OF THE KERNELS BECAME ONE! Even though they were addressed with their own ID, when I examined all the config files for each one, THEY WERE EXACTLY THE SAME!

Except for the sources that I did not touch, all the precompiled kernels became exactly like the source I was working on. So when I somehow lost my sound system in th esource, I lost it everywhere else as well. HOWEVER; while the config in the other two sources had not changed, when I attempted to compile one it would not compile at all. It kept giving me insufficient arguments errors. I even attempted to YES everything and it gave the same error.
________________________________________________________________________
So, I freaked out, erased my hard drive and totally installed mdk 9.2. MY GOODNESS!! NOW I HAVE MY SOUND and it is BETTER THAN BEFORE!!
________________________________________________________________________

Here is my non-expert, but sudden experience THEORY.
1. TOO MANY KERNELS!
2. MDK 9.1 WILL NOT MIX WITH MDK 9.2!!
So while an update from 9.1 to 9.2 works beautifully, a lot of programs do not function properly if at all. Especially when you try to update them further. Code from 9.1 is refused by parts of 9.2 adn updates for 9.2 especially. RPMDRAKE used to remove the oudated stuff and then install, but now it just complains and refuses. There even appears to be some 9.1 programs in 9.2 that are even now giving me problems in that rpmdrake will not update them due to conflicts.

So the kernel idea might have worked if I only had a source and perhaps a pre-compiled kernel, but I am guessing because it did not work anyway. The important thing now is that I have my sound, and everything else is pretty cool right now, but I am trying to finish the install by getting the damn updates and rpmdrake has already refused, two cdburner programs, some system packages, and a bunch of libs such as libs for Aikasauras.

FOR NOW, I am not going to work on any kernel source, in fact, I only have a kernel on here. Although, THAT IS ANOTHER PARTIAL ISSUE. I did wish to update my kernel from 2.4.22-10 to 2.4.22-21 and rpmdrake won't even do that. GO FIGURE?? The install was better with 9.1, but failed afterward, now 9.2 won't update properly. hmmmmmmmmmmmmm???? I will be patient for now, but I hope they do something soon, I cannot even get KONQUEROR.

That sounds very strange.

It almost sounds like one of the install cds has a problem.

I have only tried a couple of Mandrake versions, they installed fine. There was a problem with their updates that I had which was related to the update servers not having all of the files. I had to keep retrying different servers until I got it updated.

That's been a while back so I guess maybe that should be corrected, but maybe it's not.

FWIW, it's been my experience with Mandrake that all the tools that let it automaticly configure your machine make it harder to do things by hand. I generaly tell new users of Mandrake to not venture beyond what you can do with GUI interface. I used Mandrake for about 3 months and finaly became so frustrated at my inability to manualy configure anything that I switched to Slackware and haven't looked back. If you want to do a lot of fiddling around with compiling your own kernels and tweaking your system, Mandrake is not the best distro to use, imho.

It seems that you could compile the latest kernel from kernel.org and it would work. However this is not usually the case. It is hard to get things right in the config the first couple of times around.

I would strongly suggest keeping the recent kernel supplied by the distro unchanged as a backup.

Boot into the distro specific kernel and cd into your source for your new kernel.

then do this..

make mrproper oldconfig menuconfig dep clean bzImage modules modules_install install


I have had the best success using that proceedure. If you know your system well enough you can just skip the make oldconfig.

There are some changes that if you run oldconfig you will need to answer some questions but the basic configuration will be maintained.


Don't change a lot of stuff at once. Save your configs and make notes about how they work.