[SOLVED] USB Installation Media Boot Problems

Hi all,
I'm having trouble creating a live USB stick that my new (to me) HP Elitebook
2730p laptop can boot successfully. Here is what I've tried so far:
1. dd with the latest stable Arch installation media
In other words:
# dd if=/path/to/archlinux*.iso of=/dev/sdb
Result: I can boot with the USB stick on my old Dell laptop (which is running
Arch) without issue, but can't with the new HP. The BIOS will freeze if the USB
stick is inserted, and will only unfreeze after I remove it.
2. dd with a recent Arch installation media snapshot
The snapshot is ``archlinux-2012.06.05_04-00-01-core-x86_64.iso''. I
install the image to the USB stick with the same dd method above,
and I get the same behavior: works fine on the old Dell, but freezes the BIOS of
the new HP.
3. dd with an old lubuntu iso
This time, I used an old lubuntu iso
(lubuntu-11.10-desktop-amd64.iso) with dd. This method
worked without a problem -- both my old Dell and my new HP would boot it without
complaint.
3. unetbootin with the latest stable Arch installation media
Creating the USB stick with unetbootin allows me to boot the stick with the new
HP, but the boot fails to the ramfs prompt after ``Waiting 30 seconds for device
/dev/disk/by-label/ ...'' (notice how there's nothing after ``by-label/'').
Adding ``vmalloc=448M'' to the end of the unetbootin boot entry makes no
difference.
4. Image Writer for Windows
The ``USB Installation Media'' wiki page suggests using ``Image Writer for
Windows'' to create a bootable USB stick. I tried this method using Windows 7
Professional, and the result was the same as attempts 1 and 2: the USB stick
freezes the HP's BIOS.
Other notes
I've checked the md5sums of all the isos I've tried
I've updated the BIOS on the HP laptop
I've used the same USB stick for each of the above situations
The new HP laptop does not have an optical drive, and I don't own an
external one
In attempts 1, 2, and 4, I noticed that cfdisk shows that the partition
that contains the installation files has both the ``Bootable'' and ``NC'' flags
set. The cfdisk man page says that the latter flag stands for ``Not Compatible
with DOS or OS/2''. I can actually remove this flag by using the ``Maximize''
option in cfdisk, which actually makes the USB stick bootable by the HP
computer's BIOS, but the boot eventually fails to the ``ramfs prompt
thingy'' after saying ``ERROR: '/dev/disk/by-label/ARCH_201108' found, but the
filesystem type is unknown''
In attempt 3 (the lubuntu one), I noticed that cfdisk shows a bit of free
space in front of the partition that contains the lubuntu files. The ``NC'' flag
is not present when I run cdisk.
My current theory is this: I believe my new HP's BIOS is unhappy with the
``isohybrid-nature'' of the Arch installation media. Is there any way I can
confirm this, or obtain ``non-isohybrid'' Arch media?
As you might imagine, this has been pretty frustrating. Any help would be
greatly appreciated!
Daniel
Last edited by bebeababa (2012-06-10 15:04:43)

bebeababa wrote:
DSpider wrote:
Adding ``vmalloc=448M'' to the end of the unetbootin boot entry makes no difference.
Duh. That's for booting it from RAM (with MEMDISK) in case it doesn't map the entire file, which for some reason it didn't for the i686 iso on my computer. I probably should've specified it when I wrote the article. I'll add it tomorrow morning.
Speaking of which, have you tried it?
https://wiki.archlinux.org/index.php/US … O_from_RAM
Because you only seem to be using dd ("Image Writer" is the same) and Unetbootin (which had various problems since forever). The correct syntax for dd is:
$ sudo dd if=archlinux.iso of=/dev/sd[x]
Warning: Make sure to use /dev/sdx and NOT /dev/sdx1. This is a very common error!
https://wiki.archlinux.org/index.php/US … _USB_drive
Haven't tried the ``Boot the entire ISO from RAM'' method yet. I'll give that a shot next.
The ``Boot the entire ISO from RAM'' method worked like a charm! Thanks,
DSpider!
Marking thread [SOLVED].

Similar Messages

  • Can't boot from windows 7 usb installation media

    When trying to boot from windows 7 usb installation media no efi boot option availiable. Using "boot from efi file" option whith each and every .efi file on installation media results in a message saying "The selected boot device failed. Press <Enter> to Continue". 
    USB installation media created using original windows 7 iso image and couple diskpart commands(resulting in clean flash storage with a single active primary partition) plus simple copying of the iso image's contents on usb flash. 
    Enabling/Disabling SecureBoot doesn't have any impact whatsoever. 
    Installation boots from aforementioned media successfully when CSM enabled, though i would really prefer installing Windows 7 in uefi mode. Which microsoft claims Windows 7 supports. 
    Any help or suggestions would be much appreciated. Thanks in advance. 
    PS: my disappointment in this particular HP notebook is unspeakable. Aside from issue of the current topic, It keeps defaulting to windows boot manager when dual-booting windows & linux no matter what i do, and windows 8.1 Pro is constantly BSODing whenever i try to run fullscreen games on high-performance GPU whith every graphics driver i could possibly install (including both hp's own and amd's). Found silly workarounds for both of these issues, however still hate HP treating it's customers that way.

    Booting from USB 2.0 port or DVD with SecureBoot disabled gets me to a screen saying "starting windows", just before the actual setup begins and then system simply hangs. Still unable to install. Thanks for your suggestion though.

  • Can't get USB installer to boot on Thinkpad S431

    Just got a refurbished laptop, and can't figure out how to get the USB installer to boot correctly.  I've tried EFI only, EFI+compatibility, CSM disabled/enabled etc.  I can select the USB drive and it gets to the Arch menu, then when I select the first option to start the installer it reads the USB for a few seconds then just sits at a black screen.  Specs: Thinkpad S431, Core i5-3337U, Intel 4000.  I've tried several Arch isos, including 7/14 and 5/14.  The USB drive will boot/install in my desktop machine with no problems. 
    Thanks for any help

    Since it is Intel graphics, it might have been an early KMS issue.  That is, there is no possible way to get early KMS going from the installer.  In this case, you would just need to use 'nomodeset' on the kernel command line.  If you were able to use the UEFI shell, then you were probably seeing the gummiboot boot manager.  So according to this page, you need to hit 'e' to edit the kernel command line.

  • Additional Instructions for Creating USB Installation Media

    Greeting Everyone,
    I have been trying to install archlinux on my Acer c720 chromebook.  The instructions have been posted on one of the forums and I have been following them and ran into a bit of a problem.  For some mysterious reason using Syslinux as the bootloader (I think I got that right) puts the C720 into reboot immediately.  The forums indicate that I should use GRUB instead of Syslinux.  Great! That is exactly what I want to do, and here is the problem:
    The instructions for creating the USB Flash Installation Media give step by step instructions for getting archlinux.iso and Syslinux on to the USB memory stick - which I followed and succeeded- but no instructions on how to put GRUB on there instead of Syslinux.
    Could someone give me instructions on how to do that.
    I am following the "Manual Formatting" --- "In Windows" section of the wiki titled "USB Flash Installation Media."
    Just so everyone knows this is my first venture into linux world and away from point and click windows world.....

    Steef435 wrote:
    Those instructions are about the installation(about what you choose to install on your harddisk). So they aren't important yet if you haven't managed to boot up the usb drive. What three images did you try? You should get the image from here:
    https://www.archlinux.org/download/
    Did you try booting the drive on other machines and how did that go? Did you go through all the instructions described in the wiki(enabling developer mode and enabling legacy boot) and did you get to the boot menu?
    Were you able to select the usb drive in the boot menu?
    On a side-note, I don't have a Chromebook so I'm not able to confirm the instructions on how to enable developer mode etc.
    Yes I used the following images from archlinux.org:
    archlinux-2013.10.01-dual.iso
    archlinux-2014.01.05-dual.iso
    and the third was from a random selection from the drop down menu in LiLi USB creator.
    Yes I have followed the instructions from the installation wiki and was able to get the developer mode and to the boot menu on the c720 and able to select USB to boot from.
    As I mentioned earlier I had success using the method for creating a USB Installation in the wiki (under  "Using manual formatting", "In Windows" https://wiki.archlinux.org/index.php/US … tion_Media ) I was able to get the archlinux splash screen and it tries to install but resets.  And I figured out that this happens because following the instructions I end up with archlinux and Syslinux on the USB and I need arclinux and GRUB.
    Hence my request for additional instructions for getting archlinux and GRUB onto a USB for installation.
    I will try the USB installation created using LiLi on a different computer - it is much older though and I am not sure it has enough memory for it.

  • How can I create a non-EFI USB installation media

    Hi fellows,
    I usually create a non-EFI installation CD  via this procedure
    https://wiki.archlinux.org/index.php/Un … ical_Media
    But now my optical drive is broken, so I need to create an USB non-EFI installation media.
    How can I do ???

    Hello nTia89,
    I'm in a similar situation to yours. I have an ancient MacBook Pro (1,1) with a broken optical drive, and any attempts to get EFI boot working with Linux have resulted in no graphics.
    My solution has been to first install Mac OS X via USB, then install Refind. After that, Refind will recognise Arch USB media during boot and you can install.
    I'm only booting Linux, so my solution has been to use MBR on the hard drive. That forces the machine to use the BIOS compatability mode.
    Don't hesitate to ask if you have any further questions!

  • [SOLVED] USB installation, booting: root fs cannot be detected

    I followed this guide: http://wiki.archlinux.org/index.php/Ins … _a_USB_key
    SYMPTOMS
    I installed arch linux on a USB stick.
    I can see Grub, I can boot. After the HOOKS get loaded (udev is loaded as well: Loading udev...done.) I get errors as follows:
    Attempting to create root device '/dev/disk/by-uuid/myHdUUID'
    unknown
    ERROR: root fs cannot be detected. Try using rootfstype= kernel parameter.
    If the device '/dev/disk/by-uuid/myHdUUID' gets created while you are here, try adding 'rootdelay=8' or higher to the kernel command-line...
    Then I get a prompt that doesn't even let me issue the command "ls" (error: /bin/bash: ls: not found
    SOLUTION: use the fallback image, or better, rebuild your mkinitcpio kernel image, see: Configuring mkinitcpio
    My problem was that "usb" was not included in the HOOKS, it was present, yes but after the "autodetect".
    So, in the /etc/mkinitcpio.conf place "usb" before "autodetect", e.g. as follows:
    HOOKS="base udev autodetect sata filesystems"
    then regenerate the image (refer to the previous link to understand why the autodetect was creating the problems and to see exactly how to regenerate the image)
    Last edited by firepol (2008-10-09 19:18:34)

    Same problem, seems the new kernel broke UUID.
    @tim: as I stated above it seems that you fixed the problem with the kernel image file but did not adjust the grub menu to compensate for the fact that UUID is broken and thats why you got the same result even after fixing the image, lucky for me I had some broken hooks and only my fallback image generated properly so I figured it out, although it took me a little while.
    Anyhow this is basically what needs to be done to correct the problem.
    1. Boot ArchLive
    2. mkdir /media/disk
    3. mount /dev/sdxX /media/disk
    4. chroot /media/disk
    5. mkinitcpio -k 2.6.28-ARCH -g /boot/kernel26.img
    6. nano /boot/grub/menu.lst
    7. Replace any references to UUID with /dev/sdxX (where xX represents your drive and partition) instead, save and exit nano.
    8. reboot
    Make sure and pay attention to the output of the mkinitcpio command in my step 5. If there are any errors relating to one or more of the hooks you'll need to edit /etc/mkinitcpio.conf and remove the hook it complains about !!IF POSSIBLE!!.  I for example had some problem with the autodetect hook which caused my regular kernel to fail to create an image.
    If mkinicpio doesn't complain and tells you it SUCCEEDED generating the images then you should be good to go.
    Last edited by blazercist (2009-01-29 18:47:25)

  • [SOLVED] Weird behaviour after formatting USB installation media

    Hi, I have noticed this weird behaviour with USB drives I used to install Arch linux with.  I format them using fdisk and mkntfs but after replugging them in, the udevil daemon mounts them again as ARCH_2013...[something] and even the directory tree exists!  This happens also when I use mkntfs without the -f flag (initializing with zeros).  I also checked the other files in /dev/sd* in order to make sure that my drive does not appear twice, but there is only sda (my HD) and sdd (or sometimes sdb, sdc,...) which must be the USB drive, also according to dmesg.
    Any ideas?
    EDIT: I wrote something about not seeing any files when manually mounting but that was my bad, I only tried mounting /dev/sdb1 but mounting /dev/sdb brought me the same files as devmon showed.
    Last edited by ysetdng (2014-07-12 22:36:46)

    I am assuming you used dd to write the image to the disk. You can use it to remove the contents of the disk as well.
    You should make use of the arch wiki, it is quite helpful.
    https://wiki.archlinux.org/index.php/US … tion_Media
    You can use this to zero out the entire device:
    # dd if=/dev/zero of=/dev/sdx bs=8M // x is the letter assigned to the usb drive. Be careful, The dd command is destructive.
    It may take a while to zero out the entire disk, depending on the size. After that use fdisk/cfdisk or gdisk/cgdisk to create the partition table and partition.
    To create the filesystem type, this one, ext4:
    # mkfs.ext4 /dev/sdx // or create a vfat
    then create the label:
    # e2label /dev/sdx1 USB_STICK_LABEL
    Use my suggestion as a last resort. Read the wiki, most of what I have said is in there anyway.
    Last edited by rgb-one (2014-07-12 18:21:18)

  • [SOLVED] CD Drive causing boot problems

    I'm trying to install Arch, but booting the install disk causes these errors to come up:
    Loading /arch/x86_64/vmlinuz.....
    Loading /arch/x86_64/archiso.img.............ready.
    Decompressing Linux... Parsing ELF... done.
    Booting the kernel.
    : : Starting udevd...
    done.
    : : Running Hook [udev]
    : : Triggering uevents...[ 19.934456] usb 5-1.6: device descriptor read/64, error -110
    [ 35.098044] usb 5-1.6: device descriptor read/64, error -110
    [ 36.869505] ata8.00: exception Emask 0x52 SAct 0x0 SErr 0xffffffff action 0xe frozen
    [ 36.869549] ata8: SError: { RecovData RecovComm UnrecovData Persist Proto HostInt PHYRdyChg PHYInt CommWake 10B8B Dispar BadCRC Handshk LinkSeq TrStaTrns UnrecFIS DevExch }
    [ 36.869598] ata8.0: failed command: IDENTIFY PACKET DEVICE
    [ 36.869639] ata8.0: cmd a1/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in
    [ 36.869640] res 40/00:00:00:00:00/00:00:00:00:00 Emask 0x56 (ATA bus error)
    [ 36.869721] ata 8.0: status: { DRDY }
    It just stops there and won't continue to boot. Disconnecting the SATA cable from my CD drive and using a flash drive to boot fixes these issues, but I didn't continue with the install because I wasn't sure if I would be unable to boot with the drive plugged in later. This is my CD drive. It's connected to a SATA 6GB/s port on my motherboard. The drive works perfectly in Windows.
    Also, if anyone knows anything about the USB error, help would be appreciated. That was the only error that did not go away after disconnecting my CD drive. I only have a keyboard, mouse, and WiFi dongle plugged in.
    Last edited by nigh (2012-05-29 09:28:01)

    Your issue with the SATA disc drive is a problem with Udev. Namely that some SATA disc drives do not support 16-byte pass-through commands coming from Udev. See this post for a longer explanation and the correct workaround:
    https://bbs.archlinux.org/viewtopic.php?pid=895404
    Other guides online will say to comment out parts of Udev's 60-persistent-storage.rules file, but I have found that to not only not work, but mess up detection of the SATA hard drives.
    So, after, or during, Arch installation using your USB stick:
    Add
    options libata atapi_passthru16=0
    to /etc/modprobe.d/modprobe.conf
    Add
    FILES="/etc/modprobe.d/modprobe.conf"
    to /etc/mkinitcpio.conf
    Rebuild kernel image with:
    mkinitcpio -p linux
    reboot
    To narrow down your USB issue, maybe you could try booting with only one plugged in at a time to identify which one has the issue. Do they all three work even though one gives this message?

  • Request BIOS to fix an USB flash drive boot problem in EFI (GE60 0ND-265FR)

    Hello,
    I'm currently trying to install Ubuntu on my MSI GE60 0ND notebook but I'm having troubles to boot on my USB flash drive in EFI mode.
    I've disabled Fast Boot and Secure Boot options but the only thing I can have is the GRUB menu of the liveUSB and whatever option I try I always get a blank screen. On the other hand everything works fine when I set the BIOS on Legacy mode.
    It's the same problem they have on this thread : https://forum-en.msi.com/index.php?topic=165756.0 but with an other notebook.
    The problem is  I want to keep Windows 8 side by side with Ubuntu so I must have them both installed in EFI mode.
    I asked for help on a specialized forum (french Ubuntu's community) and they believe this problem is related to the BIOS. Do you think an unlocked BIOS will help with that ?
    Here are my current BIOs and EC infos :
    BIOS Version : E16GAIMS.514
    BIOS Build : 03/12/2013
    EC Version : 16GAEMS1 Ver5.05
    EC Build : 02/21/2013
    Thanks for your help, and sorry if I've made English mistakes.

    i don't know if unlocked BIOS can help you with this

  • [SOLVED]Kernel 3.0 boot problems.

    I recently built the 3.0 kernel (downloaded from kernel.org) and am trying to make it bootable.
    After creating an image and editing grub, I get an error talking about how modules.dep was not found, that /dev/sda7 does not exist and can't be mounted to new_root, that I'm on my own and Good Luck, and then I get dropped to ram fs.
    I listed the contents of the kernel26.img and kernel30.img and there is quite a difference even though they were both built using the same mkinitcpio.conf. kernel26.img was built with -p kernel26. I haven't found a preset for kernel30.
    kernel26.img boots fine.
    I think the .imgs need to be similar but I don't know how to make them similar. Or I could be completley wrong and on the wrong track. Any ideas?
    kernel26.img listed:
    /proc
    /sys
    /dev
    /bin
    /sbin
    /lib
    /usr
    /usr/bin
    /usr/lib
    /usr/sbin
    /run
    /dev/null
    /dev/zero
    /dev/console
    /dev/mem
    /bin/busybox
    /lib/libc.so.6
    /lib/libc-2.13.so
    /lib/ld-linux-x86-64.so.2
    /lib/ld-2.13.so
    /sbin/modprobe
    /sbin/blkid
    /lib/libblkid.so.1
    /lib/libblkid.so.1.1.0
    /lib/libuuid.so.1
    /lib/libuuid.so.1.3.0
    /init_functions
    /init
    /config
    /etc
    /etc/modprobe.d
    /etc/modprobe.d/usb-load-ehci-first.conf
    /sbin/udevd
    /lib/librt.so.1
    /lib/librt-2.13.so
    /lib/libpthread.so.0
    /lib/libpthread-2.13.so
    /sbin/udevadm
    /lib/udev
    /lib/udev/rules.d
    /lib/udev/rules.d/50-firmware.rules
    /lib/udev/rules.d/50-udev-default.rules
    /lib/udev/rules.d/60-persistent-storage.rules
    /lib/udev/rules.d/80-drivers.rules
    /lib/udev/firmware
    /lib/udev/ata_id
    /lib/udev/path_id
    /lib/udev/scsi_id
    /lib/udev/usb_id
    /lib/udev/load-modules.sh
    /etc/udev
    /etc/udev/udev.conf
    /hooks
    /hooks/udev
    /sbin/v86d
    /etc/modprobe.d/uvesafb.conf
    /lib/modules
    /lib/modules/2.6.38-ARCH
    /lib/modules/2.6.38-ARCH/kernel
    /lib/modules/2.6.38-ARCH/kernel/drivers
    /lib/modules/2.6.38-ARCH/kernel/drivers/connector
    /lib/modules/2.6.38-ARCH/kernel/drivers/connector/cn.ko.gz
    /lib/modules/2.6.38-ARCH/kernel/drivers/video
    /lib/modules/2.6.38-ARCH/kernel/drivers/video/uvesafb.ko.gz
    /hooks/v86d
    /lib/modules/2.6.38-ARCH/kernel/drivers/scsi
    /lib/modules/2.6.38-ARCH/kernel/drivers/scsi/scsi_mod.ko.gz
    /lib/modules/2.6.38-ARCH/kernel/drivers/scsi/sd_mod.ko.gz
    /lib/modules/2.6.38-ARCH/kernel/drivers/cdrom
    /lib/modules/2.6.38-ARCH/kernel/drivers/cdrom/cdrom.ko.gz
    /lib/modules/2.6.38-ARCH/kernel/drivers/scsi/sr_mod.ko.gz
    /lib/modules/2.6.38-ARCH/kernel/drivers/ata
    /lib/modules/2.6.38-ARCH/kernel/drivers/ata/libata.ko.gz
    /lib/modules/2.6.38-ARCH/kernel/drivers/ata/libahci.ko.gz
    /lib/modules/2.6.38-ARCH/kernel/drivers/ata/ahci.ko.gz
    /lib/modules/2.6.38-ARCH/kernel/fs
    /lib/modules/2.6.38-ARCH/kernel/fs/mbcache.ko.gz
    /lib/modules/2.6.38-ARCH/kernel/fs/jbd2
    /lib/modules/2.6.38-ARCH/kernel/fs/jbd2/jbd2.ko.gz
    /lib/modules/2.6.38-ARCH/kernel/lib
    /lib/modules/2.6.38-ARCH/kernel/lib/crc16.ko.gz
    /lib/modules/2.6.38-ARCH/kernel/fs/ext4
    /lib/modules/2.6.38-ARCH/kernel/fs/ext4/ext4.ko.gz
    /lib/modules/2.6.38-ARCH/modules.dep
    /lib/modules/2.6.38-ARCH/modules.alias
    /lib/modules/2.6.38-ARCH/modules.symbols
    kernel30.img :
    /proc
    /sys
    /dev
    /bin
    /sbin
    /lib
    /usr
    /usr/bin
    /usr/lib
    /usr/sbin
    /run
    /dev/null
    /dev/zero
    /dev/console
    /dev/mem
    /bin/busybox
    /lib/libc.so.6
    /lib/libc-2.13.so
    /lib/ld-linux-x86-64.so.2
    /lib/ld-2.13.so
    /sbin/modprobe
    /sbin/blkid
    /lib/libblkid.so.1
    /lib/libblkid.so.1.1.0
    /lib/libuuid.so.1
    /lib/libuuid.so.1.3.0
    /init_functions
    /init
    /config
    /etc
    /etc/modprobe.d
    /etc/modprobe.d/usb-load-ehci-first.conf
    /sbin/udevd
    /lib/librt.so.1
    /lib/librt-2.13.so
    /lib/libpthread.so.0
    /lib/libpthread-2.13.so
    /sbin/udevadm
    /lib/udev
    /lib/udev/rules.d
    /lib/udev/rules.d/50-firmware.rules
    /lib/udev/rules.d/50-udev-default.rules
    /lib/udev/rules.d/60-persistent-storage.rules
    /lib/udev/rules.d/80-drivers.rules
    /lib/udev/firmware
    /lib/udev/ata_id
    /lib/udev/path_id
    /lib/udev/scsi_id
    /lib/udev/usb_id
    /lib/udev/load-modules.sh
    /etc/udev
    /etc/udev/udev.conf
    /hooks
    /hooks/udev
    mkinitcpio.conf:
    # vim:set ft=sh
    # MODULES
    # The following modules are loaded before any boot hooks are
    # run. Advanced users may wish to specify all system modules
    # in this array. For instance:
    # MODULES="piix ide_disk reiserfs"
    MODULES=""
    # BINARIES
    # This setting includes, into the CPIO image, and additional
    # binaries a given user may wish. This is run first, so may
    # be used to override the actual binaries used in a given hook.
    # (Existing files are NOT overwritten is already added)
    # BINARIES are dependancy parsed, so you may safely ignore libraries
    BINARIES=""
    # FILES
    # This setting is similar to BINARIES above, however, files are added
    # as-is and are not parsed in anyway. This is useful for config files.
    # Some users may wish to include modprobe.conf for custom module options,
    # like so:
    # FILES="/etc/modprobe.conf"
    FILES=""
    # HOOKS
    # This is the most important setting in this file. The HOOKS control the
    # modules and scripts added to the image, and what happens at boot time.
    # Order is important, and it is recommended that you do not change the
    # order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
    # help on a given hook.
    # 'base' is _required_ unless you know precisely what you are doing.
    # 'udev' is _required_ in order to automatically load modules
    # 'filesystems' is _required_ unless you specify your fs modules in MODULES
    # Examples:
    # This setup specifies all modules in the MODULES setting above.
    # No raid, lvm2, or encrypted root is needed.
    # HOOKS="base"
    # This setup will autodetect all modules for your system and should
    # work as a sane default
    # HOOKS="base udev autodetect pata scsi sata filesystems"
    # This is identical to the above, except the old ide subsystem is
    # used for IDE devices instead of the new pata subsystem.
    # HOOKS="base udev autodetect ide scsi sata filesystems"
    # This setup will generate a 'full' image which supports most systems.
    # No autodetection is done.
    # HOOKS="base udev pata scsi sata usb filesystems"
    # This setup assembles an pata raid array with an encrypted root FS.
    # Note: See 'mkinitcpio -H raid' for more information on raid devices.
    # HOOKS="base udev pata raid encrypt filesystems"
    # This setup loads an lvm2 volume group on a usb device.
    # HOOKS="base udev usb lvm2 filesystems"
    HOOKS="base udev v86d autodetect pata scsi sata filesystems"
    # COMPRESSION
    # Use this to compress the initramfs image. With kernels earlier than
    # 2.6.30, only gzip is supported, which is also the default. Newer kernels
    # support gzip, bzip2 and lzma. Kernels 2.6.38 and later support xz
    # compression.
    #COMPRESSION="gzip"
    #COMPRESSION="bzip2"
    #COMPRESSION="lzma"
    #COMPRESSION="xz"
    # COMPRESSION_OPTIONS
    # Additional options for the compressor
    #COMPRESSION_OPTIONS=""
    Last edited by bsilvereagle (2011-07-27 23:29:25)

    bsilvereagle wrote:
    karol wrote:
    bsilvereagle wrote:Oh, I have lts installed, I'd just like to have both kernel26 and 3.0.
    linux 3.0 is just the next version of the kernel26, and we don't have versioned kernel yet https://bugs.archlinux.org/task/16702
    It's just the same as you uninstall foo-1.2.3 and install e.g. foo-1.2.4 or bar-1.0.0 if package foo gets replaced by package bar.
    I know, I'd just like to be able to boot .38-ARCH and 3.0. I have problems w/ thermal and I'm trying to find the coolest kernel.
    You could rebuild the original .38 arch kernel but name it differently, look at e.g. the kernel26-lts package or the lots of custom AUR kernels for references.

  • [SOLVED] USB Installation Stuck

    I used
    dd bs=4M if=/path/to/archlinux.iso of=/dev/sdx && sync
    to create my USB, but it won't do anything. I boot from USB, the only output it gives me is: "ISOLINUX 6.02 EHDD Copyright (C) 1994-2013 H. Peter Anvin et al" with a flashing underscore on the 2nd line.
    I can't type any commands or get any response from the system whatsoever. I've tried formatting the drive as FAT32 and NTFS, with the same result either way.
    I used the 2014.03.01-dual.iso file from the site. USB written from a Lubuntu system.
    Any guidance would be truly appreciated.
    Thanks,
    Travis
    Lenovo W510
    4GB RAM
    Last edited by philomathean (2014-03-28 06:40:29)

    Please remember to mark your thread as [Solved] by editing your first post and prepending it to the title.

  • [SOLVED]Hanging after booting from installation media

    Yesterday I booted from a rw-DVD got to the terminal and could execute commands, connect to the internet and use elink etc no problem. I didn't go through with installation as I wanted to read up more on partitioning my drives for dual booting before actually doing so.
    Trying the same thing today, and it hangs soon after I boot, regardless of whether I do anything. Printing the following:
    nouveau E[ DRM] failed to idle channel 0xcccc0000 [DRM]
    pci_pm_runtime_suspend(): nouveau_pmops_runtime_suspend+0x0/0xf0 [nouveau] returns -16
    INFO: rcu_preempt detected stalls on CPUs/tasks: { 6} (detected by 1, t=18002 jiffiess, g=974, c=973, q=604)
    This is without me typing anything. If I try to execute a command quickly after booting it sometimes works, but after a couple of minutes it will complain of a soft lockup.
    I've tried burning another disk, and using a USB installation media, but the same thing happens. Any thoughts?
    Edit: Trying to run it on a laptop with i7-4700MQ, 16GB ram, and Intel(R) HD Graphics 4600 / NVIDIA GeForce GTX 770M
    Second Edit: Booted with nomodeset, which worked and allowed me to install. Just trying to sort out the sodding boot loaders now...
    Last edited by glfharris (2014-07-11 22:42:31)

    Welcome to the forum.
    First of all, you should get in the habit of using [ code ] tags when posting code, not [ quote ] tags (well, unless you want to apply some styling to it, like bold, italic, etc).
    This is wrong:
    # umount /dev/sdc
    This is correct:
    # umount /dev/sdc1
    You were trying to unmount the drive as a whole, which obviously isn't mounted, instead of the first (and probably only) partition. Had you followed the advice from the note to use blkid and check if it's mounted, this wouldn't have happened. But the fact that a DVD produced that error puzzles me... I have no experience with UEFI, but I think you need to press F10, F11, or something like that, to able able to get to a UEFI boot menu, and choose the optical unit as source.
    I hope you used a BitTorrent client when downloading the ISO, and not some direct link (which are prone to CRC errors). If you used a direct link, then check the MD5 and make sure that it matches the one from the Download page. For future reference, torrents are checked while they're being downloaded.

  • Windows 7 Installation Media Only Boots into Recovery

    Ever since I've updated to Windows 8, I have been really pleased. Everything works fine but when I was automatically updated to windows 8.1, I wasn't happy. I mostly use my PC for gaming and emulating my favourite classic game consoles. But windows 8.1 either
    doesn't allow games to play, and makes my emulators run at 15 FPS (normally they run at 55-60). And now, I cant install Graphics drivers! I used to be able to on windows 8. 8.1 will not let me run any of my old Windows 7 Apps either,
    So, after spending hours backing up my date, ready to start a fresh windows 7 installation, I figured out that I cannot upgrade, or even start the installation from the USB drive!
    I had lots of issues with Windows Vista and used the same installation media to fix the OS. Now, the installation ONLY boots into recovery mode!
    Luckily, I use Debian KDE on the side, So I am able to use my computer, but not play any games.
    Is there any way to have the installation media boot into Win7 Setup?

    Hi,
    Could you provide with a screen shoot?
    Please test the USB drive in another pc.
    If it is the same issue, it would be caused by the USB  drive.
    And then follow the steps to create a bootable USB drive.
    Create a Bootable USB Flash Drive
    http://technet.microsoft.com/en-us/library/jj200124.aspx
    Hope this helps,
    Ada Liu
    TechNet Community Support

  • Boot Installation media from USB flash/Pen Drive?

    Hi there,
    The hardrive on my X60 died. Died so badly that even Resue and Recovery wouldn't start yet alone Windows (even in safe mode).
    I have a new hard drive and installation media en route from Lenovo (laptop was under warranty)
    The problem is that the installation media is on CD/DVD and my laptop does not have an optical drive.
    So my questions are:
    1. Can the installation media be installed from a USB Pen/Flash drive? (the BIOS does support USB booting)
    2. Does anyone have experience of this or instructions?
    On a side note I find it slightly irritating that even under warranty Lenovo won't supply me software/hardware that will return my laptop to its original state without the user, me, potentially having to buy an external optical drive. The warranty support chap said "you'll just need to buy an external USB optical drive" - *sighs*
    Cheers
    Lawrence

    Tnx 4 ur reply RX-8.
    I bought the lappie used. It had BIOS ver. 103 when I bought it, so I upgraded to ver. 111 and it kept on booting from pen drives just fine.
    A few days after I bought it, the internal HDD failed with S.M.A.R.T. ID 5, something about reallocated sectors count. I got an exact replacement for the dead HDD. When I installed it, I unplugged the lappie's battery, then plugged the battery back in before I buttoned it all up. I think THAT was the start of my USB flash pen drive boot problem.
    The new HDD is fine. It passes the HGST Drive Fitness Test with long SMART test, which takes between 2 and 3 hours.
    I tried the EC update. Inside the zip file was a TXT file with a link to an MSI page that has a PDF file on how to do the EC update. I had that PDF open on another machine when I did the EC update so I could follow the instructions exactly.
    After an F9 on the UEFI screen to restore defaults and an F10 to save the UEFI config, I rebooted and everything seemed OK. I then used a pin to force a reset. For the second time, I unplugged the lappie and waited a few minutes for the EC memory to clear.
    I still have the same problem. I can't boot from a USB flash pen drive.
    I'm enclosing shots of my USB config with XHCI enabled and disabled. I tried to boot from a pen drive with both XHCI settings. No joy. Will I ever be able to boot from a USB flash pen drive again?
    I should also mention that I have a portable HDD with a USB 3 interface that boots just fine on other machines but won't boot on the GS60 Ghost. The LED on the portable HDD comes on and the lappie screen just sits there with a blinking underscore cursor.

  • Maverick Boot Camp - Partition and USB installation of Windows 7

    Hi my CD-ROM drive is broken and i want to configure a partition for windows 7 and install it from a UB, but i don’t have the bootcamp option for usb installation visible.
    My OSX version is Maverick 10.9
    Mac model iMac11,2
    Boot rom : IM112.0057.B01
    My info.plist configuration file in the bootcamp package is:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">
    <dict>
              <key>32BitSupportedModels</key>
              <array>
                        <string>MacBook7,1</string>
                        <string>MacBookAir5,2</string>
                        <string>MacBookPro10,1</string>
                        <string>MacPro5,1</string>
                        <string>Macmini5,3</string>
                        <string>iMac12,2</string>
              </array>
              <key>BuildMachineOSBuild</key>
              <string>13A566b</string>
              <key>CFBundleDevelopmentRegion</key>
              <string>English</string>
              <key>CFBundleDisplayName</key>
              <string>Boot Camp Assistant</string>
              <key>CFBundleExecutable</key>
              <string>Boot Camp Assistant</string>
              <key>CFBundleGetInfoString</key>
              <string>Boot Camp Assistant 5.1.0, Copyright © 2013 Apple Inc. All rights reserved</string>
              <key>CFBundleIconFile</key>
              <string>DA</string>
              <key>CFBundleIdentifier</key>
              <string>com.apple.bootcampassistant</string>
              <key>CFBundleInfoDictionaryVersion</key>
              <string>6.0</string>
              <key>CFBundleName</key>
              <string>Boot Camp Assistant</string>
              <key>CFBundlePackageType</key>
              <string>APPL</string>
              <key>CFBundleShortVersionString</key>
              <string>5.1.0</string>
              <key>CFBundleSignature</key>
              <string>????</string>
              <key>CFBundleVersion</key>
              <string>473</string>
              <key>DARequiredROMVersions</key>
              <array>
                        <string>IM41.0055.B08</string>
                        <string>IM42.0071.B03</string>
                        <string>IM51.0090.B03</string>
                        <string>IM52.0090.B03</string>
                        <string>IM61.0093.B01</string>
                        <string>MP11.005C.B04</string>
                        <string>MB11.0061.B03</string>
                        <string>MBP11.0055.B08</string>
                        <string>MBP12.0061.B03</string>
                        <string>MM11.0055.B08</string>
              </array>
              <key>DTCompiler</key>
              <string>com.apple.compilers.llvm.clang.1_0</string>
              <key>DTPlatformBuild</key>
              <string>5A11344p</string>
              <key>DTPlatformVersion</key>
              <string>GM</string>
              <key>DTSDKBuild</key>
              <string>13A566b</string>
              <key>DTSDKName</key>
              <string></string>
              <key>DTXcode</key>
              <string>0500</string>
              <key>DTXcodeBuild</key>
              <string>5A11344p</string>
              <key>LSApplicationCategoryType</key>
              <string>public.app-category.utilities</string>
              <key>LSMinimumSystemVersion</key>
              <string>10.9.0</string>
              <key>NSMainNibFile</key>
              <string>MainMenu</string>
              <key>NSPrincipalClass</key>
              <string>NSApplication</string>
              <key>PreESDRequiredModels</key>
              <array>
                        <string>MacBook7</string>
                        <string>MacBookAir5</string>
                        <string>MacBookPro10</string>
                        <string>MacPro5</string>
                        <string>Macmini6</string>
                        <string>iMac12</string>
              </array>
              <key>PreUEFIModels</key>
              <array>
                        <string>MacBook7</string>
                        <string>MacBookAir5</string>
                        <string>MacBookPro10</string>
                        <string>MacPro5</string>
                        <string>Macmini6</string>
                        <string>iMac13</string>
              </array>
              <key>PreUSBBootSupportedModels</key>
              <array>
                        <string>MacBook7,1</string>
                        <string>MacBookAir3,2</string>
                        <string>MacBookPro8,3</string>
                        <string>MacPro5,1</string>
                        <string>Macmini4,1</string>
                        <string>iMac12,2</string>
              </array>
              <key>Win7OnlyModels</key>
              <array>
                        <string>MacBook7,1</string>
                        <string>MacBookAir3,2</string>
                        <string>MacBookPro5,5</string>
                        <string>MacPro2,1</string>
                        <string>Macmini4,1</string>
                        <string>iMac10,1</string>
              </array>
    </dict>
    </plist>
    I have already tried this :
    https://discussions.apple.com/message/21796614#21796614
    and this:
    https://discussions.apple.com/thread/3435734?start=15&tstart=0
    but neither of them have helped me to get the bootcamp work properly. Every time i try to modify this fie i get an error.
    Please any help would be welcome.

    No problem, forget the daemon tools and Microsoft usb tool, use BooTcamp Assistant for making bootable usb of windows 7 using that .iso.
    you can do the following :
    1. Add your Boot Rom Version(from system info) under DARequiredROMVersions.
    2. Add Model Identifier(from system info) under PreUSBBootSupportedModels
    3. Delete "Pre" from "PreUSBBootSupportedModels", so you have "USBBootSupportedModels"
    The first 3 steps are same as before and if its not clear you can easily google solutions with screenshots.
    The next step is only for OSX 10.9, as it employs some kind of code signature to prevent you from changing info.plist and cause bootcamp to crash.
    4. Open your terminal, use the following command
    sudo codesign -fs - /Applications/Utilities/Boot\ Camp\ Assistant.app
    Sudo means using administrator privilege and u need to enter your mac password. And the command resigns the bootcamp application so that it runs with the new info.plist file and not crash.
    5. Continue on with your installation....
    Cheers.
    P.S. back up info.plist before u change anything.
    I installed windows 7 ultimate 64 bit two days ago using this mehod. It is working perfectly. Hope this will solve your problem.Please do make a backup of ur macbook before partition, for safe side.
    while using that command mentioned in step 4., may be you get a option to download xcode or something like that, just click ok and download and install that, in my case it was about 101MB.

Maybe you are looking for

  • ALE FOR HRM - EREC SYSTEMS

    Hi all.. We are trying to configure ALE between Ecc Hr and EREC systems. what we did : 3 badi imlementations were activated in HRM and EREC systems. 1. created logical system and assigned cleint. 2. created RFC connection and  determined RFC dewstina

  • Need Suggestion on including JSTL Tags with JSF

    Hi..All.... I need some suggestions.. i Started doing a project in JSF.. i am new to JSF... I Developed some part of the project in Struts.. but now.. our clinet says... The Application Has to go with JSF.so.. started redesigning again.... Can i use

  • How do I save a file in the Dreamweaver CC folder on my computer's hard drive?

    Hi, I bought Dreamweaver CC.  I am trying to put a flash button in Dreamweaver that will like to another web site. The problem I am running into is when I try to save the flash button into my computer's Dreamweaver folder, I get a message saying "Con

  • Why do my photos play blurry??

    Hello I have high-resolution images (1600 x 1600 pixels - 300 resolution). When I import them into FCP - they look fine in the viewer and when paused in the canvas. However when I hit play they immediately become blurry. I've tried resizing to 720 x

  • Updating to Lion on my macbook and not able to access iPhoto

    I have updated my macbook (Mac OS X) to Lion but I can't seem to update iphoto. I have no access to iphoto and there is a wheel that continually spins saying it is updating, but it is now Day 7 and there is no update and there are no photos. Help!