[SOLVED] syslinux bootloader and /boot...

tomorrow[31] i'm going to install and i need to clear 2 things:
which is the minimun size for a /boot partition and if is necesary?
wanna try syslinux bootloader...do u people reccomend?
thx in advance!
Last edited by 1archgamenon2 (2011-09-01 02:16:15)

:sad emo: seems no 64 bits 4 me!
CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz (2994.40-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0xf34 Family = f Model = 3 Stepping = 4
Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
Features2=0x441d<SSE3,DTES64,MON,DS_CPL,CNXT-ID,xTPR>
sysctl -a | grep -i hw
vfs.flushwithdeps: 0
net.wlan.hwmp.inact: 5000
net.wlan.hwmp.rannint: 1000
net.wlan.hwmp.rootint: 2000
net.wlan.hwmp.roottimeout: 5000
net.wlan.hwmp.pathlifetime: 5000
net.wlan.hwmp.replyforward: 1
net.wlan.hwmp.targetonly: 0
debug.hwpstate_verbose: 0
hw.machine: i386
hw.model: Intel(R) Pentium(R) 4 CPU 3.00GHz
hw.ncpu: 2
hw.byteorder: 1234
hw.physmem: 511033344
hw.usermem: 348024832
hw.pagesize: 4096
hw.floatingpoint: 1
hw.machine_arch: i386
hw.realmem: 528367616
hw.amr.force_sg32: 0
hw.an.an_cache_iponly: 1
hw.an.an_cache_mcastonly: 0
hw.an.an_cache_mode: dbm
hw.an.an_dump: off
hw.ata.setmax: 0
hw.ata.wc: 1
hw.ata.atapi_dma: 0
hw.ata.ata_dma_check_80pin: 1
hw.ata.ata_dma: 1
hw.ath.bstuck: 4
hw.ath.txbuf: 200
hw.ath.rxbuf: 40
hw.ath.resetcal: 1200
hw.ath.shortcal: 100
hw.ath.longcal: 30
hw.ath.hal.swba_backoff: 0
hw.ath.hal.sw_brt: 10
hw.ath.hal.dma_brt: 2
hw.bce.msi_enable: 1
hw.bce.tso_enable: 1
hw.bge.allow_asf: 0
hw.cardbus.cis_debug: 0
hw.cardbus.debug: 0
hw.cs.recv_delay: 570
hw.cs.ignore_checksum_failure: 0
hw.firewire.hold_count: 0
hw.firewire.try_bmr: 1
hw.firewire.fwmem.speed: 2
hw.firewire.fwmem.eui64_lo: 0
hw.firewire.fwmem.eui64_hi: 0
hw.firewire.phydma_enable: 1
hw.firewire.nocyclemaster: 0
hw.firewire.fwe.rx_queue_len: 128
hw.firewire.fwe.tx_speed: 2
hw.firewire.fwe.stream_ch: 1
hw.firewire.fwip.rx_queue_len: 128
hw.firewire.sbp.tags: 0
hw.firewire.sbp.use_doorbell: 0
hw.firewire.sbp.scan_delay: 500
hw.firewire.sbp.login_delay: 1000
hw.firewire.sbp.exclusive_login: 1
hw.firewire.sbp.max_speed: -1
hw.firewire.sbp.auto_login: 1
hw.mfi.max_cmds: 128
hw.mfi.event_class: 0
hw.mfi.event_locale: 65535
hw.pccard.cis_debug: 0
hw.pccard.debug: 0
hw.cbb.debug: 0
hw.cbb.start_32_io: 4096
hw.cbb.start_16_io: 256
hw.cbb.start_memory: 2281701376
hw.pcic.pd6722_vsense: 1
hw.pcic.intr_mask: 57016
hw.pci.usb_early_takeover: 1
hw.pci.honor_msi_blacklist: 1
hw.pci.enable_msix: 1
hw.pci.enable_msi: 1
hw.pci.do_power_resume: 1
hw.pci.do_power_nodriver: 0
hw.pci.enable_io_modes: 1
hw.pci.default_vgapci_unit: -1
hw.pci.host_mem_start: 2147483648
hw.pci.mcfg: 1
hw.pci.irq_override_mask: 57080
hw.syscons.kbd_debug: 1
hw.syscons.kbd_reboot: 1
hw.syscons.bell: 0
hw.syscons.saver.keybonly: 1
hw.syscons.sc_no_suspend_vtswitch: 0
hw.usb.ehci.lostintrbug: 0
hw.usb.ehci.iaadbug: 0
hw.usb.ehci.no_hs: 0
hw.usb.ehci.debug: 0
hw.usb.ohci.debug: 0
hw.usb.uhci.loop: 0
hw.usb.uhci.debug: 0
hw.usb.no_boot_wait: 0
hw.usb.ctrl.debug: 0
hw.usb.umass.debug: 0
hw.usb.urio.debug: 0
hw.usb.debug: 0
hw.usb.dev.debug: 0
hw.usb.usb_lang_mask: 255
hw.usb.usb_lang_id: 9
hw.usb.template: 0
hw.usb.ugen.debug: 0
hw.usb.power_timeout: 30
hw.usb.uhub.debug: 0
hw.usb.proc.debug: 0
hw.usb.pr_recovery_delay: 250
hw.usb.pr_poll_delay: 50
hw.usb.aue.debug: 0
hw.usb.axe.debug: 0
hw.usb.cdce.interval: 0
hw.usb.cdce.debug: 0
hw.usb.cue.debug: 0
hw.usb.kue.debug: 0
hw.usb.rue.debug: 0
hw.usb.udav.debug: 0
hw.usb.rum.debug: 0
hw.usb.uath.regdomain: 0
hw.usb.uath.countrycode: 0
hw.usb.ural.debug: 0
hw.usb.zyd.debug: 0
hw.usb.u3g.debug: 0
hw.usb.ubsa.debug: 0
hw.usb.uftdi.debug: 0
hw.usb.ulpt.debug: 0
hw.usb.uplcom.debug: 0
hw.usb.uslcom.debug: 0
hw.usb.uvisor.debug: 0
hw.usb.uvscom.debug: 0
hw.usb.ucom.cons_baud: 9600
hw.usb.ucom.cons_unit: -1
hw.usb.ucom.debug: 0
hw.usb.uhid.debug: 0
hw.usb.ukbd.no_leds: 0
hw.usb.ukbd.debug: 0
hw.usb.ums.debug: 0
hw.usb.uaudio.default_channels: 0
hw.usb.uaudio.default_bits: 32
hw.usb.uaudio.default_rate: 0
hw.usb.uaudio.debug: 0
hw.wi.debug: 0
hw.wi.txerate: 0
hw.xe.debug: 0
hw.intr_storm_threshold: 1000
hw.pagesizes: 4096 0
hw.availpages: 124764
hw.bus.devctl_queue: 1000
hw.bus.devctl_disable: 0
hw.psm.tap_timeout: 125000
hw.psm.tap_threshold: 25
hw.kbd.keymap_restrict_change: 0
hw.busdma.total_bpages: 64
hw.busdma.zone0.total_bpages: 64
hw.busdma.zone0.free_bpages: 64
hw.busdma.zone0.reserved_bpages: 0
hw.busdma.zone0.active_bpages: 0
hw.busdma.zone0.total_bounced: 0
hw.busdma.zone0.total_deferred: 0
hw.busdma.zone0.lowaddr: 0xffffffff
hw.busdma.zone0.alignment: 4096
hw.clockrate: 2994
hw.via_feature_xcrypt: 0
hw.via_feature_rng: 0
hw.instruction_sse: 1
hw.apic.enable_extint: 0
hw.mca.erratum383: 0
hw.mca.amd10h_L1TP: 1
hw.mca.enabled: 1
hw.mca.count: 0
hw.mca.interval: 3600
hw.mca.force_scan: 0
hw.bwn.wme: 1
hw.bwn.usedma: 1
hw.bwn.hwpctl: 0
hw.bwn.bluetooth: 1
hw.bwn.bfp: 0
hw.snd.feeder_rate_quality: 1
hw.snd.feeder_rate_round: 25
hw.snd.feeder_rate_max: 2016000
hw.snd.feeder_rate_min: 1
hw.snd.feeder_rate_polyphase_max: 183040
hw.snd.feeder_rate_presets: 100:8:0.85 100:36:0.92 100:164:0.97
hw.snd.feeder_eq_exact_rate: 0
hw.snd.feeder_eq_presets: PEQ:16000,0.2500,62,0.2500:-9,9,1.0:44100,48000,88200,96000,176400,192000
hw.snd.vpc_reset: 0
hw.snd.vpc_0db: 45
hw.snd.vpc_autoreset: 1
hw.snd.latency_profile: 1
hw.snd.latency: 5
hw.snd.report_soft_matrix: 1
hw.snd.report_soft_formats: 1
hw.snd.compat_linux_mmap: 0
hw.snd.vpc_mixer_bypass: 1
hw.snd.verbose: 0
hw.snd.maxautovchans: 16
hw.snd.default_unit: 0
hw.snd.version: 2009061500/i386
hw.snd.default_auto: 0
hw.midi.instroff: 0
hw.midi.dumpraw: 0
hw.midi.debug: 0
hw.midi.stat.verbose: 0
hw.midi.seq.debug: 0
hw.mmc.debug: 0
hw.sdhci.debug: 0
hw.acpi.supported_sleep_state: S1 S3 S4 S5
hw.acpi.power_button_state: S5
hw.acpi.sleep_button_state: S1
hw.acpi.lid_switch_state: NONE
hw.acpi.standby_state: S1
hw.acpi.suspend_state: S3
hw.acpi.sleep_delay: 1
hw.acpi.s4bios: 0
hw.acpi.verbose: 0
hw.acpi.disable_on_reboot: 0
hw.acpi.handle_reboot: 0
hw.acpi.reset_video: 0
hw.acpi.cpu.cx_lowest: C1
hw.drm.msi: 1
hw.dri.0.name: i915 0x6d pci:0000:00:02.0
hw.dri.0.vm:
hw.dri.0.clients:
hw.dri.0.vblank:
hw.dri.0.debug: 0
# uname -a
FreeBSD diablo 8.2-RELEASE FreeBSD 8.2-RELEASE #7: Wed Feb 16 12:19:08 PST 2011 [email protected]:/usr/obj/usr/local_storage/pcbsd-build82/fbsd-source/8.2/sys/PCBSD i386
Last edited by 1archgamenon2 (2011-08-31 15:10:34)

Similar Messages

  • (SOMEWHAT SOLVED) grub2 finds and boots windows 7 but NOT arch

    I installed arch on a new system. I have 64-bit Windows 7 Ultimate. I installed arch skipped bootloader, chrooted into system and installed grub2 and installed. My system is btrfs. I do not have a seperate swap or home partition. OS-prober is installed.  I have another system with btrfs and grub2 and all works fine. When I run grub-mkconfig -o /boot/grub/grub.cfg I get this
    Keyboard is not working properly on other computer so I cannot insert code brackets.
    Found linux image: /boot/vmlinuz-linux
    Found initrd image: /boot/initramfs-linux.img
        No volume groups found   (what does this mean)
    Found Windows 7 (loader) on /dev/sda1
    done
    Again boot and root partitions are btrfs. Grub2 is the bootloader and it does support btrfs at least the version in the repos a month ago did. I have feeling this might be the problem but I do not know why. Windows 7 boots successfully by the way. No Arch Linux
    Edit: Backed up boot partition. Made the partition ext4 and cp'd it all back and still no luck. I converted it because ran the grub-mkconfig again and I got everything above but also I got an unknown filesystem error.  Converting it back to btrfs...
    Edit 2: I am writing this from within windows but grub2 now shows Arch in the the menu. (no gui on this install yet) After what feels like 100 grub-installs and grub-mkconfigs it is all working. I still have two questions. For like half a second I see a file not found and I think it is a *.mod in /usr/lib/grub/i386-pc directory. (i have good eyes). What could this be? Secondly, what does no volume groups mean? Marking this somewhat solved.
    Last edited by quasifilmie (2012-03-30 23:59:43)

    I'd just ask checking the grub.cfg file to see if the device id entries for arch in the grub menu are correct.
    In my case, I use ubuntu's grub2 and each time I have to update grub for some reason, it wont get the partition right for the arch entry.
    Last edited by debdj (2012-03-31 15:28:20)

  • [SOLVED] My /home and /boot partition show on my desktop; not mounted

    I'm guessing these two fie systems aren't mounted  and the computer is seeing them as separate volumes?
    So I guess I made a mistake during the install. This kind of explains a few things because when updating my kernel GRUB wasn't being updated as if the /boot partition wasn't mounted. I had to completely reinstall GRUB to have it point to the right kernel.
    Is there a way to fix this and get these mounted how they need to be? Probably something with my fstab file?
    When I installed I mounted my root, created /mnt/boot and /mnt/home, then mounted those to their own partitions that I had created.
    I generated my fstab and checked it, and everything looked fine. I just don't know why everything else is just fine, but /boot and /home aren't mounted?
    My partition scheme is GPT and looks like
    /dev/sda1 -- bios boot
    /dev/sda2 -- /boot
    /dev/sda3 -- /
    /dev/sda4 -- /swap
    /dev/sda5 -- /home
    I used UUIDs if that makes any difference.
    Thanks.
    Last edited by stevenmw (2014-11-06 16:41:12)

    All right. I did what bstaletic said, and performed option 3 of his suggestions. My fstab file is restored but now when I start lightdm I get to my login screen, login, and have a black screen with just a cursor. All I did was run the install media, mount each partition (starting with root first). Then I turned my swap on.
    After that, I ran
    genfstab -U -p /mnt > fstab
    I checked the fstab file, it looked like this
    # /dev/sda3
    UUID=c2d39ee2-e1c4-4989-9937-91fad2951d67 / ext4 rw,relatime,data=ordered 0 1
    # /dev/sda2
    UUID=9cd92417-c4c0-40c7-9de3-3b65b896e36b /boot ext2 rw,relatime 0 2
    # /dev/sda5
    UUID=db8633d3f-0cb2-49dc-9792-356ad37ace58 /home ext4 rw,relatime,data=ordered 0 2
    # /dev/sda4
    UUID=00d4f1cd-cc6c-4dd3-B4c7-67da333205ea none swap defaults 0 0
    So I unmouted everything and turned swap off and went back into my system. The fstab file matched the output above. I started lightdm so i could get into xfce to see if the volumes were no longer on my desktop. However, now I get a black screen with a cursor. I let it sit for a while, but I ended up going into a tty and rebooting. Same issue. Black screen and cursor. I can see and login to lightdm just fine, but not my xfce DE.
    I did try reinstalling lightDM and xfce4 and xfce4-goodies. Not xorg though. I'll try reinstallign it and see what that does.
    Last edited by stevenmw (2014-10-15 20:01:51)

  • (SOLVED) Have Syslinux, will not boot with either Syslinux or GRUB2

    Greetings everyone,
    I decided to replace GRUB Legacy on my box this morning with Syslinux. Unlike the other box where I did this, it did not go smoothly this time.
    At computer startup, it will tell me that "Boot failed <Hard drive model>".
    In order to do some more testing, I booted using SystemRescueCd into my Arch and installed GRUB2. Startup will fail at the very same moment.
    This is what fdisk has to say about my partitioning:
    Disk /dev/sda: 500.1 GB, 500107862016 bytes
    255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0xa9d357fb
    Device Boot Start End Blocks Id System
    /dev/sda1 2048 821247 409600 27 Hidden NTFS WinRE
    /dev/sda2 821248 488245247 243712000 7 HPFS/NTFS/exFAT
    /dev/sda3 488245248 523401497 17578125 7 HPFS/NTFS/exFAT
    /dev/sda4 523403262 976771071 226683905 5 Extended
    /dev/sda5 * 523403264 603402239 39999488 83 Linux
    /dev/sda6 603404288 635402239 15998976 82 Linux swap / Solaris
    /dev/sda7 635404288 936771583 150683648 83 Linux
    /dev/sda8 936773632 976771071 19998720 b W95 FAT32
    Since GRUB Legacy worked fine, I installed both Syslinux and GRUB2 for BIOS booting by overwriting the MBR. My assumption is that the BIOS cannot handle the new MBR, and thus cannot start the bootloader, but I ran out of any steps I could take to fix this. And I could be wrong, of course.
    For completeness, this is my syslinux.cfg, even though it is pretty much the stock one, and I doubt that it is part of the cause:
    # Config file for Syslinux -
    # /boot/syslinux/syslinux.cfg
    # Comboot modules:
    # * menu.c32 - provides a text menu
    # * vesamenu.c32 - provides a graphical menu
    # * chain.c32 - chainload MBRs, partition boot sectors, Windows bootloaders
    # * hdt.c32 - hardware detection tool
    # * reboot.c32 - reboots the system
    # * poweroff.com - shutdown the system
    # To Use: Copy the respective files from /usr/lib/syslinux to /boot/syslinux.
    # If /usr and /boot are on the same file system, symlink the files instead
    # of copying them.
    # If you do not use a menu, a 'boot:' prompt will be shown and the system
    # will boot automatically after 5 seconds.
    # Please review the wiki: https://wiki.archlinux.org/index.php/Syslinux
    # The wiki provides further configuration examples
    DEFAULT arch
    PROMPT 0 # Set to 1 if you always want to display the boot: prompt
    TIMEOUT 50
    # You can create syslinux keymaps with the keytab-lilo tool
    #KBDMAP de.ktl
    # Menu Configuration
    # Either menu.c32 or vesamenu32.c32 must be copied to /boot/syslinux
    UI menu.c32
    #UI vesamenu.c32
    # Refer to http://syslinux.zytor.com/wiki/index.php/Doc/menu
    MENU TITLE Arch Linux
    #MENU BACKGROUND splash.png
    MENU COLOR border 30;44 #40ffffff #a0000000 std
    MENU COLOR title 1;36;44 #9033ccff #a0000000 std
    MENU COLOR sel 7;37;40 #e0ffffff #20ffffff all
    MENU COLOR unsel 37;44 #50ffffff #a0000000 std
    MENU COLOR help 37;40 #c0ffffff #a0000000 std
    MENU COLOR timeout_msg 37;40 #80ffffff #00000000 std
    MENU COLOR timeout 1;37;40 #c0ffffff #00000000 std
    MENU COLOR msg07 37;40 #90ffffff #a0000000 std
    MENU COLOR tabmsg 31;40 #30ffffff #00000000 std
    # boot sections follow
    # TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
    LABEL arch
    MENU LABEL Arch Linux
    LINUX ../vmlinuz-linux
    APPEND root=/dev/sda5 ro
    INITRD ../initramfs-linux.img
    LABEL archfallback
    MENU LABEL Arch Linux Fallback
    LINUX ../vmlinuz-linux
    APPEND root=/dev/sda5 ro
    INITRD ../initramfs-linux-fallback.img
    LABEL windows
    MENU LABEL Windows
    COM32 chain.c32
    APPEND hd0 1
    LABEL hdt
    MENU LABEL HDT (Hardware Detection Tool)
    COM32 hdt.c32
    LABEL reboot
    MENU LABEL Reboot
    COM32 reboot.c32
    LABEL off
    MENU LABEL Power Off
    COMBOOT poweroff.com
    Any ideas? Even ideas how to get more information from this box would be very helpful... "Boot failed" is not that constructive.
    Last edited by IllDefinedPillow (2012-08-14 06:06:08)

    I see, you corrected my syntax, thanks. But it still cannot boot.
    Now, this is how syslinux.cfg looks now:
    # Config file for Syslinux -
    # /boot/syslinux/syslinux.cfg
    # Comboot modules:
    # * menu.c32 - provides a text menu
    # * vesamenu.c32 - provides a graphical menu
    # * chain.c32 - chainload MBRs, partition boot sectors, Windows bootloaders
    # * hdt.c32 - hardware detection tool
    # * reboot.c32 - reboots the system
    # * poweroff.com - shutdown the system
    # To Use: Copy the respective files from /usr/lib/syslinux to /boot/syslinux.
    # If /usr and /boot are on the same file system, symlink the files instead
    # of copying them.
    # If you do not use a menu, a 'boot:' prompt will be shown and the system
    # will boot automatically after 5 seconds.
    # Please review the wiki: https://wiki.archlinux.org/index.php/Syslinux
    # The wiki provides further configuration examples
    DEFAULT arch
    PROMPT 0 # Set to 1 if you always want to display the boot: prompt
    TIMEOUT 50
    # You can create syslinux keymaps with the keytab-lilo tool
    #KBDMAP de.ktl
    # Menu Configuration
    # Either menu.c32 or vesamenu32.c32 must be copied to /boot/syslinux
    UI menu.c32
    #UI vesamenu.c32
    # Refer to http://syslinux.zytor.com/wiki/index.php/Doc/menu
    MENU TITLE Arch Linux
    #MENU BACKGROUND splash.png
    MENU COLOR border 30;44 #40ffffff #a0000000 std
    MENU COLOR title 1;36;44 #9033ccff #a0000000 std
    MENU COLOR sel 7;37;40 #e0ffffff #20ffffff all
    MENU COLOR unsel 37;44 #50ffffff #a0000000 std
    MENU COLOR help 37;40 #c0ffffff #a0000000 std
    MENU COLOR timeout_msg 37;40 #80ffffff #00000000 std
    MENU COLOR timeout 1;37;40 #c0ffffff #00000000 std
    MENU COLOR msg07 37;40 #90ffffff #a0000000 std
    MENU COLOR tabmsg 31;40 #30ffffff #00000000 std
    # boot sections follow
    # TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
    LABEL arch
    MENU LABEL Arch Linux
    LINUX ../vmlinuz-linux
    APPEND root=UUID=d292a449-b64b-40cd-b09b-e876e50e207f ro
    INITRD ../initramfs-linux.img
    LABEL archfallback
    MENU LABEL Arch Linux Fallback
    LINUX ../vmlinuz-linux
    APPEND root=UUID=d292a449-b64b-40cd-b09b-e876e50e207f ro
    INITRD ../initramfs-linux-fallback.img
    LABEL windows
    MENU LABEL Windows
    COM32 chain.c32
    APPEND label:winboot
    LABEL hdt
    MENU LABEL HDT (Hardware Detection Tool)
    COM32 hdt.c32
    LABEL reboot
    MENU LABEL Reboot
    COM32 reboot.c32
    LABEL off
    MENU LABEL Power Off
    COMBOOT poweroff.com
    # APPEND root=/dev/sda5 ro
    # APPEND hd0 1
    However, I still believe that it fails prior to reading this file. Syslinux does not output anything before the booting fails, which it should if syslinux.cfg would be accessible but erroneous, shouldn't it?

  • [SOLVED] Wiki page for GPT disks and booting arch using UEFI

    Hi guys, I am new to archlinux. I installed archlinux x86_64 just yesterday and I like its customisability. I also like arch wiki. Nowhere else have I seen such extensive documentation, especially about things like HAL, UDEV etc. with proper instructions. Thanks to all archers.
    I have installed Archlinux x86_64 in my Dell India Studio 1537 laptop along with Windows 7 Professional x64. Both the OSes boot in UEFI-GPT setup (my UEFI is tianocore.sourceforge.net EDK DUET UEFI64 firmware booting from USB). I boot Archlinux using my own compiled grub2-bzr compiled for both BIOS and UEFI-x64. I have a 1 MB BIOS Boot Partition as required by grub2 for BIOS-GPT booting. My Archlinux system can boot both from bios and from uefi, while Windows can boot only using UEFI.
    The official Archlinux installation guide talks about only MBR (or msdos disklabel) partitions and booting from BIOS based systems. With 2TB drives becoming common place and UEFI being implemented (search for Phoenix SecureCore Tiano's 1 second POST operation), I think a proper wiki page describing differences between MBR and GPT, why GPT is better, how to setup arch to boot from GPT. Another page describing steps to setup arch to boot from UEFI (either as a separate page or as an extension of GRUB2 wiki page) is also needed.
    Some details regarding Pure GPT (not a Hybrid GPT/MBR setup) and/or UEFI setups :-
    Partitioning tools -
    GNU Parted for filesystem related tasks
    GPT fdisk tool - http://rodsbooks.com/gdisk/ , http://sourceforge.net/projects/gptfdisk/ ,  pacman -S gdisk (in extra repo) - for non-filesystem related tasks
    util-linux-ng fdisk does not support GPT disks
    Bootloader - GRUB2 - vanilla grub-legacy does not support GPT and does not support UEFI (Fedora's patched grub-legacy does support both GPT and UEFI) and syslinux does not support GPT (I may be wrong here - seems a gptmbr of syslinux does help in booting from gpt but not sure).
    For GRUB2 - Need BIOS Boot Partition to embed GRUB2's core.img in GPT disks - size about 1 MB max - no filesystem
    In GPT fdisk partition type code - EF02
    In GNU Parted or GParted - bios_grub flag on
    For UEFI-GPT booting this special partition is not needed as no embedding takes place. This is needed only in case of BIOS-GPT booting.
    Incase of custom kernel configuration - enable CONFIG_EFI_PARTITION for GPT support
                                                                        CONFIG_EFI for UEFI support (for UEFI even above option required)
                                                                        CONFIG_EFI_VARS for UEFI Runtime Variables support (optional)
    Note: Although GPT is part of UEFI specification, a UEFI system is not needed to boot from/use GPT. BIOS based GPT booting is possible with GRUB2 or Fedora's patched grub-legacy (but not vanilla grub-legacy provided by archlinux). It is also possible to boot Linux in UEFI-MBR setup (again using grub2) but I have not tried it.
    Even without UEFI and less than 2TB harddrives, GPT based partitioning has many advantages - secondary GPT header and Partition table, CRC32 checksums. Unique Disk GUID and Filesystem-independent Unique Partition GUIDs, multiple primary partitions (default is 128 partitions, but it can be changed). The only problamatic OS is Windows which does not allow GPT booing unless one has UEFI based system. It allows only UEFI-GPT or BIOS-MBR setups. In linux it just depends on how the bootloader is configured - not a problem with grub2.
    I also propose that incase of Auto-prepare Hard Drive, the installer default to GPT for "archlinux only" installs ( ie no dual-boot or triple-boot etc.).
    I did not use the official archlinux iso but used archboot 2010.04 R3 as it gave an option of installing to GPT and also provided GRUB2 during bootloader install. I have never edited any wiki page before, thats why I request some one else to start a wiki page with the information given above.
    I don't know whether this is the right place, but any Windows (Vista or 7 x64 versions) and Linux dual-boot user who has UEFI-based system with GPT partitioning and wants to get rid of Hybrid MBR setup (to boot Windows) can follow this post http://www.insanelymac.com/forum/lofive … hp/t186440 (outside this forum) - this link describes the way to make Windows boot natively in UEFI-GPT setup. After doing this one can install arch using GRUB2 compiled for UEFI x86_64, and Windows will also see
    Last edited by skodabenz (2011-01-30 19:32:48)

    Welcome to arch, skodabenz! Offering documentation on third post - all thumbs up
    You could start the wiki page in your user-space with what you have, and then invite others to join working on it. Just register a wiki account, navigate to the page you want to start, for example:
    http://wiki.archlinux.org/index.php/User:skodabenz/GPT
    and click on "edit this page".
    As noted in the other thread, arch's legacy grub is patched for gpt support. I don't know about UEFI, but you can always open a bug report asking for the patches from fedora to be included.
    edit: the page from Rod Smith is a great resource. I was absolutely terrified at first by all this screwed up GPT/MBR stuff when I tried triple-booting Arch, Win and OS x, but he really does a great job explaining what it is all about.
    Last edited by hokasch (2010-05-21 15:44:08)

  • [SOLVED] How to dual boot windows on separate drive with syslinux

    I'm trying to follow the directions from the arch syslinux wiki to add a windows dual boot option to my current syslinux.
    I have two hard drives: sda (windows MBR) and sdc (arch linux GPT). My BIOS is set to boot sdc, and syslinux is currently installed fine to boot arch linux off of sdc. I would like to add an entry to boot windows.
    I added an entry to /boot/syslinux/syslinux.cfg that looks like
    LABEL windows
    MENU LABEL Windows
    COM32 chain.c32
    APPEND mbr:0xf00f1fd3 # my actual identifier for sda from fdisk is here
    When I rebooted, I saw the new entry in the syslinux menu. When I went to arch linux, it booted fine. When I rebooted again and selected windows, it hung with a blinking underscore. The next time I rebooted, it didn't even get to the syslinux menu and just hung with a blinking underscore.
    I booted from my rescue arch usb drive. In fdisk, sdc's partition table now mirrored sda's! In other words, it looked like I had windows partitions on my linux drive, and it had the same MBR identifier even though it was supposed to be GPT. I ran gdisk /dev/sdc, it detected both GPT and MBR, and I asked it to use the GPT table and wrote out the partitions, and my drive looked normal again. I ran arch-chroot, syslinux-install_update, and everything was fine the next time I booted.
    Any advice on how I can set up windows dual boot with syslinux?
    Last edited by mikemintz (2013-08-17 18:25:46)

    I am assuming that you use Bios and not UEFI (I am not that quite familiar with UEFI).
    1) You must configure the Bios to boot from the disk where syslinux is installed, having a correct mbr and with syslinux correctly installed.
    2) The disk where windows reside must be bootable by itself with a valid mbr.
    It may be possible that windows try to boot from the linux disk (and of course fails), try to add the swap option to the chain command.
    To check if Windows is correctly installed, try to boot it directly from the Bios.
    The mbr of the syslinux disk should be gptmbr.bin:
    dd if=/usr/lib/syslinux/gptmbr.bin of=/dev/sd<letter of the linux disk> bs=440 count=1
    Warning: Be very careful with what you do with dd, it is very easy to destroy all your data!
    Last edited by olive (2013-08-17 08:31:44)

  • [Solved]Syslinux "booting... boot error" when booting Windows 7

    Hello, I've set up my computer to dual boot windows and arch. Windows is on a separate hard drive and I was able to configure syslinux with a boot menu allowing me to select Windows at startup. For a long time this has worked without any problems whatsoever, but this morning I tried selecting windows and I got what is probably the most vague error message I have ever seen.
    "Booting...
    Boot Error"
    According to this post this problem comes in when the ldsyslinux.sys file cannot be found. Unfortunately I was not able to use his suggested fix
    syslinux -U /dev/sdb1
    I wasn't aware that there was a -U flag for syslinux and after checking it seems that there isn't one.
    Last edited by samstr (2014-11-26 04:48:55)

    Sorry, I actually just fixed it on my own, it turns out my BIOS settings were a bit... weird. For some reason I didn't have my windows drive listed and it tried to boot a USB drive I had plugged into my computer. I just had to fix the drive order and it worked fine. Sorry about starting a fairly useless discussion.

  • [SOLVED]Arch Linux, and Windows 8.1 Dual Boot issue

    Hi guys. I recently bought a new laptop, and decided to run Arch Linux and Windows 8.1. I installed Windows 8.1 first as recommended by the beginners guide, and then installed Arch Linux. I made sure UEFI was enabled in my BIOS, and made sure everything was on a GPT partition. The install itself went fine. My laptop loads grub, and Arch Linux shows up and boots, but there is no option to boot into Windows 8.1. The only way I can boot into Windows 8.1 is by accessing my motherboard, and choosing to launch the windows boot manager instead of the grub launcher. How can I get Windows 8.1 to show up in grub? Thanks in advance guys.
    Last edited by Painguy (2014-08-20 20:19:37)

    Painguy wrote:
    -----------Edit------------------
    Yeah just ran this after installing os prober
    grub-mkconfig -o /boot/grub/grub.cfg
    and it works now. Sorry for the crazy posts guys. Thanks for the suggestions and help.
    Yeah I'm sure I'm doing something wrong lol. I did not install OS-Prober. I think that's where the issue is. I'm missing the menu entry in grub.cfg right? Do I just run os prober or do I have to manually edit grub.cfg.
    If that's not the case then here is what I did up until now. What I did was start with a blank SSD drive. I used cgdisk to make the disk use a GPT partitioning scheme. I installed windows 8.1 and checked in windows to make sure it boots into UEFI-GPT mode and it does.  I then installed arch linux using the beginners guide. I made sure to use cgdisk to create any extra partitions, and installed GRUB to the efi partition that windows had created ( I did not format this partition ). I then finished the installation and rebooted, and Grub only shows arch linux. I don't think I'm dealing with anything MBR related. I made sure I used the GPT partitioning scheme....i think lol.
    All you need to do is run os-prober then run grub-mkconfig. It should pick up Windows at that point.

  • [SOLVED] xmodmap hangs and crashes after update

    UPDATE: See pabloc's post for a solution. keyboard plugin of gnome-settings-daemon was overriding Xmodmap bindings.
    After a pacman -Syu today, ~/.Xmodmap is no longer being loaded on login. Running `xmodmap ~/.Xmodmap` in a terminal window causes the entire DE (Cinnamon) to freeze, and it fixes itself after a minute or so (terminal window closes).
    Here is my ~/.xinitrc
    #!/bin/sh
    if [ -f $HOME/.Xmodmap ]; then
        /usr/bin/xmodmap $HOME/.Xmodmap
    fi
    exec gnome-session-cinnamon
    I haven't modified ~/.Xmodmap recently, and it was working fine prior to the update. The only modifications are swapping of the PgUp/PgDn keys with Home/End because ThinkPads have them in a weird spot.
    Here are my pacman.log entries from today:
    [2012-10-31 14:09] Running 'pacman -Sy'
    [2012-10-31 14:09] synchronizing package lists
    [2012-10-31 14:10] Running 'pacman -S -u'
    [2012-10-31 14:10] starting full system upgrade
    [2012-10-31 14:25] removed python-mechanize (0.2.5-2)
    [2012-10-31 14:25] removed python-imaging (1.1.7-4)
    [2012-10-31 14:25] removed libwebkit3 (1.8.3-1)
    [2012-10-31 14:25] removed libwebkit (1.8.3-1)
    [2012-10-31 14:25] upgraded glib2 (2.32.4-1 -> 2.34.1-1)
    [2012-10-31 14:25] upgraded at-spi2-core (2.4.2-1 -> 2.6.1-1)
    [2012-10-31 14:25] upgraded atk (2.4.0-1 -> 2.6.0-1)
    [2012-10-31 14:25] upgraded dconf (0.12.1-2 -> 0.14.0-1)
    [2012-10-31 14:25] upgraded at-spi2-atk (2.4.0-1 -> 2.6.1-1)
    [2012-10-31 14:25] upgraded linux-api-headers (3.5.5-1 -> 3.6.3-1)
    [2012-10-31 14:25] upgraded tzdata (2012f-1 -> 2012h-1)
    [2012-10-31 14:25] Generating locales...
    [2012-10-31 14:25]   en_CA.UTF-8... done
    [2012-10-31 14:25] Generation complete.
    [2012-10-31 14:25] upgraded glibc (2.16.0-4 -> 2.16.0-5)
    [2012-10-31 14:25] upgraded binutils (2.22-10 -> 2.23-1)
    [2012-10-31 14:25] upgraded bison (2.6.2-1 -> 2.6.4-1)
    [2012-10-31 14:25] upgraded libpng (1.5.12-1 -> 1.5.13-1)
    [2012-10-31 14:25] upgraded cairo (1.12.2-3 -> 1.12.6-2)
    [2012-10-31 14:25] upgraded python2-cssutils (0.9.9-2 -> 0.9.9-3)
    [2012-10-31 14:25] upgraded python2-cherrypy (3.2.2-1 -> 3.2.2-2)
    [2012-10-31 14:25] installed python2-mechanize (0.2.5-3)
    [2012-10-31 14:25] upgraded pam (1.1.5-4 -> 1.1.6-1)
    [2012-10-31 14:25] upgraded coreutils (8.19-1 -> 8.20-1)
    [2012-10-31 14:25] upgraded perl (5.16.1-1 -> 5.16.1-2)
    [2012-10-31 14:25] upgraded imagemagick (6.7.9.8-2 -> 6.8.0.3-1)
    [2012-10-31 14:25] upgraded gcc-libs (4.7.2-1 -> 4.7.2-2)
    [2012-10-31 14:25] upgraded poppler (0.20.3-1 -> 0.20.5-1)
    [2012-10-31 14:25] upgraded poppler-qt (0.20.3-1 -> 0.20.5-1)
    [2012-10-31 14:25] upgraded python2-lxml (2.3.5-1 -> 3.0.1-1)
    [2012-10-31 14:25] installed python2-imaging (1.1.7-5)
    [2012-10-31 14:25] upgraded sip (4.13.3-2 -> 4.14-2)
    [2012-10-31 14:25] upgraded python2-sip (4.13.3-2 -> 4.14-2)
    [2012-10-31 14:25] upgraded python-dbus-common (1.1.1-1 -> 1.1.1-2)
    [2012-10-31 14:25] upgraded python2-dbus (1.1.1-1 -> 1.1.1-2)
    [2012-10-31 14:25] upgraded pyqt-common (4.9.4-2 -> 4.9.5-3)
    [2012-10-31 14:25] upgraded python2-pyqt (4.9.4-2 -> 4.9.5-3)
    [2012-10-31 14:25] upgraded python2-psutil (0.6.1-1 -> 0.6.1-2)
    [2012-10-31 14:25] installed python2-cssselect (0.7.1-2)
    [2012-10-31 14:25] upgraded calibre (0.9.2-1 -> 0.9.4-2)
    [2012-10-31 14:25] Fontconfig warning: "/etc/fonts/conf.d/53-monospace-lcd-filter.conf", line 10: Having multiple values in <test> isn't supported and may not works as expected
    [2012-10-31 14:26] upgraded cantarell-fonts (0.0.10-1 -> 0.0.10.1-1)
    [2012-10-31 14:26] installed harfbuzz (0.9.5-1)
    [2012-10-31 14:26] upgraded pango (1.30.1-1 -> 1.32.1-1)
    [2012-10-31 14:26] upgraded kmod (10-1 -> 10-2)
    [2012-10-31 14:26] upgraded hwids (20120922-1 -> 20121022-1)
    [2012-10-31 14:26] upgraded util-linux (2.22-7 -> 2.22.1-2)
    [2012-10-31 14:26] ==> journald now writes to /var/log/journal by default. This can be
    [2012-10-31 14:26]     controlled with the Storage setting in /etc/systemd/journald.conf
    [2012-10-31 14:26] upgraded systemd (194-3 -> 195-2)
    [2012-10-31 14:26] upgraded polkit (0.105-1 -> 0.107-4)
    [2012-10-31 14:26] upgraded colord (0.1.21-2 -> 0.1.24-1)
    [2012-10-31 14:26] upgraded gtk3 (3.4.4-1 -> 3.6.1-1)
    [2012-10-31 14:26] installed gstreamer (1.0.2-1)
    [2012-10-31 14:26] installed gst-plugins-base-libs (1.0.2-1)
    [2012-10-31 14:26] installed chromaprint (0.7-1)
    [2012-10-31 14:26] installed mpg123 (1.14.4-1)
    [2012-10-31 14:26] installed celt (0.11.1-4)
    [2012-10-31 14:26] installed spandsp (0.0.6pre21-1)
    [2012-10-31 14:26] installed gst-plugins-bad (1.0.2-1)
    [2012-10-31 14:26] installed gst-plugins-base (1.0.2-1)
    [2012-10-31 14:26] upgraded gsettings-desktop-schemas (3.4.2-1 -> 3.6.0-1)
    [2012-10-31 14:26] upgraded libtasn1 (2.14-1 -> 3.0-1)
    [2012-10-31 14:26] upgraded gnutls (3.1.3-1 -> 3.1.3-2)
    [2012-10-31 14:26] upgraded glib-networking (2.32.3-1 -> 2.34.0-1)
    [2012-10-31 14:26] upgraded libsoup (2.38.1-1 -> 2.40.1-1)
    [2012-10-31 14:26] upgraded gdk-pixbuf2 (2.26.3-1 -> 2.26.4-1)
    [2012-10-31 14:26] installed gst-plugins-good (1.0.2-1)
    [2012-10-31 14:26] upgraded json-glib (0.14.2-1 -> 0.15.2-1)
    [2012-10-31 14:26] upgraded clutter (1.10.6-1 -> 1.12.2-1)
    [2012-10-31 14:26] upgraded clutter-gst (1.6.0-1 -> 1.9.92-1)
    [2012-10-31 14:26] upgraded clutter-gtk (1.2.0-1 -> 1.4.0-1)
    [2012-10-31 14:26] upgraded tdb (1.2.9-2 -> 1.2.10-1)
    [2012-10-31 14:26] upgraded libcanberra (0.28-5 -> 0.30-1)
    [2012-10-31 14:26] upgraded libgee (0.6.5-1 -> 0.6.6-1)
    [2012-10-31 14:26] upgraded gnome-video-effects (0.4.0-1 -> 0.4.0-2)
    [2012-10-31 14:26] upgraded libcroco (0.6.5-1 -> 0.6.8-1)
    [2012-10-31 14:26] upgraded librsvg (2.36.3-1 -> 2.36.4-1)
    [2012-10-31 14:26] upgraded gnome-desktop (1:3.4.2-1 -> 1:3.6.1-1)
    [2012-10-31 14:26] upgraded cheese (3.4.2-1 -> 3.6.1-1)
    [2012-10-31 14:26] upgraded libwbclient (3.6.8-1 -> 3.6.9-1)
    [2012-10-31 14:26] upgraded cifs-utils (5.6-2 -> 5.7-1)
    [2012-10-31 14:26] upgraded device-mapper (2.02.97-1 -> 2.02.98-1)
    [2012-10-31 14:26] upgraded cryptsetup (1.5.0-2 -> 1.5.1-1)
    [2012-10-31 14:26] upgraded cups-pk-helper (0.2.2-1 -> 0.2.4-1)
    [2012-10-31 14:26] upgraded python2-xdg (0.23-1 -> 0.23-2)
    [2012-10-31 14:26] upgraded libtorrent-rasterbar (1:0.16.3-1 -> 1:0.16.5-1)
    [2012-10-31 14:26] upgraded python2-crypto (2.6-2 -> 2.6-3)
    [2012-10-31 14:26] upgraded python2-zope-interface (3.8.0-1 -> 4.0.1-1)
    [2012-10-31 14:26] upgraded twisted (12.2.0-1 -> 12.2.0-2)
    [2012-10-31 14:26] upgraded python2-pyopenssl (0.13-1 -> 0.13-2)
    [2012-10-31 14:26] upgraded xdg-utils (1.1.0-2.20120520 -> 1.1.0.git20121008-1)
    [2012-10-31 14:26] upgraded python2-chardet (2.0.1-5 -> 2.0.1-6)
    [2012-10-31 14:26] upgraded python2-distribute (0.6.28-1 -> 0.6.29-1)
    [2012-10-31 14:26] upgraded deluge (1.3.5-1 -> 1.3.5-3)
    [2012-10-31 14:26] upgraded e2fsprogs (1.42.5-1 -> 1.42.6-1)
    [2012-10-31 14:26] upgraded libgnome-keyring (3.4.1-1 -> 3.6.0-1)
    [2012-10-31 14:26] upgraded libsoup-gnome (2.38.1-1 -> 2.40.1-1)
    [2012-10-31 14:26] installed webkitgtk3 (1.10.1-1)
    [2012-10-31 14:26] upgraded nspr (4.9.2-1 -> 4.9.3-1)
    [2012-10-31 14:26] upgraded nss (3.13.6-1 -> 3.14-1)
    [2012-10-31 14:26] upgraded gobject-introspection (1.32.1-2 -> 1.34.1.1-1)
    [2012-10-31 14:26] upgraded gcr (3.4.1-1 -> 3.6.1-1)
    [2012-10-31 14:26] upgraded epiphany (3.4.3-1 -> 3.6.1-1)
    [2012-10-31 14:26] upgraded ethtool (1:3.5-1 -> 1:3.6-1)
    [2012-10-31 14:26] upgraded poppler-glib (0.20.3-1 -> 0.20.5-1)
    [2012-10-31 14:27] upgraded gnome-icon-theme-symbolic (3.4.0-1 -> 3.6.0-1)
    [2012-10-31 14:27] upgraded gnome-icon-theme (3.4.0-1 -> 3.6.0-1)
    [2012-10-31 14:27] upgraded evince (3.4.0-1 -> 3.6.1-1)
    [2012-10-31 14:27] upgraded rest (0.7.12-1 -> 0.7.90-1)
    [2012-10-31 14:27] installed libsecret (0.10-1)
    [2012-10-31 14:27] upgraded gnome-online-accounts (3.4.2-1 -> 3.6.0-1)
    [2012-10-31 14:27] upgraded libgweather (3.4.1-1 -> 3.6.0-1)
    [2012-10-31 14:27] upgraded libgdata (0.12.0-1 -> 0.13.2-1)
    [2012-10-31 14:27] upgraded evolution-data-server (3.4.4-1 -> 3.6.1-1)
    [2012-10-31 14:27] upgraded libnice (0.1.2-1 -> 0.1.3-1)
    [2012-10-31 14:27] upgraded farstream (0.1.2-1 -> 0.2.1-1)
    [2012-10-31 14:27] upgraded file-roller (3.4.2-1 -> 3.6.1.1-1)
    [2012-10-31 14:27] installed nss-myhostname (0.3-3)
    [2012-10-31 14:27] warning: /etc/shadow installed as /etc/shadow.pacnew
    [2012-10-31 14:27] upgraded filesystem (2012.10-1 -> 2012.10-2)
    [2012-10-31 14:27] upgraded firefox (16.0.1-1 -> 16.0.2-1)
    [2012-10-31 14:27] upgraded telepathy-glib (0.18.2-1 -> 0.20.0-1)
    [2012-10-31 14:27] installed libzeitgeist (0.3.18-3)
    [2012-10-31 14:27] upgraded folks (0.6.9-2 -> 0.8.0-1)
    [2012-10-31 14:27] upgraded gcc (4.7.2-1 -> 4.7.2-2)
    [2012-10-31 14:27] upgraded gconf (3.2.5-2 -> 3.2.5-3)
    [2012-10-31 14:27] upgraded gegl (0.2.0-4 -> 0.2.0-5)
    [2012-10-31 14:27] upgraded git (1.7.12.3-1 -> 1.8.0-1)
    [2012-10-31 14:27] upgraded gjs (1.32.0-2 -> 1.34.0-1)
    [2012-10-31 14:27] upgraded glibmm (2.32.1-1 -> 2.34.0-1)
    [2012-10-31 14:27] upgraded gnome-backgrounds (3.4.2-1 -> 3.6.0-1)
    [2012-10-31 14:27] upgraded udisks2 (1.94.0-2 -> 2.0.0-1)
    [2012-10-31 14:27] upgraded gvfs (1.12.3-3 -> 1.14.0-1)
    [2012-10-31 14:27] upgraded obex-data-server (0.4.6-2 -> 0.4.6-3)
    [2012-10-31 14:27] upgraded gvfs-obexftp (1.12.3-3 -> 1.14.0-1)
    [2012-10-31 14:27] upgraded gnome-bluetooth (3.4.2-1 -> 3.6.0-2)
    [2012-10-31 14:27] upgraded gnome-common (3.4.0.1-2 -> 3.6.0-1)
    [2012-10-31 14:27] upgraded pygobject-devel (3.2.2-1 -> 3.4.1.1-1)
    [2012-10-31 14:27] upgraded python2-gobject (3.2.2-1 -> 3.4.1.1-1)
    [2012-10-31 14:27] upgraded gnome-menus (3.4.2-1 -> 3.6.0-1)
    [2012-10-31 14:27] upgraded libcanberra-pulse (0.28-5 -> 0.30-1)
    [2012-10-31 14:27] installed ibus (1.4.99.20121006-1)
    [2012-10-31 14:27] upgraded gnome-settings-daemon (3.4.2-1 -> 3.6.1-2)
    [2012-10-31 14:27] installed iptables (1.4.16.2-1)
    [2012-10-31 14:27] upgraded iproute2 (3.5.1-1 -> 3.6.0-2)
    [2012-10-31 14:27] upgraded wpa_supplicant (1.0-1 -> 1.0-2)
    [2012-10-31 14:27] upgraded ppp (2.4.5-4 -> 2.4.5-5)
    [2012-10-31 14:27] installed net-tools (1.60.20120804git-2)
    [2012-10-31 14:27] installed dhclient (4.2.4.1-3)
    [2012-10-31 14:27] upgraded networkmanager (0.9.6.0-2 -> 0.9.6.4-1)
    [2012-10-31 14:27] upgraded network-manager-applet (0.9.6.2-1 -> 0.9.6.4-1)
    [2012-10-31 14:27] installed libpwquality (1.2.0-1)
    [2012-10-31 14:27] warning: directory permissions differ on usr/share/polkit-1/rules.d/
    filesystem: 700  package: 755
    [2012-10-31 14:27] upgraded gnome-control-center (3.4.2-1 -> 3.6.2-1)
    [2012-10-31 14:27] upgraded gnome-keyring (3.4.1-3 -> 3.6.1-1)
    [2012-10-31 14:28] upgraded gnome-panel (3.4.2.1-1 -> 3.6.0-1)
    [2012-10-31 14:28] upgraded libxklavier (5.2.1-2 -> 5.3-1)
    [2012-10-31 14:28] upgraded libgnomekbd (3.4.0.2-1 -> 3.6.0-1)
    [2012-10-31 14:28] upgraded gnome-screensaver (3.4.4-1 -> 3.6.1-1)
    [2012-10-31 14:28] upgraded gnome-session (3.4.2-3 -> 3.6.1-1)
    [2012-10-31 14:28] upgraded zenity (3.4.0-1 -> 3.6.0-1)
    [2012-10-31 14:28] upgraded mutter (3.4.1-2 -> 3.6.1-2)
    [2012-10-31 14:28] upgraded libtracker-sparql (0.14.2-1 -> 0.14.3-1)
    [2012-10-31 14:28] upgraded nautilus (3.4.2-1 -> 3.6.2-1)
    [2012-10-31 14:28] upgraded telepathy-logger (0.4.0-1 -> 0.6.0-1)
    [2012-10-31 14:28] upgraded telepathy-mission-control (5.12.1-1 -> 5.14.0-1)
    [2012-10-31 14:28] upgraded gnome-shell (3.4.2-1 -> 3.6.1-2)
    [2012-10-31 14:28] upgraded gtkmm3 (3.4.1-1 -> 3.6.0-1)
    [2012-10-31 14:28] upgraded gnome-system-monitor (3.4.1-1 -> 3.6.0-1)
    [2012-10-31 14:28] upgraded vte-common (0.32.2-1 -> 0.34.1-1)
    [2012-10-31 14:28] upgraded vte3 (0.32.2-1 -> 0.34.1-1)
    [2012-10-31 14:28] upgraded gnome-terminal (3.4.1.1-1 -> 3.6.0-1)
    [2012-10-31 14:28] upgraded gnome-themes-standard (3.4.2-1 -> 3.6.1-1)
    [2012-10-31 14:28] upgraded yelp-xsl (3.4.2-1 -> 3.6.0-1)
    [2012-10-31 14:28] upgraded yelp (3.4.2-1 -> 3.6.1-1)
    [2012-10-31 14:28] upgraded gnome-user-docs (3.4.2-1 -> 3.6.0-1)
    [2012-10-31 14:28] upgraded gpm (1.20.6-10 -> 1.20.7-1)
    [2012-10-31 14:28] upgraded smbclient (3.6.8-1 -> 3.6.9-1)
    [2012-10-31 14:28] upgraded gvfs-smb (1.12.3-3 -> 1.14.0-1)
    [2012-10-31 14:28] upgraded ilmbase (1.0.2-1 -> 1.0.3-1)
    [2012-10-31 14:28] upgraded inkscape (0.48.3.1-5 -> 0.48.3.1-7)
    [2012-10-31 14:28] upgraded iputils (20101006-7 -> 20121011-1)
    [2012-10-31 14:28] upgraded jre7-openjdk-headless (7.u7_2.3.2-2 -> 7.u9_2.3.3-1)
    [2012-10-31 14:28] upgraded jre7-openjdk (7.u7_2.3.2-2 -> 7.u9_2.3.3-1)
    [2012-10-31 14:28] upgraded jdk7-openjdk (7.u7_2.3.2-2 -> 7.u9_2.3.3-1)
    [2012-10-31 14:28] upgraded openexr (1.7.1-1 -> 1.7.1-2)
    [2012-10-31 14:28] upgraded phonon (1:4.6.0-2 -> 1:4.6.0-3)
    [2012-10-31 14:28] upgraded kdelibs (4.9.2-2 -> 4.9.2-3)
    [2012-10-31 14:28] upgraded ldns (1.6.13-1 -> 1.6.14-1)
    [2012-10-31 14:28] upgraded lib32-atk (2.4.0-1 -> 2.6.0-1)
    [2012-10-31 14:28] upgraded lib32-glibc (2.16.0-4 -> 2.16.0-5)
    [2012-10-31 14:28] upgraded lib32-util-linux (2.22-1 -> 2.22.1-1)
    [2012-10-31 14:28] upgraded lib32-e2fsprogs (1.42.4-1 -> 1.42.6-1)
    [2012-10-31 14:28] upgraded lib32-gcc-libs (4.7.2-1 -> 4.7.2-2)
    [2012-10-31 14:28] upgraded lib32-libpng (1.5.12-1 -> 1.5.13-1)
    [2012-10-31 14:28] upgraded libpurple (2.10.6-1 -> 2.10.6-2)
    [2012-10-31 14:29] upgraded libreoffice-en-US (3.6.2-2 -> 3.6.2-3)
    [2012-10-31 14:29] upgraded libreoffice-common (3.6.2-2 -> 3.6.2-3)
    [2012-10-31 14:29] upgraded libreoffice-base (3.6.2-2 -> 3.6.2-3)
    [2012-10-31 14:29] upgraded libreoffice-calc (3.6.2-2 -> 3.6.2-3)
    [2012-10-31 14:29] upgraded libreoffice-draw (3.6.2-2 -> 3.6.2-3)
    [2012-10-31 14:29] upgraded libreoffice-gnome (3.6.2-2 -> 3.6.2-3)
    [2012-10-31 14:29] upgraded libreoffice-impress (3.6.2-2 -> 3.6.2-3)
    [2012-10-31 14:29] upgraded libreoffice-kde4 (3.6.2-2 -> 3.6.2-3)
    [2012-10-31 14:29] upgraded libreoffice-math (3.6.2-2 -> 3.6.2-3)
    [2012-10-31 14:29] upgraded postgresql-libs (9.2.1-1 -> 9.2.1-2)
    [2012-10-31 14:29] upgraded libreoffice-postgresql-connector (3.6.2-2 -> 3.6.2-3)
    [2012-10-31 14:29] upgraded libreoffice-sdk (3.6.2-2 -> 3.6.2-3)
    [2012-10-31 14:29] upgraded libreoffice-sdk-doc (3.6.2-2 -> 3.6.2-3)
    [2012-10-31 14:29] upgraded libreoffice-writer (3.6.2-2 -> 3.6.2-3)
    [2012-10-31 14:29] installed webkitgtk2 (1.10.1-1)
    [2012-10-31 14:29] upgraded mkinitcpio (0.10-1 -> 0.11.0-1)
    [2012-10-31 14:30] >>> Updating module dependencies. Please wait ...
    [2012-10-31 14:30] >>> Generating initial ramdisk, using mkinitcpio.  Please wait...
    [2012-10-31 14:30] ==> Building image from preset: 'default'
    [2012-10-31 14:30]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
    [2012-10-31 14:30] ==> Starting build: 3.6.4-1-ARCH
    [2012-10-31 14:30]   -> Running build hook: [base]
    [2012-10-31 14:30]   -> Running build hook: [udev]
    [2012-10-31 14:30]   -> Running build hook: [autodetect]
    [2012-10-31 14:30]   -> Running build hook: [pata]
    [2012-10-31 14:30]   -> Running build hook: [scsi]
    [2012-10-31 14:30]   -> Running build hook: [sata]
    [2012-10-31 14:30]   -> Running build hook: [filesystems]
    [2012-10-31 14:30]   -> Running build hook: [usbinput]
    [2012-10-31 14:30]   -> Running build hook: [fsck]
    [2012-10-31 14:30] ==> Generating module dependencies
    [2012-10-31 14:30] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
    [2012-10-31 14:30] ==> Image generation successful
    [2012-10-31 14:30] ==> Building image from preset: 'fallback'
    [2012-10-31 14:30]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
    [2012-10-31 14:30] ==> Starting build: 3.6.4-1-ARCH
    [2012-10-31 14:30]   -> Running build hook: [base]
    [2012-10-31 14:30]   -> Running build hook: [udev]
    [2012-10-31 14:30]   -> Running build hook: [pata]
    [2012-10-31 14:30]   -> Running build hook: [scsi]
    [2012-10-31 14:30]   -> Running build hook: [sata]
    [2012-10-31 14:30]   -> Running build hook: [filesystems]
    [2012-10-31 14:30]   -> Running build hook: [usbinput]
    [2012-10-31 14:30]   -> Running build hook: [fsck]
    [2012-10-31 14:30] ==> Generating module dependencies
    [2012-10-31 14:30] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
    [2012-10-31 14:30] ==> Image generation successful
    [2012-10-31 14:30] upgraded linux (3.5.6-1 -> 3.6.4-1)
    [2012-10-31 14:30] upgraded linux-headers (3.5.6-1 -> 3.6.4-1)
    [2012-10-31 14:30] upgraded lvm2 (2.02.97-1 -> 2.02.98-1)
    [2012-10-31 14:30] upgraded man-pages (3.42-1 -> 3.43-1)
    [2012-10-31 14:30] upgraded mdadm (3.2.5-2 -> 3.2.6-1)
    [2012-10-31 14:30] upgraded metacity (2.34.8-1 -> 2.34.13-1)
    [2012-10-31 14:30] upgraded net-snmp (5.7.1-4 -> 5.7.2-1)
    [2012-10-31 14:30] upgraded netcfg (2.8.11-1 -> 3.0-1)
    [2012-10-31 14:30] upgraded openssh (6.1p1-2 -> 6.1p1-3)
    [2012-10-31 14:30] upgraded pidgin (2.10.6-1 -> 2.10.6-2)
    [2012-10-31 14:30] upgraded pygobject2-devel (2.28.6-6 -> 2.28.6-8)
    [2012-10-31 14:30] upgraded python2-gobject2 (2.28.6-6 -> 2.28.6-8)
    [2012-10-31 14:30] upgraded slim (1.3.4-3 -> 1.3.4-4)
    [2012-10-31 14:30] upgraded slim-themes (1.2.3-5 -> 1.2.3-6)
    [2012-10-31 14:30] ==> syslog-ng now reads from /run/systemd/journal/syslog in the
    [2012-10-31 14:30]     default config. If you still use sysvinit/initscripts, this
    [2012-10-31 14:30]     must be /dev/log in /etc/syslog-ng/syslog-ng.conf
    [2012-10-31 14:30] upgraded syslog-ng (3.3.6-1 -> 3.3.6-3)
    [2012-10-31 14:31] >>> texlive: updating the filename database...
    [2012-10-31 14:31] mktexlsr: Updating /etc/texmf/ls-R...
    [2012-10-31 14:31] mktexlsr: Updating /usr/share/texmf/ls-R...
    [2012-10-31 14:31] mktexlsr: Updating /usr/share/texmf-dist/ls-R...
    [2012-10-31 14:31] mktexlsr: Updating /var/lib/texmf/ls-R...
    [2012-10-31 14:31] mktexlsr: Done.
    [2012-10-31 14:31] recreating all formats... done.
    [2012-10-31 14:31]  (logs are under /var/lib/texmf/web2c/<engine>/<formatname>.log)
    [2012-10-31 14:31] upgraded texlive-bin (2012.0-4 -> 2012.0-5)
    [2012-10-31 14:31] Updating font cache... Fontconfig warning: "/etc/fonts/conf.d/53-monospace-lcd-filter.conf", line 10: Having multiple values in <test> isn't supported and may not works as expected
    [2012-10-31 14:31] done.
    [2012-10-31 14:31] upgraded ttf-liberation (2.00.0-1 -> 2.00.1-1)
    [2012-10-31 14:32] In order to use the new version, reload all virtualbox modules manually.
    [2012-10-31 14:32] upgraded virtualbox-host-modules (4.2.0-5 -> 4.2.4-2)
    [2012-10-31 14:32]
    [2012-10-31 14:32] Creating symlink /var/lib/dkms/vboxhost/4.2.4/source ->
    [2012-10-31 14:32]                  /usr/src/vboxhost-4.2.4
    [2012-10-31 14:32]
    [2012-10-31 14:32] DKMS: add completed.
    [2012-10-31 14:32] ==> To build and install your modules run dkms install vboxhost/4.2.4
    [2012-10-31 14:32] ==> To do this automatically at startup you can add dkms in your DAEMONS
    [2012-10-31 14:32] upgraded virtualbox-host-source (4.2.0-3 -> 4.2.4-1)
    [2012-10-31 14:32] upgraded virtualbox (4.2.0-3 -> 4.2.4-1)
    [2012-10-31 14:32] upgraded vlc (2.0.3-4 -> 2.0.4-2)
    [2012-10-31 14:32] upgraded wget (1.14-1 -> 1.14-2)
    [2012-10-31 14:32] upgraded xf86-input-evdev (2.7.3-1 -> 2.7.3-2)
    [2012-10-31 14:32] upgraded xf86-input-synaptics (1.6.2-1 -> 1.6.2-2)
    [2012-10-31 14:32] upgraded xf86-video-intel (2.20.9-1 -> 2.20.12-1)
    [2012-10-31 14:32] upgraded xorg-server-common (1.12.4-1 -> 1.13.0-3)
    [2012-10-31 14:32] upgraded xorg-server (1.12.4-1 -> 1.13.0-3)
    [2012-10-31 14:32] upgraded xorg-xinit (1.3.2-1 -> 1.3.2-3)
    [2012-10-31 14:38] Running 'pacman -S baobab'
    [2012-10-31 14:38] installed baobab (3.6.2-1)
    [2012-10-31 17:08] Running 'pacman -S syslinux'
    [2012-10-31 17:10] Running 'pacman -S syslinux'
    [2012-10-31 17:11] ==> If you want to use syslinux as your bootloader
    [2012-10-31 17:11] ==> edit /boot/syslinux/syslinux.cfg and run
    [2012-10-31 17:11] ==>   # /usr/sbin/syslinux-install_update -i -a -m
    [2012-10-31 17:11] ==> to install it.
    [2012-10-31 17:11] installed syslinux (4.06-1)
    [2012-10-31 17:30] Running 'pacman -Syyu gnome-settings-daemon'
    [2012-10-31 17:30] synchronizing package lists
    [2012-10-31 17:30] starting full system upgrade
    [2012-10-31 17:30] upgraded gnome-settings-daemon (3.6.1-2 -> 3.6.1-2)
    [2012-10-31 17:30] Running 'pacman -Syu'
    [2012-10-31 17:30] synchronizing package lists
    [2012-10-31 17:30] starting full system upgrade
    [2012-10-31 17:39] Running 'pacman -Sy'
    [2012-10-31 17:39] synchronizing package lists
    [2012-10-31 17:39] starting full system upgrade
    [2012-10-31 17:39] Running 'pacman -U /tmp/yaourt-tmp-root/PKGDEST.yAV/downgrade-3.2-1-any.pkg.tar.xz'
    [2012-10-31 17:39] upgraded downgrade (3.1-1 -> 3.2-1)
    [2012-10-31 17:40] Running 'pacman -U /tmp/yaourt-tmp-root/PKGDEST.P2k/dropbox-1.4.20-1-x86_64.pkg.tar.xz'
    [2012-10-31 17:40] upgraded dropbox (1.4.17-1 -> 1.4.20-1)
    [2012-10-31 17:41] Running 'pacman -U /tmp/yaourt-tmp-root/PKGDEST.C5t/package-query-1.1-2-x86_64.pkg.tar.xz'
    [2012-10-31 17:41] upgraded package-query (1.0.1-1 -> 1.1-2)
    [2012-10-31 17:42] Running 'pacman -U /tmp/yaourt-tmp-root/PKGDEST.i8t/teamviewer-7.0.9377-1-x86_64.pkg.tar.xz'
    [2012-10-31 17:42] upgraded teamviewer (7.0.9360-1 -> 7.0.9377-1)
    [2012-10-31 17:42] Running 'pacman -U /tmp/yaourt-tmp-root/PKGDEST.21N/yaourt-1.2.1-1-any.pkg.tar.xz'
    [2012-10-31 17:42] upgraded yaourt (1.1-1 -> 1.2.1-1)
    [2012-10-31 17:44] Running 'pacman -U /tmp/yaourt-tmp-daniel/PKGDEST.nxI/cinnamon-git-20121031-1-x86_64.pkg.tar.xz'
    [2012-10-31 17:44] upgraded cinnamon-git (20121015-1 -> 20121031-1)
    Last edited by dtomasiewicz (2012-11-20 20:11:06)

    I've done a bit more playing around with this. It seems running xmodmap ~/.Xmodmap does work, it's just very slow and CPU-hungry. Reducing my .Xmodmap file to include only the overrides (4 of them) allows it to complete in about a second.
    However, it's still not being loaded on login, despite being in .xinitrc. In order to get my keybinds to work in a program, I need to open a terminal, run xmodmap manually, then execute whatever program I want them to work in.
    I tried downgrading xf86-input-evdev but my keyboard no longer worked on boot, once the display manager appeared (and I couldn't switch TTYs with Ctrl+Shift+F*).
    Last edited by dtomasiewicz (2012-11-02 16:43:21)

  • Syslinux won't boot from btrfs boot

    I have a USB drive, and I installed Arch on it. The problem is, that if I use one btrfs partition for / and /boot, at boot I can only see the copyrights line of syslinux. It won't even get to the system selection table.
    BUT if I make a backup of the root partition, change filesystem to ext4, and restore the files, the system boots fine.
    Why would it be happening?
    Last edited by Lockheed (2014-01-14 16:30:57)

    I have the same issue, same symptom, only the header line pops up and no menu or "boot>" prompt ever loads.
    In my setup, I have Arch on /dev/sda6, a legacy BIOS extended partition formatted as btrfs, and the / of my installation (including /boot) is in a dedicated btrfs subvolume. I attempt to chainload syslinux from the WinXP bootloader as I usually do. All works fine under ext4, but no go with btrfs. Looks like syslinux doesn't play well with btrfs at the moment, unless we are both missing something obvious...
    The syslinux changelog suggests that booting from a btrfs subvolume is possible (as of version 4.06). However the changelog for 6.02 has a red Bug Warning saying that using syslinux 6.02 on btrfs corrupts the superblock...
    Last edited by daviddem (2014-01-17 17:56:04)

  • Syslinux & GPT: no boot

    I have followed the instructions on the wiki to install syslinux manually and configure it as such, for use with GPT. I received no errors in my configuration, including the 'dd' step. I verified that the boot flag was set and that the syslinux.cfg file contained the correct partition for root. I installed the bootloader to /dev/sda.
    I also tried doing it the 'automatic' way (with compensation for GPT, I did install gptfdisk for both methods) with the bash script syslinux-install_update -iam. This also 'succeeded' but I still have no usable bootloader.
    Someone please help me out, I have tried both methods multiple times and I still can not boot to my hard drive.
    Laptop I'm installing on is a Lenovo IdeaPad Z575, uses BIOS but not EFI.
    TIA.
    - gdea73 -

    syslinux-install_update -iam
    will in fact fail at the second step (-a), which is setting the boot flag. Use
    syslinux-install_update -im
    instead and just set the Legacy BIOS Bootable bit yourself.
    Edit, as it's nothing important:
    DSpider wrote:msthev, it uses the gptfdisk package to set the boot flag. Edit "/usr/sbin/syslinux-install_update" and see for yourself.
    Yes, but it will fail if gptfdisk it's not installed, which isn't impossible, since you can set the attribute using gdisk. I had a similarly looking problem and the solution was to omit -a.
    Last edited by msthev (2012-10-26 16:23:41)

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

  • [SOLVED] Kernel panic at boot due to root FS not found

    When I try to boot using a new kernel version (eg. 3.0.1 or 2.6.39), I get a kernel panic with an "init not found" error message. I haven't been able to get any more detailed error messages, but I assume that there's a problem with finding or mounting my root filesystem.
    For now, I'm stuck with 2.6.38.7-1, which boots without any problems. (I keep trying the new kernel, then rolling it back using a Live CD.)
    I have a shared EXT4 root and boot partition, and I'm using Grub 0.97. Other than that, I'm not sure what information would be helpful in tracking down this problem, and any help would be appreciated.
    Last edited by dcecile (2011-08-10 00:41:46)

    No problem.
    Here's my full Grub. It has a lot of trial-and-error entries, and I made *-old copies of my 2.6.38 kernel files:
    # Config file for GRUB - The GNU GRand Unified Bootloader
    # /boot/grub/menu.lst
    # DEVICE NAME CONVERSIONS
    # Linux Grub
    # /dev/fd0 (fd0)
    # /dev/sda (hd0)
    # /dev/sdb2 (hd1,1)
    # /dev/sda3 (hd0,2)
    # FRAMEBUFFER RESOLUTION SETTINGS
    # +-------------------------------------------------+
    # | 640x480 800x600 1024x768 1280x1024
    # ----+--------------------------------------------
    # 256 | 0x301=769 0x303=771 0x305=773 0x307=775
    # 32K | 0x310=784 0x313=787 0x316=790 0x319=793
    # 64K | 0x311=785 0x314=788 0x317=791 0x31A=794
    # 16M | 0x312=786 0x315=789 0x318=792 0x31B=795
    # +-------------------------------------------------+
    # for more details and different resolutions see
    # http://wiki.archlinux.org/index.php/GRUB#Framebuffer_Resolution
    # general configuration:
    timeout 2
    default 0
    color light-blue/black light-cyan/blue
    # boot sections follow
    # each is implicitly numbered from 0 in the order of appearance below
    # TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
    title Arch Linux
    root (hd0,2)
    kernel /boot/vmlinuz-linux root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro panic=30 vga=0x318
    initrd /boot/initramfs-linux.img
    title Arch Linux Fallback
    root (hd0,2)
    kernel /boot/vmlinuz-linux root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro panic=30 vga=0x318
    initrd /boot/initramfs-linux-fallback.img
    title Arch Linux Ext4
    root (hd0,2)
    kernel /boot/vmlinuz-linux root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro panic=30 vga=0x318
    initrd /boot/initramfs-linux-ext4.img
    title Arch Linux Log
    root (hd0,2)
    kernel /boot/vmlinuz-linux root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro debug rootdelay=5 panic=30 ignore_loglevel vga=0x318
    initrd /boot/initramfs-linux.img
    title Arch Linux Break
    root (hd0,2)
    kernel /boot/vmlinuz-linux root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro rootwait break=y panic=30 vga=0x318
    initrd /boot/initramfs-linux.img
    title Arch Linux Nonboot Log
    root (hd0,2)
    kernel /vmlinuz-linux root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro debug rootdelay=5 panic=30 ignore_loglevel vga=0x318
    initrd /initramfs-linux.img
    title Arch Linux Baduuid Log
    root (hd0,2)
    kernel /boot/vmlinuz-linux root=/dev/disk/by-uuid/1ec8f74e-3268-45d0-ae20-9ee94d1c983b ro debug rootdelay=5 panic=30 ignore_loglevel vga=0x318
    initrd /boot/initramfs-linux.img
    title Arch Linux LTS
    root (hd0,2)
    kernel /boot/vmlinuz26-lts root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro panic=30 vga=0x318
    initrd /boot/kernel26-lts.img
    title Arch Linux LTS Fallback
    root (hd0,2)
    kernel /boot/vmlinuz26-lts root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro panic=30 vga=0x318
    initrd /boot/kernel26-lts-fallback.img
    title Arch Linux LTS Log
    root (hd0,2)
    kernel /boot/vmlinuz26-lts root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro debug rootdelay=5 panic=30 ignore_loglevel vga=0x318
    initrd /boot/kernel26-lts.img
    title Arch Linux Old
    root (hd0,2)
    kernel /boot/vmlinuz26-old root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro panic=30 vga=0x318
    initrd /boot/kernel26-old.img
    title Arch Linux Old Fallback
    root (hd0,2)
    kernel /boot/vmlinuz26-old root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro panic=30 vga=0x318
    initrd /boot/kernel26-old-fallback.img
    title Arch Linux Old Log
    root (hd0,2)
    kernel /boot/vmlinuz26-old root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro debug rootdelay=5 panic=30 ignore_loglevel vga=0x318
    initrd /boot/kernel26-old.img
    title Windows
    rootnoverify (hd0,0)
    makeactive
    chainloader +1
    This is the 3.0 entry that doesn't work:
    title Arch Linux
    root (hd0,2)
    kernel /boot/vmlinuz-linux root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro panic=30 vga=0x318
    initrd /boot/initramfs-linux.img
    And this is the 2.6.38 entry that does work:
    title Arch Linux Old
    root (hd0,2)
    kernel /boot/vmlinuz26-old root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro panic=30 vga=0x318
    initrd /boot/kernel26-old.img
    Here's "lsinitcpio /boot/initramfs-linux.img":
    ./etc
    ./etc/udev
    ./etc/udev/udev.conf
    ./etc/modprobe.d
    ./etc/modprobe.d/usb-load-ehci-first.conf
    ./init
    ./init_functions
    ./bin
    ./bin/busybox
    ./sys
    ./proc
    ./dev
    ./hooks
    ./hooks/udev
    ./run
    ./config
    ./usr
    ./usr/bin
    ./usr/sbin
    ./lib
    ./lib/udev
    ./lib/udev/usb_id
    ./lib/udev/firmware
    ./lib/udev/scsi_id
    ./lib/udev/path_id
    ./lib/udev/ata_id
    ./lib/udev/rules.d
    ./lib/udev/rules.d/50-udev-default.rules
    ./lib/udev/rules.d/80-drivers.rules
    ./lib/udev/rules.d/50-firmware.rules
    ./lib/udev/rules.d/60-persistent-storage.rules
    ./lib/modules
    ./lib/modules/3.0-ARCH
    ./lib/modules/3.0-ARCH/modules.alias.bin
    ./lib/modules/3.0-ARCH/modules.symbols.bin
    ./lib/modules/3.0-ARCH/kernel
    ./lib/modules/3.0-ARCH/kernel/fs
    ./lib/modules/3.0-ARCH/kernel/fs/ext4
    ./lib/modules/3.0-ARCH/kernel/fs/ext4/ext4.ko.gz
    ./lib/modules/3.0-ARCH/kernel/fs/mbcache.ko.gz
    ./lib/modules/3.0-ARCH/kernel/fs/jbd2
    ./lib/modules/3.0-ARCH/kernel/fs/jbd2/jbd2.ko.gz
    ./lib/modules/3.0-ARCH/kernel/sound
    ./lib/modules/3.0-ARCH/kernel/sound/core
    ./lib/modules/3.0-ARCH/kernel/sound/core/seq
    ./lib/modules/3.0-ARCH/kernel/sound/core/seq/snd-seq-device.ko.gz
    ./lib/modules/3.0-ARCH/kernel/sound/core/snd.ko.gz
    ./lib/modules/3.0-ARCH/kernel/sound/core/snd-rawmidi.ko.gz
    ./lib/modules/3.0-ARCH/kernel/sound/soundcore.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers
    ./lib/modules/3.0-ARCH/kernel/drivers/ata
    ./lib/modules/3.0-ARCH/kernel/drivers/ata/libata.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/ata/ahci.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/ata/libahci.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/usb
    ./lib/modules/3.0-ARCH/kernel/drivers/usb/core
    ./lib/modules/3.0-ARCH/kernel/drivers/usb/core/usbcore.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/usb/host
    ./lib/modules/3.0-ARCH/kernel/drivers/usb/host/uhci-hcd.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/usb/host/ehci-hcd.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/video
    ./lib/modules/3.0-ARCH/kernel/drivers/video/backlight
    ./lib/modules/3.0-ARCH/kernel/drivers/video/backlight/lcd.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/video/fb_sys_fops.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/video/sysimgblt.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/video/syscopyarea.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/video/sysfillrect.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/input
    ./lib/modules/3.0-ARCH/kernel/drivers/input/ff-memless.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/scsi
    ./lib/modules/3.0-ARCH/kernel/drivers/scsi/sd_mod.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/scsi/scsi_mod.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-ezkey.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-sjoy.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-gyration.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-samsung.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-roccat.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-lcpower.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-kye.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-dr.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-wacom.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-keytouch.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-uclogic.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-cherry.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-roccat-kovaplus.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-zpff.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-elecom.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-roccat-common.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-roccat-arvo.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-waltop.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-roccat-pyra.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-picolcd.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-twinhan.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-emsff.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-sunplus.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-apple.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-topseed.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-chicony.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-magicmouse.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-cypress.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-kensington.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-roccat-kone.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-axff.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-multitouch.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-logitech.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-petalynx.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-prodikeys.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/usbhid
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/usbhid/usbhid.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-sony.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-zydacron.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-roccat-koneplus.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-gaff.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-microsoft.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-monterey.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-ntrig.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-belkin.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-pl.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-a4tech.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-ortek.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-quanta.ko.gz
    ./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-tmff.ko.gz
    ./lib/modules/3.0-ARCH/kernel/lib
    ./lib/modules/3.0-ARCH/kernel/lib/crc16.ko.gz
    ./lib/modules/3.0-ARCH/modules.dep.bin
    ./sbin
    ./sbin/blkid
    ./sbin/udevadm
    ./sbin/modprobe
    ./sbin/udevd

  • Can a Mini use a hard disk from a Macbook and boot OK?

    My Macbook in the shop getting repaired for the RSD problem. I pulled the 120GB HD I had installed and put in the factory HD when I sent it out.
    I needed a computer so I bought a Mac Mini with only a 80GB HD. My question is; can I swap out the HD and let the mini use the OS X install from the Macbook and boot up properly or is it like windows and the version of the OS is slightly different due to the hardware?
    MacMini 1.83GHz & Macbook 2GHz   Mac OS X (10.4.7)  

    Hello,
    I've done this with the PowerPC Macs (PowerPC to PowerPC), and it's always worked fine.
    You should be fine doing this as well. Just don't install it in a PowerPC system since it's an Intel version of OS X.
    But, you'll be fine. Understand that you'll likely void the warranty on the Mac Mini, and that removing the drive will be a lot more work than it was in the MacBook.
    But, it will work fine.
    If you don't want to risk the warranty on the Mini, then you may want to just get an external FireWire or USB 2.0 portable hard drive enclosure to install the hard drive in (make sure it's Serial-ATA). And, then you can either boot from the external drive, or use that drive to clone it to your Mini's internal drive.
    I hope this helps.
    Let us know if you have other questions.
    P.S., if you'd like, go ahead and click the "Helpful" or "Solved" buttons on any of the posts / replies above if you feel they were helpful or adequately answered your question.

  • T43 still can't clone hard disk and boot

    I have a T43, 1871-WKL, with a 60G HD.  I purchased a 160G Samsung HM160HC as an upgrade.  I cannot get the system to clone and boot the new drive.
    I hook up the new Samsung drive with a Sabrent USB to IDE cable and the drive works fine.  I can use it for storage with no problem.  Doing a full format with verify works like a champ.
    First I tried Acronis TrueImage 10.0.  It tells me the target media has write errors about 4% into the clone.
    So I tried Clonezilla.  It works fine, either as the same size or expanding.  I and see the drive and copy stuff on and off the drive no problem.  
    However, when I insert the drive into the carrier for the internal drive and try to boot from it, it hangs with a blank screen and blinking cursor. 
    I was TOLD that it MAY be due to the fact I have no R&R on my drive.  So I download the R&R software and installed in on the original drive and cloned it.  Again, it won't boot.  I even tried booting the R&R rescue CD.  It will boot the CD with the ORIGINAL drive in the laptop, but the CD Boot hangs if I have the new drive in the laptop.  
    I tried it with the Acronis rescue disk as well, even though I didn't have an Acronis clone of the drive.
    I must have swapped out the drive over a dozen times, and I getting tired of wearing out the mounting screws.  Any ideas?
    Mike

    Mike, welcome to the forum,
    you need to firstly create an Acronis rescue disc and then reverse clone. Install the new drive as primary in your T43 and your original drive in the USB caddy / USB -> IDE cable and then simply clone the drive.
    Please see the following article in the forum Knowledgebase; Cloning Hard Drive Including The Predesktop Area With Acronis
    Andy  ______________________________________
    Please remember to come back and mark the post that you feel solved your question as the solution, it earns the member + points
    Did you find a post helpfull? You can thank the member by clicking on the star to the left awarding them Kudos Please add your type, model number and OS to your signature, it helps to help you. Forum Search Option T430 2347-G7U W8 x64, Yoga 10 HD+, Tablet 1838-2BG, T61p 6460-67G W7 x64, T43p 2668-G2G XP, T23 2647-9LG XP, plus a few more. FYI Unsolicited Personal Messages will be ignored.
      Deutsche Community     Comunidad en Español    English Community Русскоязычное Сообщество
    PepperonI blog 

Maybe you are looking for