beatlejuice321,
I can answer this for you, however I don't have time just yet, as I'm about to go into work. When I get home, I'll post up an answer. Also Aaron_Adams should be able to help as well, if he get's to this before me...
When I installed slackware a month or so ago, I thought I selected kernel "2.4.5.", but unfortunetly "2.2.19." was installed. Is there a way to upgrade this without too much trouble?
Thanks,
-Beatlejuice
beatlejuice321,
I can answer this for you, however I don't have time just yet, as I'm about to go into work. When I get home, I'll post up an answer. Also Aaron_Adams should be able to help as well, if he get's to this before me...
AMD Athlon 2200+ 1.8Ghz
1280MB PC-3200 CAS2.5 RAM
ATI Radeon 9600 Pro 128MB AGP
Western Digital WDC WD2500JB-00FUA0 250GB 7200 rpm ATA/133
Seagate ST3200822A 200GB 7200 rpm ATA/133
Western Digital WDC WD1200BB-00CAA1 120GB 7200 rpm ATA/133
Western Digital WDC WD800BB-00CAA1 80GB 7200 rpm ATA/133
Maxtor OneTouch 2HA43R32 1TB 7200 rpm USB 2.0
D-Link DFE-530TX+ 10/100 NIC
D-Link DWL-G520 Rev.A
Debian 5.0r1 Lenny
Thanks, I appreciate it. I'll be looking for your post.
-Beatlejuice
Ok upon install of Slackware 8.0, you will need to select expert install to be able to choose the 2.4.5 kernel. From the a1 package there will be four kernels to select. If you are using a system with non-scsi then select the 2.4.5 kernel for ide, if your using scsi, then select the one for that. Remember only one out of the four can be selected so make sure you have the right one. Ok next in that same package is the modules. There are the 2.2.19 modules and the 2.4.5 modules. It say's the 2.2.19 modules are required, but that's only because the 2.2.19 kernel is the default. So we want to unselect the 2.2.19 modules which I believe are called modules. You will want to have the 2.4.5 modules selected which I believe are called mods245. After all this is done, make sure you only install the kernel source for the 2.4.5 kernel. That is in package k1, and it's called lnx245. The rest of the install is up to you....
Ok if you just want to correct what you already have, then you will need to d/l the 2.4.18 kernel from http://www.kernel.org and compile it. Once this is done issue the command mv arch/i386/boot/bzImage /vmlinuz-2.4.18 and then configure /etc/lilo.conf to match accordingly so that you can boot that kernel. A word of advice I would not wright over the current /vmlinuz because you may not be able to boot the new kernel right away, espcially if you've never done this before. Once you get the new kernel working, and you would like to remove the old kernel you can do a removepkg packagename.tgz. I can't remember what the 2.2.19 kernel package is called off the top of my head, but if you need to know let me know. I will look it up....
AMD Athlon 2200+ 1.8Ghz
1280MB PC-3200 CAS2.5 RAM
ATI Radeon 9600 Pro 128MB AGP
Western Digital WDC WD2500JB-00FUA0 250GB 7200 rpm ATA/133
Seagate ST3200822A 200GB 7200 rpm ATA/133
Western Digital WDC WD1200BB-00CAA1 120GB 7200 rpm ATA/133
Western Digital WDC WD800BB-00CAA1 80GB 7200 rpm ATA/133
Maxtor OneTouch 2HA43R32 1TB 7200 rpm USB 2.0
D-Link DFE-530TX+ 10/100 NIC
D-Link DWL-G520 Rev.A
Debian 5.0r1 Lenny
OK, thanks!
I have never compiled a kernel before. So I may just back up my system and reinstall Slackware, as I am sure this is much faster. Let you know if I have any problems.
-Beatlejuice
Even though you may never do it again, being able to sucessfully compile a kernel is a skill that is good to have.
If you don't use the install for a productivity machine and are just experimenting then i recomend you try to make your own kernel install.
If you need help in the process, there are resources at
http://www.tldp.org/HOWTO/Kernel-HOWTO.html
and
http://kernelnewbies.org/
Alastair
whatdoyougetwhenyoumultiplysixbynine??
Thanks Alastair, I'll do that. I have been looking forward to installing Gentoo Linux, and I believe you have to build most of your install with that. I will probably try installing it on one of my test machines at home.
Thanks for the links.
-Beatlejuice
I have the same dilemma but I was curious
/usr/src/linux
is a link to
/usr/src/linux-2.2.19
but in there is also a folder called
/usr/src/linux-2.4.5
and also a zipped file
/usr/src/linux.2.4.5.reiserfs.diff.gz (not sure what this is though)
Can I use somthing in here to update the kernel because I am lacking a internet connection on my linux box
or is there another location I might be able to find it.
I did check out
http://www.tldp.org/HOWTO/Kernel-HOWTO.html
but it was reffering to redhat and I got a little confused
cindir,
If you want to run 2.4.5 without reinstalling slack, you're going to have to likely compile the 2.4.5 kernel. There have been some odd situations, when it seems that I've had both installed, and it will just change all of a sudden, but I won't get into that. ??? The reason why there are both dir's in /usr/src is a result of what you selected during installation. There may also be /lib/modules/2.4.5. It could be possible to boot from 2.4.5 if you change the /usr/src/linux link to point to 2.4.5 :
$rm /usr/src/linux
$ln -s /usr/src/linux-2.4.5 /usr/src/linux
It may seem odd that it would work, but i've had weird experiences with kernels sometimes.
Anyway, if that doesn't work and you want to compile the kernel just do the following:
$cd /usr/src/linux-2.4.5
$make mrproper
$make config/menuconfig/xconfig #whichever you prefer
$make dep
$make bzImage
$make modules
$make modules_install
$cp /usr/src/linux-2.4.5/arch/i386/boot/bzImage /boot/vmlinuz-2.4.5
$emacs/vi /etc/lilo.conf # again, whichever you prefer
in lilo.conf you'll want something like the following :
# Linux bootable partition config begins
image=/boot/vmlinuz-2.2.19
root=/dev/hda1
label=Linux-2.2.19
image=/boot/vmlinuz-2.4.5
root=/dev/hda1
label=Linux-2.4.5
# Linux bootable partition config ends
After this is completed run
$/sbin/lilo
In case you ended up changing the /usr/src/linux link back to linux-2.2.19 again, you'll want to change it to point to linux-2.4.5
That should be all you need. A final note, your kernel image will likely be in the root directory and be called vmlinuz, you can rename it to vmlinuz-2.2.19 and move it to boot, or do whatever you please. Just remember to update lilo.conf with your changes, and make sure the image path is set properly
Thanks it worked out great changing the /usr/src/linux link didnt work but using your help I got it in 2.4.5
Any place I can go to help slim down and perfect the linux configuration I understood some but most of it was beyond me.
I need a little more indepth explanation, the one liner description didn't help much.
Bookmarks