[WBEL-users] newbie - kernel and other upgrades questions
Alon
js at wsco.com
Sun Jan 23 07:29:33 CST 2005
Hi Craig (and Pete),
As you suggested, I rebooted the machine. That was about 8 hours ago,. and
something went wrong.
My guess it was the lines that I put into the /etc/modules.conf as the
network adapter failed to load.
Unfortunatly, the server is in a NOC and only after 8 hours I was able to
gain access physically to it
and remove those lines. So now I'm back online.
The sensors issue hasn't been resolved of course
Here is the path and files on my system (slightly different path than what
you had)
# ls -l /lib/modules/2.4.21-27.0.2.EL.um.1smp/unsupported/drivers/i2c/
total 192
-rwxr--r-- 1 root root 3456 Jan 19 10:39 dmi_scan.o
-rwxr--r-- 1 root root 10700 Jan 19 10:39 i2c-algo-bit.o
-rwxr--r-- 1 root root 8980 Jan 19 10:39 i2c-algo-pcf.o
-rwxr--r-- 1 root root 7764 Jan 19 10:39 i2c-ali1535.o
-rwxr--r-- 1 root root 8128 Jan 19 10:39 i2c-ali15x3.o
-rwxr--r-- 1 root root 6892 Jan 19 10:39 i2c-amd756.o
-rwxr--r-- 1 root root 24420 Jan 19 10:39 i2c-core.o
-rwxr--r-- 1 root root 8796 Jan 19 10:39 i2c-dev.o
-rwxr--r-- 1 root root 5808 Jan 19 10:39 i2c-elektor.o
-rwxr--r-- 1 root root 3996 Jan 19 10:39 i2c-elv.o
-rwxr--r-- 1 root root 3476 Jan 19 10:39 i2c-hydra.o
-rwxr--r-- 1 root root 8488 Jan 19 10:39 i2c-i801.o
-rwxr--r-- 1 root root 5276 Jan 19 10:39 i2c-i810.o
-rwxr--r-- 1 root root 3024 Jan 19 10:39 i2c-isa.o
-rwxr--r-- 1 root root 5244 Jan 19 10:39 i2c-philips-par.o
-rwxr--r-- 1 root root 8192 Jan 19 10:39 i2c-piix4.o
-rwxr--r-- 1 root root 12056 Jan 19 10:39 i2c-proc.o
-rwxr--r-- 1 root root 7452 Jan 19 10:39 i2c-sis5595.o
-rwxr--r-- 1 root root 3852 Jan 19 10:39 i2c-velleman.o
-rwxr--r-- 1 root root 4308 Jan 19 10:39 i2c-via.o
-rwxr--r-- 1 root root 7808 Jan 19 10:39 i2c-viapro.o
-rwxr--r-- 1 root root 5504 Jan 19 10:39 i2c-voodoo3.o
AND,.. my kernel as a reminder is:
# uname -r
2.4.21-27.0.2.ELsmp
So, I think the modules are sitting in the right place and those are the
correct version.
> why not check for the kernel you are using to make sure that they are
> installed?
Didn't I just do that? I gave the uname -r and the path of where I found
the modules.
If that is NOT how I should check them, please let me know how I SHOULD
check them.
> did you modprobe this already? Maybe try again after a restart. I don't
> see anything that represents an error other than it seems that it can't
> find the files - see above. Are you sure you isntalled the right kernel-
> unsupported for the kernel that you are booting?
Finding the right path,. does that have anything to do with the
/etc/modules?
If so,. that is where I got the wrong entries when I entered them.
I'm affraid that I don't know what to enter in that file without doing
something wrong.
Obviously what I entered wasn't right, but I did try.
> ----
> I really am not gonna get involved with your efforts to 'make' kernel
> modules that are already made and you haven't given a reason to do so.
Please forgive me for being stupid, (I can't help it at times), but my
intention was NOT
to build anything if I don't have to. The reason I was using 'make' was
because I read
the INSTALL in the lm_sensors, and it was talking about compiling. Perahps
I'm
reading the wrong instructions, but I did try to read something.
Did I mention that I'm a novice?
> ----
>> **********
>> 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
> ---
> what are these paths? why?
Those lines got me into the troubleof not booting properly (well. it killed
my network adapter connections).
That was what I thought I should put in the modules.conf, but obviously that
is not what I should do.
I tried to follow the instructions, and in them there were those lines. So I
don't know what values to put into the
modules.conf.
> I'm quite certain that you still don't have the right kernel-unsupported
> that matches the kernel you are booting with.
>From Pete Biggs:
> # rpm -q --all | grep 2.4.21-27.0.2
> kernel-smp-2.4.21-27.0.2.EL
> kernel-2.4.21-27.0.2.EL
> kernel-doc-2.4.21-27.0.2.EL
> kernel-source-2.4.21-27.0.2.EL <<<<<===------- AHA!!! I don't have
> that one!
This is from my system:
# rpm -q --all | grep 2.4.21-27.0.2
kernel-smp-2.4.21-27.0.2.EL
kernel-2.4.21-27.0.2.EL
kernel-smp-unsupported-2.4.21-27.0.2.EL.um.1
Perhaps this was the whole confusion all about??
What is this file: kernel-2.4.21-27.0.2.EL.src.rpm????
I was sure it was the source file that was mentioned over and over.. and it
refused to be installed!
Now at least it is installed:
My system AFTER the install:
# rpm -q --all | grep 2.4.21-27.0.2
kernel-smp-2.4.21-27.0.2.EL
kernel-2.4.21-27.0.2.EL
kernel-smp-unsupported-2.4.21-27.0.2.EL.um.1
kernel-source-2.4.21-27.0.2.EL.um.1
Still ,.. nothing has changed even after another reboot.
# 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.
-Alon.
More information about the Whitebox-users
mailing list