When upgrading to Kernel 5.4.62-1 getting make.log error on e1000e-3.8.4

When trying to upgrade to kernel 5.4.62-1 in Manjaro Setting I am getting the following error on e1000e-3.8.4.

Make log:

DKMS make.log for e1000e-3.8.4 for kernel 5.4.62-1-MANJARO (x86_64)
Thu Sep 10 20:45:21 EDT 2020
make: Entering directory '/usr/lib/modules/5.4.62-1-MANJARO/build'
make: uname: No such file or directory
make: gcc: No such file or directory
make: make: No such file or directory
make: *** [Makefile:1729: /var/lib/dkms/e1000e/3.8.4/build] Error 127
make: Leaving directory '/usr/lib/modules/5.4.62-1-MANJARO/build'

Laptop Configuration:

System: Kernel: 4.19.143-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0
Desktop: GNOME 3.36.5 Distro: Manjaro Linux
Machine: Type: Laptop System: LENOVO ThinkPad X230 serial:
Mobo: LENOVO model: serial: UEFI [Legacy]: LENOVO

Battery: ID-1: BAT0 charge: 23.1 Wh condition: 34.9/57.7 Wh (60%) model: LGC 45N1025
status: Discharging
CPU: Topology: Dual Core model: Intel Core i5-3320M bits: 64 type: MT MCP arch: Ivy Bridge
rev: 9 L2 cache: 3072 KiB
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 20751
Speed: 1197 MHz min/max: 1200/2600 MHz Core speeds (MHz): 1: 1197 2: 1197 3: 1198
4: 1197
Graphics: Device-1: Intel 3rd Gen Core processor Graphics vendor: Lenovo driver: i915 v: kernel
bus ID: 00:02.0
Device-2: Acer ThinkPad Integrated Camera type: USB driver: uvcvideo bus ID: 1-1.6:5
Display: x11 server: X.Org 1.20.8 driver: intel resolution: 1366x768~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 4000 (IVB GT2) v: 4.2 Mesa 20.1.7
direct render: Yes
Audio: Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Lenovo
driver: snd_hda_intel v: kernel bus ID: 00:1b.0
Sound Server: ALSA v: k4.19.143-1-MANJARO
Network: Device-1: Intel 82579LM Gigabit Network vendor: Lenovo driver: e1000e v: 3.8.4-NAPI
port: 6080 bus ID: 00:19.0
IF: enp0s25 state: down mac:
Device-2: Intel Centrino Advanced-N 6205 [Taylor Peak] driver: iwlwifi v: kernel
port: efa0 bus ID: 03:00.0
IF: wlp3s0 state: up mac:
Drives: Local Storage: total: 465.76 GiB used: 50.97 GiB (10.9%)
ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB
Partition: ID-1: / size: 144.15 GiB used: 50.97 GiB (35.4%) fs: ext4 dev: /dev/sda4
Swap: Alert: No Swap data was found.
Sensors: System Temperatures: cpu: 48.0 C mobo: N/A
Fan Speeds (RPM): cpu: 0
Info: Processes: 207 Uptime: 1h 34m Memory: 11.43 GiB used: 1.45 GiB (12.7%) Init: systemd
Compilers: gcc: 10.2.0 Packages: 1478 Shell: fish v: 3.1.2 inxi: 3.1.05

These are the Kernel Install Logs:

The following packages will be installed:
linux54
linux54-headers
linux54-acpi_call

Starting
resolving dependencies…
looking for conflicting packages…
Packages (3) linux54-5.4.62-1 linux54-acpi_call-1.1.0-70 linux54-headers-5.4.62-1
Total Download Size: 91.70 MiB
Total Installed Size: 187.03 MiB
:: Proceed with installation? [Y/n]
:: Retrieving packages…
downloading linux54-5.4.62-1-x86_64.pkg.tar.zst…
downloading linux54-headers-5.4.62-1-x86_64.pkg.tar.zst…
downloading linux54-acpi_call-1.1.0-70-x86_64.pkg.tar.xz…
checking keyring…
checking package integrity…
loading package files…
checking for file conflicts…
checking available disk space…
:: Processing package changes…
installing linux54…
Optional dependencies for linux54
crda: to set the correct wireless channels of your country [installed]
installing linux54-headers…
installing linux54-acpi_call…

