On Sat, Feb 26, 2005 at 11:55:19PM -0500, Harry Cochran wrote: > Fourth try to identify error: ...
How about reading "palo --help"? > SinoHub5:/etc# cat palo.conf > --commandline=1/vmlinux initrd=1/initrd.img root=/dev/sda3 HOME=/ > --format-as=2 > --update-partition=/dev/sda > SinoHub5:/etc# palo > palo version 1.5 [EMAIL PROTECTED] Tue Sep 21 15:14:17 MDT 2004 > OK we're doing a format as ext2 > ipl: addr 16384 size 36864 entry 0x0 > Warning!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > Boot loader header version is 3, I only know how > to handle version 4. It MIGHT work anyway. Could you replace "--update-partition=" with "--init-partition="? I'm expecting palo to blow everything on f0 away and build a new ext2 file system. THen you can: o mount /dev/sda1 /mnt o copy /boot/* /mnt o edit /etc/fstab so /dev/sda1 is mounted on /boot. If that boots, then: o unmount /boot o rm /boot/* o mount /boot As you might guess, the order is important. :^) > This, plus 10 tries at booting, all tells me that: > > 1. You can't specify a recovery kernel with this method (not very comforting > ... but palo "finds" 2.4.27-32 every time anyway). I was wondering why you > didn't specify one in your example. Now I know. One isn't needed. palo can list the contents of an ext2 directory. So any vmlinux/initrd can be used if palo can list it. > 2. initrd has nothing to do with the v3 vs. v4 problem right > 3. I can't find the magic in front of the symlinks vmlinux and initrd.img to > get 2.6 to load. I get "failed to load ram disk" every time with 10 tries at > initrd=x, where x is 0/initrd.img, 1/initrd.img, 1/boot/initrd.img, > /boot.initrd.img, etc. Or maybe it's something else entirely. Can you dump the following info (cut/paste to a shell): fdisk -l /dev/sda mount cat /etc/palo.conf ls -l /boot The "ls" command assumes the f0 partition is mounted on /boot. > Having an f0 > partition and an e2 /boot is looking pretty good right now! /boot on f0 partition definitely works. I'm certainly not the only one using it. hth, grant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
