Develop Bugs

[Dev] Building a 2.6.29 kernel for the Hero

Hello,
I would like to build a 2.6.29 kernel for Hero for us to run properly Donut roms.
Here is my progress so far:
- I have sync the android kernel msm from git.
# git clone git://android.git.kernel.org/kernel/msm.git
# cd msm
# git checkout --track -b android-msm-2.6.29 origin/android-msm-2.6.27
- then:
# adb pull config.gz ./
# gunzip config.gz && mv config .config
# make PATH=$PATH:android-1.6_r1/prebuilt/linux-x86/toolchain/arm-eabi-4.2.1/bin ARCH=arm SUBARCH=arm CROSS_COMPILE=arm-eabi-
But no luck: it asks me questions to configure the kernel (error in .config?)
I have attached some useful files.

Try running make menuconfig and manually load the .config file. What happens?

kernel sources for hero is not available on http://developer.htc.com/ then no hero support in android.git.kernel.org/kernel/msm.git

Z!L0G80 said:
kernel sources for hero is not available on http://developer.htc.com/ then no hero support in android.git.kernel.org/kernel/msm.git
Click to expand...
Click to collapse
Well this guy did it here for sapphire before Htc released kernel sources.... So I think we can.
erikwt said:
Try running make menuconfig and manually load the .config file. What happens?
Click to expand...
Click to collapse
I copied the hero .config file to kernel root, then "make menuconfig" and loaded .config, then exit and yes to "write .config" question.
Make failed, output attached (make1.txt)
I then applied TigerTael sapphire patch as he "tends to think the memory locations may be correct". Tried to manually load hero's .config and got attached error (error.txt)
I then "make msm_defconfig" and could compile a kernel witch I added to ADP-1.6 boot.img. But no luck it does not work and adb logcat waits for device.... while I am waiting for advices
Regards

Was the downloaded config copied from a build of the same kernel version? If not do "make oldconfig" before commencing with "make menuconfig" or other build.

phel21 said:
Was the downloaded config copied from a build of the same kernel version? If not do "make oldconfig" before commencing with "make menuconfig" or other build.
Click to expand...
Click to collapse
'make oldconfig' asks me the questions to configure the kernel.....
Edit:
If that could help:
cat /proc/iomem
00700000-0079afff : msm_panel.1
007a0000-007bffff : ram_console
19200000-257fffff : System RAM
19223000-19513fff : Kernel text
19514000-195ebf7f : Kernel data
a0200000-a0200fff : msm_serial_hs.0
a0400000-a0400fff : msm_sdcc.1
a0500000-a0500fff : msm_sdcc.2
a0800000-a0800fff : msm_hsusb
a9900000-a9900fff : msm_i2c.0
a9900000-a9900fff : msm_i2c
a9c00000-a9c00fff : msm_serial.2
a9c00000-a9c00fff : msm_serial
aa200000-aa2effff : mdp
aa600000-aa600fff : msm_mddi.0

Yes. It will ask you questions as the kernel has added new capabilities - which you will need to configure. Use the help for the new options to guide your choices, although usually the default is the best way to go. Not doing "oldconfig" step will leave you with a busted build configuration.

I assume you're using the config options from /proc/config.gz on the phone?

CombinedEffort said:
I assume you're using the config options from /proc/config.gz on the phone?
Click to expand...
Click to collapse
of course I do

