dAlexis wrote:1) Is initrd mandatory for successfull uefi boot? I was never using initrd, but it's present in refind sample.
I don't think it's absolutely required, but I've been using initrds on all my systems for at least five years -- I've found it's just less of a hassle that way. This is why it's present in the rEFInd documentation, since I maintain rEFInd and wrote that documentation.
2) Is it mandatory to copy kernel in uefi partition?
HERE in sample I found kernel, copied to uefi, but is it really needed?
The answer depends on your boot loader and boot manager. For gummiboot, the answer is basically "yes," although if you were to chainload gummiboot from something other than the ESP, you could do otherwise. For ELILO, as a practical matter the answer is also "yes," although in theory it can load a kernel from elsewhere. (The documentation is silent on the details of how to refer to another partition, though, and I've never gotten it to work.) If you use GRUB, the answer is "no"; GRUB can load a kernel from anywhere (including an LVM or RAID setup for GRUB 2). For rEFInd, the answer is "no," but with some caveats -- rEFInd relies on EFI filesystem drivers to read kernels, and those are available for FAT (built into all EFIs), HFS+ (built into Macs' EFIs and available as a separate driver), ext2/3/4fs, ReiserFS, and ISO-9660 (available as a driver with rEFInd).
If you're designing a setup from scratch, the approach that will give you the greatest flexibility is likely to be to create an ESP that's 512MiB or larger in size and mount it in Linux at /boot. This is a bit unusual, but it means you'll be able to use
any EFI boot loader with kernels placed (from Linux) in the usual location. If that's impractical, then a separate non-ESP FAT /boot partition makes sense. If you must use a Linux filesystem because you rely on symbolic links in /boot, then use ext2/3/4fs or ReiserFS on a /boot partition. If you move away from those filesystems or put /boot on a Linux filesystem in a RAID or LVM setup, you'll be limiting your choice of boot loaders and boot managers a great deal.
Or my boot partition on primary booting uefi ssd will be found?
I'm sorry, I'm afraid I just don't understand what you're asking by this.
3) Mixed UEFI & non UEFI disks - setting uefi support in kernel will be enough?
There's no such thing as a "UEFI disk" or a "non-UEFI disk." If you're referring to
GUID Partition Table (GPT) disks, then you can mix those along with
Master Boot Record (MBR) disks (or other disk types) all you like; you just need to be sure that the kernel supports all the partition table types you use. Partition table support is independent of EFI support in the Linux kernel.
4) Is it needed to set uefi stuff, related to grub2, in configs, using refind? I think, no, but I remember about possible cross-dependencies...
I'm not entirely sure what you mean by this, but if you use rEFInd to launch GRUB 2, then the options passed to the kernel are set entirely in GRUB 2's configuration, not in rEFInd's configuration. rEFInd simply launches GRUB 2, which loads its own configuration file. In most cases, though, it will be simpler and easier to bypass GRUB 2 and have rEFInd launch the Linux kernel directly. This eliminates the need to configure GRUB 2, although you will then need to set kernel options in rEFInd, normally by creating a /boot/refind_linux.conf file. This is normally much easier than dealing with GRUB 2's arcane configuration. See
the rEFInd documentation on launching Linux for details of how to do this.