[SOLVED] Fail to boot Arch x86_64 live CD on a HP laptop

Hey, guys, what's up?
Well, here's the thing: I bought a new laptop a couple days ago and I'm kind of having some trouble. Its a HP Pavilion dm4-1063cl (this model: http://www.notebookcheck.info/HP-Pavili … 579.0.html, just in case).
I ran some tests in Windows 7 about the architecture of the processor and it clearly seems that it can support arch x86_64 bits. However, I tried to boot Arch x86_64 by a Net Installation CD and it doesn't work. The process fail in the "Loadin UDEV events" phase, something like that. PS: the i686 image boots perfectly.
Then, I thought that was the CD I burned the reason for trouble - I did not check md5sum and stuff like that. So, I burned another dual image (with boths i686 and x86_64) and tried to run again the 64bits kernel. It did not work in the same phase.
The only response I get is a dark screen that never seems to go away. It was a panic I've never seen before with Arch Linux.
The only alternative I can think right now is trying an older version of the live image CD and see what happens, but it doesn't seem like a very good option. Any ideas?
Hope someone of you can help me. Here in Brazil, most of computers we buy come with Windows installed and we don't have quite a chance of not getting - or paying for - it. I'm sure I'll have such a trouble installing dual boot with Arch Linux, but I really miss my Arch Linux...
And, damn, I worked too hard to get a new processor. I really dont wanna use Arch i686 on a pc with x86_64 architecture, it seems like an option, but a dumb one. =p
Cheers,
Wilson.
EDIT: It turns out that tt was not a kernel panic as I thought. The kernel changed the resolution of the display during this fase, and somehow it doesent work.
The trick I used to solve this was adding "nomodeset" to the kernel line in the Live CD booting. Btw, you can do it by selecting the booting option you want in the live CD and pressing TAB. Then, you can edit the kernel line. (:
Last edited by wilsaooo (2010-12-28 06:17:41)

lamegaptop wrote:
Resurrecting this post because I may help you or someone else.
HP DM4-1265, Intel Corei5, Intel Graphics. (Two days old, windoze wiped, Arch installed)
At boot the brightness is, for some unexplained reason, set all the way down to 0 on these intel based DM4 laptops. A few simple <Fn>+<F3> turns the brightness back up.
To solve this I had to put this in rc.local -
echo 6 > /sys/class/backlight/acpi_video0/brightness
you can enter it manually to test first (as root). Try to turn your brightness up and down with it to make sure it works.
My fan ran like crazy too. HP chose to default a BIOS setting that keeps the fan running constantly. I disabled that and all is well. Fan only comes on when needed and lm_sensors shows my temps, right now, at 43C. Ambient is at 77F right now (I'm in Florida) and this kick butt Arch laptop is, in fact, on my lap.....
Don't give up man.
First of all: thanks for replying.
I installed manually the "coretemp" kernel modules and lm-sensors now give some different response. The script "sensors-detect" does not find any answer.
Looks like the temperature run in a regular level (50º-60º), which I consider a good sign. However, sometimes when I use arch for 24h+, it shuts down suddenly and does not let me boot my computer again - I believe it is a overheating problem. Happened a couple times, big no big deal.
On the other hand, in Windows 7 I have no trouble at all. The temperature goes around 40º with some daily activities. It worries me out because I used - and I do use - largely and successfully Arch i686 version in crappy notebooks with no heating at all.
I tried some tweaks in the rc.local, but none of them seemed to really work. With cpufreq, I could slow down the processors and maintain a regular temperature. Looks like I can list some of the fans speed in the /sys/ files, but much of them do not seem to have any change at all. Some of them looks like to have some "max_state" set to low values like 1, but most do have a limit like 10.
I will keep trying. If there's anything new, I'll post here
Cheers,
Wilson

Similar Messages

[Solved] Unable to boot Arch off SUSE GrUB

Hi,
I have several OS installed on my machine. I used to boot everything including Arch but BSD, Solaris & PCBSD with GrUB2 off UbuntuStudio. Earlier today I installed SUSE GrUB on sda and now I am unable to boot Arch. I've used SUSE GrUB earlier and was able to boot Arch off it.
Here is my menu.lst
# Modified by YaST2. Last modification on Sun Oct 17 18:52:19 SGT 2010
# THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader
# Configure custom boot parameters for updated kernels in /etc/sysconfig/bootloader
default 0
timeout 8
##YaST - generic_mbr
gfxmenu (hd0,30)/boot/message
##YaST - activate
###Don't change this comment - YaST2 identifier: Original name: linux###
title Desktop -- openSUSE 11.2 - 2.6.31.14-0.1
root (hd0,30)
kernel /boot/vmlinuz-2.6.31.14-0.1-desktop root=/dev/disk/by-id/ata-ST3320418AS_9VMD0YPT-part31 resume=/dev/disk/by-id/ata-ST3320418AS_9VMD0YPT-part5 splash=silent quiet showopts vga=0x315
initrd /boot/initrd-2.6.31.14-0.1-desktop
###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 11.2 - 2.6.31.14-0.1
root (hd0,30)
kernel /boot/vmlinuz-2.6.31.14-0.1-desktop root=/dev/disk/by-id/ata-ST3320418AS_9VMD0YPT-part31 showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 x11failsafe vga=0x317
initrd /boot/initrd-2.6.31.14-0.1-desktop
###Don't change this comment - YaST2 identifier: Original name: windows 1###
title Windows 7 Ultimate Edition x64
rootnoverify (hd0,0)
chainloader +1
###Don't change this comment - YaST2 identifier: Original name: other###
title FreeBSD 8.1 i386
rootnoverify (hd0,2)
chainloader +1
###Don't change this comment - YaST2 identifier: Original name: other###
title OpenSolaris 2009.06 b134 x86
rootnoverify (hd0,3)
chainloader +1
###Don't change this comment - YaST2 identifier: Original name: other###
title PC-BSD 8.1 amd64
rootnoverify (hd2,0)
chainloader +1
###Don't change this comment - YaST2 identifier: Original name: CentOS (2.6.18-194.11.4.el5xen) (/dev/sda6)###
title CentOS (2.6.18-194.11.4.el5xen) (/dev/sda6)
root (hd0,5)
kernel /boot/vmlinuz-2.6.18-194.11.3.el5 ro root=/dev/sda6 rhgb quiet
initrd /boot/initrd-2.6.18-194.11.3.el5.img
###Don't change this comment - YaST2 identifier: Original name: Centos-base###
title CentOS-base (2.6.18-194.el5) (on /dev/sda6)
root (hd0,5)
kernel /boot/vmlinuz-2.6.18-194.el5 ro root=/dev/sda6 rhgb quiet
initrd /boot/initrd-2.6.18-194.el5.img
###Don't change this comment - YaST2 identifier: Original name: linux (/dev/sda8)###
title PCLinuxOS
root (hd0,7)
configfile /boot/grub/menu.lst
###Don't change this comment - YaST2 identifier: Original name: linux (/dev/sda10)###
title Simply Mepis
root (hd0,9)
configfile /boot/grub/menu.lst
###Don't change this comment - YaST2 identifier: Original name: Chakra GNU/Linux (/dev/sda12)###
title Chakra GNU/Linux (/dev/sda12)
root (hd0,11)
configfile /boot/grub/menu.lst
###Don't change this comment - YaST2 identifier: Original name: Fedora (2.6.34.7-56.fc13.x86_64) (/dev/sda14)###
title Fedora (2.6.34.7-56.fc13.x86_64) (/dev/sda14)
root (hd0,13)
configfile /boot/grub/menu.lst
###Don't change this comment - YaST2 identifier: Original name: linux (/dev/sda16)###
title Mandriva Spring 2010.1
root (hd0,15)
configfile /boot/grub/menu.lst
###Don't change this comment - YaST2 identifier: Original name: Calculate Linux Desktop x86_64 10.9 KDE (/dev/sda18)###
title Calculate Linux Desktop x86_64 10.9 KDE (/dev/sda18)
root (hd0,17)
configfile /boot/grub/menu.lst
###Don't change this comment - YaST2 identifier: Original name: linux###
title Arch linux 2010.05 x86_64
rootnoverify (hd0,18)
chainloader +1
###Don't change this comment - YaST2 identifier: Original name: Desktop -- openSUSE 11.3 - 2.6.34.7-0.3 (/dev/sda23)###
title openSUSE 11.3 - 2.6.34.7-0.3
root (hd0,22)
configfile /boot/grub/menu.lst
###Don't change this comment - YaST2 identifier: Original name: other###
title caeLinux
root (hd0,24)
kernel /vmlinuz root=/dev/sda25 ro quiet splash
initrd /initrd.img
###Don't change this comment - YaST2 identifier: Original name: other###
title UbuntuStudio 10.04 amd64
root (hd0,26)
kernel /vmlinuz root=/dev/sda27 ro quiet splash
initrd /initrd.img
###Don't change this comment - YaST2 identifier: Original name: other###
title Linux Mint 9 amd64
root (hd0,28)
kernel /vmlinuz root=/dev/sda29 ro quiet splash
initrd /initrd.img
Here is etc/fstab from Arch -
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
devpts /dev/pts devpts defaults 0 0
shm /dev/shm tmpfs nodev,nosuid 0 0
#/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
#/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
#/dev/fd0 /media/fl auto user,noauto 0 0
/dev/sda19 /boot ext2 defaults 0 1
/dev/sda20 / ext4 defaults 0 1
/dev/sda21 /var ext4 defaults 0 1
/dev/sda22 /home ext4 defaults 0 1
/dev/sda5 swap swap defaults 0 0
I've results from bootinfo script as well but the file is big and I am unable to post all those details in here.
Best,
David
Last edited by avenuemax (2010-10-18 05:30:48)

Here is the menu list off PCLinuxOS
timeout 15
color black/cyan yellow/cyan
gfxmenu (hd0,7)/boot/gfxmenu
default 0
title linux
kernel (hd0,7)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=77fb6caf-c436-4855-b25a-436f4f6c40f0 vmalloc=256M resume=UUID=92ecb3e1-84a1-4855-8a49-3c9616638795 splash=silent vga=788
initrd (hd0,7)/boot/initrd.img
title linux-nonfb
kernel (hd0,7)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=77fb6caf-c436-4855-b25a-436f4f6c40f0 vmalloc=256M resume=UUID=92ecb3e1-84a1-4855-8a49-3c9616638795
initrd (hd0,7)/boot/initrd.img
title failsafe
kernel (hd0,7)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=77fb6caf-c436-4855-b25a-436f4f6c40f0 failsafe vmalloc=256M
initrd (hd0,7)/boot/initrd.img
title Windows 7 Ultimate Edition x64
root (hd0,0)
map (0x81) (0x80)
map (0x80) (0x81)
makeactive
chainloader +1
title CentOS (Final)
root (hd0,5)
configfile /boot/grub/menu.lst
title MEPIS Linux 8.5
root (hd0,9)
configfile /boot/grub/menu.lst
title Arch
root (hd0,18)
configfile /grub/menu.lst
title Fedora (Goddard)
root (hd0,13)
configfile /boot/grub/menu.lst
title Mandriva Linux (Official)
root (hd0,15)
configfile /boot/grub/menu.lst
title Calculate Linux sda18
root (hd0,17)
configfile /boot/grub/menu.lst
title Chakra
root (hd0,11)
configfile /boot/grub/menu.lst
title openSUSE 11.3 (x86_64)
VERSION = 11.3
root (hd0,22)
configfile /boot/grub/menu.lst
title PC-BSD 8.1 amd64
root (hd2,0)
chainloader +1
title FreeBSD 8.1 i386
root (hd0,2)
chainloader +1
title OpenSolaris 2009.06 b134 x86
root (hd0,3)
chainloader +1
I can boot Arch from here, wish I get to do that from SUSE GrUB.

[SOLVED]Gummiboot cannot boot arch

Hello. I've been reading the wiki guide until the end when i got stuck. I have windows 8 installed with a UEFI mobo so i just used the same ESP for arch. Now i try to boot arch but get a "vmlinuz not found" message. What did i do wrong?
while still on live cd i mounted the EFI partition (/dev/sda2) to /boot (same root and home partition) and then installed and configured gummiboot as described.
Do i have to add that ESP to the fstab file? Or how to fix it?
Last edited by Juszr (2015-03-31 17:10:49)

Load up the Arch live ISO, mount your partitions and use `arch-chroot` then post the output of:
ls /boot
# efibootmgr -v
lsblk -f
# parted -l
You can use `sprunge` to post the output of the commands.
<command> | curl -F 'sprunge=<-' http://sprunge.us
https://wiki.archlinux.org/index.php/Li … in_clients

[SOLVED] Can only boot Arch via CD

Hi all,
I've installed 64 bit Arch on the 2nd hard drive of a Dell Optiplex 980.
It works very nicely, but I have a strange boot issue:
If I boot from the Arch CD, and select "Boot other OS", hit Tab, and manually edit the grub line to "chain.c32 hd 1 0", I am taken to the grub menu on the hard drive and can select my install which boots and runs fine.
If I select the 2nd HD in the BIOS boot menu (instead of the CD), I get to the same grub menu, but upon selecting my install, I get an Error 17.
Has anyone run into this before?
Thanks in advance!
Last edited by basementhead (2010-09-24 17:52:11)

Turns out I misunderstood how grub works.
When I changed my menu.lst to (hd 0,0) it works.
I thought that the 2nd drive was (hd 1,0), which was reinforced by the boot CD working with (1,0), but I guess the drives are renumbered when you boot from CD?
The big clues were that the partition that grub said couldn't boot was 0xde (a Dell partition), and I was sure I'd wiped the entire drive, but I knew that the 1st drive was a default Dell/Windows7 install.
Then using grub command line menu, I typed "find /sbin/init" and it found it on (hd0,2), and the mystery was solved....
Anyway - fixed by treating the drive as if it was /dev/sda (hd 0,0) instead of /dev/sdb (hd 1,0)
Thanks!

[Solved] Dual UEFI Booting Arch against pre-existing Ubuntu install

Hi All,
I'm new to Arch Linux and have just managed to install it on my T530 Lenovo laptop along side a pre-existing Ubuntu installation.
However, although I did consult the dual boot posting and article here on the site beforehand, those articles seemed to be about installing Grub. Since I already have it up and working, I was nervous about deleting it and so potentially loosing my working Ubuntu installation.
I tried installing mounting my pre existing /boot/efi partition but the pre-existing vmlinuz-linux file (no doubt from my Ubuntu installation) prevented it from working. My solution was to create the boot folder on the same partition as my Arch installation.
I now have an installation that works (kind of) however, it appears each time I boot up, I have to edit the Grub entry for my Arch installation to update the UUID Grub points to to get it to load up Arch. I can't find where the actual file being loaded in Grub resides (the file that it appears generates this script, is itself built from a series of predefined variables).
I admit I am playing at the moment - I'm keen to get to grips with this distro and am up for considering all options including deleting and starting again to learn to get it set up correctly. My questions are:
How should I have done this so that my Arch linux distro was loaded via Grub called by the UEFI and had the same booting file structure as the already existing Ubuntu installation (using the BOOTLOADER partition and the /boot/efi folders on it)
How do I edit the Grub file for my Arch distro so it stays edited (no more retyping all the UUIDs each time I load it up
Is there a way to get to the installation I currently have to an the more ideal state
Details taken thanks to the bootrepair application are here:
http://paste.ubuntu.com/10682898/
Thanks and regards,
Simon
Last edited by simon_sjw (2015-04-22 11:50:52)

I don't think there are any Ubuntu kernel images on your EFI system partition (they are in /boot, not /boot/efi).
If you want Arch to boot in an EFI system you should mount /boot (rather than /boot/efi) to the EFI system partition.
To do this, copy the /boot folder over to /dev/sda1 and add it to your /etc/fstab (in Arch):
/dev/sda1 /boot vfat rw,relatime,discard,nodev,nosuid,noexec,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
It's probably best to install & configure GRUB from Arch rather than Ubuntu because Arch mounts /boot to the ESP while all other distributions mount /boot/efi so the results may get confusing (ie, GRUB may create menu entries to boot Ubuntu with your Arch kernel and vice versa); also the Arch kernel image is booted read-write whereas most other kernel images are booted read-only.
https://wiki.archlinux.org/index.php/GRUB#UEFI_systems
I find the os-prober script can fail sometimes so this is probably your problem here.
Personally, I use gummiboot to boot my Debian system by copying the kernel image & initial ramdisk to the EFI system partition using these commands in Debian (this would also work in Ubuntu):
# mount /dev/sda1 /mnt
# cp /vmlinuz /initrd.img /mnt
Then I make a gummiboot menu entry; your Ubuntu entry would look like this:
title Ubuntu
linux /vmlinuz
initrd /initrd.img
options root=/dev/sda2 ro
Add any kernel parameters after "ro" and make an entry for Arch as well (you may also need to configure /boot/loader/loader.conf as per the ArchWiki page) & install gummiboot from Arch using:
# gummiboot install
You can then create a post-install script at /etc/kernel/postinst.d/zz-update-gummiboot in your Ubuntu system to copy over the kernel image & initrd to the ESP whenever the kernel is updated:
#!/bin/sh
mount /dev/sda1 /mnt
cp /vmlinuz /initrd.img /mnt/
umount -R /mnt
Make this executable:
# chmod +x /etc/kernel/postinst.d/zz-update-gummiboot
This method will only work if you have /boot mounted to the EFI system partition (as outlined in the Beginner's Guide).

[SOLVED] Failing to boot on Macbook Pro

I'm trying to install arch on a MacBookPro7,1. I have installed refit and have partitioned my hard drive to add three additional fat32 partitions for home, root and swap.
When booting off the arch cd, the menu to boot the 64 bit arch installer comes up. Then it says comreset failed errno=-16 and boots into initramfs and prevents me from starting the actual installation.
Any help with my situation would be much appreciated
Last edited by sarvagnan937 (2011-03-27 20:23:44)

sarvagnan937 wrote:I used the latest arch core installation media. I'm unable to find the archboot installation isos
Here are the lastest archboot isos. Hope this will work for you.

[Solved] Can't boot arch after merge linux partition

Before this i have issue with my partition table, but i can fix it with testdisk.
After that, i merge all my linux partition into one. I mean like this
Before i merge my linux partition:
/ >> /dev/sda3
/var >> /dev/sda4
swapfile >> /dev/sda6
/home >> /dev/sda7
My new partition
/ >> /dev/sda3
swapfile >> /dev/sda6
i can't boot my arch after i backup and moved my home and var directory to /dev/sda3 with livecd.
How to fix this issue?
Last edited by nizar (2009-03-28 04:18:29)

Solved by myself! LOL
I edit and remove /dev/sda4 and /dev/sda7 in my /etc/fstab file with livecd.
Now, arch boot without /dev/sda4 and /dev/sda7

[SOLVED] Unable to boot Arch installer

Hello everyone.
I am no experienced Linux user (I'm just about one year and a half), but I think that dealing with things is the way to learn about them. I'm using Debian and want to switch to Arch.
I have an USB drive, and would like to put the installer (sorry? I'm not sure if that's the correct name. Please excuse me if I am not too concise) on it, without using a CD. I also have an Internet connection through ethernet, and I guess the "installer" will be able to use it to download any needed files.
So, as explained in the wiki and some external guides, I have copied the ISO I downloaded to the USB drive (with dd), just after formatting it as FAT32 with MBR.
I rebooted, with the USB plugged in, entered the BIOS menu and set the USB floppy as the first boot device. Then I exited from BIOS. I saw the LED of my pendrive flicking but no more, the BIOS stayed there (Press ESC to enter BIOS setup menu) and the light always flicking. (I waited about half an hour and nothing happened.)
I have tried it many times, and nothing has changed. I'm now a bit scared: is there anything wrong with my motherboard? Maybe with the filesystem on the external drive? I was wondering if there were any other choices to install Arch from within another Linux distro (Debian "Squeeze" in this case). I know nothing about chroot and other advanced techniques, but (if this helps) I don't want to save anything from my hard drive, i.e., I want a clean install.
Thank you, and, as I said, sorry if this question is very weird, or if I'm missing something important. I'm sure I've looked through many places in the web -too many, I guess; my eyes now hurt me. I'm also not very good at English so, sorry again.
P.S.: I have just tried with a CD-R burning the ISO with Brasero, and it didn't work. The same: freezing. I have UEFI disabled in my BIOS. I'm now wondering what's happening with my computer. It has about five years, and it looks like packed rubbish, but ...
Last edited by Kalrish (2013-03-02 18:46:23)

It sounds like you're mixing up the methods for creating the USB install media. You mention formatting with FAT32, that's from the Without overwriting the USB drive method. But you also mention copying the iso with dd, which is from the Overwrite the USB drive method.
You should follow one method or the other from the wiki only, and pay attention to the output for any errors. Then, if things go wrong again, you will be able to provide better detail.

[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] Failed to mount /boot/efi

Hi,
Recently I've been having a lot of trouble starting Arch Linux. As in I can't. It starts off fine, but then whike it tries to mount my disks I get this problem:
systemd-fsck[159]: fsck.fat 3.0.23 (2013-10-15)
systemd-fsck[159]: /dev/sda5: 111 files, 6783/130048 clusters
[ OK ] Started File System Check on /dev/disk/by-uuid/6AE1-65C8.
Mounting /boot/efi...
[ FAILED ] Failed to mount /boot/efi.
See 'systemctl status boot-efi.mount' for details.
[ DEPEND ] Dependency failed for Local File Systems.
Welcome to emergency mode! After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" to try again
to boot into default mode.
This is the output of systemctl status boot-efi.mount:
boot-efi.mount - /boot/efi
Loaded: loaded (/etc/fstab)
Active: failed (Result: exit-code) since Sun 2013-12-01 17:40:58 EST; 4min 16s ago
Where: /boot/efi
What: /dev/disk/by-uuid/6AE1-65C8
Process: 179 ExecMount=/bin/mount /dev/disk/by-uuid/6AE1-65C8 /boot/efi -t vfat -o rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro (code=exited, status=32)
Dec 01 17:40:58 jay-archlinux systemd[1]: boot-efi.mount mount process exited, code=exited status=32
Dec 01 17:40:58 jay-archlinux systemd[1]: Failed to mount /boot/efi
Dec 01 17:40:58 jay-archlinux systemd[1]: Unit boot-efi.mount entered failed state.
The output of mount /dev/disk/by-uuid/6AE1-65C8 /boot/efi -t vfat:
mount: unknown filesystem type: 'vfat'
(When I first started getting this it told me dosfstools wasn't installed. However I've since installed the latest version and it's made no difference.
I dual boot Arch Linux and Windows 8 on a laptop under UEFI, and have had this setup for about a year now. This problem seems like it may be associated with recent problems I've been having with windows 8 (Spontaneously restarting itself 2 or 3 times a day with a BSoD and "Kernel Data Inpage Error".) One time after such a restart I went to boot Arch Linux after the restart rather than Windows and got errors similar to the one I first posted, except that they were occurring with my Windows NTFS partitions which I mount in Arch Linux. After booting into Windows and restarting manually, the error just became what it is now. However I'm not sure if this was where the problem first began or not as I haven't used Arch Linux very often over the past few months.
Does anyone have any idea what's going on or how to fix it?
Thanks.
Last edited by jdgordon01 (2013-12-01 14:05:59)

pacman -Q linux
linux 3.11.6-1
uname -a
3.9.9-1-ARCH #1 SMP PREEMPT Wed Jul 3 22:45:16 CEST 2013 x86_64 GNU/Linux
No idea how that's happened... I initially tried 'mkinitcpio -p linux' but it also did nothing.
EDIT: Turns out I must have updated at some point and forgotten a crucial step in manually copying the new files in /boot/ to /boot/efi/EFI/arch/ which is necessary when updating under UEFI systems. I updated again using the live USB/chrooting, manually copied everything that was needed and everything's working again!
Last edited by jdgordon01 (2013-12-01 14:05:35)

Boot arch netinstall iso from grub2

http://www.panticz.de/MultiBootUSB
I found this blog post and I successfully did it with linux mint but I couldn't do it with arch. what are the correct grub2 commands?
I tried with:
set root=(hd0,1)
loopback loop /arch.iso
linux (loop)/boot/vmlinuz26 iso-scan/filename=/arch.iso
initrd (loop)/boot/System.map26
I have no idea what System.map26 is and grub2 didn't choke when I offered it to him so I tried it. I couldn't find the normal initrd file.
Moreover, I know that there should be some boot=something parameter to the kernel in order for it to work but I couldn't guess the right one and I found no documentation about it.
If someone did it, I would appreciate your help
Thanks.

This is what I have:
menuentry "ArchLinux 2009-08 Core 64bit" {
set root=(hd0,1)
loopback loop /boot/iso/archlinux-2009.08-core-x86_64.iso
linux (loop)/boot/vmlinux26 iso-scan/filename=/boot/iso/archlinux-2009.08-core-x86_64.iso quiet
Get I get a "File not found" error.
*Edit*
I found /boot/grub/menu.lst (inside the iso) and found this:
title Boot Arch Linux Live CD
kernel /boot/vmlinuz26 lang=en locale=en_US.UTF-8 archisolabel=ARCHISO_KE1AECIE ramdisk_size=75%
initrd /boot/archiso_pata.img
There's the path for the initrd
*Edit #2*
"You need to load the kernel first." Well duh. You're supposed to do that grub.
Last edited by jordanwb (2009-11-10 19:37:19)

[SOLVED] Arch Linux Duke (2007) Fails to Boot

Folks, I have a unique and challenging problem that has exhausted my Arch Linux skills, and so I am now turning to you.
I have a vintage Pentium Pro 200 system (that’s 200 MHz folks! – 200 MHz 686 architecture – the original 686!), two CPUs, running a dual boot between Windows NT 4.0 and Arch Linux Duke (2007). It has 512 MB of RAM and a 120 GB hard drive, partitioned up between Windows NT and Linux. I built this system new in 2007, hence the dated version of Arch. It has run like a charm all these years, granted not getting that much use. After about a year of no use at all, I fired the system up last week to help with a little research for a blog post I was writing on networking Windows NT 4.0 and Mac OS 8.6. Windows NT 4.0 fired right up with no issue, and after I was done testing what needed to be tested I tried to boot over to Arch.
After a year of disuse, Arch unexpectedly and stubbornly refused to boot. The boot process started up just fine, but towards the end, it declared that it could not mount the root file system on the root device and took a kernel panic and stopped. My Arch skills have gotten a bit rusty in the last few years, but I dusted them off and went to work. My guess was a file system or superblock error. Arch wouldn’t boot, but I dragged out my trusty RIPLinux 2.9 Rescue Live CD and fired it up. It came right up and ran, and I was able to mount the Arch partition and view all the files… everything seemed to be there; it just wouldn’t boot. Windows NT 4.0 AND RIPLinux both boot and run on the machine, so the hardware is fine as well.
A little information on the disk layout. Windows NT 4.0 is in the first partition on the hard drive. The extended partition has a second Windows NT 4.0 partition (sort of a /home partition for Windows NT 4.0), followed by the main Arch partition (the one I am trying to boot), followed by a swap partition and then the largest partition, which I use to share data between Arch and Windows NT 4.0 (I have loaded an ext2/3 driver into Windows NT 4.0 and it happily accesses the Linux partitions on the box).
RIPLinux’s e2fsck did find some issues with the Arch partition and I had it repair them all. I checked again afterwards that all the files were still there, and they were. With the partition now known to be clean, and the superblock repaired from one of the backups, all should have been well. However, Arch still wouldn’t (and still won’t) boot.
RIPLinux has a kind of a chain loader function, so I had it attempt to start up Arch for me. However, this was flummoxed by the fact that Arch addresses all my hard drive partitions as /dev/sdax and RIPLinux addresses them as /dev/hdax. Hence, without a common language, it was hard to get the one to start the other. Still, using this function, I have been able to get a crippled version of Arch running on the machine again. No modules had been loaded, and so it couldn’t do almost anything, but there it was (and is), Arch Linux Duke, at the CLI level. From there, I can see all the files, I can move freely in and out of my user account and the root account, but I can’t make the thing actually boot properly.
If you have read this far, you are a trooper. Summarizing what I know, the hardware is good, the file system is clean, the superblock is good, I can mount it cleanly from a live CD and I can chain load a crippled version of Arch. Here is the boot process blow-by-blow. When I try to do a normal boot, the Windows NT 4.0 loader passes control to the Lilo boot sector I have placed on hda1 (sda1 in Duke’s parlance). Lilo takes over, present a menu and when I select Duke, takes off. Arch Linux Duke starts to boot. It gets a good long way along, all the way along to:
:: Loading udev events [Pass]
:: Mount root Read-only
:: Checking file systems
This is where it stops.
The next thing I see is:
/dev/sda6
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else) then the superblock is corrupt and you might try running e2fsck with an alternate superblock:
E2fsck –b 8193 <device>
I then get a sort of character based splash screen that says
**********FILE SYSTEM CHECK FAILED ****************************
* Please repair manually and reboot. Note that the root file system
* is currently mounted read-only. To remount it read-write, type:
* mount –n –o remount,rw /. When you exit the maintenance
* shell, the system will reboot automatically
Give root password for maintenance
At this point, I give the root password and enter the maintenance shell as root. I typed in “mount” and the first entry I got back is
/dev/sda6 on / type ext3 (rw)
This is exactly the root partition that the start up complains about. It is clearly there. I can see it, I can walk around it… it is clearly there. Why won’t it boot? Despite the message, the superblock is fine – it passes every test e2fsck can throw at it.
At this point, I did a “e2fsck /dev/hda6 (which is how RIPLinux would have passed it into Arch” and it says it is “clean”. I suspect that the Superblock message is because Arch sees root as sda6, while RIP passed it in as hda6...
Deciding to see what Arch would be seeing as it tried to set things up in the boot sequence, I tried the following next:
# mknod “/dev/root2” b 3 6
(“3” because RIPLinux refers to my hard drive as IDE, while Arch refers to it by major number “8”, which is SCSI. By the way, it IS an IDE drive – not sure why Arch insists on using the sdx nomenclature instead of hdx)
Then I entered “mount /dev/root2 /mnt/hda6” and “ls /mnt/hda6”
All was well. I can make the node, I can mount it, and I can see the contents. All is clearly well, but something is clearly wrong enough that Arch can’t boot.
I am totally out of ideas. I have tried every trick I know and am out of tricks. I would welcome any insights as to what I could try to get this venerable Arch installation back on its legs.
By the way, the key section of the /etc/lilo.conf file (lest anyone want to know) is:
image = /boot/vmlinuz26
root = /dev/sda6
label = ArchLinux-Duke
initrd = /boot/kernel26.img
read-only
I am stumped. Thanks in advance for any and all pointers you may be able to offer.
Last edited by mac57 (2014-06-02 17:42:21)

Folks, thanks for all your helpful comments, and I wanted to report back to you that I finally overcame the issue, and ArchLinux-Duke (2007) is once again executing flawlessly on my old Pentium Pro 200 system. I won't bother reporting here all the blind allies I went down as I tried to figure out what was wrong, but in the end, literally moments before I was about to give up and overwrite my Arch installation with a new Linux variant (antiX seemed well suited for such old and low power hardware), my attention was drawn to a note I had made in my files back in 2007 about a problem with similar symptoms. In that case, I had just deleted ZenWalk Linux from the hard drive (both Arch and Zen had been on the drive), and merged several partitions to make use of the newly free space. This had changed Arch's view of the drive lettering, and what had been its /dev/sddx root device was now /dev/sdcx. Arch failed to boot, throwing off the same errors I was seeing now. I wish I had recalled that note a month or so ago! It would have saved me a lot of work and a lot of frustration.
At any rate, as a last step, and testing the idea that maybe the drive lettering had changed for some reason, I repeatedly manually booted Arch, specifying root=/dev/sda6, then /dev/sdb6, then /dev/sdd6, and finally, /dev/sdc6. Eureka! Arch now considered itself to be on /dev/sdc6 whereas previously it had been on /dev/sda6. This got me part way there, but the boot failed at the filesystem check stage and threw me into root. I disabled the file system check in /etc/rc.sysinit and got farther. Then I cleaned up /etc/fstab to agree with the new sdc naming, and I was back on the air fully.
So, what had happened was that Arch had changed its view of the drive it was on from sda6 to sdc6. While I could not understand why this "sudden" change had occurred, at least I had a solution, and had Arch back up and running.
Trolling through the rest of my notes, I found the answer. In 2012, the Tekram SCSI card in the machine failed, and I ultimately replaced it with an Adaptec card. The Tekram card did not have a BIOS segment on it. The Adaptec card did. My guess is that this caused the two internal SCSI devices I have built into the system (Iomega ZIP and Jaz respectively) to be enumerated first, claiming the "sda" and "sdb". device names. That left "sdc" for the root device, and that is where Arch went next. This is my guess anyway.
I should have caught this issue back in 2012, at the time, but from my notes, I can see that I tested the new card thoroughly using the Windows NT 4.0 side of the machine, but never thought to bring up Arch as well. Hence, this problem lay dormant for two years, before I attempted to fire up Arch last month and blundered right into it.
It has not all been bad. I have learned more about the ext2 and ext3 file systems and superblocks in the intervening time than I will ever need to use. I have learned how to manually boot Linux on a machine whose BIOS is so old that it cannot address the disk cylinder that the kernel is on and I have completely refreshed the many general Linux skills that used to just flow from my finger tips. It has been a frustrating experience, but ultimately a successful and useful one.
Just wanted to let everyone know that this is now [SOLVED]. I would mark the post as such, but I don't see any obvious way to do that. Thanks again everyone.

Arch x86_64 won't boot, but i686 will. Live USB and HDD.

To be more succinct, what could cause 64 bit arch not to boot when 32 bit arch boots fine on a non-UEFI system that supports 64 bit, when all other variables are constant?
My first response seeing this post would be to immediately assume the noob (me) posting this doesn't know the difference between a 32 and 64 bit system. However, "ubuntu-14.04.1-desktop-amd64.iso" (latest 64 bit ubuntu iso) boots from live USB and installs without error. It also came preinstalled with Windows 7 (64 bit), so I'm relatively sure it supports x86_64.
I wrote "archlinux-2014.08.01-dual.iso" (MD5 verified) to my USB. Selecting i686 boots fine. Selecting x86_64 restarts my system, eventually sending me back to the arch live menu after it posts.
Upon recommendation by a WonderWoofy on reddit, I tried to install arch x86_64 by bootstrapping and chrooting from the 64 bit ubuntu live usb. I ended up with same problem, where attempting to load arch reboots my system immediately.
Right now, I'm assuming it's the same issue booting from the live usb (arch iso) and from the arch installation on my hard drive, since they seem identical to me. I haven't tried recreating the install for i686 to see if it works (mainly because it's late -- if it'll help I'll do it upon suggestion).
Here's the only text that shows once I attempt to boot into arch. This is from the hard drive and using syslinux (which is pointed at my root partition on sda -- I don't have a boot partition).
Loading ../vmlinuz-linux... ok
Loading ../initramfs-linux.img...ok
Probing EDD (edd=off to disable)... ok
Which doesn't look like it's messing up anywhere...
And of course I'm a noob so go easy on me x)
UPDATE: I found this thread but I'm not seeing his error message, so I'm not sure what to do.
Last edited by SirProudNoob (2014-08-13 02:54:24)

It's an Intel Core 2 Quad processor. Are there any more diagnostic commands that would be helpful? I didn't see anything else in util-linux that might help...
Here's the output for "lscpu":
ubuntu@ubuntu:~$ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 1
Core(s) per socket: 4
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 23
Stepping: 10
CPU MHz: 2327.537
BogoMIPS: 4655.07
L1d cache: 32K
L1i cache: 32K
L2 cache: 2048K
NUMA node0 CPU(s): 0-3

[SOLVED] Live USB fail to boot

Booting Arch netinstall and core from a USB fails on waht appears to be "booting the kernel"
After that the screen is flood with what looks like a dump.
The last 5 lines are something like (i quickly copied them down) and each line is preceded by a bunch of numbers:
do_one_initcall +0x35/0x170
? quick_tc86c001_idet +0x22/0x22
kernel_init +0xae/0x13a
? start_kernel +0x35d/0x35d
kernel_thread_helper +0x6/0x10
_ *blinking*
It hangs there and doesn't go away until I reset the machine
iso was torrented but I did a md5 check anyway and then created it using Universal USB installer. It works fine on my laptop.
Hardware
Mother board: Gigabyte GA-Z77-D3H
BIOS: BIOS Date: 02/21/12 15:12:36 Ver: 04.06.05
Processor: Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz (4 CPUs), ~5.9GHz
Card name: NVIDIA GeForce GTX 560 Ti
NIC:Atheros AR8151 PCI-E Gigabit Ethernet Controller (NDIS 6.20)
Last edited by glethro (2012-06-17 03:23:54)

glethro wrote:I will leave this as solved as the kernel panic is no longer happening.. But archbot doesn't seem to work either. When in the configure step it shows a fstab file with an entry only for tmp. I booted this and it created the entire file system as read only. I reinstalled and used my own fstab file and was still left with a read-only system.
I successfully installed archlinux using archboot... concerning your fstab issue, I just haven't look this file in the configure step and everything worked fine... did you try editing this file manually without using the archboot installer ?

[SOLVED] Luks with /arch/setup installation , fails at boot

Hi all,
So I tried to install arch on virtualbox with encrypted partitions (root /, /home/ and swap), but it fails at boot.
/dev/sda1 is /boot
/dev/sda2 is swap
/dev/sda3 is /
/dev/sda4 is /home
The root partition seems to be loading fine because it asks for my password, then the boot sequence goes on, until the /home/ (apparently) :
:: Bringing up loopback interface
:: Unlocking encrypted volumes: chome..Usage: cryptsetup [-?vyrq] (...all the options...can't copy paste with virtualbox)
/sbin/cryptsetup: Unknown action
failed [FAIL]
/dev/mapper/croot: clean, 27576/457856 files, 166316/1830898 blocks
fsck.ext4: No such file or directory while trying to open /dev/mapper/chome
Possibly non-existent device?
/dev/sda1: clean,29/24096 files, 20790/96356 blocks
[FAIL]
It seems that it tries to open /dev/mapper/chome but it's not mounted yet
In my /etc/crypttab, I added the lines :
chome /dev/sda4 none luks
cswap /dev/sda2 none luks
/etc/fstab (I didn't change anything, /arch/setup configured it that way) :
/dev/mapper/chome /home ext4 defaults 0 1
/dev/mapper/croot / ext4 defaults 0 1
/dev/mapper/cswap swap swap defaults 0 0
/dev/sda1 /boot ext2 defaults 0 1
And grub :
title Arch Linux
root (hd0,0)
kernel /vmlinuz-linux root=/dev/mapper/croot cryptdevice=/dev/sda3:croot ro
initrd /initramfs-linux.img
What I wanted to do was to have swap,root and home encrypted partitions mounted at boot, but maybe it is not possible?
I tried a lot of configurations for /etc/fstab and /etc/crypttab according to what I could find on the net but nothing worked. I read the whole tutorial https://wiki.archlinux.org/index.php/Sy … _with_LUKS but there is no config for fstab or crypttab or grub when installing with /arch/setup
Thanks for any help !
Last edited by John0000 (2012-04-12 12:50:18)

Indeed you have a point, putting password in plaintext isn't very safe.
There is a good alternative though: https://wiki.archlinux.org/index.php/Sy … _a_Keyfile
the reason why you don't have a passphrase for root in a file somewhere is that you provide this passphrase during boot-time.
Somewhere during boot you get the option to unlock you root device by typing in a passphrase... right?
ro means that the volume is mounted read only http://linux.die.net/man/8/mount

[SOLVED] Fail to boot Arch x86_64 live CD on a HP laptop

Similar Messages

Maybe you are looking for