gecka said:
of course I do
Click to expand...
Click to collapse
Godspeed! (sorry, i cannot contribute anything as I am a total noob, but I'll read your progress regardless!)
(edit: i could beta test though..^_^)

http://forum.xda-developers.com/showpost.php?p=4737995&postcount=37
maybe this could be of any help?

E2K said:
http://forum.xda-developers.com/showpost.php?p=4737995&postcount=37
maybe this could be of any help?
Click to expand...
Click to collapse
please read first post

Now that kernel sources are out, it is time to port changes to 2.6.29.

Hey guys what would be the best? Apply HTC Hero kernel changes to 2.6.29 or apply 2.6.29 changes from 2.6.27 to hero kernel ?
I have applied HTC changes (3.4Mo patch!) to android2.6.29msm and I can compile it. When I run it it says it is a 2.6.27-dirty kernel... Why dirty ?

Lox, it probably means that some of your kernel changes from 2.6.27? or coded for 2.6.27 are not valid in the newer build, hence the 'dirty' reference.
Dirty here meaning spoilt or wrong.
I don't code, and i don't know exactly how much experience you have yourself, but do you reckon Cyanogen or maybe Drizzy could help some of you Hero ROM chefs out with some tips? I'm sure they'd love to give some pointers as to how they've gone about cooking on the Sapphire and Magic.

maybe you did a dirty trick

Lox_Dev said:
Hey guys what would be the best? Apply HTC Hero kernel changes to 2.6.29 or apply 2.6.29 changes from 2.6.27 to hero kernel ?
I have applied HTC changes (3.4Mo patch!) to android2.6.29msm and I can compile it. When I run it it says it is a 2.6.27-dirty kernel... Why dirty ?
Click to expand...
Click to collapse
You can get dirty tagged when you change owner of the files compared to the user who pulled them from git.

packetlss said:
You can get dirty tagged when you change owner of the files compared to the user who pulled them from git.
Click to expand...
Click to collapse
Well I understand that but I don't understand why it is not 2.6.29 ?
I have done:
git checkout --track -b android-msm-2.6.29 origin/android-msm-2.6.27

Why start with 2.6.29 and not the latest stable kernel (2.6.31.x) now that HTC-patches just have been released. According to the changelogs there's quite a few interesting android-specific improvements in those later revisions.
Is the intention to match kernel version for android 1.6 source? I'd expect generic android kernel-enhancements to be integrated into the kernel.org kernel. In that case it should be fairly easy to use a more recent kernel than that included in an official android release.

Lox, is this a dead project? Are you focusing on your optimized .27 kernel for our devices?

[02 Nov][RECOVERY][NAND|SD][cLK|MAGLDR] ClockworkMod Recovery 5.0.2.6 "YES/NO" STABLE

Hi, folks
ClockworkMod Recovery (<- source).
"Changelog of ClockworkMod Recovery"
changes are here for some of the work we have done for support in RM
https://github.com/arif-ali/cLK
https://github.com/CyanogenMod/android_device_htc_leo
changes for the yes/no patch, and anything provided in this thread are here
https://github.com/arif-ali/android_bootable_recovery
https://github.com/arif-ali/android_device_htc_leo
If you cannot wait for new builds, then Arifs nightly builds are available here.
Features:
Based on 5.0.2.6 sources
Re-coded recovery and leo gits in few places to have the same CWR working for both MAGLDR and cLK
Fixed cLK with versioning in cLK to add clk=1.4.0.1 to /proc/cmdline
Now require cLK 1.4.0.1, rather than the 1.4 from cedesmith
Compiled using official Offmode-Charging Fix by Koush
Edited confirmation menu to show one "no" only
Re-arranged YES / NO: YES now is on first place
ReiserFS and NILFS Support
Offmode-Charging with cLK ONLY
SD-EXT backup / restore (no matter if Reiser, NILFS, ext 2/3/4)
You can flash this image easily from within Android; simply copy the file onto your sdcard and run following commands:
Code:
$ su
# flash_image recovery /sdcard/name_of_recovery_file.img
Maybe the flash_image command is not available on your build; you can find it attached. Copy it into /system/bin folder and run following in terminal emulator:
Code:
$ su
# chmod 777 /system/bin/flash_image
For cLK:
You need android sdk installed and path variable set in windoze to "*androidsdk*/platform-tools" and "*androidsdk*/tools" (alternatively you can copy the .img into the tools folder of android sdk and operate from there)
Flash appropiate cLK 1.4.0.1 layout from second post
Download the file attached
Boot your phone into fastboot mode (hold back key (left arrow) whilst powering on)
Open a command line by pressing "windoze key+r" and typing "cmd", followed by enter
Navigate to folder, which contains the recovery image
Type "fastboot erase recovery" (<- not really necessary; just to make sure), followed by enter
Type "fastboot flash recovery name_of_recovery_file.img", followed by enter
Type "fastboot reboot" for rebooting your phone
Access recovery as described in cedesmiths thread (hold home key whilst powering on)
You're done
Click to expand...
Click to collapse
For MAGLDR 1.13, booting from NAND:
Download the file attached
Download a partition layout incl. recovery from this thread which fits your ROM you want to use best and unzip it into "C:\recovery" for example
Copy over the recovery image file from inside the zip archive into this folder "C:\recovery", delete existing "recovery-raw.img" and rename copied image file to "recovery-raw.img"
Flash the recovery and partition layout using "DAF.exe" as usual and described in the thread of raiderx or the ROM provider
Boot Recovery with menu point "8. AD Recovery"
You're done
Note: For future updates of CWR it's best to set up a fixed boot partition size of 5M and not use the filesize flag in flash.cfg.
[/list]
Click to expand...
Click to collapse
For MAGLDR up to 1.13, booting from SDCard (SD-files version):
Download the file attached
Extract the files to the root directory of your sdcard
Start recovery within MAGLDR with menu point "AD SD"
Recovery should start
You're done
Click to expand...
Click to collapse
For both via CWR:
Download the *_CWR.zip file onto sdcard
Go into recovery by either holding home key in cLK or using the 8. AD to recovery in MAGLDR
Note: recovery-partition size of minimum 5MB needed
Select Install zip from sdcard
Select Choose zip from sdcard
Navigate/Select the recovery from the sdcard
Select yes to install the recovery
reboot into recovery, and hooray, you are in the new recovery
Click to expand...
Click to collapse

August 7, 2011
Newest sources 4.0.1.4
June 10, 2011
4.0.0.0 sources
Changelog of recovery:
- added the efs partition to the do not format list
- also fix up the /sdcard symlink on startup
- tar nandroid and /data/media support
June 8, 2011
3.2.0.1 sources
Changelog of recovery:
- Rename format_ignore_partitions to a forbid_format
- Fix 6 extentedcommands declaration warnings
June 3, 2011
3.2.0.0 sources
Added changes necessary for compiling "one recovery for all"
ClockworkmodRecovery now works for MAGLDR and cLK, no extra recovery for each loader
Added new cLK 1.4.0.1 partition layouts as attachment
Arif is continuing this for unknown time: thank you very much, Arif
April 18, 2011
3.0.2.4 sources; renamed to 3.0.2.5
Compiled with Koush's Offmode Charging fix
Attention: Filesize is ~ 1MB bigger than previous version due to new Offmode Charge Fix (i believe); it still fits into 5MB Recovery Partition Size
SD Version is only working if power or USB is plugged in -.- Working 3.0.2.4 Version here
April 13, 2011
Updated to newer 3.0.2.4 sources; see "changelog" link in first post
Full support for REISERFS & NILFS filesystems
cLK and MAGLDR will follow
Added zip file containing cedesmith's offmodecharging and my edits as "patch" (diff) file
Added another flash-method and attached the binary which is necessary
March 29, 2011
Added some cLK_1.4_partition layouts; attached on this post
Normal Cache-size Version (usable for most cases):
boot 5M
cache 44MB
recovery 5MB
misc 1MB
system 80-160MB in 10MB steps, 180-400 in 20MB steps
userdata = rest of available NAND
Small Cache-size Version (requires initrd.gz which links /cache to userdata partition):
boot 5M
cache 5MB
recovery 5MB
misc 1MB
system 80-160MB in 10MB steps, 180-400 in 20MB steps
userdata = rest of available NAND
stirkac made an exe installer with these layouts; it installs cLK and the desired layout automatically. You can find it here. Thank him
March 25, 2011
Updated to 3.0.2.4 sources
March 17, 2011
Updated to 3.0.1.9 sources
cLK was updated to latest patches from cedesmith incl. complete offmode charging support (LED color changing, button press behaviour etc)
March 15, 2011
Backup'n Restore does what it is intended to
cLK is running well and was updated to latest patches from cedesmith
MAGLDR is running well if restored backups are from same version
March 14, 2011
Second run, needs testing by MAGLDR users regarding full restore (mainly: Boot partition!)
cLK is running well
March 10, 2011
Initial release, 3.0.1.4, English only
Bug with MAGLDR; removed
Notes:
- Backups from a previous version can't be restored with this one. However, backups from this version are fully working.
- Offmode charging is only possible with cLK; MAGLDR up to 1.13 isn't capable about that at this time, maybe in future releases.
- MAGLDR Versions are untested by me, here i'll need your feedback, especially regarding restorings from earlier versions (e.g 3.0.1.4 backup restored in 3.0.1.9 = working or not).
CWM "ChangeLog", but w/o Version No.

Awesome. Only thing we really need now is a change log between different CWM versions as they come out.
PS>> Gave you an extra post in case you need it later.

hmm, i'll look around if an official changelog already exists, otherwise i have to figure this out and write for myself, yes.
and thx for extra post

Hard to find an actual version history... All I found was ROM Manager's version history:
http://gh-pages.clockworkmod.com/ROMManagerManifest/CHANGELOG.txt

Nice Work ..
Cool.. Will Save On The Poor Vol Down Key!
Nice Work ..

Cool nice job well done...

seadersn said:
hi, folks
after testing this out i've decided to make it public: my compiled and edited version of ClockworkMod Recovery.
download from multiupload.com
features:
based on newest 3.0.1.4
edited confirmation menu to show one "no" only
edited title to show "S.ClockworkMod Recovery 3.0.1.4" (for determination)
SD-EXT backup / restore incl.
this one is usable for both cLK & MAGLDR.
instructions:
this thread / recovery will be updated every 2-4 weeks, if new recovery is available.
have fun!
Click to expand...
Click to collapse
wooow~try it right now ! thank you!!

@ karendar: thx for looking too. but it seems, there isn't one available, not even in the sources... maybe @ forum, but haven't found sth until now.

EDIT
It works! : D
No more "No's": D
And the function "PowerOff" is rly nice
@seadersn,
kommt das auch auf Handy-FAQ?
Thnx
Greetings.

xD hab ich's mir doch gedacht jap, wird's voraussichtlich in den nächsten drei stunden.
jep, it will

Freu mich schon
Könntest du die ganze Recovery übersetzen [E-D]?
Oder ist das unmöglich?
Could you translate the whole recovery?
Or is that impossible?

nope, this isn't impossible; but this is really too much for me atm maybe in about a week, german only.

We can wait
You have so much time
Thnx.
Greetings.

seadersn said:
hi, folks
after testing this out i've decided to make it public: my compiled and edited version of ClockworkMod Recovery (<- source).
download from multiupload.com
features:
based on newest 3.0.1.4
edited confirmation menu to show one "no" only
edited title to show "S.ClockworkMod Recovery 3.0.1.4" (for determination)
SD-EXT backup / restore incl.
this one is usable for both cLK & MAGLDR.
Click to expand...
Click to collapse
BEAUTIFUL!
Can this be used with MAGLDR 1.11!?!?
If yes can you please provide me with the kernel and initrd to replace the existing ones on SDcard!?
Thx

seadersn said:
hi, folks
after testing this out i've decided to make it public: my compiled and edited version of ClockworkMod Recovery (<- source).
download from multiupload.com
features:
based on newest 3.0.1.4
edited confirmation menu to show one "no" only
edited title to show "S.ClockworkMod Recovery 3.0.1.4" (for determination)
SD-EXT backup / restore incl.
this one is usable for both cLK & MAGLDR.
instructions:
this thread / recovery will be updated every 2-4 weeks, if new recovery is available.
have fun!
Click to expand...
Click to collapse
Any chance you can add reiserfs and btrfs support when making a Nandroid Backup and Restore?

https://github.com/CyanogenMod/android_bootable_recovery#
Here's the original Github for the Gingerbread Clockwork recovery... I haven't programmed in so long I don't think I'm of any help with this.
Pongster, I'm digging through gits to see if anyone had this implemented already in a modded version.

hi,
thx for the github link; anyway i've already added it to the first post unfortunately a changelog or sth similar isn't arising from the sources but thx, again.
regarding reiser+btr: i don't know this much of programming, what i did was an (easy) change of existing code, but if it's already present in the source code and one only needs the mount points, this is no problem, i believe
i can have a further, deeper look into that, but it would take a while if it's not present and i have to change the code and i will definitively need help. no assurance about that
regarding magldr 1.11: life engineer, i will pm you a version for testing. maybe tomorrow morning, GMT+1?
@ spyros, from where do you know that i have plenty of time, he?

seadersn said:
hi,
thx for the github link; anyway i've already added it to the first post unfortunately a changelog or sth similar isn't arising from the sources but thx, again.
regarding reiser+btr: i don't know this much of programming, what i did was an (easy) change of existing code, but if it's already present in the source code and one only needs the mount points, this is no problem, i believe
i can have a further, deeper look into that, but it would take a while if it's not present and i have to change the code and i will definitively need help. no assurance about that
regarding magldr 1.11: life engineer, i will pm you a version for testing. maybe tomorrow morning, GMT+1?
@ spyros, from where do you know that i have plenty of time, he?
Click to expand...
Click to collapse
hey seadersn,
I have been looking at the compilation of recovery as well, and a thought about drivers came about. Which kernel are you using are using the same one in device/htc/leo, or the one compiled by cedesmith. I think in order to get the reiserfs or btrfs, then all we need to do is compile our own kernel with the mods, and put it in the right place and it should work.
I will give it a test with my kernel this evening
with respect to the initrd and zImage, that's easy to get, You need the following 2 files
out/target/product/leo/kernel
out/target/product/leo/ramdisk-recovery.img
but again this needs testing, unless someone else can confirm this

seadersn said:
hi,
thx for the github link; anyway i've already added it to the first post unfortunately a changelog or sth similar isn't arising from the sources but thx, again.
regarding reiser+btr: i don't know this much of programming, what i did was an (easy) change of existing code, but if it's already present in the source code and one only needs the mount points, this is no problem, i believe
i can have a further, deeper look into that, but it would take a while if it's not present and i have to change the code and i will definitively need help. no assurance about that
Click to expand...
Click to collapse
seadersn, check this out: Post from the desire forums... Looks like ReiserFS might be supported in Clockwork directly. Just need to edit .config:
http://forum.xda-developers.com/showpost.php?p=10488102&postcount=432
Alot of the kernels already have ReiserFS and btrfs, I believe...

[24.APR.2011][KERNEL] AA 0.6 OC [ext2/3/4,cifs,reiserfs,btrfs,nilfs,utf8][MAGLDR/cLK]

Use at your own risk, overclock at your own risk - I'm not responsible for damage to your device​
The kernel used in this ROM is based on MDJ S9.2, and have ported it, and have patched to the latest upstream with the relevant fixes
The git is available here, check logs and diffs for the changes made. There is a neat build script to get it compiled for yourself if you want as well in Linux or cygwin. I am using the test branch at the moment.
Howto cLK (kernel_aa_X.X.zip)
Click to expand...
Click to collapse
Download kernel
Unzip archive
run script.sh (linux) or script.bat (windows) to copy over the kernel modules to your phone (make sure adb is in your path)
grab the initrd.gz from your current rom
then, either
reboot phone into fastboot by holding the back key
run "fastboot -c "" -b 0x11800000 flash:raw boot zImage initrd.gz"
or
make boot.img by using "mkbootimg --kernel zImage --ramdisk initrd.gz --cmdline "console=null" --base 0x11800000 -o boot.img"
adb push boot.img /sdcard/
adb shell flash_image boot /sdcard/boot.img
reboot your phone
Howto MAGLDR CWM (kernel_aa_X.X.zip) & Howto cLK (kernel_aa_X.X_clk_ppp.zip)
Click to expand...
Click to collapse
Download kernel
copy archive onto the FAT partition of your SD card
reboot phone into CWM
Select Install zip from sdcard
Select choose zip from sdcard
Select the kernel from the SD
Select Yes to install the zip
reboot your phone
Differences between kernel_aa_X.X.zip and kernel_aa_X.X_clk_ppp.zip
Click to expand...
Click to collapse
my initrd (so has boot.img which will only work with cLK)
Added ppp specific stuff
Added 02recov, which allows to get ROM Manager working (works for me)
NOTE: The initrd may or may not work for everyone please report your problems with dmesg and logcat files
Thanks/credits
Click to expand...
Click to collapse
m-deejay
Cotulla (MAGLDR)
RaiderX303 (ClockworkMod)
cedesmith (cLK)
#htc-linux and #htc-linux-chat
All ROM users

Changelog
v0.6 (24/04/2011)
Add reiserfs support
Add NILFS support
Add btrfs support
v0.5 (21/03/2011)
Removed SMARTASS
Merged with master git
v0.4 (18/03/2011)
kernel patch to save reboot reason so is available on bootloader (credits to cedesmith)
v0.3 (01/03/2011)
Add back PPP support (to work with cLK)
Add cLK patches (credits to cedesmith)
more MDJ stuff config
v0.2 (14/02/2011)
re-cloned MDJ S9.2
Created branch test
Removed squashfs
Removed unnecessary PPP
Merged with master git
v0.1 (12/02/2011)
cloned MDJ S9.2
merged with master git
Previous Changelog from MDJ
Code:
S9.2:
- fixed wifi mac addresses ( http://www.gitorious.com/linux-on-wince-htc/linux_on_wince_htc/commit/4c31f2fb265ae68b82ed5e8ea4bec91208837011 )
S9.1:
- Initial Release

reserved another

Trying now
Sent from my HTC HD2 using XDA Premium App

Nice, thanks.....if i'm not wrong Mdj's kernel wasnt UV, right?

is it UV? afaik no
af974 said:
Nice, thanks.....if i'm not wrong Mdj's kernel wasnt UV, right?
Click to expand...
Click to collapse
afaik, it is not UV, I cannot see it in his changelogs

updated kernel see OP, changelog and git logs for details

Thanks so much. It's said that MDJ's kernel is extraordinary power-saving and low battery drainage. We have not seen Mr MDJ on the forum for quite a long time. We just hope you great guys to carry on the goodness of MDJ's kernel.

about time someone made a proper kernel for cLk ..thanks arif-ali

arif-ali said:
Use at your own risk, overclock at your own risk - I'm not responsible for damage to your device​
The kernel used in this ROM is based on MDJ S9.2, and have ported it, and have patched to the latest upstream with the relevant fixes
The git is available here, check logs and diffs for the changes made. There is a neat build script to get it compiled for yourself if you want as well in Linux or cygwin. I am using the test branch at the moment.
Download kernel
Unzip archive
run script.sh (linux) or script.bat (windows) to copy over the kernel modules to your phone (make sure adb is in your path)
grab the initrd.gz from your current rom
then, either
reboot phone into fastboot by holding the back key
run "fastboot -c "" -b 0x11800000 flash:raw boot zImage initrd.gz"
or
make boot.img by using "mkbootimg --kernel zImage --ramdisk initrd.gz --cmdline "console=null" --base 0x11800000 -o boot.img"
adb push boot.img /sdcard/
adb shell flash_image boot /sdcard/boot.img
reboot your phone
Download kernel
copy archive onto the FAT partition of your SD card
reboot phone into CWM
Select Install zip from sdcard
Select choose zip from sdcard
Select the kernel from the SD
Select Yes to install the zip
reboot your phone
my initrd (so has boot.img which will only work with cLK)
Added ppp specific stuff
Added 02recov, which allows to get ROM Manager working (works for me)
NOTE: The initrd may or may not work for everyone please report your problems with dmesg and logcat files
m-deejay
Cotulla (MAGLDR)
RaiderX303 (ClockworkMod)
cedesmith (cLK)
#htc-linux and #htc-linux-chat
All ROM users
Click to expand...
Click to collapse
Can you please make a cLK CWM Kernel of your to use with Typhoons build...
I have tried it this way and is not working and I think that the file structure for Typhoon builds is different that common build.
I would like to try this kernel. Is it possible plz?

zach.antre said:
Can you please make a cLK CWM Kernel of your to use with Typhoons build...
I have tried it this way and is not working and I think that the file structure for Typhoon builds is different that common build.
I would like to try this kernel. Is it possible plz?
Click to expand...
Click to collapse
what problems are you getting, any logcats or dmesg output

arif-ali said:
what problems are you getting, any logcats or dmesg output
Click to expand...
Click to collapse
it was stuck in bootscreen, i will try to send later.
Till then you can check the GL_Core kernel thread that had same issue
he made a Kernel for Typhoon builds and a kernel for all others.
you can see the differencies

arif-ali said:
what problems are you getting, any logcats or dmesg output
Click to expand...
Click to collapse
here is the logcat

@zach.antre
I have added the 0.5 kernel with wpa in OP, This is the only difference I see between my kernel and the GL kernel.
I haven't tested it, so not sure if it will work.
If you do test it, let me know how it goes.
thanks

arif-ali said:
@zach.antre
I have added the 0.5 kernel with wpa in OP, This is the only difference I see between my kernel and the GL kernel.
I haven't tested it, so not sure if it will work.
If you do test it, let me know how it goes.
thanks
Click to expand...
Click to collapse
I'll test it know, give 5 minutes and i'll report back
------------------EDIT---------------------------
After testing your kernel again i get the same issues.
System will not start, it is stuck in bootscreen.
You will find attached the logcat
I should mention that TyphooNs build is nonSense, it is CM7

Not many use this, but hey, might as well release it
updated kernel to
* Add reiserfs support
* Add NILFS support
* Add btrfs support

arif-ali said:
Not many use this, but hey, might as well release it
updated kernel to
* Add reiserfs support
* Add NILFS support
* Add btrfs support
Click to expand...
Click to collapse
Hey Arif, what exactly is reiserfs, nilfs, btrfs?

mattfmartin said:
Hey Arif, what exactly is reiserfs, nilfs, btrfs?
Click to expand...
Click to collapse
they are all file systems, similar to ext2/3/4, but some people prefer these instead
plus this is the basis for the recovery kernel as well that is available on RM, so more I can support, the better

arif-ali said:
Not many use this, but hey, might as well release it
updated kernel to
* Add reiserfs support
* Add NILFS support
* Add btrfs support
Click to expand...
Click to collapse
Hi Arif, thanks for all the good work!
1) Does this kernel work for GB, or only Froyo?
2) Does cLK version incorporate any of the new ppp wrapper stuff discussed in cedesmith's thread?
Thanks!

