Good day.
I have found bug in Bionicpup64 8.0 Startup manager. When you choose kernel module to load at startup, the chosen module is not being loaded.
Steps to reproduce:
1. Launch Startup manager and choose Add new module.
2. Add coretemp for example.
3. OK, save session, reboot Puppy.
4. Notice to boot sequence screen, that coretemp seems to be loaded.
5. But, after boot, coretemp is NOT loaded. As result, Psensor and GKrellm does not show CPU temperatures.
I also tried to modify the file /etc/rc.d/MODULESCONFIG, but this gave the same result - coretemp NOT loaded at system startup.
Yes, I know, that there is another way to load kernel modules, but I think, if the supplied utility has bug, it should be reported.
Please fix this bug.
Bionicpup64 8.0 Startup Manager bug
- OscarTalks
- Posts: 2196
- Joined: Mon 06 Feb 2012, 00:58
- Location: London, England
This may not be a bug at all.
The coretemp module may not be able to load (even if you set it in the configuration) because it is not a suitable module for your hardware.
Please try running modprobe coretemp in terminal and post the output.This is on a machine which has AMD and not intel CPU so it is not the correct module for the sensor.
The coretemp module may not be able to load (even if you set it in the configuration) because it is not a suitable module for your hardware.
Please try running modprobe coretemp in terminal and post the output.
Code: Select all
# modprobe coretemp
modprobe: ERROR: could not insert 'coretemp': No such device
#
Oscar in England
Bootmanager problem with temp modules
G'day,
I had this problem a while ago when new Ubuntu Pups were not loading my temperature module via BootManager. I vaguely recall reporting this in a Ubuntu-Pup thread.
However I get around this now in all Pups by adding the appropriate "modprobe xxxxx" line into my /root/StartUp 'mount-at-boot' script file where I already have lines to mount my data partitions:
This is a quicker fix than using the old BootManager for me.
David S.
I had this problem a while ago when new Ubuntu Pups were not loading my temperature module via BootManager. I vaguely recall reporting this in a Ubuntu-Pup thread.
However I get around this now in all Pups by adding the appropriate "modprobe xxxxx" line into my /root/StartUp 'mount-at-boot' script file where I already have lines to mount my data partitions:
My laptop needs the 'coretemp' module so its Startup file has 'coretemp' in place of my desktop's 'smsc47b397' in the above example.#!/bin/sh
mount /dev/sda5 /mnt/sda5
mount /dev/sdb3 /mnt/sdb3
modprobe smsc47b397
This is a quicker fix than using the old BootManager for me.
David S.
Oh, I forgot to post mySystem Information. Here it is.OscarTalks wrote: Please try running modprobe coretemp in terminal and post the output.This is on a machine which has AMD and not intel CPU so it is not the correct module for the sensor.Code: Select all
# modprobe coretemp modprobe: ERROR: could not insert 'coretemp': No such device #
I have Intel Core i3-7100 CPU.
Modprobe coretemp returned nothing in terminal.
But, after running modprobe coretemp in terminal, coretemp loaded.
Also, Bionicpup is installed on USB Flash drive, because I test it for now. The main OS on this PC is Linux Mint 18.3 Sylvia. On Linux Mint, coretemp launches without any problems.
Thank you, davids45. Your script is working well. But still, I think this bug should be fixed.