[SOLVED] Starting kmod fails with an error

All Gurus once were Newbies
Forum rules
There are no such things as "stupid" questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Please stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions prefer the other forums within the support section.
Before you post please read how to get help
Post Reply
User avatar
ineuw
Level 3
Level 3
Posts: 159
Joined: Sun Nov 13, 2016 12:27 am
Location: Canada

[SOLVED] Starting kmod fails with an error

Post by ineuw » Fri May 25, 2018 2:06 pm

After going through the process of setting up the temperature sensors, using "sudo sensors-detect" as outlined https://askubuntu.com/questions/15832/h ... emperature and restarted the desktop, I got the following error.

ineuw@desktop32 ~ $ sudo /etc/init.d/kmod start
[....] Starting kmod (via systemctl): kmod.serviceJob for systemd-modules-load.service failed because the control process exited with error code. See "systemctl status systemd-modules-load.service" and "journalctl -xe" for details.
failed!


Then I got,

ineuw@desktop32 ~ $ systemctl status systemd-modules-load.service
● systemd-modules-load.service - Load Kernel Modules
Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static; vendor preset:
Active: failed (Result: exit-code) since Fri 2018-05-25 14:03:52 EDT; 3min 27s ago
Docs: man:systemd-modules-load.service(8)
man:modules-load.d(5)
Process: 8202 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
Main PID: 8202 (code=exited, status=1/FAILURE)

May 25 14:03:51 desktop32 systemd[1]: Starting Load Kernel Modules...
May 25 14:03:52 desktop32 systemd[1]: systemd-modules-load.service: Main process exited, cod
May 25 14:03:52 desktop32 systemd[1]: Failed to start Load Kernel Modules.
May 25 14:03:52 desktop32 systemd[1]: systemd-modules-load.service: Unit entered failed stat
May 25 14:03:52 desktop32 systemd[1]: systemd-modules-load.service: Failed with result 'exit
lines 1-13/13 (END)...skipping...
● systemd-modules-load.service - Load Kernel Modules
Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2018-05-25 14:03:52 EDT; 3min 27s ago
Docs: man:systemd-modules-load.service(8)
man:modules-load.d(5)
Process: 8202 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
Main PID: 8202 (code=exited, status=1/FAILURE)

May 25 14:03:51 desktop32 systemd[1]: Starting Load Kernel Modules...
May 25 14:03:52 desktop32 systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
May 25 14:03:52 desktop32 systemd[1]: Failed to start Load Kernel Modules.
May 25 14:03:52 desktop32 systemd[1]: systemd-modules-load.service: Unit entered failed state.
May 25 14:03:52 desktop32 systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.

