Comment 45 for bug 721576

In my case grepping dmesg output for EFI string results in:

[ 0.000000] EFI v2.10 by American Megatrends
[ 0.000000] Kernel-defined memdesc doesn't match the one from EFI!

Followed by bunch of (mem00 through mem188):

[ 0.000000] EFI: mem00: type=3, attr=0xf, range=[0x0000000000000000-0x0000000000008000) (0MB)
[ 0.000000] EFI: mem01: type=7, attr=0xf, range=[0x0000000000008000-0x0000000000077000) (0MB)
[ 0.000000] EFI: mem02: type=4, attr=0xf, range=[0x0000000000077000-0x0000000000078000) (0MB)
[ 0.000000] EFI: mem03: type=3, attr=0xf, range=[0x0000000000078000-0x00000000000a0000) (0MB)
[ 0.000000] EFI: mem04: type=2, attr=0xf, range=[0x0000000000100000-0x000000000056d000) (4MB)
[ 0.000000] EFI: mem05: type=7, attr=0xf, range=[0x000000000056d000-0x0000000001000000) (10MB)

etc (through mem188)... I could provide all memXXX lines if needed. Followed by:

[ 1.264080] efifb: probing for efifb
[ 1.264341] efifb: framebuffer at 0xd9000000, mapped to 0xffffc90012880000, using 1920k, total 1920k
[ 1.264343] efifb: mode is 800x600x32, linelength=3200, pages=1
[ 1.264344] efifb: scrolling: redraw
[ 1.264345] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[ 1.264390] fb0: EFI VGA frame buffer device
[ 1.535400] EFI Variables Facility v0.08 2004-May-17

So, I'd guess based on the above output that my Gateway system is indeed EFI based.