lukedunk said:
Hi Arif, thanks for all the good work!
1) Does this kernel work for GB, or only Froyo?
2) Does cLK version incorporate any of the new ppp wrapper stuff discussed in cedesmith's thread?
Thanks!
Click to expand...
Click to collapse
1a) personally, haven't tested this in GB, so not sure. zach.antre tested it with one of the GB roms, and didn't quite work. I still need to do some testing, to see exactly what is different to make it work. (but you can still test if you want the challenge)
1b) This kernel is used as a basis for CWR that is on RM, so the fact it works there, and the basis there is GB, I would have thought that it would work with GB, but I could be wrong
2) No, as the wrapper is still beta at the moment (and several people are still having problems). Once we know that is working effectively with no problems, I will have no problems in adding it in.

NST-Kernel v0.1 USB-Host and Multitouch enabled (for software versions 1.1 and 1.1.2)

Hi,
after the great work from verygreen, wheilitjohnny and arkusuma I decided to build a kernel with both of their improvements included.
Features:
based on the BN kernel for the software versions 1.1 and 1.1.2
USB-Host by verygreen http://forum.xda-developers.com/showthread.php?t=1457971
Multitouch by wheilitjohnny and improved by arkusuma http://forum.xda-developers.com/showthread.php?t=1563645
Additional USB related drivers (usb-storage, usb-serial ...)
This is just the kernel, you still need to perform additional steps to get this features working, please look into the corresponding threads.
Howto install the kernel:
Download the file with the kernel and extract it, you should get a file called UImage
Use Noogie or adb to replace the uImage on the /boot partition
Reboot
DISCLAMER and WARNING:
I'm not responsible for bricked devices, dead SD cards, lost data, fried USB-Devices. Make a backup before you try anything described here!
USB-Host support is still WIP (work in progress), the battery drain is noticeable higher. If you don't plan on using the USB-devices you should use a kernel without USB-Host support.
Downloads:
NST-Kenel_v0.1_uImage.zip
github repository for the sourcecode
Thanks to:
verygreen for the USB-Host support
wheilitjohnny for the initial Multitouch support
arkusuma for the improvements to the multitouch support
Renate NST for testing

