[OCKERNEL GB - CPU 1500MHz LPDDR2 333MHz] EternityProject Kernel for Motorola OLYMPUS

Search This thread

kholk

Retired Recognized Developer
May 20, 2007
2,293
3,829
Torino
Welcome to the EternityProject Olympus Kernel Thread!


What is it?
It is a kernel with some updates on Tegra2 and Cortex A9 management drivers.

Why should I flash it?
You should flash it only if you know what are you doing.
If you know what are you doing, you shouldn't ask this question.

Flashing methods:
1. Copy eternityproject_vx.x.img into your fastboot folder and do this:
Code:
fastboot flash boot eternityproject_vx.x.img

OR

2. Download the update.zip version and flash it through ClockWorkMod Recovery.

Installing Modules (Only for method 1):
Code:
adb push modules/dhd.ko /data/local/tmp/
adb push modules/evfwd.ko /data/local/tmp/
adb push modules/aev.ko /data/local/tmp/
adb shell
 su
 mount -o remount,rw /dev/block/mmcblk0p12 /system
 cp /data/local/tmp/dhd.ko /system/lib/
 cp /data/local/tmp/evfwd.ko /system/lib/hw/
 cp /data/local/tmp/aev.ko /system/lib/hw/
 chmod 777 /system/lib/dhd.ko
 chmod 777 /system/lib/hw/evfwd.ko
 chmod 777 /system/lib/hw/aev.ko
 exit
 exit

Features:
-- Stock frequencies
-- Optimized/Modified Tegra 2 Drivers
-- Modified Cortex-A9 (Tegra 2 core)'s cache behavior. Great results on tests.

