[KERNEL] vz-oc-linaro kernel v4: CM10.1 overclocking kernel - Linaro build

Search This thread

vanja_z

Senior Member
Oct 1, 2012
125
130
There has been a lot of active development on the kernel for our device with new commits almost every day. For this reason, the kernels I put up have been becoming outdated pretty quickly. For example, the cm10.1-oc(-linaro).2 builds are only EXACTLY compatible with the 20130219-NIGHTLY. You may find the kernels also work with other builds however it is not guaranteed.

I will be putting up new builds roughly once per fortnight and I will attempt to keep the compatibility section up to date.
 

johnwayne007

Senior Member
Nov 25, 2008
336
209
127.0.0.1
Samsung Galaxy S22 Ultra
Re: [KERNEL] vz-oc kernel: CM10.1 overclocking, normal & Linaro builds

Would it be possible to build your kernel and also use git to pull the latest patches from CM, for personal use since a fortnight is a long time between nightlies?

Sent from my One X using xda premium
 

rohan32

Retired Forum Mod / Retired Recognized Developer
Nov 27, 2011
1,980
5,028
New Jersey
rmathur.com
There has been a lot of active development on the kernel for our device with new commits almost every day. For this reason, the kernels I put up have been becoming outdated pretty quickly. For example, the cm10.1-oc(-linaro).2 builds are only EXACTLY compatible with the 20130219-NIGHTLY. You may find the kernels also work with other builds however it is not guaranteed.

I will be putting up new builds roughly once per fortnight and I will attempt to keep the compatibility section up to date.

If you set the kernel to install the modules the kernel build generates as well, you will almost completely rid your kernel of these compatibility problems. Unless a kernel commit is merged that also has parts in the device trees, your kernel will still function as it was intended, and nothing should break.

If you need help with an installer for the modules, feel free to grab one of my recent kernel release packages and see how the updater script i use does it.
 

bball606

Member
Feb 15, 2011
36
1
For anyone who flashed this kernel, can you boot into the 2/24 CM nightly using the boot.img from that zip? Me and a few others are experiencing a boot loop on the latest nightly over in the CM10.1 thread after flashing this kernel.
 

incofstupid

Senior Member
May 17, 2012
55
9
Bellevue
There has been a lot of active development on the kernel for our device with new commits almost every day. For this reason, the kernels I put up have been becoming outdated pretty quickly. For example, the cm10.1-oc(-linaro).2 builds are only EXACTLY compatible with the 20130219-NIGHTLY. You may find the kernels also work with other builds however it is not guaranteed.

I will be putting up new builds roughly once per fortnight and I will attempt to keep the compatibility section up to date.

Havent had a chance to say thanks for your hardwork putting this kernel. This kernel is awesome, made my HOXL fluid and snappier with the 1.7 OC. Keep the good work. once again thank you. :good:
 

bball606

Member
Feb 15, 2011
36
1
I'm running 2.22 cm10.1 with linaro_vz2, no problems.

dbd
Sorry, my question was very unspecific. I mean the stock CM kernel, not this one.
It seems that after flashing this kernel and then flashing the 2/24 nightly (and running the stock boot.img from CM zip) there is a bootloop. Once this kernel, or an older CM boot.img is flashed, the device can boot.
 

blacklistedcard

Senior Member
Dec 30, 2010
885
174
Re: [KERNEL] vz-oc kernel: CM10.1 overclocking, normal & Linaro builds

Sorry, my question was very unspecific. I mean the stock CM kernel, not this one.
It seems that after flashing this kernel and then flashing the 2/24 nightly (and running the stock boot.img from CM zip) there is a bootloop. Once this kernel, or an older CM boot.img is flashed, the device can boot.

I'm running 2/24 nightly and with this kernel its booting fine. I did notice that there were other people with the same problem.

Sent from my One X using xda app-developers app
 

bball606

Member
Feb 15, 2011
36
1
h8 said bootlooping was caused by a recent commit that should be fixed in the next nightly. As far as I know this kernel wasn't the issue.
 

blacklistedcard

Senior Member
Dec 30, 2010
885
174
Re: [KERNEL] vz-oc kernel: CM10.1 overclocking, normal & Linaro builds

h8 said bootlooping was caused by a recent commit that should be fixed in the next nightly. As far as I know this kernel wasn't the issue.

I was lucky that I don't have the reboot problem that other people were having with the last nightly.

Sent from my One X using xda app-developers app
 

nickeedoo

Senior Member
May 12, 2010
461
88
Running 2.22 with the linaro 2 (last file in the list). Everything except wifi seems to work fine.

Edit: useful information time. Instead of just saying "it's not working", I'll provide some description.
I toggle the wifi setting to on, and it says "turning wifi on..." but it never comes on.
Logcat say:

Code:
D/WifiService(  464): setWifiEnabled: true pid=1181, uid=1000
D/BluetoothAdapter(  675): 1090326768: getState() :  mService = null. Returning STATE_OFF
D/BluetoothAdapter( 1181): 1089374768: getState() :  mService = null. Returning STATE_OFF
E/WifiStateMachine(  464): Failed to load driver!
D/BluetoothAdapter(  675): 1090326768: getState() :  mService = null. Returning STATE_OFF
E/WifiStateMachine(  464): DriverFailedState
D/BluetoothAdapter( 1181): 1089374768: getState() :  mService = null. Returning STATE_OFF
 
Last edited:

macropterous

Senior Member
May 14, 2012
187
42
nyc
Running 2.22 with the linaro 2 (last file in the list). Everything except wifi seems to work fine.

Edit: useful information time. Instead of just saying "it's not working", I'll provide some description.
I toggle the wifi setting to on, and it says "turning wifi on..." but it never comes on.
Logcat say:

Code:
D/WifiService(  464): setWifiEnabled: true pid=1181, uid=1000
D/BluetoothAdapter(  675): 1090326768: getState() :  mService = null. Returning STATE_OFF
D/BluetoothAdapter( 1181): 1089374768: getState() :  mService = null. Returning STATE_OFF
E/WifiStateMachine(  464): Failed to load driver!
D/BluetoothAdapter(  675): 1090326768: getState() :  mService = null. Returning STATE_OFF
E/WifiStateMachine(  464): DriverFailedState
D/BluetoothAdapter( 1181): 1089374768: getState() :  mService = null. Returning STATE_OFF

Good info, thanx.

I am running the 2.22 nightly with the linaro2 kernel as well, and Wifi is able to connect. I have noticed dropped WiFi signal and inconsistent WiFi connectivity, which has been reported on the CM10.1 issue tracker.

dbd
 

vanja_z

Senior Member
Oct 1, 2012
125
130
I am really glad that people are enjoying this kernel but I would like to urge you guys to NOT report any issues in the CM10.1 thread or anywhere other than in this thread unless you are using the stock kernel for that ROM.

Also, just to reiterate, cm10.1_vz-oc(linaro).2.zip kernels are ONLY properly compatible with cm-10.1-20130219-NIGHTLY-evita.zip

ps. I will look at Rohans helpful suggestion soon but probably not for the next build.
 
Last edited:

macropterous

Senior Member
May 14, 2012
187
42
nyc
I am really glad that people are enjoying this kernel but I would like to urge you guys to NOT report any issues in the CM10.1 thread or anywhere other than in this thread unless you are using the stock kernel for that ROM.

Also, just to reiterate, cm10.1_vz-oc(linaro).2.zip kernels are ONLY properly compatible with cm-10.1-20130219-NIGHTLY-evita.zip

ps. I will look at Rohans helpful suggestion soon but probably not for the next build.

I could have been more clear...
I did not report an issue, I was just mentioning that CM10.1 has been tracking a number of WiFi connectivity issues, so perhaps the issue was not kernel specific.

dbd
 

