Booting solaris 9:  /etc/bootrc?

I have installed solaris in PIII 500 and all works perfect during instalation, but when reboot to run this message appear:
<i>boot:source: open of '/etc/bootrc' failed</i>
I try to boot with the software CD1 of 2 and it say the same
I'm changing from windows and my knowledge of unix is limited, so can you give me solutions with simple words?
Thanks to all

Do you have more than one HDD installed in the system, and did you
try to install Solaris to the secondardy disk?
It seems the <font face="Courier">boot: source: open of '/etc/bootrc' failed</font>
problem is a bug in the Solaris installer. It writes the wrong bootpath
property to the root filesystem of the new Solaris installation.
<div class="pre"><pre> ----------------------</pre></div>
I just tried to install Solaris 10 b69 on c1d0s6.
c0d0 is the boot disk, master device on the primary ide channel.
c1d0 is another ide disk, master device on the secondary ide channel.
The physical device path for c1d0s6 is
<div class="pre"><pre>
# ls -l /dev/dsk/c1d0s6
lrwxrwxrwx 1 root root 50 Jan 9 2004 /dev/dsk/c1d0s6 ->
../../devices/pci@0,0/pci-ide@7,1/ide@1/cmdk@0,0:g
</pre></div>
But the installer writes this to /boot/solaris/bootenv.rc:
<div class="pre"><pre>
# grep bootpath /sol10/boot/solaris/bootenv.rc
setprop bootpath /pci@0,0/pci-ide@7,1/ide@0/cmdk@0,0:g
</pre></div>
(Note: "<a href="mailto:ide&#64;0" target="_blank">ide&#64;0</a>" instead of "<a href="mailto:ide&#64;1" target="_blank">ide&#64;1</a>")
Solaris 10 cannot be booted from the secondary disk, the Solaris boot code
reports:
<div class="pre"><pre>
Run Error: File not found
boot: source: open of '/etc/bootrc' failed
</pre></div>
Changing the bogus bootpath in bootenv.rc fixes the boot problem.
It should be possible to fix the bootpath by interrupting the boot process
with ESC, and setting the correct boot device in the "Boot Tasks" submenu
on the last screen named "Boot Solaris".

Similar Messages

  • Dual booting Solaris 8 with Windows

    Hello!
    I am going to build a machine for running both Solaris 8 and 98 SE. I may put each OS on a separate hardrive or just put them on different partitions/slices. Firstly, is this possible? and secondly how? Do I have to edit the etc/bootrc script???
    I'd appreciate some help on this one.
    Steve

    1. helpful group - yahoo groups -> solarisonintel
    2. stolen from a message in that group -> multiboot.solaris-x86.org/v/6.html

  • Problem booting Solaris 10 on ProLiant server after installation.

    Hi all!
    I have a brand new HP ProLiant DL360 G5 server. It contains 6 internal
    hard drives. RAID 5 is configured on these drives using built-in HP
    Smart Array P400i controller. I've just installed Solaris 10 8/07 on this
    server. Solaris requires a driver for P400i controller. I'm using Driver
    Update CD created from HP provided ISO image. Solaris 10 is
    officially supported OS for DL360 G5 server.
    Installation proceeds as expected:
    1) At the begining of Solaris installation, Driver Update is used to
    load HP driver for raid controller. During installation, disk is
    recognized as c1d0t0 (the only disk in system); one partition is
    created on this disk.
    2) Disk is devided to 6 slices:
    c1d0t0s0 - swap, 4GB
    c1d0t0s1 - /, cca 32GB
    c1d0t0s[3,4,5,6] - /zones/[a,b,c,d] - each cca 160GB
    3) At the end of installation, CPQary3 driver is installed to target
    system without any errors reported. No errors are reported during
    installation at all.
    After reboot, GRUB is started. It shows boot menu containing two
    options:
    - Solaris 'normal' boot
    - failsafe boot
    PROBLEM: Selecting 'normal' boot leads to immediate system restart.
    According to documentation, this case occurs when PCQary3
    driver is not installed.
    I'm able to boot using 'failsafe' option in grub. After entering single
    user, I load PCQary3 driver to runtime using 'install-du' command.
    I'm also able to find instaled Solaris using 'install-recovery' and mount
    its root volume to /a directory. Necessary driver IS installed inside
    /a/kernel/drv/ directory. Options 'bootpath' in /a/boot/solaris/bootenv.rc
    file is set up correctly pointing to device associated with /dev/dsk/c1d0t0s1
    device. Also GRUB is able to recognize UFS filesystem for boot partition.
    I've already tried (without success):
    1) Use RAID 1+0 instead of RAID5
    2) Create only 3,5GB partition instead of 700GB large one.
    3) Place / on c1d0t0s0 instead of c1d0t0s1.
    4) Re-create boot archive using 'bootadm update-archive -R /a'
    So, everything seems to be installed correctly, but system cannot boot.
    Do you have any ideas how to fix this problem?
    Jozef

    Sounds like an issue I just had with a brand new X4150, installation and failsafe worked fine, but normal booting led to immediate reboot of the server. This was due to an incompatibility of solaris and intel's newest generation xeon chips.
    You can still boot 'normal' solaris in 32-bit mode:
    hit 'e' at the grub menu, 'e' again to edit the 'normal' boot entry and add 'kernel/unix' after multiboot. This should boot up solaris in 32-bit mode. From there, download and install the latest patch set (125370-06 and 127112-05 are fixing this issue). After that you should be fine.
    Bjoern

  • Dual boot Solaris 8 and Windows XP

    Hello. I currently have windows xp as my OS. I would like to install Solaris 8 as a secondary OS. I have a separate hard drive I would like to put Solaris on. My question is, will the solaris installation allow me to choose which drive to install solaris to? Also, how can I set up my system to boot windows if I do nothing, but boot solaris if I choose to? Thanks for any help, I'm new to solaris and to dual-booting.

    Try this URL:
    http://sun.pmbc.com/faq/9.html
    Hope it helps.
    Senthilkumar
    Developer Technical Support
    Sun Microsystems, Inc.
    http://www.sun.com/developers/support

  • How do can I use Jumpstart to boot Solaris from Slave Drive

    Hi all,
    I have XP on Master Drive and I used Jumpstart to install Solaris on Slave Drive.
    This is the profile:
    install_type     initial_install
    system_type     standalone
    usedisk          c0d1
    boot_device      c0d1 update
    root_device     c0d1s0
    fdisk           c0d1 solaris all
    partitioning     explicit
    filesys          c0d1s0 10000 /
    filesys          c0d1s1 1111 swap
    filesys          c0d1s7 free /export/home
    cluster          SUNWCreq
    Now, I specified that the boot_device is c0d1 but after the installation the boot device is c0d0 which is my Master Drive...
    ...when I use Windows Boot Manager to boot Solaris... it cannot find the boot files on the master drive so it runs the DCA...
    ... so under the DCA I have to tell Solaris that the boot files are in my Slave Drive then I save it.
    ...I don't want to make this change everytime
    any ideas that would make this install hands free?

    ...don't know the answer to that but here is an alternative:
    ... use this as your finish script
    ... it changes the bootpath in bootenv.rc to point to the slave drive
    #!/usr/bin/perl
    open(INFILE,"/a/boot/solaris/bootenv.rc");
    open(OUTFILE,">/a/boot/solaris/bootenv.rc_out");
    while(<INFILE>) {
    chomp;
    #--cmdk@0,0 is the master drive
    #--cmdk@1,0 is the slave drive
    s/cmdk\@0\,0/cmdk\@1\,0/g;
    print OUTFILE "$_\n";
    #...replace bootenv.rc_out with bootenv.rc
    ...happy programming

  • Can't boot Solaris 10 during installation

    I am stuck up with a petty problem while booting Solaris 10 1/06 from the installation CD no.1. The GRUB boot loader appears fine, but when I try to boot the Solaris kernel and module, a message appears
    Error 28: Selected item cannot fit into memory
    My x86 computer's configuration is as follows:
    Intel Pentium 4 processor 2.83 GHz
    RAM 128 MB
    HD 80GB
    I can't figure out whether the problem is really due to insufficient memory or do I need to install more RAM on my platform.Can someone help me out with this?

    128mb is plenty of memory. No it isn't plenty of memory. Solaris 10 Update 1 or Solaris Express needs at least
    256mb of memory. The initial root ramdisk that is loaded from the CD/DVD
    uncompresses to ~ 128mb already, leaving no space for the SunOS kernel on a
    system with only 128mb of memory!

  • Cannot boot Solaris 11.1 Live Media for x86

    Hi,
    if I boot from Live-CD (burned "sol-11_1-live-x86.iso"), it comes:
    ---begin---
    atapi_id_upate: select failed
    ata_command: select failed DRY 0x1 CMD 0xef F 0x66 N 0x0 S 0x0 H 0x0 CL 0x0 CH 0x0
    WARNING: /pci@0,0/pci1002,43a0@15/pci-ide@0/ide@1 (ata1):
    timeout: abort request, target=1 lun=0
    ---end---
    Any hints?
    Thanks!
    dynup
    Edited by: dynup on 19.02.2013 02:42

    dynup wrote:
    ---begin---
    atapi_id_upate: select failed
    ata_command: select failed DRY 0x1 CMD 0xef F 0x66 N 0x0 S 0x0 H 0x0 CL 0x0 CH 0x0
    WARNING: /pci@0,0/pci1002,43a0@15/pci-ide@0/ide@1 (ata1):
    timeout: abort request, target=1 lun=0
    ---end---
    Any hints?Have you checked that the disc is actually readable by the CD drive which you use for booting? Perhaps it may help to use a USB stick to boot Solaris.
    Kind regards,
    Steffen

  • Dual boot Solaris 9 and Solaris 10 on a SCSI hard disk

    Hi,
    I would like to dual boot Solaris 9 and Solaris 10 on a SCSI hard disk. Currenlty that 16gb hard disk has Solaris 9 installed on it.
    What are the steps needed to install Solaris 10 and dual boot them?
    Thanks a million.
    ldd

    Unfortunately we can't help you as this forum is only for questions or problems relating to Sun Update Connection, Patch Manager 2.0, & PatchPro 2.2.
    We recommend you post your question on one of the Solaris OS forums:
    http://forum.sun.com/jive/category.jspa?categoryID=139

  • ??? - Install CD w/ custom /boot/solaris/devicedb/master ?

    Howdy Friends:
    Any suggestion on how I might go about creating a custom Solaris 10 install CD with a modified /boot/solaris/devicedb/master file? My IDE controller isn't recognized by Solaris 10, and I need to modify the master file to include the driver info (Sil 0680 IDE RAID) for installation.
    I am aware I could just create an install floppy via DD, however this system does not have a floppy drive nor a working FDD controller. I also cannot boot via a USB floppy due to no support in the BIOS.
    I've tried installing via a network install (PXE), but I never get past the "Solaris Network Boot..." screen.
    Any help installing on this system would be awesome. I'm excited to use Solaris 10!
    -- JWheeler
    tpawiredboy*at*unequa-tsi.net

    The process for creating a bootable Solaris x86 CD is quite a bit harder than it is on Sparc hardware. Or at least it was with the only process I know about. It is much simpler to perform a network-based installation.
    One catch to the network install, however, is that a Sparc system cannot read all the partitions on the x86 Solaris CD. I had to put the disc into an existing Solaris x86 system, NFS mount a directory from my Sparc server, and perform a "./setup_install_server" from the x86 system to the NFS directory.
    Once that was complete, I could use the Sparc server to jumpstart the x86 systems using custom configurations. It also allowed me to install the correct drivers for the x86 system in question that were not part of the Solaris CD (which is one of the problems you describe).
    I realize that you were probably looking for a simpler answer that this...

  • Booting Solaris on OpenSPARC

    Hi all,
    I'm trying to boot Solaris on a Xilinx ml411 board with one OpenSPARC core.
    I wrote the following files to the matching OpenSPARC address.
    0xff f000 0000 - OpenSPARCT1_Arch.1.5/hypervisor/src/greatlakes/ontario/t1_fpga/prom.bin
    0xff f008 0000 - OpenSPARCT1_Arch.1.5/S10image/openboot.bin
    Can someone explain the error below.
    Thanks,
    Teck Hua
    <Output>
    Entering hypervisor
    Scrubbing initial RAM
    Copying from ROM to RAM
    Entering hypervisor
    Running from RAM
    Hypervisor version: Hypervisor 0.1 2007/08/03 11:23 [greatlakes:ontario:t1_fpga] Not scrubbing remaining hypervisor RAM. Using pre-initialized memory.
    Not scrubbing guest memory. Using pre-initialized guest memory.
    Using pre-initialized Guest stand-alone program memory image.
    WATCHDOG: pcpu: 00000000 tl: 00000003 tt: 00000010 gl: 00000003 trap state:
    tl: 00000001 tt: 000001ff htstate: 00000004 tstate: 0000000000000400
    tpc: fffffffffffffffc tnpc: fffffffffffffffc
    tl: 00000002 tt: 000001ff htstate: 00000000 tstate: 0000000814001400
    tpc: fffffffffffffffc tnpc: fffffffffffffffc
    tl: 00000003 tt: 00000010 htstate: 00000000 tstate: 0000024400001400
    tpc: 0000000000800020 tnpc: 0000000000800024 trap globals:
    gl: 00000000
    %g0-%g3: 0000000000000000 0000000000000014 0000000000001890 0000000000070000
    %g4-%g7: 0000000000000000 0000000000064dc8 0000000000064dc8 0000000000009ab8
    gl: 00000001
    %g0-%g3: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
    %g4-%g7: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
    gl: 00000002
    %g0-%g3: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
    %g4-%g7: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
    rtba: 0000000000800000

    Hi,
    OpenSPARC T1 v1.5 does not support Solaris boot. This feature is scheduled for v1.6 which is expected to come out soon.
    With v1.5, you can boot hypervisor and can run stand-alone C program. Method to link C program executable in the hypervisor binary is described in the Design and Verification document.
    openboot.bin included in the S10image directory is meant for booting Solaris on Legion full-system simulator.
    HTH.

  • Installed flash disk does not boot (Solaris 10 on Fore CPU-50 VME cpu-card)

    Greetings,
    After installation of Solaris on a system with a flask disk as system disk, the disk is not bootable.
    Configuration:
    System: Fore CPU-50 VME cpu-card (sparc50)
    OS: Solaris 10 (Sparc version, CD-media)
    System-disk: ADTRON S35FA-8GC20N Smart Storage 3.5” SCSI Flash pack.
              (configured as c0t1d0)
    Error message at boot:
    Can’t read disk label
    Can’t open disk label package
    When I mount the installed disk on another system I can read and inspect the flash disk.
    The logging files begin.log, finish.log and install_log in the /var/sadm/system/logs/ directory don’t mention any errors during installation phase.
    The logging file /var/sadm/system/logs/install_log begins with:
    Configuring disk
    -     Creating Solaris disk label (VTOC)
    Creating and checking UFS filesystems
    -     Creating / (c0t1d0s0)
    -     etc.
    This install_log file ends with:
    Installing boot information
    -     Installing boot blocks (c0t1d0s0)
    -     Updating system firmware for automatic rebooting
    How can I make this flash disk bootable?
    Thanks,
    Herm

    It's a G3 with the integrated 5 i Smart array
    controller. There are driver updates for Sol 10 on
    the HP side. Just filter for OS. There you get the 5i
    driver !
    greets
    D@veI searched the HP site, but wasn't able to find the driver for Solaris 10. Could you give me the url? I did find links for drivers for Solaris 8 & 9 though.
    Thanks,
    -Jeff

  • V240 can't boot: Solaris 10

    Hi all
    I am having trouble booting one of my remote systems via the alom. Three days prior to this issue I successfully booted the machine, did some work on it, and then gracefully shut it down. I am unable to boot the machine now though.
    Here is the error I get:
    {1} ok boot
    Probing system devices
    Probing memory
    ChassisSerialNumber xxxxxx
    Probing I/O buses
    Sun Fire V240, No Keyboard
    Copyright 2007 Sun Microsystems, Inc.  All rights reserved.
    OpenBoot 4.22.33, 4096 MB memory installed, Serial #xxxxxx.
    Ethernet address xxxxxx, Host ID: xxxxxxx.
    Rebooting with command: boot                                         
    Boot device: disk  File and args:
    Boot load failed.
    The file just loaded does not appear to be executable.I have searched on Google and found a few things which I have tried (install bootblock, etc) but it has not solved my problem. Any ideas on how to get this sorted or is it a disk fault?

    Yip, I have tried those. Tried an upgrade install as well...then hit a speed bump;
    &#9472; Upgrading Solaris Software - Progress     &#9472;&#9472;&#9472;&#9472;&#9472;&#9472;&#9472;&#9472;&#9472;&#9472;&#9472;&#9472;&#9472;&#9472;&#9472;&#9472;&#9472;&#9472;&#9472;&#9472;&#9472;&#9472;&#9472;&#9472;&#9472;&#9472;&#9472;&#9472;&#9472;&#9472;&#9472;&#9472;&#9472;&#9472;&#9472;&#9472;&#9472;&#9472;&#9472;&#9472;
      The Solaris software is now being upgraded on     the system using the profile
      you created. Upgrading Solaris software can take up to 2 hours (may be
      longer on servers) depending on the software you've selected,     the
      reallocation of any space if needed, and the speed of     the network or local
      CD-ROM.
      When Solaris software     is completely upgraded,     the message `Upgrade complete'
      will be displayed.
           0                                                          100
    panic[cpu0]/thread=2a10277fca0: free: freeing free block, dev:0x5500000001, block:22856, ino:326218, fs:/a
    000002a10277f1c0 ufs:real_panic_v+60 (0, 18d7ad0, 2a10277f460, 180c000, 0, 60010db5880)
      %l0-3: 000000007018c078 000000007018c100 000000000180c310 000000007bbb7ce8
      %l4-7: 00000000704faa40 0000060011da5430 0000000000000064 0000000001815000
    000002a10277f270 ufs:ufs_fault_v+c8 (600168a76c0, 18d7ad0, 2a10277f460, 0, 60011d04d28, 180c000)
      %l0-3: 0000000000000000 0000000000022120 000000000187a000 0000000000000000
      %l4-7: 000000000180c000 0000000000000000 0000060011d04c80 0000000000000001
    000002a10277f320 ufs:ufs_fault+1c (600168a76c0, 18d7ad0, 5500000001, 5948, 4fa4a, 600127b60d4)
      %l0-3: 00000600127b6000 0000030003b44158 000002a10277f630 00000000018d7800
      %l4-7: 0000030003b44000 000000000000007b 0000000000000089 0000000000000001
    000002a10277f3d0 ufs:indirtrunc+28c (55c, 30003b3e000, ffffffffffffffff, 0, 10, ffffffffffffffff)
      %l0-3: 0000000000000089 0000000000000010 000006001dfcb260 000000000000008d
      %l4-7: 0000030003b3f570 00000000005c9948 000000000000055c ffffffffffffffff
    000002a10277f4a0 ufs:indirtrunc+248 (3, 30003bbc000, ffffffffffffffff, 1, 10, 0)
      %l0-3: 0000000000000089 0000000000000000 000006001dfca2e0 000000000000008d
      %l4-7: 0000030003bbc00c 00000000005c5da8 0000000000000003 ffffffffffffffff
    000002a10277f570 ufs:ufs_itrunc+690 (600168a4750, 0, 2a10277f7a8, b, 45e0c8, 8d)
      %l0-3: 0000000000000000 000002a10277f6ac 0000000000000001 000002a10277f630
      %l4-7: 0000000000000000 00000600127b6000 ffffffffffffffff 0000000000000010
    000002a10277f800 ufs:ufs_trans_itrunc+19c (600168a4750, 0, 81, 21, 0, 2a10277f8d0)
      %l0-3: 000002a10277f8d8 0000000000000080 000000000000ffbf 0000000000000040
      %l4-7: 0000060011d04cc8 00000600168a4830 0000060011d04c80 00000600127b6000
    000002a10277f8e0 ufs:ufs_delete+3a0 (60011d04c80, 600168a4750, 81a4, 0, 600168a76c0, 1)
      %l0-3: 00000000000081a4 000000000000f000 00000600168a4770 0000000000000000
      %l4-7: 00000600168a4830 0000000000000001 0000000000000000 000000000000f000
    000002a10277f9c0 ufs:ufs_thread_delete+dc (600168a4750, 18d8400, 600168a4750, 2a10277fa70, 60011d04c80, 60011d04cf0)
      %l0-3: 0000060011d04cd0 0000000000000000 00000600168a4750 0000000000000000
      %l4-7: 0000000000000001 00000600168a4750 00000600168a4750 00000600168a4750
    syncing file systems... [2] [2] [2] [2] [2] [2] [2] [2] [2] [2] [2] [2] [2] [2] [2] [2] [2] [2] [2] [2] [2] done (not all i/o completed)
    dumping to /dev/md/dsk/d13, offset 839909376, content: kernel
    100% done: 52724 pages dumped, compression ratio 3.66, dump succeeded
    rebooting...
    Probing system devices
    Probing memory
    ChassisSerialNumber xxxxxx
    Probing I/O buses
    Sun Fire V240, No Keyboard
    Copyright 2007 Sun Microsystems, Inc.  All rights reserved.
    OpenBoot 4.22.33, 4096 MB memory installed, Serial #xxxxx
    Ethernet address xxxxxx, Host ID: xxxxxx
    Rebooting with command: boot                                         
    Boot device: disk  File and args:
    Boot load failed.
    The file just loaded does not appear to be executable.Things seem to be pointing to a faulty disk. When I ran fsck on the two mirrored boot slices I got errors. It eventually fixed them up after running fsck a few times. Still can't boot though.

  • Dual Boot Solaris 2.5.1 and 2.8

    Is it possible to dual boot a Sparc Ultra 10 workstation with Solaris 2.5.1 and a more recent version (such as 2.8). If so please point me to some documentation.
    This is required as we are running several pieces of software licensed against the hostid, that will soon require different versions of Solaris.
    Thanks in anticipation.

    You should make an alias for your second OS location, for example disksol28.The easiest way to do this is run the format command. Write down the physical path for each disk you see. Your boot disk is probably c0t0d0 and the second disk, if you have one would be c0t1d0. If you are going to install 2.8 on another slice/partition of the first disk, write down that pathname, you'll need it for the nvalias command. If you are going to install it on the second disk then the alias "disk1" will probably work already, if you did not change the eeprom during install. You'll just have to:
    ok
    boot disk1
    If you install 2.8 on another slice of your single disk then do not forget to include the slice in your alias.
    If I asume your 2.5.1 is a flat file system (/ only, no /usr, /var, /opt, /export etc.) on slice 0 and swap is on Slice 1, then I can put another flat file system on Slice 3 - don't touch Slice 2. This OS can use the same swap Slice 1. To create an alias to boot from Slice 3:
    ok
    nvalias disksol28 <pathname from format goes here> :d
    reset <- (locks it in to NVRAM)
    example:
    nvalias disksol28 /pci@1f,400/pci@1/disk@0,0:d
    reset
    Note:Slice 0 is asumed in most aliases. For example if your alias ends wih disk@0,0 Slice 0 is assumed. You can also say disk@0,0:a to indicate Slice 0 but ":a" is not really needed.
    If you are booting off of any other slice then it must be indicated in your alias.
    Slice
    0 :a
    1 :b
    2 :c
    3 :d
    4 :e
    5 :f
    6 :g
    7 :h
    If you want to create an alias for your second disk (c0t1d0) with root on slice 0:
    ok
    nvalias disksol28 <pathname from format goes here>
    reset <- (locks it in to NVRAM)
    example:
    nvalias disksol28 /pci@1f,400/pci@1/disk@1,0
    reset
    Please write down any custom aliases because a Stop+n or set-defaults will wipe them out.
    If you make a mistake with nvalias then:
    ok
    nvunalias disksol28
    reset
    If you want disksol28 to be your primary boot device then:
    ok
    setenv boot-device disksol28
    setenv diag-device disksol28
    reset
    Good Luck,
    John

  • Booting solaris with cd

    Hi All!
    I got a annoying problem here, we have about 30 PCs installed with solaris 7, I want now to backup the ufs partition, where the solaris installation is on, my idea is to boot with a solaris cd, mount the backup file server via nfs, then dump the partition I want to backup with ufsdump, for restoring would be the same procedure, only with ufsrestore..
    now my problem, because I'm still quite new treating solaris issues, I just don't know how to get the network connection after I have booted with the install cd ( after starting with the webstart I got a offer from the installer, that it wants to make a partition so that it can copy all the boot files, because I don't want to have any change on my harddisk, I said no and get a shell. with ifconfig I can only see the loop device, I also tried to make a /etc/hostname.elxl0 file, but the mounted ramdisk is read only.....
    How can I get network connection after booting with the Install CD?
    we have 3com network cards, all the PCs are in a nis+ network.
    thanks a looooot for answers
    Luotao Fu

    I am at an early stage with this though I started some time ago. I downloaded all the Solaris files ending up with images named like sol-8-u7-ia-v1-a.zip.
    I unzipped the files.
    I was not sure what to do next as I am seeing comments about renaming the files with a suffix .iso. I have not done this. I seem to have Easy CD Creator, (I can see now I have started the HP software I have) and have selected the data option. It has written the first of my files to CD. This is called sol-8-u7-ia-v1-a
    I cannot boot from it, and do not know whether to change the bios to boot from CD.
    Please could someone tell me where the definitive instructions are.
    I found references to using downloading the DCA and putting it on to floppy. Well I have downloaded but at 1.44 Mb it will not write to a floppy!
    Thanks for any help
    Mike Gunner
    Reading UK (at home)

  • [SOLVED] efibootmgr not generating boot loader (rEFInd, etc.) entry.

    Hello,
    The following command runs without problem or any output. It wouldn't create any entry. Also my refind.conf is not being followed. rEFInd is able to detect kernels and boot fine from /boot
    efibootmgr -c -g -d /dev/sda -p 1 -w -L "rEFInd" -l '\EFI\refind\refind_x64.efi'
    Information
    efibootmgr 0.6.0-1
    refind-efi 0.6.8-1
    Linux 3.8.4-1-ARCH
    sudo efibootmgr
    BootCurrent: 000A
    Timeout: 0 seconds
    BootOrder: 0006,0007,0008,0009,000A,000B,000C,000D,000E,000F,0010,0011,0012,0013
    Boot0000 Setup
    Boot0001 Boot Menu
    Boot0002 Diagnostic Splash Screen
    Boot0003 Startup Interrupt Menu
    Boot0004 ME Configuration Menu
    Boot0005 Rescue and Recovery
    Boot0006* USB CD
    Boot0007* USB FDD
    Boot0008* ATAPI CD0
    Boot0009* ATA HDD2
    Boot000A* ATA HDD0
    Boot000B* ATA HDD1
    Boot000C* USB HDD
    Boot000D* PCI LAN
    Boot000E* ATAPI CD1
    Boot000F* ATAPI CD2
    Boot0010 Other CD
    Boot0011* ATA HDD3
    Boot0012* ATA HDD4
    Boot0013 Other HDD
    Boot0014* IDER BOOT CDROM
    Boot0015* IDER BOOT Floppy
    Boot0016* ATA HDD
    Boot0017* ATAPI CD:
    Boot0018* PCI LAN
    ls -R /boot
    /boot:
    EFI initramfs-linux-fallback.img initramfs-linux.img refind_linux.conf vmlinuz-linux
    /boot/EFI:
    boot refind tools
    /boot/EFI/boot:
    bootx64.efi icons refind.conf
    /boot/EFI/boot/icons:
    *** Icons
    /boot/EFI/refind:
    icons refind.conf refind_x64.efi
    /boot/EFI/refind/icons:
    *** icons
    /boot/EFI/tools:
    drivers shells
    /boot/EFI/tools/drivers:
    ext2_x64.efi ext4_x64.efi hfs_x64.efi iso9660_x64.efi reiserfs_x64.efi
    /boot/EFI/tools/shells:
    Shell.efi Shell_Full.efi
    cat /boot/refind_linux.conf
    "Boot to X" "root=PARTUUID=5416f920-35fc-42a8-8a34-564c8c332bfe ro rootfstype=ext4 add_efi_memmap systemd.unit=graphical.target"
    "Boot to Console" "root=PARTUUID=5416f920-35fc-42a8-8a34-564c8c332bfe ro rootfstype=ext4 add_efi_memmap systemd.unit=multi-user.target"
    # 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 5
    # Hide user interface elements for personal preference or to increase
    # security:
    # banner - the rEFInd title banner (built-in or loaded via "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
    # safemode - remove the submenu option to boot Mac OS X in "safe mode"
    # 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
    # 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, as well as PNG images.
    #banner hostname.bmp
    #banner mybanner.png
    # 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,
    # or a PNG image. The PNG format is required if you need transparency
    # support (to let you "see through" to a full-screen banner).
    #selection_big selection-big.bmp
    #selection_small selection-small.bmp
    # Set the font to be used for all textual displays in graphics mode.
    # The font must be a PNG file with alpha channel transparency. It must
    # contain ASCII characters 32-126 (space through tilde), inclusive, plus
    # a glyph to be displayed in place of characters outside of this range,
    # for a total of 96 glyphs. Only monospaced fonts are supported. Fonts
    # may be of any size, although large fonts can produce display
    # irregularities.
    # The default is rEFInd's built-in font, Luxi Mono Regular 12 point.
    #font myfont.png
    # 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
    textonly
    # Set the EFI text mode to be used for textual displays. This option
    # takes a single digit that refers to a mode number. Mode 0 is normally
    # 80x25, 1 is sometimes 80x50, and higher numbers are system-specific
    # modes. Mode 1024 is a special code that tells rEFInd to not set the
    # text mode; it uses whatever was in use when the program was launched.
    # 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 1024 (no change)
    #textmode 2
    textmode 1024
    # 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 1024 768
    #resolution 3
    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
    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
    scan_driver_dirs /boot/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
    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 UNLESS you include
    # a volume name and colon before the directory name, as in "myvol:/somedir"
    # to scan the somedir directory only on the filesystem named myvol. 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,ESP2: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 "Recovery HD".
    #dont_scan_volumes "Recovery HD"
    # 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, unless you precede
    # the directory name by a filesystem name, as in "myvol:EFI/somedir"
    # to exclude EFI/somedir from the scan on the myvol volume but not on
    # other volumes.
    #dont_scan_dirs ESP:/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,TextMode.efi,ebounce.efi,GraphicsConsole.efi,MokManager.efi,HashTool.efi,HashTool-signed.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. 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
    default_selection "vmlinuz-linux"
    # 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
    cat /etc/fstab
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    # /dev/sda2
    UUID=7b92a840-4747-43b7-b2cf-02cbf92afce7 / ext4 rw,relatime,data=ordered 0 1
    # /dev/sda4
    UUID=72f64fd4-a3f1-424c-8fe3-cdf7751a84e0 /home ext4 rw,relatime,data=ordered 0 2
    # /dev/sda1
    # UUID=5447-7409 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
    UUID=5447-7409 /boot vfat noatime 0 2
    # /dev/sda3
    UUID=1e11bea5-41db-4969-a8fa-a461734b71ac none swap defaults 0 0
    This is a clean install using April 01 ISO with minimal or no modifications. I have tried to follow wiki as precisely as possible. I am not sure what I am missing. Thanks.
    EDIT1: Updated and cleaned the post to better reflect current structure and added /etc/fstab.
    EDIT2: @swordfish Removed /boot/EFI/arch.
    Last edited by donniezazen (2013-04-04 06:37:07)

    I used March ISO instead of April ISO and it worked flawlessly. There is some problem with April ISO where efibootmgr and UEFI Shell1/2 fail with ASSERT_EFI_ERROR (status = device error).
    I have removed both /boot/EFI/boot and /boot/EFI/arch. I now have two entries one on vmlinuz-linux on 1024 Fat 32 partition which works and second one boot/vmlinuz-linux on 20G / partition which fails and takes me to rootfs. Also refind isn't showing UEFI shells that  I have in /boot/EFI/tools/Shells.
    ls -R /boot
    /boot:
    EFI initramfs-linux-fallback.img initramfs-linux.img refind_linux.conf vmlinuz-linux
    /boot/EFI:
    drivers refind tools
    /boot/EFI/drivers:
    ext2_x64.efi ext4_x64.efi hfs_x64.efi iso9660_x64.efi reiserfs_x64.efi
    /boot/EFI/refind:
    icons refind.conf refind_x64.efi
    /boot/EFI/refind/icons:
    ### Icons
    /boot/EFI/tools:
    Shell.efi
    # 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 5
    # Hide user interface elements for personal preference or to increase
    # security:
    # banner - the rEFInd title banner (built-in or loaded via "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
    # safemode - remove the submenu option to boot Mac OS X in "safe mode"
    # 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
    # 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, as well as PNG images.
    #banner hostname.bmp
    #banner mybanner.png
    # 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,
    # or a PNG image. The PNG format is required if you need transparency
    # support (to let you "see through" to a full-screen banner).
    #selection_big selection-big.bmp
    #selection_small selection-small.bmp
    # Set the font to be used for all textual displays in graphics mode.
    # The font must be a PNG file with alpha channel transparency. It must
    # contain ASCII characters 32-126 (space through tilde), inclusive, plus
    # a glyph to be displayed in place of characters outside of this range,
    # for a total of 96 glyphs. Only monospaced fonts are supported. Fonts
    # may be of any size, although large fonts can produce display
    # irregularities.
    # The default is rEFInd's built-in font, Luxi Mono Regular 12 point.
    #font myfont.png
    # 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
    textonly
    # Set the EFI text mode to be used for textual displays. This option
    # takes a single digit that refers to a mode number. Mode 0 is normally
    # 80x25, 1 is sometimes 80x50, and higher numbers are system-specific
    # modes. Mode 1024 is a special code that tells rEFInd to not set the
    # text mode; it uses whatever was in use when the program was launched.
    # 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 1024 (no change)
    #textmode 2
    textmode 1024
    # 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 1024 768
    #resolution 3
    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
    showtools shell, 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
    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
    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 UNLESS you include
    # a volume name and colon before the directory name, as in "myvol:/somedir"
    # to scan the somedir directory only on the filesystem named myvol. 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,ESP2: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 "Recovery HD".
    #dont_scan_volumes "Recovery HD"
    # 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, unless you precede
    # the directory name by a filesystem name, as in "myvol:EFI/somedir"
    # to exclude EFI/somedir from the scan on the myvol volume but not on
    # other volumes.
    #dont_scan_dirs ESP:/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,TextMode.efi,ebounce.efi,GraphicsConsole.efi,MokManager.efi,HashTool.efi,HashTool-signed.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. 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
    Thanks for suggesting to try older ISO.
    UPDATE:- Most recent ls -R /boot and my refind.conf. Reading over Rod Smith's rEFInd documentation has helped me clean up a little more and set up a good boot manager with automatic kernel detection and shell. I do want to get rid of drivers list that shows itself up along with kernel. Next is to tackle menu entry. Thanks.
    Last edited by donniezazen (2013-04-04 06:43:16)

Maybe you are looking for

  • Different Compressor settings for export in FCPX = same result

    HI For test purposes for a movie screener to upload, I've been changing the settings of a custom Compressor setting I imported into FCPX but seem to get the same result size-wise whether its 1- or 2-pass. Do I need to delete the icon in FCPX and then

  • Need Of Important Updates Required Asha 305

    I loved the update of Nokia Asha 305 V7.42. But there are many missing features which are required. Phone memory gets full and only remedy i find is deleting the messages and contacts or going to nokia care and reflashing it. Removing of unwanted app

  • Table difference between different versions

    how do i find out which sap tables has been changed between 4.6C and ecc 6.0 version.  Is there a program I can run? website?

  • BPM Required ??

    I have the following scenario 1) Sync SOAP Sender sends data to XI (Webservice call to XI) 2) XI calls a stored procedure in a database ( JDBC Receiver ) (Sync) 3) Based on result of step2 jdbc call, XI will call another stored procedure in a databas

  • I am trying to understand servlets

    In the tutorial it says : 2. In a terminal window <INSTALL>/j2eetutorial14/examples/web/bookstore1/. What is the terminal window is this a J2EE editor window of some sort? I do not quite understand what they mean by "terminal window".