yashsingh1/xdaforums huggingface dataset:
[Galaxy S Plus I9001 Android Development] robert_jacketti:
Are you open for suggestions to add to your kernel?

If you are I would like to suggest Back Light Notification!

it will make the menu and back button light up when you receive a message or something, this way even when you have your sound turned of and your screen off, you see that you have a message.

http://xdaforums.com/showthread.php?t=1080529

In section source you will find the github which contains a howto, to show how to implement this in a gingerbread kernel.
[Galaxy S Plus I9001 Android Development] drummer1839:
... voodoo sound would be nice :)
[Galaxy S Plus I9001 Android Development] dbx4:
The developer of voodoo writes in his description on google play:

:(
[Galaxy S Plus I9001 Android Development] Costinutz32:
Congrats!

I have the same problem you had,after recompiling it hangs at samsung :|.....:(.

I am trying to modify Vitality Kernel (from the open source of course).
[Galaxy S Plus I9001 Android Development] spawk:
Work on cm7 ? Radio is présent ? Thank for UR job
[Galaxy S Plus I9001 Android Development] broodplank1337:
Compiled from samsung sources, so don't think it's compatible with CM7
[Galaxy S Plus I9001 Android Development] broodplank1337:
If anyone wants to try out:

http://www.mediafire.com/?gdv4t19octq4iyh

but basically it's just stock
[Galaxy S Plus I9001 Android Development] chasemyass:
maybe you can have a look at cm7 kernel sources, the ones that are uploaded on github founded at this post?
[Galaxy S Plus I9001 Android Development] broodplank1337:
Ok thnx :)
[Galaxy S Plus I9001 Android Development] chasemyass:
no no...I say thanx ...

You are becoming an total developer if you are keepin` this way lol...

OT I`m at the point where I need to buy another ~100 Gb HDD to run Linux on it ... I`m starting to learn more abt theese too ... lol
[Galaxy S Plus I9001 Android Development] broodplank1337:
Hehe ^^

I want to become a real developer one day, and I think that won't be a big problem :D I just ran it from an ubuntu virutal machine lol. takes a while to compile, but it worked :P
[Galaxy S Plus I9001 Android Development] xewier:
please write the fully instruction
[Galaxy S Plus I9001 Android Development] broodplank1337:
To be honest, the instructions are not much more then this:

1. Install ubuntu, setup a user account besides root

2. Start terminal and do this:

sudo apt-get update
sudo apt-get install git unrar libncurses5-dev qt3-dev-tools
git clone https://android.googlesource.com/platform/prebuilt.git

This will download the needed things to compile

3. Now download the i9001 open source kernel from opensource.samsung.com

extract the GT-I9001_Kernel.tar.gz to the root and go in the terminal again, enter this to extract it to /kernel:

tar xvfz GT-I9001_Kernel.tar.gz

4. Now set the variables in the terminal, so that it will look in the right directory:

export ARCH=arm
export CROSS_COMPILE=arm-eabi-
export PATH=$PATH:~/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/

5. Now enter the following commands in the terminal:

cd kernel
make xconfig
make -j4

xconfig = a graphical interface for the kernel configuration

make -j4 = compile with 4 cores

Then you will get a zImage in /kernel/arch/arm/boot/.

I copied that zImage to an extracted boot.img in kitchen, and replaced it, then packed it again.
[Galaxy S Plus I9001 Android Development] xewier:
How to make overclock?
[Galaxy S Plus I9001 Android Development] broodplank1337:
No idea.. just found out how to compile it
[Galaxy S Plus I9001 Android Development] xewier:
okay thanx brood
[Galaxy S Plus I9001 Android Development] dbx4:
Study how manveru0 did it:

https://github.com/manveru0/FeaCore_Phoenix/commit/5dcb208453600f1d4882ea50b77d19bc81e40689

The basic idea is to extend the CPU frequency table with more higher values.

Before:

static struct cpufreq_frequency_table freq_table[] = {
{ 0, 122880 },
{ 1, 245760 },
{ 2, 368640 },
{ 3, 768000 },
/* 806.4MHz is updated to 1024MHz at runtime for MSM8x55. */
{ 4, 806400 },
{ 5, CPUFREQ_TABLE_END },
};

After:

static struct cpufreq_frequency_table freq_table[] = {
{ 0, 122880 },
{ 1, 245760 },
{ 2, 368640 },
{ 3, 768000 },
/* 806.4MHz is updated to 1024MHz at runtime for MSM8x55. */
{ 4, 806400 },
{ 5, 1017600 },
{ 6, 1113600 },
{ 7, 1209600 },
{ 8, 1305600 },
{ 9, 1401600 },
{ 10, 1497600 },
{ 11, 1516800 },
{ 12, 1612800 },
{ 13, 1708800 },
{ 14, 1804800 },
{ 15, CPUFREQ_TABLE_END },
};
[Galaxy S Plus I9001 Android Development] nikku_hot123:
And what are the commits for undervolt???? As i had also compiled a stock kernel successfully but i was not able to overclock and undervolt. Thanks for.the values^^
[Galaxy S Plus I9001 Android Development] Blumdum:
look through these lines

https://github.com/manveru0/FeaCore_Phoenix/commit/5dcb208453600f1d4882ea50b77d19bc81e40689

there you can find a small table:

+ { 806400, PLL_2, 3, 0, 192000000, 1050, VDD_RAW(1050) },
131
+ { 1017600, PLL_2, 3, 0, 192000000, 1100, VDD_RAW(1100) },
132
+ { 1113600, PLL_2, 3, 0, 192000000, 1125, VDD_RAW(1125) },
133
+ { 1209600, PLL_2, 3, 0, 192000000, 1150, VDD_RAW(1150) },
134
+ { 1305600, PLL_2, 3, 0, 192000000, 1175, VDD_RAW(1175) },
135
+ { 1401600, PLL_2, 3, 0, 192000000, 1200, VDD_RAW(1200) },
136
+ { 1497600, PLL_2, 3, 0, 192000000, 1225, VDD_RAW(1225) },
137
+ { 1516800, PLL_2, 3, 0, 192000000, 1250, VDD_RAW(1250) },
138
+ { 1612800, PLL_2, 3, 0, 192000000, 1250, VDD_RAW(1250) },
139
+ { 1708800, PLL_2, 3, 0, 192000000, 1275, VDD_RAW(1275) },
140
+ { 1804800, PLL_2, 3, 0, 192000000, 1300, VDD_RAW(1300) },

i think these lines are respective for undervolting

but i would do all those changes to an other kernel for a proper oc/uv
[Galaxy S Plus I9001 Android Development] nikku_hot123:
I am asking about undervolted values because i think many users are having problem in running overclocked kernels (including me:rolleyes:) but surprisingly skyhigh 1.3 kernel is running flawlessly which is also oc. I pm`d skyhigh but he is also not having answers. So i would like to compare voltage table. and i need favor from you guys..:):)
[Galaxy S Plus I9001 Android Development] Blumdum:
i think i posted the voltage table just look in the fifth row

the number in the first row is the cpu clock

so 806,4mhz -> 1050mV

.....

1804,8mhz -> 1300mV

i could be wrong...

EDIT:

here is the voltage table of skyhigh kernel

768mhz -> 1050mV

806,4mhz -> 1050mV

1017,6mhz -> 1100mV

1113,6mhz -> 1125mV

1209,6mhz -> 1150mV

1305,6mhz -> 1175mV

1401,6mhz -> 1200mV

1497,6mhz -> 1225mV

1516,8mhz -> 1250mV

1623,8mhz -> 1275mV

1708,8mhz -> 1300mV

1804,8mhz -> 1325mV

so skywalker01 has only different voltages in the clock speed 1623,8mhz -> 1804,8mhz
[Galaxy S Plus I9001 Android Development] nikku_hot123:
I will compare and tell later....
[Galaxy S Plus I9001 Android Development] chasemyass:
the non supported OC could came from MotherBoard too .. it`s made to not accept OC/OV/UV running kernels ... as far as I saw all phones that camed from service stopped accepting OC kernels ... :)
[Galaxy S Plus I9001 Android Development] nikku_hot123:
I do agree with you ...and i have also survived a brick:banghead:

But the point is that skyhigh 1.3 is working..:rolleyes:
[Galaxy S Plus I9001 Android Development] chasemyass:
Test UV values...and ask someone to repack skyhigh 1.4 with same values...Even if I think that skywalker didn't change those so the problem could be from other variables

Sent from my GT-I9001
[Galaxy S Plus I9001 Android Development] skywalker01:
Pointless to recompile SkyHigh 1.4 on that matter since chasemyass is absolutetly right:

OC and UV values are EXACTLY the same in V1.3 and V1.4x !

Not true. Although your message was quite spartan (this was your WHOLE message: "hey man...we are missing you too much..i have a question why in all overclocked kernels whether its ics or gingerbread only yours skyhigh 1.3 kernel is booting for me and none of the oc kernels are working ....plz help") I gave you some details you don't even refer to once:

"Hi,

sorry, but I really can't continue my xda development activities for an indefinite time.

Unfortunately I can't be of much help either in your specific case, the only facts I can give you are those that I already explained in post #190 of my SkyHigh thread:

http://xdaforums.com/show...&postcount=190

If SkyHigh 1.3 works for you then the latest FeaCore version (which comes with FeaMod 1.4) should also work since it is very similar due to OC and UV settings.

If the latest FeaCore doesn't work for you it is also a miracle to me that I can't explain.

With one exception perhaps: it may be the cpu governor which is set to ondemand in all kernels that I am aware of. All other custom ROMs and kernels use an init.d script or an android app to change it to another governor which happens very late in the boot process.

SkyHigh has smartassV2 as default governor hard coded into the kernel core, but this is also true for V1.4x which also doesn't work for you as I understand it.

So it's still a quite mysterious behaviour.

Regards,

skywalker01"

While it still is a quite mysterious behaviour there are several possible reasons for that and I will extend my answer now since I (accidentally) found much more information here in this thread that you didn't give me by pm:

1. cpu governor as mentioned in my pm

2. startup sequence (= ram disk) of the kernel which is COMPLETELY different between V1.3 and V1.4 and I also mentioned that in my SkyHigh thread

3. other parameters in the kernel core (which is very unlikely since most parameters in V1.3 are very similar to the last FeaCore version but which doesn't work for you)

You should concentrate first on governor since this is done quickly. Then on the ram disk which holds a lot of stuff. Especially compare the init.rc and init.qcom.rc files of both versions and all scripts that are called from within !

A last hint to broodplank: the kernel core is completely compatible to CM7, the decisive difference here is also the startup sequence in the ram disk.

I already mentioned that fact several times but nobody seems to notice it.

Just compare the ram disk of the official Sky High V1.3 release and the ram disk of my CM7 alpha build release, which has the same SkyHigh V1.3 kernel core.

Except for the CM7 headphone fix. This will make stock and AOSP kernels incompatible, but this doesn't affect the ability to boot ;-)

Most important difference: you have to use different versions of the init binary file.

Hope that helps,

skywalker01
[Galaxy S Plus I9001 Android Development] EternalFame:
Where do I have to copy the GT-I9001_Kernel.tar.gz ?

I tried on the Datasystems where the folders like bin, dev, root, .. are but the terminal says :" Could not execute open." It says that it cant find the file.?

Then i copied the .tar.gz to the root folder in Datasystem but it shows the same error ):
[Galaxy S Plus I9001 Android Development] EternalFame:
OK guys i am now able to extract the .tar.gz to /kernel xD

i tried just to compile it without any changes and set the variable but when i run the make xconfig

it gives me errors ):
[Galaxy S Plus I9001 Android Development] dbx4:
You do realize you need a compiler if you want to compile something, right? :D

sudo apt-get install build-essential
[Galaxy S Plus I9001 Android Development] oisis:
It is working for ICS so maybe for you will be helpfull:

1. Split the boot.img from update.zip and created new ramdisk img

split_bootimg.pl boot.img
mkdir ramdisk
cd ramdisk
gzip -dc ../boot.img-ramdisk.gz | cpio -i

Swap kernel and modules and then:

find . | cpio -o -H newc | gzip > ../newramdisk.cpio.gz

2. Create new boot img using built zImage and newramdisk.cpio.gz

mkbootimg --kernel zImage --ramdisk newramdisk.cpio.gz --base
0x00400000 -o newtestboot.img

3. Change name from newtestboot.img to boot.img

mv newtestboot.img boot.img

4. Swap boot.img in some zip pkg with kernel.

5. Install your new kernel and try to startup phone.

Hint:

When i'm compiling kernel i'm doing in this way:

make ARCH=arm mrproper -j3
make ARCH=arm clean -j3
adb pull /proc/config.gz ./
gzip -d ./config.gz
mv ./config ./.config
make ARCH=arm oldconfig -j3
make ARCH=arm menuconfig -j3
make ARCH=arm -j3

Then it is easlier:

mkdir -p ../kernel-out/modules
cp arch/arm/boot/zImage ../
find ./ -name "*.ko" -exec cp {} ../kernel-out/modules \;

Download: split_bootimg, mkbootimg

Put extracted files in /usr/local/bin and set permissions to 755.
[Galaxy S Plus I9001 Android Development] EternalFame:
now at the make command after some time this appears:

and there is no new zimage );
[Galaxy S Plus I9001 Android Development] oisis:
On screenshoot is not enough log to say something. Compilation error was before but i cannot see it.
[Galaxy S Plus I9001 Android Development] EternalFame:
markus@markus-linux:~/kernel/kernel$ make -j2
scripts/kconfig/conf -s arch/arm/Kconfig
CHK include/linux/version.h
CHK include/generated/utsrelease.h
UPD include/generated/utsrelease.h
make[1]: »include/generated/mach-types.h« ist bereits aktualisiert.
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
CC init/version.o
LD init/built-in.o
CC kernel/panic.o
In file included from kernel/panic.c:64:
kernel/../arch/arm/mach-msm/smd_private.h:79:2: error: #error No SMD Package Specified; aborting
kernel/panic.c:66:33: error: mach/msm_iomap-7xxx.h: No such file or directory
kernel/panic.c:67:28: error: mach/msm_iomap.h: No such file or directory
kernel/panic.c: In function 'panic':
kernel/panic.c:81: warning: unused variable 'i'
kernel/panic.c:203: warning: 'noreturn' function does return
make[1]: *** [kernel/panic.o] Fehler 1
make: *** [kernel] Fehler 2
make: *** Warte auf noch nicht beendete Prozesse...
CC [M] fs/coda/psdev.o
CC [M] fs/coda/cache.o
In file included from fs/coda/cache.c:21:
include/linux/coda.h:223: error: expected specifier-qualifier-list before 'u_quad_t'
make[2]: *** [fs/coda/cache.o] Fehler 1
make[2]: *** Warte auf noch nicht beendete Prozesse...
LD fs/configfs/built-in.o
In file included from fs/coda/psdev.c:45:
include/linux/coda.h:223: error: expected specifier-qualifier-list before 'u_quad_t'
CC [M] fs/configfs/inode.o
make[2]: *** [fs/coda/psdev.o] Fehler 1
make[1]: *** [fs/coda] Fehler 2
make[1]: *** Warte auf noch nicht beendete Prozesse...
CC [M] fs/configfs/file.o
fs/configfs/file.c: In function 'configfs_read_file':
fs/configfs/file.c:117: warning: format '%zd' expects type 'signed size_t', but argument 3 has type 'size_t'
CC [M] fs/configfs/dir.o
CC [M] fs/configfs/symlink.o
CC [M] fs/configfs/mount.o
CC [M] fs/configfs/item.o
LD [M] fs/configfs/configfs.o
make: *** [fs] Fehler 2
markus@markus-linux:~/kernel/kernel$
[Galaxy S Plus I9001 Android Development] dbx4:
EternalFlame, are you using a working kernel config? And which kernel are you trying to compile (where did you get the source)?

To get a working kernel config, you can get the config of the kernel running on your phone right now (connect phone via usb first):

$ adb pull /proc/config.gz
$ gunzip config.gz
$ mv config /path/to/kernel/source/.config
[Galaxy S Plus I9001 Android Development] oisis:
Exactly, there is something wrong with kernel sources or configuration, follow my faq, make oldconfig etc..
[Galaxy S Plus I9001 Android Development] EternalFame:
I tried to compile from samsung source (:

Sorry for the inconvenience :/
[Galaxy S Plus I9001 Android Development] oisis:
So then follow my FAQ.
[Galaxy S Plus I9001 Android Development] EternalFame:
oisis i tried your hints to compile the kernel

make ARCH=arm mrproper -j3

make ARCH=arm clean -j3

adb pull /proc/config.gz ./

gzip -d ./config.gz

mv ./config ./.config

make ARCH=arm oldconfig -j3

make ARCH=arm menuconfig -j3

make ARCH=arm -j3

but when i do the first prompt it gives me a ****in' error ):

make: /opt/toolchains/arm-2009q3/bin/arm-none-linux-gnueabi-gcc: Command not found

but i have already installed the build essential ... then i tried to download the 2009q3 myself and put it in opt/toolchains/ but its always the same );

i know i am annoying but could you pls pls give me a step to step guide? :/

the only thing i managed to do yet is to extract the GT-I9001_Kernel.tar.gz to /kernel ^^
[Galaxy S Plus I9001 Android Development] oisis:
If you want build kernel for arm you need compiler for arm, build-essential and others system debs for compilations are for x86 that is why you need to download toolchain, extract it somewhere(example /opt/toolchain) and tell your system where it is. To tell your system where it is just add something like this to file ~/.bashrc

export CCOMPILE=/opt/toolchains/arm-2009q3/bin/arm-eabi-
export CROSS_COMPILE=/opt/toolchains/arm-2009q3/bin/arm-eabi-

and check that paths are correct. You can download newest toolchain. Hope it helps to understand of arm compilation idea.
[Galaxy S Plus I9001 Android Development] EternalFame:
damn i was so close :/

it built about 10 minutes and then there was no free space left :/

have to install ubuntu fresh and kick windows away from my hard drive :P

PS: where can i find the var. LOCAL_VERSION?

BTW: thanks oisis for your engagement! you are awesome!
[Galaxy S Plus I9001 Android Development] oisis:
LOCAL_VERSION - don't get it, can you explain?

Installing Ubuntu but i prefer Kubuntu, installation is the same. Download 12.04 LTS.
[Galaxy S Plus I9001 Android Development] EternalFame:
i am more likely to use ubuntu (:

whats the difference between these two?

ps: i mean the var where the name of the kernel which is shown in the phone settings is stored (:
[Galaxy S Plus I9001 Android Development] oisis:
LOCAL_VERSION you can find in kernel settings, general section if I remember but not sure.

Kubuntu has KDE and Ubuntu Gnome. KDE looks more like windows and has more tools, is more configurable.
[Galaxy S Plus I9001 Android Development] dbx4:
You could also set up a virtual system using VirtualBox and install Linux on it.

I would also strongly recommend that you first compile a kernel for your linux system. After you have learned and experienced how it is done, you can then move on to Android which is a bit more complex because of the cross-compilation toolchain involved. An excellent way to really learn Linux would be to install Gentoo Linux. The manual installation procedure of Gentoo will walk you through quite a lot of system internals including compiling a kernel and is quite educational.
[Galaxy S Plus I9001 Android Development] EternalFame:
Thank you..all of you guys (:

I finally managed to compile it to a zImage and my kernel is booting (:

Now i want look a little bit at the sources maybe i can learn something for school (we do C programming and C++) (:

Edit:/ the kernel is really smooth but i cant turn on wifi because of wifi-error ):

Whats wrong?
[Galaxy S Plus I9001 Android Development] oisis:
Look into the wireless network drivers :), try to include drivers bcm4329 from old Arco kernel(2.6.35.7) to new Arco kernel(2.6.35.14) this can be interesting. I was planning to do that but no free time :(.

Old kernel link.

New kernel link.
[Galaxy S Plus I9001 Android Development] EternalFame:
I am compiling for 2.3 so i think it would be better to look at manverus files isnt it?

Do you have an idea which file i have to change for wifi drivers?

/EDIT: kay found it in drivers/net/wireless/bcm4329

have to download his source and i try to change the whole folder with mine (:

could that work?
[Galaxy S Plus I9001 Android Development] oisis:
2.3 has good and working kernel so try to make one for ICS :). drivers are in: drivers/net/wireless/bcm4329/*. Config from AOKP kernel.
[Galaxy S Plus I9001 Android Development] EternalFame:
i am not really interested in 4.0 at the moment i want to learn some things about compiling before i do foreign things (:

but the wifi error drives me nuts ^^

everything is so smooth with this kernel but without wifi its useless xD

do you think that changing the whole bcm4329 with the one from manverus feacore will help?
[Galaxy S Plus I9001 Android Development] oisis:
Don't know, never used manverus feacore before.
[Galaxy S Plus I9001 Android Development] EternalFame:
Hmm..

Is it possible to change folders without changing any other files?

@brood: you compiled from the same source. Do you also have the wlan error? :/
[Galaxy S Plus I9001 Android Development] EternalFame:
**** -.-

the bmc4329 folder was missing in my source so i added the one from manveru0s source and compiled but wifi is still not available -.-

logcat says it cant load wifi drivers but they are in the bmc4329 folder arent they?

W/System.err( 174): android.provider.Settings$SettingNotFoundException: wifi_en
abled
W/System.err( 174): at android.provider.Settings$Secure.getInt(Settings.java
:2293)
W/System.err( 174): at com.android.server.WifiService.setWifiEnabled(WifiSer
vice.java:442)
W/System.err( 174): at android.net.wifi.IWifiManager$Stub.onTransact(IWifiMa
nager.java:199)
W/System.err( 174): at android.os.Binder.execTransact(Binder.java:320)
W/System.err( 174): at dalvik.system.NativeStart.run(Native Method)
D/WifiService( 174): setWifiEnabled: true
D/WifiService( 174): ****************setWifiEnabled(), allowWifi***************
*true
E/WifiSettingButton( 247): onReceive()-S:2
E/WifiHW ( 174): DRV_AP_MODULE_ARG.
E/WifiHW ( 174): WIFI_CONF_PATH. /system/etc/wifi/wifi.conf
E/WifiHW ( 174): DRIVER_MODULE_PATH. /etc/wifi/dhd.ko
E/WifiHW ( 174): insmod load_file "/etc/wifi/dhd.ko"
E/WifiHW ( 174): return of insmod (args:firmware_path=/system/etc/wifi/bcm4329
_sta.bin nvram_path=/system/etc/wifi/nvram_net.txt iface_name=eth0) : ret = -1,
Exec format error
V/WifiSettings( 1108): resetRetryDialogVariable
E/WifiService( 174): Failed to load Wi-Fi driver.
E/WifiSettingButton( 247): onReceive()-S:4
V/WifiSettings( 1108): resetRetryDialogVariable

anyone knows how to fix it?
[Galaxy S Plus I9001 Android Development] oisis:
Just check after kernel compilation you have file bcm4329.ko or dhd.ko if yes that is mean you have wifi module, if not is mean that wifi module is not compiled. Check all path from log maybe you didn't add some needed files for wifi. Try to make another logcat and dmesg then we can have more information about wifi.

In terminal emulator or adb shell make something like that:

dmesg | grep dhd > /sdcard/dhd-dmesg.txt
dmesg | grep bms4329 > /sdcard/bcm4329-dmesg.txt

Check this one file: /system/etc/wifi/wifi.conf also check name of wifi interface in stock rom and in CM7 or rom that you are making kernel for it.
[Galaxy S Plus I9001 Android Development] EternalFame:
the dhd.ko is there in system/etc/wifi but the two text-files from dmesg are empty :/
[Galaxy S Plus I9001 Android Development] dbx4:
There's a version (magic) number mismatch with the dhd.ko module.

See http://xdaforums.com/showthread.php?t=444338

The kernel logs its messages to /proc/kmsg which you can access with the shell command "dmesg". dmesg output will be even more helpful in debugging this issue.

It might help to turn on CONFIG_MODVERSIONS in your kernel config (Loadable module support -> Module versioning support), recompiling and trying again.

It could also make sense to "make mrproper" in the kernel dir which will clean all compiled files and the config, copy your config in there and compile everything from a clean start.
[Galaxy S Plus I9001 Android Development] oisis:
This path is ok?

DRIVER_MODULE_PATH. /etc/wifi/dhd.ko

Are you sure this module is builded by you? Becouse if it is from old kernel it will not work for 100%.

You can also try this:

dmesg | grep wifi > /sdcard/wifi-dmesg.txt

or

dmesg | grep net > /sdcard/net-dmesg.txt

sorry but don't remember now string to search in dmesg, If files will be empty just make this:

dmesg > /sdcard/dmesg.txt

and search whole log for something network related.
[Galaxy S Plus I9001 Android Development] EternalFame:
ok i just compiled feacore pheonix and it boots an so on and so on but its the same wifi error so the source cant be the problem :/

i try the CONFIG_MODVERSIONS thingy (;

PS: i always do mrproper and clean :D

/EDIT: Module verioning support was turned on in config :/