Updating module dependencies…
:: Running post-transaction hooks…
(1/5) Arming ConditionNeedsUpdate…
(2/5) Updating module dependencies…
(3/5) Install DKMS modules
==> dkms install --no-depmod -m e1000e -v 3.8.4 -k 5.4.62-1-MANJARO
Error! Bad return status for module build on kernel: 5.4.62-1-MANJARO (x86_64)
Consult /var/lib/dkms/e1000e/3.8.4/build/make.log for more information.
==> Warning, `dkms install --no-depmod -m e1000e -v 3.8.4 -k 5.4.62-1-MANJARO’ returned 10
==> depmod 5.4.62-1-MANJARO
(4/5) Updating linux initcpios…
==> Building image from preset: /etc/mkinitcpio.d/linux54.preset: ‘default’
-> -k /boot/vmlinuz-5.4-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.4-x86_64.img
==> Starting build: 5.4.62-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [systemd]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.4-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux54.preset: ‘fallback’
-> -k /boot/vmlinuz-5.4-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.4-x86_64-fallback.img -S autodetect
==> Starting build: 5.4.62-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [systemd]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.4-x86_64-fallback.img
==> Image generation successful
(5/5) Updating Grub-Bootmenu
Generating grub configuration file …
Found background: /usr/share/grub/background.png
Found linux image: /boot/vmlinuz-5.4-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.4-x86_64.img
Found initrd fallback image: /boot/initramfs-5.4-x86_64-fallback.img
Found linux image: /boot/vmlinuz-4.19-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.19-x86_64.img
Found initrd fallback image: /boot/initramfs-4.19-x86_64-fallback.img
Found Windows 10 on /dev/sda1
Found Windows 7 on /dev/sda2
Found Manjaro Linux (20.1) on /dev/sda4
Found memtest86+ image: /boot/memtest86+/memtest.bin
done

Question, any ideas how to address the error?

That basically means that it didn’t find the tools to make it.

Could go to this dir and post what is there on line 1729 ?

I went to the /var/lib/dkms/e1000e/3.8.4/build directory and opened the Make file. There are 156 lines in the file.

Makefile contents:

SPDX-License-Identifier: GPL-2.0

Copyright© 1999 - 2020 Intel Corporation.

#ifndef REMOVE_COMPAT
ifneq ($(KERNELRELEASE),)

kbuild part of makefile

#endif /* REMOVE_COMPAT */

Makefile for the @SUMMARY@

obj-$(CONFIG_E1000E) += e1000e.o

define e1000e-y
netdev.o
ethtool.o
ich8lan.o
mac.o
nvm.o
phy.o
manage.o
80003es2lan.o
82571.o
param.o
endef
e1000e-y := $(strip ${e1000e-y})

#ifdef BUILD_PTP_SUPPORT
e1000e-$(CONFIG_PTP_1588_CLOCK:m=y) += ptp.o
#endif

#ifndef REMOVE_COMPAT

e1000e-y += kcompat.o

else # ifneq($(KERNELRELEASE),)

normal makefile

DRIVER := e1000e

ifeq (,$(wildcard common.mk))
$(error Cannot find common.mk build rules)
else
include common.mk
endif

Check that kernel version is at least 2.4.17

ifeq (0,$(shell [ ${KVER_CODE} -lt $(call get_kvercode,2,4,17) ]; echo “$?”))
$(warning *** Aborting the build.)
$(error This driver is not supported on kernel versions older than 2.4.17)
endif

######################

Kernel Build Macro

######################

customized kernelbuild function

${1} is the kernel build target

${2} may contain extra rules to pass to kernelbuild macro

We customize the kernelbuild target in order to provide our hack to disable

CONFIG_PTP_1588_CLOCK support should -DNO_PTP_SUPPORT be defined in the extra

cflags given on the command line.

devkernelbuild = $(call kernelbuild,$(if $(filter -DNO_PTP_SUPPORT,${EXTRA_CFLAGS}),CONFIG_PTP_1588_CLOCK=n) ${2},${1})

###############

Build rules

###############

Standard compilation, with regular output

default:
@+$(call devkernelbuild,modules)

Noisy output, for extra debugging

noisy:
@+$(call devkernelbuild,modules,V=1)

Silence any output generated

silent:
@+$(call devkernelbuild,modules,>/dev/null)

Enable higher warning level

checkwarnings: clean
@+$(call devkernelbuild,modules,W=1)

Run sparse static analyzer

sparse: clean
@+$(call devkernelbuild,modules,C=2 CF="-D__CHECK_ENDIAN__ -Wbitwise -Wcontext")

Run coccicheck static analyzer

ccc: clean
@+$(call devkernelbuild,modules,coccicheck MODE=report))

Build manfiles

manfile:
@gzip -c …/${DRIVER}.${MANSECTION} > ${DRIVER}.${MANSECTION}.gz

Clean the module subdirectories

clean:
@+$(call devkernelbuild,clean)
@-rm -rf *.${MANSECTION}.gz *.ko

Install the modules and manpage

install: default manfile
@echo “Copying manpages…”
@install -D -m 644 ${DRIVER}.${MANSECTION}.gz ${INSTALL_MOD_PATH}${MANDIR}/man${MANSECTION}/${DRIVER}.${MANSECTION}.gz
@echo “Installing modules…”
@+$(call devkernelbuild,modules_install)
@echo “Running depmod…”
@$(call cmd_depmod)

Target used by rpmbuild spec file

rpm: default manfile
@install -D -m 644 ${DRIVER}.${MANSECTION}.gz ${INSTALL_MOD_PATH}${MANDIR}/man${MANSECTION}/${DRIVER}.${MANSECTION}.gz
@install -D -m 644 ${DRIVER}.ko ${INSTALL_MOD_PATH}/lib/modules/${KVER}/${INSTALL_MOD_DIR}/${DRIVER}.ko

uninstall:
rm -f ${INSTALL_MOD_PATH}/lib/modules/${KVER}/${INSTALL_MOD_DIR}/${DRIVER}.ko;
$(call cmd_depmod)
if [ -e ${INSTALL_MOD_PATH}${MANDIR}/man${MANSECTION}/${DRIVER}.${MANSECTION}.gz ] ; then
rm -f ${INSTALL_MOD_PATH}${MANDIR}/man${MANSECTION}/${DRIVER}.${MANSECTION}.gz ;
fi;

########

Help

########
help:
@echo ‘Cleaning targets:’
@echo ’ clean - Clean files generated by kernel module build’
@echo ‘Build targets:’
@echo ’ default - Build module(s) with standard verbosity’
@echo ’ noisy - Build module(s) with V=1 verbosity – very noisy’
@echo ’ silent - Build module(s), squelching all output’
@echo ‘Static Analysis:’
@echo ’ checkwarnings - Clean, then build module(s) with W=1 warnings enabled’
@echo ’ sparse - Clean, then check module(s) using sparse’
@echo ’ ccc - Clean, then check module(s) using coccicheck’
@echo ‘Other targets:’
@echo ’ manfile - Generate a gzipped manpage’
@echo ’ install - Build then install the module(s) and manpage’
@echo ’ uninstall - Uninstall the module(s) and manpage’
@echo ’ help - Display this help message’
@echo ‘Variables:’
@echo ’ LINUX_VERSION - Debug tool to force kernel LINUX_VERSION_CODE. Use at your own risk.’
@echo ’ W=N - Kernel variable for setting warning levels’
@echo ’ V=N - Kernel variable for setting output verbosity’
@echo ’ INSTALL_MOD_PATH - Add prefix for the module and manpage installation path’
@echo ’ INSTALL_MOD_DIR - Use module directory other than updates/drivers/net/ethernet/intel/${DRIVER}’
@echo ’ Other variables may be available for tuning make process, see’
@echo ’ Kernel Kbuild documentation for more information’

.PHONY: default noisy clean manfile silent sparse ccc install uninstall help

endif # ifneq($(KERNELRELEASE),)
#endif /* REMOVE_COMPAT */

By reading this: AUR (en) - e1000e-dkms there have been made changes to kernel. I guess until the module is not corrected, it will not work with newer kernels.

Btw… isn’t that driver integrated into linux 5.4 ?

Have look here: kernel/git/stable/linux.git - Linux kernel stable tree

1 Like

Hi Megavolt,

Thanks for your recommendations\observations. To be honest I don’t tend to change my kernel unless I am re-installing my OS. I only pursued this direction to try to learn more about Linux and also try to do some testing before upgrading my daily driver.

As I am reviewing the patch notes now. I’m not sure how to tell if the e1000e driver has been integrated in the kernel?

I did follow the driver notes to source forge and it looks like amongst the bugs was 665 which seems to be related to what I experienced.

https://sourceforge.net/p/e1000/bugs/665/

To check if it is integrated, just run:

modprobe e1000e && lsmod | grep "e1000e"

If it can be loaded and is displayed, then it should be there.

Just to clarify to complete the test:

modprobe e1000e && lsmod | grep "e1000e
  1. Uninstall e1000e-dkms driver that was sourced from the AUR.

  2. Install the Kernel 5.4.62-1

  3. Then after reboot run the following command from terminal:

"modprobe e1000e && lsmod | grep “e1000e”

Additional Question:

Does it make sense to do this test knowing the bug I mentioned in the previous post?

1 Like

Cause of these errors at the link it has not been build. Therefore it should not get loaded.

I removed the Intel e1000e and the LAN card is still working at the 4.19 kernel.

modprobe e1000e && lsmod | grep "e1000e"
e1000e                294912  0

I did switch to the 5.4.62-1 and my LAN is still working. The only item I am trying to figure out is when my system boots up I can see something “Failed” in red, but it goes by so quickly I can’t read the message.

I’m trying to use the journalctl -r command to see if I can find what failed during boot. Any recommendations on how I might tune that command?

This is what I found so far:

journalctl -r | grep failed | more

Sep 11 22:21:27 mani dbus-daemon[820]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedes
ktop.Avahi.service not found.
Sep 11 22:09:59 mani NetworkManager[821]: <info>  [1599876599.8533] device (wlp3s0): ipv6: duplicate address check failed for the fe80::86ea:882a:
f451:3e44/64 lft forever pref forever lifetime 402-0[4294967295,4294967295] dev 3 flags permanent,tentative src kernel address

Thanks.

This could help:

journalctl -b -0 --grep="failed|Failed"

This is what I have found so far:

journalctl -r -b -0 --grep="failed|Failed"
-- Logs begin at Fri 2020-08-14 13:53:02 EDT, end at Fri 2020-09-11 22:37:52 EDT. --
Sep 11 22:37:29 mani seahorse[2444]: DNS-SD initialization failed: Daemon not running
Sep 11 22:37:29 mani dbus-daemon[789]: [system] Activation via systemd failed for unit 'dbus-org.fr>
Sep 11 22:37:23 mani gsd-color[2192]: failed to connect to device: Failed to connect to missing dev>
Sep 11 22:37:20 mani gnome-shell[1437]: Failed to set CRTC gamma: drmModeCrtcSetGamma on CRTC 42 fa>
Sep 11 22:37:20 mani gsd-media-keys[2202]: Failed to grab accelerator for keybinding settings:playb>
Sep 11 22:37:20 mani gsd-media-keys[2202]: Failed to grab accelerator for keybinding settings:rfkill
Sep 11 22:37:20 mani gsd-media-keys[2202]: Failed to grab accelerator for keybinding settings:hiber>
Sep 11 22:37:20 mani gsd-media-keys[2202]: Failed to grab accelerator for keybinding settings:playb>
Sep 11 22:37:20 mani gnome-shell[1437]: Failed to set CRTC gamma: drmModeCrtcSetGamma on CRTC 42 fa>
Sep 11 22:37:19 mani dbus-daemon[789]: [system] Activation via systemd failed for unit 'dbus-org.fr>
Sep 11 22:37:19 mani gnome-shell[1982]: Failed to load background 'file:///home/rsruser/.local/shar>
Sep 11 22:37:17 mani gnome-shell[1982]: Failed to launch ibus-daemon: Failed to execute child proce>
Sep 11 22:37:14 mani /usr/lib/gdm-x-session[1897]: xf86EnableIOPorts: failed to set IOPL for I/O (O>
Sep 11 22:37:14 mani /usr/lib/gdm-x-session[1897]: (WW) Open ACPI failed (/var/run/acpid.socket) (N>
Sep 11 22:37:14 mani /usr/lib/gdm-x-session[1897]: (WW) Failed to open protocol names file lib/xorg>
Sep 11 22:37:14 mani kernel: audit: type=1103 audit(1599878234.086:131): pid=1878 uid=0 auid=429496>
Sep 11 22:37:14 mani audit[1878]: CRED_ACQ pid=1878 uid=0 auid=4294967295 ses=4294967295 subj==unco>
Sep 11 22:37:14 mani dbus-daemon[789]: [system] Activation via systemd failed for unit 'dbus-org.fr>
Sep 11 22:37:14 mani dbus-daemon[789]: [system] Activation via systemd failed for unit 'dbus-org.fr>
Sep 11 22:37:12 mani kernel: audit: type=1112 audit(1599878232.236:124): pid=1816 uid=0 auid=429496>
Sep 11 22:37:12 mani audit[1816]: USER_LOGIN pid=1816 uid=0 auid=4294967295 ses=4294967295 subj==un>
Sep 11 22:37:09 mani kernel: audit: type=1100 audit(1599878229.946:123): pid=1816 uid=0 auid=429496>
Sep 11 22:37:09 mani audit[1816]: USER_AUTH pid=1816 uid=0 auid=4294967295 ses=4294967295 subj==unc>
Sep 11 22:37:08 mani dbus-daemon[789]: [system] Activation via systemd failed for unit 'dbus-org.fr>
Sep 11 22:37:07 mani dbus-daemon[789]: [system] Activation via systemd failed for unit 'dbus-org.fr>
Sep 11 22:37:05 mani gsd-sharing[1592]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBu>
Sep 11 22:37:05 mani gsd-sharing[1592]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBu>
Sep 11 22:37:05 mani gsd-sharing[1592]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBu>
Sep 11 22:37:05 mani /usr/lib/gdm-wayland-session[1374]: dbus-daemon[1374]: [session uid=120 pid=13>
Sep 11 22:37:05 mani dbus-daemon[789]: [system] Activation via systemd failed for unit 'dbus-org.fr>
Sep 11 22:37:05 mani gnome-shell[1437]: Failed to launch ibus-daemon: Failed to execute child proce>
Sep 11 22:37:05 mani gsd-media-keys[1613]: Failed to grab accelerator for keybinding settings:rfkill
Sep 11 22:37:05 mani gsd-media-keys[1613]: Failed to grab accelerator for keybinding settings:playb>
Sep 11 22:37:05 mani gsd-media-keys[1613]: Failed to grab accelerator for keybinding settings:playb>
Sep 11 22:37:05 mani gsd-media-keys[1613]: Failed to grab accelerator for keybinding settings:hiber>
Sep 11 22:37:03 mani gsd-sharing[1592]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBu>
Sep 11 22:37:03 mani gsd-sharing[1592]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBu>
Sep 11 22:37:03 mani gsd-sharing[1592]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBu>
Sep 11 22:37:03 mani /usr/lib/gdm-wayland-session[1374]: dbus-daemon[1374]: [session uid=120 pid=13>
Sep 11 22:37:03 mani dbus-daemon[789]: [system] Activation via systemd failed for unit 'dbus-org.fr>
Sep 11 22:37:02 mani geoclue[1579]: Failed to connect to avahi service: Daemon not running
Sep 11 22:37:02 mani dbus-daemon[789]: [system] Activation via systemd failed for unit 'dbus-org.fr>
Sep 11 22:37:01 mani gnome-shell[1437]: Failed to launch ibus-daemon: Failed to execute child proce>
Sep 11 22:37:00 mani /usr/lib/gdm-wayland-session[1374]: dbus-daemon[1374]: [session uid=120 pid=13>
Sep 11 22:37:00 mani /usr/lib/gdm-wayland-session[1374]: dbus-daemon[1374]: [session uid=120 pid=13>
Sep 11 22:37:00 mani /usr/lib/gdm-wayland-session[1374]: dbus-daemon[1374]: [session uid=120 pid=13>
Sep 11 22:37:00 mani /usr/lib/gdm-wayland-session[1374]: dbus-daemon[1374]: [session uid=120 pid=13>
Sep 11 22:36:59 mani /usr/lib/gdm-wayland-session[1374]: dbus-daemon[1374]: [session uid=120 pid=13>
Sep 11 22:36:59 mani /usr/lib/gdm-wayland-session[1374]: dbus-daemon[1374]: [session uid=120 pid=13>
Sep 11 22:36:59 mani /usr/lib/gdm-wayland-session[1374]: dbus-daemon[1374]: [session uid=120 pid=13>
Sep 11 22:36:59 mani /usr/lib/gdm-wayland-session[1374]: dbus-daemon[1374]: [session uid=120 pid=13>
Sep 11 22:36:58 mani audit[1185]: CRED_ACQ pid=1185 uid=0 auid=4294967295 ses=4294967295 subj==unco>
Sep 11 22:36:58 mani dbus-daemon[789]: [system] Activation via systemd failed for unit 'dbus-org.fr>
Sep 11 22:36:58 mani wpa_supplicant[1100]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa>
Sep 11 22:36:58 mani kernel: bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0a5c-21e6.hcd>
Sep 11 22:36:56 mani audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj==uncon>
Sep 11 22:36:56 mani systemd[1]: Failed to start simple and lightweight fan control program.
Sep 11 22:36:56 mani systemd[1]: thinkfan.service: Failed with result 'exit-code'.
Sep 11 22:36:56 mani systemd[1]: nordvpnd.socket: TCP_NODELAY failed: Operation not supported
Sep 11 22:36:55 mani systemd-udevd[388]: controlC0: Process '/usr/bin/alsactl restore 0' failed wit>
Sep 11 22:36:54 mani systemd-udevd[408]: cfg80211: Process '/usr/bin/set-wireless-regdom' failed wi>
Sep 11 22:36:54 mani kernel: acpi_call: module verification failed: signature and/or required key m>
Sep 11 18:36:50 manjaro kernel: acpi PNP0A08:00: _OSC failed (AE_SUPPORT); disabling ASPM

There is nothing about the e1000e module. Still there are some other errors which don’t fit this topic. Feel free to create a new one.

btw the log is cut off at the right side with “>”. If your terminal is too small, better run it like this:

journalctl -b -0 --grep="failed|Failed" | cat

@megavolt

Looks like it is the thinkfan software. I disabled it and the red error is gone. So guess I will be researching if that has issues:

systemctl status thinkfan.service                                                1 
● thinkfan.service - simple and lightweight fan control program
	 Loaded: loaded (/usr/lib/systemd/system/thinkfan.service; disabled; vendor preset: disabled)
	Drop-In: /etc/systemd/system/thinkfan.service.d
	         └─override.conf
	 Active: failed (Result: exit-code) since Fri 2020-09-11 22:47:08 EDT; 8s ago
	Process: 2614 ExecStart=/usr/bin/thinkfan $THINKFAN_ARGS (code=exited, status=1/FAILURE)

Sep 11 22:47:08 mani systemd[1]: Starting simple and lightweight fan control program...
Sep 11 22:47:08 mani thinkfan[2614]: ERROR: /sys/devices/platform/coretemp.0/hwmon/hwmon2/temp3_inp>
Sep 11 22:47:08 mani systemd[1]: thinkfan.service: Control process exited, code=exited, status=1/FA>
Sep 11 22:47:08 mani systemd[1]: thinkfan.service: Failed with result 'exit-code'.
Sep 11 22:47:08 mani systemd[1]: Failed to start simple and lightweight fan control program.
lines 1-12/12 (END)
1 Like

Thanks for all your help. I learned allot.

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.