[ipxe-devel] [PATCH 0/2] Support platforms that do not process the CTRL key

[y at cs.umb.edu]

 Hi Robin, I researched this issue and a lot of people have had problems with it
in the past. Here are some relevant links (no solutions found): 

 * https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/722950
 * https://bbs.archlinux.org/viewtopic.php?id=163231
 * https://sourceforge.net/p/etherboot/mailman/message/22886868/
 * http://etherboot.org/wiki/macbuild#refit
 * http://debian.2.n7.nabble.com/Bug-429695-grub-efi-key-combinations-requiring-ctrl-do-not-work-td654610.html

 It seems the problem is prevalent on macs. 

 Fortunately, Grub includes CTRL key shortcuts *and* alternatives *hint hint* I
tested it myself. I took pictures, but I'm failing to upload them. I think you
get the point.

 Suffice it to say, I've contacted the creator of rEFInd (Roderick Smith) for
his EFI and mac EFI expertise, to examine the point of remapping the CTRL key.
However, I expect that this fix will be too extreme to be practical. While it
might be fun, in all practical sense, changing a few lines in iPXE and being
done with it is far easier than researching the depths of mac's EFI
implementation and determining a course of action for 'fixing' the CTRL key
issue. This could include modifying EFI firmware (doable?) or making some kind
of bootloader EFI program or some better solution that Mr. Smith comes up with.
If the solution is painstaking, then it would mean any mac user interested in
trying out iPXE would have to take far extra pains getting the CTRL key to work
vs. iPXE accepting alternative keys.

 Ultimately the best course of action would be to follow suit with Grub, which
displays text messages like "Ctrl-X or ESC" - Exit. Going this path would
require further modification to the source, because as I recall the autoboot
function is currently only designed to take one key parameter, it would need to
be modified to take at least two. 

 Secondly, although it is not included in my patches, I did at one time try
printing in 'config' menu a message like "Press Ctrl-X or BACKSPACE" --
something along those lines -- and the string was too long to be printed to
screen. Perhaps a shorter string will suffice.

 Once those two things are patched it would be a nice solution IMHO. 

 This is a really easy way of adding support for these unsupported platforms. As
I've said, I'm pretty sure that trying to add CTRL support to the mac will be
difficult and very out of the way, even though it sounds like fun learning how
to do! However, when I hear from Roderick Smith, things may change. But I'm not
sure I will be hearing from him; I get the sense that he is busy for at least a
little while. I hope you will agree with my decision, unless you have a good
reason not to.

 Sincerely, bazz