[WBEL-users] newbie - kernel and other upgrades questions
Alon
js at wsco.com
Sat Jan 22 18:45:38 CST 2005
Hi Craig,
> did you modprobe it?
Yes I did, it was in the previous email, but here it is again:
# modprobe i2c-proc
modprobe: Can't locate module i2c-proc
**********
Did I run detect-sensor?
Yes I have, but it come up with lots of errors:
# sensors-detect
This program will help you to determine which I2C/SMBus modules you need to
load to use lm_sensors most effectively.
You need to have done a `make install', issued a `depmod -a' and made sure
`/etc/conf.modules' (or `/etc/modules.conf') contains the appropriate
module path before you can use some functions of this utility. Read
doc/modules for more information.
Also, you need to be `root', or at least have access to the /dev/i2c[-/]*
files
for some things. You can use prog/mkdev/mkdev.sh to create these /dev files
if you do not have them already.
If you have patched your kernel and have some drivers built-in you can
safely answer NO if asked to load some modules. In this case, things may
seem a bit confusing, but they will still work.
IF THIS IS AN IBM THINKPAD, PRESS CTRL-C NOW!
IBM Thinkpads have a severely broken i2c/SMBus implementation, just
scanning
the bus will break your Thinkpad forever!
If this is a non-Thinkpad IBM, we still suggest you press CTRL+C. We have
had users reporting system breakage on other IBM systems as well.
We can start with probing for (PCI) I2C or SMBus adapters.
You do not need any special privileges for this.
Do you want to probe now? (YES/no): yes
Probing for PCI bus adapters...
Sorry, no PCI bus adapters found.
We will now try to load each adapter module in turn.
Do you now want to be prompted for non-detectable adapters? (yes/NO): yes
Load `i2c-elektor' (say NO if built into your kernel)? (YES/no): yes
modprobe: Can't locate module i2c-elektor
Loading failed (Illegal seek)... skipping.
Load `i2c-elv' (say NO if built into your kernel)? (YES/no): yes
modprobe: Can't locate module i2c-elv
Loading failed (Illegal seek)... skipping.
Load `i2c-philips-par' (say NO if built into your kernel)? (YES/no): yes
modprobe: Can't locate module i2c-philips-par
Loading failed (Illegal seek)... skipping.
Load `i2c-velleman' (say NO if built into your kernel)? (YES/no): yes
modprobe: Can't locate module i2c-velleman
Loading failed (Illegal seek)... skipping.
To continue, we need module `i2c-dev' to be loaded.
If it is built-in into your kernel, you can safely skip this.
i2c-dev is not loaded. Do you want to load it now? (YES/no): yes
modprobe: Can't locate module i2c-dev
Loading failed (Illegal seek), expect problems later on.
We are now going to do the adapter probings. Some adapters may hang halfway
through; we can't really help that. Also, some chips will be double
detected;
we choose the one with the highest confidence value in that case.
If you found that the adapter hung after probing a certain address, you can
specify that address to remain unprobed. That often
includes address 0x69 (clock chip).
Couldn't open /proc/bus/i2c?!? at /usr/sbin/sensors-detect line 2970,
<STDIN> line 7.
**********
> Did you follow the instructions?
I believe I have, but the run fails. I'm referring to the instructions that
show on the sensors-detect command.
The first instruction is to: make install and it fails.
See the output:
# make install
grep: /lib/modules/2.4.21-27.0.2.ELsmp/build/Makefile: No such file or
directory
grep: /lib/modules/2.4.21-27.0.2.ELsmp/build/include/linux/autoconf.h: No
such file or directory
grep: /lib/modules/2.4.21-27.0.2.ELsmp/build/.config: No such file or
directory
grep: /lib/modules/2.4.21-27.0.2.ELsmp/build/.config: No such file or
directory
grep: /lib/modules/2.4.21-27.0.2.ELsmp/build/.config: No such file or
directory
grep: /lib/modules/2.4.21-27.0.2.ELsmp/build/.config: No such file or
directory
grep: /lib/modules/2.4.21-27.0.2.ELsmp/build/.config: No such file or
directory
grep: /lib/modules/2.4.21-27.0.2.ELsmp/build/.config: No such file or
directory
grep: /lib/modules/2.4.21-27.0.2.ELsmp/build/.config: No such file or
directory
grep: /lib/modules/2.4.21-27.0.2.ELsmp/build/.config: No such file or
directory
grep: /lib/modules/2.4.21-27.0.2.ELsmp/build/.config: No such file or
directory
grep: /lib/modules/2.4.21-27.0.2.ELsmp/build/.config: No such file or
directory
grep: /lib/modules/2.4.21-27.0.2.ELsmp/build/.config: No such file or
directory
grep: /lib/modules/2.4.21-27.0.2.ELsmp/build/.config: No such file or
directory
Makefile:170: kernel/i2c-core.d: No such file or directory
Makefile:170: kernel/i2c-dev.d: No such file or directory
Makefile:170: kernel/i2c-algo-bit.d: No such file or directory
Makefile:170: kernel/i2c-algo-biths.d: No such file or directory
Makefile:170: kernel/i2c-elv.d: No such file or directory
Makefile:170: kernel/i2c-velleman.d: No such file or directory
Makefile:170: kernel/i2c-algo-pcf.d: No such file or directory
Makefile:170: kernel/i2c-proc.d: No such file or directory
Makefile:170: kernel/i2c-pport.d: No such file or directory
grep: /lib/modules/2.4.21-27.0.2.ELsmp/build/.config: No such file or
directory
Error - missing file /lib/modules/2.4.21-27.0.2.ELsmp/build/.config !!
Verify kernel source is in /lib/modules/2.4.21-27.0.2.ELsmp/build and then
cd to /lib/modules/2.4.21-27.0.2.ELsmp/build and run 'make config' !!
Exception: if you're using a stock RedHat/Fedora kernel...
(1) Install the appropriate kernel-source RPM.
(2) Copy the appropriate config...
from /lib/modules/2.4.21-27.0.2.ELsmp/build/configs/<...>
to /lib/modules/2.4.21-27.0.2.ELsmp/build/.config
(3) Do *NOT* 'make dep' or 'make config'.
make: *** [/lib/modules/2.4.21-27.0.2.ELsmp/build/.config] Error 1
**********
The modprobe version installed on my box is:
# modprobe --version
modprobe version 2.4.25
**********
> put the lines it suggests into /etc/modules.conf
Here is the output of the Current /etc/modules.conf
I'm having a bit of a hard time trying to understand what value, syntax I
need to enter into the modules.conf.
I've plugged the lines that I think are correct. Don't I need to actually
put something in those directories?
# vi modules.conf
alias eth0 e100
alias scsi_hostadapter ata_piix
alias sound-slot-0 i810_audio
post-install sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -L >/dev/null
2>&1 || :
pre-remove sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -S >/dev/null
2>&1 || :
alias usb-controller usb-uhci
alias usb-controller1 ehci-hcd
path[misc]=/lib/modules/current/extra/misc
path=/lib/modules/current/extra
> Definitely seems to me that you aren't following the instructions.
Aparently I have reading comprehension problems. Did I miss a step?
More information about the Whitebox-users
mailing list