On Tuesday 27 May 2003 22:30, Mark Knecht wrote: > On Tue, 2003-05-27 at 11:38, Condon Thomas A KPWA wrote: > > >> No, that's not the question. I understand that. The question was > > >> how would anyone know that the root cause of the depmod problem > > >> was having lm_sensors installed in the first place? The error > > >> message didn't seem to say lm_sensors anywhere? (Or did I miss > > >> it?) > > > > > > Well from the unresolved symbols one sees that i2c is not > > > installed either as modules or in the current running kernel. > > > So one goes through everything that could use i2c and there > > > really is not that many of those. The most logical choice is > > > lm_sensors. > > > > Then let me ask the next question. If the unresolved symbols tell > > me that i2c is not installed, how do I know (without pre-knowledge > > of what i2c is because I'm a novice) which packages might use it? > > Would it be found by emerge -s i2c > > In this case, no. i2c was part of the kernel compile. I turned it off > and got messed up. > > I agree that having some way of figuring this out (for novices like > you and I) would be really helpful...
As your original post had those modules with unresolved symbols one could search if that module file belongs to some package or is it kernel module. qpkg -f /lib/modules/2.4.20-gentoo-r4/misc/adm1021.o which prints this in my machine. sys-apps/lm_sensors * -- [EMAIL PROTECTED] mailing list
