Slackware Walkthrough for kernel 2.6.12.4 from kernel 2.4.29
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.
Slackware Walkthrough for kernel 2.6.12.4 from kernel 2.4.29
This is a walkthrough for updating the kernel on slakware 10.1 kernel 2.4.29 to kernel 2.6.12.4 the newest stable version at the moment. i have downloaded the kernel from the www.kernel.org site. For newbs like me you have to find the mirror that has the DL available....
next step: i have read everything from "how to's" to "this is how's".... almost none of it makes sense!
for now the answer is unresolved. from the README once kernel is untarred i get that we need to NOT put the kernel in the usr/src/DIRECTORY
to untar the .gz file type: command in the directory of choice.
tar -xvzf linux-2.6.12.4.tar.gz
for bz formats i beleive its: tar -xvjf linux-2.6.12.4.tar.bz2
onced the tarred file is untarred you then have to ....this is where i am confused....... i gather from the README that i have to make menuconfig and then compile the kernel. i went in and read the help on each and every one of the options. WOAH!!!! that took a long time. choose what suits your fancy and then continue on. this is the exact point that i am stumped on. some help me's state that i have to give the kernel a symbolic link to where the kernel is at, others like the one the kernel comes with, state that i do not need to do such things but to go ahead and install the kernel in the usr/src/xxxx directory. which one is right or are both right? any help will hellp me put together this WALKTHROUGH for other helpless noobs like me.
BAHHHH!!!!!!!!!!!!!!!ARGH!!!!!!!!!!!!!!!!!!!!!!!!SHEEZ!!!!!!!! u gotta luv it....
From a pragmatic point of view, it looks like you don't even want to attempt to upgrade that way. It looks like you want to find the newer version of Slackware that comes with the 2.6.12.4 kernel. Then, you probably want to install that newer version on a separate partition and try it out before you begin depending on it.
From what I have seen, when you make that great a change in kernels, you might also need to change a lot of other things in your system as well. As you might guess, those other things that you might need to change are not documented. You find out about those other things when you boot up with the new kernel and your system doesn't work properly.
Please calm down, I will try to give you some hints that worked for me when compiling the latest kernel in Slackware 10.1
From your post I discern that you already compile the kernel using
make menuconfig
make
make modules_install
if that is the case you have almost finished, what remains to use your new kernel is the following
1. copy your new kernel to the boot directory
assuming you are in /usr/src/linux (cp arch/i386/boot/bzImage /boot/kernel-2.6.12.-4)
2. copy the system.map
(cp System.map /boot/System.map-2.6.12.4)
3. copy the configuration
(cp .config /boot/config-2.6.12.4)
4. update your boot loader (lilo or grub), in either case you must review carefully that lilo or grub is pointing to your new kernel
Anyway, I suggest you to read the following explanation, I used it and it helped me a lot:
Also, you will most likely have to recompile alsa also. Perhaps, if you are able, you can just use the /testing/ kernel provided by Slackware http://www.slackware.at/data/slackwa...inux-2.6.12.3/ <--yes, you are trying to do .4, but that should be released by the slackware team soon ;P
well everyone i thank you extensively for your help on this matter. as for my quote it is meant to be just a joke.... a buddy and i were just joking about how much you have to get through to make things just right. it came to mind and viola i changed my quote. no biggie.... again as for your help it is greatly appreciated. the xushi.co.uk link is proving to be absolutly wonderful.... i am doing it step by step and will post resultys. thanks everyone... hopefully i will typing this next reply in 2.6.12.4... till then...see ya...
hello all the moment that ihavd been waiting for has now arrived. i am currently running the 2.6.12.4 kernel succesfully. alot of things work on my system now such as my wireless mouse that previously did not work. so now i have the ability to finally use the mireless mx700 duo that i had. no more dealing with 2 mice anymore. pheww... that is a relief. all i did was follow the guide that xushi had on the earlier post. line by line. DL and install pkg, so on.....everything is working great except that sounds is now gone. i had alsa running b4 now it gives me some errors. i love my xmms so i would like to get it back. lol....
i tried the lsmod |grep snd and it just goes back to command promt.... still no sound.... when i go to my xmms it tells me to check that my soundcard is configured correctly, i have the correct output plugin selected and that no other program is blocking the soundcard... i am not sure what i did to mess up the prev settings but alsa was working when i was on the 2.4.29 kernel. is it possible that i messed up the modules dealing with alsa? if so can i fix it without having to recompile the kernel?
Last edited by silverdrgn; 08-15-2005 at 04:20 PM.
welll...i forgot to ask: did you make the alsa stuff as modules,
or did you compile it into the kernel. ?
i always make them as modules.
to be sure do a " modprobe -l |grep snd ".
if there's no output, the modules are not there or alsa is compiled in the kernel.
( ...or you forgot to mark the alsa items in xconfig )
ok i see the prob module that you stated is trouble.... removed it. also i dont know how to make files executables. my freind told me how when i first got slack on my box. i never used it so i forgot...(sorry) i feel that once i get alsa working everything wil b just fine. uh oh im being summoned by the wife. b right backk...
Last edited by silverdrgn; 08-15-2005 at 05:46 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Slackware Walkthrough for kernel 2.6.12.4 from kernel 2.4.29
guys guys guys c'mon.......
on 2.6.12.4 and LUVING IT
well guys i'll b back later if the wife allows me to play
