I just did a clean install, and just saw that it says âdevice tree is out of dateâ.
I used this from May 28. CoreELEC-Amlogic-ng.arm-19.5-Matrix_nightly_20220528-Generic.img.gz
Used the device tree that Portisch posted today, June 2.
Where do you found DTB?
At device tree of generic img nightly 0528 & 0601 only found sc2_s905x4_ugoos_am7 and ugoos_x4
This?
@clarkss12 please try this dtb. I have no idea about the device LED. Maybe you ask the vendor about the android dtb? Did the LED work with ugoos_x4 dtb?
sc2_s905x4_1gbit.dtb (85.3 KB)
Place the file as dtb.img and also in the folder device-trees without rename the file. Then the text on the screen on boot should be gone.
Since I am beating this to death⌠I will try to make this my last post for awhileâŚ
I did a complete update using the newest device tree from Portisch but with the nightly from May 30.
The ârebootâ now works. The power LED is blue, and changes to red as
it boots, which is excellent.
The screenshot function using the control and S buttons on a keyboard captures the screen.
Play back info
I tested HD and UHD videos. All worked great EXCEPT those encoded with the VC-1 video codec ( I have a few of those from BlueRay rips).
Ethernet and WiFi work great.
Both USB ports works as expected, did NOT connect and external HDD to test the capabilities.
Still need to test live TV, since most of the streams are in 480i or 1080i.
All in all, working great so far, except the videos encoded with the VC-1 codec.
Attached are screenshots of various video codecs playing. It shows the video codec and CPU usage, bit rate, etc
âŚ
Yes, use that device tree as he posted⌠Works good and the power LED even works.
1 Like
I installed a USB hub and I get a working eth1 I can see eth0 with a ifconfig -a but there is no light on the switchâs port in CE mode.
I also get this is in journalctl.
Aug 06 14:43:10 CoreELEC kernel: meson6-dwmac fdc00000.ethernet: Failed to reset the dma
Full logs -- Journal begins at Fri 2021-08-06 14:43:07 UTC, ends at Thu 2022-06-02 22:21 - Pastebin.com
From sshâing into the box in Android it uses something else if that helps
[ 1.937556] 1.937556@2] load module: dwmac_meson8b
[ 1.938409] 1.938409@2] meson8b-dwmac fdc00000.ethernet: IRQ eth_wake_irq not found
[ 1.938575] 1.938575@2] meson8b-dwmac fdc00000.ethernet: IRQ eth_lpi not found
[ 1.939483] 1.939483@2] meson8b-dwmac fdc00000.ethernet: PTP uses main clock
[ 1.940196] 1.940196@2] meson8b-dwmac fdc00000.ethernet: no reset control found
[ 1.941864] 1.941864@2] meson8b-dwmac fdc00000.ethernet: User ID: 0x11, Synopsys ID: 0x37
[ 1.942096] 1.942096@2] meson8b-dwmac fdc00000.ethernet: DWMAC1000
[ 1.942776] 1.942776@2] meson8b-dwmac fdc00000.ethernet: DMA HW capability register supported
[ 1.943739] 1.943739@2] meson8b-dwmac fdc00000.ethernet: RX Checksum Offload Engine supported
[ 1.944722] 1.944722@2] meson8b-dwmac fdc00000.ethernet: COE Type 2
[ 1.945384] 1.945384@2] meson8b-dwmac fdc00000.ethernet: TX Checksum insertion supported
[ 1.945953] 1.945953@2] usb 1-2.1: Unsupported device
[ 1.946295] 1.946295@3] meson8b-dwmac fdc00000.ethernet: Wake-Up On Lan supported
[ 1.946971] 1.946971@2] usb 1-2.1: Unsupported device
[ 1.947688] 1.947688@3] meson8b-dwmac fdc00000.ethernet: Normal descriptors
[ 1.948960] 1.948960@2] meson8b-dwmac fdc00000.ethernet: Ring mode enabled
[ 1.949720] 1.949720@2] meson8b-dwmac fdc00000.ethernet: Enable RX Mitigation via HW Watchdog Timer
[ 1.950752] 1.950752@2] meson8b-dwmac fdc00000.ethernet: device MAC address 02:ad:32:01:46:3a
I tried:
0528 & 0601 nightly with sc2_s905x4_1gbit.dtb
Renamed as dtb.img placed at root and sc2_s905x4_1gbit.dtb on devicetrees
Burn with rufus and etcher
Evey time same result transpeed logo nothing of coreelec
Im using reset Button method.
Unplug power cable
Insert microsd
Push reset Button
Plug Power cable without leave reset button until appear coreelec logo
Never logo for međ
Method
Terminal emulator type su intro reboot update intro
Reboot logo transpeed followed for a black screen
That really has be puzzled⌠You did it correctly. Try it again with the ugoos_X4.dtb, but it should not matter. The terminal emulator method should have worked also. There must be something different with the device tree that is not working on your box. Our boxes will have different modifications, but the hardware should be the same. One of the people on Freaktab has the same box as I, so I will ask him to test it.
1 Like
Information about our boxes. I was never able to get past the Russian language to post anything. Maybe you can ask someone there to test it with your device.
https://4pda.to/forum/index.php?act=search&source=all&forums[]=640&query=HK1RBOX+X4&x=19&y=12&subforums=1
1 Like
One more thought, doubt if it matters, donât have time to test it right now. Our boxes comes with a root switch. Try different settings of the root switch (under Android) and see if that works. Also, when you first boot your box up with the toothpick depressing the reset switch, you should see the âAndroid bootloaderâ screen for a second when you apply power.
1 Like
Here is the text from Android /dev/dtb for my device /dts-v1/;/ { model = "Amlogic"; amlogic-dt-id = "sc2_s905x4_ah212"; co - Pastebin.com It doesnât work with CE since it is a different kernel but it might give clues my Ethernet is not working.
I have finally found a SD card that works with this device, it is more picky then other device I used. So the only issue I have is the Ethernet, not sure why @clarkss12 has working LAN.
Is your WiFi working?
Yes wifi is working and an Ethernet hub.
That is strange, usually it is the WiFi that doesnât work. I havenât had Ethernet issues in a very long time. Unless, going back years ago with the Pine64 :). As I recall, had to modify an Ethernet cable to get it to work.
I struggled with getting the stock remote control to work in CoreELEC, but thanks to Betatester for helping me, I finally got it to work.
Since I am old and forget everything, I made a YouTube video to help me in the future.
These boxes tend to have different hardware spec within, e.g. different brands of wifi/BT chips, different/no ethernet NIC chips (I think ânoâ means using the CPU built-in PHY/only 100M?), so this is to be expected.
Based on my Android dtb it uses something called rgmii which I speculate might not be available in this kernel. However I am more concerned that meson6 not meson8 is being called.
A person on freak tab, acknowledge that his gigabit Ethernet on his box was working also under CoreELEC.
Thatâs rather vague. Can we have a link to that post please.
Joined to report, otherwise Clark would tell my parents.
Installed CoreELEC on June 2nd using that same day nightly (I think later it was updated to June 3rd release), no issues but still didnât shutdown properly using the file at post #40, seconds later it restart just like on Android.The above happens whether HDMI-CEC is enabled or disabled. On that note, if thereâs a proper option on CoreELEC that disables HDMI-CEC, the tv turns off when I power off the box. LED and ethernet works properly. At 3840x2160 CoreELEC seems to run only @ 23.98, 24, 25, 29.97, and 30Hz, it doesnât work between the 50s-60Hz. Android runs fine by default at 3840x2160 60Hz. At 4096x2160, it will only work at 23.98 & 24Hz. Cannot comment on the remote, I use a keyboard, but Clark did mentioned that it worked.
Thanks you devs and contributors.
Could one of of you copy your Android /dev/dtb file so I can compare with my h/w? I feel it is a timing issue for rgmii since occassionally I do have the Ethernet lights stay on and the IP shows as 169. class.