Great work! Thanks mali100!
by the way, this is the kernel for 1.1, right?
just better state that avoid asking XD
P.S.: I didn't look at the kernel for previous versions, is the kernel actually changed?

wheilitjohnny said:
Great work! Thanks mali100!
by the way, this is the kernel for 1.1, right?
just better state that avoid asking XD
Click to expand...
Click to collapse
Thanks, totally forgot to mention this. It is for 1.1 and 1.1.2
P.S.: I didn't look at the kernel for previous versions, is the kernel actually changed?
Click to expand...
Click to collapse
The kernel changed from 1.0 to 1.0.1 and also with the update to 1.1. But no changes for the last update from 1.1 to 1.1.2

mali100 said:
Hi,
after the great work from verygreen, wheilitjohnny and arkusuma I decided to build a kernel with both of their improvements included.
Features:
[*]Additional USB related drivers (usb-storage, usb-serial ...)
[/LIST]
Click to expand...
Click to collapse
Very nice! I haven't been able to make proper use of usb-serial converters yet because the permission of the created device (eg /dev/ttyUSB0) is always set to 0600 when the device is connected. From what I've read, usually an entry in ueventd.rc solves this. Unfortunately ueventd seems to be omitted from the B&N image..

How are you trying to open the device? It worked fine when I tried directly from the terminal or with this app https://play.google.com/store/apps/details?id=android_serialport_api.sample

