You are not logged in.
Pages: 1
Dump
Last edited by beta990 (2012-08-25 13:43:00)
Offline
USB: Format USB with FAT32, extract contents from ISO to USB directly > 7zip, unarchiver, etc.
Which version of the iso are you using?
Last edited by KairiTech (2012-08-07 19:13:48)
Offline
Hi, I followed your guide, but I'm still stuck at the beginning. It launches a shell, and modprobe or efibootmgr work. It tells me they are not commands. (I'm running from a CD, formatting a kingston USB as FAT32 and dumping everything in it would only take me back to the mobo settings utility, even when it recognized the stick as a uefi bootable option)
Offline
beta990 wrote:USB: Format USB with FAT32, extract contents from ISO to USB directly > 7zip, unarchiver, etc.
Which version of the iso are you using?
Last edited by KairiTech (2012-08-08 14:31:23)
Offline
I do not use Grub2 but rEFInd at the moment. This means that you still have to copy the kernel files to the right directory every kernel update. (See wiki UEFI Bootloaders
Is it still required to have the kernel in /boot? If it isn't required you could modify /etc/mkinitcpio.d/linux.preset to create the kernel in the EFI directory structure.
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
I do not use Grub2 but rEFInd at the moment. This means that you still have to copy the kernel files to the right directory every kernel update. (See wiki UEFI Bootloaders
Is it still required to have the kernel in /boot? If it isn't required you could modify /etc/mkinitcpio.d/linux.preset to create the kernel in the EFI directory structure.
Thanks for the suggestion going to test this out.
Offline
Hi, I followed your guide, but I'm still stuck at the beginning. It launches a shell, and modprobe or efibootmgr work. It tells me they are not commands. (I'm running from a CD, formatting a kingston USB as FAT32 and dumping everything in it would only take me back to the mobo settings utility, even when it recognized the stick as a uefi bootable option)
Offline
As I have posted elsewhere if you just mount your EFI partition as /boot refind can find your kernels and load them without having to move them. There is no reason you can't have a /boot partition formated as FAT32.
Offline
As I have posted elsewhere if you just mount your EFI partition as /boot refind can find your kernels and load them without having to move them. There is no reason you can't have a /boot partition formated as FAT32.
/dev/sda1 = UEFI Partition (FAT32)
/dev/sda2 = /boot (ext2)
/dev/sda1 on /boot
/dev/sda2 on /boot/efi
Offline
As I have posted elsewhere if you just mount your EFI partition as /boot refind can find your kernels and load them without having to move them. There is no reason you can't have a /boot partition formated as FAT32.
That is a good idea, there is just one problem if you want to create a multiboot system. Each installation should put the kernel in its own directory or use a unique name, so you WILL have to modify the preset file.
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
acvar wrote:As I have posted elsewhere if you just mount your EFI partition as /boot refind can find your kernels and load them without having to move them. There is no reason you can't have a /boot partition formated as FAT32.
That is a good idea, there is just one problem if you want to create a multiboot system. Each installation should put the kernel in its own directory or use a unique name, so you WILL have to modify the preset file.
Unless you are using more then 1 rolling release distribution I really don't see a problem here. Distro's that only change the kernel every 6 months can easily be put in their own directory while keepig the arch kernels in the "root" of the efi partition. Refind can find them anywhere on the efi partition.
Offline
Pages: 1