Hello.
I have a really strange problem. For weeks, I have been able to create
and download my ramdisk to my PLEB card (running arm linux on an
SA1100) with no problems.
Now, for some reason, I cannot do this any more. When I try to boot the
machine, it passes by the boot prompt and dumps a ton of hex on the
minicom screen. There seems to be some mention of errors with respect to
interrupts.
What does work, however, is if I simply download a pre-made ramdisk. So
my problem must be in how I am creating my ramdisk. Here is what I'm
doing.
First, I take a pre-made ram disk, unzip it and mount it to a point on my
linux machine:
gunzip ramdisk_img.gz | mount -o loop -t ext2 ramdisk /ramd
Then, I add a file or two to it. Now, I want to re-create the ramdisk so
that I can download it:
umount /ramd | cat ramdisk_img | gzip -v9 > ramdisk2.gz
Next, I start minicom, power up my PLEB and get to the blob>
prompt. Here, I type:
download kernel
Then, I switch to 115200 baud and in another window, type:
uuencode zImage zImage > /dev/ttyS0
Note here that zImage is the kernel-file here.
When that is done, I switch back to 9600 baud and type:
download ramdisk
Then, I switch to 115200 baud and in another window, type:
uuencode ramdisk2.gz zImage > /dev/ttyS0
When that is done, I switch back to 9600 baud and type:
boot
Can anyone help me out here? This is where I'm having troubles. Like I
said earlier, this used to work, but now it does not. I can't figure out
how this is different from what I did before. This is the process that I
received from Zsolt Kiraly and he credited Nico Pitre and Phil Blundell
for helping him out.
Any thoughts?
Thanks very much,
Philip Ferguson
MIT
Space Systems Lab
_______________________________________________
http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