My USB keyboard does not work with this kernel. Multi Touch works so I uploaded the file right (Noogie). It worked before with the original "USB-Host" kernel.

Just to be clear, what's the difference between:
usb-host-mt-pack_0.1.zip
&
NST-kernel_0.1_uImage.zip
?
The mt-pack update should go over the uImage or can it be applied direct?

The mt-pack includes this kernel, and all the other stuff mentioned there. It's not necessary to use both. If you want an automated way of installing multitouch and usb-host support, just use the mt-pack, if you want to do everything manually take the uImage and figure out what else you have to change.

Hi
Have anybody such kernel for nook with Glow 1.1.5?

up

pasha4ur said:
Hi
Have anybody such kernel for nook with Glow 1.1.5?
Click to expand...
Click to collapse
Hi, I'm also wondering if somebody with a Glow has already tested this?
Thanks in advance!

OK, so I'm an idiot - I've searched high-and-low, and I can't find a solid method for easily moving this kernel over to my touch. I'm building a survey tablet for a non-profit, and the e-ink screen would be awesome for them - having a multitouch keyboard even better.
Any pointers? I tried CWM SD card, and can't mount /boot, ADB doesn't show /boot.
Is it as simple as connect via adb and:
mkdir /boot
mount <some point> /boot <some flags>?
profit!
?

