hwmon-cpufreq-2.6.26

[Roberto A. Foglietta]

contains

/usr/local/lib/modules/2.6.26-tinycore

instead of

/lib/modules/2.6.26-tinycore

[Jason W]

Tinycore has a particular depmod utility that maps and loads kernel modules from /usr/local/lib/modules/`uname -r` just like they are in /lib/modules.  It is by design so that kernel module extensions are PPI compatible.   In fact, /usr/local/lib/modules/`uname -r` is the standard place to install modules in TC.

[Roberto A. Foglietta]

However at boot time there are a lots of messages like this:

Code: [Select]

WARNING: Can't read module /lib/modules/2.6.26-tinycore/kernel.tclocal/drivers/char/hw_random/amd-rng.ko.gz: No such file or directory

tc@box:~$ ls -al /lib/modules/2.6.26-tinycore/
drwxrwxr-x    3 root     root            0 Apr  6 05:16 ./
drwxr-xr-x    3 root     root            0 Apr  6 05:16 ../
lrwxrwxrwx    1 root     root           35 Apr  6 05:16 build -> /usr/local/src/linux-headers-2.6.26/
drwxrwxr-x    7 root     root            0 Apr  6 05:16 kernel/
lrwxrwxrwx    1 root     root           45 Apr  6 05:16 kernel.tclocal -> /usr/local/lib/modules/2.6.26-tinycore/kernel/

tc@box:~$ find / -name amd-rng.ko.gz 2>/dev/null
/tmp/tcloop/hwmon-cpufreq-2.6.26/usr/local/lib/modules/2.6.26-tinycore/kernel/drivers/char/hw_random/amd-rng.ko.gz
/usr/local/lib/modules/2.6.26-tinycore/kernel/drivers/char/hw_random/amd-rng.ko.gz
/mnt/sda2/tclocal/lib/modules/2.6.26-tinycore/kernel/drivers/char/hw_random/amd-rng.ko.gz


[Jason W]

Ok, I will look into it.

[Jason W]

I have that tce extension in my tce directory to load on boot and when I try to modprobe that particular module it simply says no such device.  But other modules from that extension load just fine.  Let me try the tcz version and see if that makes a difference.


EDIT: Modules seem to load ok here with the tcz extension.

[Roberto A. Foglietta]

I have cleaned my tclocal and everything is ok for me too, sorry.
In the future before open a bug report I will clean my tclocal.

[Jason W]

No problem at all.  Oh, and also using tclocal does not always work well with the tcz extension type.  It can work but files in tclocal can get in the way of the "installing" of the tcz.  Tcz's don't have the advantage of the brute force untarring of the tce which overwrites any files in it's path.  So stray files or dangling symlinks are not overwritten by the tcz which can cause problems. 

But according to your info the files are all there where they should be, that is as long as the amd-rng.ko.gz in /usr/local....  is a symlink pointing to the same file in /tmp/tcloop.

[Roberto A. Foglietta]

if tclocal is void then warnings does not happen, otherwise they happen because depmod -a into rcS

Code: [Select]

- depmod -a
+ depmod -ae 2>/dev/null

the initrd.gz image should be remake