Using own kernel lacks working resume from suspend, any tips?

Timo Jyrinki timo.jyrinki at
Wed Nov 12 17:50:55 CET 2008


Whenever I'd like try my own built kernel, there's one problem: I
can't resume from suspend, ie. the phone becomes seemingly totally
dead so I have to remove battery -> can't use suspend -> not too
exciting to use own kernel.

The _reason_ I'd like to use own kernel is because current "stable"
branch kernel doesn't include the Glamo boost 50MHz -> 80MHz
which really noticeably improves screen updates. It is in all other

My current procedure is the following, can you give me any points to
improve that could affect the issue?

0. (install openmoko-x86_64-20080916-arm-linux-gnueabi-toolchain.tar.bz2)

For the kernel:
1. git clone git:// linux-2.6
2. cd linux-2.6 ; git checkout origin/stable
3. cp arch/arm/configs/gta02-moredrivers-defconfig ./.config
4. git branch my_own_branch
5. ./build
6. dfu-util -a kernel -D uImage.bin -R

For the modules, this is hacky but I don't know a better way at the moment:
7. find | grep "\.ko" | grep -v "\.cmd" | sed 's/$/ /' | tr -d "\n" > mods
8. /usr/local/openmoko/cross/bin/arm-angstrom-linux-gnueabi-strip
--strip-debug `cat mods`
9. tar zcvf new_modules.tar.gz `cat mods`
10. scp new_modules.tar.gz root at
11. On the Neo: cd /lib/modules/2.6.24/ ; tar zxvf ~/new_modules.tar.gz
12. ln -s /lib/modules/2.6.24 /lib/modules/2.6.24-yourrevisionnameetc
13. depmod -a

In 13., if you did the 12. and strip with only --strip-debug like
shown in 8., you don't get any warnings which looks nice.

14. Reboot -> observe the unability to resume from suspend.

Any help welcome, the wiki has scarce information on using an own
kernel to the fullest (including modules).


More information about the support mailing list