Code:
mount -o rw,remount rootfs /
mkdir /boot
mount -t vfat /dev/block/mmcblk0p1 /boot

Renate NST said:
Code:
mount -o rw,remount rootfs /
mkdir /boot
mount -t vfat /dev/block/mmcblk0p1 /boot
Click to expand...
Click to collapse
Thanks, that did it. 2 years of .Net and my Linux has just about evaporated!

Hi,
I already have multitouch enabled for a long time using another tutorial.
Does yours fix the problem with the screen sometimes locking up (where you have to slide with two finger to release it again)?
Or does this version also have that problem? Thanks!

rhhd said:
Hi,
I already have multitouch enabled for a long time using another tutorial.
Does yours fix the problem with the screen sometimes locking up (where you have to slide with two finger to release it again)?
Or does this version also have that problem? Thanks!
Click to expand...
Click to collapse
It's based on the other kernel and has the same problems.

[KERNEL]{S} Advanced Stock ICS Kernel Build 17 [08/12/12]

Advanced Stock ICS Kernel for Xperia S​Here is a kernel based on the Stock ICS kernel with some features which come from DoomLord's GB kernel.
Features
autorooting
CWM recovery (with reboot recovery support)
init.d support (thanks DoomLord)
TUN/TAP driver
Download links
Build 17 (Fastboot)
Build 17 (CWM)
Build 16 (Fastboot)
Build 16 (CWM)
Prerequisites
An unlocked bootloader: Tuto here.
A stock ICS ROM (6.1.A.0.452 to 6.1.A.2.55). Don't expect this kernel to work with CM9/10.
How to flash
For elf files :
Read DoomLord's guide
You just have to replace kernel.elf by the name of the downloaded kernel in the flash command (eg : ics4.elf)
For zip files:
Flash the zip file from the recovery
Changelogs
Build 17 (08/12/12) :
Merge 6.1.A.2.55 kernel sources
Autodetect rom version in default.prop based on build.prop
Updated recovery, adbd and busybox (JB version)
Build 16 (01/11/12) :
Random reboot issue probably fixed (patch from CM10 kernel, thanks Kali)
Rom version increased to 6.1.A.2.50
Updated recovery, adbd and busybox (JB version)
SD card mounted by default in recovery
Vibration at boot removed, only led and backlight now
Build 15 (05/09/12) : Increase ROM version in default.prop from 6.1.A.0.452 to 6.1.A.2.45
Build 14 :
New MMC driver (from codeaurora) : it fixes issue while formatting partitions in CWM
Wifi module built from source (in the ramdisk)
Updated recovery
Disable again hardware clock
Build 13 :
Backup / Restore fixed with dedupe
Backlight enabled in CWM
Better "reboot recovery" handling in adbd / busybox and recovery
Build 12 :
Updated recovery
Hardware clock correctly saved (from CM9 kernel)
Build 11 : Go back to GCC 4.4 (fix artifacts with camera preview)
Build 10 :
Kernel built with GCC 4.6
Several autoroot fixes (Superuser app pushed just once and correctly removed in /data)
Working reboot recovery command (with adb too)
Updated su (3.1.1) and Superuser (3.1.3)
A bunch of new command included in the new busybox (ifconfig, wget, vi, and many more !)
Build 9 :
Kernel built from sources
TUN/TAP driver included (for VPN)
Build 8 : Fix mass storage in CWM
Build 7 : Fix MTP
Build 6 : Key mapping in CWM fixed
Build 5 :
New recovery built from latest CM9 sources
Fixed generation of md5sum with nandroid
Increased font size in CWM
Boot partition backup and restore
New adbd built from CM9 sources (fixed an issue with hardcoded sh path in /system)
Build 4 :
Correct su binary
Don't wait 3 sec if /cache/recovery/boot exists
Build 3 :
Leds and vibrator at startup fixed
Sources
Ramdisk sources
Kernel sources
Credits
DoomLord : many thanks to him for its kernel and all his scripts.
championswimmer and sminki for their help
FreeXperia team for their work on CM

