Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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.
Currently I have a PIII-Xeon dual processor system with an Adaptec 7892 scsi controller. Originally, I loaded Slack-10.1 with the adaptec.s kernel and then recompiled it to include HIGHMEM and SMP. It works just fine using the 2.4.29 kernel as I haven't recompiled with the 2.4.31 kernel in -current, yet.
My issue is, I'm wanting to upgrade to the 184.108.40.206 kernel in the /testing branch. I installed the headers, and the source, since I know that the generic kernel and modules won't work 'out of the box'. I went into the source tree, and ran 'make menuconfig' enabled SMP and turned off Raid (I actually have a raid system, but stupidly, did not enable it during installation (as I mentioned, I ran with adaptec.s instead of raid.s for who knows what reason). I compiled the kernel and installed the config, system.map, kernel image and edited lilo.conf and ran 'lilo'. Following that, I rebooted trying to use the kernel, with a pretty good guess it wouldn't load without a ramdisk/initrd image. It didn't... it wouldn't find the scsi device and halted when attempted to locate the root device.
As per the README.initrd in the /testing tree, I rebooted back into 2.4.29, then ran mkinitrd. I specified 'aacraid' and 'aic7xxx' since I have noticed they're called in my 2.4.29 bootup, and called the 'jbd' and 'ext3' modules since my root partition uses ext3. The following was the first mkinitrd I ran in the /boot dir:
As usual, I added the 'initrd = /boot/initrd.gz' line to lilo.conf, and reran lilo. Then rebooted. Now it found the scsi controller, but made reference to unknown symbols, specifically (forgive me, it never saved to dmesg after rebooting into 2.4.29, nor any logs) mentioning 'transport' and 'spi'. Looking in the /lib/modules/220.127.116.11js/kernel/drivers/scsi dir, I noticed the scsi_transport_spi, scsi_transport_fc, and scsi_transport_iscsi modules. I tried loading them into the mkinitrd statements prior to the aacraid module, and edited everything, reran lilo, and rebooted. Again, it came up with unknown symbols and then it's attempt to load the other scsi modules. I started off using the stock .config file with Slack's kernel-source install.
The modules are in the /boot/initrd-tree/ directory, in /lib/modules/18.104.22.168js/ as mentioned in the startup screen. My main question here is... Am I missing additional modules, or am I missing something during configuration, or compilation in order to get the adaptec SCSI adapter to work?
Nevermind One thing I noticed with the 2.4.29 kernel was the inclusion of an Adaptec I2O Raid module. I added the 'dpt_12o' module to the mkinitrd command, and now it loads, albeit with some errors, but I can't see those errors interfering with the operation of the system thus far.