Amlogic S905X2

My RT8153 is identified as 8151 in CE, weird.

CoreELEC:~ # lsusb
Bus 002 Device 005: ID 0bda:8151 Realtek Semiconductor Corp. RTL8151 Adapteon Business Mobile Networks BV

Edit1

I used another USB to Ethernet adapter (Microsoft Surface Ethernet adapter) and this one is working flawlessly. Please note that it has another hardware ID which leads me to this that it is a driver issue.

Edit2
this is the kernel log

[ 175.930965@2] usb 2-1.4: new SuperSpeed USB device number 5 using xhci-hcd
[ 175.951599@2] usb 2-1.4: New USB device found, idVendor=0bda, idProduct=8153
[ 175.951607@2] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[ 175.951609@2] usb 2-1.4: Product: USB 10/100/1000 LAN
[ 175.951612@2] usb 2-1.4: Manufacturer: Realtek
[ 175.951614@2] usb 2-1.4: SerialNumber: 001000001
[ 175.967935@2] usb 2-1.4: Unsupported device
[ 175.968084@2] usb 2-1.4: Unsupported device
[ 176.095409@2] usb 2-1.4: reset SuperSpeed USB device number 5 using xhci-hcd
[ 176.127697@2] r8152 2-1.4:1.0 (unnamed net_device) (uninitialized): Unknown version 0x6010
[ 176.127705@2] r8152 2-1.4:1.0 (unnamed net_device) (uninitialized): Unknown Device
[ 176.127753@2] usb 2-1.4: Unsupported device

According this ubuntu bug discussion, a driver update is required to make the device work and this is the driver patch. I am unfortunately not familiar with CE build process to apply it.

@leptdre I added the patch you found, please try this build and see if it will work.
https://mega.nz/#!AWwWWQQY!K1cbCCW_zlIvapjgDSZ5_kmq-BVB0LBTkI1mFOWY4Tk
Make sure you extract the rar file first, and put the tar into the update folder.

That’s working very good, finally using a usb 3.0 hub + Ethernet. Thank you so much for your hard work.

CoreELEC:~ # iperf -c 192.168.137.1
Connecting to host 192.168.137.1, port 5201
[ 5] local 192.168.137.150 port 44804 connected to 192.168.137.1 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 111 MBytes 929 Mbits/sec 0 423 KBytes
[ 5] 1.00-2.00 sec 113 MBytes 949 Mbits/sec 0 423 KBytes
[ 5] 2.00-3.00 sec 113 MBytes 945 Mbits/sec 0 423 KBytes
[ 5] 3.00-4.00 sec 113 MBytes 944 Mbits/sec 0 423 KBytes
[ 5] 4.00-5.00 sec 113 MBytes 947 Mbits/sec 0 423 KBytes
[ 5] 5.00-6.00 sec 113 MBytes 950 Mbits/sec 0 423 KBytes
[ 5] 6.00-7.00 sec 113 MBytes 947 Mbits/sec 0 423 KBytes
[ 5] 7.00-8.00 sec 112 MBytes 942 Mbits/sec 0 423 KBytes
[ 5] 8.00-9.00 sec 113 MBytes 946 Mbits/sec 0 423 KBytes
[ 5] 9.00-10.00 sec 113 MBytes 945 Mbits/sec 0 423 KBytes


[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 1.10 GBytes 945 Mbits/sec 0 sender
[ 5] 0.00-10.00 sec 1.10 GBytes 943 Mbits/sec receiver

Perfect. I have one of those too, although mine is a 8153. But it refuses to work in USB 3.0 mode, not sure why.

[ 1070.950127@3] usb 2-1.2: New USB device found, idVendor=0bda, idProduct=8153
[ 1070.950130@3] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1070.950132@3] usb 2-1.2: Product: USB 10/100/1000 LAN
[ 1070.950134@3] usb 2-1.2: Manufacturer: Realtek
[ 1070.950135@3] usb 2-1.2: SerialNumber: 00xxxxxxxxxx
[ 1070.960589@3] usb 2-1.2: Unsupported device
[ 1070.962007@3] usb 2-1.2: Unsupported device
[ 1071.070526@3] usb 2-1.2: reset SuperSpeed USB device number 5 using xhci-hcd
[ 1071.158669@3] r8152 2-1.2:1.0 eth1: v1.08.9
[ 1071.191489@4] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 1073.262484@3] r8152 2-1.2:1.0 eth1: Stop submitting intr, status -71
[ 1073.263159@3] usb 2-1.2: usb_reset_and_verify_device Failed to disable LTM
[ 1073.263159@3] .
[ 1073.789566@3] usb 1-1.2: new high-speed USB device number 5 using xhci-hcd
[ 1073.890136@3] usb 1-1.2: New USB device found, idVendor=0bda, idProduct=8153
[ 1073.890139@3] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1073.890141@3] usb 1-1.2: Product: USB 10/100/1000 LAN
[ 1073.890142@3] usb 1-1.2: Manufacturer: Realtek
[ 1073.890144@3] usb 1-1.2: SerialNumber: 00xxxxxxxxxx
[ 1073.918676@3] usb 1-1.2: Unsupported device
[ 1073.918746@3] usb 1-1.2: Unsupported device
[ 1074.011337@3] usb 2-1.2: USB disconnect, device number 5
[ 1074.078491@3] usb 1-1.2: reset high-speed USB device number 5 using xhci-hcd
[ 1074.262373@3] r8152 1-1.2:1.0 eth1: v1.08.9
[ 1074.295488@4] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready

I had one of those in the same form of my current one (3 x USB 3.0 ports + 1 GBe Ethernet port). The Hub is USB 3.0 however the Ethernet card only work at 300 to 350 mbits which lead me to think that either the Ethernet chip is only connected to the hub through a USB 2.0 link or that the there is something faulty in the firmware of the hub itself.

I have an issue playing the Jellyfish (http://jell.yfish.us/) samples on my KM9 Pro. I tried with the 400 Mbits HVEC file (I am running an SSD as the boot and storage drive so no IO bottleneck). On Android the file plays very smoothly. However in CE, the hole UI starts to blink (lines, artefacts, etc, ). Is there any issue with the hardware decoder in CE ???

Hello everyone! Thanks for reading this!

First of all I’m noob and i want to thank everyone out there for contributing on this wonderfull endless open project.
:clap::clap::clap::clap: a big applause from me (and probably from many many others)
for helping people and make there life easier, hats of and salute all for the big efforts and many hours.

Here it comes…

it seems to me that multiple hardware and “main software” (like kodi,linux etc.) providers are in a transition phase to newer and better products, and noticing that you people are working very hard to keep up with all this on many fronts…

I started thinking about postponing my new hardware purchase untill the very first “officially” stable S905X2 version is released. (initially i was thinking about getting a [H96 MAX X2] one of these days) Should I get this hardware a.s.a.p.? or should i wait till the stable version is released? or should I skip on this hardware and wait for the S905X3?

Can someone make an educated guess about, how long it can take untill S905X2 (bugless) stable version is released?

With kind regards and respects,

thanks for replying in advance

I think it’s the USB device, not hub, because I get about the same speed when I connect it to the PC.
It’s probably a USB 3.0 device, but doesn’t have the right connections for USB3.0 to actually work.

Regarding the Jellyfish playback. We’ll need Kodi and dmesg logs. In Kodi enable video component debugging first.
Then reboot and run the video. After that collect and post the logs.

This was the surface Ethernet adapter I used https://www.aliexpress.com/item/32829528601.html
And this was the hub+adapter (I purchased using this link)

Edit: Link updated

I have this one https://www.ebay.com/itm/112541143662

These are the videos playback kernel logs

4K 250 Mbps h264

1403.050315@3] spdif_b keep clk continuous
[ 1403.050336@3] aml_spdif_close
[ 1403.050433@3] audio_ddr_mngr: frddrs[0] released by device ff642000.audiobus:spdif_b
[ 1404.065635@2] fatal error happend
[ 1404.124924@2] DI: di_receiver_event_fun: vf_notify_receiver ligth unreg
[ 1404.124939@2] DI: di_receiver_event_fun: VFRAME_EVENT_PROVIDER_RESET
[ 1404.124948@2] keep exit is skip current
[ 1404.124951@2] video_vf_light_unreg_provider: keep cur_disbuf failed
[ 1404.124960@2] H264 sysinfo: 3840x2160 duration=3203, pts_outside=1
[ 1404.124962@2] sync_outside=0, use_idr_framerate=0
[ 1404.124985@2] h264_reset_userdata_fifo: bInit: 1, ri: 0, wi: 0
[ 1404.124986@2] h264_reset_qos_mgr
[ 1404.124991@2] vh264dec: vf_ppmgr_reset
[ 1404.137037@2] Enter set parameter cmd1.
[ 1404.137116@2] vdec mux clock is 666666656 Hz
[ 1404.137120@2] vdec1 video changed to 3840 x 2160 60 fps clk->667MHZ
[ 1404.137128@2] actual_dpb_size 12 max_dpb_size 6 max_ref 4
[ 1404.164629@2] [DI] no muti instance.
[ 1404.164652@2] PPMGRVPP: warn: ppmgr rebuild from light-unregister

4K 400 Mbps HVEC 10 Bits

