Kernel boot/options question

I'm booting the kernel-beyond.  My kernel command line is as follows:
Kernel command line: root=/dev/hda2 pci=assign-busses idebus=100 ro
When my system is booting I see this:
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
And further down with the IDE drives:
hda: max request size: 128KiB
hda: 195371568 sectors (100030 MB) w/8192KiB Cache, CHS=65535/16/63, UDMA(100)
hda: cache flushes supported
hda: hda1 hda2 hda3 hda4 <hda5>
Does this mean I'm actually using UDMA 100??  My hdparm -tT /dev/hda returns:
/dev/hda:
Timing cached reads:   2000 MB in  2.00 seconds = 999.99 MB/sec
Timing buffered disk reads:   86 MB in  3.03 seconds =  28.34 MB/sec
I would think my buffered disk reads would be higher then that.  Any suggestions or am I already as fast as I'm going to get?
Norm

This is what I get with hdparm -i /dev/hda
/dev/hda:
Model=FUJITSU MHU2100AT, FwRev=00000008, SerialNo=NQ07T5128E90
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=DualPortCache, BuffSize=8192kB, MaxMultSect=16, MultSect=16
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=195371568
IORDY=yes, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes:  pio0 pio1 pio2 pio3 pio4
DMA modes:  mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
AdvancedPM=yes: mode=0x80 (128) WriteCache=enabled
Drive conforms to: ATA/ATAPI-6 T13 1410D revision 3a:  ATA/ATAPI-2 ATA/ATAPI-3 ATA/ATAPI-4 ATA/ATAPI-5 ATA/ATAPI-6
* signifies the current active mode

