Re: [gentoo-user] About to attempt EFI install, which modules to compile?

[Dale <rdalek1967@gmail.com>]

German wrote:
> Hi people. I am about to try today an EFI gentoo install with sysrecuecd. It is all more or less clear to me in the install docs, however I am not sure how to gather info about my hardware, which modules should be compiled when installing kernel manually. Is there a way to gather this info? What command should be issued to accomplish that? Also, I am sort of reluctant to compile kernel manually. Is this possible to use genkernel to install system in EFI mode or I must to use manual compilation? Thank you for your advice and suggestions.
>

I have no experience with EFI, yet.  I think this will help with one
part of your post tho.  You can use lsmod while booted with sysrescue
and get a list of what modules are being used.  I've done that before. 
It helps. 

Another command that can help and may be better. lspci -k.  That should
look like this snippet:

01:00.1 Audio device: NVIDIA Corporation GT216 HDMI Audio Controller
(rev a1)
        Subsystem: NVIDIA Corporation Device 069a
        Kernel driver in use: snd_hda_intel
02:00.0 USB controller: VIA Technologies, Inc. Device 3483 (rev 01)
        Subsystem: Gigabyte Technology Co., Ltd Device 5007
        Kernel driver in use: xhci_hcd
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
        Subsystem: Gigabyte Technology Co., Ltd Motherboard
        Kernel driver in use: r8169
04:06.0 Ethernet controller: Davicom Semiconductor, Inc. Ethernet 100/10
MBit (rev 31)
        Subsystem: ARCHTEK TELECOM Corp Device 0008
        Kernel driver in use: dmfe

What you are really looking for is the "Kernel driver in use:" part.  If
you are making your own kernel, you use that info to find the module to
enable, either built in or as a module.  I sometimes cheat and use this
command:

lspci -k | grep Kernel

Make sure that K is upper case OR add the -i option to grep.  That
command only lists the part I am really interested in and the driver
name sometimes tells what it is for anyway.  Plus, it's generally best
to enable the hardware you got. 

Maybe someone else can come along and shine some light on the rest. 

Dale

:-)  :-)