#maemo

the maemo5 kernel guide all implies it's part of the kernel source package, but it's not (at least anymore).

Oops, missed a step, it's made with a special make command..

@rambo iirc back in the day there was a compilation option to store the .config within the linux kernel, also also some tool to retrieve it

@rambo Try the kernel sources package in the SDK. It was defconfig arm-rx-51 (or something like that) Or visit the maemo irc channel.

@mace and @tkojo I figured it out already ("oops, missed a step"): it's actaully in the developers guide, but a easy to miss... left a VM in my home desktop to compile, I'll see how it went when I get back...

It seems the instructions on the wiki are "a bit dated" and failed to insmod my iptable_nat.ko ("invalid module format"). Made some educated guesses on what to change and waiting to recompile all modules...

On the same note, any idea how to get the "iptables" binary tool compiled, manipulating the kernel tables without it is going to be painfull...

didn't work, need to think this more tomorrow...

using dpkg-buildpackage seemed to build usable kernel modules, but of course that reset the config to default...

@rambo You might want to make your changes and add it to the other patches under the debian directory.

@ferrix that proved out to be rather complex since the rules file does all kinds of weird stuff, been trying to follow what it exactly does but ...

Figured out how to patch the .config inside the buildroot debian/rules creates. But I really wonder why I get symbol version mismatch even when compiling with dpkg-buildpackage which should set all versions to same as the default kernel.

(I also wonder how is it possible that there are a few symbols missing even when trying to insmod -f nf_conntrack.ko, AFAIUnderstand the missing symbols should be part of netfilter core and thus in the kernel, unless someone optimized things way too far...)

I'm pretty sure I could get all this working in 15 minutes by simply flashing the kernel that dpkg-buildpackage creates, but that would defeat the point of getting NAT working on the stock kernel.