Similar Messages

  • Pavilion dv7 advanced boot options keyboard not working

    1. Print screen key has never worked
    2. In Advanced Boot Options screen, arrow keys do not function to select Safe Mode, Esc key does not work to cancel out of screen.

    Hi,
    Does the arrow and esc key works in Windows?
    If it doesnt work in windows also then i can suggest you to try doing a hard reset and check..else could be a hardware issue
    How to Perform Hard Reset
    Note:
    If you have HP Support Assistant installed on the computer(The Blue Question Mark) then open it ==> Complete all pending Updates & Tuneups==> Restart and Check. It may solve your problem
    Although I am an HP employee, I am speaking for myself and not for HP.
    **Click on “Kudos” Star if you think this reply helped** Or Mark it as "Solved" if issue got fixed.

  • G400s bios don't have usb boot option

    hi all
    my laptop is G400s, i want try install linux but i got to bios but usb boot option missing ,
    any option i wrong to choose or any suggetion?
    pictur below is my bios setting picture:
    Link to picture
    Link to picture
    Link to picture
    Link to picture
    Moderator note; picture(s) totalling >50K converted to link(s) Forum Rules
    Solved!
    Go to Solution.

    hi try2ops,
    Welcome to Lenovo Community Forums!
    The options set under your BIOS are all set,
       With that, try this
    Plug in your Bootable USB
        Power ON your system then right away start hitting F12
    It should give you a Boot Menu Including USB as bootable.
    Hope this helps
    Cheers!
    Did someone help you today? Press the star on the left to thank them with a Kudo!
    If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
    Follow @LenovoForums on Twitter!

  • [SOLVED]Unknown boot option `radeon.modeset=0'

    Hi All. I've just installed newest kernel from testing repo (2.6.31). After that on my MobilityRadeon X1400 the 3D acceleration stopped working (I've used "early start method" from ArchWiki). So i've set /boot/grub/menu.lst a follows:
    # (0) Arch Linux
    title  Arch Linux
    root   (hd0,1)
    kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/ad5d0eae-969d-4e29-a98e-925480dc4519 radeon.modeset=0 ro quiet vga=838
    initrd /boot/kernel26.img
    And during the reebot i can see: Unknown boot option `radeon.modeset=0' ignoring
    Despite it 3d acceleration works fine after that. Can someone explaint the problem?
    Last edited by Nixxx (2009-10-12 23:30:58)

    @Zariel: While disabling KMS I've removed "radeon" from MODULES in /etc/mkinitcpio.conf and then I've lunched "mkinitcpio -p kernel26". Shoud I do anything else? As AndyRTR wrote despite this message KMS seems to be disabled bacause the 3D acceleration is working fine - "modinfo radeon" says:
    filename:       /lib/modules/2.6.31-ARCH/kernel/drivers/gpu/drm/radeon/radeon.ko                                                                                           
    license:        GPL and additional rights                                                                                                                                   
    description:    ATI Radeon                                                                                                                                                 
    author:         Gareth Hughes, Keith Whitwell, others.                                                                                                                     
    license:        GPL                                                                                                                                                         
    alias:          pci:v00001002d00009714sv*sd*bc*sc*i*                                                                                                                       
    alias:          pci:v00001002d00009713sv*sd*bc*sc*i*                                                                                                                       
    alias:          pci:v00001002d00009712sv*sd*bc*sc*i*
    alias:          pci:v00001002d00003150sv*sd*bc*sc*i*
    depends:        drm,ttm,i2c-core,i2c-algo-bit
    vermagic:       2.6.31-ARCH SMP preempt mod_unload 686
    parm:           no_wb:Disable AGP writeback for scratch registers (int)
    parm:           modeset:Disable/Enable modesetting (int)
    parm:           dynclks:Disable/Enable dynamic clocks (int)
    parm:           r4xx_atom:Enable ATOMBIOS modesetting for R4xx (int)
    parm:           vramlimit:Restrict VRAM for testing (int)
    parm:           agpmode:AGP Mode (-1 == PCI) (int)
    parm:           gartsize:Size of PCIE/IGP gart to setup in megabytes (32,64, etc)
    (int)
    parm:           benchmark:Run benchmark (int)
    parm:           test:Run tests (int)
    parm:           connector_table:Force connector table (int)

  • Partition is there, but Windows boot option is gone?

    Hey folks, I'm having a small issue with bootcamp.
    Not too long ago did I have Windows running just fine on my Mac; everything was up to date, I managed to install 7 and upgrade to 8.1 just fine. Everything was good until one evening I open my Mac up, there is a command line that states "no bootable device." I don't believe I had installed Yosemite because last time I shut the Mac it was in Windows. I found a thread from another user here, and followed LonerT's suggestions and managed to get Windows back as a boot option, but the command line still pops up with "non-system disk."
    The bootcamp partition is still on my HD with everything installed, so if there's some way I could get this back to how it was without having to go through the hassle of erasing the partition and starting anew I would be greatly appreciative.
    Thanks!

    Whoa, LonerT!?
    Certainly, here are the results of the commands:
    joshuas-mbp:~ joshua$ diskutil list
    /dev/disk0
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *500.3 GB   disk0
       1:                        EFI EFI                     209.7 MB   disk0s1
       2:                  Apple_HFS Macintosh HD            394.4 GB   disk0s2
       3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
       4:       Microsoft Basic Data MAC TO PC               5.0 GB     disk0s4
       5:       Microsoft Basic Data BOOTCAMP                100.0 GB   disk0s5
    joshuas-mbp:~ joshua$
    joshuas-mbp:~ joshua$ diskutil cs list
    No CoreStorage logical volume groups found
    joshuas-mbp:~ joshua$
    joshuas-mbp:~ joshua$ sudo gpt -vv -r show /dev/disk0
    Password:
    gpt show: /dev/disk0: mediasize=500277790720; sectorsize=512; blocks=977105060
    gpt show: /dev/disk0: Suspicious MBR at sector 0
    gpt show: /dev/disk0: Pri GPT at sector 1
    gpt show: /dev/disk0: Sec GPT at sector 977105059
          start       size  index  contents
              0          1         MBR
              1          1         Pri GPT header
              2         32         Pri GPT table
             34          6       
             40     409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
         409640  770347720      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
      770757360    1269536      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
      772026896       1520       
      772028416    9762816      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
      781791232       2048       
      781793280  195311616      5  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
      977104896        131       
      977105027         32         Sec GPT table
      977105059          1         Sec GPT header
    joshuas-mbp:~ joshua$
    joshuas-mbp:~ joshua$ sudo fdisk /dev/disk0
    Disk: /dev/disk0 geometry: 60821/255/63 [977105060 sectors]
    Signature: 0xAA55
             Starting       Ending
    #: id  cyl  hd sec -  cyl  hd sec [     start -       size]
    1: EE 1023 254  63 - 1023 254  63 [         1 -     409639] <Unknown ID>
    2: AF 1023 254  63 - 1023 254  63 [    409640 -  770347720] HFS+      
    3: AB 1023 254  63 - 1023 254  63 [ 770757360 -    1269536] Darwin Boot
    *4: 07 1023 254  63 - 1023 254  63 [ 772028416 -    9762816] HPFS/QNX/AUX
    joshuas-mbp:~ joshua$
    I thought the corestorage command was a bit odd so I looked around the web to find out what it means. It doesn't sound promising.
    As for you question on "what modifications were made to get [the drive] bootable again:"
    I followed these instructions you gave in that thread listed above...
    Here is an example.
    sudo fdisk -e /dev/disk0
    Password:
    fdisk: could not open MBR file /usr/standalone/i386/boot0: No such file or directory
    Enter 'help' for information
    fdisk: 1> p
    Disk: /dev/disk0 geometry: 121643/255/63 [1954210120 sectors]
    Offset: 0 Signature: 0xAA55
             Starting       Ending
    #: id  cyl  hd sec -  cyl  hd sec [     start -       size]
    1: EE 1023 254  63 - 1023 254  63 [         1 -     409639] <Unknown ID>
    2: AF 1023 254  63 - 1023 254  63 [    409640 - 1452530904] HFS+      
    3: AB 1023 254  63 - 1023 254  63 [1452940544 -    1269536] Darwin Boot
    *4: 07 1023 254  63 - 1023 254  63 [1454211072 -  499998720] HPFS/QNX/AUX
    fdisk: 1> setpid 4
             Starting       Ending
    #: id  cyl  hd sec -  cyl  hd sec [     start -       size]
    *4: 07 1023 254  63 - 1023 254  63 [1454211072 -  499998720] HPFS/QNX/AUX
    Partition id ('0' to disable)  [0 - FF]: [7] (? for help)
    fdisk: 1> flag 4
    Partition 4 marked active.
    Saying the Windows is bootable may be a bit subjective; the option appeared after this example you gave, but it won't boot into Windows.

  • [SOLVED] Longwinded beginner - Dual-boot & partition questions

    Hello,
    I'm interested in installing Arch Linux alongside Windows XP (dual-boot). I have little previous linux experience, although I have rented some servers that have used it in the past, as well as compiling some stuff with it while at University (studying Computer Science). Nevertheless, I am relatively confident that if I can still boot into XP, I will be able to acccustomise myself and like the fact that this distribution seems to be hands-on and leaves a lot up to the user.
    I've been reading the Beginner's Guide and the dual boot guide, and I would like to get started, however, I'm not going to go ahead with this until I am certain that I will be left with a system that can still boot into Windows XP. I assume that it'll take me a while to get to grips with Arch, and in the meantime it would be massively inconvenient if I couldn't work/play/etc...
    What I already know
    Anyway, currently I have a 250GB hard drive that I use for Windows (as well as 3 other hard drives full of stuff). I have partitioned the drive with Windows XP on it with gparted like so:
    (in order)
    UNALLOCATED                         32GB
    SDB1 (Windows XP)                 50GB
    SDB2 (Downloads)                  150GB
    I hope to use the unallocated space to hold linux (and then have access to my other windows drives in the future, using ntfs-3g), however, I am a little confused over what partitions I 'should' have and how large they should be, considering that I will use the OS to mainly develop, browse the web, listen to music, etc...
    I was thinking:
    /boot    -- ext2         -- 100MB
    /          -- ext4         -- 15GB
    swap    --                -- 1GB
    /home  -- ext4         -- 12GB
    /var     -- ReiserFS   -- 4GB
    Questions
    • Is 30GB too little, even though most of my stuff is on other NTFS hard drives?
    • How large should / be? I've read that it contains /bin, /dev, /etc and others. How do I know how much space these need? Am I misunderstanding things?
    • Is a /var partition unnecessary? How large should it be?
    • 10GB for /home, 1GB for swap, 100MB for /boot?
    • Do I need a /tmp or /usr? This is a single-user machine, but I don't want it to get messy!
    • I was thinking of giving /boot ext2, and /var ReiserFS, and then giving every other partition ext4. That okay?
    • Do I need to set these partitions up when installing, or can I set them up in advance with gparted - it might be simpler.
    • Due to already having 2 NTFS primary partitions on the hard disk, I presume that some of the above will need to be logical partitions in an extended partition? How is this done?
    Once the partitions have been set up, and linux is installed, I presume it's just a matter of completing the rest of Part I of the guide, and then ammending /boot/grub/menu.lst to include 'Windows XP'? At that point I am able to restart Windows XP, and only delve into Arch when I want to continue with the configuration, fixing, and so on...
    Sorry for the wall of text, and thanks for your patience. (:
    Last edited by Bedtimes (2009-09-27 14:21:55)

    That's the thing, I expect that I'm doing something wrong with the GRUB loader - and I admit my hard disk layout has been quite strange for a long time before installing linux.
    Basically, it currently looks like this:
    /dev/sda1    ntfs    Music           250GB
    /dev/sdb3    ext2   /boot           120MB
    /dev/dsb4    extended
    ---- /dev/sdb5    linux-swap       1GB
    ---- /dev/sdb6    ext4    /           20GB
    ---- /dev/sdb7    ext4    /home   12GB
    /dev/sdb1    ntfs    Windows XP  50GB
    /dev/sdb2    ntfs    Downloads    150GB
    /dev/sdc1    ntfs    TV & Movies   950GB
    • This list is in order that the entries appear on the hard disk, hence /boot is in the first 1024 cylinders of the hard disk, but as you can see the sdb numbers are actually in the chronological order that I created them.
    • I used an extended partition with logical partitions inside since I had read that there was an issue with more than 4 partitions in a hard disk, and I already had 2 NTFS partitions.
    • When it asked me to install GRUB to the MBR, I installed it to SDB as opposed to SDBx as it asked me to in the manual. This is the drive that contains /boot!
    • I just managed to amend something in the menu.lst, in order that I can boot into Windows XP. Therefore my machine is not totally fucked up any more. (: Unfortunately, what I changed doesn't make sense to me, since I would have expected Windows XP to be on a different hard disk.
    The contents of sdb3:
    grub    kernel26-fallback.img    kernel26.img
    lost+found    System.map26    umlinuz26
    When typing the command /sbin/blkid:
    /dev/sda1: UUID="D0..." LABEL="Music" TYPE="ntfs"
    /dev/sdb1: UUID="A8..." LABEL="Windows XP" TYPE="ntfs"
    /dev/sdb2: UUID="557..." LABEL="Downloads" TYPE="ntfs"
    /dev/sdb3: UUID="2676..." TYPE="ext2"
    /dev/sdb5: UUID="0474..." TYPE="swap"
    /dev/sdb6: UUID="0886..." TYPE="ext4"
    /dev/sdb7: UUID="519becf..." TYPE="ext4"
    /dev/sdc1: UUID="46AC59" LABEL="TV & Movies" TYPE="ntfs"
    Inside /boot/grub/menu.lst:
    timeout 5
    default 0
    color light-blue/black light-cyan/blue
    # (1) Windows XP
    title Windows XP
    rootnoverify (hd0,0)
    chainloader +1
    # (2) Arch Linux
    title Arch Linux
    root (hd1,5)
    kernel /boot/vmlinuz root=/dev/disk/by-uuid/0886... ro vga=773
    initrd          /boot/kernel26.img
    # (3) Arch Linux (Fallback)
    title Arch Linux (Fallback)
    root (hd1,5)
    kernel /boot/vmlinuz root=/dev/disk/by-uuid/0886... ro vga=773
    initrd          /boot/kernel26-fallback.img
    edit: I'm able to access all of the installation partitions with gparted-live's terminal (by mounting the devices I need to access into folders in my root folder), so is there anything else you want me to check/change in order to find my linux root/boot partition?
    Last edited by Bedtimes (2009-09-27 12:54:24)

  • Boot option to Choose os

    I am Using Hp 15doo2tx  model laptop
    In my laptop I have installed two operating System(OS) Windows 8.1 & Ubuntu in different partitions. When I switch on my lap  it was not showing any options for choosing OS automatically windows is booting. If I want to boot Ubuntu  then I want to go for  boot option in the bios and I need to choose Ubuntu. I need options to choose the OS before booting how should I do it. can any one help me?
    I have also edited the grub file (/etc/default/grub) in Ubuntu and made the  time out to 10 seconds still problems remains.
    What is the changes to be made in the  BIOS settings to show OS options before booting?

    RaguS wrote:
    I am Using Hp 15doo2tx  model laptop
    In my laptop I have installed two operating System(OS) Windows 8.1 & Ubuntu in different partitions. When I switch on my lap  it was not showing any options for choosing OS automatically windows is booting. If I want to boot Ubuntu  then I want to go for  boot option in the bios and I need to choose Ubuntu. I need options to choose the OS before booting how should I do it. can any one help me?
    I have also edited the grub file (/etc/default/grub) in Ubuntu and made the  time out to 10 seconds still problems remains.
    What is the changes to be made in the  BIOS settings to show OS options before booting?
    You might to also chekc out the Ubuntu forum as well...a simple search did come up with info from Ubuntu site...
    http://askubuntu.com/questions/221835/installing-ubuntu-on-a-pre-installed-windows-8-64-bit-system-u...
    I am a Volunteer to help others on here-not a HP employee.
    Replies aren't online 24/7 because of Time Zone differences.
    Remember in this Day and Age of Computing the Internet is Knowledge at your fingertips if you choose understand it. -2015-

  • [SOLVED] Board no longer sees uefi as boot option

    Hi,
    I installed Arch on an ssd and was using rEFind to boot the system. It was working fine until I unhooked the ssd from the Mobo to install a hard drive with an old version of arch.( I was going to use the hd for extra space) However, when I hooked my ssd back up the bios did not detect the uefi. It shows the ssd but not the option to boot with uefi.
    When I run lsblk -f from my old installation I can see that the ssd is not mounted to anything. I can mount the ssd with the old installation and see all my files. I just can't boot to the ssd. Any Ideas?
    I have an Asus mobo and a Kingston ssd. Probably not relevant info but thought I would mention it just in-case.
    Last edited by Mgrim (2013-03-08 05:42:47)

    ls -l /dev/disk/by-partuuid/  output
    lrwxrwxrwx 1 root root 10 Mar  4 15:12 0c20bfb2-b03b-467f-9faf-d8f7311027ec -> ../../sdb4
    lrwxrwxrwx 1 root root 10 Mar  4 15:12 38362986-f8ad-416d-86eb-659f7e78f8c3 -> ../../sdb1
    lrwxrwxrwx 1 root root 10 Mar  4 15:12 628b4764-b385-4f6c-a92c-8c1ccc551e19 -> ../../sdb3
    lrwxrwxrwx 1 root root 10 Mar  4 15:12 82e01db0-b264-4555-910d-aa020bccb086 -> ../../sdb2
    -not sure how to do this for sda drive
    refind.conf
    # 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 20
    # Hide user interface elements for personal preference or to increase
    # security:
    # banner - the rEFInd title banner
    # label - 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
    # all - all of the above
    #hideui singleuser
    #hideui all
    # 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 hostname.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.
    #textonly
    # Set the screen's video resolution. Pass this option two values,
    # corresponding to the X and Y resolutions. 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 1024 768
    # 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,linux
    # 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 shell, mok_tool, about, reboot, exit
    # 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,external,optical,manual
    # 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 no additional directories.
    #also_scan_dirs boot,EFI/linux/kernels
    # 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.
    # 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
    # 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
    Last edited by Mgrim (2013-03-05 16:07:44)

  • No windows installed but still have Windows as boot option?

    Hi guys,
    I’ve recently bought a new MBP 15’’ Haswell while trying to install Windows through boot camp, the installation failed, so I tried to remove the partition that was created via boot camp and got an error, had to remove it via disk utility. The process worked well but if I hold option key during start up Windows option still appear along with Macintosh HD and Recovery 10.9.
    My question is, that is happening because I’ve removed the boot camp partition using the disk utility or its supposed to show up, even w/o Windows installed?
    I’ve tried to reset also the NVram and PRAM (cmd + option + p + r) on start up, but Windows option still there. Since it I didn’t have anything on the Macbook still I tried to re-intall the OSX, but still didn’t fix it.
    Please let me know, if its supposed to be like that, Windows to show as boot option even if it isn’t installed, and if not, how to fix it.
    Thanks in advance,
    Regards,
    Tiago

    Allan,
    How to do that? It shows to me a single partition on disk utility. Also, I intent to install Windows again when Apple fix this Boot Camp / Windows 8 problem, that is being reported all over the comunity, do u think that I should format and install OSX again.
    Also if you can guide me how to format everything and install OSX please do so. Because When i tried to format the partition via recovery it gives an error saying that its not possible to mount the partition, something like that.
    Regards,
    Tiago

  • Cannot boot. volume disappeared from boot option after Disk Utility (GUI) repair

    I have a 13-inch MBP with the latest OS X version.
    Problem
    Yesterday, I went to the Recovery Mode and performed Repair on my boot volume. I was not having a problem, but I just wanted to verify and repair as a regular maintenance. The Disk Utility said some kind of error (I cannot remember, but something about EFI?), and I cannot start my computer since then (question mark folder icon when I try to boot).
    I have tried the following
    I tried to recover the drive by going into the Recovery Mode, but when I press Option key for boot options, I just have an empty grey screen have no option(not even the recovery volume). I have also tried to enter into the Single User Mode, but it goes straight back to the question mark folder icon. Just in case, I performed PRAM and SMC reset, but still no dice.
    Next, I tried to boot with Command+R pressed, and the computer went into Internet Recovery Mode, which works fine. Then, I went to the Disk Utility, and my SSD is on the list with the volume that has OS X(only volume on the entire disk except recovery volume, etc). I use FileVault2, and I can unlock the volume and mount it without any problem. When I do Verify Disk, it says that the volume appears to be OK. Also, performed fsck using Recovery Mode's Terminal, and it still says that "The volume Macintosh HD appears to be OK," the exact same message that I got from GUI disk utility. I also tried to unlock and set the volume as a start-up disk, but I still get the question mark folder icon.
    If you need further details, please let me know! Please save me!

    Hello jukim,
    Thanks for using Apple Support Communities.
    Great troubleshooting done so far.  Since you're still booting to the flashing question mark, even after repairing the disk, the next step would be to reinstall OS X.
    A flashing question mark or globe appears when you start your Mac
    https://support.apple.com/kb/TS1440
    OS X Mavericks: Reinstall OS X
    http://support.apple.com/kb/PH13871
    Take care,
    Alex H.

  • [SOLVED] Black screen after kernel boot after pacman -Syu

    Hi, after full system upgrade with pacman -Syu, I get after the kernel boot black screen and everything is freezing. Then need to manually shut down the power button!
    Normally when my system starts up after the kernel boot I get straight to the command line terminal login.
    Can anybody help me how to fix this? Any clues? Any advice is welcome!
    The problem is solved by downgrading to kernel 3.6.11.-1
    Many thanks for the help from the people on #archlinux !
    Last edited by OpenEye (2013-01-29 05:14:04)

    jasonwryan wrote:
    Please stop bumping your thread: use the edit button
    https://wiki.archlinux.org/index.php/Fo … te#Bumping
    What have you done about the errors being printed to your logs? You could start by fixing the network error and the broken udev rule...
    Are you still using intiscripts? They are no longer supported: https://www.archlinux.org/news/end-of-i … s-support/
    # edit: not a pacman issue, moving to Newbie Corner
    I have searched for many hours and days for solutions on the internet and forums, tried some things, but with no results! I don't know how to fix the errors! Do you know how to fix that? I'm a total n00b! I'm doing my best as I can! Need help, thanks!

  • Windows 8 does not have a USB boot option

    QuestionHow can I boot my Windows 8 laptop from a USB device? I created a recovery disk on a USB thumb drive.
    So far I have:
    Entered into the UEFI (BIOS) and set USB to boot first.
    Disabled secure boot.
    I tried to reboot using the general setup options for startup in the windows settings page. I choose boot from USB through the UEFI, but got an error message that system does not have a USB boot option.
    To confirm I also created a bootable DVD with an ISO burner, but my laptop cannot detect a DVD boot option either.
    I assumed that the firmware of the UEFI for this computer allowed a bootable USB but in practice I cannot seem to get this work.
    AnswerTo assist with not being able to boot from a USB device on a Windows 8 laptop, perform the following:
    Plug in USB bootable device.
    Hold down F12 when restarting and access UEFI menu (option is below drive list). If system is set to fast boot, CLICK HERE for instructions on entering the UEFI.
    Go to UEFI and make USB "1st boot".
    Disable secure boot.
    Go to the "Advance" Tab, select "System".
    Change boot order from UEFI to CSM.
    Save changes and exit (F10).
    Computer will restart and boot from USB drive.
    When finished go back into the UEFI and set defaults then save changes and exit (F10). Windows 8 will reboot normally next reboot.

    Done that, only choices are "Set up Firefox to Sync" & "Pair a Device". No ''UNLINK THIS DEVICE". Your turn.

  • A friend bought second hand macbook air mid 2011 with crossed circle on the display, we tried recovery from partition and same thing happened, after internet recovery it stays the same except now it asks for password for boot option, what happened?

    A friend bought second hand macbook air mid 2011 with crossed circle on the display and give to me to try to recover the system, I tried recovery from partition and same thing occured, after internet recovery it stays the same-crossed circle after reboot, then we tried to boot from USB with mac os 10.8 on it, it installs something,like it has being finishing installation, rebootes, and now it asks for password for boot option.We have no idea what that password could be.What happened!!!

    I forgot to write down my computer specs:
    iMac 27 Mid 2011
    2.7 GHz Intel Core i5
    4 GB 1333 MHz DDR3
    AMD Radeon HD 6770M 512 MB
    OS X 10.9.2

  • How can I boot to USB device if no USB boot option in BIOS

    I just purchased a Toshiba NB305-N410BL but am concerned as to how I would image the 250GB HDD if I can not boot from an external cdrom drive.  I tried to backup to shared network folder but none show up on list.  Only boot options in BIOS are HDD, FDD, and LAN.  Thanks for all help in advance.

    Hi, buddy-erp.
    I don't know if my instructions apply to you because I only have the NB305 model. However, if you say you have followed all instructions, that is, 1) insured that no other USB devices are connected to your computer at bootup time and 2) have pressed F12 to enter the boot menu; 3) and then designated the USB flash drive as the source of the bootable restoration software you may need Toshiba technical support. I wonder if there is a BIOS update for your computer too. This may need to be downloaded and installed prior to beginning the restoration process. Nevertheless, as stated, I have a NB305 model and the instructions are clear. FYI (for your information), a virus infected my system and made certain changes to this process. Toshiba technical support informed me that the information displayed was wrong and the process outlined was unnecessary but did require technical support to restore it to the OEM default options.
    Good luck.
    Sincerely,
    Bi-Ill
    Good luck!
    Sincerely,
    Bill5960

  • No boot option after Windows 7 install on Mac Pro

    Hi,
    I have problem and it is very frustrating.
    My configuration
    Mac Pro 1.1 2x2.66
    RAM 5 GB
    HDs
    Bay1 500GB (have a Mac OSx 10.6)
    Bay2 250GB (install Windows 7 Ultimate 64bit)
    Bay3 250GB (in raid Mac OSX 10.6.6) primary system
    Bay4 250GB (in raid Mac OSX 10.6.6)
    I have install Windows 7 via Bootcamp from system 10.6.6 and format and install Windows 7 on HD in Bay2. After installation I try to choose which operating system I want to run (with option key) but nothing happen.
    It was grey screen without apple logo and system boot to Windows 7 only.
    I try everything to boot with different options (key shift,x,c,...) but nothing happen. I can only boot with windows 7 and if is the windows 7 DVD in drive first ask to boot with DVD, after that boot on Windows 7.
    I try to put Mac OS system DVD but still don't want to run.
    I also try to remove HD from Bay1(macosx) and Bay2 (windows7) and boot from Raid HD and I have error that there is no boot system.
    In windows 7 I run Paragon HFS+ and I can see HD500 in Bay1 but cant see in Bay3 and 4 (RAID hd). In disk utility I can see all hard drives.
    I try to reset PRAM but while booting what ever I press nothing happens and boot only windows 7.
    I need solution for this problem, please help me with this issue, thx

    Another thing that might be close...
    I've installed Win7 64-bit on a second HDD. It is Ok to choose boot with 'option' key, but another option is missing: while in win7 apple's bootcamp control panel shows both MacHD and Win7 bootable partitions, so I can tell 'software way' to boot to win or to Snow Leo. It's OK. However when I open 'startup disk' in OS X there's only Mac HD so if I need to reboot to windows I can't just do it with several clicks. I actually have to shut down OS X, wait for boot screen, press option and then wait for the boot options to appear and them choose. It's 'a bit' annoying, let alone windows version of bootcamp seems to do the job smarter. And it really is a good thing to choose "reboot into desired OS" with a click and go to kitchen for tea or something and not seat in front of the machine waiting for boot screen...
    Am I missing something? Is it done the other way then 'system preferences>startup disk'?

Maybe you are looking for

  • Urgent, SELECT statement results in error

    hi all, this is very urgent, could you guys have a look at my SELECT statement?   SELECT vk~kunnr         "customer no           vk~vbeln         "sales order no           vk~audat         "date           vk~vbtyp         "SD DOCUMENT CATEGORY       

  • 32 inch Class 720p LCD HDTV

    I have only had my TV for about 8-9 months and yesterday morning, while watching my local news, I lost the audio.  I tried various channels and still nothing.  I tried shutting the TV off, thinking it would "reset", but no such luck.  I am still with

  • 10.7 Lion Install - Drag and Drop no longer works

    Just upgraded to Lion and my 'drag and drop' featuer works no where... No in finder (desktop to trash), Safari (customizing toolbar), or Dock (removing or rearranging icons). The rest of the track pad and all new gestures work flawlessly, but when I

  • ITunes doesn't open on my ipad

    When I try to connect to the iTunes store frm my iPad, it says can't connect. This despite my wifi being in working condition. I am able to use my brows er but not iTunes store. Can anyone help? Btw, apple support *****.

  • How to start java app with many jar files

    Hi, I have an application that makes use of 50 jar files. When I try to start the application, I need a very long command line like java -classpath file1.jar;file2.jar;file3.jar; ... de.me.myapp.myclass This is not very handy. Is there a shorter way