SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
A couple of months back I was playing with Slackware 11.0 when I was trying to get the ipw2200 drivers to work. Eventually someone suggested that I try to huge26.s kernel and it almost worked right out of the box. I remember all I had to do was install the extra modules (and I cant remember how) and change an address or two (cant remember what those were either, i think they were pci addresses). Well I lost that configuration and I am finally getting around to setting it up again. I cant remember for the life of me how I did it.
I have installed the huge26.s kernel so my kernel is 2.6.17. This boots fine but I don't have any modules (presumably why my mouse does not work as well). I can remember what the command to install these was. I have tried a few that I have found online but they put me in a different spot then I ended up in last time. When I do this im loosing my .xsf file support. So now I have to copy all the src onto my hard drive and recompile my kernel. What happened to the .xsf support that I had before i ran installpkg modules.****.***?
I know there is an easy way to do this. Does anyone know what it is? (if your way includes 100 steps then thats not the one I'm looking for)
when i at first tried to compile a kernel using the pre-compiled huge26.s I sort of stumbled on the same problem.
my solution isn't that great but it worked for me.
First downloaded the cd1 from the 3-iso-pack. you can find mirrors on the slackware site
i opend the iso image and copied the kernel-source-184.108.40.206 to the K package from the iso ,then deleting the original kernel-source-220.127.116.11 in the K package.
But wait when you open the kernel-source-18.104.22.168 package you'll find the kernel-modules plus the kernel-generic-something. copy them to the A package .Don't touch the header files from 22.214.171.124 source files. Then delete the kernelsource files plus the module files from the A package : 126.96.36.199
now you set just burn cd1 and at boot type huge26.s , do the expert install .If it asks what bzimage/vmlinuz img it will boot go for option cdrom , go for the scan then you'll get the option to boot with the huge26.s precompiled kernel. That's about how i did it.
I really got stuck compiling the kernel so why not install the kernel at installation
Yeah I did install the kernel during the install process. It was the modules that I was having trouble with. I know there is a really easy way to do it I just cant remember what it is. I compiled all the modules in with the kernel, enabled .xfs support and everything works fine now. I guess I learned more by doing it that way and experiencing all the frusteration. I also learned that kernel panic message I get every time I tried to compile my own kernel was a result of not adding support for my file system in the kernel. So anyways Im all set and got to where I wanted to be.
If anyone knows the really simple way of doing this, please let me know.
The huge26.s kernel is meant to provide maximum hardware support for installing Slackware. Afterwards, you can run a normally packaged kernel. You can do it as follows:
1) Install Slackware normally, with huge26.s as the installed kernel.
3) Install extra/linux-188.8.131.52/kernel-generic-184.108.40.206-i486-1.tgz and extra/linux-220.127.116.11/kernel-modules-18.104.22.168-i486-1.tgz or, if you have a SMP system, extra/linux-smp-22.214.171.124/kernel-generic-smp-126.96.36.199-i686-3.tgz and extra/linux-smp-188.8.131.52/kernel-modules-smp-184.108.40.206-i686-3.tgz
4) Read the newly installed /boot/README.initrd file and make your initial ramdisk with the needed modules. Normally you will only need the bare minimum to boot the system, that is, the modules needed to access your root partition. Reinstall lilo.
You should now be running a kernel much leaner than huge26.s, and known to the pkgtools utilities. The hotplug scripts should manage the modules for the rest of your hardware (sound card, network cards, etc.) but, if you run into any trouble, you can edit /etc/hotplug/blacklist and/or /etc/rc.d/rc.modules to manually configure your hardware drivers.
The huge26.s kernel is meant to provide maximum hardware support for installing Slackware. Afterwards, you can run a normally packaged kernel. <snip>
Not to contradict but if you read the Slackware 11 RELEASE NOTE you will find PVs' reasoning behind the huge26 and test26 kernels. There is no reason not to use either except to trim for size. But that will have no effect on performance if you leave them as installed.
Slackware 11 RELEASE NOTE excerpt;
Anyway, since there is hardware out there that requires a 2.6 kernel in order to install, this release of Slackware has both 220.127.116.11 and a 2.6.18 kernels integrated into the installer. To install using one of these, after booting the first disc, enter huge26.s at the boot prompt for the supported 18.104.22.168 kernel (which also supports installing via NFS), or test26.s to use the 2.6.18 kernel from /testing. These kernels have compiled-in support for essentially all of the hard drive controllers and filesystems that are supported by the 2.6.x kernel series, and should be helpful for people with new SATA controllers or other hardware that 22.214.171.124 doesn't support. This kernel doesn't have any built in network support and is primarily intended for installing from local media (although huge26.s will support an NFS installation if you run the 'network' script to load your network module, and you're installing from CD or DVD). After the packages have installed and you've reached the menu where you are prompted to select a kernel to install, BE CERTAIN to install huge26.s or test26.s (whichever one you used to install) or there's a chance that your machine will be unable to boot with the stock sata.i kernel that you'll end up with.
Also, the kernel module packages for 2.6.x are not part of the
standard installation, so if you install using huge26.s or test26.s
kernel you'll have to install the corresponding kernel-modules package
when you're done. They can be found under /extra/linux-126.96.36.199/ (or
ISO number two under /extra/linux-188.8.131.52), or
/testing/packages/linux-2.6.18/ (or ISO number four under
/testing-2.6.18/packages/linux-2.6.18). You might also consider
installing the other packages there and building an initrd according to
the instructions in README.initrd if you'd like to be running a slimmer
kernel without a lot of unneeded drivers taking up RAM, or better yet,
visit ftp.kernel.org in /pub/linux/kernel/v2.6/ and grab the latest
version of the 2.6 kernel to build your own. It'll probably have some
important fixes. Note that the 2.6 kernels do not have an
"alsa-driver" package, but if you remove that package then you'll have
to upgrade to the kernel-headers package for your 2.6 kernel in order
to have the /usr/include/sound/ ALSA headers. These have not been
extensively tested, and you may be better off sticking with the
kernel-headers for 184.108.40.206 (which are what glibc was compiled against)
and the alsa-driver package compiled for 220.127.116.11.
Thats it! Your done! None of that compile a new kernel or make an initrd or anything.
As a wise man once said, "Not to contradict, but"...this will not work if you use a file system such as reiserfs which is not compiled into kernel-generic. In that case you do need an initrd or recompile your kernel.