My immediate guess is path resolution is failing somewhere. Until I get a chance to look, as I used a fresh make menuconfig, I can't say for certain.

The occasional problem here is that it keeps the old paths, so if you directory tree does not match that of the original build machine, this are going to be wonky.

Hi,
I'm trying the same (ie recompile the kernel), but using the .config.old file instead of the .config~. The compile goes OK, but the resulted uImage does not boot.
I load the uImage via TFTP, it works, as the original kernel boots well via TFTP.
I compiled the kernel modules and placed them, also I copied the firmware files into the /lib/modules/.
So where you able to add additional kernel modules to the pogopro kernel?
What was the command line you used?
regards,
Jeno

Thank you for the quick reply. No, I don't have serial connection, I wanted to avoid the HW "work". :-). I modified the uboot variables via blparam, and kept the original kernel on the TFTP server and just moved the kernel images on the server to boot either the one compiled by me, or the original one.
Anyhow, the problem seems to be workarounded. Instead of using the new kernel, I just compiled the modules I need (to use my webcam). Fortunately these new modules load perfectly into the orig kernel, and allow motion to work perfectly. Motion is installed from optware.