Re: Modules not showing up after compile - why?
On Mon, Dec 04, 2000 at 03:04:53PM +0000, Anthony Campbell wrote:
> On 04 Dec 2000, Harry Henry Gebel wrote:
> > On Mon, Dec 04, 2000 at 12:16:35PM +0000, Anthony Campbell wrote:
> > > However, lsmod and modprobe show nothing: there is no /proc/ksyms or
> > > /proc/modules.
> > > Questions: why don't these things show up, and how does the kernel work
> > > if the modules aren't there?
> > Did you run LILO after you installed the kernel? If you didn't you are
> > probably still booting into your old kernel. If you run `dmesg` you will
> > get a list off all the boot-up messages; the first one will include the
> > data the kernel was compiles. If you enabled modules you should have
> > /proc/modules even if it's empty (assuming you have /proc mounted).
> You're right; I had the wrong kernel loaded!
> Now that I've got the right one, I again can't use sound or access my
> parallel port. I get:
> The kernel does not recognize /dev/sda1 as a block device
> (maybe insmod driver?)
> Opening /dev/audio: no such device.
> I don't know which drivers to install with insmod. Anyway, I thought the
> kernel was supposed to call these things automatically?
I don't know much about setting up module autoloading, but I'm sure
somebody on the list can tell you more, make the subject "setting up module
autoloading" or something similar to get their attention. Still, I get on
pretty good without it using modprobe. Modprobe is a program loads a driver
and any other drivers that driver depends on.
The command for an older zip drive is `modprobe ppa`, or for a newer one
`modprobe imm`. On some systems I can't get ppa to load while lp is loaded,
if you have this problem run `rmmod lp` to unload the lp driver first.
The configuration of the sound card must be setup before you can load the
sound driver, if you use the ALSA modules they can be configured with a
program called `alsaconf`, I don't know what the configuration program is
for the OSS drivers, but I'm sure there is one.
My usual policy is to compile anything I use 100% of the time into the
kernel, so when I was using OSS I always compiled it into the kernel. I
usually have the following compiled as modules.
IDE CDROM drive
Floppy drive
Serial ports
ppp
Zip drive
ALSA (only because I don't know how to compile them into the kernel)
I don't compile lp support at all, but if you have a printer attached to
the computer you will need that too, if you do you definitely want to
compile it as a module so you can unload it if it decides not to get along
with ppa (although if they were getting along when they were both compiled
in they will probably get along with both as modules, but I have found this
to vary from system to system.)
I haven't done anything to set up module autoloading but everything loads
automatically except ppa. (and ALSA, but alsaconf sets that up to get
loaded during boot-up so it is functionally the same as being loaded
automatically.) If you look in /proc/modules you will probaly see that some
at least have already been loaded for you. The modules are in
subdirectories of /lib/modules/kernel-version-number , if you need to know
the name of a driver you can usually figure it out by digging around in
there (the name of the module is the file name with the .o removed, so the
ppa driver is ppa.o , etc.)
--
Harry Henry Gebel, ICQ# 76308382
West Dover Hundred, Delaware
Reply to: