Re: Tiny Core v17.0 upgrade issues

[Rich]

Hi Stefann
It's looking in the wrong place:

...

Code: [Select]

tc@hp510: ----- Snip -----

modprobe: can't load module p4-clockmod.ko.gz (kernel/drivers/cpufreq/p4-clockmod.ko.gz): No such device

 ----- Snip ----- ...

It should either try to load (full path):

Code: [Select]

/lib/modules/6.18.35-tinycore/kernel/drivers/cpufreq/p4-clockmod.ko.gzor in this case (current directory):

Code: [Select]

./p4-clockmod.ko.gz
You shouldn't need to do this, but try:

Code: [Select]

sudo /sbin/depmod -a
sudo /sbin/udevadm trigger
sudo modprobe p4-clockmod.ko.gz
If that fails, try:

Code: [Select]

sudo modprobe /lib/modules/6.18.35-tinycore/kernel/drivers/cpufreq/p4-clockmod.ko.gz
If it still fails, try:

Code: [Select]

sudo modprobe /lib/modules/$(uname -r)/kernel/drivers/cpufreq/p4-clockmod.ko.gz

[Stefann]

Thanks Rich,

I actually already tried full path already in previous post without success
But anyways... I tried all your suggestions but zero success (data at end of this post).

The strange thing is:
ls -l command clearly shows p4-clockmod.ko.gz to be present in the correct directory, and "not being zero bytes".
But modprobe reports it cannot find it there.

Anyway... don't break your head about it to much.
At least acpi-cpufreq.ko.gz  did work and I got valid content in  scaling_governor
This is my 2nd system "just being a sandbox".
I think I will stop the 5day run on my primary system tomorrow around noon, 5hrs shy of 5 days, Than I have plenty things to try in the afternoon.
- look for power spikes with osciloscope
- test power settings and measure with energy meter
- conclude towards a viable configuration and start it for at least a 24hr testrun.

thanks being with me on this!!

Code: [Select]

tc@hp510:/lib/modules/6.18.35-tinycore/kernel/drivers/cpufreq$ sudo modprobe p4-clockmod.ko.gz
modprobe: can't load module p4-clockmod.ko.gz (kernel/drivers/cpufreq/p4-clockmod.ko.gz): No such device
tc@hp510:/lib/modules/6.18.35-tinycore/kernel/drivers/cpufreq$ sudo modprobe ./p4-clockmod.ko.gz
modprobe: module ./p4-clockmod.ko.gz not found in modules.dep
tc@hp510:/lib/modules/6.18.35-tinycore/kernel/drivers/cpufreq$ sudo /sbin/depmod -a
tc@hp510:/lib/modules/6.18.35-tinycore/kernel/drivers/cpufreq$ sudo /sbin/udevadm trigger
tc@hp510:/lib/modules/6.18.35-tinycore/kernel/drivers/cpufreq$ sudo modprobe p4-clockmod.ko.gz
modprobe: can't load module p4-clockmod.ko.gz (kernel/drivers/cpufreq/p4-clockmod.ko.gz): No such device
tc@hp510:/lib/modules/6.18.35-tinycore/kernel/drivers/cpufreq$ sudo modprobe /lib/modules/6.18.35-tinycore/kernel/drivers/cpufreq/p4-clockmo
d.ko.gz
modprobe: module /lib/modules/6.18.35-tinycore/kernel/drivers/cpufreq/p4-clockmod.ko.gz not found in modules.dep
tc@hp510:/lib/modules/6.18.35-tinycore/kernel/drivers/cpufreq$ sudo modprobe /lib/modules/$(uname -r)/kernel/drivers/cpufreq/p4-clockmod.ko.
gz
modprobe: module /lib/modules/6.18.35-tinycore/kernel/drivers/cpufreq/p4-clockmod.ko.gz not found in modules.dep
tc@hp510:/lib/modules/6.18.35-tinycore/kernel/drivers/cpufreq$ ls -l p4*
-rw-r--r--    1 tc       staff         2447 Jun 20 02:14 p4-clockmod.ko.gz

[Rich]

Hi Stefann
Two more things. What do these commands return:

Code: [Select]

ls -l /lib/modules/$(uname -r)/modules.dep
grep "p4-clockmod" /lib/modules/$(uname -r)/modules.dep

[Stefann]

Hi Stefann
Two more things. What do these commands return:

Code: [Select]

ls -l /lib/modules/$(uname -r)/modules.dep
grep "p4-clockmod" /lib/modules/$(uname -r)/modules.dep

Note, system still running. No crash in 4.5 day.
I have other obligations today. Not sure whether I have time to spend in this today, if not it will become tomorrow.

On the commands:
On my primary system (note, “huis” is Dutch for “home”, it’s my home control computer):

Code: [Select]

tc@huis:~$ ls -l /lib/modules/$(uname -r)/modules.
dep
-rw-r--r--    1 tc       staff        69582 Jun 20 02:16 /lib/modules/6.18.35-tinycore/modules.dep
tc@huis:~$ grep "p4-clockmod" /lib/modules/$(uname -r)/modules.dep
kernel/drivers/cpufreq/p4-clockmod.ko.gz: kernel/drivers/cpufreq/speedstep-lib.ko.gz
tc@huis:~$

On my 2nd, sandbox system:

Code: [Select]

tc@hp510:~$ ls -l /lib/modules/$(uname -r)/modules
.dep
-rw-r--r--    1 tc       staff        69582 Aug 29 16:15 /lib/modules/6.18.35-tinycore/modules.dep
tc@hp510:~$ grep "p4-clockmod" /lib/modules/$(uname -r)/modules.dep
kernel/drivers/cpufreq/p4-clockmod.ko.gz: kernel/drivers/cpufreq/speedstep-lib.ko.gz
tc@hp510:~$

[gadget42]

being curious, i did this on a handy devuan system(bare metal if that makes a difference):

Code: [Select]

root@somewhere:/lib/modules/6.1.0-52-amd64/kernel/drivers/cpufreq# uname -a
Linux somewhere 6.1.0-52-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.180-1 (2026-08-03) x86_64 GNU/Linux
root@somewhere:/lib/modules/6.1.0-52-amd64/kernel/drivers/cpufreq# ls -hl /lib/modules/$(uname -r)/modules.dep
-rw-r--r-- 1 root root 515K Aug  5 10:27 /lib/modules/6.1.0-52-amd64/modules.dep
root@somewhere:/lib/modules/6.1.0-52-amd64/kernel/drivers/cpufreq# grep "p4-clockmod" /lib/modules/$(uname -r)/modules.dep
kernel/drivers/cpufreq/p4-clockmod.ko: kernel/drivers/cpufreq/speedstep-lib.ko
root@somewhere:/lib/modules/6.1.0-52-amd64/kernel/drivers/cpufreq# modprobe /lib/modules/6.1.0-52-amd64/kernel/drivers/cpufreq/p4-clockmod.ko
modprobe: FATAL: Module /lib/modules/6.1.0-52-amd64/kernel/drivers/cpufreq/p4-clockmod.ko not found in directory /lib/modules/6.1.0-52-amd64(everything in the cpufreq directory modprobed fatal, just an fyi)

Stefann is not alone...hmmm...

strange/weird.