Root [KERNEL][UPDATE: 05/24/2012] bKernel-v2.3 & bKernel-CM7-v2.3 - 2.6.32.59

b_randon14 · Nov 13, 2011

Posted a CM7 version, based off Tickerguy's latest CM7 kernel(found in Beta 7!!)

ziggy46 · Nov 13, 2011

b_randon14 said:
Posted a CM7 version, based off Tickerguy's latest CM7 kernel(found in Beta 7!!)

I flashed the cm7 version... of frequencies didn't show up. Govonrrs did though. And so did undervolting

shimdachef · Nov 14, 2011

ziggy46 said:
I flashed the cm7 version... of frequencies didn't show up. Govonrrs did though. And so did undervolting

Use SetCPU or Nofrills, it'll show up there

b_randon14 · Nov 16, 2011

A new stockROM version of bKernel released. It's DEV-0.23! CM7 version with updates will be coming soon!

b_randon14 · Nov 16, 2011

Added a new CM7 version with updates from my last StockROM version release. It's super fast!!

Austrie · Nov 16, 2011

This kernel should be fast, GUARANTEED faster than stock CM7, even at same voltage, because of this kernel using ext2.
~~~
B_randon I was thinking of using ext2 too, but to many "new" people are using the triumph, so I decided to stick with ext4. To many people like to do battery pulls...

b_randon14 · Nov 16, 2011

Yeah well I left the cm on ext4 because the I/o speeds are way faster than the stock rom on ext4

mantera · Nov 16, 2011

>* Mounting of ext2 in the init.rc(This will mount the ext3 partitions as non-journaled ext2 partitions)

I'm confused. I assume this init.rc file that you mention is in the ramdisk, correct? Can you explain how this would affect the final filesystem once the actual file system is loaded? And did you figure out where the file system gets mounted as ext4?

I thought that the actual file system that is formatted during the actual ROM flashing? For example, looking in the updater script for the cm7 zip package, I see:

format("ext4", "EMMC", "/dev/block/mmcblk0p7");
mount("ext4", "EMMC", "/dev/block/mmcblk0p7", "/system");

I assume this means that during the flashing of CM7, /system is formatted as ext4 and so it will remain as ext4 until you reformat it as something else, correct?

TheGeekRedneck · Nov 16, 2011

Anyone know how battery life is with the CM7 version of this kernel?

I've been using mantera's OC kernel for the last few days and battery life has tanked compared to Tickerguy's...

Austrie · Nov 16, 2011

mantera said:
>* Mounting of ext2 in the init.rc(This will mount the ext3 partitions as non-journaled ext2 partitions)

I'm confused. I assume this init.rc file that you mention is in the ramdisk, correct? Can you explain how this would affect the final filesystem once the actual file system is loaded? And did you figure out where the file system gets mounted as ext4?

I thought that the actual file system that is formatted during the actual ROM flashing? For example, looking in the updater script for the cm7 zip package, I see:

format("ext4", "EMMC", "/dev/block/mmcblk0p7");
mount("ext4", "EMMC", "/dev/block/mmcblk0p7", "/system");

I assume this means that during the flashing of CM7, /system is formatted as ext4 and so it will remain as ext4 until you reformat it as something else, correct?

Only bkernel is ext2, cm7 is still ext4. Stock triumph is ext3, when you it becomes ext4, you have to change "("ext3", "EMMC"," to "("ext4", "EMMC",". It have 3 different sections that can be formated, data, cache, and system. In all you can have a mix combination of 3 filesytems on one phone. bkernel mount everything as ext2, so its a ext2 kernel, while cm7 and MIUI is ext4.

I'm confused(or I find it unnecessary) about, using the update script to change to ext4 if the kernel is already ext4, its not like the kernel is a different filesystem.

Edit: Its not the Init.rc in ramdisk...

b_randon14 · Nov 16, 2011

mantera said:
>* Mounting of ext2 in the init.rc(This will mount the ext3 partitions as non-journaled ext2 partitions)

I'm confused. I assume this init.rc file that you mention is in the ramdisk, correct? Can you explain how this would affect the final filesystem once the actual file system is loaded? And did you figure out where the file system gets mounted as ext4?

I thought that the actual file system that is formatted during the actual ROM flashing? For example, looking in the updater script for the cm7 zip package, I see:

format("ext4", "EMMC", "/dev/block/mmcblk0p7");
mount("ext4", "EMMC", "/dev/block/mmcblk0p7", "/system");

I assume this means that during the flashing of CM7, /system is formatted as ext4 and so it will remain as ext4 until you reformat it as something else, correct?

