All of lore.kernel.org
 help / color / mirror / Atom feed
From: jlnance@unity.ncsu.edu
To: linux-kernel@vger.kernel.org
Subject: Help with modules
Date: Fri, 27 Dec 2002 09:47:18 -0500	[thread overview]
Message-ID: <20021227144718.GA2567@ncsu.edu> (raw)

Hello All,
    I am having some problems using the 2.5.53 kernel because my module
scripts dont work.  I got the modutils-2.4.21-10 SRPM package from
ftp.kernel.org/pub/linux/kernel/people/rusty/modules. I verified that
it contains both the old modutils and the new module-init-tools source
code.  I built it and installed the resulting RPM on my Red Hat 8.0
machine.  When I boot, I get messages about modprobe failing:

 Dec 27 08:56:39 tricia modprobe: FATAL: Module hid not found.
 Dec 27 08:56:39 tricia rc.sysinit: Initializing USB HID interface:  failed
 Dec 27 08:56:39 tricia modprobe: FATAL: Module keybdev not found.
 Dec 27 08:56:39 tricia rc.sysinit: Initializing USB keyboard:  failed
 Dec 27 08:56:39 tricia modprobe: FATAL: Module mousedev not found.
 Dec 27 08:56:39 tricia rc.sysinit: Initializing USB mouse:  failed

and none of my modules get loaded.

If I boot the stock Red Hat 8.0 kernel using the new modutils, everything
seems to work fine (and its a lot more modular than the 2.5.53 kernel I
am trying to use).

I have a modules.conf file, but I think I read somewhere that the newer
modutils want a modprobe.conf file which I dont have.  That may be the
problem, but thats just a guess (and I dont know what should go in
that file).

I would certainly appreciate any suggestions anyone might have for fixing
my setup.  I would like to help test the 2.5.X kernels, but this has
been an difficult series of kernels to follow casually.  Hopefully this
is the last big obstacle.

Thanks,

Jim

                 reply	other threads:[~2002-12-27 14:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20021227144718.GA2567@ncsu.edu \
    --to=jlnance@unity.ncsu.edu \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.