Hi Steve,
> I create a initrd image for the
> IDE cdrom module (mkinitrd --preload ide-cd initrd-2.2.16.img 2.2.16)
You don't mention that you have an extra CD player. You should only use ide-
cd for CD *readers*. You use the writer as a pseudo SCSI device.
You don't necessarily have to make an initrd for this purpose. You probably
don't need the ide-cd driver until after booting.
> During bootup I get error
> msg like this '/lib/ide-cd.o: unresolved symbol....'
> ...
> If I run 'modprobe \*' only two of the maybe 10-15 modules I compiled
OK, so it seems you compiled and installed the modules. In that case, maybe
you forgot to copy your new kernel to /boot?
> load. Doing 'lsmod' shows the ide-scsi module and nls_iso8859-1. I can
> go to /lib/modules/2.2.16 and manually load the modules and it works.
> The cdrom drive is mountable. But isn't this what modprobe is suppose to
> do?
Well, the command you specify (with the backslash in it) makes no sense. You
load nothing this way. The modules you see were probably loaded at boot.
Ususally you set the modules that should be loaded at boot in
/etc/conf.modules. If you want to load modules by hand you either have to have
the modules directories in the path, or specify a filename or path on the
command line. Don't forget you should use ./* if you reference files in the
current directory if it is not in the path.
> So, if you've read this far here are the questions:
>
> 1. What is causing ide-cd.o to generate this error msg?
Again, the kernel and modules don't seem to match. Either you did not install
the kernel in /boot, or you use the wrong ide-cd.o on the initrd, since you
state you can load ide-cd.o from /lib/modules/###/block. (Well, that is how I
understand it, you are a little fuzzy in this respect. If you recompile a
kernel (and not the modules) some modules might have this symbol problem,
others might not. So can you load all the modules by hand? Or just a few?)
> 2. Why is modprobe looking in /lib and not
> /lib/modules/<kernel-version>/modules.dep?
a) Well, this is your initial ramdisk, which stores the modules in /lib. b)
modprobe only looks for dependencies in modules.dep, it does not load all the
files mentioned in this file if you supply it a *. conf.modules is for that.
> 3. What the hell do modules.conf/conf.modules have to do with the price
> of tea in china?
Where again did you read that one?
> 4. How do I modify modules.conf/conf.modules to allow modprobe to load
> ide-cd.o?
Add "options ide-cd ignore=hdc" to conf.modules, assuming your CD writer is
hdc (it's a good idea to jumper the writer as master instead of slave). This
way all cd players except for the writer are recognized as IDE devices. This
is all explained in the CD-Writing-HOWTO. I guess you missed it :).
> 5. Where does the initrd file come into play in all this?
Initrd is an initial ramdisk, that you use if you need to load drivers that
are needed at boot, eg. for SCSI-adapters, if you boot from SCSI. ide-cd is
not one of them, but(/so) it doesn't harm (not) loading it early in the boot
process.
> 6. Who will win the World Series this year? (Just checking to see if
> your awake. :-))
The Chicago Rangers ;)? Well, I think France is winning the European
Championship this year.
Ciao,
Leonard.
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.