Solved

Involved question

Posted on 1998-04-13
2
209 Views
Last Modified: 2010-04-22
This is a really involved question but I will throw it out anyway.  To start, I am using  RedHat 5.0, kernel 2.0.32 on a system with a Jaz drive, an Adaptec SCSI 2940 card, and Ensoniq AudioPCI card using OSS Comercial.

Here goes:  I dual boot linux with Win95 for several reasons, and I recently wanted to compile fat 32 support into my kernel so I could mount my windows partitions and play with them under linux.  I used the patch found at http://bmrc.berkeley.edu/people/chaffee/fat32.html to patch a fresh kernel that I just downloaded.  Everything patched OK and then compiled OK, using the old config modified slightly for the patch.

When I subsequently boot, I get an error when I try to load the aix7xxx module, something about failed dependencies.  When it later tries to load the Jaz drive, it also fails, saying that it does not seem to be a valid block device.  I can now mount my windows partitions, but my jaz drive will not mount, and my SCSI CDROM does not work.  If I issue the command "/sbin/modprobe sg" everything works correctly, except for soundon with OSS, but that is a different problem.  Why does this not work on bootup?
0
Comment
Question by:Sylver
2 Comments
 
LVL 1

Accepted Solution

by:
mzito earned 100 total points
ID: 1637136
Here's the problem:  You didn't recompile your modules as well.  Go back to your machine and do the following:
(as root.  I'll provide comments as I go along in parentheses)
cd  /lib/modules/2.0.32
(this, obviously, changes you to the directory where the kernel modules are stored)
rm -rf *
(scary, I know.  If you want to feel safer, back them up someplace)
cd /usr/src/linux
make config
(do all your options, select everything you want as a module, etc.)
make dep ; make clean ; make ____ (zlilo, zImage, etc) ; make modules ; make modules_install
(This will make all the dependencies, clean out all the garbage from the last compile, then compile the kernel itself, then compile the modules, then finally install the modules)

You get this problem when the version information in the modules is not set.  When the kernel is upgraded or changed, their dependencies no longer work properly.  So, recompile the kernel AND recompile the modules.  That'll solve your problem.
Incidentally, the jaz and scsi cd-rom error messages are caused by the error from the scsi controller.  Since the scsi controller never gets recognized, the SCSI devices never get recognized, and thus your problems.  If you have any more questions, feel free to email me @ mzito@wwprsd.mercernet.net

Best Wishes,
Matthew Zito
0
 

Author Comment

by:Sylver
ID: 1637137
Thanks
0

Featured Post

What Security Threats Are You Missing?

Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

Join & Write a Comment

Introduction We as admins face situation where we need to redirect websites to another. This may be required as a part of an upgrade keeping the old URL but website should be served from new URL. This document would brief you on different ways ca…
I. Introduction There's an interesting discussion going on now in an Experts Exchange Group — Attachments with no extension (http://www.experts-exchange.com/discussions/210281/Attachments-with-no-extension.html). This reminded me of questions tha…
Learn how to get help with Linux/Unix bash shell commands. Use help to read help documents for built in bash shell commands.: Use man to interface with the online reference manuals for shell commands.: Use man to search man pages for unknown command…
Connecting to an Amazon Linux EC2 Instance from Windows Using PuTTY.

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

20 Experts available now in Live!

Get 1:1 Help Now