Looks, I have similar problem!
When using the procedure, described by Denis:
- Download the linux_2.6.35.orig.tar.gz and linux_2.6.35-34.2.diff.gz;
- Unpacking both, cd linux-2.6.35;
- Applying the patch as patch -p1 < ../linux_2.6.35-34.2.diff
- cp debian/config/i386/config.fitpc2 .config
and than do:
make oldconfig
the build asks a lot of configuration questions, like:
Xen guest support (XEN) [N/y/?] (NEW) n
IBM Calgary IOMMU support (CALGARY_IOMMU) [N/y/?] (NEW) n
AMD IOMMU support (AMD_IOMMU) [N/y/?] (NEW) n
... and so on.
At the end, there is
a lot of differences between the original
config.fitpc2 and the new
.config, created by this procedure.
Diff between the both files attached.
Plain
make asks the same questions exactly. Looks as it executes make oldconfig internally.
All this looks as the config.fitpc2 is not fit the kernel

. AFAIK, all these messages, finished with
(NEW) means that the relevant parameters are not configured in the
config.fitpc2.
Can I get the kernel and the config which are compatible?
P.S.
I build the kernel not on the fitpc itself, but on my development machine, which is (naturally) more advanced.
uname -a on it shows:
Linux ilia-Linux 3.2.0-26-generic #41-Ubuntu SMP Thu Jun 14 17:49:24 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
Can the kernel cross-compilation be done? If yes, how?
Thanks.
Ilia.