Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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.
couldn't you just open the slack11 CD1 .iso and drop the kernel image in new directory (that follow the format Pat V. uses) ?
then burn the new version of the .iso and boot that kernel?
I wish it were that easy. But remember that the iso must be bootable. So, you need to know exactly how to format the iso, and there's not enough room. You'd have to get rid of another kernel, and as you mentioned, there's probably some config file that needs changing.
Well, I manged to compile a new kernel - 2.6.20.6.
I was also able to add it to the slackwae DVD. I thought that
I solved the problem.
But, I did something wrong. It turns out that on my slackware installation
I have (in lib/modules) only the version 2.4.33. - which is the version of the
sata.i config file that I loaded as default for the kernel compile.
I did it like this:
1) Downloaded and extracted the new kernel (on my 10.1 slack router)
2) make menuconfig -> loaded the config from /kernels/sata.i on 11.0 slackware dvd
3) made some changes
4) Saved the config
5) make
6) Took the bzImage, System.map and .config (renamed it to config)
What did I do wrong? Why do I have /lib/modules/2.4.33.3 instead of my kernel version?
Because you didn't do 'make modules_install' to install the modules. Ether way, you can't really put that on the slackware install CD. You'll have to compile them after you boot the new kernel. Can you boot the new kernel ?
OK, maybe I wasn't clear enough.
I compiled the new kernel and added the new kernel to
the slack dvd - like it's described in readme.txt in
the isolinux folder. I created the new slackware DVD.
It worked, I installed the slackware using this dvd,
and the new kernel that I compiled.
BUT, I found out that after the installation of my
new slackware with kernel 2.6.20.6, the folder
/lib/modules had:
/lib/modules/2.4.33.3 instead of 2.6.20.6 - this coses
all sorts of problems.
What does make modules_install do? Does this put the
correct modules in bzImage or does this install the new
modules on the machine that you issue the command?
I need to make those modules and transfer them to the
new machine. Can I do that somehow? Or can I put them
inside the newly compiled bzImage?
Well, 'make modules_install' does what you might think it does, it installs the kernel modules to '/lib/modules/2.6.20.6', and because you haven't run it, there is no such directory. What I would do is get the source, use the same .config and compile and install the modules on the newly installed Slackware. So that would be 'make modules', then 'make modules_install'.
well you could also just copy the compiled modules you already have and fix the simlink to point to your new
/lib/modules/2.6.20
AFIK slackware always installs the 2.4.33 modules, even if you install with a 2.6 kernel you have to install the modules later. I suppose you could try something like this too:
Code:
mkdir /tmp/modulespkg
make modules # you shouldn't need this if they're already built in your source tree
make DESTDIR=/tmp/modulespkg modules_install
cd /tmp/modulespkg
makepkg modules-2.6.20.tgz
all this on your 10.1 box
then move the modules-2.6.20 package you just created to your new lappy and do an installpkg
I DON`T KNOW IF YOUR RUNNING 64 BIT OR 32 BUT YOOU NEED TO LOOK AT THIS
"kernels/huge26.s/* - added a 2.6.17.13 kernel to the official
(supported) package set. The user will be given a choice of
whether to install the 2.4.33.3 or 2.6.17.13 kernel. If a 2.6
kernel is used, additional packages must be added after the
installation -- at the very least the kernel-modules package.
Possibly also the kernel-headers to provide /usr/include/sound
used to compile ALSA applications.
* extra/linux-smp-2.6.17.13/* - added a 2.6.17.13 kernel, modules,
and headers with SMP and hyperthreading support, optimized for
i686 or better cores (including dual core CPUs)."
Same thing happen, when i tried to install mandriva 2007 on my friends machine, VIA chipset with "Seagate sata2" harddisk. the installer couldn't recognize the hard disk. But everything works fine when i use Slackware 11
Why don't you try to make initramfs, use mkinitrd command with your new precompiled kernel, but remember to add the slackware setup scripts. The scripts is on the initrd.img file on your slacks DVD.
do something like this on another machine with slackware 11:
1. install or configure kernel 2.6, make sure the module that recognize your sata disk also builded
2. copy initrd.img from your slack DVD (from isolinux folder) to your writeable disk and then extract it (it actually gzip compressed initramfs) #gunzip -S .img -d initrd.img //it will produce a file named initrd without suffix
3. #mkdir mounted_initrd
4. #mount initrd mounted_initrd -o loop //mount to a directory using loopback interface
5. #you will see, that under mounted directory, only modules for 2.4 kernel exist. so you must create a new initramfs with kernel 2.6 modules.
i don't remember the parameter for mkinitrd, and right now i use M$ at internet cafe.. sorry i gonna continue this post later if i already remember it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.