Well that is on the stock based kernel. Yeah the init.RC is in the ramdisk and it mounts everything and sets everything up to boot. So if the partition is formatted as ext3 like it is from the factory, you can have the init.rc mount that ext3 partition as an ext2 because it is backwards compatible with ext2. On cm7 for some reason, the init.qcom.RC is what mounts the partitions. It mounts them as ext4. The ext3 partitions can be mounted as ext4 as well cause if you notice in tickerguys cm7 updater script he only formats system and maybe cache but it doesn't format data as ext4 but through the initram data gets mounted as ext4. But like on the intercept you could mount an rfs partition as ext2 or ext4 because they ain't compatible(rfs is based off fat) so you had to convert to one or the other. And an ext2 formatted partition can't be mounted as ext4 I believe. The updater script actually formats the partition, but with the initrc youcan choose what to mount so long as whatever the partition is formatted as can be mounted as that(I.e ext3 mounted as ext4).

As for battery life I haven't put much hours on the cm7 build but on the stock based roms I get pretty good battery life

b_randon14 · Nov 16, 2011

mantera said:
>* Mounting of ext2 in the init.rc(This will mount the ext3 partitions as non-journaled ext2 partitions)

I'm confused. I assume this init.rc file that you mention is in the ramdisk, correct? Can you explain how this would affect the final filesystem once the actual file system is loaded? And did you figure out where the file system gets mounted as ext4?

I thought that the actual file system that is formatted during the actual ROM flashing? For example, looking in the updater script for the cm7 zip package, I see:

format("ext4", "EMMC", "/dev/block/mmcblk0p7");
mount("ext4", "EMMC", "/dev/block/mmcblk0p7", "/system");

I assume this means that during the flashing of CM7, /system is formatted as ext4 and so it will remain as ext4 until you reformat it as something else, correct?

Well that is on the stock based kernel. Yeah the init.RC is in the ramdisk and it mounts everything and sets everything up to boot. So if the partition is formatted as ext3 like it is from the factory, you can have the init.rc mount that ext3 partition as an ext2 because it is backwards compatible with ext2. On cm7 for some reason, the init.qcom.RC is what mounts the partitions. It mounts them as ext4. The ext3 partitions can be mounted as ext4 as well cause if you notice in tickerguys cm7 updater script he only formats system and maybe cache but it doesn't format data as ext4 but through the initram data gets mounted as ext4. But like on the intercept you could mount an rfs partition as ext2 or ext4 because they ain't compatible(rfs is based off fat) so you had to convert to one or the other. And an ext2 formatted partition can't be mounted as ext4 I believe. The updater script actually formats the partition, but with the initrc youcan choose what to mount so long as whatever the partition is formatted as can be mounted as that(I.e ext3 mounted as ext4).

As for battery life I haven't put much hours on the cm7 build but on the stock based roms I get pretty good battery life

Austrie · Nov 16, 2011

b_randon14 said:
Well that is on the stock based kernel. Yeah the init.RC is in the ramdisk and it mounts everything and sets everything up to boot. So if the partition is formatted as ext3 like it is from the factory, you can have the init.rc mount that ext3 partition as an ext2 because it is backwards compatible with ext2. On cm7 for some reason, the init.qcom.RC is what mounts the partitions. It mounts them as ext4. The ext3 partitions can be mounted as ext4 as well cause if you notice in tickerguys cm7 updater script he only formats system and maybe cache but it doesn't format data as ext4 but through the initram data gets mounted as ext4. But like on the intercept you could mount an rfs partition as ext2 or ext4 because they ain't compatible(rfs is based off fat) so you had to convert to one or the other. And an ext2 formatted partition can't be mounted as ext4 I believe. The updater script actually formats the partition, but with the initrc youcan choose what to mount so long as whatever the partition is formatted as can be mounted as that(I.e ext3 mounted as ext4).

As for battery life I haven't put much hours on the cm7 build but on the stock based roms I get pretty good battery life

Filesystems being mounted as a another, confusing like hell.... :cool:

Isn't it the init.rc in kernel?

ziggy46 · Nov 16, 2011

should i be worried about pulling the battery and my system corrupting?

i really dont want that to happen lol...

mantera · Nov 16, 2011

b_randon14 said:
Well that is on the stock based kernel. Yeah the init.RC is in the ramdisk and it mounts everything and sets everything up to boot. So if the partition is formatted as ext3 like it is from the factory, you can have the init.rc mount that ext3 partition as an ext2 because it is backwards compatible with ext2. On cm7 for some reason, the init.qcom.RC is what mounts the partitions. It mounts them as ext4. The ext3 partitions can be mounted as ext4 as well cause if you notice in tickerguys cm7 updater script he only formats system and maybe cache but it doesn't format data as ext4 but through the initram data gets mounted as ext4. But like on the intercept you could mount an rfs partition as ext2 or ext4 because they ain't compatible(rfs is based off fat) so you had to convert to one or the other. And an ext2 formatted partition can't be mounted as ext4 I believe. The updater script actually formats the partition, but with the initrc youcan choose what to mount so long as whatever the partition is formatted as can be mounted as that(I.e ext3 mounted as ext4).

Ahh ok. After a lot more looking through the files, I see the mount commands now. thanks.

mantera · Nov 16, 2011

TheGeekRedneck said:
Anyone know how battery life is with the CM7 version of this kernel?

