I tried to compile a vanilla 2.6.16 kernel using my previous .15 config and make doesn't build zImage.chrp. Also, the boot images wind up in arch/powerpc/boot instead of arch/ppc/boot/images like before. Just for kicks I tried the plain zImage and it does not boot.

Some of the configs have moved around in .16 but I do have CHRP set in the Platform section.

_________________
--Aaron
Gentoo 2006.1
Kernel-2.6.17-no4

I also have a problem booting 2.6.16-1.2069 in fedora core 4
it just hangs after loading with yaboot
but 2.6.16-1.2054 works fine in fedora core 5

nels

to start with, since 2.6.16, 32bit desktop powerpc (powermacs, ibm chrp and pegasos systems) has moved to ARCH=powerpc, so anything you had under arch/ppc is not supposed to build anymore.

I suppose your problem comes from the fact that the .15 .config was for ARCH=ppc, and thus not all needed options for ARCH=powerpc where reused or something.

A known working .config file for 2.6.16 on pegasos can be found at :
http://www.ppczone.org/downloads/config-2.6.16-pegasos

Hope this helps.

Friendly,

Sven Luther

Sven,

Thanks for the reply. I noticed everything was moved to arch/powerpc/boot and arch/ppc/boot/images is now left empty.

I tried your config, but I still don't get a zImage.chrp file after I compile the kernel: Which image am I supposed to use?

_________________
--Aaron
Gentoo 2006.1
Kernel-2.6.17-no4

Yes, the config Sven provides works fine with gentoo-
sources 2.6.16-r2, but like Aaron I'm stuck with no
zImage.chrp boot-kernel.

The zImage kernel image produced will work fine.

[edit 19:05]

Sorry about being slightly off topic with 2.6.15:
I tried the linux-pegasos-debian-2.6.15.6.tar.bz2 kernel
from http://www.ppckernel.org/specialized.php on my
Debian. After booting I ended with a non-working PS2- keyboard. USB-Keyboard works however.

But Sound-driver is broken and throws many
unknown_symbols on boot. Could be cauesd by
missing configuration however?

Then I tested 2.6.16-9 from sid. This one boots
into garbled characters directly after kernel-load.

If someone could recommend a working kernel-image for
Debian, this would be highly appreciated. I used
2.6.8 before, but some very strange instabilities
when using DVD-ROM force me to upgrade.

In 2.4 times updating and building kernels really was
much less of a hassle.


Regards,
Peter

Hi Peter ...

The linux-image-2.6.15-1-powerpc kernel currently in etch/testing should work without problems.

The 2.6.16 kernel is particular, because we went through the ARCH=ppc to ARCH=powerpc migration, and this caused some trouble in debian's mkvmlinuz implementation, which need some work. I have been actively working on this since the last two weeks, but interspaced with other (firmware mostly) work. Please expect a resolution to this in the next few weeks.

That said, the debian 2.6.16 kernel will not be moved to testing unless this is fixed, which is the reason for debian's two-stage devel archive. Unstable/sid can possibly be broken, but testing/etch should be almost always in a releasable state.

So, don't worry, things are under control, they just need a bit more work right now.

Friendly,

Sven Luther

Hello Sven,

thanks a lot for those hints! 2.6.15-1-powerpc/testing
boots fine so far.

Only 2 problems, that I had also with the kernel from
ppckernel.org, remain:

My PS2-keyboard ist not found, I have to use it on USB.
And more of a problem: Sound hardware is not initialized:

snd_timer: Unknown symbol snd_info_register
[...]
snd_pcm: Unknown symbol snd_info_register
[...]
snd_ac97_codec: Unknown symbol snd_info_register
[...]

you need to load the atkbd and i8042 modules. They should be included by your ramdisk generator, if they are not, please file a bug report.

Maybe psmouse also if you have a ps2 mouse too.
Mmm, you are missing some sound/alsa stuff. I don't know which one, last i tried a clean install, sound worked out of the box for me, so maybe try dpkg-reconfiguring the alsa stuff.

Friendly,

Sven Luther[/quote]

Hi Sven,
Thank you again. Invoking alsaconf fixed it.

Adding atkbd and i8042 to /etc/modules helped too.


Many regards,
Peter