Can't boot Arch for installation. USB stick issue.

I got stuck. I tried to install arch on my dekstop, but booting Arch from USB stick freezes in same point, after running hooks. I tried with two usb sticks, new iso etc. Ubuntu was installed before without any problem from the same stick.
It freezes after showing:
Waiting 30 seconds for device /dev/disk/by-label/ARCH_201108 ...
[4.053579] sd 12:0:0:0: [sdb] No Caching mode page present
[4.053634] sd 12:0:0:0: [sdb] Assuming drive cache: write through
[4.056259] sd 12:0:0:0: [sdb] No Caching mode page present
[4.059035] sd 12:0:0:0: [sdb] Assuming drive cache: write through
In some attempts I also got this:
ata_id[12376]: HDIO_GET_IDENTITY failed for '/dev/sdb': Invalid argument

Problem is sovled, but the solution is really courious.
In fact, there was no issue with usb stick. Display freezes on first showed lines and does not follow the rest. Arch booted successfully but I cannot notice that, because I still see first lines (messages from first post were just warnings). Switching FullHD, 16:9 monitor to old 3:4 display solved the problem.
It's really strange. Should I report it somewhere?
Last edited by 0xddr (2012-05-12 23:30:53)

Similar Messages

  • Booting Arch-ISO from USB-Stick in UEFI mode fails

    Hi there,
    I'm running an Asrock H77M-ITX UEFI mobo. On this system I've already installed Arch on a Samsung 830 SSD (GPT formatted) - but in BIOS legacy mode because I've written the Arch-ISO image with "dd" to an USB-Stick (and UEFI boot mode wasn't even presented at boot).
    Out of curiosity I've re-formatted the stick and copied Arch-ISO following https://wiki.archlinux.org/index.php/Un … B_from_ISO.
    Now I could start the ISO in UEFI mode, but it failed to start gummiboot with the "No loader found. Configuration files in \loader\entries\*.conf are needed." error message, concerning a problem with gummiboot.
    Following some advice on the forum, I did this:
    - install refind-efi 0.4.7-2
    - copy /usr/lib/refind/refindx64.efi to [USB]/EFI/boot and renaming it to bootx64.efi (i.e. replacing the original bootx64.efi from gummiboot)
    - Create a new file in the same directory ([USB]/EFI/boot/) called refind.conf
    - Add this to it:
    textonly
    scanfor manual
    menuentry Arch {
    loader /arch/boot/x86_64/vmlinuz
    initrd /arch/boot/x86_64/archiso.img
    options "gpt loglevel=7 add_efi_memmap none=UEFI_ARCH_x86_64"
    With this I can launch Arch-ISO from the USB-Stick in UEFI mode and I can choose Arch from rEFIND. Then Arch-ISO starts booting but it always stops at the same point with this message:
    sd 6:0:0:0: [sdb] No Caching mode page present
    sd 6:0:0:0: [sdb] Assuming drive cache: write through
    sd 6:0:0:0: [sdb] Attached SCSI removable disk
    ERROR: '/dev/disk/by-label/' device did not show up after 30 seconds ...
    Falling back to interactive prompt
    You can try to fix the problem manually, log out when you are finished
    sh: can't access tty: job control turned off
    [rootfs /]#
    sdb is the USB-Stick from which I start Arch-ISO. Again - I didn't use dd to write the ISO to the stick.
    Maybe this is pretty easy to solve, but I have to admit that I'm somewhat stuck
    Last edited by swordfish (2012-11-19 21:31:43)

    WonderWoofy wrote:See what the difference is between archiso and archboot maybe?  Seriously, have you made any effort whatsoever?
    Of course. Read:
    The "Main Page" ( https://www.archlinux.org/ ) states:
    "You've reached the website for Arch Linux, a lightweight and flexible Linux® distribution that tries to Keep It Simple."
    "Keep It Simple". Yeah!
    In line with that, the "The Arch Way" page ( https://wiki.archlinux.org/index.php/The_Arch_Way ) states:
    "The following five core principles comprise what is commonly referred to as the Arch Way, or the Arch Philosophy, perhaps best summarized by the acronym KISS for Keep It Simple, Stupid."
    The ArchWiki ( https://wiki.archlinux.org/ ) links to several other pages, such as these:
    The "Forum Etiquette" page ( https://wiki.archlinux.org/index.php/Forum_Etiquette ) states under "Ineffective Discussion":
    "Arch is a Do It Yourself community" and "treat others as you would be treated; respect them and their views". I am very much a "do it yourself" person -- that's why I like The Arch Way. I also go by the Golden Rule stated here.
    Now, everyone is a newbie at some time. I and other posters here are obviously newbies with respect to ArchLinux. Even experts were newbies at one time. Newbies, by definition, do not necessarily know what they're doing, or where to find information. Hence, Arch's "Beginners' Guide" and such. Hence, posts on this board from newbies asking for help.
    As regards initial installation of ArchLinux, and consistent with the above, the FAQ ( https://wiki.archlinux.org/index.php/FAQ ), under "Q) Arch needs an installer. Maybe a GUI installer", states:
    "A) Since installation doesn't occur often (read the rest of this article to know more about what rolling release means), it is not a high priority for developers or users. The Installation Guide and Beginners' Guide have been fully updated to use the command-line method. If you're still interested in using an installer, consider using Archboot."
    So the basic installation instructions explicitly state that Archboot is not needed.
    The "Installation Guide" ( https://wiki.archlinux.org/index.php/Installation_Guide ) says nothing about either Archboot or Archiso.
    The "Beginners Guide" ( https://wiki.archlinux.org/index.php/Beginners%27_Guide ) says nothing about either Archboot or Archiso.
    The "Archboot" page ( https://wiki.archlinux.org/index.php/Archboot ) is consistent with the above information, because it states:
    "Archboot is a set of scripts to generate bootable media for CD/USB/PXE.
    It is designed for installation or rescue operation."
    The "Archiso" page ( https://wiki.archlinux.org/index.php/Archiso ) states:
    "Archiso is a small set of bash scripts that is capable of building fully functional Arch Linux based live CD and USB images. It is a very generic tool, so it could potentially be used to generate anything from rescue systems, install disks, to special interest live CD/DVD/USB systems, and who knows what else."
    So the pages describing both Archboot and Archiso clearly state that these tools are oriented towards already-existing installations -- even though it seems that they might be used, in certain circumstances, for initial installations.
    I happen to be very new at playing around with installing Linux distros (although I've used Unix/Linux as a regular user for more than 30 years), and am brand new with respect to ArchLinux. I only began playing with it this past Saturday. So I would expect a bit of useful help as opposed to "RTFM!" I will soon get past the need to RTFM for basic tasks, but I have a way to go.
    The fact is that for me and a number of other new ArchLinux users, the installation guides simply do not work. C.f. my post https://bbs.archlinux.org/viewtopic.php?id=153170 . I've done a lot of googling as well as searching the archives on this board, and others have come up against the same show-stopping installation problems that I have. I and others have posted to several recent threads on this board, trying to get past the problems, so far with no success.
    Now, the.ridikulus.rat had written:
    "You guys are using Archboot's kernel options for Archiso. Thats the issue in both the cases."
    Given that neither of these sets of scripts were used by me or swordfish, this comment is not useful.
    Given the above, can you or anyone else tell us what Archiso or Archboot might do to help us with our installation problems? Also, can you tell us how we, as newbies, ought to have found out how these might help?
    Alan

  • [SOLVED]Can't boot Arch after installation-grub use wrong uuid in bios

    Hello I would like to ask for Your help and say hello. I'm new here.
    I have one big problem with Arch. Can't boot it after base installation. The same problem with Arch, that was mentioned in this topic:
    https://bbs.archlinux.org/viewtopic.php … 7#p1294597
    I have the same problem and the same error:
    No such Device: ad4103fa-d940-47ca-8506-301d8071d467.
    Loading Linux core repo kernel ...
    error: no such partition.
    Loading initial ramdisk ...
    error: you need to load the kernel first.
    Press any key to continue..._
    I'm new here, and with Arch, could you explain me how to fix it? I tried the solution given in the link above, several times but with each time i have errors and warnings from the post 1 in mentioned topic. I installed my Arch from usb thumb drive. Maybe this is something to do with it? Also, my hard drive that Arch is installed on is being connected to a "raid card" named Adaptec, but during installation my disk is being found so i think that drivers is present and works ok, so it is not related to this, also there is no raid present, i use it only as a mean to connect to motherboard because there is not enough sata port, and because:
    https://bugs.archlinux.org/task/35626
    he wrote that this error is also on virtualbox, so it is not my fault and Adaptec related issue.
    I haven't tried this yet:
    Sotanaht,
    I had the exact same problem as you, but I was able to fix it by replacing the bad grub.cfg file with the grub.conf file found in the same directory. If you try this do not forget to back up your original file (just in-case smile)
    because i don't know much about it, don't want to destroy data on my hard disks or to destroy my other distros (i use Ubuntu with derrativates such as Mint, Kubntu, Lubuntu, Xubuntu, and Slackware 13.37 and 14.00).
    If you could explain it in details i would be really happy.
    I could post something about my setup, please write what. My computer is:
    -AMD X4 PII 955 runinng at 3.2GHz
    -4GB DDR2 runinng at base clock (800 if i remember correctly)
    -about 7 hard drive disk connected to a sata ports, one adaptec drive that i mentioned above and one dvd-rom
    -nvidia GTX260
    -850W PSU Chieftec
    Last edited by firekage (2013-07-02 08:11:29)

    Yes, of course. I did it several times with
    grub-mkconfig -o /boot/grub/grub.cfg
    and the result is always the same - Error posted above.
    Here is my grub.cfg file:
    # DO NOT EDIT THIS FILE
    # It is automatically generated by grub-mkconfig using templates
    # from /etc/grub.d and settings from /etc/default/grub
    ### BEGIN /etc/grub.d/00_header ###
    insmod part_gpt
    insmod part_msdos
    if [ -s $prefix/grubenv ]; then
    load_env
    fi
    set default="0"
    if [ x"${feature_menuentry_id}" = xy ]; then
    menuentry_id_option="--id"
    else
    menuentry_id_option=""
    fi
    export menuentry_id_option
    if [ "${prev_saved_entry}" ]; then
    set saved_entry="${prev_saved_entry}"
    save_env saved_entry
    set prev_saved_entry=
    save_env prev_saved_entry
    set boot_once=true
    fi
    function savedefault {
    if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
    fi
    function load_video {
    if [ x$feature_all_video_module = xy ]; then
    insmod all_video
    else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
    fi
    if [ x$feature_default_font_path = xy ] ; then
    font=unicode
    else
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos5'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 ad4103fa-d940-47ca-8506-301d8071d467
    else
    search --no-floppy --fs-uuid --set=root ad4103fa-d940-47ca-8506-301d8071d467
    fi
    font="/usr/share/grub/unicode.pf2"
    fi
    if loadfont $font ; then
    set gfxmode=auto
    load_video
    insmod gfxterm
    set locale_dir=$prefix/locale
    set lang=en_US
    insmod gettext
    fi
    terminal_input console
    terminal_output gfxterm
    set timeout=5
    ### END /etc/grub.d/00_header ###
    ### BEGIN /etc/grub.d/10_linux ###
    menuentry 'Arch Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-ad4103fa-d940-47ca-8506-301d8071d467' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos5'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 ad4103fa-d940-47ca-8506-301d8071d467
    else
    search --no-floppy --fs-uuid --set=root ad4103fa-d940-47ca-8506-301d8071d467
    fi
    echo 'Loading Linux core repo kernel ...'
    linux /boot/vmlinuz-linux root=UUID=ad4103fa-d940-47ca-8506-301d8071d467 ro quiet
    echo 'Loading initial ramdisk ...'
    initrd /boot/initramfs-linux.img
    menuentry 'Arch Linux, with Linux core repo kernel (Fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-fallback-ad4103fa-d940-47ca-8506-301d8071d467' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos5'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 ad4103fa-d940-47ca-8506-301d8071d467
    else
    search --no-floppy --fs-uuid --set=root ad4103fa-d940-47ca-8506-301d8071d467
    fi
    echo 'Loading Linux core repo kernel ...'
    linux /boot/vmlinuz-linux root=UUID=ad4103fa-d940-47ca-8506-301d8071d467 ro quiet
    echo 'Loading initial ramdisk ...'
    initrd /boot/initramfs-linux-fallback.img
    ### END /etc/grub.d/10_linux ###
    ### BEGIN /etc/grub.d/20_linux_xen ###
    ### END /etc/grub.d/20_linux_xen ###
    ### BEGIN /etc/grub.d/20_memtest86+ ###
    ### END /etc/grub.d/20_memtest86+ ###
    ### BEGIN /etc/grub.d/30_os-prober ###
    ### END /etc/grub.d/30_os-prober ###
    ### BEGIN /etc/grub.d/40_custom ###
    # This file provides an easy way to add custom menu entries. Simply type the
    # menu entries you want to add after this comment. Be careful not to change
    # the 'exec tail' line above.
    ### END /etc/grub.d/40_custom ###
    ### BEGIN /etc/grub.d/41_custom ###
    if [ -f ${config_directory}/custom.cfg ]; then
    source ${config_directory}/custom.cfg
    elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
    source $prefix/custom.cfg;
    fi
    ### END /etc/grub.d/41_custom ###
    It is wrong, the root partition is different than in this, we can see that this grub leads to wrong root partition, i posted my root partition at the bottom from /etc/fstab. I don't know how to fix it - i'm not familiar with the dos names (hd 0,5 and so on).
    Here is my /etc/fstab:
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    # /dev/sdb2
    UUID=59603166-5d8a-4aaf-81f7-5a822fd630e5 / ext4 rw,relatime,data=ordered 0 1
    # /dev/sdb1
    UUID=20028674-d7e8-4bf4-8551-64f133641962 none swap defaults 0 0
    (END)
    Last edited by firekage (2013-07-01 06:26:59)

  • [Solved] Boot process hangs for installed Arch and installation usb

    Hi. I've been using Arch Linux for around 6 months now and I'm in love with it. It is now my primary OS. However, I might have done something or performed some update, and I can no longer boot into Arch. The boot process hangs right before it should show the login screen (I'm using Gnome 3.6 with GDM). I see the following messages on the screen:
    Loading Linux core repo kernel ...
    Loading initial ramdisk ...
    /dev/sda3: recovering journal
    /dev/sda3: clean, 330610/1749664 files, 5585671/6996827 blocks
    And then it hangs right there. I have to hard-reboot after this.
    I then tried to boot using the Arch Linux Installation USB (archlinux-2012.12.01-dual.img), which also hangs at a particular point, before it should show me the prompt. I took a picture of the screen where it hangs: Screen Capture. This is an issue with just my laptop, because the USB boots just fine on another laptop I tried.
    I also have Windows 7 and Ubuntu 12.10 installed on my system, and I'm able to boot into both of them.
    I have 2 hard drives: /dev/sda is a 120GB SSD, and /dev/sdb is a 500GB hard disk. My partitions are as follows:
    sda1 - Windows 7 100MB System Reserved Partition (boot flag enabled)
    sda2 - Windows 7 OS
    sda3 - ArchLinux (boot flag enabled)
    sdb1 - Ubuntu 12.10 (boot flag enabled)
    sdb2 - Just data
    I ran bootinfoscript and below is the output:
    Boot Info Script 0.61 [1 April 2012]
    ============================= Boot Info Summary: ===============================
    => Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector 1 of
    the same hard drive for core.img. core.img is at this location and looks
    in partition 99 for .
    => Grub2 (v1.99) is installed in the MBR of /dev/sdb and looks at sector 1 of
    the same hard drive for core.img. core.img is at this location and looks
    in partition 99 for .
    sda1: __________________________________________________________________________
    File system: ntfs
    Boot sector type: Windows Vista/7: NTFS
    Boot sector info: No errors found in the Boot Parameter Block.
    Operating System:
    Boot files: /bootmgr /Boot/BCD
    sda2: __________________________________________________________________________
    File system: ntfs
    Boot sector type: Windows Vista/7: NTFS
    Boot sector info: No errors found in the Boot Parameter Block.
    Operating System: Windows 7
    Boot files: /Windows/System32/winload.exe
    sda3: __________________________________________________________________________
    File system: ext4
    Boot sector type: -
    Boot sector info:
    Mounting failed: mount: /dev/sda3 already mounted or sda3 busy
    sdb1: __________________________________________________________________________
    File system: ext4
    Boot sector type: -
    Boot sector info:
    Operating System: Ubuntu 12.10
    Boot files: /boot/grub/grub.cfg /etc/fstab
    sdb2: __________________________________________________________________________
    File system: ntfs
    Boot sector type: Windows Vista/7: NTFS
    Boot sector info: No errors found in the Boot Parameter Block.
    Operating System:
    Boot files:
    ============================ Drive/Partition Info: =============================
    Drive: sda _____________________________________________________________________
    Disk /dev/sda: 120.0 GB, 120034123776 bytes
    255 heads, 63 sectors/track, 14593 cylinders, total 234441648 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    Partition Boot Start Sector End Sector # of Sectors Id System
    /dev/sda1 * 2,048 206,847 204,800 7 NTFS / exFAT / HPFS
    /dev/sda2 206,848 178,466,084 178,259,237 7 NTFS / exFAT / HPFS
    /dev/sda3 * 178,466,085 234,440,703 55,974,619 83 Linux
    Drive: sdb _____________________________________________________________________
    Disk /dev/sdb: 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
    Partition Boot Start Sector End Sector # of Sectors Id System
    /dev/sdb1 * 63 20,948,759 20,948,697 83 Linux
    /dev/sdb2 20,964,824 976,771,071 955,806,248 7 NTFS / exFAT / HPFS
    "blkid" output: ________________________________________________________________
    Device UUID TYPE LABEL
    /dev/mmcblk0p1 6665-3162 vfat
    /dev/sda1 CA6A20CC6A20B75B ntfs System Reserved
    /dev/sda2 1EE242D5E242B137 ntfs
    /dev/sda3 65db0c59-9f04-46f1-975d-8a4c28132137 ext4
    /dev/sdb1 bb9818db-ce7c-43a4-8ad5-8d3702001aed ext4
    /dev/sdb2 3C2E3A4E2E3A0206 ntfs
    ================================ Mount points: =================================
    Device Mount_Point Type Options
    /dev/mmcblk0p1 /media/dhaval/6665-3162 vfat (rw,nosuid,nodev,uid=1000,gid=1000,shortname=mixed,dmask=0077,utf8=1,showexec,flush,uhelper=udisks2)
    /dev/sdb1 / ext4 (rw,errors=remount-ro)
    =========================== sdb1/boot/grub/grub.cfg: ===========================
    # DO NOT EDIT THIS FILE
    # It is automatically generated by grub-mkconfig using templates
    # from /etc/grub.d and settings from /etc/default/grub
    ### BEGIN /etc/grub.d/00_header ###
    if [ -s $prefix/grubenv ]; then
    set have_grubenv=true
    load_env
    fi
    set default="0"
    if [ x"${feature_menuentry_id}" = xy ]; then
    menuentry_id_option="--id"
    else
    menuentry_id_option=""
    fi
    export menuentry_id_option
    if [ "${prev_saved_entry}" ]; then
    set saved_entry="${prev_saved_entry}"
    save_env saved_entry
    set prev_saved_entry=
    save_env prev_saved_entry
    set boot_once=true
    fi
    function savedefault {
    if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
    fi
    function recordfail {
    set recordfail=1
    if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfail; fi; fi
    function load_video {
    if [ x$feature_all_video_module = xy ]; then
    insmod all_video
    else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
    fi
    if [ x$feature_default_font_path = xy ] ; then
    font=unicode
    else
    insmod part_msdos
    insmod ext2
    set root='hd1,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
    else
    search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
    fi
    font="/usr/share/grub/unicode.pf2"
    fi
    if loadfont $font ; then
    set gfxmode=auto
    load_video
    insmod gfxterm
    set locale_dir=$prefix/locale
    set lang=en_US
    insmod gettext
    fi
    terminal_output gfxterm
    if [ "${recordfail}" = 1 ]; then
    set timeout=-1
    else
    set timeout=10
    fi
    ### END /etc/grub.d/00_header ###
    ### BEGIN /etc/grub.d/05_debian_theme ###
    set menu_color_normal=white/black
    set menu_color_highlight=black/light-gray
    if background_color 13,37,73; then
    clear
    fi
    ### END /etc/grub.d/05_debian_theme ###
    ### BEGIN /etc/grub.d/10_linux ###
    function gfxmode {
    set gfxpayload="${1}"
    if [ "${1}" = "keep" ]; then
    set vt_handoff=vt.handoff=7
    else
    set vt_handoff=
    fi
    if [ "${recordfail}" != 1 ]; then
    if [ -e ${prefix}/gfxblacklist.txt ]; then
    if hwmatch ${prefix}/gfxblacklist.txt 3; then
    if [ ${match} = 0 ]; then
    set linux_gfx_mode=keep
    else
    set linux_gfx_mode=text
    fi
    else
    set linux_gfx_mode=text
    fi
    else
    set linux_gfx_mode=keep
    fi
    else
    set linux_gfx_mode=text
    fi
    export linux_gfx_mode
    if [ "${linux_gfx_mode}" != "text" ]; then load_video; fi
    menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-bb9818db-ce7c-43a4-8ad5-8d3702001aed' {
    recordfail
    gfxmode $linux_gfx_mode
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd1,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
    else
    search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
    fi
    linux /boot/vmlinuz-3.5.0-21-generic root=UUID=bb9818db-ce7c-43a4-8ad5-8d3702001aed ro quiet splash acpi_osi=Linux acpi_backlight=vendor $vt_handoff
    initrd /boot/initrd.img-3.5.0-21-generic
    submenu 'Advanced options for Ubuntu' $menuentry_id_option 'gnulinux-advanced-bb9818db-ce7c-43a4-8ad5-8d3702001aed' {
    menuentry 'Ubuntu, with Linux 3.5.0-21-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.5.0-21-generic-advanced-bb9818db-ce7c-43a4-8ad5-8d3702001aed' {
    recordfail
    gfxmode $linux_gfx_mode
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd1,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
    else
    search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
    fi
    echo 'Loading Linux 3.5.0-21-generic ...'
    linux /boot/vmlinuz-3.5.0-21-generic root=UUID=bb9818db-ce7c-43a4-8ad5-8d3702001aed ro quiet splash acpi_osi=Linux acpi_backlight=vendor $vt_handoff
    echo 'Loading initial ramdisk ...'
    initrd /boot/initrd.img-3.5.0-21-generic
    menuentry 'Ubuntu, with Linux 3.5.0-21-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.5.0-21-generic-recovery-bb9818db-ce7c-43a4-8ad5-8d3702001aed' {
    recordfail
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd1,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
    else
    search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
    fi
    echo 'Loading Linux 3.5.0-21-generic ...'
    linux /boot/vmlinuz-3.5.0-21-generic root=UUID=bb9818db-ce7c-43a4-8ad5-8d3702001aed ro recovery nomodeset
    echo 'Loading initial ramdisk ...'
    initrd /boot/initrd.img-3.5.0-21-generic
    menuentry 'Ubuntu, with Linux 3.2.0-29-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.2.0-29-generic-advanced-bb9818db-ce7c-43a4-8ad5-8d3702001aed' {
    recordfail
    gfxmode $linux_gfx_mode
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd1,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
    else
    search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
    fi
    echo 'Loading Linux 3.2.0-29-generic ...'
    linux /boot/vmlinuz-3.2.0-29-generic root=UUID=bb9818db-ce7c-43a4-8ad5-8d3702001aed ro quiet splash acpi_osi=Linux acpi_backlight=vendor $vt_handoff
    echo 'Loading initial ramdisk ...'
    initrd /boot/initrd.img-3.2.0-29-generic
    menuentry 'Ubuntu, with Linux 3.2.0-29-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.2.0-29-generic-recovery-bb9818db-ce7c-43a4-8ad5-8d3702001aed' {
    recordfail
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd1,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
    else
    search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
    fi
    echo 'Loading Linux 3.2.0-29-generic ...'
    linux /boot/vmlinuz-3.2.0-29-generic root=UUID=bb9818db-ce7c-43a4-8ad5-8d3702001aed ro recovery nomodeset
    echo 'Loading initial ramdisk ...'
    initrd /boot/initrd.img-3.2.0-29-generic
    ### END /etc/grub.d/10_linux ###
    ### BEGIN /etc/grub.d/20_linux_xen ###
    ### END /etc/grub.d/20_linux_xen ###
    ### BEGIN /etc/grub.d/20_memtest86+ ###
    menuentry "Memory test (memtest86+)" {
    insmod part_msdos
    insmod ext2
    set root='hd1,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
    else
    search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
    fi
    linux16 /boot/memtest86+.bin
    menuentry "Memory test (memtest86+, serial console 115200)" {
    insmod part_msdos
    insmod ext2
    set root='hd1,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
    else
    search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
    fi
    linux16 /boot/memtest86+.bin console=ttyS0,115200n8
    ### END /etc/grub.d/20_memtest86+ ###
    ### BEGIN /etc/grub.d/30_os-prober ###
    menuentry 'Windows 7 (loader) (on /dev/sda1)' --class windows --class os $menuentry_id_option 'osprober-chain-CA6A20CC6A20B75B' {
    insmod part_msdos
    insmod ntfs
    set root='hd0,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 CA6A20CC6A20B75B
    else
    search --no-floppy --fs-uuid --set=root CA6A20CC6A20B75B
    fi
    chainloader +1
    ### END /etc/grub.d/30_os-prober ###
    ### BEGIN /etc/grub.d/30_uefi-firmware ###
    ### END /etc/grub.d/30_uefi-firmware ###
    ### BEGIN /etc/grub.d/40_custom ###
    # This file provides an easy way to add custom menu entries. Simply type the
    # menu entries you want to add after this comment. Be careful not to change
    # the 'exec tail' line above.
    ### END /etc/grub.d/40_custom ###
    ### BEGIN /etc/grub.d/41_custom ###
    if [ -f ${config_directory}/custom.cfg ]; then
    source ${config_directory}/custom.cfg
    elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
    source $prefix/custom.cfg;
    fi
    ### END /etc/grub.d/41_custom ###
    =============================== sdb1/etc/fstab: ================================
    # /etc/fstab: static file system information.
    # Use 'blkid' to print the universally unique identifier for a
    # device; this may be used with UUID= as a more robust way to name devices
    # that works even if disks are added and removed. See fstab(5).
    # <file system> <mount point> <type> <options> <dump> <pass>
    proc /proc proc nodev,noexec,nosuid 0 0
    # / was on /dev/sdb1 during installation
    UUID=bb9818db-ce7c-43a4-8ad5-8d3702001aed / ext4 errors=remount-ro 0 1
    =================== sdb1: Location of files loaded by Grub: ====================
    GiB - GB File Fragment(s)
    4.564525127 = 4.901121536 boot/grub/grub.cfg 1
    5.130507946 = 5.508840960 boot/initrd.img-3.2.0-29-generic 2
    5.851592541 = 6.283099648 boot/initrd.img-3.5.0-21-generic 2
    6.317649364 = 6.783524352 boot/vmlinuz-3.2.0-29-generic 1
    4.965751171 = 5.331934720 boot/vmlinuz-3.5.0-21-generic 2
    5.851592541 = 6.283099648 initrd.img 2
    5.851592541 = 6.283099648 initrd.img.old 2
    4.965751171 = 5.331934720 vmlinuz 2
    4.965751171 = 5.331934720 vmlinuz.old 2
    I tried adding nomodeset and acpi=off to the boot parameters, but the boot process still hangs. Please let me know if I should provide any other information.
    Last edited by dhavalparmar (2012-12-30 11:45:25)

    Ok.. So my Arch Linux randomly decided to work. I'm sure I didn't do anything between my last "not working" state and my current "working" state. Below are a few things I tried:
    I thought of trying an earlier build of ArchLinux, and downloaded archlinux-2012.11.01-dual.iso and made a bootable USB out of it. It still hung.
    I was getting error messages during Arch boot that the last access time for the disks was at a future date. I found out that Ubuntu was using localtime instead of UTC and screwing up my hardware clock. I fixed it, and thought maybe the time issues were causing the boot problem. But fixing time didn't solve my problem.
    I chrooted into Arch from my Ubuntu install, ran 'sudo pacman -Syyu' and updated my Arch install.
    I thought maybe GDM isn't starting up. I re-enabled the service using 'systemctl enable gdm.service'.
    I removed OpenNTPd and installed NTPd. Enabled the daemon using 'systemctl enable ntpd'
    None of the above solved the problem, and rebooting to Arch still hung the system. So I stopped fiddling with it yesterday. Today, as usual, I just tried logging into Arch.. And it just worked out of the blue. The solution to me is as mysterious as the problem.
    I told this to my friend who introduced me to Arch, and this is what he said:
    Damn it computers, you were supposed to be deterministic!

  • THERE are Macbooks can boot linux from a usb stick linux?

    THERE are Macbooks can boot linux from a usb stick linux? like a usb stick with Fedora or ubuntu...

    Mid 2011 MacBook Air.
    I have gotten linux running on an older mac, but I think I had to use rEFIT
    http://refit.sourceforge.net/

  • Making a Windows 7 Installation USB Stick

    This is a discussion of making a bootable Windows 7 Installation USB-stick Media. It might apply to making other USB connected "Disks" like Smartcards bootable too.
    I recently had to do this (a Laptop with no build-in DVD drive and no USB DVD drive around). And it turned out to be surprisingly simple, using nothing but build in Windows tools from the Disk. I only found
    this german langauge guide and nothing in english (but I might just have searched after the wrong terms, google has been wierd regarding langauge lately), so I thought I write it up (along with some problems I ran into).
    Making a USB-Stick into a bootable Windows 7 (and propably Vista) Media is a 3 step process:
    1. Create a Active, Primary, FAT32 Partition of 4+ GB on the stick
    2. use bootsect.exe from Windows Disk to create the MBR and Partition Boot Record for that Partition
    3. Copy all files from the Disk to said Partition
    4. Test if it boots
    Detail analysis:
    Step 1 is so simple I doubt it needs explanations. Create enough free space on the USB disk (at worst delete all previous Partitions). Make a Priamry Partition of 4+ GiB. Mark it as Active. Format it in FAT32. The Guide used Diskpart,
    but this step can be done with any Partition Tool under any Windows, Linux, UNIX or DOS.
    While the choice of FAT32 seems a bit outdated, theye propably did not gave the relevant bootlaoder the ability to read NTFS. Or maybe they just though FAT32 is enough for a media that is mostly read. I have not tried what happens if I format it in NTFS, but
    it might be possible.
    Step 2 was the only tricky part. You need the programm "boot\bootsect.exe" from the Installation Media. It also must be run on a non-UEFI booted OS (otherwise it cancels out).
    I had a Windows 8 on a new Laptop so I had a UEFI booted system. Luckily I also had a VMWare Windows 7 lying around. I just assigned the Windows 7 ISO image to the Windows 7 VM, then connected the USB drive to the host.
    Once you have the USB stick in a a proper Windows mount the Parttion you created under 1 under any driveletter (should happen automatically under Windows), and open a console as Administrator (asumes DVD is drivletter is D: and the USB stick's partition
    ins Driveletter E:):
    //Go into the boot directory on the Install DVD
    D:
    cd boot
    //You should see a command promt like "D:\BOOT>"
    //Run bootsect.exe
    bootsect.exe /nt60 d:
    Step 3 is to either copy the contents of the DVD media (copy and paste) or the Image (Mount into Virtual DVD Drive and copy/paste, unpack ISO images contents) into the partition.
    How does this compare to other Distribution ways?
    To DVD:
    There is no need for a DVD drive. Even if a bootable USB-DVD drive is avalible, the Stick or Card will only need only USB port (most USB drives need 2 Ports due the 1 Ampere energy need of the drives).
    Flash Media has no seek times and much better throughput (the old weakpoint of any Disk and DVD/CD in particular)
    A FAT32 partition is inherently writeable. So modifications to the "Installation media" like Implementing Service Packs and other Windwos Updates, Modifying ei.cfg/preactivation/setup answer files, implementing special Disk/RAID drivers into the Windows
    PE or adding stuff that should be installed with Windows is easy (and do not requrie reburning a 4 GiB Image file).
    Since it only needs a 4 GiB partition, on a big USB stick there would still be place for other Data Partitions
    Since it relies on old techniques (Generic Bootloader + Active Primary Partition + partition boot loader), multiple Installation media on a big enough stick might be feasible (with a more advanced bootloader like GRUB). Have to test that part.
    However, the cost/media is a lot higher then a DVD. So if you need multiple Medias it will propably be cheaper to use the old DVD approach.
    Due to the needs of bootsec.exe, first creating the media can be more difficulty then just burning an image. But once it is bootable this programm is no longer needed.
    To PXE/network Distrubution:
    If you have the nessesary setup already (DHCP/PXE Server, powerfull network), the USB stick is likely inferior. The USB stick should beat a 100 MBIT Network easily, but will propably be beaten by a 1 GBIT Network. Network isntallation uses existing infrastructure
    (that you need for other reasons anyway) so the cost per media is even lower then the DVD.
    The PXE way also has even better modifyability - sending out different answer files or even automatically booting different images based on the Compuers MAC adress are tried techniques.
    If you lack the nessesary setup, the USB stick is a lot easier to implement and a lot easier to transport.
    Advanced things:
    Need to check if the partition could be formated as NTFS. I prefer a Journalling Filesystem for my USB-sticks.
    Need to check if using a advanced boot manager techniques (like Grub or modifciations to the BCD of the Windows PE) allows me to put multiple install media on one Stick (with one primary partition per "media"). Especially combining the x32/x86 and
    x64 Windows Installation Media would be worthwhile. As would be inlcuding a Window 8 or Vista installation media.
    Current Step 3 and 2 can propably be switched. I see no reason bootsect could not run from the USB stick as it runs from the DVD (it only accesses the MBR and
    VBR of the Disk, areas not in use by Windows)
    Steps 1 through 3 might be possible from the Windows PE environment. If so, only a computer with legacy BIOS boot would be nessesary (no actuall installation).
    Windows 7 can be installed on a (U)EFI system, but I have not checked if I can use the boot from teh stick on such a Computer. Latest for Windows 8 Media UEFI compatibilty is nessesary.
    Let's talk about MVVM: http://social.msdn.microsoft.com/Forums/en-US/wpf/thread/b1a8bf14-4acd-4d77-9df8-bdb95b02dbe2 Please mark post as helpfull and answers respectively.

    Advanced things:
    Need to check if the partition could be formated as NTFS. I prefer a Journalling Filesystem for my USB-sticks.
    Windows 7 can be installed on a (U)EFI system, but I have not checked if I can use the boot from teh stick on such a Computer. Latest for Windows 8 Media UEFI compatibilty is nessesary.
    I converted the stick to NTFS using the convert.exe and it continued booting. So chances are high they only choose FAT32 in the example because no feature of NTFS was per nessesary in a "almost only reading" scenario like installation media.
    The second part depends on the BIOS. I have a more advanced one where I can choose legacy boot options (like USB stick) in the boot option menu even when the default setting is UEFI, as long as I don't need Secure boot (wich I do not).
    Another question arose: Windows 7 has the Kernel/BCD level ability to boot from .VHD Files. The only thing preventing version below corporate from using this feature is a license check that is run just before the login (so way after the booting has been
    completed).
    Starting with 3.0 Windows PE is based on the kernel of Windows 7. So the instlaltion system might have the ability to boot from .VHD too and might have no such check in place. If so, I could put both versions of the Windows 7 installer into .VHD, reducing the
    need to have physical primary partitions for those.
    Windows bootprocess vs. Linux boot process under BIOS:
    The BIOS goes over all the boot media. If it finds one with a MBR, that one is executed and the BIOS part of the boot process is officially over.
     -> Under Windows the MBR contains the "generic boot loader". A simple piece of code as old as BIOS (25 Years) that looks for the primary partition with "Active" Flag on "it's" disk. If it finds one, the Partition Boot Record of that parition is executed.
    The MBR has done it's part
        -> NTLDR (NT too 2000), this one reads the boot.ini file and gives/executeds apropirate options
        -> BOOTMGR (Vista, 7), this one reads the BCD files
          -> Since Windows 7 BOOTMGR can also chainload the Partition Boot Record that is inside a .VHD File
        -> Wicher was used in Windows 3.X/95/98/ME
    Higher versions can chainload lower versions, but must be designed for this and (re)installed in the proper "order".
    The sometimes odd behavior that Windows 7 tries to keep 100 MiB in a seperate primary partition is there to have proper places for later additions to the BOOTMGR settings. Specifically it allows multiple BOOTMGR OS to use/edit the same BOOTMGR instace without
    running into problems with "whose partition is active?" (since it is always the System Reserved one). It's not disimilar to having an extra /boot partition in Linux or how a GRUB's stage 2 works.
    -> Under a typical Grub Legacy the MBR contains the Stage 1. It directly reads the Stage 2 from the proper partition/file system with a hardcoded path, but due to size limit of the MBR cannot do more. In some cases it starts a stage 1.5 wich has more
    space to do work (63 sectors between MBR and first partition), but I never used this Setup
        -> Stage 2 loads the Grub Configuration from the disk. From here it depends on what OS you want to boot.
            -> For Linux or Unix the kernel is started directly.
            -> Any Windows OS up to 7 can be booted using the chainloader command. For the OS this is identical to having the partition choosen by the Generic Bootloader.
    While it can be chainloaded by the Generic Bootloader from the active primary partition, GRUB and thus Linux has no
    requirement for any Primary Partitions. Stage 1 is designed to directly access the specific File System containng the Stage 2. In fact it does not even need to reside on the same disk (as the Generic Bootloader has to).
    If one does not need the Active Flag to control the Generic Bootloader (because a proper Stage 1 is installed in MBR) it is adviseable to mark wichever Windows Partition is chainloaded as active (up to Vista at least I had very odd behavior if the Windows boot
    partition was not marked active, down to randomly shredded Partition boot managers).
    After running a Windows Setup usually the Stage 1 has to be restored, as Windwos Setup will always write it's Generic Bootloader in the MBR. In order to get "rid" of a Grub all one has to do is overwrite the MBR with the Generic Bootloader and set the active
    flag properly.
    Let's talk about MVVM: http://social.msdn.microsoft.com/Forums/en-US/wpf/thread/b1a8bf14-4acd-4d77-9df8-bdb95b02dbe2 Please mark post as helpfull and answers respectively.

  • I can't boot from OS install USB drive Mac Mini Model 1176

    How I can't boot from OS install USB drive, Mac Mini Model 1176

    Thank you Eustace Mendis for your answer.
    I rebooted the Mac Mini holding the Option key down but it doesn't work. I used an USB drive with O.s 10.7 from Apple that I have used previuosly with other computers and I also tried with a CD install O.S 10.6
    It seems that the Mac Mini can't recognize the keyboard inputs and I tried with 3 different keyboards but still didn't work.
    I also reset the SMC and PRAM but I had no luck. Any clues?

  • Howto boot recovery discs from usb stick

    hi.i have t40 and i just bought recovery media(because predesktop area is dead).i tried many ways but i cant afford to boot recovery medias from usb stick.which tool should i use?? i dont have optical drive??

    Hello mate,
    What version of windows are using ? It's possible with windows 7.
    http://forum.lenovo.com/t5/X-Series-ThinkPad-Laptops/Making-a-usb-stick-with-the-Lenovo-recovery-par...
    Knowledge is of two kinds. We know a subject ourselves, or we know where we can find information on it.
    ThinkPad T510 4313-CTO Windows 8 x64 - Intel Core i7-620M - NVIDIA NVS 3100M - 8GB RAM - 240GB SSD- Intel Centrino Ultimate-N 6300 - Gobi 2000.
    ThinkPad Helix 3697-CTO Windows 8.1 x64 - Intel Core i7-3667U - Intel HD Graphics 4000 - 8GB RAM- 256GB SSD - Intel Centrino Advanced-N 6205 - Ericsson C5621gw

  • Elitebook 8460p only boots from two specific USB sticks

    My Elitebook 8460p boots perfectly normally from HDD but will ONLY boot from two specific USB sticks - 1. A Windows Recovery USB and 2. A Parted Magic USB stick which is a commercial partition recovery/imaging utility - it will NOT boot from ANY OTHER USB stick at all.It'll boot from a CD/DVD. What I would like to know is why it won't boot from any other bootable USB stick at all other than those two?

    That is because the other usb sticks you have tried have not been made properly bootable. Check the partition type on the sticks that work. Do they have a uefi partition or are they just MBR partitions that are active? Use Windows own disk management snapin to investigate the usb sticks.

  • After BIOS Update cannot boot Satellite C640 using USB Stick

    After upgrading my Toshiba Satellite C640-10E (PSC02E) bios to 2.00 WIN, I cannot boot the laptop using USB Stick, When I checked the BIOS using F2 I was stunned because the USB connected to laptop was labeled as FLOPPY drive. Is there any option to downgrade the BIOS?
    Thanks

    From my experience the BIOS is able to boot from
    - USB FDD (floppy disk)
    - Primary HDD,
    - USB Memory stick
    - Network (LAN)
    So I dont think that your USB memory is recognized as a USB FDD but the USB FDD appears as a separate boot device.
    It would be interesting to know if another USB flash memory would act as your old USB flash stick.
    PS: as Tonny suggested: you cannot downgrade because you dont have previous BIOS version only Toshiba service agents are able to downgrade the BIOS using traditional BIOS.

  • Can't boot arch installation media with nvidia 9600GT – nouveau error

    Hello!
    I recently tried Arch Linux and was very pleased with the performance and distro philosophy. I've managed to install it on my laptop following the beginners guide. Though, today I tried the same thing on my desktop computer and can't even reach the installation command line. This desktop have a nvidia 9600GT graphics card installed.
    I leave my process here for better understanding:
    Boot computer with installation media (I'm using the archlinux-2013.08.01-dual.iso);
    Select Boot Arch Linux (x86_64) option from the menu;
    Kernel starts to boot and then it gives me the following right after the Triggering uevents message:
    nouveau E[ PFIFO][0000:02:00.0] DMA_PUSHER - ch 1 [DRM] get 0x000000000 put 0x0000000000 ib_get 0x00000000 ib_put 0x00000001 state 0xa0000000 (err: IB_EMPTY) push 0x00406040
    the boot process freezes and I have to manually shutdown the computer.
    Just to be sure, I tried the same installation media on a different computer and it boots normally.
    I'm thinking of swaping the graphics card temporarily just for the initial installation. After that I could install the nvidia drivers and connect this graphic card back on. But sadly I'm one graphics card short.
    Can you help me?
    Thank you in advance.

    cfr wrote:
    Welcome to Arch.
    Try editing the kernel command line and adding nomodeset. This should force the OS to fall back to an alternative because nouveau requires modesetting, if I remember correctly.
    Wow! That solved it! Thank you.

  • 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 boot Arch from external HDD

    Hi, well first off this is not my first Arch Linux installation, I'm using Arch for a little over a year now (coming from slack). But this is my first attempt to have Arch on an external HDD.
    Alrighty, the situation is as follows: A rather new computer (supports booting from USB devices and the bios is set to boot from removable devices first) with a built in HDD and an external HDD that's connected to that computer via USB.
    What I did: I connected the external HDD to the computer and booted off a 2008.6 Overlord core-CD.
    Arch-Live recognized the internal HDD as sda and the external HDD as sdb.
    I partitioned the external HDD using cfdisk and ran mkfs.ext3 on it (I didn't use any switches with that).
    I started the installer, set my mount points (I should mention I'm not gonna use a swap partition here), installed the packages, well just went through the installation routine and installed grub in the MBR of sdb (the external HDD).
    Then I rebooted. And this is what doesn't work: When I boot that computer with the external HDD connected the computer completely hangs right before grub would come up. It freezes completely, ctrl+alt+del doesn't work, I need to use the powerswitch to reboot the computer.
    So I put the Arch-CD back in the CD drive trying to boot into my Arch System on the external HDD. So I started typing:
    root (hd1,0)
    kernel /boot/vmlinuz26 root=/dev/sdb1 ro vga=773
    initrd /boot/kernel26.img
    When I try to boot off that grub tells me that there is no such device as hd1,0. The funny thing is, that the auto copmletion in grub works for the kernel /boot/vmlinuz26 but it doesn't for the device /dev/sdb1, in fact even root=/de<tab> returns a "unrecognized string" message.
    So this is what I did and I can't boot off my external HDD, neither can I boot into my system on the external hdd from the cdrom.
    What am I missing here?

    The harddrive you boot from is in my experience always hd0. Could this mean your external disc is hd2?
    Have you tried chainloading from the installer cd to your external disc?

  • [SOLVED] Install Arch Linux on USB Stick!

    So, here is the deal. I want to install Arch Linux on a USB Stick so I can plug it at any computer and have my system... with me
    I've had a little bit experience with Arch so I know a few things about it... used it for a few months before on a real system.
    My USB stick is a HighSpeed 17-20 MBPS and it's 16 GB capacity.
    So how do I do it?
    Last edited by 1lj4z1 (2012-04-05 07:25:53)

    I'm using occasionally Arch installed on HDD-USB, I've just added usb hook to mkinitcpio.conf and removed autodetect (more modules=more hardware supported). So far it worked on 3 different computers (all of them have one main HDD so no grub issues, but it's no biggie if it doesn't boot right away, you can always edit grub on-the-fly by pressing "e")
    About USB stick: installing on USB stick is not the same as running it in LIVE mode! Consider yourself warned.
    If you just install it you really should read about SSD optimizations because USB flash cells also have limited read/write cycles (actually is less robust and sophisticated than SSD). Something to look at: noatime mount option, disable swap if not necessary, profile-sync-daemon and so on...
    1lj4z1 wrote:Well I don't need to chroot, i am running it live. I'll see about mkinitcpio.conf but I can't understand what you mean rebuilding initramfs? What is that exactcly?
    It means if you fiddle with mkinitcpio you should run:
    # mkinitcpio -p linux
    afterwards or bad things will happen
    Last edited by masteryod (2012-03-27 15:37:13)

  • Can't boot from my External USB since 10.5.6 Update

    Hi to everyone and sorry in advance for my english.
    Here's my problem:
    I have a copy of Mac OS X in my external USB drive, just for emergency. Two days ago I decided to update the OS, so i reboot my iMac and everythings gone in the right way. So the disk had no problems.
    I run Software update and I downloaded a 377 MB Update (from 10.5.5 to 10.5.6). The installation was successful and the iMac reboot. After first reboot I had a second reboot and now it happend. My screen is still grey with the apple logo and the black wheel that keep rollin'. The hard disk seems to be freezed.
    Someone knows if there's something i can do?? I don't wanna reinstall Mac OS.
    Thanks. Andrea.

    Restart, holding down the OPTION key until the icons start showing up on the screen. When the spinning gear stops, select the internal HD, and click arrow underneath. That should boot the machine with the internal HD. From there you can run Disk Utility on the USB HD. By the way, your English is fine.

Maybe you are looking for