Welcome to the new location of Alien's Wiki, sharing a single dokuwiki install with the SlackDocs Wiki.
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
wiki:talk:linux:kernelbuilding [2006/05/16 11:25] – created alien | wiki:talk:linux:kernelbuilding [2016/12/30 13:50] (current) – old revision restored. alien | ||
---|---|---|---|
Line 3: | Line 3: | ||
Feel free to comment on this Wiki page. Do you have suggestions to make it better? Critical remarks? Leave them here. | Feel free to comment on this Wiki page. Do you have suggestions to make it better? Critical remarks? Leave them here. | ||
- | Eric | + | |
--------------------------------------------------- | --------------------------------------------------- | ||
+ | |||
+ | >Are you sure merging the xauth is neccesary? I tried it and had to step out for a minute. Gnome locked the screen automatically and since then X hasn't worked, and I get an error saying "error in locking authority file / | ||
+ | | ||
+ | |||
+ | Hi David - I guess you did the merge while you were in X, then? The safe way would have been to do this in a console... before starting X.\\ The fact that it is not mentioned in other manuals and faqs does not mean it does not work :-)\\ As for your problem - look at the ''/ | ||
+ | --- Eric | ||
+ | |||
+ | --------------------------------------------------- | ||
+ | |||
+ | > Found typo: '... a X terminal...' | ||
+ | But did it really need **six** revisions of your feedback line to tell me this :-) That is what the '' | ||
+ | --- Eric | ||
+ | |||
+ | So sorry about that. When it comes to editing: can't help meself, mate :) | ||
+ | |||
+ | --------------------------------------------------- | ||
+ | |||
+ | >Spotted a formatting typo. Look under **Modifying lilo.conf** | ||
+ | > | ||
+ | >The first code block in the section says: < | ||
+ | label = linux read-only # Non-UMSDOS filesystems should be mounted read-only for checking | ||
+ | </ | ||
+ | label = linux | ||
+ | read-only | ||
+ | </ | ||
+ | > | ||
+ | >Perhaps a rogue < | ||
+ | > | ||
+ | >Nice guide Eric. Thanks for the rest of your good work too. I appreciate you highlighting the point Linus made (the infamous /usr/src ' | ||
+ | > | ||
+ | >However I still think Linus has a point. If nothing else, juggling chainsaws when you're tired, and you've done it a million times before, **could** be hazardous to your health ;-) | ||
+ | > | ||
+ | >- mjc - | ||
+ | |||
+ | Thanks for spotting this mjc, I fixed it. The kernel sources location is a hot topic on [[http:// | ||
+ | --- Eric | ||
+ | --------------------------------------------------- | ||
+ | --------------------------------------------------- | ||
+ | Hello Eric/Alien; | ||
+ | |||
+ | Thanks to this guide, I ' | ||
+ | |||
+ | The nvidia self-compiled kernel wasn't gathered from the 'check your other compiled modules' | ||
+ | |||
+ | It's obviously arch-stupid of me to have forgotten about this one, what with the nvidia logo popping up in my face every morning, but a warning to keep some sources at hand in some particular cases may come handy. | ||
+ | |||
+ | As examples that come to mind, there is the Proprietary graphic drivers like ATI or NVIDIA and the VirtualBox module. | ||
+ | |||
+ | I am suggesting, if my system wasn't wrong and if it is normal for the new kernel to struggle to get to X with an Xorg.conf claiming for a proprietary module from an older kernel, that you edit the relevant part more or less like this: | ||
+ | |||
+ | ---- | ||
+ | |||
+ | | ||
+ | |||
+ | Most certainly you will have packages installed that contain kernel modules that are not part of the default | ||
+ | | ||
+ | | ||
+ | Now, with the installation of your new kernel, you will lose these modules, and you have to recompile the | ||
+ | | ||
+ | |||
+ | You can get an overview of some packages that have installed a kernel module for your current kernel by running | ||
+ | this command (i.e. you must run this command while still running your old kernel): | ||
+ | |||
+ | > cd / | ||
+ | > grep -l " | ||
+ | |||
+ | // | ||
+ | |||
+ | The mentioned packages will need a recompile, which isn't a chore unless for your graphic driver since you | ||
+ | will end up in a terminal, with X respawning in a loop, upon your first reboot. Be sure to have your driver' | ||
+ | | ||
+ | | ||
+ | |||
+ | For ALSA you have a choice: either enable the ALSA driver that is part of the kernel you've just downloaded, | ||
+ | or leave the kernel configuration like Slackware' | ||
+ | | ||
+ | they will not work with the ALSA driver releases you can install separately. | ||
+ | |||
+ | ---- | ||
+ | |||
+ | That's it, thank you & sorry for the bother/ | ||
+ | |||
+ | ---- | ||
+ | Hi Jean-Philippe. \\ Good idea there, I've added a clear warning sign in that section. Thanks, \\ | ||
+ | --- Eric | ||
+ | |||
+ | |||
+ | ---- | ||
+ | |||
+ | Hi Eric, | ||
+ | |||
+ | Text under the " | ||
+ | |||
+ | Thanks for the article. | ||
+ | |||
+ | --- Dan 2011-08-05 | ||
+ | |||
+ | -------------------- | ||
+ | **Kernel key ID ended** | ||
+ | |||
+ | Hi Eric, | ||
+ | |||
+ | the kernel key ID is changed. In the square, you write 0x517D0F0E, but it's ended. Now it's 6092693E. | ||
+ | |||
+ | Regards | ||
+ | |||
+ | Davide | ||
+ | -------------------- | ||
+ | Hi Eric, | ||
+ | |||
+ | it's always a good idea to do a "make mrproper" | ||
+ | |||
+ | Regards, | ||
+ | |||
+ | Heiko |