Changelog:
Code:
Gingerbread: V1.4
- Overclocked a bit more.
- Some other kernel performance improvements (only on 1.5GHz version)
Gingerbread: V1.3
- CPU: 1300MHz
- AVP: 280MHz
- LPDDR2: 333MHz
- eval-'s cmdline hack (one boot.img for all tegraparts)
- Some other minor performance and power management enhancements.
Gingerbread: V1.2
- CPU: 1210MHz
- AVP: 275MHz
- LPDDR2: 333MHz
- Kernel version updated to 2.6.32.44
Gingerbread: V1.1
- New OC method by faux123
Gingerbread: V1.0
- BFQ updated to BFQv2-r1
- EternityProject optimizations integrated
- Codebase migration to ATRIX ATT GB official source
- ISO9960 CDROM FS supported
- UDF FS supported
- NTFS r/w supported
- CIFS supported
- EXT4 supported
FroYo: V1.0
- Some other ARM Dual/MultiCore optimizations
- ARM Kernel Scheduler optimizations
- Improved stability and error checking on memory ioremaps
FroYo: v0.99
- fix LP2 scheduling in atomic
- video: pwm_backlight: Add check_fb hook
- Initial support for dualcore AES engine
- ARM: SMP: ensure smp_send_stop() waits for CPUs to stop
- Enabled support for CISCO VPNs. Various configuration options updated.
- aev and evfwd modules compiled statically. Not modules anymore.
Gingerbread: v0.95
- WiFi FIX for Gingerbread (Try #1)
v0.9b
- WiFi module has been reverted to ATT version.
v0.9
- Introducing SLQB as default SLAB allocator
- Compilation optimizations // slight performance enhancement on CPU operations
v0.8
- Wakeup fix -- Voltages as to nVidia specs (Never go up of more than 100mV)
v0.7b
- Audio routing fixed. Now sound is fully working (tested on my device)
- ARB Semaphores tuned for Olympus AP20H
- SLAB Allocator: SLAB
- IO Scheduler: BFQ
- Fixed CWM updater-script. Now it'll install the modules just fine.
v0.5
- Sound MUX BUG solved but still no sound
- Custom Frequency/Voltage table for Tegra
- Frequency/Voltage management support via PimpMyCpu
- MAX Frequency (default): 1.1GHz
v0.4
- WiFi Support via Olympus board source files hacked
v0.3
- New PMIC and Temperature Sensor driver
- Kernel version: 2.6.32.42
v0.1
- ALSA: Support for concurrent playback/record
- ThumbEE instructions support enabled
- Power management: Accelerate grace period if last non-dynticked CPU
- Touchscreen management: One event per tap (no double-events)
- Touch events: Debug messages disabled
- Touch events: Added finger release event
- SPI: Building without LPRINTK (performance optimization)
- Subsystem suspend and resume implemented
- Clocksource updated to reflect the changes
- Sched optimizations
- timer: Separate clocksource and sched_clock
- usb: host: tegra: Fix enumeration after lp0
- staging: android: lowmemorykiller: Ignore shmem pages in page-cache
- tegra: cpufreq thermal throttling cleanups
- Tegra ALSA: Fix Playback crash after Record
- Tegra ALSA: Fix for kernel panic when dealing with DMA
- tegra: clock: Add function to set SDMMC tap delay
- tegra-aes: AES Crypto Hardware Acceleration implemented
- tegra: registering tegra-avp device
- tegra: Add speedo-based process identification
- tegra: duplicate vde clock for aes in tegra2_clocks
- tegra: hardware arbitration semaphore support
- tegra: add VDE and arb semaphores to iomap.h
- video: tegra: support output pin polarities setting
- tegra: Prevent requeuing in-progress DMA requests
- Semaphores implementation
- Cache management: Don't wipe data. Overwrite it instead.
- ASM routines optimizations
- Build optimizations
- Added parameter checking to memory functions on GPU code
- Optimized SDIO suspend handler
- Kernel version: 2.6.32.24



Actual recommended ROM (FroYo):
AP: Version.4.2.11.MB860.Retail.en.FR - OSHWT_U1_6.54.0 - OLYEM_U4_2.1.1
BP: 01.97.00R (just 'cause this version works for me)

Actual recommended ROM (Gingerbread):
AP: Aura 1.2.2.1 (or later)
BP: 01.97.00R (just 'cause this version works for me)

If you come from faux123's kernel:
An user has kindly reported that there's a procedure to follow for making WiFi to work with other kernels (EternityProject included!)
Thanks Kholk, you pointed me in the right direction. I was able to get WIFI working after flashing back to the stock kernel provided by faux.

Directions:
If you are useing Faux123's kernel Try this:
Flash the stock kernel he provides on his site.
Before reboot remove SIM card (this may not be nessasary)
Boot and Check airplane mode (this too may not be nessasary)
Shut down and install Kholk's kernel.

It worked for me.
Thanks to joeavery for publishing these directions.



Have a read at this:
Repeat after me: HIGH VOLTAGE = HIGH TEMP. HIGH TEMP = UNSTABLE.

The problem is temperature. There are process variations in different revs and batches of silicon that will cause them to react differently to higher than spec voltage. Some batches will deal with it fine. Some will create a bunch of extra heat.

The overclock can fail for two reasons: 1. Not enough voltage: the rise/fall time of the signal is too slow at the given voltage/frequency. 2. Too much voltage: the chip produces too much heat and (in this case) the phone shuts itself down.

Because of process variations neither of the limits are constant. Kholk's voltage settings are intentionally high so you can undervolt and find the lowest stable voltage.

This is similar to PC overclocking, but not the same. Imagine if you were overclocking your PC and the core voltage was 1.2V and 3 GHz stock. You wouldn't immediately try for 4.5GHz @ 2.0V would you?

Unless you roll your own kernel you have no control over the voltage settings. You can't overvolt, only undervolt. so Kholk's kernel defaults to the HIGHEST POSSIBLE STABLE VOLTAGE, which will be unstable DUE TO HIGH TEMPERATURE for many users.
Thanks to stewartsoda for pointing this out. :)


Known problems and solutions:
1. Random reboots: This happens only when you put your phone in sleep mode when WiFi is enabled. There are two solutions:
*** A. Turn off WiFi prior sending your device in sleep mode
*** B. Go in WiFi settings, press Menu, then Advanced. Set your WiFi Sleep Mode switch to NEVER. This won't put the WiFi chip in sleep mode when enabled and your device is in sleep mode.
*** C. Install a software like JuiceDefender (or others) that will shut down your WiFi when you put your device to sleep.


Download:
EternityProject Kernel v1.0 FroYo - update.zip for CWM: MegaUpload


!!NEW!!
EternityProject Kernel v1.4 Gingerbread EXT4 1.4GHz - update.zip for CWM: MegaUpload
EternityProject Kernel v1.4 Gingerbread EXT4 1.5GHz - update.zip for CWM: MegaUpload
The kernel will convert your /system partition to EXT4 (if it still isn't EXT4) and boot from it.


IMPORTANT: Flash the 01.97.00R Radio or you'll have WiFi problems (random reboots)!!!
Note2: The CWM update will automatically install Kernel+Modules.
Note3: The kernel doesn't work on Motorola's official 1.8.3 due to board management incompatibilities. The GINGERBREAD Kernel is highly experimental and unstable.
Note4: If you flash the EXT4 kernel and you want to go back to EXT3, you'll have to reflash your system partition via FastBoot or RSD(SBF)!
Note5: Don't play with voltages on SetCPU unless you really know what you are doing: you can cause unstabilities.


Old Versions:

EternityProject Kernel v1.3 Gingerbread w/SYSTEM EXT4 converter - update.zip for CWM: MegaUpload
EternityProject Kernel v1.2 Gingerbread - update.zip for CWM: MegaUpload
EternityProject Kernel v1.2 Gingerbread w/SYSTEM EXT4 converter - update.zip for CWM: MegaUpload
EternityProject Kernel v1.1 Gingerbread - update.zip for CWM: MegaUpload
EternityProject Kernel v1.1 Gingerbread -- OVERCLOCKING TEST (AVP 275MHz | CPU 1100MHz) -- update.zip for CWM: MegaUpload
EternityProject Kernel v1.1 Gingerbread -- OVERCLOCKING TEST (AVP 275MHz | CPU 1180MHz) -- update.zip for CWM: MegaUpload
EternityProject Kernel v1.1 Gingerbread -- OVERCLOCKING TEST (AVP 275MHz | CPU 1180MHz | LPDDR2 333MHz) -- update.zip for CWM: MegaUpload
EternityProject Kernel v1.0 Gingerbread - update.zip for CWM: MegaUpload
EternityProject Kernel v0.99 - update.zip for CWM: MegaUpload
EternityProject Kernel v0.9b - update.zip for CWM: MegaUpload
EternityProject Kernel v0.95 GINGERBREAD - update.zip for CWM: MegaUpload
EternityProject Kernel v0.9b GINGERBREAD - update.zip for CWM: MegaUpload
EternityProject Kernel v0.9 - update.zip for CWM: MegaUpload
EternityProject Kernel v0.8 - update.zip for CWM: MegaUpload
EternityProject Kernel v0.7b: MegaUpload
EternityProject Kernel v0.7b - update.zip for CWM: MegaUpload
EternityProject Kernel v0.5: MegaUpload
EternityProject Kernel v0.5 - update.zip for CWM: MegaUpload
EternityProject Kernel v0.4: MegaUpload
EternityProject Kernel v0.4 - update.zip for CWM: MegaUpload
EternityProject Kernel v0.3: MegaUpload
EternityProject Kernel v0.1: MegaUpload


Git:
Eternity Project hosted @ gitorious.org
FroYo kernel source: https://www.gitorious.org/eternity-prj/eternityprj-kernel-olympus
Gingerbread kernel source: https://www.gitorious.org/eternity-prj/eternityprj-kernel-olympus-gb




Enjoy!

The Eternity Project Developer
--kholk
 

Attachments

  • 2011-07-08_23-48-06_109.jpg
    2011-07-08_23-48-06_109.jpg
    100.2 KB · Views: 16,619
Last edited:

frankiedizzle87

Senior Member
Aug 23, 2009
679
18
Buffalo NY
Oh wow so the rumors of your departure was false? Hmmmmm any wanna try this? I've always heard hell hath no fury like a dev scorned lol

Sent from my MB860 using XDA Premium App
 

Swiftks

Retired Forum Moderator
Mar 16, 2011
3,741
1,910
The Woodlands, TX
PIMP Juice.... Waiting.. Waiting... :D

Downloading... Downloading... :)

Just remember, I was nice to you, and never called you bad names, so please don't hurt my phone. :p

Huumm, flash??? Don't flash?? flash??? don't flash?? I hate being the guinea pig
 
Last edited:

Swiftks

Retired Forum Moderator
Mar 16, 2011
3,741
1,910
The Woodlands, TX
Error when trying to flash with fastboot

"Unknown partition 'eternityprj_0.1.img"
"error: cannot determine image filename for 'eternityprj_0.1.img"
 
Last edited:

kholk

Retired Recognized Developer
May 20, 2007
2,293
3,829
Torino
I'm very sorry about the source not being published for now.. it's really huge and I've got an HSPA connection here as I'm far from home...

I'll "steal" a WiFi connection from someone soon ;)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 74
    Welcome to the EternityProject Olympus Kernel Thread!


    What is it?
    It is a kernel with some updates on Tegra2 and Cortex A9 management drivers.

    Why should I flash it?
    You should flash it only if you know what are you doing.
    If you know what are you doing, you shouldn't ask this question.

    Flashing methods:
    1. Copy eternityproject_vx.x.img into your fastboot folder and do this:
    Code:
    fastboot flash boot eternityproject_vx.x.img

    OR

    2. Download the update.zip version and flash it through ClockWorkMod Recovery.

    Installing Modules (Only for method 1):
    Code:
    adb push modules/dhd.ko /data/local/tmp/
    adb push modules/evfwd.ko /data/local/tmp/
    adb push modules/aev.ko /data/local/tmp/
    adb shell
     su
     mount -o remount,rw /dev/block/mmcblk0p12 /system
     cp /data/local/tmp/dhd.ko /system/lib/
     cp /data/local/tmp/evfwd.ko /system/lib/hw/
     cp /data/local/tmp/aev.ko /system/lib/hw/
     chmod 777 /system/lib/dhd.ko
     chmod 777 /system/lib/hw/evfwd.ko
     chmod 777 /system/lib/hw/aev.ko
     exit
     exit

    Features:
    -- Stock frequencies
    -- Optimized/Modified Tegra 2 Drivers
    -- Modified Cortex-A9 (Tegra 2 core)'s cache behavior. Great results on tests.

    Changelog:
    Code:
    Gingerbread: V1.4
    - Overclocked a bit more.
    - Some other kernel performance improvements (only on 1.5GHz version)
    Gingerbread: V1.3
    - CPU: 1300MHz
    - AVP: 280MHz
    - LPDDR2: 333MHz
    - eval-'s cmdline hack (one boot.img for all tegraparts)
    - Some other minor performance and power management enhancements.
    Gingerbread: V1.2
    - CPU: 1210MHz
    - AVP: 275MHz
    - LPDDR2: 333MHz
    - Kernel version updated to 2.6.32.44
    Gingerbread: V1.1
    - New OC method by faux123
    Gingerbread: V1.0
    - BFQ updated to BFQv2-r1
    - EternityProject optimizations integrated
    - Codebase migration to ATRIX ATT GB official source
    - ISO9960 CDROM FS supported
    - UDF FS supported
    - NTFS r/w supported
    - CIFS supported
    - EXT4 supported
    FroYo: V1.0
    - Some other ARM Dual/MultiCore optimizations
    - ARM Kernel Scheduler optimizations
    - Improved stability and error checking on memory ioremaps
    FroYo: v0.99
    - fix LP2 scheduling in atomic
    - video: pwm_backlight: Add check_fb hook
    - Initial support for dualcore AES engine
    - ARM: SMP: ensure smp_send_stop() waits for CPUs to stop
    - Enabled support for CISCO VPNs. Various configuration options updated.
    - aev and evfwd modules compiled statically. Not modules anymore.
    Gingerbread: v0.95
    - WiFi FIX for Gingerbread (Try #1)
    v0.9b
    - WiFi module has been reverted to ATT version.
    v0.9
    - Introducing SLQB as default SLAB allocator
    - Compilation optimizations // slight performance enhancement on CPU operations
    v0.8
    - Wakeup fix -- Voltages as to nVidia specs (Never go up of more than 100mV)
    v0.7b
    - Audio routing fixed. Now sound is fully working (tested on my device)
    - ARB Semaphores tuned for Olympus AP20H
    - SLAB Allocator: SLAB
    - IO Scheduler: BFQ
    - Fixed CWM updater-script. Now it'll install the modules just fine.
    v0.5
    - Sound MUX BUG solved but still no sound
    - Custom Frequency/Voltage table for Tegra
    - Frequency/Voltage management support via PimpMyCpu
    - MAX Frequency (default): 1.1GHz
    v0.4
    - WiFi Support via Olympus board source files hacked
    v0.3
    - New PMIC and Temperature Sensor driver
    - Kernel version: 2.6.32.42
    v0.1
    - ALSA: Support for concurrent playback/record
    - ThumbEE instructions support enabled
    - Power management: Accelerate grace period if last non-dynticked CPU
    - Touchscreen management: One event per tap (no double-events)
    - Touch events: Debug messages disabled
    - Touch events: Added finger release event
    - SPI: Building without LPRINTK (performance optimization)
    - Subsystem suspend and resume implemented
    - Clocksource updated to reflect the changes
    - Sched optimizations
    - timer: Separate clocksource and sched_clock
    - usb: host: tegra: Fix enumeration after lp0
    - staging: android: lowmemorykiller: Ignore shmem pages in page-cache
    - tegra: cpufreq thermal throttling cleanups
    - Tegra ALSA: Fix Playback crash after Record
    - Tegra ALSA: Fix for kernel panic when dealing with DMA
    - tegra: clock: Add function to set SDMMC tap delay
    - tegra-aes: AES Crypto Hardware Acceleration implemented
    - tegra: registering tegra-avp device
    - tegra: Add speedo-based process identification
    - tegra: duplicate vde clock for aes in tegra2_clocks
    - tegra: hardware arbitration semaphore support
    - tegra: add VDE and arb semaphores to iomap.h
    - video: tegra: support output pin polarities setting
    - tegra: Prevent requeuing in-progress DMA requests
    - Semaphores implementation
    - Cache management: Don't wipe data. Overwrite it instead.
    - ASM routines optimizations
    - Build optimizations
    - Added parameter checking to memory functions on GPU code
    - Optimized SDIO suspend handler
    - Kernel version: 2.6.32.24



    Actual recommended ROM (FroYo):
    AP: Version.4.2.11.MB860.Retail.en.FR - OSHWT_U1_6.54.0 - OLYEM_U4_2.1.1
    BP: 01.97.00R (just 'cause this version works for me)

    Actual recommended ROM (Gingerbread):
    AP: Aura 1.2.2.1 (or later)
    BP: 01.97.00R (just 'cause this version works for me)

    If you come from faux123's kernel:
    An user has kindly reported that there's a procedure to follow for making WiFi to work with other kernels (EternityProject included!)
    Thanks Kholk, you pointed me in the right direction. I was able to get WIFI working after flashing back to the stock kernel provided by faux.

    Directions:
    If you are useing Faux123's kernel Try this:
    Flash the stock kernel he provides on his site.
    Before reboot remove SIM card (this may not be nessasary)
    Boot and Check airplane mode (this too may not be nessasary)
    Shut down and install Kholk's kernel.

    It worked for me.
    Thanks to joeavery for publishing these directions.



    Have a read at this:
    Repeat after me: HIGH VOLTAGE = HIGH TEMP. HIGH TEMP = UNSTABLE.

    The problem is temperature. There are process variations in different revs and batches of silicon that will cause them to react differently to higher than spec voltage. Some batches will deal with it fine. Some will create a bunch of extra heat.

    The overclock can fail for two reasons: 1. Not enough voltage: the rise/fall time of the signal is too slow at the given voltage/frequency. 2. Too much voltage: the chip produces too much heat and (in this case) the phone shuts itself down.

    Because of process variations neither of the limits are constant. Kholk's voltage settings are intentionally high so you can undervolt and find the lowest stable voltage.

    This is similar to PC overclocking, but not the same. Imagine if you were overclocking your PC and the core voltage was 1.2V and 3 GHz stock. You wouldn't immediately try for 4.5GHz @ 2.0V would you?

    Unless you roll your own kernel you have no control over the voltage settings. You can't overvolt, only undervolt. so Kholk's kernel defaults to the HIGHEST POSSIBLE STABLE VOLTAGE, which will be unstable DUE TO HIGH TEMPERATURE for many users.
    Thanks to stewartsoda for pointing this out. :)


    Known problems and solutions:
    1. Random reboots: This happens only when you put your phone in sleep mode when WiFi is enabled. There are two solutions:
    *** A. Turn off WiFi prior sending your device in sleep mode
    *** B. Go in WiFi settings, press Menu, then Advanced. Set your WiFi Sleep Mode switch to NEVER. This won't put the WiFi chip in sleep mode when enabled and your device is in sleep mode.
    *** C. Install a software like JuiceDefender (or others) that will shut down your WiFi when you put your device to sleep.


    Download:
    EternityProject Kernel v1.0 FroYo - update.zip for CWM: MegaUpload


    !!NEW!!
    EternityProject Kernel v1.4 Gingerbread EXT4 1.4GHz - update.zip for CWM: MegaUpload
    EternityProject Kernel v1.4 Gingerbread EXT4 1.5GHz - update.zip for CWM: MegaUpload
    The kernel will convert your /system partition to EXT4 (if it still isn't EXT4) and boot from it.


    IMPORTANT: Flash the 01.97.00R Radio or you'll have WiFi problems (random reboots)!!!
    Note2: The CWM update will automatically install Kernel+Modules.
    Note3: The kernel doesn't work on Motorola's official 1.8.3 due to board management incompatibilities. The GINGERBREAD Kernel is highly experimental and unstable.
    Note4: If you flash the EXT4 kernel and you want to go back to EXT3, you'll have to reflash your system partition via FastBoot or RSD(SBF)!
    Note5: Don't play with voltages on SetCPU unless you really know what you are doing: you can cause unstabilities.


    Old Versions:

    EternityProject Kernel v1.3 Gingerbread w/SYSTEM EXT4 converter - update.zip for CWM: MegaUpload
    EternityProject Kernel v1.2 Gingerbread - update.zip for CWM: MegaUpload
    EternityProject Kernel v1.2 Gingerbread w/SYSTEM EXT4 converter - update.zip for CWM: MegaUpload
    EternityProject Kernel v1.1 Gingerbread - update.zip for CWM: MegaUpload
    EternityProject Kernel v1.1 Gingerbread -- OVERCLOCKING TEST (AVP 275MHz | CPU 1100MHz) -- update.zip for CWM: MegaUpload
    EternityProject Kernel v1.1 Gingerbread -- OVERCLOCKING TEST (AVP 275MHz | CPU 1180MHz) -- update.zip for CWM: MegaUpload
    EternityProject Kernel v1.1 Gingerbread -- OVERCLOCKING TEST (AVP 275MHz | CPU 1180MHz | LPDDR2 333MHz) -- update.zip for CWM: MegaUpload
    EternityProject Kernel v1.0 Gingerbread - update.zip for CWM: MegaUpload
    EternityProject Kernel v0.99 - update.zip for CWM: MegaUpload
    EternityProject Kernel v0.9b - update.zip for CWM: MegaUpload
    EternityProject Kernel v0.95 GINGERBREAD - update.zip for CWM: MegaUpload
    EternityProject Kernel v0.9b GINGERBREAD - update.zip for CWM: MegaUpload
    EternityProject Kernel v0.9 - update.zip for CWM: MegaUpload
    EternityProject Kernel v0.8 - update.zip for CWM: MegaUpload
    EternityProject Kernel v0.7b: MegaUpload
    EternityProject Kernel v0.7b - update.zip for CWM: MegaUpload
    EternityProject Kernel v0.5: MegaUpload
    EternityProject Kernel v0.5 - update.zip for CWM: MegaUpload
    EternityProject Kernel v0.4: MegaUpload
    EternityProject Kernel v0.4 - update.zip for CWM: MegaUpload
    EternityProject Kernel v0.3: MegaUpload
    EternityProject Kernel v0.1: MegaUpload


    Git:
    Eternity Project hosted @ gitorious.org
    FroYo kernel source: https://www.gitorious.org/eternity-prj/eternityprj-kernel-olympus
    Gingerbread kernel source: https://www.gitorious.org/eternity-prj/eternityprj-kernel-olympus-gb




    Enjoy!

    The Eternity Project Developer
    --kholk
    11
    Cough.. KANGED... cough....

    Please mention source of your super amazing OC to 1.3 GHz.. Thanks..

    BTW, this is NOT the first time... You seemed to have VERY VERY short memory....

    Remember, I DO NOT MIND people COPY my work.. but I DO mind when they don't credit...
    7
    OMG... he's KANGING me hardcore and no one is doing anything about it... :(

    All I am asking for is acknowledgement of my work :p He didn't even mention me or atrix-dev-team... :(
    6
    I'm going to close this thread temporary since there are many reports about this is not working. Also, I'm going to clean unncessary offtopic rants.

    @ the OP please PM me when you test this and make it work, so I can reopen it.

    Thanks,


    EDIT Thread reopened since the OP will provide contundent evidence that this is completely working. Also he will be posting the kernel source for GPL compliance.

    @ all members, again. Please stay on topic.
    6
    The kernel has been patched including nvidia's patches, linux kernel official patches and custom work.

    In a few hours I'll post the new version, v0.3, updated to Linux 2.6.32.42.