• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Hroark's Prevail Kernel Factory

The~Skater~187 said:
Is this correct:

*
* Generic Driver Options
*
path to uevent helper (UEVENT_HELPER_PATH) []
Maintain a devtmpfs filesystem to mount at /dev (DEVTMPFS) [N/y/?] n
Select only drivers that don't need compile-time external firmware (STANDALONE) [Y/n/?] y
Prevent firmware from being built (PREVENT_FIRMWARE_BUILD) [Y/n/?] y
Userspace firmware loading support (FW_LOADER) [Y/?] y
Include in-kernel firmware blobs in kernel binary (FIRMWARE_IN_KERNEL) [Y/n/?] y
External firmware blobs to build into the kernel binary (EXTRA_FIRMWARE) []
Driver Core verbose debug messages (DEBUG_DRIVER) [N/y/?] n
Managed device resources verbose debug messages (DEBUG_DEVRES) [N/y/?] n
Enable a generic cross-process locking mechanism (GENLOCK) [N/y/?] (NEW) y
Enable a misc-device for userspace to access the genlock engine (GENLOCK_MISCDEVICE) [N/y/?] (NEW) y

I chose yes for all those options
Click to expand...

attached is the config I am using, you can rename it to .config

edit : never mind file is too big

here it is

myconfig2.txt
 
hroark13 said:
attached is the config I am using, you can rename it to .config

edit : never mind file is too big

here it is

myconfig2.txt
Click to expand...

So I add that to my new kernel folder, then copy prevailconfig from my kernelorig folder?

Edit:Enable a generic cross-process locking mechanism (GENLOCK) [N/y/?] (NEW) n
What does this mean? Should I have chose yes?
 
The~Skater~187 said:
So I add that to my new kernel folder, then copy prevailconfig from my kernelorig folder?
Click to expand...


you only use one config and that is the file named .config

use which ever one you want, if you want to use mine rename myconfig2.txt to .config

if you want to use your copy it to the folder and rename it to or copy it to .config

you could download the myconfig2.txt and rename that .config

you will also need these pre-built rfs and fsr modules

modules _2_6_35_14_SAM_SPH_M820.zip
 
here are all the modules (except ext4)

if you are to lazy to strip them your self

the only modules we can not make are the RFS and FSR modules
 
The~Skater~187 said:
Once I downlaod and extract them, do i add them to the kernel, or the Ramdisk?
Click to expand...


modules are for the ram disk

hroark13 said:
stock or ctmod based roms are not gonna show the second part of the kernel version



on CM7 it does

the hroak13 is my Linux login name and the hroark13-d is the Linux workstation name

we are limited on what we can make the first part of the kernel string say

because we can not compile the FSR or RFS modules
(my new CM7 kernel; does not include RFS, I did not include them)


we can edit them with a hex editor and change them, but we can not change the length of the "vermagic" string


for my latest .14 kernel I took the 2 FSR modules from the TASS kernel that had this string

vermagic=2.6.35.7-perf-CL787041

and with hex editor changed it to

vermagic=2.6.35.14-SAM-SPH-M820


as you can see they have the same number of characters

you then have to make sure the kernel zImage you compile has the exact string

I did this by editing the make file like this


VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 35
EXTRAVERSION = .14-SAM-SPH-M820
NAME = Yokohama
Click to expand...
 
I'm going to try now. I added the modules and I'm compiling, but I keep getting this about a Generic drivers:

* Generic Driver Options
*
path to uevent helper (UEVENT_HELPER_PATH) []
Maintain a devtmpfs filesystem to mount at /dev (DEVTMPFS) [N/y/?] n
Select only drivers that don't need compile-time external firmware (STANDALONE) [Y/n/?] y
Prevent firmware from being built (PREVENT_FIRMWARE_BUILD) [Y/n/?] y
Userspace firmware loading support (FW_LOADER) [Y/?] y
Include in-kernel firmware blobs in kernel binary (FIRMWARE_IN_KERNEL) [Y/n/?] y
External firmware blobs to build into the kernel binary (EXTRA_FIRMWARE) []
Driver Core verbose debug messages (DEBUG_DRIVER) [N/y/?] n
Managed device resources verbose debug messages (DEBUG_DEVRES) [N/y/?] n
Enable a generic cross-process locking mechanism (GENLOCK) [N/y/?] (NEW) y
Enable a misc-device for userspace to access the genlock engine (GENLOCK_MISCDEVICE) [N/y/?] (NEW) y
 
The~Skater~187 said:
I'm going to try now. I added the modules and I'm compiling, but I keep getting this about a Generic drivers:

* Generic Driver Options
*
path to uevent helper (UEVENT_HELPER_PATH) []
Maintain a devtmpfs filesystem to mount at /dev (DEVTMPFS) [N/y/?] n
Select only drivers that don't need compile-time external firmware (STANDALONE) [Y/n/?] y
Prevent firmware from being built (PREVENT_FIRMWARE_BUILD) [Y/n/?] y
Userspace firmware loading support (FW_LOADER) [Y/?] y
Include in-kernel firmware blobs in kernel binary (FIRMWARE_IN_KERNEL) [Y/n/?] y
External firmware blobs to build into the kernel binary (EXTRA_FIRMWARE) []
Driver Core verbose debug messages (DEBUG_DRIVER) [N/y/?] n
Managed device resources verbose debug messages (DEBUG_DEVRES) [N/y/?] n
Enable a generic cross-process locking mechanism (GENLOCK) [N/y/?] (NEW) y
Enable a misc-device for userspace to access the genlock engine (GENLOCK_MISCDEVICE) [N/y/?] (NEW) y
Click to expand...


