hi there. I have a S905 box using the DTBs from http://kszaq.libreelec.tv/s905/8.2/device_trees/S905/ - specifically gxbb_p200_2G_1Gbit_OTG_Port.dtb . Can you please add support for loadable DTBs?
Posts by KyleS
-
-
Does anyone have the latest on h.265 support for this? CoreElec still cannot play simple 4k60hz video and has completely corrupt output (dusted off my "new" box from February and these basic same issues are present) so I'm totally looking to flip again.
I also had eMMC corruption the last time I tried the LE image (from Bables) - has this been resolved?
-
LKML: Maxime Jourdan: [PATCH 0/2] media: meson: vdec: Add compliant H264 support looks like HDR support has landed (?).
-
This forum is not a platform for spreading unsubstantiated misinformation on other operating systems.
I am privy to all CE matters being part of the team and say you are BOTH wrong in the quotes you have made.
Please edit to correct your errors.
Quote from 20 minutes agoYou have been suspended from the forum until 24 September 3019 07:00.
lol. Talk about retaliation...
The reason I made the thread was to bring awareness to the issue and to help resolve as I'm aware team members don't necessarily have 4K panels to truly test. The information being purposely hidden (see how adam unlisted the thread) is incredibly problematic and I know would have certainly stopped me and many others from buying a box.
LibreELEC (OSS Linux really) currently can't do 4K content as the decoder isn't upstream and/or written yet. This is why I made the thread here to ask if it's actually fundamentally a hardware problem - or if it's a simple amlogic SDK problem.
-
I'm incredibly unclear why CoreELEC is censoring this information... Any 4K content on the SoC is nearly completely corrupt when it's hardware accelerated. I suppose it's because they received sponsorship money and are peddling bad units now?
Will LibreELEC have this problem too with accelerated content?
https://discourse.coreelec.org/t/amlogic-ng-a…corruption/7039
-
Code
Display More# table x96max, type: NEC 0x142 KEY_ESC 0x14e KEY_1 0x10d KEY_2 0x10c KEY_3 0x14a KEY_4 0x109 KEY_5 0x108 KEY_6 0x146 KEY_7 0x105 KEY_8 0x104 KEY_9 0x101 KEY_0 0x113 KEY_ENTER 0x111 KEY_HOME 0x116 KEY_UP 0x151 KEY_LEFT 0x150 KEY_RIGHT 0x11a KEY_DOWN #0x0071 KEY_MUTE 0x110 KEY_VOLUMEDOWN 0x118 KEY_VOLUMEUP 0x140 KEY_POWER 0x14c KEY_MENU 0x119 KEY_BACK 0x158 KEY_NEXTSONG 0x159 KEY_PREVIOUSSONG 0x100 KEY_TEXT 0x147 KEY_CONTEXT_MENU
-
New look with KODI-19. Please note, this is the first trial version and many things may not work.
X96 MAX 64/4G eMMC and SD Card work.
Does anyone have usable wireless? The box seems to get very upset with very little traffic.
Code
Display More[ 6.762275] meson-ir ff808000.ir: receiver initialized [ 6.809969] brcmfmac: F1 signature read @0x18000000=0x17224356 [ 6.816006] ------------[ cut here ]------------ [ 6.816073] WARNING: CPU: 0 PID: 457 at brcmf_sdiod_sgtable_alloc+0xb0/0x148 [brcmfmac] [ 6.816075] Modules linked in: brcmfmac brcmutil hci_uart ir_nec_decoder btsdio btqca btbcm btintel bluetooth rc_x96max mali_kbase(O) meson_ir rc_core cfg80211 ao_cec_g12a ecdh_generic ecc meson_vdec(C) rfkill videobuf2_dma_contig v4l2_mem2mem [ 6.816106] CPU: 0 PID: 457 Comm: kworker/0:3 Tainted: G C O 5.3.0-rc8 #1 [ 6.816107] Hardware name: Shenzhen Amediatech Technology Co., Ltd X96 Max (DT) [ 6.816118] Workqueue: events brcmf_driver_register [brcmfmac] [ 6.816122] pstate: 40000005 (nZcv daif -PAN -UAO) [ 6.816131] pc : brcmf_sdiod_sgtable_alloc+0xb0/0x148 [brcmfmac] [ 6.816139] lr : brcmf_sdiod_sgtable_alloc+0xb0/0x148 [brcmfmac] [ 6.816140] sp : ffff0000103fba80 [ 6.816142] x29: ffff0000103fba80 x28: 0000000000000000 [ 6.816144] x27: ffff800086bbb000 x26: ffff800089dd9e00 [ 6.816147] x25: ffff000009b26bc8 x24: ffff80009a4fcc00 [ 6.816150] x23: ffff000012118548 x22: ffff800089e34400 [ 6.816152] x21: ffff800089e34400 x20: 0000000000000023 [ 6.816155] x19: ffff800089e34400 x18: 00000000fffffff0 [ 6.816157] x17: 0000000000000000 x16: 0000000000000000 [ 6.816160] x15: ffff000012130e90 x14: ffff0000121e700a [ 6.816162] x13: 0000000000000000 x12: ffff0000121e6000 [ 6.816165] x11: ffff000012130000 x10: ffff0000121e6650 [ 6.816168] x9 : 0000000000000000 x8 : 0000000000000001 [ 6.816170] x7 : 0000000000000127 x6 : 0000000000000001 [ 6.816172] x5 : 0000000000000000 x4 : 0000000000000000 [ 6.816175] x3 : 0000000000000000 x2 : b937bdd8fab0ab00 [ 6.816177] x1 : 0000000000000000 x0 : 0000000000000024 [ 6.816180] Call trace: [ 6.816190] brcmf_sdiod_sgtable_alloc+0xb0/0x148 [brcmfmac] [ 6.816197] brcmf_sdio_probe+0x28c/0x890 [brcmfmac] [ 6.816205] brcmf_ops_sdio_probe+0x1f0/0x350 [brcmfmac] [ 6.816213] sdio_bus_probe+0xa0/0x170 [ 6.816218] really_probe+0xec/0x3d0 [ 6.816221] driver_probe_device+0xdc/0x130 [ 6.816224] device_driver_attach+0x6c/0x78 [ 6.816226] __driver_attach+0x9c/0x168 [ 6.816230] bus_for_each_dev+0x70/0xc0 [ 6.816232] driver_attach+0x20/0x28 [ 6.816236] bus_add_driver+0x190/0x220 [ 6.816238] driver_register+0x60/0x110 [ 6.816241] sdio_register_driver+0x24/0x30 [ 6.816250] brcmf_sdio_register+0x14/0x48 [brcmfmac] [ 6.816258] brcmf_driver_register+0xc/0x18 [brcmfmac] [ 6.816263] process_one_work+0x1fc/0x388 [ 6.816266] worker_thread+0x4c/0x4f8 [ 6.816269] kthread+0x120/0x128 [ 6.816274] ret_from_fork+0x10/0x1c [ 6.816275] ---[ end trace ee34d4fdfe242e45 ]--- [ 6.829866] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4356-sdio for chip BCM4356/2 [ 6.834714] usbcore: registered new interface driver brcmfmac [ 6.943633] input: eventlircd as /devices/virtual/input/input1 [ 6.974855] meson8b-dwmac ff3f0000.ethernet eth0: PHY [0.0:00] driver [RTL8211F Gigabit Ethernet] [ 6.974877] meson8b-dwmac ff3f0000.ethernet eth0: phy: setting supported 00,00000000,000062ff advertising 00,00000000,000062ff [ 6.978410] meson8b-dwmac ff3f0000.ethernet eth0: No Safety Features support found [ 6.978424] meson8b-dwmac ff3f0000.ethernet eth0: PTP not supported by HW [ 6.978432] meson8b-dwmac ff3f0000.ethernet eth0: configuring for phy/rgmii link mode [ 6.978440] meson8b-dwmac ff3f0000.ethernet eth0: phylink_mac_config: mode=phy/rgmii/Unknown/Unknown adv=00,00000000,000062ff pause=10 link=0 an=1 [ 6.980798] meson8b-dwmac ff3f0000.ethernet eth0: phy link down rgmii/Unknown/Unknown [ 6.988069] Bluetooth: hci0: BCM: chip id 101 [ 6.988318] Bluetooth: hci0: BCM: features 0x2f [ 6.989808] Bluetooth: hci0: BCM4354A2 [ 6.989824] Bluetooth: hci0: BCM4356A2 (001.003.015) build 0000 [ 7.077756] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4356-sdio for chip BCM4356/2 [ 7.077855] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available [ 7.081474] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4356/2 wl0: Jun 16 2015 14:25:06 version 7.35.184.r1 (TOB) (r559293) FWID 01-b22ae69c [ 7.904678] Bluetooth: hci0: BCM4356A2 (001.003.015) build 0266 [ 10.751260] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 10.807801] brcmfmac: mmc_submit_one: CMD53 sg block write failed -22 [ 10.807810] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame [ 20.443272] brcmfmac: mmc_submit_one: CMD53 sg block write failed -22 [ 20.443281] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame [ 20.862176] fuse: init (API version 7.31) [ 20.987292] brcmfmac: mmc_submit_one: CMD53 sg block write failed -22 [ 20.987300] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame [ 29.133398] brcmfmac: mmc_submit_one: CMD53 sg block write failed -22 [ 29.133410] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame [ 30.136995] brcmfmac: mmc_submit_one: CMD53 sg block write failed -22 [ 30.137022] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame [ 55.111497] brcmfmac: mmc_submit_one: CMD53 sg block write failed -22 [ 55.111512] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame [ 69.905043] brcmfmac: mmc_submit_one: CMD53 sg block write failed -22 [ 69.905049] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame [ 70.911698] brcmfmac: mmc_submit_one: CMD53 sg block write failed -22 [ 70.911706] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame [ 74.201920] brcmfmac: mmc_submit_one: CMD53 sg block read failed -22 [ 74.201936] brcmfmac: brcmf_sdio_rxglom: glom read of 512 bytes failed: -5 [ 74.201944] brcmfmac: brcmf_sdio_rxfail: abort command, terminate frame [ 74.202112] brcmfmac: brcmf_sdio_readframes: brcmf_sdio_readframes: glom superframe w/o descriptor! [ 74.202119] brcmfmac: brcmf_sdio_rxfail: terminate frame [ 74.202298] brcmfmac: mmc_submit_one: CMD53 sg block read failed -22 [ 74.202306] brcmfmac: brcmf_sdio_rxglom: glom read of 512 bytes failed: -5 [ 74.202312] brcmfmac: brcmf_sdio_rxfail: abort command, terminate frame [ 74.202512] brcmfmac: brcmf_sdio_readframes: brcmf_sdio_readframes: glom superframe w/o descriptor! [ 74.202518] brcmfmac: brcmf_sdio_rxfail: terminate frame [ 74.203087] brcmfmac: mmc_submit_one: CMD53 sg block read failed -22 [ 74.203096] brcmfmac: brcmf_sdio_rxglom: glom read of 512 bytes failed: -5 [ 74.203102] brcmfmac: brcmf_sdio_rxfail: abort command, terminate frame [ 74.205078] brcmfmac: brcmf_sdio_readframes: brcmf_sdio_readframes: glom superframe w/o descriptor! [ 74.205126] brcmfmac: brcmf_sdio_rxfail: terminate frame [ 74.205356] brcmfmac: mmc_submit_one: CMD53 sg block write failed -22 [ 74.205359] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame [ 75.205701] brcmfmac: mmc_submit_one: CMD53 sg block write failed -22 [ 75.205708] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame [ 77.798496] brcmfmac: mmc_submit_one: CMD53 sg block write failed -22 [ 77.798552] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame [ 116.665715] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame [ 116.665846] mmc0: tuning execution failed: -5 [ 117.694663] brcmfmac: mmc_submit_one: CMD53 sg block read failed -22 [ 117.694677] brcmfmac: brcmf_sdio_rxglom: glom read of 512 bytes failed: -5 [ 117.694684] brcmfmac: brcmf_sdio_rxfail: abort command, terminate frame [ 117.694821] brcmfmac: brcmf_sdio_readframes: brcmf_sdio_readframes: glom superframe w/o descriptor! [ 117.694827] brcmfmac: brcmf_sdio_rxfail: terminate frame [ 117.695296] brcmfmac: mmc_submit_one: CMD53 sg block read failed -22 [ 117.695305] brcmfmac: brcmf_sdio_rxglom: glom read of 512 bytes failed: -5 [ 117.695310] brcmfmac: brcmf_sdio_rxfail: abort command, terminate frame [ 117.695463] brcmfmac: brcmf_sdio_readframes: brcmf_sdio_readframes: glom superframe w/o descriptor! [ 117.695468] brcmfmac: brcmf_sdio_rxfail: terminate frame [ 117.696273] brcmfmac: mmc_submit_one: CMD53 sg block write failed -22 [ 117.696280] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
-
Regarding audio, right now there is unfortunately only 2.0 PCM audio support for Amlogic in mainline kernel.
Developers will certainly let you know when this is improved.
afl1 Very big thank you for bringing the DVB support!
Where is everyone hacking on the kernel?
-
You came to the resource to the developers, agitate for competitors. Are you a provocateur or want to look like the smartest?
CE has linux 4.9, here going development of 5.0. What are you want to say?...
CoreELEC is moderating any threads not related to the Odroid-N2 or legacy boxes, there's no free speech over there... LibreELEC is at least trying to keep universal support mainline for the SoCs themselves, CoreELEC is focusing their efforts on the old SDK instead...
That's the difference.
-
KyleS at this point there is no technical solution for S905X2 wifi on the mainline kernel. If that changes, then we can negotiate the project decision on how ugly the patch is and what to support.
Anything I can influence? Which subsystem isn't playing ball?
-
Some comments:
WiFi on S905X2: may not be supported for a while yet, or at all. S905X2 has a design flaw in how the SDIO module is internally connected and while an egregious hack/workaround exists in Amlogic's 4.9 kernel it's looking unlikely that a cleaner solution acceptable to upstream kernel maintainers can be found. We might attempt a mainline kernel version of the egregious hack through a local patch, or since the majority of users stream media over Ethernet anyway, we might just leave it unsupported and avoid the support/maintenance work. The issue is allegedly resolved with the S905X3 chip which is already being sampled to manufacturers.
Device trees: The mainline kernel avoids the silliness of 1G/2G/3G variants needed on the legacy kernel which makes life easier, but we will still need to figure out (and then upstream) the device trees for popular devices. I'm keen that device trees are sent upstream so that devices can be uniquely identified by "compatible" strings in the device-tree, as this allows simple things like the remote control keymap (also sent upstream) to be described in the device-tree for a better out of box user experience. Submitting changes to the kernel is not the most straightforward process but if non-coding folk like myself can figure it out (my personal collection of one-line kernel changes is slowly increasing) the bar is not set impossibly high.
arm vs. aarch64: performance is marginally higher on aarch64 but arm allows us to support widevine drm (which is not available in 64-bit format) so arm is our preferred option and official nightlies and the Kodi binary add-ons to match them, once they start, will be arm only. Maintaining a single image for all Amlogic hardware (two images until panfrost evolves bifrost support) is a bigger win than the minor performance gain. On G12 hardware the future gain from running the CPUs at full speed (at the moment they are under-clocked) will dwarf the architecture difference.
Please re-consider the WiFi stance. I'm in a condo and use WiFi exclusively from my current s905 Kodi box. I've had a x96 Max (4GB) for a while and I'm excited to see LibreELEC leading the charge once again for these boxes. I can't wait to watch 4k HDR over my point to point wireless :-).
-
-
Manual and auto updating aren't working for me either. I get notification that an update is available but no files are in the .update directory. When I check "available versions" in Kodi there is nothing there.
Reboot.
-
LibreELEC:/sys/devices/virtual/amhdmitx/amhdmitx0 # chmod 666 output_rgb
LibreELEC:/sys/devices/virtual/amhdmitx/amhdmitx0 # cat output_rgb
cat: read error: Input/output error
LibreELEC:/sys/devices/virtual/amhdmitx/amhdmitx0
-
kszaq you know about this right? Running Android on a mainline graphics stack [LWN.net] | GitHub - robherring/gbm_gralloc: Android gralloc module using libgbm API from Mesa . Kodi Leia has gbm support, which may get around the issues you've described?
-
Which 'community' release are you running? .. we can bug the creator to add the patch we need testing and spin you a build.
kszaq currently.
-
amlogic s905 clone box, using Wireless. I've set the network to block on boot so it's not a race in that regard.
-
I've seen this issue on and off since starting to use Libreelec. I thought it was a couple bad servers in the pool, and just bad luck... However, even tonight I added 1.ca.pool.ntp.org and 2.ca.pool.ntp.org, rebooted... still no clock set.
Obviously adding `ntpd -p 0.ca.pool.ntp.org 1.ca.pool.ntp.org 2.ca.pool.ntp.org` to my autostart.sh resolves the issue instantly, but this is crap for less knowledgeable people. Please consider using ntpd or similar instead of the current mechanism.