Good read. Thank you.
-scoon
]]>as for what i'm working on, i tried lilo to see if it would make a difference, and lilo installed fine for my existing system, but when trying to add the installer partition, it complained that the kernel was too big...??? okay, is this maybe the problem grub was having too somehow? any idea what to do from here anyone?
]]>Hmmm. I have ide drives adn found that the installer wanted to name them sda instead of hda. I thought sda was for scsi drives. Is that not the case?
-scoon
well with arch you can have it either way
but if you go with defaults on install its gonna come out sda
the modules & hooks in /etc/mkinitcpio.conf control the outcome of hda or sda
& if you have multiple interfaced hard drives in your machine (ide scsi sata) it can be a real headache if you dont know what your doing
if you leave modules empty it will be sda
whatever hook gets loaded 1st defines which drive gets sda second hook would get sdb
for more info read this
http://wiki.archlinux.org/index.php/Con … mkinitcpio
-scoon
]]>at the grub prompt edit ( hit "e" ) for each line to make it look like this
root (hd0,3)
kernel /boot/vmlinuz26 root=/dev/sda4 ro
initrd /boot/kernel26.img
that is if root is on 1st drive("0") & 4th partition ("3") cause grub starts counting from 0
if you went with defaults your kernel line should be /dev/sda# not /dev/hda#
-scoon
]]>I use grub. It seems pretty straight forward, but when I go to boot, it gives me an error right away "Invalid or unsupported executable format"
Does this mean it doesnt work with the new vmlinuz from the Duke ISO, or have i done something wrong?
]]>