Hello, i have the same issue than diplomatic with the ssv6051 driver .I have the tv box Mecool m8s pro W. I can't use the command ifconfig wlan0 up, and WIFI doesn't work. How can i fix this problem? Maybe i have to upload the s905W dtb from Android. How could i decompile that dtb?
Thanks, your work is really amazing
Display MoreHello community,
Just wanted to report that, after some needed tinkering, I successfully installed LE on a Mecool M8S Pro W. Thank you, wrxtasy and kszak, for compiling and posting this. In a nutshell, Kodi on LE is a light-year ahead of the Android version.
I also want to report a problem with the gxl_p281_2g.dtb device tree. The problem is that, well, it's just an exact copy of the gxl_p281_1g.dtb file. It did not work on my 2gb S905W device. (Just got stuck at boot logo.) There are no provisions for 2gb RAM. So, long story short, I ended up fixing the 2g DT by comparing the 1g and 2g DT blobs from my device and applying the changed bytes to gxl_p281_1g.dtb. There were only 3 or 4 instances that needed to be applied. In the end, it worked like a charm. I'm attaching my gxl_p281_2g.dtb here.
There's also an issue with the ssv6051 driver. The kernel keeps spamming the log with these things...
Code Display More[ 126.184671@0] [aml_sd_emmc_irq] sdio: warning... data crc, vstat:0xa3ffa008, virqc:3fff [ 126.184688@0] [aml_sd_emmc_irq] @ cmd 53 with ffffffc05ea97a88; stop 0, status 4 [ 126.184699@0] [aml_host_bus_fsm_show] sdio: err: wait for irq service, bus_fsm:0x8 [ 126.184729@0] aml_sd_emmc_data_thread 2639 sdio: cmd:53 [ 126.184753@2] SSV6XXX_SDIO sdio:0001:1: sdio read failed size ret[-84] [ 126.184761@2] _do_rx(): IF_RECV() retruns -84 (dlen=352) [ 126.389450@0] [aml_sd_emmc_irq] sdio: warning... data crc, vstat:0xa3ffa008, virqc:3fff [ 126.389466@0] [aml_sd_emmc_irq] @ cmd 53 with ffffffc05ea97a88; stop 0, status 4 [ 126.389475@0] [aml_host_bus_fsm_show] sdio: err: wait for irq service, bus_fsm:0x8 [ 126.389485@0] aml_sd_emmc_data_thread 2639 sdio: cmd:53 [ 126.389508@2] SSV6XXX_SDIO sdio:0001:1: sdio read failed size ret[-84] [ 126.389515@2] _do_rx(): IF_RECV() retruns -84 (dlen=352) [ 126.594254@0] [aml_sd_emmc_irq] sdio: warning... data crc, vstat:0xa3ffa008, virqc:3fff [ 126.594271@0] [aml_sd_emmc_irq] @ cmd 53 with ffffffc05ea97a88; stop 0, status 4 [ 126.594281@0] [aml_host_bus_fsm_show] sdio: err: wait for irq service, bus_fsm:0x8 [ 126.594303@0] aml_sd_emmc_data_thread 2639 sdio: cmd:53 [ 126.594327@2] SSV6XXX_SDIO sdio:0001:1: sdio read failed size ret[-84] [ 126.594335@2] _do_rx(): IF_RECV() retruns -84 (dlen=352) [ 126.799030@0] [aml_sd_emmc_irq] sdio: warning... data crc, vstat:0xa3ffa008, virqc:3fff [ 126.799048@0] [aml_sd_emmc_irq] @ cmd 53 with ffffffc05ea97a88; stop 0, status 4 [ 126.799060@0] [aml_host_bus_fsm_show] sdio: err: wait for irq service, bus_fsm:0x8 [ 126.799082@0] aml_sd_emmc_data_thread 2639 sdio: cmd:53 [ 126.799106@2] SSV6XXX_SDIO sdio:0001:1: sdio read failed size ret[-84] [ 126.799115@2] _do_rx(): IF_RECV() retruns -84 (dlen=352)
These cycles of lines are written many times a second. When I remove the driver with modprobe -r ssv6051, the spam stops instantly. I don't use wifi on this, so I can't speak for how the driver works in general.