Presenting the X1Boot Manager!

[musa]

Hi
hurray I got cfe to work or I found the right commands .
instead of
boot -elf -noints -fs=amigafs ide0.5,x1boot/boot/zimage+5.11
I use this
boot -elf -noints -fs=amigafs ide0.0,x1boot:boot/zimage+5.11
and dir is
dir -fs=amigafs ide0.0:
insted of
dir -fs=amigafs ide0.1: (my amigaboot.of partion is number 1)

and dir of x1boot is
dir -fs=amigafs ide0.0,x1boot:

very happy
Have a nice day to all
Peter

[xeno74]

very happy
Have a nice day to all
Peter

Great! Thanks a lot for sharing your experiences!

[Hypex]

Hi
hurray I got cfe to work or I found the right commands .

Excellent. FYI my boot command line was this:

Code: Select all

boot -z -elf -noints -nousb -fs=amigafs ide0.1,dh12:boot/zImage-5.11

I can check my kernel boot dir with this:

Code: Select all

dir -fs=amigafs ide0.1,dh12:boot

My HDD is on the default 0.1 unit and though I would like it as first unit I never did move it as I didn't want to break my system. Given these things can be particular. I'm always getting stuck on the keyboard only working in one port when I take my X1000 out for a run but a broken AmigaOne HDD is harder to fix.

[Hypex]

Some extra info, So I was able to boot the vmlinux-5.11 kernel directly from CFE with boot command. But it breaks from the X1Boot menu. AmigaBoot would take up some memory and when loading kernel there wouldn't be enough reserve left to hold it in memory. But AmigaBoot doesn't abort with any out of memory error.

I've confirmed that the zImage is actually a stripped kernel. So I've adjusted my kernel installer to compensate and strip it down before compressing a vmlinux image. I'm making some extra progress so should have an update soon.

[xeno74]

I've confirmed that the zImage is actually a stripped kernel.

Yes, that's correct.

make -j4 CROSS_COMPILE=powerpc-linux-gnu- ARCH=powerpc zImage

Output:

Code: Select all

  CALL    scripts/atomic/check-atomics.sh
  CALL    scripts/checksyscalls.sh
  CHK     include/generated/compile.h
powerpc-linux-gnu-strip -s -R .comment vmlinux -o arch/powerpc/boot/vmlinux.strip

file vmlinux.strip

Output:

Code: Select all

vmlinux.strip: ELF 64-bit MSB executable, 64-bit PowerPC or cisco 7500, version 1 (SYSV), statically linked, BuildID[sha1]=24fbed3cd662d00018c80f0430ba471c1de150e9, stripped

Code: Select all

-rwxrwxr-x 1 christian christian 38940256 Mai 31 10:21 vmlinux-5.13
-rwxrwxr-x 1 christian christian 32036432 Mai 31 10:25 vmlinux.strip

After that:

gzip -9 vmlinux.strip (max compression, from Unix)

[Hypex]

Yes, that's correct.

Thanks xeno74. I tested using a usual strip command which did okay. The specific line got it down slightly more. I found out "nm" can extract a system map from a full kernel. But don't know where to get the abi from. Those files common in boot folders.

[vox]

Just passing throgh to say "I wish this was in EPROM"

[xeno74]

Great description!

X1000 Linux doesn't exactly have a boot loader. It used to boot Linux kernel from USB which uses the same method as from HDD. I used a preset menu entry that runs a CFE command to boot from USB. That means, using the CFE boot command, it loads an ELF binary into a specified location and then jumps to the entry point.

Thanks!

Please note:

CFE firmware does not recognise USB devices on power-up unless they are connected to the first USB port which is reserved for the keyboard. Unless you have a USB hub connected to the first port which allows you to connect both the keyboard and USB stick, you will need to insert the USB stick AFTER you have entered CFE.

[Hypex]

Thanks.

Yes, I tend to forget that I had a USB stick plugged into my Apple keyboard. Which is why I am able to so easily boot from USB. Since that contains a hub connected to my keyboard port. When I plug in a USB stick to my front port it's a bit hit and miss. I find it unreliable and it won't always mount.