On Wed, Jan 17, 2007 at 09:42:09AM -0700, Brad Taylor wrote: > Ken, > > Thanks for the reply > > I'm building for an development board which has a AMCC 440GX. My > bootloader is u-boot not yaboot.
Ah, tricky. Yes, I have fond memories of u-boot, it was one of the better things on that pile of !#*$ known as the AmigaOne. In many ways, you are going to be on your own here, nobody else has this sort of kit. > > I built with ARCH=ppc. I suppose that on your board, that is probably still the correct way to go. The trouble is that things in the kernel easily get broken for ppc. One of the changes which I think is still in progress is the need for the bootloader to simulate OpenFirmware, but I think that only applies on ARCH=powerpc. > > The .config comes from a previously successful kernel build on my > development system. > Normally, I would be reluctant to suggest using a kernel older than the system's headers, because it can lead to exotic breakage which is very hard to detect. But, I think in this case it might be a useful debugging tool _if_ your previous kernel version was fairly recent. That is, try using the 'known good' kernel to see if it boots. If it does, the combination of the newer kernel, current toolchain, 2.6.17 headers, would seem to be the problem. If the previous config was from an old kernel (say, before 2.6.15) it's possible that too much has changed. In that case, you might do better to review an appropriate defconfig from 2.6.17, if there is one. Assuming that changing the command line is not a big issue for you, it might be worth trying to boot with init=/bin/sh first, to see how far it gets in the boot. Oh, and please don't top post, and trim out what is no longer needed in the text you are replying to. Thanks. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce _______________________________________________ Clfs-support mailing list [email protected] http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support
