I gave up on setting up my Poweredge 2850 on 64 bit due to PSU issues, and am setting up the Poweredge750 in the meantime.
I setup my system, which has two identical 40Gb SATA's w/ 2 R0 arrays in mdadm, and /boot w/ R1. (I finally discovered why my old G3 ml350 did not boot correctly, lilo requires v 0.90 metadata
My question is: in the faq it reccomends the use of generic
. This is news to me--in the past if I wasn't running huge I would simply compile a long-term-stable candidate. For the purposes of making an initrd, you need to know any modules not in the kernel which you need to provide for the initrd.
Is there a correct method of doing this? TLDP mentions:
"You can see what modules are already loaded into the kernel by running lsmod, which gets its information by reading the file /proc/modules."
I'm still in setup though, which is using hugesmps.
During my testing days I would run:
lspci -vvv | grep modules
and then I'd make an initrd out of all the modules listed.
Upon inspecting /proc/modules and the above output, I do notice there are differences.
Is there a, "correct way," to derive this information? Now that I think about it, I don't want to make an initrd with redundant modules that are already in the kernel.
In all honesty, I'd like to compile a custom kernel with the modules my system requires in lieu of using generic, which is what brough about this post.