This is amazing, but I was looking precisely for the same answer! I've got a 901 EEE-PC (ATOM 32bit) and slack 13.37 64bit in all my computers but this one (which, of course, is now running slack 13.37 32bit). So, seeing this post I decided to go ahead and try cross-compilation. After a few tries, this is how I got my 901 running a trimmed and 'tailor-made' 18.104.22.168 kernel.
IMPORTANT NOTE: this worked in a multilib Slackware 64bit system. It may or may not work on pure Slackware 64 bit systems.
As root (obviously) do
#make menuconfig ARCH=i386
The ARCH=1386 is important . Make sure that in the kernel's configuration menu "Executable file formats / Emulations --->" there is no option "IA32 Emulation (NEW)". This means that everything is OK. You probably know this already, but just go to "General setup --->" and fill something like "eee-pc" in "Local version - append to kernel release". This way the modules tree will not be overwritten in the host machine.
Now do (the -j 8 is optional, just to take advantage of a 4 core CPU)
#make all ARCH=i386 -j 8
#make modules_install ARCH=i386
Then just copy the image (called bzImage) in /usr/src/linux-22.214.171.124/arch/x86/boot/ to somewhere safe (mine goes to the USB Pen directly).
cp /usr/src/linux-126.96.36.199/arch/x86/boot/bzImage /media/USB-DISK
To be sure that the image is a 32bit executable go to /usr/src/linux-188.8.131.52/arch/x86/boot/ and do
The result should look like this (note the 'x86 boot executable')
bzImage: Linux kernel x86 boot executable bzImage, version 184.108.40.206-eeepc (root@calypso) #8 SMP PREEMPT Sun Jul 3 10:33:16, RO-rootFS, root_dev 0x801, swap_dev 0x1, Normal VGA
#tar zcf eee-pc.tgz /lib/modules/220.127.116.11-eeepc/
Copy that to the USB and proceed with the install. I suppose you know what to do on the Notebook!
Mine is now working flawlessly with a costumed 18.104.22.168 kernel cross-compiled ina 64bit machine
Last edited by sairum; 07-03-2011 at 06:07 AM.