[Q] Help!! wifi error after loading compiled franco kernel

[shashi_hv]

Suggestion: restore the stock init **** and leave it alone. There is absolutely no need to mess with that to get WiFi working on any ROM. Others, like tun.ko, you need to load manually via initscript or whatever. Go fix your kernel compile and it will just work.

init is already restored by flashing openOptimus GB ROM!! I just tried to flash the kernel zip over it, thats all!!

To compile stock kernel, I used following commands:

1. make thunderg-perf_defconfig
2. make zImage -j4
3. make modules

and to compile franco, just copy the .config to source root directory

1. make zImage -j4
2. make modules

I did not changed any of the settings at all!!

signed zip was created using koush's AnyKernel method using standard practises of replacing zImage, other *.ko modules and signed it!!

I tried this method on openOptimus ROM without any mod to init ****s!!! Because franco's kernel was already working with this ROM!!!

I dont know where I could go wrong here!!!

 

[dr.notor]

Apparently your compiler. Stuff that spits out "executable format error" or similar is clearly miscompiled. NFC what gcc version you are using but get another one.

 

[franciscofranco]

Ok. Let's try and do this as simple as possible.

make clean
make distclean

This **** clears everything that is created on compiling.

Copy the fucking .config to the root folder then

make -j4

It will compile everything (dont need to make zImage then make modules)

After the compile is done copy zImage and wireless.ko to the flashable zip and flash it. Done. If the problem still persists go to the .config and make it OPTIMIZE FOR SIZE instead of using the -Omfguberoptimizationshitflag.

If this **** fails then sir there's nothing we can do.

 

[andy572]

I think, the kernel searches the module in the wrong place.
When using "make modules && make modules install", the kernel search for in
/usr/lib/modules{KERNEL_VERSION}/wireless.ko instead in /system/lib/modules/wireless.ko

 

[dr.notor]

I think, the kernel searches the module in the wrong place.
When using "make modules && make modules install", the kernel search for in
/usr/lib/modules{KERNEL_VERSION}/wireless.ko instead in /system/lib/modules/wireless.ko

insmod /system/lib/modules/wireless.ko needs to work and not spit some nonsensical "exec format error" ****...

modprobe never worked, that searches in /lib/modules/$KVER, someone might finally compile it right in busybox.

 

[franciscofranco]

insmod /system/lib/modules/wireless.ko needs to work and not spit some nonsensical "exec format error" ****...

modprobe never worked, that searches in /lib/modules/$KVER, someone might finally compile it right in busybox.

Something like that happened with my x5 when I tried to force load a module that wasn't compiled for that kernel version, it just laughed at me and sent to **** up.
I think andy has got a point there. What I don't understand is why someone does "make zImage" and then "make modules" while doing a single "make -j4" works fine.
Other than what I said in the explanation post I got no clue.

 

[dr.notor]

Something like that happened with my x5 when I tried to force load a module that wasn't compiled for that kernel version, it just laughed at me and sent to **** up.

IIRC that spews up some "wrong version magic" error, not this. At least on Linux.

 

[franciscofranco]

IIRC that spews up some "wrong version magic" error, not this. At least on Linux.

That I do not know, but I'll trust on what you say. Either way I hope the OP can fix that problem, we already gave him all the possible solutions I can think of.

 

[dr.notor]

That I do not know, but I'll trust on what you say. Either way I hope the OP can fix that problem, we already gave him all the possible solutions I can think of.

Just quickly tried:

insmod: error inserting 'ipv6.ko': -1 Invalid module format
kernel: ipv6: version magic '2.6.35.14-test gcc-4.5' should be '2.6.35.14 gcc-4.5'

is the **** it spits up on console and in dmesg on Linux.

Anyway, no other ideas, sounds like some obvious PEBKAC...

 

[fserve]

how i do that:

make clean
make distclean

make menuconfig <= and mark that Optimized for space option, inside one of those menus.

make -j4

then
update original franco.kernel.zip with

arch/boot/arm/zImage
drivers/balbalbla/net/wireless.ko

Work pretty well. i can get 1.5MB kernel with that. | Same performance.

 

[shashi_hv]

F*(king nonsense still!! No luck for me!!!

I tried fetching the Aug 18th committed source from franco's github.

Did make clean

make distclean

make -j4

I changed only the path of the arm eabi. Nothing else!!

Same results, except wifi everything works!!

Tried on different ROM's, andy's or mik's.. etc!!

I don't want to say I loose, but I will try one more day to get it up!!!

I dont know what is f*(king problem/mistake I am doing!!

 

[shashi_hv]

how i do that:

make clean
make distclean

make menuconfig <= and mark that Optimized for space option, inside one of those menus.

make -j4

then
update original franco.kernel.zip with

arch/boot/arm/zImage
drivers/balbalbla/net/wireless.ko

Work pretty well. i can get 1.5MB kernel with that. | Same performance.

I get around 1.8 MB kernel, not 1.5 MB!!

 

[shashi_hv]

I think, the kernel searches the module in the wrong place.
When using "make modules && make modules install", the kernel search for in
/usr/lib/modules{KERNEL_VERSION}/wireless.ko instead in /system/lib/modules/wireless.ko

My biggest question is who loads the modules at boot time?? Can it be controlled thro' any config or a script, so that we can set the search path??

 

[dr.notor]

My biggest question is who loads the modules at boot time?? Can it be controlled thro' any config or a script, so that we can set the search path??

Well no, until you can load the module manually, your biggest problems is the broken **** you are flashing. After that, you will have no problems with loading the module, it just works. For everyone.

 

[shashi_hv]

Thanks notor!!

I shall try so!!!

 

[dr.notor]

This will loads any modules you have. Stick it to /system/etc/init.d/10modules or whatever and chmod 777. Anyway, it will definitely not help in any way unless insmod /system/lib/modules/wireless.ko really works without any errors.

#!/system/bin/sh
#
# Load any extra modules

MODULES="$(ls /system/lib/modules)"
MODULES_DIR="/system/lib/modules"

if [ ! -d $MODULES_DIR ]
then
    exit 0
fi

if [ -z "$MODULES" ]
then
	exit 0
fi

for i in $MODULES
do
	insmod $MODULES_DIR/$i >/dev/null 2>&1
done

exit 0

 

[andy572]

Why insmod modules manually or in a shell script? the kernel is clever enough to load modules through udev when needed ... there is no need for such scripts but have a
experimental module to load!

 

[franciscofranco]

Which toolchain are you using?

Sent from my Huawei u8800 using XDA Premium App

 

[dr.notor]

Why insmod modules manually or in a shell script? the kernel is clever enough to load modules through udev when needed ... there is no need for such scripts but have a
experimental module to load!

udev? On Android?

 

[shashi_hv]

Which toolchain are you using?

Sent from my Huawei u8800 using XDA Premium App

I think the tool chain was the problem(Which I had copied from my friend!!).

But nevertheless, I replaced the tool chain with code sourcery one, and I could build one properly with it!!

I think the tool chain was from the android ndk!!!