You are not logged in.
Pages: 1
i installed arch64 after being away for a while. and i installed beyond on it and made an initrd with mkinitcpio. my system seems to boot fine now but the device for my /boot partition is missing (/dev/md1) when i boot the beyond kernel i compiled it seems to be there. here is my mkinitcpio and menu.lst
# vim:set ft=sh
MODULES="xfs md-mod raid0 raid1"
BINARIES=""
FILES=""
HOOKS="base udev autodetect ide fbsplash keymap"
FBTHEMES="darch"
FBRES="1024x768"
timeout 5
default 0
color light-blue/black light-cyan/blue
# (0) Arch Linux
title Arch Linux [/boot/vmlinuz]
root (hd0,0)
kernel (hd0,0)/vmlinuz26beyond root=/dev/md2 ro md=2,/dev/hda2,/dev/hdb2 vga=792 splash=silent,fadein,theme:darch console=tty1 quiet
initrd (hd0,0)/initrd
Offline
spot the difference...
# (0) Windows
title Windows
root (hd0,0) no verify
makeactive
chainloader +1
savedefault
# (1) Beyond
title Beyond-Arch
root (hd0,5)
kernel /vmlinuz26beyond root=/dev/hda7 ro video=vesafb:ywrap,mtrr,1024x768-32@75 splash=silent,theme:darch console=tty1 quiet ro
initrd /kernel26beyond.img
savedefault
# (2) Game
title Invaders
root (hd0,5)
kernel /invaders/invaders
Offline
you use windows and i don't? idk ;-p
Offline
you use windows and i don't? idk ;-p
Errrm
initrd (hd0,0)/initrd
initrd /kernel26beyond.img
You're not using mkinitcpio, yo.
Offline
that was just what i called my image when i made it with mkinitcpio. i ran mkinitcpio -k 2.6.17-beyond -g initrd
Offline
Well, then this is probably an initscripts issue - I know tpowa recently made some changes to the initscripts with relation to raid devices....
Offline
Pages: 1