[ 1474.427134@1] asoc-aml-card auge_sound: S/PDIF Playback enable
[ 1474.503264@3] vfm_map_store:rm default
[ 1474.503301@3] vfm_map_store:add default decoder ppmgr deinterlace amlvideo amvideo
[ 1474.503426@3] the demux clock on, ref cnt: 1
[ 1474.503432@3] the parser_top clock on, ref cnt: 1
[ 1474.503436@3] the vdec clock on, ref cnt: 1
[ 1474.503455@3] the clk_hevc_mux clock on, ref cnt: 1
[ 1474.503458@3] the clk_hevcb_mux clock on, ref cnt: 1
[ 1474.503501@3] hevc mux clock is 499999992 Hz
[ 1474.503516@3] hevc back mux clock is 499999992 Hz
[ 1474.503586@3] vdec_create instance ffffff8014937000, total 1
[ 1474.503631@3] The fw has been loaded.
[ 1474.504488@3] HEVC stbuf alloced at 0000000060400000, secure = 0, size = 15728640
[ 1474.504521@3] vdec_init, dev_name:amvdec_h265, vdec_type=VDEC_TYPE_SINGLE
[ 1474.504523@3] vdec_init set vfm decoder ffffff8014937000
[ 1474.505235@3] decoder_bmmu_box_alloc_box, tvp_flags = 0
[ 1474.505767@3] [0]h265:pts_unstable=0
[ 1474.505778@3] [0]h265: ver (201602101,0) decinfo: 3840x2160 rate=3203
[ 1474.506230@3] [LOCAL], the fw (hevc_mmu) will be loaded.
[ 1474.506786@3] di_receiver_event_fun: vframe provider reg ppmgr
[ 1474.506899@3] set run_early_proc_fun_flag to 1
[ 1474.506902@3] DI: reg f
[ 1474.509653@0] hevc mux clock is 666666656 Hz
[ 1474.509681@0] hevc back mux clock is 666666656 Hz
[ 1474.509686@0] hevc video changed to 3840 x 2160 60 fps clk->667MHZ
[ 1474.509732@0] vdec_init, vf_provider_name =
[ 1474.510646@0] video first pts = 0
[ 1474.510659@0] vdec_request_irq ffffff800994b670, parser
[ 1474.512403@0] video first checkin pts = 0
[ 1474.512412@0] first check in vpts <0x55:0x0> ok!
[ 1474.515322@1] [0]Bit depth luma = 10
[ 1474.515330@1] [0]Bit depth chroma = 10
[ 1474.515337@1] [0]init_decode_head_hw: (0, 0) body_size 0x0 header_size 0x0
[ 1474.515355@1] [0]set pic_list_init_flag 1
[ 1474.518908@3] [0]init_decode_head_hw: (3840, 2160) body_size 0xff0000 header_size 0x7f80
[ 1474.518955@3] [0]init_buf_spec2 3840 2160
[ 1474.518958@3] [0]set pic_list_init_flag to 2
[ 1474.519005@1] [0]set pic_list_init_flag to 3
[ 1474.570332@1] [0]VH265: output first frame
[ 1474.570357@1] video first pts = 1
[ 1474.570506@1] DI bypass all 3840x2160-0x501000.
[ 1474.727373@1] asoc-aml-card auge_sound: S/PDIF Playback disable
[ 1474.727767@0] spdif_info: rate: 44100, channel status ch0_l:0x100, ch0_r:0x100, ch1_l:0x0, ch1_r:0x0
[ 1474.727821@0] aml_spdif_fifo_ctrl, bit depth:16, frddr type:1, toddr:type:1
[ 1477.107559@3] threadrw add more buffer from 32 → 64 for size 2097152
CoreELEC:~ #

One of the culprits could be the USB 3.0 port in your box. Try to validate its speed with another device.

The adapter is limited to USB 2.0 speed on my computer as well, so it’s not the box.
And a USB 3.0 SD card reader works fine and gets close to 80MB/s reads.

Then I suggest get another adapter (like the Hub one). It is really fast and gives you 3 additional USB 3.0 ports. My SSD is actuallu plugged into one of those ports and the box is able to use it as a boot device.

I updated the link for the second adapter I have.

Thanks. I’ll keep this in mind if I ever need one again.
Basically USB2.0 speeds are plenty for my needs, so it’s not really a problem.

Ok, any update regarding the HW decoder ???

To all users what where applying the bl301 bootloader blob injection:
Please make again with the last nightly (0814) again a injection by running the tool inject_bl301 to enable auto update of the bl301 blob.

More information:
https://discourse.coreelec.org/t/coreelec-bl301-wake-up-feature-inject-bl301

Hi,

Thanks for the hard work that is being done.
I don’t know if this is the right thread, if not I am sorry.
I now have a x96 max s905x2, but I can not get the right aspect ratio with 1080p hevc files that are 1920808 pixels. I tested the same file in x264 and then it displays the correct aspect ratio.
With 1080p hevc 1920
808 pixels 24hz display, when I choose original aspect ratio in video settings it is more like a square, if I choose normal it’s stretched to a 16:9 aspect ratio with no black bars. If I then apply a pixel ratio of 1.30 the aspect ratio is correct, but the right and left sides have something weird going on like a fish eye effect, and it is distracting while watching.
Can anybody confirm this problem? 1080p hevc 1920*1080 pixels watches fine in the correct aspect ratio

Thanks anyway

I would still like to add I now tried to play 1080p hevc 1920x816 pixels if i just boot up the x96 max s905x2 in android mode. In the VLC media player I also can’t get the correct aspect ratio. Best Fit is just stretched out 16:9. Original aspect ratio is a square. So in VLC it is even impossible to get the correct aspect ratio. It has the exact same problems as the coreelec system. So what does that say? is it a s905x2 problem. All I know is that the chromecast ultra displays the correct wide screen aspect ratio right away, and doesn’t give the fish eye effect on the left and right sides. Greetings