[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Yet another magic word problem


I have a problem which materialize as 'Bad Magic Number' during boot.

I have installed Debian Squeeze on my Sheevaplug by following Martin
Michlmayr's great howto. I put uImage and uInitrd on a USB dongle and
booted. When I reached the partioner I asked it to install on my 2 GB
SD card. I configured it to have boot partion and a main partion.

During the installation the installer complained about two things:
1. It couldn't make the system bootable. I was asked to boot using /vmlinuz
I thought that I would solve manually later by following the steps in the howto.

2. It couldn't retrieve a proper os-udep (or something like that)
I continued as I don't know what os-udep is. I know this is in
principle bad but thought that I could investigate it later.

The boot partion contain:
-rw-r--r-- 1 root root   84904 2010-03-01 03:32 config-2.6.32-3-kirkwood
lrwxrwxrwx 1 root root      28 2010-05-25 23:31 initrd.img ->
-rw-r--r-- 1 root root 5428259 2010-05-25 23:31 initrd.img-2.6.32-3-kirkwood
drwxr-xr-x 2 root root   12288 2010-05-25 21:53 lost+found
-rw-r--r-- 1 root root  999932 2010-03-01 03:32 System.map-2.6.32-3-kirkwood
lrwxrwxrwx 1 root root      25 2010-05-25 23:31 vmlinuz ->
-rw-r--r-- 1 root root 1431196 2010-03-01 03:29 vmlinuz-2.6.32-3-kirkwood

'/boot' on the main partion is empty.

When I reached the
setenv bootargs_console console=ttyS0,115200
setenv bootcmd_mmc 'mmcinit; ext2load mmc 0:1 0x01100000 /......

in the howto I thought that because I couldn't neither uImage nor
uInitrd I thought that initrd.img and vmlinuz probably was the ones I
should use instead. However, using these leads to the Bad Magic

Therefore: Where can I find uImage nor uInitrd if they are not on the
boot partion and not in /boot ?

Could I use the ones which I used for the installation procedure ?

Best regards

Esben Rugbjerg
Guldborgvej 44, 3.th.
2000 Frederiksberg
email: esbenrugbjerg@gmail.com
mobil-tlf.: +45 28715166

Reply to: