| Autor |
Nachricht |
|
|
Titel: How do I make my modules survive a reboot?
 Verfasst am: 17.07.2006, 03:08 Uhr
|
|
Anmeldung: 12. Jul 2005
Beiträge: 28
Wohnort: SC, USA
|
|
| After a recent dist-upgrade, I now get an error during boot that hotplug does not recognize my mouse, and I also get a failure of eth0. Both are resolved if I modprobe psmouse and rt2500 (then ifup eth0), but I have not been able to figure out how to make these two survive a reboot. What is the correct method to update the modules to load at boot? |
|
|
| |
|
|
|
 |
|
|
|
Titel:
Verfasst am: 17.07.2006, 03:12 Uhr
|
|
Anmeldung: 16. Apr 2006
Beiträge: 207
Wohnort: England
|
|
| I'm not sure if there is a definitive way of doing it it but I personally add any modules to /etc/modules |
_________________
sidux 32 & 64 | PCLinuxOS | PC-BSD
repository of shame - compiz fusion & beryl repo for debian Sid/Lenny/Etch | 32-bit | 64-bit
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 21.07.2006, 02:45 Uhr
|
|
Anmeldung: 12. Jul 2005
Beiträge: 28
Wohnort: SC, USA
|
|
| When I add the two modules to /etc/modules and reboot, I get the same result. If I edit /etc/modules again, my changes are not there. Something is writing over /etc/modules (every boot?) and the new additions are not retained. What would do this and how do I turn it off? |
|
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 21.07.2006, 04:04 Uhr
|
|
Anmeldung: 02. Mai 2004
Beiträge: 471
Wohnort: Portland, OR, USA
|
|
| Try adding them to "/etc/modules-2.6" instead. I think "/etc/modules" is no longer used. |
|
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 21.07.2006, 05:57 Uhr
|
|
Developer
Anmeldung: 01. Okt 2004
Beiträge: 245
Wohnort: Australia
|
|
From module-init-tools init script:
Code:
KVER=$(uname -r)
KMAJ=${KVER%${KVER#*.*[^.]}}
KMAJ=${KMAJ%.}
if [ -e /etc/modules-$KVER ]; then
MODULES_FILE=/etc/modules-$KVER
elif [ -e /etc/modules-$KMAJ ]; then
MODULES_FILE=/etc/modules-$KMAJ
else
MODULES_FILE=/etc/modules
fi
You can see what files are accepted and in what order. |
|
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 21.07.2006, 06:24 Uhr
|
|
Anmeldung: 25. Jun 2006
Beiträge: 56
|
|
| maybe you can try putting the text files into the /etc/modprobe.d folder |
|
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 21.07.2006, 07:38 Uhr
|
|
Anmeldung: 05. Okt 2004
Beiträge: 2069
Wohnort: w3
|
|
|
Zitat:
You can see what files are accepted and in what order.
So, simply remove all files /etc/modules-* (they are not needed any more) and just leave /etc/modules. After that add your module into that file and it will be activated with every boot.
Greetings,
Chris |
_________________
"An operating system must operate."
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 23.07.2006, 01:22 Uhr
|
|
Anmeldung: 12. Jul 2005
Beiträge: 28
Wohnort: SC, USA
|
|
| Thanks for the help. I did find another file named after the kernel that was overwriting etc/modules on each boot. When I editted that file, the changes stayed. It took a bunch of rebooting to read the message as it whizzed by while booting. How do I capture all that text and save it to read it at a more human pace? |
|
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 23.07.2006, 12:16 Uhr
|
|
Anmeldung: 05. Okt 2004
Beiträge: 2069
Wohnort: w3
|
|
Simply:
Code:
dmesg > bootmessages.txt
That puts them all in a handy text file.
Greetings,
Chris |
_________________
"An operating system must operate."
|
| |
|
|
|
|
|
|