just say yes, if you would of used my config (myconfig2.txt) as your .config it should have not asked you about this
 
So I compiled fine, flashed, and this is what I'm getting from the logcat:

- waiting for device -
- exec '/system/bin/sh' failed: No such file or directory (2) -

And it stays at the splash screen.
 
The~Skater~187 said:
So I compiled fine, flashed, and this is what I'm getting from the logcat:

- waiting for device -
- exec '/system/bin/sh' failed: No such file or directory (2) -

And it stays at the splash screen.
Click to expand...


did you use the new modules ?

did you change any of the version strings?
 
The~Skater~187 said:
The only things I did was add your .config to the hpkf/kernel folder, then I added the modules to the lib/modules folder of the ramdisk and compiled.
Click to expand...


is your hpkf/kernel folder the new .14 source

can you open the make file and tell me what it says at the top
 
what is your ramdisk, is it kouma's


if so you dont want to use the ext4 modules

the config i gave you has built in ext4 so we dont need the modules

you will need to edit the init.rc to remove the insmod line for the ext4.ko and jbd2.ko and make sure those two files are not in there

and if you want to remove the two rfs module lines and files too you can

i do on my cm7 kernel
 
hroark13 said:
is your hpkf/kernel folder the new .14 source

can you open the make file and tell me what it says at the top
Click to expand...

Yupp, hpkf/kernel is the new .14 source.
This is the top of the Makefile:

VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 35
EXTRAVERSION = .14-SAM-SPH-M820
NAME = Yokohama
 
hroark13 said:
what is your ramdisk, is it kouma's


if so you dont want to use the ext4 modules

the config i gave you has built in ext4 so we dont need the modules

you will need to edit the init.rc to remove the insmod line for the ext4.ko and jbd2.ko and make sure those two files are not in there

and if you want to remove the two rfs module lines and files too you can

i do on my cm7 kernel
Click to expand...

i actually think my Ramdisk is from your unofficial 1.3

These are the rfs module lines in the init.rc that you were reffering to?

insmod /lib/modules/rfs_glue.ko
insmod /lib/modules/rfs_fat.ko

I can just delete them?
 
The~Skater~187 said:
i actually think my Ramdisk is from your unofficial 1.3

These are the rfs module lines in the init.rc that you were reffering to?

insmod /lib/modules/rfs_glue.ko
insmod /lib/modules/rfs_fat.ko

I can just delete them?
Click to expand...


yes those are them

if you rom is ext4 you really don't need them

I removed them

also if your are insmodding the ext4.ko and jbd2.ko that woulf probably conflict with you zImage
 
if after cleaning up and re-create, if it does not boot

download my 2.6.35.14 kernel

unpack it, and copy the zImage to arch/arm/boot

and and then re-pack with your ram disk


what we want to do is see if it is a problem with your ramdisk or with your zImage
 
hroark13 said:
you do not need RFS if you are running ext4 on all your partitions

if you have a partiton that is formatted as RFS than you need them

you do need the FSR those are needed no matter what what you run
Click to expand...

Figured it out. I copied your .config to the kernelorig folder and not the kernel folder.
I got it to fully boot. :D

So the rfs_fat.ko isn't needed? I thought that had something to do with mounting the sdcards fat partition?
 
The~Skater~187 said:
Figured it out. I copied your .config to the kernelorig folder and not the kernel folder.
I got it to fully boot. :D

So the rfs_fat.ko isn't needed? I thought that had something to do with mounting the sdcards fat partition?
Click to expand...


kernel has built in FAT support


RFS is very similar to FAT, it is just Samsungs implementation of it

on a stock ROM

sdcard is fat and most internal partitions are RFS
 
if you want your kernel version to say something else you can do this

change the top of the make file to look like this

FROM

VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 35
EXTRAVERSION = .14-SAM-SPH-M820
NAME = Yokohama

TO


VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 35
EXTRAVERSION = .14-GENOCIDE_187
NAME = Yokohama


change it to what you want, but after the .14-

you can only use 12 characters



you will then have to hexedit each of the modules you will be using in your ram disk


like this


before

Offset 0 1 2 3 4 5 6 7 8 9 A B C D E F

00025650 72 69 65 74 61 72 79 00 64 65 70 65 6E 64 73 3D rietary.depends=
00025660 66 73 72 00 76 65 72 6D 61 67 69 63 3D 32 2E 36 fsr.vermagic=2.6
00025670 2E 33 35 2E 31 34 2D 53 41 4D 2D 53 50 48 2D 4D .35.14-SAM-SPH-M
00025680 38 32 30 20 70 72 65 65 6D 70 74 20 6D 6F 64 5F 820 preempt mod_


after

Offset 0 1 2 3 4 5 6 7 8 9 A B C D E F

00025650 72 69 65 74 61 72 79 00 64 65 70 65 6E 64 73 3D rietary.depends=
00025660 66 73 72 00 76 65 72 6D 61 67 69 63 3D 32 2E 36 fsr.vermagic=2.6
00025670 2E 33 35 2E 31 34 2D 47 45 4E 4F 43 49 44 45 2D .35.14-GENOCIDE-
00025680 31 38 37 20 70 72 65 65 6D 70 74 20 6D 6F 64 5F 187 preempt mod_
 
shot_000008.jpg
Just a preview. ;)
What do you use for a hex editor?
 
You must log in or register to reply here.
Back
Top Bottom