Red Hat Bugzilla – Bug 1276696
modules not loaded on boot
Last modified: 2016-07-19 15:21:22 EDT
Description of problem:
/etc/modules isnt loading my modules on boot
some apps and daemons(demons, whatever) like to have thier ducks in a row after booting but this isnt happening. This is glaringly obvious when running apps like fldigi or dated apps using older soundcard interfaces.
/dev/dsp isnt here.....geee, I wonder Y? THE FRIGGIN MODULE AINT LOADED!
True, Im using a modified file. But this should not prevent the file from loading on boot.At a loss why this is.I have stuff in here that needs to load on boot like tpm, sounds modules and crypto modules for ecryptfs(Private home folder). Yet none of these are loaded.
If theres no ecryptfs module loaded, your Private folder wont mount.
Version-Release number of selected component (if applicable):
detected in 22, but Ive been using this setup since 21.
Steps to Reproduce:
1.modify the file and put something there like snd-pcm-oss
3.check for /dev/dsp
this file should load everything
What file are you putting that in? /etc/modules? thats not used.
See 'man modules-load.d' for the current method.
You need /etc/modules-load.d/something.conf files with the modules you wish to load in it/them.
If you switch to that does it work?
/etc/modules is the normal standard way. If this standard has changed then we need to notify people as such.
Document it or something.Write a BS comment there that says moved. Do something.
I will have to reboot and see. That may explain some things.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.