[SOLVED] xrdb not reading .Xresources at boot

spent a few hours trying to figure this out yesterday to no avail but still learned alot.
so in my home folder I have .Xresources file:
! terminal colors ------------------------------------------------------------
! tangoesque scheme
*background: #111111
*foreground: #babdb6
! Black (not tango) + DarkGrey
*color0: #000000
*color8: #555753
! DarkRed + Red
*color1: #ff6565
*color9: #ff8d8d
! DarkGreen + Green
*color2: #93d44f
*color10: #c8e7a8
! DarkYellow + Yellow
*color3: #eab93d
*color11: #ffc123
! DarkBlue + Blue
*color4: #204a87
*color12: #3465a4
! DarkMagenta + Magenta
*color5: #ce5c00
*color13: #f57900
!DarkCyan + Cyan (both not tango)
*color6: #89b6e2
*color14: #46a4ff
! LightGrey + White
*color7: #cccccc
*color15: #ffffff
I also made a .xinitrc file in my home directory:
xrdb -merge ~/.Xresources
my problem is after boot I still have to manually use xrdb ~/.Xresources to have my .Xresources file to run.
I know there is a lot on Google about this but I read through a large amount trying to get it to work. Apparently there are various problems and they depended up how your Desktop Manager starts the X environment.
I am using LXDE (desktop manager) and openbox (windowd manager). At login I am greated with a login splash screen that takes me into my LXDE environment... I just can't figure out how to force startx to trigger the reading of my .Xresources file.
I made sure all files were not made as root and they have the proper permissions including being ecexcutable.
However my boot is configured,  the .Xresources is simply not getting run through xrdb as doing it manually after boot workds perfectly...
The arch wiki reads: "are using  a Display Manager t log into X. Most DM will autoload the ~/.Xresources file on login"
So is this more a lxde question?
Another blog I read said that LXDE may not read .Xresources automatically thus the need for the .xinitrc file.... I followed those instructions as well to no avail:
create .xinitrc
chmod +x .xinitrc
add xrdb -load ~/.Xresources &     
to the .xinitrc file
... did not work for my setup
at this point I am at a loss.
Any help would be greatly appreciated.
Last edited by soulrainX (2013-03-21 13:05:53)

Welcome!
Have you tried adding the command to Openbox' autostart.sh file? I don't know exactly how it's called, but it's usually placed in $XDG_CONFIG_HOME/openbox/ and if everything works correctly, it is executed upon starting Openbox.
EDIT
... and having read the comment below, yes, please use code tags. It confused me at first whether you were literally typing 'add' and 'create' as commands in your shell or not.
Last edited by ayekat (2013-03-21 11:56:01)

