Marco345

Hello, In s905w kernel 4.16.1 the internal emmc is not recognized. I get [ 1.863928] mmc1: tuning execution failed: -5 [ 1.863953] mmc1: error -5 whilst initialising MMC card I recompiled the kernel (balbes150 github), for usbserial support and all the mmc drivers. The other modules are installed ok, but mmc_core gives error as follow: mmc_core: Unknown symbol of_node_put (err 0) Does anybody anyone have any idea?

dmesg for this device is [ 2.618612] amlogic-new-usb2 d0078000.usb2phy: USB2 phy probe:phy_mem:0xd0078000, iomap phy_base:0xffffff800059a000 [ 2.618896] amlogic-new-usb3 d0078080.usb3phy: This phy has no usb port [ 2.618931] amlogic-new-usb3 d0078080.usb3phy: USB3 phy probe:phy_mem:0xd0078080, iomap phy_base:0xffffff800059c080

I get the following in lsusb command Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Devices connected to Bus 001 are working. Does it mean that there is usb3 root hub inside, or there is something wrong with the DTB file? I have checked all devices like mine in internet, and all seems to have USB 2 Hi-speed, not USB 3.

I am using a Dtb file that i have extracted from android firmware for this device. That is the only dtb file that the emmc is recognized. I have tried with other dtb files for p201 p212 and other but the usb problems are the same. I have even tried to edit the dtb files combining values from different dtbs but without success. Have anyone success with any dtb for this device?

@balbes150 thank you! I have a box MXQ PRO 4K S905W P281 and tried kernel 3.14 and 4.16. They both works but: In kernel 3.14 Usb 3.0 is not working, so 3 from 4 Usb ports are not working. Only the usb 2.0 port is ok. The usb3 hub is listed in lsusb. In kernel 4.16 all usb ports are ok, all connected devices are listed in lsusb, but devices like usb bluetooth or usb hspda modem are not working. These devices are listed correctly in lsusb but are not creating ttyUSB ports. In modprobe usbserial is missing. Does anyone have any idea how to fix the problem in kernel 3.14 or 4.16?