

That said, it's conceivable that there is a bug in rEFInd that's causing it to ignore a valid refind_nf file under certain circumstances - but if so, the problem is pretty rare, and I can't fix a problem that I can't reproduce without help from those who do have the problem. In neither of those cases is this a rEFInd problem it's a problem with the filesystem or file, or perhaps in the EFI itself. As I stated in that thread, I suspect the problem is either filesystem damage or a refind_nf file that's in an improper format. In that thread, I offered some hypotheses about why that was happening, but the OP didn't post back with a resolution that would enable positive identification of the actual cause. You've linked to one thread that claims rEFInd was ignoring the file. More broadly speaking, the claim that rEFInd ignores refind_nf is overly-broad at best.

The refind_nf file is not relevant to setting the EFI framebuffer mode that detail is set via the "resolution" and/or "textmode" options in the nf file - note that those two files are not equivalent. I can still force it to use the EFI framebuffer driver if I like by generating an /etc/X11/nf file and setting that file to use the framebuffer driver.Īs for the EFI framebuffer device being for Macs, I believe the documentation is simply outdated. Now when I switch between X and text mode, the VirtualBox screen changes size, but I don't get scroll bars unless one of the modes is set too large for my host OS's display. I'm guessing this driver didn't work in EFI mode until recently, but now it does. My last few installs, though, have begun using the VirtualBox driver. Until recently, most Linux X installations have used the EFI framebuffer device when VirtualBox has booted in EFI mode. In either case, you can just set a mode in the configuration file within the virtual machine rather than adjust it with obscure commands in the host OS. (I'm not sure if Arch's package uses the same filename or option name.) In the case of GRUB, you'd need to regenerate your grub.cfg file for the change to take effect, but rEFInd reads nf at boot time, so you could just change it there and be done with it. GRUB 2 has something similar: It's the GRUB_GFXMODE option in /etc/default/grub, at least on a Fedora 18 installation. I generally find it easier to use the "resolution" token in rEFInd's nf file. See this page for details, including what the different GOP modes are. VBoxManage setextradata "VM name" VBoxInternal2/UgaVerticalResolution 768 VBoxManage setextradata "VM name" VBoxInternal2/UgaHorizontalResolution 1024 VBoxManage setextradata "VM name" VBoxInternal2/EfiGopMode 2
