Re: 2.6.5-pre* does not boot on my PReP PPC

From: Christian Kujau
Date: Mon Apr 05 2004 - 16:41:56 EST


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

[ if someone is bored from me cc'ing too many - plz cry! ]

Tom Rini wrote:
| OK, hmm. I've got some better ideas then. It sounds like the code to
| have puts show up on VGA isn't selected/compiled in. Or, there's still
| some other problem wrt the OF transition code. Just having a serial
| console selected still doesn't give output however, right?

I'll give it a try with 2.6 this week.

|
|>another issue here: i was finally able to cross-compile 2.5.x / 2.6.x
|>kernels (on x86). i tried to compile kernels from 2.5.21 on with
|>"allnoconfig" (was introduced in 2.5.21). only 2.5.30 can be built, all
|>other attempts to build "zImage" fail...(still compiling 2.5.6x)...
|>(full logs of builds available...)
|
| The simple answer is, don't use allnoconfig :). Do a 'make
| common_defconfig' and then from there turn off stuff you don't need.

um, yes. but the target "common_defconfig" was disabled somewhere in
2.5, so my shini script broke. i wanted to do common_defconfig first,
then always keep my .config and do "oldconfig" after patching, but
somehow my script broke, so i went with "allnoconfig"...but ok, i'll try
again.

if anyone is interested: http://nerdbynature.de/bits/sheep/build/
all the logfiles produced when patchin/compiling 2.5.21 up to 2.5.75.


right here the latest 2.4-benh and 2.6-benh kernels (via rsync), also
compiled via crosscompile: http://nerdbynature.de/bits/sheep/latest-kernel/

thanks,
Christian.
- --
BOFH excuse #212:

Of course it doesn't work. We've performed a software upgrade.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFAcc1Q+A7rjkF8z0wRAtxBAKCrbpGe3/HlW8UMLAdFKHCnWiyB/QCfV4FC
hVoNM7pW01ntTdFBETVxT44=
=jCF2
-----END PGP SIGNATURE-----
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/