Flicker on boot

2012-12-19
2012-12-29
  • Jordan Fern
    Jordan Fern
    2012-12-19

    I've created a video here showing what i mean.

    http://www.youtube.com/watch?v=Up25N55bHBs&feature=youtu.be

    Any ideas?

    Here is my config (changed hashes to ± just for pasting)

    ±
    ± refind.conf
    ± Configuration file for the rEFInd boot menu
    ±

    ± Timeout in seconds for the main menu screen. Setting the timeout to 0
    ± disables automatic booting (i.e., no timeout).
    ±
    timeout 05

    ± Hide user interface elements for personal preference or to increase
    ± security:
    ± banner - the rEFInd title banner
    ± label - boot option text label in the menu
    ± singleuser - remove the submenu options to boot Mac OS X in single-user
    ± or verbose modes; affects ONLY MacOS X
    ± hwtest - the submenu option to run Apple's hardware test
    ± arrows - scroll arrows on the OS selection tag line
    ± hints - brief command summary in the menu
    ± editor - the options editor (+, F2, or Insert on boot options menu)
    ± all - all of the above
    ± Default is none of these (all elements active)
    ±
    ±hideui singleuser
    ±hideui all
    hideui label,singleuser,hwtest,arrows,hints,editor

    ± Set the name of a subdirectory in which icons are stored. Icons must
    ± have the same names they have in the standard directory. The directory
    ± name is specified relative to the main rEFInd binary's directory. If
    ± an icon can't be found in the specified directory, an attempt is made
    ± to load it from the default directory; thus, you can replace just some
    ± icons in your own directory and rely on the default for others.
    ± Default is "icons".
    ±
    icons_dir myicons

    ± Use a custom title banner instead of the rEFInd icon and name. The file
    ± path is relative to the directory where refind.efi is located. The color
    ± in the top left corner of the image is used as the background color
    ± for the menu screens. Currently uncompressed BMP images with color
    ± depths of 24, 8, 4 or 1 bits are supported.
    ±
    banner rEFIND.bmp

    ± Custom images for the selection background. There is a big one (144 x 144)
    ± for the OS icons, and a small one (64 x 64) for the function icons in the
    ± second row. If only a small image is given, that one is also used for
    ± the big icons by stretching it in the middle. If only a big one is given,
    ± the built-in default will be used for the small icons.
    ±
    ± Like the banner option above, these options take a filename of an
    ± uncompressed BMP image file with a color depth of 24, 8, 4, or 1 bits.
    ±
    selection_big selection-big.bmp
    ±selection_small selection-small.bmp

    ± Use text mode only. When enabled, this option forces rEFInd into text mode.
    ± Passing this option a "0" value causes graphics mode to be used. Pasing
    ± it no value or any non-0 value causes text mode to be used.
    ± Default is to use graphics mode.
    ±
    ±textonly

    ± Set the EFI text mode to be used for textual displays. This option
    ± takes a single digit that refers to a mode number. The default is 0
    ± (80x25), 1 is sometimes 80x50, and higher numbers are system-specific
    ± modes. If you specify an invalid mode, rEFInd pauses during boot to
    ± inform you of valid modes.
    ± CAUTION: On VirtualBox, and perhaps on some real computers, specifying
    ± a text mode and uncommenting the "textonly" option while NOT specifying
    ± a resolution can result in an unusable display in the booted OS.
    ± Default is 0
    ±
    ±textmode 2

    ± Set the screen's video resolution. Pass this option either:
    ± * two values, corresponding to the X and Y resolutions
    ± * one value, corresponding to a GOP (UEFI) video mode
    ± Note that not all resolutions are supported. On UEFI systems, passing
    ± an incorrect value results in a message being shown on the screen to
    ± that effect, along with a list of supported modes. On EFI 1.x systems
    ± (e.g., Macintoshes), setting an incorrect mode silently fails. On both
    ± types of systems, setting an incorrect resolution results in the default
    ± resolution being used. A resolution of 1024x768 usually works, but higher
    ± values often don't.
    ± Default is "0 0" (use the system default resolution, usually 800x600).
    ±
    resolution 2880 1800
    ±resolution 3

    ± Launch specified OSes in graphics mode. By default, rEFInd switches
    ± to text mode and displays basic pre-launch information when launching
    ± all OSes except OS X. Using graphics mode can produce a more seamless
    ± transition, but displays no information, which can make matters
    ± difficult if you must debug a problem. Also, on at least one known
    ± computer, using graphics mode prevents a crash when using the Linux
    ± kernel's EFI stub loader. You can specify an empty list to boot all
    ± OSes in text mode.
    ± Valid options:
    ± osx - Mac OS X
    ± linux - A Linux kernel with EFI stub loader
    ± elilo - The ELILO boot loader
    ± grub - The GRUB (Legacy or 2) boot loader
    ± windows - Microsoft Windows
    ± Default value: osx
    ±
    use_graphics_for osx,windows

    ± Which non-bootloader tools to show on the tools line, and in what
    ± order to display them:
    ± shell - the EFI shell (requires external program; see rEFInd
    ± documentation for details)
    ± gptsync - the (dangerous) gptsync.efi utility (requires external
    ± program; see rEFInd documentation for details)
    ± apple_recovery - boots the Apple Recovery HD partition, if present
    ± mok_tool - makes available the Machine Owner Key (MOK) maintenance
    ± tool, MokManager.efi, used on Secure Boot systems
    ± about - an "about this program" option
    ± exit - a tag to exit from rEFInd
    ± shutdown - shuts down the computer (a bug causes this to reboot
    ± EFI systems)
    ± reboot - a tag to reboot the computer
    ± Default is shell,apple_recovery,mok_tool,about,shutdown,reboot
    ±
    showtools reboot

    ± Directories in which to search for EFI drivers. These drivers can
    ± provide filesystem support, give access to hard disks on plug-in
    ± controllers, etc. In most cases none are needed, but if you add
    ± EFI drivers and you want rEFInd to automatically load them, you
    ± should specify one or more paths here. rEFInd always scans the
    ± "drivers" and "drivers_{arch}" subdirectories of its own installation
    ± directory (where "{arch}" is your architecture code); this option
    ± specifies ADDITIONAL directories to scan.
    ± Default is to scan no additional directories for EFI drivers
    ±
    ±scan_driver_dirs EFI/tools/drivers,drivers

    ± Which types of boot loaders to search, and in what order to display them:
    ± internal - internal EFI disk-based boot loaders
    ± external - external EFI disk-based boot loaders
    ± optical - EFI optical discs (CD, DVD, etc.)
    ± hdbios - BIOS disk-based boot loaders
    ± biosexternal - BIOS external boot loaders (USB, eSATA, etc.)
    ± cd - BIOS optical-disc boot loaders
    ± manual - use stanzas later in this configuration file
    ± Note that the legacy BIOS options require firmware support, which is
    ± not present on all computers.
    ± On UEFI PCs, default is internal,external,optical,manual
    ± On Macs, default is internal,hdbios,external,biosexternal,optical,cd,manual
    ±
    scanfor internal,hdbios,external,optical

    ± Delay for the specified number of seconds before scanning disks.
    ± This can help some users who find that some of their disks
    ± (usually external or optical discs) aren't detected initially,
    ± but are detected after pressing Esc.
    ± The default is 0.
    ±
    ±scan_delay 5

    ± When scanning volumes for EFI boot loaders, rEFInd always looks for
    ± Mac OS X's and Microsoft Windows' boot loaders in their normal locations,
    ± and scans the root directory and every subdirectory of the /EFI directory
    ± for additional boot loaders, but it doesn't recurse into these directories.
    ± The also_scan_dirs token adds more directories to the scan list.
    ± Directories are specified relative to the volume's root directory. This
    ± option applies to ALL the volumes that rEFInd scans. If a specified
    ± directory doesn't exist, it's ignored (no error condition results).
    ± The default is to scan the "boot" directory in addition to various
    ± hard-coded directories.
    ±
    ±also_scan_dirs boot,EFI/linux/kernels

    ± Partitions to omit from scans. You must specify a volume by its
    ± label, which you can obtain in an EFI shell by typing "vol", from
    ± Linux by typing "blkid /dev/{devicename}", or by examining the
    ± disk's label in various OSes' file browsers.
    ± The default is an empty list (all volumes are scanned).
    ±
    ±dont_scan_volumes

    ± Directories that should NOT be scanned for boot loaders. By default,
    ± rEFInd doesn't scan its own directory or the EFI/tools directory.
    ± You can "blacklist" additional directories with this option, which
    ± takes a list of directory names as options. You might do this to
    ± keep EFI/boot/bootx64.efi out of the menu if that's a duplicate of
    ± another boot loader or to exclude a directory that holds drivers
    ± or non-bootloader utilities provided by a hardware manufacturer. If
    ± a directory is listed both here and in also_scan_dirs, dont_scan_dirs
    ± takes precedence. Note that this blacklist applies to ALL the
    ± filesystems that rEFInd scans, not just the ESP.
    ±
    ±dont_scan_dirs EFI/boot,EFI/Dell

    ± Files that should NOT be included as EFI boot loaders (on the
    ± first line of the display). If you're using a boot loader that
    ± relies on support programs or drivers that are installed alongside
    ± the main binary or if you want to "blacklist" certain loaders by
    ± name rather than location, use this option. Note that this will
    ± NOT prevent certain binaries from showing up in the second-row
    ± set of tools. Most notably, MokManager.efi is in this blacklist,
    ± but will show up as a tool if present in certain directories. You
    ± can control the tools row with the showtools token.
    ± The default is shim.efi,MokManager.efi,TextMode.efi,ebounce.efi,GraphicsConsole.efi
    ±
    ±dont_scan_files shim.efi,MokManager.efi

    ± Scan for Linux kernels that lack a ".efi" filename extension. This is
    ± useful for better integration with Linux distributions that provide
    ± kernels with EFI stub loaders but that don't give those kernels filenames
    ± that end in ".efi", particularly if the kernels are stored on a
    ± filesystem that the EFI can read. When uncommented, this option causes
    ± all files in scanned directories with names that begin with "vmlinuz"
    ± or "bzImage" to be included as loaders, even if they lack ".efi"
    ± extensions. The drawback to this option is that it can pick up kernels
    ± that lack EFI stub loader support and other files. Most notably, if you
    ± want to give a kernel a custom icon by placing an icon with the kernel's
    ± filename but a ".icns" extension in the same directory as the kernel, this
    ± option will cause the icon file to show up as a non-functional loader tag.
    ± Passing this option a "0" value causes kernels without ".efi" extensions
    ± to NOT be scanned; passing it alone or with any other value causes all
    ± kernels to be scanned.
    ± Default is to NOT scan for kernels without ".efi" extensions.
    ±
    scan_all_linux_kernels

    ± Set the maximum number of tags that can be displayed on the screen at
    ± any time. If more loaders are discovered than this value, rEFInd shows
    ± a subset in a scrolling list. If this value is set too high for the
    ± screen to handle, it's reduced to the value that the screen can manage.
    ± If this value is set to 0 (the default), it's adjusted to the number
    ± that the screen can handle.
    ±
    ±max_tags 0

    ± Set the default menu selection. The available arguments match the
    ± keyboard accelerators available within rEFInd. You may select the
    ± default loader using:
    ± - A digit between 1 and 9, in which case the Nth loader in the menu
    ± will be the default.
    ± - Any substring that corresponds to a portion of the loader's title
    ± (usually the OS's name or boot loader's path).
    ±
    ±default_selection 1

    ± Include a secondary configuration file within this one. This secondary
    ± file is loaded as if its options appeared at the point of the "include"
    ± token itself, so if you want to override a setting in the main file,
    ± the secondary file must be referenced AFTER the setting you want to
    ± override. Note that the secondary file may NOT load a tertiary file.
    ±
    ±include manual.conf

    ± Sample manual configuration stanzas. Each begins with the "menuentry"
    ± keyword followed by a name that's to appear in the menu (use quotes
    ± if you want the name to contain a space) and an open curly brace
    ± ("{"). Each entry ends with a close curly brace ("}"). Common
    ± keywords within each stanza include:
    ±
    ± volume - identifies the filesystem from which subsequent files
    ± are loaded. You can specify the volume by label or by
    ± a number followed by a colon (as in "0:" for the first
    ± filesystem or "1:" for the second).
    ± loader - identifies the boot loader file
    ± initrd - Specifies an initial RAM disk file
    ± icon - specifies a custom boot loader icon
    ± ostype - OS type code to determine boot options available by
    ± pressing Insert. Valid values are "MacOS", "Linux",
    ± "Windows", and "XOM". Case-sensitive.
    ± graphics - set to "on" to enable graphics-mode boot (useful
    ± mainly for MacOS) or "off" for text-mode boot.
    ± Default is auto-detected from loader filename.
    ± options - sets options to be passed to the boot loader; use
    ± quotes if more than one option should be passed or
    ± if any options use characters that might be changed
    ± by rEFInd parsing procedures (=, /, ±, or tab).
    ± disabled - use alone or set to "yes" to disable this entry.
    ±
    ± Note that you can use either DOS/Windows/EFI-style backslashes ()
    ± or Unix-style forward slashes (/) as directory separators. Either
    ± way, all file references are on the ESP from which rEFInd was
    ± launched.
    ± Use of quotes around parameters causes them to be interpreted as
    ± one keyword, and for parsing of special characters (spaces, =, /,
    ± and ±) to be disabled. This is useful mainly with the "options"
    ± keyword. Use of quotes around parameters that specify filenames is
    ± permissible, but you must then use backslashes instead of slashes,
    ± except when you must pass a forward slash to the loader, as when
    ± passing a root= option to a Linux kernel.

    ± Below are several sample boot stanzas. All are disabled by default.
    ± Find one similar to what you need, copy it, remove the "disabled" line,
    ± and adjust the entries to suit your needs.

    ± A sample entry for a Linux 3.3 kernel with its new EFI boot stub
    ± support on a filesystem called "KERNELS". This entry includes
    ± Linux-specific boot options and specification of an initial RAM disk.
    ± Note uses of Linux-style forward slashes, even in the initrd
    ± specification. Also note that a leading slash is optional in file
    ± specifications.
    menuentry Linux {
    icon EFI/refind/icons/os_linux.icns
    volume KERNELS
    loader bzImage-3.3.0-rc7
    initrd initrd-3.3.0.img
    options "ro root=UUID=5f96cafa-e0a7-4057-b18f-fa709db5b837"
    disabled
    }

    ± A sample entry for loading Ubuntu using its standard name for
    ± its GRUB 2 boot loader. Note uses of Linux-style forward slashes
    menuentry Ubuntu {
    loader /EFI/ubuntu/grubx64.efi
    icon /EFI/refined/icons/os_linux.icns
    disabled
    }

    ± A minimal ELILO entry, which probably offers nothing that
    ± auto-detection can't accomplish.
    menuentry "ELILO" {
    loader \EFI\elilo\elilo.efi
    disabled
    }

    ± Like the ELILO entry, this one offers nothing that auto-detection
    ± can't do; but you might use it if you want to disable auto-detection
    ± but still boot Windows....
    menuentry "Windows 7" {
    loader \EFI\Microsoft\Boot\bootmgfw.efi
    disabled
    }

    ± EFI shells are programs just like boot loaders, and can be
    ± launched in the same way. You can pass a shell the name of a
    ± script that it's to run on the "options" line. The script
    ± could initialize hardware and then launch an OS, or it could
    ± do something entirely different.
    menuentry "Windows via shell script" {
    icon \EFI\refind\icons\os_win.icns
    loader \EFI\tools\shell.efi
    options "fs0:\EFI\tools\launch_windows.nsh"
    disabled
    }

    ± Mac OS is normally detected and run automatically; however,
    ± if you want to do something unusual, a manual boot stanza may
    ± be the way to do it. This one does nothing very unusual, but
    ± it may serve as a starting point. Note that you'll almost
    ± certainly need to change the "volume" line for this example
    ± to work.
    menuentry "My Mac OS X" {
    icon \EFI\refind\icons\os_mac.icns
    volume "OS X boot"
    loader \System\Library\CoreServices\boot.efi
    disabled
    }

     
  • I've made some changes to the resolution-setting code in the last couple of versions, particularly to support adjusting the text-mode resolution. The text-mode code should only be called if you explicitly set a text-mode resolution via the textmode option, which you don't have, so it's unlikely that this is the cause. I've been fiddling with this code since the last release, though, so you might want to give this intermediate version a try:

    http://www.rodsbooks.com/refind-bin-0.6.0.4.zip

    If that doesn't help, try commenting out the resolution line from refind.conf and see if that helps. (Please try this even if you prefer the flicker to using whatever your default resolution is; knowing if the flicker persists is useful diagnostic information.)

    If none of this helps, or if commenting out the resolution line helps but is unacceptable to you, please post back with your screen output information, available from rEFInd's information display. It should be either "Graphics Output (UEFI)" or "UGA Draw (EFI 1.10)".

     
  • Jordan Fern
    Jordan Fern
    2012-12-20

    Thanks Rod, ill have a look this afternoon and report back...

    The Screen flickered before i changed the resolution (that was my attempt to fix it)

    Could you also maybe set up a distribution list for new versions of the software?

     
  • Jordan Fern
    Jordan Fern
    2012-12-20

    Ok tried both things and updated my rEFInd, still flickers :(

    From the about menu i have the following details:

    EFI Revision: 1.10
    Platform: 64Bit
    Firmware: Apple 1.10
    Screen Output: Graphics Output (UEFI), 2880x1800

    Anything else i can help you with mate?
    Also if you look at the youtube video a guy also commented with the same issue.

     
  • Valentina
    Valentina
    2012-12-21

    I had the same problem yesterday. Fortunately version 0.6.0.5 (link provided above) works fine without setting a resolution in the configuration file

     
  • Jordan Fern
    Jordan Fern
    2012-12-21

    Also can confirm this works perfect. What did you change?

     
  • I'm glad it worked. I actually made a lot of changes to the resolution-setting code with 0.6.0.5, but what I think happened was this:

    1. Prior to version 0.5.1, most text-mode output appeared on Macs only when the program explicitly entered text mode. This contrasts with PCs, in which text-mode output would overlay graphics mode. The result is that certain error messages would not appear on Macs. Also of relevance for this bug, a text-mode program startup banner was not displayed on Macs, although the code to do so was being called.

    2. With version 0.5.1, I made changes intended to at least partially overcome the problem of error messages not appearing on Macs, by including more calls to a function that enters text mode. I believe this introduced your "flicker" bug because the function that displays the banner at startup ended up calling this code. The result was a brief entry into text mode followed by an immediate exit from it.

    3. To fix this, I moved the initial screen-setup code to after the point where the configuration file was read (previously it was done before then) and displaying the text-mode startup banner only if the configuration file specifies the textonly parameter.

    I may just eliminate the startup banner entirely, since its only benefit is confirming that the program has launched but hung, and now that only works in text mode.

     
  • Jordan Fern
    Jordan Fern
    2012-12-21

    If i could like/Thank that post i would lol

    Thanks for the great work Rod,

    Have a great christmas mate,

    Cheers

     
  • Jack
    Jack
    2012-12-29

    Hi,

    How did you do to remove the icon from the internal volume?

    Thanks.