makes it perfectly start does not make any errors
greetings and thanks

yes it boots!
(maybe you can help with my Question here )

Hey, I also have tested several times to include recovery, but withut succes, didn't get any further then a booting kernel without recovery or vibration and LED on to enter recovery but no entering recovery and kernel that doesn't boot.
Please pm me if you want to work together, I saw your kernel is from ICX team? I know nick very well so I'd would be a pleasure to work with you too

sminki said:
yes it boots!
(maybe you can help with my Question here )
Click to expand...
Click to collapse
for this question and any other other question similar to this
head here
http://forum.xda-developers.com/showthread.php?t=1659584
it has menu driven process to extract and repack kernel.elf (ramdisk also can be extracted and packed )

Welcome Champ, good to see you mate.
I will leave the thread here as knowing you, you will have a kernel ready for us in a few hours.:fingers-crossed:

thanks for the test guys... so now i'm diving into including recovery....
good to know i could pull off kernel.elf editing in my first attempt lol
@colossus if not in hours, then definitely within 1 or 2 days
EDIT :
can someone send me the kernel.elf from FXP122 cm9 ??
will save me the time to download the whole ROM

This is sweet, good job!!

john9 said:
This is sweet, good job!!
Click to expand...
Click to collapse
Only a few files to edit now
We'll keep you updated
Sent from my LT26i using XDA