Similar Messages

  • [SOLVED] xterm not reading ~/.Xresources

    Apparently, .Xresources is the new file of choice for x-clients and .Xdefaults is deprecated, at least so I read on the internetz. I have tried the following in my .Xresources:
    xterm*background:Black
    xterm*foreground:Green
    but not luck. A quick "$ strace -eopen xterm" reveals that xterm doesn't even bother reading that file anymore, but rather prefers ~/.Xdefaults-arch ???
    I am thinking lol wut, What is up with that? Anyone know why xterm is behaving that way?
    Anyone got xterm to work with ~/.Xresources?
    Last edited by awayand (2011-06-13 18:23:10)

    As far as I know, you have to use xorg-xrdb. execute xrdb -merge ~/.Xresources, e. g. in your .xinitrc, depending on how you are starting your wm. It is also not mandatory to use .Xresources. In my xinitrc I'm using the following:
    xrdb -merge << "EOF"
    URxvt*font:xft:monospace:size=12
    URxvt*scrollBar:false
    EOF

  • FATAL: Could not read from the boot medium! system halted.

    hi
    im running win7 64 bit on my pc , installed virtualbox 4.1.16
    i have downloaded oracle vm server 3 ( v29653-01.iso ) , created new virtual machine and attached iso file but unable to boot from the iso
    i am getting FATAL: Could not read from the boot medium! system halted.
    under vm settings > storage > i have
    IDE: controller
    v29653-01.iso
    atrributes: cd/dvd IDE primary master
    live cd/dvd unchecked
    under general tab i have > Operating system: linux version: oracle (64 bit )
    Edited by: user9182826 on Aug 4, 2012 5:34 PM
    Edited by: user9182826 on Aug 4, 2012 6:12 PM

    Not sure if you are running into the same issue..
    OVM 3.0.3 - New VM loses filesystem after OS install
    For OEL5 VMs on 3.0.3 you have to add 'xen_emul_unplug=never' to your kernel boot line.

  • [SOLVED]Partitions not getting automounted at boot

    Hi,
    After I while I wasn't using my laptop I've made a full update (ofc I've checked for announcement for any manual intervention needed but there was nothing new). On reboot slim failed to autologin so I've switched to console to check the .Xinitrc file but, as soon as I logged in, the terminal output said it couldn't get to the user home directory because it's not there , and in fact the /home directory is actually empty. Since I didn't deleted anything of course I guess my home is probably not getting automounted or something...can this be the problem? how can I solve this ?
    Thanks in advance
    Last edited by Eit (2013-10-21 14:54:26)

    I've found in the boot log the message exactly reported in this thread.
    https://bbs.archlinux.org/viewtopic.php?id=170898
    And I've seen the guy fixed the error message warning about the root device not being rw, message which I've never sorted out becuase I wasn't getting any real problem out of that. I've read further in the topic and I've found the link to another topic related to the RW root partition problem
    https://bbs.archlinux.org/viewtopic.php?id=167153&p=4
    However, modifying the default grub config and regenerating that (as in post #95, even if post #96 says it shouldn't be necessary anymore) does not fix the problem of the root partition not being mounted as read write and neither the problem of partitions not getting automounted.
    I'm getting a bit confused.
    Edit: changing topic title to clarify
    Last edited by Eit (2013-10-17 21:12:01)

  • [SOLVED:] SLIM not reading slim.conf (no password auto-focus)

    Yesterday I began having issues with SLIM.  I'm not sure if they're related, but  while running Puppy , I inadvertently deleted the desktop icon for my Arch home directory on /dev/sda8.  I rebooted Puppy and it reappeared.  After running Puppy, something went wrong with my clocks (system and hardware) and the times were all wrong.  I fixed that with NTPD.  I currently dual boot Arch and Windows 7 from the hard drive, and occasionally from a USB stick, Puppy Linux.  I'm using an ASUS K50IJ laptop.  I run Xfce4.  I do not have any disk encryption enabled.
    When I boot up, the SLIM login appears as normal, but rather than password auto-focus, I'm prompted for a username.  If I enter the username and hit return, I'm still staring at the username prompt.  After three or four iterations of entering a username + enter, I finally get a password prompt and can log in.
    I have tried:
    1.  Reinstalling archlinux-themes-slim
    2.  Uninstalling archlinux-themes-slim and slim, then reinstalling slim
    3.  Removing old Xfce4 & Xfwm sessions
    4.  Removing slim.conf and entering a pristine version.
    5.  Reviewing /var/log/slim.log files for oddities.  I found one:
    Before the trouble started, I the message in the log was:
    slim: waiting for X server to begin accepting connections
    X.Org X Server 1.12.2
    Release Date: 2012-05-29
    X Protocol Version 11, Revision 0
    Build Operating System: Linux 3.0.32-1-lts x86_64
    Current Operating System: Linux asus 3.4.4-2-ARCH #1 SMP PREEMPT Sun Jun 24 18:5
    9:47 CEST 2012 x86_64
    Kernel command line: root=/dev/sda4 ro
    Build Date: 30 May 2012 07:24:13PM
    Current version of pixman: 0.26.2
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    (==) Log file: "/var/log/Xorg.0.log", Time: Sun Jul 8 15:30:48 2012
    (==) Using config directory: "/etc/X11/xorg.conf.d"
    /usr/bin/xauth: file /home/rasteenb/.Xauthority does not exist
    /usr/bin/startxfce4: X server already running on display :0.0
    Now I get:
    slim: waiting for X server to begin accepting connections.slim: unexpected signal 15
    slim: waiting for X server to begin accepting connections.
    slim: System is booting up.
    slim: pam_authentication(): Authentication failure
    slim: System is booting up.
    slim: pam_authentication(): Authentication failure
    slim: System is booting up.
    slim: pam_authentication(): Authentication failure
    slim: System is booting up.
    slim: pam_authentication(): Authentication failure
    slim: System is booting up.
    slim: pam_authentication(): Authentication failure
    Now I'm stumped.
    Rob
    Last edited by rasteenb (2012-07-17 11:16:03)

    I solved this - slim was not the last daemon I started in rc.conf.  By moving it to the end, I get password auto-focus and everything works.
    Now my rc.conf looks like
    # DAEMONS
    DAEMONS=(syslog-ng dbus acpid @network @wicd @openntpd @cupsd @crond slim)
    I found this recommendation in the Display Manager wiki page while researching the problem:
    Ensure you start the display manager last in the DAEMONS array, otherwise X will later allocate a tty device which was previously claimed by Getty (see /etc/inittab). Not placing the display manager at the end can cause X crashes, and is therefore unsupported.
    I'd just been lucky before that there wasn't a conflict.
    There is a "flicker" during login where I'm shown the XFCE splash, then the SLIM splash again, then the XFCE desktop.  Not sure what's going on there, but it's no big deal.
    Cheers,
    Rob

  • [Solved]Root filesystem read-only at boot

    Hi,
    I can't boot arch. Root filesystem is mounted ro, so nothing works properly. Last boot I make a pacman -Syu without incidences. A few weeks ago I make manual intervention  (filesystem upgrade - manual intervention required from latest news). I think that last new (Users of unofficial kernels must enable devtmpfs support) is not the problem  since I don't complile the kernel.
    dmesg show 2 mount operations to /dev/sda3 (my root partition, EXT4 fs).
    mtab have 2 entrys with /sda3. The last shown "ro" flag, and some strange parameters  for me .
    Maybe is a disk problem? How can I remove this flag, or remount in rw mode?
    umount -f don't work.
    I use a dual boot with GRUB, and second system is  W7.
    Thanks in advanced.
    Last edited by HermesT (2012-01-14 19:05:56)

    Some extra info:
    from dmesg
    [ 1.237581] sda: sda1 sda2 sda3 sda4 < sda5 >
    [ 1.829594] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
    [ 5.722599] EXT4-fs (sda3): re-mounted. Opts: user_xattr,acl,barrier=1,data=ordered.
    mtab
    rootfs / rootfs rw 0 0
    proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
    /sys /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
    udev /dev devtmpfs rw,nosuid,relatime,size=10240k,nr_inodes=215507,mode=755 0 0
    /run /run tmpfs rw,nosuid,nodev,relatime,size=10240k,mode=755 0 0
    /dev/sda3 / ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
    devpts /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 0 0
    shm /dev/shm tmpfs rw,nosuid,nodev,relatime 0 0
    /dev/sda1 /media/SYSTEM fuseblk rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 0 0
    /dev/sda2 /media/COMPAQ fuseblk rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 0 0
    /dev/sda5 /media/Almacen fuseblk rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 0 0
    * please, note that rootfs (?) is the same partition as /dev/sda3, like can be seen in df output.
    df
    S.ficheros 1K-bloques Usado Disponible Uso% Montado en
    rootfs 21096088 12132788 7891664 61% /
    udev 10240 0 10240 0% /dev
    /run 10240 252 9988 3% /run
    /dev/sda3 21096088 12132788 7891664 61% /
    shm 1550516 0 1550516 0% /dev/shm
    /dev/sda1 102396 25744 76652 26% /media/SYSTEM
    /dev/sda2 54772576 36097780 18674796 66% /media/COMPAQ
    /dev/sda5 548819964 142760132 406059832 27% /media/Almacen

  • [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)

  • I have a problem with the mac can not read video files with the extension IMOD. How can I solve this problem?

    I have a problem with the mac can not read video files with the extension IMOD. How can I solve this problem?

    By doing a Google search. 

  • I have an imac 2009 the disk drive is damaged and I have lost the passwords I need to reset passwords I tried booting with a macosx disk from an external hard drive but did not read the drive how else can I reset password ?

    I have an imac 2009 the disk drive is damaged and I have lost the passwords I need to reset passwords I tried booting with a macosx disk from an external hard drive but did not read the drive how else can I reset password ?
    I have a 2012 mac book pro can I use that to connect with firewire and load osx that way? and how woudl I do that?
    Thanks so much!

    To what password are you referring? Do you mean your user account's admin password? Or do you mean the master password for File Vault or do you mean a Firmware Password?
    For an admin password:
    Forgot Your Account Password
    For Snow Leopard and earlier
         Mac OS X 10.6- If you forget your administrator password
    For Lion/Mountain Lion
        Boot to the Recovery HD:
    Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
         When the menubar appears select Terminal from the Utilities menu.
         Enter resetpassword at the prompt and press RETURN. Follow
         instructions in the dialog window that will appear.
         Or see Reset a Mac OS X 10.7 Lion Password and
         OS X Lion- Apple ID can be used to reset your user account password.
    If you cannot do the above then try this:
      1. Boot to Safe Mode by restarting and after the chime press and hold down the COMMAND-S keys until a black screen with white type appears.
      2. At the prompt, type the following commands pressing return after each command line:
         /sbin/fsck -yf
         If you do not receive a "Filesystem OK" message then repeat this command until
         you do.  If after seven tries you still do not receive a "Filesystem OK" message,
         then the system is corrupted and needs to be reinstalled.
         mount -uw /
         cd /private/var/db/netinfo
         mv local.nidb local.old
         rm ../.AppleSetupDone
         shutdown -r now
    The second-to-last command above will cause OS X to think that the operating system is newly installed, and when the new owner starts up the computer it will send him/her to the startup wizard where he/she can start a new user without reinstalling.
    This last method does not actually change a password. It simply removes the user accounts and lets you create an initial admin account as if the computer were new out of the box.
    How to reset the OS X password without a startup CD:
    Reboot into Single-user Mode. Enter the following and press RETURN after each command line
       1. Type fsck -fy
       2. Type mount -uw /
       3. Type passwd <username>
    I have never tried this method myself.

  • Could not read boot block (input/output errror) powerbook g4

    Hello
    My friend gave me a powerbook g4 and a copy of osx lion, I would like to install it but the internal hardive is not available within the "select Destination" area of the  installation process. I tried to repair the disk which is labelled Disk0s1, but shortly after it is underway i recieve this message.
    **/dev/disk0s1 could not read boot block (input/output error) Error: The underlying task reported failure on exit. 1 non HFS volume checked, 1 volume could not be repaired because of an error.
    Within disk utilities the Disk01s is grey, I can try to repair it but the above error occurs. Do you know what the problem is and how I can fix it?

    Since you are going to install system fresh, it sounds like, you should erase the drive.  Boot from the installer disc, then select the language but do not start the installer.  From the menu bar, you should have either an Applications or an Installer menu. From one of the menus, you can then start Disk Utility.
    From the drives and volumes pane, select the internal drive hardware listing. 
    This will now allow you to partition or erase the disc.  Now click the Erase tab and select Mac OS Extended (Journaled) as the format and then click the "Erase" button.  You can name the volume that will actually be created, like for instance "MacintoshHD" or whatever you want.)
    Once the erase has completed, you need to check the information for the hard drive at the bottom of the window.  Be sure that the partition scheme is Apple Partition Map.  If for some reason it is something else, like GUID, you won't be able to install MacOS on it.  You will need to click the Partition tab, click the "Options..." button and select Apple Partition Map, then click the "Partition" button.
    Once this is done, then you can quit Disk Utility and you should be able to install Tiger on that HD.

  • My MacBook Pro does not read NTFS format, how can I solve this problem?

    I connected my external Hard drive to my Mac and it gives the error abou not reading the NTFS files... is there an app that can solve this problem?
    Thanks a lot

    You can take the drive to a PC, off load the files and right click and format the drive exFAT or FAT and place the files back on, then the Mac can read it.
    If you install NTFS reading software on your Mac, you will always be paying for it and it's updates, breaks your connections to the hard drive as well.
    Neutral formats are best, proprietary ones that require one to pay is bad.
    Drives, partitions, formatting w/Mac's + PC's

  • When i put my iphone in sleep mode it open itself and a messege appeares for a fraction of a second i could not read it i restarted it and downloaded the last update nothing solved

    Yesterday my iphone opened itself i hit the sleep button . After15 seconds it opened again ,a messege appeares for a fraction of a seconed i could not read it and i tried to shoot it but i couldn't .from yesterday this is the 3rd time that i recharge my iphone .

    Hey saandyy,
    Thanks for using Apple Support Communities.
    You can try to restart the iPhone to exit recovery mode.
    Turn your iOS device off and on (restart) and reset
    http://support.apple.com/kb/HT1430
    If you can't update or restore your iOS device
    http://support.apple.com/kb/ht1808
    Recovery mode erases your device and restores it, which should resolve the issue. If you previously synced with iTunes or iCloud, you may be able to restore from your backup after recovery.
    Have a nice day,
    Mario

  • X41 wireless not loading firmware at boot [Solved]

    Hi,
    I have a Lenovo X41T with an ipw2200 chipset for which I have installed ipw2200-fw from pacman. I have ipw2200 as my last module in the MODULES section in rc.conf. When I start my computer, my ipw2200 driver complains that the firmware is not being loaded. I checked the ipw2200 driver homepage and it listed two possible reasons for why it was giving the error: either the firmware was incompatible with the driver in the kernel or /sys was not being mounted at boot. So I added sys to my fstab and rebooted. I received the same error. However, if other people have no problems using the ipw2200 driver then it means that something else is wrong.
    I tried navigating into /sys/ and found a 'firmware' directory. The only thing in that directory is 'acpi'. Do other users of the ipw2200 driver have firmware installed in the /sys directory? Is there something else that is causing this problem?
    Any help would be greatly appreciated.
    EDIT: I should also mention that the driver works after I rmmod ipw2200; modprobe ipw2200. It would just be a lot more nifty if I didn't have to do that.
    EDIT 2: Here is my rc.conf as well as the errors I am seeing: http://pastebin.archlinux.org/13605
    EDIT 3: I think that my initrd is trying to load the ipw2200 module before the filesystem has been mounted.
    Last edited by kandrews (2007-09-02 01:17:02)

    I figured out that I needed to add the firmware hook to mkinitcpio.conf and regenerate the initrd with regenerate the initrd with
    mkinitcpio -p kernel26

  • Wired connection doesn't work if cable is not plugged in at boot time

    Hey all,
    I started using arch a few days ago and I simply love it, but I have a problem. The wired connection doesn't work if the cable is not plugged in at boot time, or if it was plugged in at boot time, then plugged out and in again. Switching it off and on again via the gui has the same effect. I am using NetworkManager with dhcpcd, NetworkManager is started via systemd, dhcpcd is not, I let NetworkManager do that. When I started investigating this problem there were some remnants of netctl, but now NetworkManager is the only networking-related service started at boot time. When the cable is plugged back in, NM-applet shows that it's connected, and an IP address is assigned, but the connection doesn't work.
    Here's some information regarding the system:
    It's a lenovo G50-70 laptop, it uses the r8169 driver for ethernet. (I dualboot it with windows 8.1, but arch is default and all this stuff happens also if i only use arch)
    The router is a Linksys EA2700/N600
    journalctl -u NetworkManager
    aug 26 19:14:33 arch_daboka NetworkManager[527]: <info> NetworkManager (version 0.9.10.1) is starting...
    aug 26 19:14:33 arch_daboka NetworkManager[527]: <info> Read config: /etc/NetworkManager/NetworkManager.conf
    aug 26 19:14:33 arch_daboka NetworkManager[527]: <info> WEXT support is enabled
    aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> Loaded plugin keyfile: (c) 2007 - 2013 Red Hat, Inc. To report bugs please use the NetworkMan
    aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> new connection /etc/NetworkManager/system-connections/Bokros
    aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> new connection /etc/NetworkManager/system-connections/1. vezetékes kapcsolat
    aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> new connection /etc/NetworkManager/system-connections/UPC1838142
    aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> monitoring kernel firmware directory '/usr/lib/firmware'.
    aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.3/0000:02:00.0/iee
    aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> rfkill1: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1f.0/PNP0C09:00/VPC20
    aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> WiFi hardware radio set enabled
    aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> WWAN hardware radio set enabled
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-wifi.so
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-wwan.so
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-adsl.so
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-bluetooth.so
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> WiFi enabled by radio killswitch; enabled by state file
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> WWAN enabled by radio killswitch; enabled by state file
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> WiMAX enabled by radio killswitch; enabled by state file
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> Networking is enabled by state file
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (lo): link connected
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (lo): carrier is ON
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (lo): new Generic device (driver: 'unknown' ifindex: 1)
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (lo): exported as /org/freedesktop/NetworkManager/Devices/0
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (enp1s0): carrier is OFF
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (enp1s0): new Ethernet device (driver: 'r8169' ifindex: 2)
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (enp1s0): exported as /org/freedesktop/NetworkManager/Devices/1
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
    aug 26 19:14:36 arch_daboka systemd[1]: Started Network Manager.
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (enp1s0): preparing device
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): using nl80211 for WiFi device control
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): driver supports Access Point (AP) mode
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): new 802.11 WiFi device (driver: 'ath9k' ifindex: 3)
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): exported as /org/freedesktop/NetworkManager/Devices/2
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): preparing device
    aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> use BlueZ version 5
    aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> wpa_supplicant started
    aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0) supports 4 scan SSIDs
    aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: starting -> ready
    aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20
    aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: ready -> disconnected
    aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0) supports 4 scan SSIDs
    aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: disconnected -> inactive
    aug 26 19:14:42 arch_daboka NetworkManager[527]: <info> startup complete
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Auto-activating connection 'Bokros'.
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) starting connection 'Bokros'
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) scheduled...
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) started...
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTING
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) scheduled...
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) complete.
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) starting...
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: prepare -> config (reason 'none') [40 50 0]
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0/wireless): connection 'Bokros' has security, and secrets exist. No new sec
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Config: added 'ssid' value 'Bokros'
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Config: added 'scan_ssid' value '1'
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Config: added 'psk' value '<omitted>'
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) complete.
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Config: set interface ap_scan to 1
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: inactive -> authenticating
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: authenticating -> associated
    aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: associated -> 4-way handshake
    aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: 4-way handshake -> completed
    aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireles
    aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 3 of 5 (IP Configure Start) scheduled.
    aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 3 of 5 (IP Configure Start) started...
    aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: config -> ip-config (reason 'none') [50 70 0]
    aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
    aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> dhcpcd started with pid 3599
    aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 3 of 5 (IP Configure Start) complete.
    aug 26 19:15:01 arch_daboka dhcpcd[3599]: version 6.4.3 starting
    aug 26 19:15:01 arch_daboka NetworkManager[527]: dhcpcd[3599]: version 6.4.3 starting
    aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> (wlp2s0): DHCPv4 state changed nbi -> preinit
    aug 26 19:15:01 arch_daboka dhcpcd[3599]: DUID 00:01:00:01:1b:7c:0d:d6:28:d2:44:7f:89:66
    aug 26 19:15:01 arch_daboka dhcpcd[3599]: wlp2s0: IAID 65:59:c9:b5
    aug 26 19:15:01 arch_daboka NetworkManager[527]: dhcpcd[3599]: DUID 00:01:00:01:1b:7c:0d:d6:28:d2:44:7f:89:66
    aug 26 19:15:01 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: IAID 65:59:c9:b5
    aug 26 19:15:01 arch_daboka dhcpcd[3599]: wlp2s0: soliciting an IPv6 router
    aug 26 19:15:01 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: soliciting an IPv6 router
    aug 26 19:15:02 arch_daboka dhcpcd[3599]: wlp2s0: rebinding lease of 192.168.1.137
    aug 26 19:15:02 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: rebinding lease of 192.168.1.137
    aug 26 19:15:07 arch_daboka dhcpcd[3599]: wlp2s0: leased 192.168.1.137 for 86400 seconds
    aug 26 19:15:07 arch_daboka dhcpcd[3599]: wlp2s0: adding route to 192.168.1.0/24
    aug 26 19:15:07 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: leased 192.168.1.137 for 86400 seconds
    aug 26 19:15:07 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: adding route to 192.168.1.0/24
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> (wlp2s0): DHCPv4 state changed preinit -> reboot
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> address 192.168.1.137
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> plen 24 (255.255.255.0)
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> gateway 192.168.1.1
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> server identifier 192.168.1.1
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> lease time 86400
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> hostname 'arch_daboka'
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> nameserver '192.168.1.1'
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> domain name 'chello.hu'
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 5 of 5 (IPv4 Commit) started...
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 5 of 5 (IPv4 Commit) complete.
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTED_LOCAL
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTED_GLOBAL
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Policy set 'Bokros' (wlp2s0) as default for IPv4 routing and DNS.
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Writing DNS information to /usr/bin/resolvconf
    aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) successful, device activated.
    aug 26 19:15:14 arch_daboka dhcpcd[3599]: wlp2s0: no IPv6 Routers available
    aug 26 19:15:14 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: no IPv6 Routers available
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): link connected
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 4
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Auto-activating connection '1. vezetékes kapcsolat'.
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) starting connection '1. vezetékes kapcsolat'
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 1 of 5 (Device Prepare) scheduled...
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 1 of 5 (Device Prepare) started...
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 2 of 5 (Device Configure) scheduled...
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 1 of 5 (Device Prepare) complete.
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 2 of 5 (Device Configure) starting...
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: prepare -> config (reason 'none') [40 50 0]
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 2 of 5 (Device Configure) successful.
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 3 of 5 (IP Configure Start) scheduled.
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 2 of 5 (Device Configure) complete.
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 3 of 5 (IP Configure Start) started...
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: config -> ip-config (reason 'none') [50 70 0]
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> dhcpcd started with pid 4322
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 3 of 5 (IP Configure Start) complete.
    aug 26 19:15:34 arch_daboka dhcpcd[4322]: version 6.4.3 starting
    aug 26 19:15:34 arch_daboka dhcpcd[4322]: DUID 00:01:00:01:1b:7c:0d:d6:28:d2:44:7f:89:66
    aug 26 19:15:34 arch_daboka dhcpcd[4322]: enp1s0: IAID 44:7f:89:66
    aug 26 19:15:34 arch_daboka NetworkManager[527]: dhcpcd[4322]: version 6.4.3 starting
    aug 26 19:15:34 arch_daboka NetworkManager[527]: dhcpcd[4322]: DUID 00:01:00:01:1b:7c:0d:d6:28:d2:44:7f:89:66
    aug 26 19:15:34 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: IAID 44:7f:89:66
    aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): DHCPv4 state changed nbi -> preinit
    aug 26 19:15:34 arch_daboka dhcpcd[4322]: enp1s0: soliciting an IPv6 router
    aug 26 19:15:34 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: soliciting an IPv6 router
    aug 26 19:15:34 arch_daboka dhcpcd[4322]: enp1s0: rebinding lease of 192.168.1.138
    aug 26 19:15:34 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: rebinding lease of 192.168.1.138
    aug 26 19:15:39 arch_daboka dhcpcd[4322]: enp1s0: leased 192.168.1.138 for 86400 seconds
    aug 26 19:15:39 arch_daboka dhcpcd[4322]: enp1s0: adding route to 192.168.1.0/24
    aug 26 19:15:39 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: leased 192.168.1.138 for 86400 seconds
    aug 26 19:15:39 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: adding route to 192.168.1.0/24
    aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): DHCPv4 state changed preinit -> reboot
    aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> address 192.168.1.138
    aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> plen 24 (255.255.255.0)
    aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> gateway 192.168.1.1
    aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> server identifier 192.168.1.1
    aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> lease time 86400
    aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> hostname 'arch_daboka'
    aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> nameserver '192.168.1.1'
    aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> domain name 'chello.hu'
    aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
    aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 5 of 5 (IPv4 Commit) started...
    aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
    aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 5 of 5 (IPv4 Commit) complete.
    aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
    aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
    aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTED_LOCAL
    aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTED_GLOBAL
    aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> Policy set '1. vezetékes kapcsolat' (enp1s0) as default for IPv4 routing and DNS.
    aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> Writing DNS information to /usr/bin/resolvconf
    aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) successful, device activated.
    aug 26 19:15:47 arch_daboka dhcpcd[4322]: enp1s0: no IPv6 Routers available
    aug 26 19:15:47 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: no IPv6 Routers available
    ping -c 10 192.168.1.1
    PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
    64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=4.38 ms
    64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=2.79 ms
    64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=4.89 ms
    64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=5.30 ms
    64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=1.59 ms
    64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=1.61 ms
    64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=4.37 ms
    64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=2.40 ms
    64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=6.47 ms
    --- 192.168.1.1 ping statistics ---
    10 packets transmitted, 9 received, 10% packet loss, time 9014ms
    rtt min/avg/max/mdev = 1.599/3.759/6.471/1.627 ms
    ping -c 100 8.8.8.8 - it's not completely disconnected, but it's always 8 packets at once that are received
    PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
    64 bytes from 8.8.8.8: icmp_seq=20 ttl=46 time=41.7 ms
    64 bytes from 8.8.8.8: icmp_seq=21 ttl=46 time=40.0 ms
    64 bytes from 8.8.8.8: icmp_seq=22 ttl=46 time=38.8 ms
    64 bytes from 8.8.8.8: icmp_seq=23 ttl=46 time=39.3 ms
    64 bytes from 8.8.8.8: icmp_seq=24 ttl=46 time=41.8 ms
    64 bytes from 8.8.8.8: icmp_seq=25 ttl=46 time=38.4 ms
    64 bytes from 8.8.8.8: icmp_seq=26 ttl=46 time=38.4 ms
    64 bytes from 8.8.8.8: icmp_seq=27 ttl=46 time=38.0 ms
    64 bytes from 8.8.8.8: icmp_seq=56 ttl=46 time=43.4 ms
    64 bytes from 8.8.8.8: icmp_seq=57 ttl=46 time=49.8 ms
    64 bytes from 8.8.8.8: icmp_seq=58 ttl=46 time=40.2 ms
    64 bytes from 8.8.8.8: icmp_seq=59 ttl=46 time=44.3 ms
    64 bytes from 8.8.8.8: icmp_seq=60 ttl=46 time=38.5 ms
    64 bytes from 8.8.8.8: icmp_seq=61 ttl=46 time=43.4 ms
    64 bytes from 8.8.8.8: icmp_seq=62 ttl=46 time=39.2 ms
    64 bytes from 8.8.8.8: icmp_seq=63 ttl=46 time=40.5 ms
    64 bytes from 8.8.8.8: icmp_seq=92 ttl=46 time=38.3 ms
    64 bytes from 8.8.8.8: icmp_seq=93 ttl=46 time=43.7 ms
    64 bytes from 8.8.8.8: icmp_seq=94 ttl=46 time=42.3 ms
    64 bytes from 8.8.8.8: icmp_seq=95 ttl=46 time=46.6 ms
    64 bytes from 8.8.8.8: icmp_seq=96 ttl=46 time=44.9 ms
    64 bytes from 8.8.8.8: icmp_seq=97 ttl=46 time=42.9 ms
    64 bytes from 8.8.8.8: icmp_seq=98 ttl=46 time=41.7 ms
    64 bytes from 8.8.8.8: icmp_seq=99 ttl=46 time=37.8 ms
    --- 8.8.8.8 ping statistics ---
    100 packets transmitted, 24 received, 76% packet loss, time 99062ms
    rtt min/avg/max/mdev = 37.886/41.455/49.829/3.000 ms
    cat /etc/dhcpcd.conf - I tried clientid instead of duid and disabling IPv6, but neither of those helped.
    # A sample configuration for dhcpcd.
    # See dhcpcd.conf(5) for details.
    # Inform the DHCP server of our hostname for DDNS.
    hostname
    # Use the hardware address of the interface for the Client ID.
    #clientid
    # or
    # Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
    duid
    # Persist interface configuration when dhcpcd exits.
    persistent
    # Rapid commit support.
    # Safe to enable by default because it requires the equivalent option set
    # on the server to actually work.
    option rapid_commit
    # A list of options to request from the DHCP server.
    option domain_name_servers, domain_name, domain_search, host_name
    option classless_static_routes
    # Most distributions have NTP support.
    option ntp_servers
    # Respect the network MTU.
    # Some interface drivers reset when changing the MTU so disabled by default.
    #option interface_mtu
    # A ServerID is required by RFC2131.
    require dhcp_server_identifier
    # Generate Stable Private IPv6 Addresses instead of hardware based ones
    slaac private
    # A hook script is provided to lookup the hostname if not set by the DHCP
    # server, but it should not be run by default.
    nohook lookup-hostname
    #noipv4ll
    #Disable IPv6
    #noipv6rs
    #noipv6
    cat /etc/NetworkManager/NetworkManager.conf
    [main]
    plugins=keyfile
    dhcp=dhcpcd
    ## Set static hostname
    #[keyfile]
    #hostname=foobar
    ## HTTP-based connectivity check
    #[connectivity]
    #uri=http://nmcheck.gnome.org/check_network_status.txt
    I couldn't find anything else to append, but if there are other log or conf files or anything else, which would help solving the problem, I should put here, please tell me.

    Try to use dhclient perhaps?  Might I also suggest letting systemd deal with the dhcp issue and not NM.  That may seem incongruous but it is possible NM is mis-handling the dhcp hand-off to the network card.  I'm no guru but I got thinking about this when I saw this in your output:
    aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
    aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
    aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTED_LOCAL
    It is very possible that I'm mis-interpreting this information so please take it with a boulder of salt. 

  • [SOLVED] Windows 8.1, lost Arch boot loader, cannot reinstall or boot

    Hi all,
    Apologies but I am only posting as I have exhausted my (admittedly quite limited) knowledge and have spent hours trying to get it back up and running but nothing seems to work at all. This will probably be quite long, apologies if there is something really obvious that I have missed on the Wiki or anywhere, but I'm only posting as I can't seem to get anywhere with it at all despite reading and trying.
    Essentially I had a Toshiba Satellite p850-321 laptop (UEFI, secure boot off, fast boot off) which I had dual booting with Windows 8 and Arch using rEFInd. I then had several moments of madness, starting when for some reason - on very little sleep so didn't think - decided to upgrade Windows 8 to 8.1. Unsurprisingly (but a surprise for me at the time), it then booted straight into Windows 8.1, no rEFInd. In hindsight, it had probably just set itself as boot priority but I thought it had overwritten rEFInd with its own bootloader or set it back to default or something so started on a way to try and get it back.
    I then spent many hours trying to get my old bootable Arch USB stick to work with no joy, updating it to the latest arch iso and all sorts. It eventually worked when I updated the laptop BIOS. Booted from the USB, chrooted into arch, reinstalled rEFInd, played around, eventually got it to reboot and display rEFInd but Arch wouldn't start. At this point I noticed that my fstab looked strange (devices/labels mixed up from what I expected), so followed the Beginner's Guide again and recreated the fstab. My disk is partitioned as follows (main partitions of note):
    /dev/sda2 - Windows EFI partition
    /dev/sda4 Windows 8.1
    /dev/sda6 arch swap partition (archswap)
    /dev/sda7 arch root partition (archroot)
    /dev/sda8 arch home partition (archhome)
    Couldn't get rEFInd to work so decided to start again with gummiboot. Installed gummiboot, followed Beginner's Guide to install and configure it. Edited arch.conf and after having to mess about with the location of vmlinuz-arch.efi in the conf file, I have the options part looking like this:
    options        root=/dev/sda7 rw 
    Now gummiboot loads on startup but all I get on trying to load Arch from gummiboot is the dreaded:
    ERROR: device '' not found. Skipping fsck
    ERROR: Unable to find root device ''.
    I've tried changing the root in options in arch.conf to UUID, PARTUUID and even different partitions (just to see what happened...) - the same. Is it likely to be due to me recreating the fstab and something is messed up there?
    Another problem is that now, whatever I do, I cannot boot from the USB again to get in to even try to fix anything. The laptop on boot just hangs for a while and then loads the gummiboot from the disk drive rather than from the USB (I've set the boot priority, everything) and nothing will allow me to boot from the USB. That is probably a secondary issue, I can probably try to reinstall the BIOS again and see if that helps.
    If anyone has had anything similar and has any solutions I'd be really grateful - anything. I don't mind being shown to be incredibly stupid, I get that a lot so have a lot of experience! - just anything that can get me back into Arch again without having to reinstall from scratch!
    Thanks.
    Last edited by pilf (2013-11-02 19:45:44)

    Thanks for replying, very much appreciated. The partitions were numbered sequentially, I only posted up the partitions that I thought were of interest to the issue (which wasn't very helpful!). The partitions are as follows:
    Partition No     Type             
    1                     Win Recover
    2                     EFI System (EFI partition)
    3                     Microsoft Reserved
    4                     Microsoft Basic (Windows 8.1 installation)
    5                     Windows Recover
    6                     Linux Swap
    7                     Microsoft Basic (Arch root partition)
    8                     Microsoft Basic (Arch home partition)
    9                     Windows Recover
    It looks like I have managed to solve it, but I admit I'm not sure what of the several changes I made that solved it. I managed to boot into the USB arch disk by resetting my BIOS back to defaults and then changing the boot order back, which was the only way it would boot the USB - without resetting back and putting the boot order back exactly how it was before it wouldn't boot from the USB. Anyway...
    Checked the partitions with gdisk, no problems. I did sort the partitions as you mentioned, just in case. Changed the partition names using gdisk to the same names I had before (archroot, archhome, archswap). Changed the types from Microsoft Basic to Linux filesystem (partitions 7 and 8) and wrote the partition.
    Mounted everything, chrooted, edited the gummiboot arch.conf file and noticed there were some strange characters in it, a forward slash before /root in the options for example. I had edited the arch.conf file from windows by booting into Windows, mounting the EFI partition (mountvol z: /s) and editing it that way, which would have messed up the formatting. It can't have only been that though as it wasn't booting anyway which is why I went into Windows to edit the file in the first place. Corrected the arch.conf file, rebooted and it booted. Some errors on boot which I need to correct but I can work on those as it boots into my arch installation.
    So all solved. I thought I'd update just to say thanks for the advice and in case it helps anyone else in the future.

Maybe you are looking for

  • Need to change color of a symbol with a custom slider

    I'm pretty new to Flash and am not sure if it is the right app to try to do the following: I need to create an interactive piece. It's much more involved than this but fundamentally I need to create a slider on the left side of a window that is the c

  • FS Matrox MXO2 Mini -- For Client Display

    Hello Folks, I'm selling a MXO2 Mini I have laying around on eBay. No minimum and no reserve, so it goes to the highest bidder. This box works GREAT with Adobe CS6, btw. And for anybody who might be interested, I'm also selling an Avid Mojo (original

  • Using Type Input in Conditional Statement

    If the user types "ball" in the input textfield, instance name: name_txt, I want to move to the next frame and stop. Can somebody tell me, what I am doing wrong here? Thank you! submit_btn.addEventListener(MouseEvent.CLICK, onClick); function onClick

  • DB check finished with warnings

    Hello All, In SAPCHECK latesh .chk file finished with warnings BR0280I BRCONNECT time stamp: 2009-03-26 10.30.46 BR0815I Number of indexes in schema of owner SAPAUTH: 2 BR0815I Number of indexes in schema of owner SAPR3: 49400 BR0815I Number of index

  • How can i reset Bridge CS6 to its default settings?

    Hello, i have a problem with Bridge CS6. Somehow its very slow and lags. when i tried to open a folder it takes sometimes several minutes before anything happens. is there a way to reset bridge to its default settings without reinstalling? Thanks