Top Liked Posts

  • There are no posts matching your filters.
  • 21
    Introduction
    This is a replacement kernel for CyanogenMod 10 and 10.1 evita builds. The kernel is designed to be as close as possible to the stock CyanogenMod kernel with a few improvements.

    Linaro toolchain:
    The kernel is compiled with the latest Linaro toolchain based on gcc 4.7 rather than the default Android toolchain. This may provide performance improvements in some situations. I have made a few patches applied to make it compatible with gcc 4.7.

    Overclock:
    The highest frequency now available under Settings -> Performance with these kernels is,
    Code:
    CPU: 1782 MHz 1.25 V
    L2:  1350 MHz 1.15 V
    BUS:  532 MHz
    I've also included a modified thermald.conf in the flashable zip.

    Refresh rate:
    I've reverted the refresh rate to the original value from the sense source code (57 Hz). This works better when "Disable HW overlays" is selected.

    Downloading and installing
    Download the flashable zip,

    cm10.1_vz-oc-linaro.4.zip MD5=7233ccffa17fa16a2dc6292ecf755fb4
    mega.co.nz
    ubuntuone.com

    Older versions:
    cm10.1_vz-oc-linaro.3.zip MD5=5e0efdfd0390f3f923090a574d142808
    mega.co.nz
    ubuntuone.com
    cm10.1_vz-oc.2.zip MD5=cf2c4ee8ba09627e598b78dcea225d39
    cm10.1_vz-oc-linaro.2.zip MD5=2931cc59515949fa461a89ea17c99328
    vz-oc.1.zip MD5=2f1740d67cd1d5c02a7ac5489bafe7a0
    vz-oc.2.zip MD5=4e4d444130e8eb71c27cc23fed65fc88
    vz-oc-linaro.1.zip MD5=ca674641e05595e64698afda8aa02943
    vz-oc-linaro.2.zip MD5=2b01472d00e069c53f934c30b49475d1
    cm10.1_vz-oc.1.zip MD5=576db9e99b2289dae7fc5b548a0d61b4
    cm10.1_vz-oc-linaro.1.zip MD5=1a5f3b50608e6b44da50829b2c04ec5c

    If you have HBOOT earlier than 1.14 or have S-OFF, then you can just flash the zip from recovery. This will flash the kernel as well as all required modules and thermald.conf. Otherwise, HBOOT 1.14 users will need to extract the boot.img, enter bootloader mode and run
    Code:
    fastboot flash boot boot.img
    Then you will also need to flash the zip to get modules and themald.conf.

    Compatability
    cm10.1_vz-oc-linaro.4 is compatible with CM10.1 UNOFFICIAL build from 16/04/2013 onwards.
    cm10.1_vz-oc-linaro.3 is compatible with CM10.1 NIGHTLY build from 01/03/2013 onwards.
    cm10.1_vz-oc.2 (and linaro) are compatible with CM10.1 NIGHTLY build from 19/02/2013 only.
    cm10.1_vz-oc.1 (and linaro) are compatible with CM10.1 UNOFFICIAL build from 06/02/2013 only.
    vz-oc.2 (and linaro) are compatible with CM10 NIGHTLY builds from 26/12/2012 to 13/01/2013.
    vz-oc.1 (and linaro) are compatible with CM10 NIGHTLY builds from 28/11/2012 to 25/12/2012.

    Future development
    I hope to introduce GPU overclocking soon and there will be updated builds as
    soon as changes come into the main CyanogenMod repo.

    Building the kernel
    For those who would like to build the kernel themselves, here are some basic
    instructions. First you will need to acquire some tools. You can get the default
    toolchain from the CM10 source code at,
    Code:
    system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/
    Otherwise, if you want to use the Linaro toolchain, you can get it at
    Linaro toolchain
    You will also need a working boot image to get the ramdisk from. You can build
    mkbootimg using these instructions
    building mkbootimg
    Finally, you can get split_bootimg_pl from William Encks site
    download split_bootimg_pl
    Clone the repo and change to your desired branch
    Code:
    git clone https://github.com/vanja-zecevic/android_kernel_htc_msm8960.git
    git checkout jellybean-oc
    Now export an environmental variable pointing to your desired toolchain
    Code:
    export CCOMPILER=$PATH_TO_TOOLCHAIN/bin/arm-eabi-
    Copy the config file, run menuconfig once and start the build replacing -j12
    with your desired number of threads
    Code:
    cp ./config-oc ./.config
    make ARCH=arm SUBARCH=arm CROSS_COMPILE=$CCOMPILER menuconfig
    make ARCH=arm SUBARCH=arm CROSS_COMPILE=$CCOMPILER -j12
    Extract a ramdisk from a working boot image and repack with your freshly built
    kernel using the following command for cm10,
    Code:
    ./split_bootimg_pl ./boot.img
    ./mkbootimg --base 0x80400000 --ramdiskaddr 0x81800000 \
      --cmdline 'console=ttyHSL0,115200,n8' \
      --kernel arch/arm/boot/zImage --ramdisk boot.img-ramdisk.gz \
      -o boot_vz-oc.img
    cm10.1 will need the following cmdline
    Code:
    --cmdline 'console=ttyHSL0,115200,n8  androidboot.hardware=qcom'

    You are ready to flash your new kernel!

    Contact
    I hope you enjoy using this kernel! Please also visit the github page for this project for alternative download links and for the source code.

    GitHub

    Cheers,
    Vanja
    8
    Hey all, posted a new build with some minor updates. Works well with Corys unofficial builds.
    4
    I am really glad that people are enjoying this kernel but I would like to urge you guys to NOT report any issues in the CM10.1 thread or anywhere other than in this thread unless you are using the stock kernel for that ROM.

    Also, just to reiterate, cm10.1_vz-oc(linaro).2.zip kernels are ONLY properly compatible with cm-10.1-20130219-NIGHTLY-evita.zip

    ps. I will look at Rohans helpful suggestion soon but probably not for the next build.
    3
    There has been a lot of active development on the kernel for our device with new commits almost every day. For this reason, the kernels I put up have been becoming outdated pretty quickly. For example, the cm10.1-oc(-linaro).2 builds are only EXACTLY compatible with the 20130219-NIGHTLY. You may find the kernels also work with other builds however it is not guaranteed.

    I will be putting up new builds roughly once per fortnight and I will attempt to keep the compatibility section up to date.

    If you set the kernel to install the modules the kernel build generates as well, you will almost completely rid your kernel of these compatibility problems. Unless a kernel commit is merged that also has parts in the device trees, your kernel will still function as it was intended, and nothing should break.

    If you need help with an installer for the modules, feel free to grab one of my recent kernel release packages and see how the updater script i use does it.
    2
    I've put up cm10.1 kernels!

    ps. cm10.0 stable kernel is coming soon, I haven't forgotten, sorry for the delay