championswimmer said:
btw if anyone wishes to do this before me,
this diffstats should help you
https://github.com/championswimmer/xps-ramdisk/commit/a61969aefca00ce3a6e4e112e97403fb6f0c79e9
it shows how doomlord added recovery to gb kernel..
Click to expand...
Click to collapse
cool.. well that's a hell of a lot easier than the manual route I was taking. This was my goal, but for personal rather than pseudo "xda glory" as I'm working with DooM's stuff I didn't feel right posting it without his permission, but he's probably too busy to care
go for it championswimmer :victory:

Excuse my noob-ish question, but... what's the difference between a 'stock' kernel with recovery and a completely custom kernel like DoomLord's? Is it to do with core frequencies/governors?

fNOOB said:
Excuse my noob-ish question, but... what's the difference between a 'stock' kernel with recovery and a completely custom kernel like DoomLord's? Is it to do with core frequencies/governors?
Click to expand...
Click to collapse
Frequencies and governors are one possible customicing for kernels, for the most users the most important thing. also Kernel modifing can allows you init.d support, undervoltscripts and also allows (or denies) MSC support... and, for shure, clean out some tings, make things more efficiently and and and... a dev is nearly totaly free to create a very customiced kernel with or without special Driver support or so

noob.fl said:
Frequencies and governors are one possible customicing for kernels, for the most users the most important thing. also Kernel modifing can allows you init.d support, undervoltscripts and also allows (or denies) MSC support... and, for shure, clean out some tings, make things more efficiently and and and... a dev is nearly totaly free to create a very customiced kernel with or without special Driver support or so
Click to expand...
Click to collapse
Cheers mate

sminki said:
cool.. well that's a hell of a lot easier than the manual route I was taking. This was my goal, but for personal rather than pseudo "xda glory" as I'm working with DooM's stuff I didn't feel right posting it without his permission, but he's probably too busy to care
go for it championswimmer :victory:
Click to expand...
Click to collapse
using someone's work just because 'he's too busy to care' is not the aim which we at xda strive for ...
i've already talked with Doomlord regarding using his recovery... and as long as I clearly mention it's his work and provide links back to his thread, he has no issues with anyone else using it...
(and i'll surely do that ^^ when i release a kernel containing his recovery, if i ever do that)

championswimmer said:
using someone's work just because 'he's too busy to care' is not the aim which we at xda strive for ...
i've already talked with Doomlord regarding using his recovery... and as long as I clearly mention it's his work and provide links back to his thread, he has no issues with anyone else using it...
(and i'll surely do that ^^ when i release a kernel containing his recovery, if i ever do that)
Click to expand...
Click to collapse
cool, i was only making a bad joke, we all know DooM cares

sminki said:
cool, i was only making a bad joke, we all know DooM cares
Click to expand...
Click to collapse
lol.. ok
and i'll bring you some unicorns soon

championswimmer said:
lol.. ok
and i'll bring you some unicorns soon
Click to expand...
Click to collapse
I can't wait! :victory:

so this kernel has the ro.secure property in default.prop set to 0??

Tnaks mate for your job!
tested right now the test version and the sony logo fades and reboots

can you plug it into a pc and run a logcat from command prompt and give me the output of any comes??