I've been using mantera's OC kernel for the last few days and battery life has tanked compared to Tickerguy's...

Are you overclocking? If so, I would expect the battery life to be worse since you're using more power... Try setting back to 1024 and does that put your battery usage back to what you were expecting?

b_randon14 · Nov 17, 2011

Austrie said:
Filesystems being mounted as a another, confusing like hell....

Isn't it the init.rc in kernel?

Ha yeah lol. It's in the init.rc of the stock ROM kernel, now on CM7 its in init.qcom.rc(tickerguys) or I believe in isaac's builds it's init.triumph.rc, and I assume its somthing like that for the MIUI kernel as well. Yeah I believe that ext3 will mount as ext2 or ext4, and ext4 will mount as ext3 or ext2, but I believe ext2 will only mount as ext2 and ext3. Not 100% on that, but you could find out on google or somthing. Now you an't do something crazy like mount a ext3 partition as ntfs or fat or somthing lol!!! But the ext(extended filesystem) are somewhat backwards and even forwards compatible.

@ziggy, possibly if the kernel is requesting a write to the nand at the moment you pull the battery and all the writes hadn't been synced before. But i never had had a problem. And it's not so much loosing data, just it becoming corrupted. It may still appear to be there, but not work quite right. Like it still shows you have a text file there, but it don't open right. I have never had a problem that I have seen surface itself using ext2

bing7625 · Nov 17, 2011

i've been doning some research on the MSM8655 which is the chipset used in the triumph, and most of the OCing info i'm finding is based off the HTC thunderbolt because it uses the same GPU and chipset as this phone. now from what i could find is that the chipset itself is stable at 1.9ghz, but not at 2ghz. and i went through multiple articles to confirm this. from everything i read though is that the thunderbolt runs stable at 1.996GHz, but our phones when you use the 1.9GHz freq is only running at 1.901GHz, which in theory SHOULD mean our chipset should be stable at this speed, but as we all know this isn't the case at all with a lot of phones not being able to work above certain freq's most likely because of the imperfection of processor making, but if you google around a bit you will find out that the thunderbolt runs stable at 1.996GHz.

Austrie · Nov 17, 2011

This could be because of its HTC software....

bing7625 · Nov 17, 2011

i was thinking that could be the case.

b_randon14 · Nov 17, 2011

Yeah software can affect how stable a cpu runs. For example on the samsung based ROMs for the captivate(this is what phone shane87, my brother, has) they can only go to about 1400 stable, more like 1200 and be completely stable. But on the official CM7 builds, 1.6 is really stable. Their SoC is the hummingbird though and it's a little bit older, and not as robust.

b_randon14 · Nov 18, 2011

Added a EXT3 stock ROM version of bKernel-DEV-0.23 for those of you who are worried about data corruption when using EXT2.

streetpounder · Nov 18, 2011

Austrie said:
I was wondering for a 3 days, why can the evolution shift handle 2ghz and we have a better processor. Next thing bkernel comes out with 2ghz...

Edit: also some people triumphs can barely handle past 1.5ghz, so I know some random person will be sorry at 2ghz....

I think voltages are coming into play as well. My phone was not very stable past 1.4 until we got voltage control in the kernel. I now have been at 61 min 1.7 max for the last few days with a gentle undervolt at low steps and a a slight overvolt at the 1.6 and 1.7 Ghz frequencies... It has been rock solid no reboots, cold to the touch, and running around 15-18hrs per full charge of here and there use. I`m guessing there are variations in the powering to chip from phone to phone... thus contributing to the stability or lack thereof at the upper rung frequencies. I`m rocking 60 MFlops in linpack and 4000 ish on antutu @ 1.7GHz. Currently sitting at 15h 42min with 32% left on battery

thangfish · Nov 20, 2011

Hey B_,
Any idea if TG's .08 build has kernel changes that would preclude the use of your current build?

isaacj87 · Nov 20, 2011

thangfish said:
Hey B_,
Any idea if TG's .08 build has kernel changes that would preclude the use of your current build?

No, the changes were only on the software side. This kernel should still work.

Root [KERNEL][UPDATE: 05/24/2012] bKernel-v2.3 & bKernel-CM7-v2.3 - 2.6.32.59

Android Expert

Android Expert

Newbie

Android Expert

Android Expert

Android Expert

Android Expert

Android Expert

Member

Android Expert

Android Expert

Android Expert

Android Expert

Android Expert

Android Expert

Android Expert

Android Expert

Well-Known Member

Android Expert

Well-Known Member

Android Expert

Android Expert

Well-Known Member

Android Expert

Android Expert

BEST TECH IN 2023

Smartphones

Best Android Phones

Upcoming

Best iPhones

Upcoming

Tablets

Best Tablets

Upcoming

Laptops

Best Laptops

Upcoming

Televisions

Best TVs

Upcoming

Game Consoles

Best Game Consoles

Upcoming

Wearables

Best Wearables

Upcoming

Smart Home

Smart Home Tech

Upcoming

Similar threads