Package Details: modprobed-db 2.41-1

Git Clone URL: (read-only, click to copy)
Package Base: modprobed-db
Description: Keeps track of EVERY kernel module ever used - useful for those of us who make localmodconfig :)
Upstream URL:
Licenses: MIT
Conflicts: modprobed_db
Replaces: modprobed_db
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 218
Popularity: 2.47
First Submitted: 2013-11-15 22:21
Last Updated: 2019-08-24 13:16

Dependencies (2)

Required by (13)

Sources (1)

Latest Comments

1 2 3 4 5 6 ... Next › Last »

bugsmanagement commented on 2018-11-25 02:28


Ahh, look over once more, the magic happens here:

"sort -k 1,1 "$DB" /tmp/.inmem | uniq > /tmp/.potential_new_db"

Missed it the first time and focused a bit too much on "cp /tmp/.potential_new_db "$DB"" :)

graysky commented on 2018-11-23 11:10

@bugsmanagement - It does not overwrite. Try the experiment: load your module, update, rmmod, update. It's still there.

bugsmanagement commented on 2018-11-22 22:20

Forgive me for my lack of understanding, but looking over your script, it appears to me that it overwrites than updates the database? What I worry about, ie, I connect to my VPN provider, which accordingly loads the tun module, modprobed-db updates the database. Coincidentally after reboot, tun module is not loaded, modprobed-db then polls, see no tun module, and overwrites the database omitting the tun module?

graysky commented on 2015-09-21 08:28

Ha, no entry for flavor so but it does show you example usage.

artafinde commented on 2015-09-21 08:13

--> The system service and timer have been deprecated in favor of user flavors.
--> See the manpage of modprobed for details.
Manual of modprobed-db (8) doesn't have any entry for 'flavors'.

artafinde commented on 2015-08-15 12:24

@Th3voic3 : I noticed the same issue first time I build kernel with the new version of modprobed. With no changes second time worked fine and it is still ok, thus I didn't report it. Try maybe a logout and login and see if without changes this behaviour persists.

graysky commented on 2015-08-15 11:19

Seems ok to me:
% sudo modprobed-db r
Modprobed-db v2.31

146 modules currently loaded per /proc/modules
291 modules are in /home/facade/.config/modprobed.db

Attempting to modprobe the contents of /home/facade/.config/modprobed.db
modprobe: WARNING: Module pci_hotplug not found.

283 modules are now loaded per /proc/modules

th3voic3 commented on 2015-08-15 09:39

Don't know when that problem appeared exactly, but running modprobed-db in recall mode (with sudo) now defaults to /root/.config. I bypassed it for now by copying modprobed-db.conf to /root/.config as to redirect it to my db in my user dir.

For me the problem seems to be, that $HOME in a script run with sudo outputs "/root".

francoism commented on 2015-08-05 13:22

could you add usb_storage to the IGNORE list? :)

graysky commented on 2015-05-14 17:37

If you need that module, remove it from your db list. The problem is if you are using a kernel that you build without it, obviously, it will not be available so I recommend that you:

1) Remove it from your list
2) Install the default Arch kernel and reboot into it
3) Now build linux-ck (or whatever kernel) with your modprobed-db line/make localmodconfig line and you should be fine.