Re: apt-get
On Tue, Dec 07, 1999 at 09:38:41PM -0600, Nathan York wrote
> > > fixed:~# dpkg -P lm-sensors
> > > dpkg: error processing lm-sensors (--purge):
> > > Package is in a very bad inconsistent state - you should
> > > reinstall it before attempting a removal.
> > > Errors were encountered while processing:
> > > lm-sensors
> > >
> > > and when i try to reinstall it i get the
> > > depmod: QM_MODULES: function not implemented.
> > >
> > I had a quick look at the postinst script for lm-sensors, and all
> > it does is
> > depmod -a >/dev/null
> >
> > What do you see if you run depmod -a as root?
> depmod: QM_MODULES: Function not implemented
> > What do you get if you grep -4 QM_MODULES /etc/conf.modules?
> nothing
> > What's in /etc/modutils/lm-sensors?
> file doesn't exist
> >
>
> does anyone know what QM_MODULES is and how i can get it on my system...
I think it's more likely to be a matter of getting something *off* your
system; you may have a corrupted or bad module on your system, that's
making depmod choke.
Try issuing the command
# depmod -av
as root; this will list your modules as depmod process them.
If there is a problem with one of them I'd be suspicious of either
the last name it shows you, or perhaps one of the next few that you don't
get to see... on my system, depmod seems to print out the names in reverse
directoy order (i.e., exactly the opposite of ls -1U).
If you can narrow down the directory in which the problem occurs,
check first that it's under /lib/modules (or somewhere else that
you have decided modules belong); if it isn't, then some package
or some one has put an entry under /etc/modutils to tell depmod
to look there, and if it doesn't contain modules then that will
be a problem.
Alternatively, try issuing the command
# depmod -v <file>
on files in that directory until you find the one that causes the problem.
If you can't find the file this way, look in /etc/conf.modules for
lines that start
path[....
for a list of the directories that depmod will check; if depmod has
a problem with the first file in a directory then the last name you
see may be from a different directory.
Once you've identified the file that seems to be causing the problem,
issue a
$ dpkg -S <file>
to find out which package to blame, so you can fix it properly later.
Check the documentation for this package, in case it tells you how to
'properly' fix the problem.
Meantime, move the file aside to some other place where depmod won't
find it and try
# update-modules (if the problem was somewhere in /etc/modutils/)
and then
# depmod -a
again.
If that works and you don't need whatever package owns the offending file,
run
# dpkg --purge <badbadpackage>
and try
apt-get install lm-sensors
again.
If you need the package, you may want to try re-installing it -
it's possible that the file in question was OK, but became corrupted
somehow (or, that a fixed version is up now).
John P.
--
huiac@camtech.net.au
john@huiac.apana.org.au
"Oh - I - you know - my job is to fear everything." - Bill Gates in Denmark
Reply to: