Insert module permanently or on every boot?

Hi folks, I recently ‘deployed’ a new mainboard, which naturally has a different BIOS and set-up to my old one. Running ‘sensors’ with the new one does not give much info.

sp 09:51:~> 
sensors
radeon-pci-0200
Adapter: PCI adapter
temp1:        +29.0°C  (crit = +120.0°C, hyst = +90.0°C)
k8temp-pci-00c3
Adapter: PCI adapter
Core0 Temp:   +31.0°C  
Core0 Temp:   +36.0°C  
Core1 Temp:   +29.0°C  
Core1 Temp:   +34.0°C  

But if I:

# modprobe nct6775

I get much more info.

sensors
radeon-pci-0200
Adapter: PCI adapter
temp1:        +29.0°C  (crit = +120.0°C, hyst = +90.0°C)

k8temp-pci-00c3
Adapter: PCI adapter
Core0 Temp:   +31.0°C  
Core0 Temp:   +36.0°C  
Core1 Temp:   +28.0°C  
Core1 Temp:   +33.0°C  

nct6776-isa-0290
Adapter: ISA adapter
Vcore:          +1.31 V  (min =  +0.00 V, max =  +1.74 V)
in1:            +1.84 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
AVCC:           +3.33 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
+3.3V:          +3.33 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in4:            +2.02 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in5:            +1.69 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in6:            +2.02 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
3VSB:           +3.46 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
Vbat:           +3.38 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
fan1:             0 RPM  (min =    0 RPM)
fan2:          1171 RPM  (min =    0 RPM)
fan3:             0 RPM  (min =    0 RPM)
SYSTIN:         +28.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor = thermistor
CPUTIN:         +39.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
AUXTIN:         -59.0°C  (high = +101.0°C, hyst = +101.0°C)  sensor = thermistor
PCH_CHIP_TEMP:   +0.0°C  
PCH_CPU_TEMP:    +0.0°C  
PCH_MCH_TEMP:    +0.0°C  
intrusion0:    ALARM
intrusion1:    ALARM
beep_enable:   disabled

AFAICS, other distros put a line in /etc/modules or /etc/modprobe.conf. I do not have either file. Do I simply create one of the above and put the driver in there? Or does openSuse have its own way of doing this?

Add it to /etc/modprobe.d/99-local.conf

Hi,

If you are on 13.x release then systemd is in charge most probably, that said see

man 5 modules-load.d

something like

printf '%s
' '# load nct6775 at boot' 'nct6775' > nct6775.conf

Thanks guys. I am very dim. I put the line nct6775 in to /etc/modprobe.d/99-local.conf, rebooted, and then did lsmod and sensors. No sign of the module being loaded. I have googled about, and can’t find an example of a populated 99-local.conf file, so I do not know the syntax… Should I have put

install nct6775

in there?

It should run the files in alphabetical order. Note that the file should permissions should be set as other files in the directory.

If you have not done so, since the hardware change, try running:


# mkinitrd

I reinstalled 13.2 after the changes…

On 2015-01-31 11:06, wakou wrote:
>
> Hi folks, I recently ‘deployed’ a new mainboard, which naturally has a
> different BIOS and set-up to my old one. Running ‘sensors’ with the new
> one does not give much info.

There is a “sensors-detect” script that should tell you what to do.

> AFAICS, other distros put a line in /etc/modules or /etc/modprobe.conf.
> I do not have either file. Do I simply create one of the above and put
> the driver in there? Or does openSuse have its own way of doing this?

Because if a module doesn’t load automatically, it is a bug. That file
should be empty or missing in a proper distro. So they say :slight_smile:


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

Thanks Robin, I have run sensors-detect. Which is how I found the module nct6775 . But it does not get loaded, I have to modprobe it. I want it to load on boot.

sensors-detect should offer you to store the configuration to /etc/sysconfig/sensors.
This is then read on boot by lm_sensors.service and the configured modules will be loaded by it.

You might have to enable lm_sensors.service manually though:

sudo systemctl enable lm_sensors

Even this should be done automatically by sensors-detect, but after a quick glimpse at the script it seems to look for the lm_sensors.service in the wrong path.

Yes, that’s right. However, it is still necessary to do

systemctl enable lm_sensors

and start it with

systemctl start lm_sensors

Because if a module doesn’t load automatically, it is a bug. That file
should be empty or missing in a proper distro. So they say :slight_smile:

Not quite. That really only applies to hardware buses/ports supporting PNP hardware. Some of the sensor hardware is apparently attached to legacy ISA buses. The ‘sensor-detect’ utility probes for such hardware. The program probes a number of different buses and mentions

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):
Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no):

You can enable lm_sensors in the yast2-services manager
provided it is installed.

The thread is actually about the OP wanting the 'nct6775 driver to load automatically. (This driver supports particular Nuvuton chipsets used for temperature monitoring.)

I know, I was just commenting regarding lm_sensors.:expressionless:
Because you can activate and enable it thereto run at boot
which is what I did.

Thanks Conram and Deano. I have enabled the service in YAST, and lm_sensors now loads the module for me. I am still none the wiser as to exactly how to do this myself, but it now works, and calling ># sensors reports the info.

Thanks for the update wakou.