This issue makes it annoying to load watchdog drivers, as systemd now
supports hardware watchdogs they'd have to be added to rc.local or a
custom service. The pre-systemd behaviour only applied the blacklist
with udev, not when processing /etc/modules(-load.d) so that they could
be prevented from
Any news about this? it seems all watchdog modules are blacklisted
unless the watchdog daemon is installed and one module is enabled in
/etc/default/watchdog. With basic watchdog functionality already enabled
in systemd shouldn't this be changed to support it?
--
You received this bug notificatio
To get this working on 18.04, delete all the blacklisted module name
from /lib/modprobe.d/*.conf
Then, add the module name to `/etc/modules-load.d/myfoo-module.conf`.
After that three things are needed:
$ sudo update-initramfs -u
$ sudo depmod -a
$ sudo systemctl reboot
--
You received this bu
In my case I'm trying to get softdog to load for SBD instead of the
watchdog daemon.
I can see the point of marking it as opinion, but as Olivier points out,
you have to eliminate the blacklist entry from all of the blacklists
spammed into /lib/modprobe.d, systemd-modules-load does not discriminat
Issue still exists in 18.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1535840
Title:
systemd ignoring /etc/modules due to blacklist
To manage notifications about this bug go to:
https://bugs.l
This problem still exists.
The problem is that these modules are listed in the blacklist files
provided with the kernel(/lib/modprobe.d/blacklist_linux-*.conf). Given
that these files aren't located in /etc they apparently are not
configuration files. Also very new kernel package you get a new fil
** Changed in: systemd (Ubuntu)
Status: Confirmed => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1535840
Title:
systemd ignoring /etc/modules due to blacklist
To manage notificatio
I tried that but I had no success.
I now have the /etc/init.d/watchdog start in /etc/rc.local (systemctl
did not worked that way) and so start using that
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Same problem here, once you have removed the modules from every
blacklist files, you must update initramfs:
$ sudo update-initramfs -u
Then, it works ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
I also have this problem and it is stupid to have watchdog started
manually using systemd after each (re)boot to work.
I have removed all blacklist-entries for iTCO_wdt and also rebuild
initramfs ... but it still says at boot that module is blacklisted ...
:-(
--
You received this bug notificati
I'm having the same issue. In fact, removing iTCO_wdt from all
blacklists doesn't solve the problem. At the boot I still get:
systemd-modules-load[365]: Module 'iTCO_wdt' is blacklisted
Adding the following to /etc/modprobe.d/watchdog.conf doesn't help
either:
install /sbin/modprobe iTCO_wdt
--
Thanks for the tip, will try that. What is extremely frustrating is that
to unblacklist a module you have to edit 4 different, some dynamic
files. I don't really get how such poor design could ever be validated.
Maybe we're missing something (systemd config?).
```
# Blacklists that must be edited
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1535840
Title:
sy
Generally me work-around so far has been to avoid systemd!
However, where that is not an option you might be able to edit
/etc/default/watchdog so the module is loaded on watchdog start-up. It is not
ideal as you might have some other reasons for wanting the /dev/watchdog
virtual file to be test
I'm having the exact same issue, can't load watchdog TCO-related modules
because they are blacklisted.
Did you find any workaround?
I don't want to mess with the blacklist list.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
15 matches
Mail list logo
