[WBEL-users] newbie - kernel and other upgrades questions
Craig White
craigwhite at azapple.com
Sun Jan 23 11:10:55 CST 2005
On Sun, 2005-01-23 at 18:21 +0200, Alon wrote:
> > ----
> > yum remove kernel-smp-unsupported
> > yum install kernel-smp-unsupported
> >
> > or you can download it and install it...
> > wget
> > ftp://ftp.esat.net/mirrors/whiteboxlinux.org//3.0/en/updates/i686/kernel-smp-unsupported-2.4.21-27.0.2.EL.i686.rpm
> >
> > see
> > <ftp://ftp.esat.net/mirrors/whiteboxlinux.org//3.0/en/updates/i686/>
> >
> > notice how kernel-unsupported rpms match the kernels?
>
>
> WOW, .. so much confusion could have been saved if I had those command lines
> available about... oh.. 10 emails ago.
---
I have to assume that you would be consistent and get updates from the
same sources. I have no idea where you got that 'um.1' kernel-smp-
unsupported but whatever you were doing, it was wrong
---
> > when you get the right kernel-unsupported modules installed (suppose I
> > should say if and when), when you execute sensors-detect, it will tell
> > you which modules that it detects and to load into /etc/modules.conf and
> > thus to modprobe
> > ----
> >>
> > problem is the um.1 in case you still haven't gotten it
>
> Now I get it,. but really.. that wasn't clear to me earlier.
>
> So,. finally.. I get some results to pull in.. but still no sensors found.
>
>
> ======================================================================================
> # sensors-detect
> This program will help you to determine which I2C/SMBus modules you need to
<snip>
> 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.
---
pretty normal through here
---
> 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
> /lib/modules/2.4.21-27.0.2.ELsmp/unsupported/drivers/i2c/i2c-elektor.o:
> init_module: No such device
> Hint: insmod errors can be caused by incorrect module parameters, including
> invalid IO or IRQ parameters.
> You may find more information in syslog or the output from dmesg
> /lib/modules/2.4.21-27.0.2.ELsmp/unsupported/drivers/i2c/i2c-elektor.o:
> insmod
> /lib/modules/2.4.21-27.0.2.ELsmp/unsupported/drivers/i2c/i2c-elektor.o
> failed
> /lib/modules/2.4.21-27.0.2.ELsmp/unsupported/drivers/i2c/i2c-elektor.o:
> insmod i2c-elektor failed
> Loading failed (Illegal seek)... skipping.
> Load `i2c-elv' (say NO if built into your kernel)? (YES/no): YES
> /lib/modules/2.4.21-27.0.2.ELsmp/unsupported/drivers/i2c/i2c-elv.o:
> init_module: No such device
> Hint: insmod errors can be caused by incorrect module parameters, including
> invalid IO or IRQ parameters.
> You may find more information in syslog or the output from dmesg
> /lib/modules/2.4.21-27.0.2.ELsmp/unsupported/drivers/i2c/i2c-elv.o: insmod
> /lib/modules/2.4.21-27.0.2.ELsmp/unsupported/drivers/i2c/i2c-elv.o failed
> /lib/modules/2.4.21-27.0.2.ELsmp/unsupported/drivers/i2c/i2c-elv.o: insmod
> i2c-elv failed
> Loading failed (Illegal seek)... skipping.
> Load `i2c-philips-par' (say NO if built into your kernel)? (YES/no): YES
> Module loaded succesfully.
> Load `i2c-velleman' (say NO if built into your kernel)? (YES/no): YES
> /lib/modules/2.4.21-27.0.2.ELsmp/unsupported/drivers/i2c/i2c-velleman.o:
> init_module: No such device
> Hint: insmod errors can be caused by incorrect module parameters, including
> invalid IO or IRQ parameters.
> You may find more information in syslog or the output from dmesg
> /lib/modules/2.4.21-27.0.2.ELsmp/unsupported/drivers/i2c/i2c-velleman.o:
> insmod
> /lib/modules/2.4.21-27.0.2.ELsmp/unsupported/drivers/i2c/i2c-velleman.o
> failed
> /lib/modules/2.4.21-27.0.2.ELsmp/unsupported/drivers/i2c/i2c-velleman.o:
> insmod i2c-velleman failed
> 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 already loaded.
>
> 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).
>
> Some chips are also accessible through the ISA bus. ISA probes are
> typically a bit more dangerous, as we have to write to I/O ports to do
> this. Do you want to scan the ISA bus? (YES/no): YES
> Probing for `National Semiconductor LM78'
> Trying address 0x0290... Failed!
> Probing for `National Semiconductor LM78-J'
> Trying address 0x0290... Failed!
> Probing for `National Semiconductor LM79'
> Trying address 0x0290... Failed!
> Probing for `Winbond W83781D'
> Trying address 0x0290... Failed!
> Probing for `Winbond W83782D'
> Trying address 0x0290... Failed!
> Probing for `Winbond W83627HF'
> Trying address 0x0290... Failed!
> Probing for `Winbond W83697HF'
> Trying address 0x0290... Failed!
> Probing for `Silicon Integrated Systems SIS5595'
> Trying general detect... Failed!
> Probing for `VIA Technologies VT82C686 Integrated Sensors'
> Trying general detect... Failed!
> Probing for `VIA Technologies VT8231 Integrated Sensors'
> Trying general detect... Failed!
> Probing for `ITE IT8705F / IT8712F / SiS 950'
> Trying address 0x0290... Failed!
> Probing for `IPMI BMC KCS'
> Trying address 0x0ca0... Failed!
> Probing for `IPMI BMC SMIC'
> Trying address 0x0ca8... Failed!
>
> Now follows a summary of the probes I have just done.
> Just press ENTER to continue:
>
>
> I will now generate the commands needed to load the I2C modules.
> Sometimes, a chip is available both through the ISA bus and an I2C bus.
> ISA bus access is faster, but you need to load an additional driver module
> for it. If you have the choice, do you want to use the ISA bus or the
> I2C/SMBus (ISA/smbus)? smbus
>
> WARNING! If you have some things built into your kernel, the
> below list will contain too many modules. Skip the appropriate ones!
> To load everything that is needed, add this to some /etc/rc* file:
>
> #----cut here----
> # I2C adapter drivers
> # I2C chip drivers
> #----cut here----
>
> To make the sensors modules behave correctly, add these lines to either
> /etc/modules.conf or /etc/conf.modules:
>
> #----cut here----
> # I2C module options
> alias char-major-89 i2c-dev
> #----cut here----
----
this appears to be done but it won't take effect until next reboot
----
> Do you want to generate /etc/sysconfig/lm_sensors? (YES/no): YES
> Copy prog/init/lm_sensors.init to /etc/rc.d/init.d/lm_sensors
> for initialization at boot time.
>
> # locate lm_sensors.init
> /usr/share/doc/lm_sensors-2.6.5/lm_sensors.init
>
> # modprobe i2c-proc
>
> # cp /usr/share/doc/lm_sensors-2.6.5/lm_sensors.init /etc/rc.d/init.d/
> ====================================================================================
>
> So,. from reading the "to-do list", I need (already done) to copy the
> lm_sensors for the init.d area.
> Also, I needed to copy/paste a single line into the modules.conf.
> BUT, do I need to do anything with this code:
>
> #----cut here----
> # I2C adapter drivers
> # I2C chip drivers
> #----cut here----
>
> ??
>
> It seems rem'd out. So I'm not sure it carries a value. But again,. now I'm
> guessing whereas I'm no longer
> sure what I'm doing.
----
it's not finding anything so there's nothing to put into modules.conf
yet.
I am confused about the errors on the insmod of the various sensor types
could you please see what you get when you
ls -l /lib/modules/2.4.21-27.0.2.ELsmp/unsupported/drivers/i2c
does it look virtually identical to that which I had listed several
emails ago?
also, the results of sensors-detect might put some errors in dmesg or
syslog.
after running sensors-detect, look near the bottom of /var/log/messages
and /var/log/dmesg to see if there are any problems of import
Craig
More information about the Whitebox-users
mailing list