NSLU2 apex boot problems
I'm trying to get my NSLU2 going with an updated kernel image that fits with Debian. I was using slugos/le + debian before.
In my slugos/le + debian environment, I downloaded and installed kernel-image-2.6.23-1-ixp4xx, and created the corresponding ramdisk. I downloaded the apex binary at the bottom of this wiki page: http://www.nslu2-linux.org/wiki/Debian/CompileApex. Then I took the debian installer image, and unpacked it with slugimage. I took my new apex, vmlinuz, and initramfs, replaced the ones in the debian installer with mine, and rebuilt the image with slugimage.
I then flashed the new image onto my NSLU2 with upslug2. When I was done that, I halted apex while it booted, and reset the environment variables to the values that slugimage listed as it built the image.
Now, my NSLU2 seems to continuously load and reload the kernel image. When it gets to loading the initramfs, it stops, goes back, and loads the kernel image again. I can't interrupt the process. What have I done wrong?
Here's the output of slugimage:
$ slugimage -p -b RedBoot -s SysConf -L apex.flash -k vmlinuz-2.6.23-1-ixp4xx -r initrd.img-2.6.23-1-ixp4xx -t Trailer -o slug-image-2.6.23-1
Read 0x00040000 bytes from "RedBoot" into <RedBoot> (2 blocks / 2 blocks)
Read 0x00020000 bytes from "SysConf" into <SysConf> (1 blocks / 1 blocks)
Read 0x00020000 bytes from "apex.flash" into <Loader> (2 blocks / 2 blocks)
Read 0x0013D1BC bytes from "vmlinuz-2.6.23-1-ixp4xx" into <Kernel> (10 blocks / 10 blocks)
Read 0x003593CC bytes from "initrd.img-2.6.23-1-ixp4xx" into <Ramdisk> (27 blocks / 27 blocks)
Read 0x00000010 bytes from "Trailer" into <Trailer> (0x00010 bytes / 0x00010 bytes)
Wrote 2 blocks (0x00000000 to 0x00040000) from <RedBoot> into "slug-image-2.6.23-1"
Wrote 1 blocks (0x00040000 to 0x00060000) from <SysConf> into "slug-image-2.6.23-1"
Wrote 2 blocks (0x00060000 to 0x000A0000) from <Loader> into "slug-image-2.6.23-1"
Wrote 10 blocks (0x000A0000 to 0x001E0000) from <Kernel> into "slug-image-2.6.23-1"
Wrote 48 blocks (0x001E0000 to 0x007E0000) from <Ramdisk> into "slug-image-2.6.23-1"
Wrote 1 blocks (0x007E0000 to 0x00800000) from <FIS directory> into "slug-image-2.6.23-1"
Wrote 0x00010 bytes (0x007FFFF0 to 0x00800000) from <Trailer> into "slug-image-2.6.23-1"
And here's what apex does:
APEX Boot Loader 1.5.6 -- Copyright (c) 2004,2005,2006,2007 Marc Singer
compiled for Debian NSLU2
APEX comes with ABSOLUTELY NO WARRANTY. It is free software and
you are welcome to redistribute it under certain circumstances.
For details, refer to the file COPYING in the program source.
apex => mem:0x00200000+0xb818 (47128 bytes)
env => nor:0x7c000+15k (in-use)
Use the command 'help help' to get started.
# copy -s $kernelsrc $bootaddr
# copy -s fis://kernel 0x000A0000
|
/
-
\
|
1310688 bytes transferred
# copy -s $ramdisksrc $ramdiskaddr
# copy -s fis://ramdisk 0x001E0000
/A
APEX Boot Loader 1.5.6 ...... Lather, rinse, repeat.
Annirak
Reply to: