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.
Hi Everybody, i have made a tutorial for a 13.37 Kernel Upgrade at http://2012revolution.us/doku.php?id=start , let me know what you think!!! i can help and add to the tutorial along the way, and dont be afraid to comment to the wiki! Thanks!
-Phillip
Hi Everybody, i have made a tutorial for a 13.37 Kernel Upgrade at http://2012revolution.us/doku.php?id=start , let me know what you think!!! i can help and add to the tutorial along the way, and dont be afraid to comment to the wiki! Thanks!
-Phillip
Hi. Well done for making an effort. A couple of observations:
I'm not sure that who the target audience in terms of skill level, but if this is aimed at beginners they should be advised to verify the kernel tar ball before compiling. On overview of the stages at the beginning would also be good, as would some references and more detailed explanation of what each stage is for.
The lack of initrd implies that you are building from the huge config. You might want to address this in the guide, as it is arguably better to build from a generic config.
It's your computer so you can build the kernel where you like, but I'm wondering why you don't use /usr/src as that's where the kernel sources are by default.
Nice work.
As kristizz said why not compile in /usr/src ?
However:
Quote:
Lets do a…
root@darkstar:~/kernel33/linux-3.3-rc6# cp -v arch/x86/boot/bzImage /boot/vmlinuz-linux3.3-rc6ro3/linux-3.3-rc6
What we just did was copy the bzImage which is your New kernel to your /boot/ directory.
Hi Everybody, i have made a tutorial for a 13.37 Kernel Upgrade at http://2012revolution.us/doku.php?id=start , let me know what you think!!! i can help and add to the tutorial along the way, and dont be afraid to comment to the wiki! Thanks!
-Phillip
You do not need to be root to compile a kernel.
I repeat: You do not need to be root to compile a kernel.
I do not understand why people believe this.
Please, please, please read Linux Kernel in a Nutshell. It was written by Greg Kroah-Hartman who is a kernel maintainer.
all very good feedback and very valid, but with that said, thanks for the laying the foundation of a user guide for upgrades, it will only get better now that you have laid the foundation
wget "http://www.kernel.org/pub/linux/kernel/v3.0/testing/linux-3.3-rc6.tar.bz2" -O - | tar vxj ; cd linux*;cp /boot/config*huge ./.config;make&&make modules&&make install&&make modules_install;reboot
one line to rule them all
While it is true that root is not required to build the kernel and the official README says
Quote:
To do the actual install you have to be root, but none of the normal
build should require that. Don't take the name of root in vain.
I still side with salemboot: it is kind of easier. It also seems to be the Slackware way, judging by slackbuilds.
I have to point out, though, that skipping make oldconfig may cause you to have a bad time. In one instance I forgot to do it and still was able to boot a misconfigured kernel. Super-glitchy graphics gave away my mistake, so I fixed it, but who knows what else was broken?
Also, in my latest attempt to bring custom kernels to multiple desktops and laptops, I wrote a kernel slackbuild script. It is an amalgamation of the official Slackware scripts for kernel, modules, and firmware. You still have to configure the kernel (which is by far the hardest part), but then you can follow my very easy README and make a package which can be used to upgrade kernel/modules/firmware in one fell swoop, as simply as
Quote:
installpkg <name>
lilo
You also benefit from being able to uninstall your custom kernels cleanly and quickly. One major caveat is my refusal to deal with initrd: since I am already making my own kernel, I can easily throw in whatever it needs to boot (in my case, just ext4).
qweasd, looks like you're doing something very similar to me. I also have a combined kernel+modules SlackBuild script I use. I still use a separate package for firmware though. (currently the one from current)
I thought about adding a "mkinitrd' to the doinst.sh, but at the moment I still do that bit and lilo manually.
elvis, thanks for the link...just finished reading it, good info in there and was nice to hear from an official kernel developer to build in a user created directory and not in /usr/src like everyone says
I still use a separate package for firmware though.
Starting with 144, udev looks in /lib/firmware/$(uname -r) and then /lib/firmware. So there is a very clean way to install the correct firmware without colliding with the Slackware package.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.