[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 235
  • Last Modified:

Involved question

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
Sylver
Asked:
Sylver
1 Solution
 
mzitoCommented:
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
 
SylverAuthor Commented:
Thanks
0

Featured Post

The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now