Here is me, helping you even though you clearly have way too much attitude.

Did you even follow my last set of instructions? If so, you would have realized that you are probably loading arch/i386/defconfig. Well, let's think about this for just a second. Why would that file have stuff that is gonna work for you? It clearly does not. Have you ever had a kernel work for you? Which one? From your rambling posts jfs.s works for you. Load that config!!! If you don't have a copy of the stock Slackware config file for jfs.s, then just go to any Slackware mirror and find it. Another big hint, it's called kernels/jfs.s/config.

Now you are starting with something that works for your system. Breaking that is 100% up to you.

Note that none of this really matters. You can also just make all the right choices when compiling your kernel. I've already made a lengthy post about all the options that I chose in the past called "Something for kernel compilers". Use the search function to find it. It's all about the very thing that you claim no one has ever covered. How to make all the right choices when compiling your kernel.

Here's another trick. From the linux kernel source directory, remove .config (since it doesn't work anyway). Now, copy over a working config to .config (again, for you that would be the config for jfs.s). now type "make oldconfig". It will only ask you questions about options that weren't available in the 2.4 kernel but now are. There are usually less than 20. "?" is the most useful answer. When you are all done, then "make xconfig" for any fine-tuning.

Note you have other issues. Namely, you are somehow not being prompted for kernel selection at boot time. You should figure out why, since it has been covered ad naseum on this forum. Then, when you mess up a kernel compile, you won't have to re-install.

Goddamn! IT IS CALLED "X Window"!!!

Read them and I have to say I am very leary of even considering this now. Your help has been top notch, be sure. Now, yes, I have had it work one time, oddly I forgot the NIC in it and ever since I redid it the very same way I get these errors, and I have tried all the different Tulip drivers, they don't work well. So I am waiting for my 3Com card to come, then I will try again. Be sure I read it all, took the time and re read it again, just to be sure. The errors come from something else, not me, or how I do this. I do not even get past the compile stage now. I get the errors and ctl c out of it, and delete the whole thing.



Probably true.



Since the last episode, I am not using jfs.s anymore, I am using bare.i and had to do a trick to even get to boot without the floppy. Some reason the lilo.conf file would not write properly so it made me use the boot disk. I cheated and fixed it.

so when I get my New NIc then I will go on and try it again, I know now it seems to have something to do with my nic. Thank you for your ever so well behaved patience. I know I have not been very good about this, but I honestly have read everything at least 4 times for surety. Just so I would not have to go through this too, yet here I am. Once again, Thank you.

BenneJezzerette - as requested by a few people in the "This Is How I Do It All" thread, your posts have been split off into this new thread.