Well I tried booting the new kernel and got the same error as the other fellow, even though I followed the instructions:
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
Please check your kernel config and/or bootloader.
Any idea what I did wrong?
I found that I had to set mainlineLinux to yes, then reset the plug and set arcNumber before that went away.
Marvell>>setenv mainlineLinux yes
Marvell>>setenv arcNumber 2097
It was something along those lines, I figure that that environment variable is only looked at when uboot starts up.
In my case it resolved that error, but I ran into a couple more before getting the kernel to completely load.
1) The 2.6.30-rc1 kernel changes the nand_mtd of the bootargs to orion_nand
2) The kernel didn't seem to know what filesystem the root was
I fixed both these problems by changing my bootargs to
set bootargs 'console=ttyS0,115200 mtdparts=orion_nand:0x100000@0(uboot)ro,0x300000@0x100000(uImage)ro,0x1fc00000@0x400000(rootfs)rw root=/dev/mtdblock2 rootfstype=jffs2'
After that the kernel loaded up and
debian:~# uname -r
I've yet to verify that the additional features I put in the kernel work, and interestingly I get a warning when I reboot the system:
/proc/misc: No entry for device-mapper found
Is device-mapper driver missing from kernel?
Failure to communicate with kernel device-mapper driver.
I figure I'm missing something since its been a while since I built a kernel from source.