>On Sat, Feb 26, 2005 at 09:05:34PM -0500, Harry Cochran wrote: >> Hi, >> >> Is an easier way to do this just to have a 50MB f0 partition and then a >> 50-200MB e2 partition that you mount as /boot?
On Sat, Feb 26, 2005 at 09:16:34PM -0500, Grant Grundler wrote: >no. >grant Okay. Trying it your way one more time. However ... first palo.conf SinoHub5:/etc# cat palo.conf --commandline=1/vmlinux initrd=1/initrd.img root=/dev/sda3 HOME=/ --format-as=2 --update-partition=/dev/sda --recoverykernel=/boot/vmlinux-2.4.17-32 SinoHub5:/etc# palo palo version 1.5 [EMAIL PROTECTED] Tue Sep 21 15:14:17 MDT 2004 ELF32 executable For ext2/3-formatted palo partitions, you cannot specify a kernel or a ramdisk. 2nd try to identify error: SinoHub5:/etc# cat palo.conf --commandline=0/vmlinux root=/dev/sda3 HOME=/ --format-as=2 --update-partition=/dev/sda --recoverykernel=/boot/vmlinux-2.4.17-32 SinoHub5:/etc# palo palo version 1.5 [EMAIL PROTECTED] Tue Sep 21 15:14:17 MDT 2004 ELF32 executable For ext2/3-formatted palo partitions, you cannot specify a kernel or a ramdisk. 3rd try to identify error: 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. ko 0x44000 ksz 3687647 k64o 0x0 k64sz 0 rdo 0 rdsz 0 <1/vmlinux initrd=1/initrd.img root=/dev/sda3 HOME=/> Fourth try to identify error: SinoHub5:/etc# cat palo.conf --commandline=0/vmlinux 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. ko 0x44000 ksz 3687647 k64o 0x0 k64sz 0 rdo 0 rdsz 0 <0/vmlinux root=/dev/sda3 HOME=/> 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. 2. initrd has nothing to do with the v3 vs. v4 problem 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. Having an f0 partition and an e2 /boot is looking pretty good right now! No joy tonight, Harry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
