• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1]
Author Topic: latest debian kernel (2.6.32.11) fails to boot  (Read 1835 times)
digininja
Newbie
*

Karma: 0
Posts: 13



View Profile WWW
« on: April 04, 2010, 04:12:31 PM »

I'm following these instructions http://www.openplug.org/plugwiki/index.php/Installing_Debian_To_Flash and am trying to use the 2.6.32.11 kernel from here http://sheeva.with-linux.com/sheeva/ .

When I get to the bootm command I get:
Code:
Marvell>>    bootm 0x0400000 0x0800000
## Booting image at 00400000 ...
   Image Name:   Debian kernel
   Created:      2010-04-04  10:27:18 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1431196 Bytes =  1.4 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 00800000 ...
   Image Name:   debian-installer ramdisk
   Created:      2010-04-04  10:27:18 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    2616636 Bytes =  2.5 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Error: unrecognized/unsupported machine ID (r1 = 0x0000020f).

Available machine support:

ID (hex)        NAME
00000690        Marvell DB-88F6281-BP Development Board
00000691        Marvell RD-88F6192-NAS Development Board
00000692        Marvell RD-88F6281 Reference Board
00000831        Marvell SheevaPlug Reference Board
0000085b        QNAP TS-119/TS-219
000009c6        QNAP TS-41x
00000915        Marvell OpenRD Base Board
00000939        Marvell OpenRD Client Board

Please check your kernel config and/or bootloader.

Reading other mentions of this error it says that their hardware isn't in the list but I'm using a normal SheevaPlug which I assume is the line with ID 831 in the supported list. If not the how can I tell what ID my device has and how can I get it to boot?
Logged

tbm
Full Member
***

Karma: 7
Posts: 121



View Profile WWW
« Reply #1 on: April 05, 2010, 02:25:05 PM »

You have to do this:

Code:
setenv mainlineLinux yes
setenv arcNumber 2097
saveenv
reset
Logged

digininja
Newbie
*

Karma: 0
Posts: 13



View Profile WWW
« Reply #2 on: April 05, 2010, 02:43:39 PM »

I tried it both with and without the reset as the set of instructions above that set in the howto don't include the reset. Both times it failed.

I'll give it another try now and see if it does it again though.
Logged

digininja
Newbie
*

Karma: 0
Posts: 13



View Profile WWW
« Reply #3 on: April 05, 2010, 03:07:47 PM »

OK, worked like a charm. I'm sure I did exactly the same last night but hey, computers aren't the logical things that they are supposed to be and neither are humans at that time in the morning!

I'll see if I can find someone to report the missing reset to to get the wiki updated.

Thanks
Logged

Pages: [1]
Print
Jump to: