T-R42 owners...please help! which is your wifi chip?

[vicolodo]

Hello T-R42 owners,

i have a problem with wifi: it does not work more

BUT perhaps you could help me and others with similar problems:

open the terminal and type: cat /sys/class/rkwifi/chip

and post the result on this thread , adding the model and board version you have (if you know it)

Thanks a lot!

[bill-ns]

T-R42 v1.0

chip = RK901

Bill

[vicolodo]

T-R42 v1.0

chip = RK901

Bill

Thank you

[buhohitr]

Same here:
T-R42 v1.0
chip = RK901

[makku71]

t-r42

Hi !
My Board is a T-R42 V1.0 B351V1.0 2013/08/01
and the output sys
RK901 like the others

[vicolodo]

Hi !
My Board is a T-R42 V1.0 B351V1.0 2013/08/01
and the output sys
RK901 like the others

Thank you!

[vicolodo]

Same here:
T-R42 v1.0
chip = RK901

thank you!
i found that RK901 is hard-coded into the kernel, as you can read here:
it depends on the parameters used compiling the kernel:

in fact i found this:
https://github.com/gripped/MK808-hea...fi_sys_iface.c

i am not an expert, but i think that is the kernel procedure that writes the attributes of the class for wifi on the file system,
one of which is the file /sys/class/rkwifi/chip

the fact that we have all RK901 is because all (almost) our kernels have been compiled with the configuration
#ifdef CONFIG_RK901

I dont know if my device instead should use a different kernel (compiled with other configuration),
but i think that probably RK901 is the right value also for my device

This because i think that the cause of my problem is different:
seems that the problem is caused by an error returned by the insmod (insert module) procedure
(called by the load driver procedure ,
that perhaps it is something like what can be found here
https://github.com/aloksinha2001/picuntu-3.0.8-alok/blob/master/RK30_MT5931_MT6622/wifi/wifi.c
)

The insmod function does these two things:
- allocates memory for the driver and loads the file (rkwifi.ko) on this area:

module = load_file(filename_release, &size);

- initialize the module
ret = init_module(module, size, args);

One of this two events went wrong, because i am sure insmod in my case returns -1

I went to this conclusion following the logcat trace and searching infomations on the web, as you can see here
http://www.freaktab.com/showthread.p...-is-the-answer

i read somewhere that the init_module may return error when the user has not the permission to insert the module into the kernel...

so can be that some permission is missing ...like a problem caused by rooting, where i have no more root permissions after flashing the ROM...or something like that...

do you have any suggestion?

Thanks a lot!