ineuw@desktop32 ~ $ journalctl -xe
May 25 13:57:47 desktop32 systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
May 25 13:57:47 desktop32 systemd[1]: Failed to start Load Kernel Modules.
-- Subject: Unit systemd-modules-load.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li ... temd-devel
--
-- Unit systemd-modules-load.service has failed.
--
-- The result is failed.
May 25 13:57:47 desktop32 systemd[1]: systemd-modules-load.service: Unit entered failed state.
May 25 13:57:47 desktop32 systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
May 25 13:57:47 desktop32 sudo[7886]: pam_unix(sudo:session): session closed for user root
May 25 13:57:59 desktop32 ntpd[1080]: 159.203.8.72 local addr 192.168.1.68 -> <null>
May 25 13:58:20 desktop32 ntpd[1080]: 144.217.65.183 local addr 192.168.1.68 -> <null>
May 25 13:58:23 desktop32 ntpd[1080]: 206.108.0.134 local addr 192.168.1.68 -> <null>
May 25 13:59:11 desktop32 kernel: [UFW BLOCK] IN=wlxe84e0639ec84 OUT= MAC=01:00:5e:00:00:01:e0:b9:e5:22:05:ba:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=23801 DF PROTO=2
May 25 14:01:16 desktop32 kernel: [UFW BLOCK] IN=wlxe84e0639ec84 OUT= MAC=01:00:5e:00:00:01:e0:b9:e5:22:05:ba:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=23904 DF PROTO=2
May 25 14:02:21 desktop32 wpa_supplicant[1243]: wlxe84e0639ec84: WPA: Group rekeying completed with e0:b9:e5:22:05:bb [GTK=TKIP]
May 25 14:03:21 desktop32 kernel: [UFW BLOCK] IN=wlxe84e0639ec84 OUT= MAC=01:00:5e:00:00:01:e0:b9:e5:22:05:ba:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=24146 DF PROTO=2
May 25 14:03:51 desktop32 sudo[8169]: ineuw : TTY=pts/1 ; PWD=/home/ineuw ; USER=root ; COMMAND=/usr/sbin/service kmod start
May 25 14:03:51 desktop32 sudo[8169]: pam_unix(sudo:session): session opened for user root by (uid=0)
May 25 14:03:51 desktop32 systemd[1]: Starting Load Kernel Modules...
-- Subject: Unit systemd-modules-load.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li ... temd-devel
--
-- Unit systemd-modules-load.service has begun starting up.
May 25 14:03:51 desktop32 kernel: w83627ehf: Found W83627DHG chip at 0x290
May 25 14:03:51 desktop32 kernel: ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\_SB.PCI0.SBRG.SIOR.HWRE) (20170531/utaddr
May 25 14:03:51 desktop32 kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
May 25 14:03:52 desktop32 systemd-modules-load[8202]: Failed to insert 'w83627ehf': Device or resource busy
May 25 14:03:52 desktop32 systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
May 25 14:03:52 desktop32 systemd[1]: Failed to start Load Kernel Modules.
-- Subject: Unit systemd-modules-load.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li ... temd-devel
--
-- Unit systemd-modules-load.service has failed.
--
-- The result is failed.
May 25 14:03:52 desktop32 systemd[1]: systemd-modules-load.service: Unit entered failed state.
May 25 14:03:52 desktop32 systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
May 25 14:03:52 desktop32 sudo[8169]: pam_unix(sudo:session): session closed for user root
May 25 14:04:37 desktop32 ntpd[1080]: 209.115.181.108 local addr 192.168.1.68 -> <null>
May 25 14:05:26 desktop32 kernel: [UFW BLOCK] IN=wlxe84e0639ec84 OUT= MAC=01:00:5e:00:00:01:e0:b9:e5:22:05:ba:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=24484 DF PROTO=2
May 25 14:06:17 desktop32 kernel: perf: interrupt took too long (5041 > 4931), lowering kernel.perf_event_max_sample_rate to 39500
May 25 14:07:31 desktop32 kernel: [UFW BLOCK] IN=wlxe84e0639ec84 OUT= MAC=01:00:5e:00:00:01:e0:b9:e5:22:05:ba:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=24738 DF PROTO=2
May 25 14:09:37 desktop32 kernel: [UFW BLOCK] IN=wlxe84e0639ec84 OUT= MAC=01:00:5e:00:00:01:e0:b9:e5:22:05:ba:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=24977 DF PROTO=2
lines 2441-2488/2488 (END)
ineuw@desktop32 ~ $
Last edited by ineuw on Sat Jun 02, 2018 8:31 pm, edited 1 time in total.
Linux Mint 18.3 desktop & on a Macbook 3.1 laptop, both 64 bit.

Mute Ant
Level 13
Level 13
Posts: 4785
Joined: Tue Sep 03, 2013 7:45 pm

Re: Starting kmod fails with an error

Post by Mute Ant » Sat May 26, 2018 3:37 am

On a completely non-Mint system, with no systemd, you have to start the service-things manually and it just works...
mute@devuan:~$ cd /etc/init.d
mute@devuan:/etc/init.d$ sudo ./kmod start
[info] Loading kernel module lp.
[info] Loading kernel module ppdev.
[info] Loading kernel module parport_pc.

I don't get the error you get... Failed to insert 'w83627ehf': Device or resource busy ...which might hint at the problem... what module is your code asking for that a plain-vanilla Linux doesn't need?
In Chapter One, Boron slays the entire Marketing Department by explaining Asynchronous Protocols.

User avatar
ineuw
Level 3
Level 3
Posts: 159
Joined: Sun Nov 13, 2016 12:27 am
Location: Canada

Re: Starting kmod fails with an error

Post by ineuw » Sat May 26, 2018 6:33 pm

Mute Ant wrote:
Sat May 26, 2018 3:37 am
On a completely non-Mint system, with no systemd, you have to start the service-things manually and it just works...
mute@devuan:~$ cd /etc/init.d
mute@devuan:/etc/init.d$ sudo ./kmod start
[info] Loading kernel module lp.
[info] Loading kernel module ppdev.
[info] Loading kernel module parport_pc.

I don't get the error you get... Failed to insert 'w83627ehf': Device or resource busy ...which might hint at the problem... what module is your code asking for that a plain-vanilla Linux doesn't need?
Mute Ant, thanks for the reply, and please don't waste your time with this. Ended up installing xsensors and got what I wanted, a GUI app to monitor the temp. What you see was the end of a series of errors that cropped up while trying out various apps.
Linux Mint 18.3 desktop & on a Macbook 3.1 laptop, both 64 bit.

Post Reply

Return to “Newbie Questions”