SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I just finished compiling my first new kernel(Yay! ). Now I want to try and go back and take out what I don't need. I know I have a lot of stuff compiled in that I will never use.
Before I do this, though, I was wondering if I uncheck a setting and then compile it and it doesn't work. I know I can use the kernel before the new one to boot, add that setting back into my kernel. But when I compile it, can I just run make to compile the new setting or do I have to run mrproper, to clear all the stuff from the old compile and recompile the entire kernel again? I noticed one time I ran make without mrproper and it went by really fast, but I wasn't sure if it created what I needed or not.
A lot of this depends on several things. Oh, and be careful, 'make mrproper' deletes your kernel config too.
On 2.4 kernels, it was generally considered that a 'make clean' was really needed before rebuilding. With 2.6 kernels, the dependency tracking has been greatly improved, and a 'make' should be fine. Makes after the first should be faster, because source files with no configuration changes don't need to be recompiled: the existing object files (file.o) can just be linked into the final version.
Awesome, that's really good to know. Heh, I must have forgotten to mention in my first post that the kernel I compiled was the 2.6.13.1 kernel. But it looks like I have to go back to a 2.6.12 kernel in order to get my damn ATI drivers working :-\. It's more practice I suppose.
Which ATI drivers are you trying to use? The Xorg or XFree ones, or the proprietary ones written by ATI?
And yeah, mentioning a kernel version in a thread about compiling a kernel might be helpful. *grin* But I answered it for both version to help future searchers/readers.
I am trying to get the proprietary ones from ATI to work. Unfortunately it is not going too well. I finally got Xorg to start, before it would not even start, it just froze. However, when I run the glxgears test program I get about 2000FPS(not sure if thats good or not).
When I run the fgl_glxgears test program I get about .663 - .8 FRS. (That is less than ONE FPS). The fgl_glxgears program does give me this error over and over and over as it runs:
Code:
FGLTexMgr: open of shared memory object failed (Function not implemented)
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
fglX11AllocateManagedSurface: __FGLTexMgrCreateObject failed!!
I am not sure what that means, maybe someone else could help? I installed the latest ATI drivers and I am using kernel 2.6.12 and Xorg 8.6.2.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.