You are not logged in.
Pages: 1
I downloaded the iso image found here.
According to the fast guide Im following, I created a archcd partition and copied everything from the cd there. I then edited grubs menu.lst.
Problems started after reboot, grub gave me "file not found". Rebooting back into my existing install, remounting the archcd partition, I see that there is no "isolinux" folder on that partition. Is the guide outdated? This was what I added to menu.lst:
title archcd
kernel (hd1,5)/isolinux/vmlinuz root=/dev/sdb6 BOOTMEDIA=cd
initrd (hd1,5)/isolinux/initrd.img
The partition I created to hold the copied contents of the cd is /dev/sdb6.
Heres whats on the fakecd partition:
$ cd /media/archcd && ls -R
.:
boot boot.catalog isomounts overlay.sqfs root-image.sqfs
./boot:
archiso_ide.img isolinux releasenotes.txt
archiso_pata.img memdisk.bin splash.xpm.gz
diag2.img memdisk.bin.COPYING System.map26
diag2.img.COPYING memtest vmlinuz26
grub memtest86+ x86test_zImage.bin
help memtest86+-1.70.bin x86test_zImage.bin.COPYING
invaders.img memtest86+-1.70.bin.COPYING
./boot/grub:
arch.xpm.gz iso9660_stage1_5 reiserfs_stage1_5 tools.lst
colors.lst jfs_stage1_5 settings.lst tryboot.lst
e2fs_stage1_5 keyboards.lst splash.xpm.gz ufs2_stage1_5
fat_stage1_5 menu.lst stage1 vstafs_stage1_5
ffs_stage1_5 minix_stage1_5 stage2 xfs_stage1_5
help.lst more.lst stage2_eltorito
./boot/help:
bootexisting.txt contrib.txt legacyide.txt usb.txt
./boot/isolinux:
boot.msg help.msg isolinux.cfg options.msg splash.rle splashsmall.rle
./boot/memtest86+:
memtest.bin
Searching around the forums, I found this thread. He is using something different:
# (0) Arch Linux
title Arch Linux
root (hd0,0)
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/... ro rootdelay=8
initrd /boot/kernel26.img
Those files I have! So I updated the files/folders to point to those instead. But no avail, grub still gives the same error.
Whats my next step?
Offline
I had a similar problem except I got past the boot menu and arch started loading but never found the partition, something like a kernel panic or something rather.
I think it has something to do with an improperly or bad kernel configuration.
Offline
Pages: 1