Posts by dtech
-
-
-
-
In the previous log, you almost misled me because the adapter connected for the second time was the V4:
Code: dmesg (9.2.8.1)
Display More[ 51.875978@2] usb 1-1.3: new high-speed USB device number 4 using dwc_otg [ 51.977350@2] usb 1-1.3: New USB device found, idVendor=0bda, idProduct=8178 [ 51.977363@2] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 51.977370@2] usb 1-1.3: Product: USB WLAN [ 51.977375@2] usb 1-1.3: Manufacturer: 802.11n [ 51.977381@2] usb 1-1.3: SerialNumber: 00e04c000001 [ 52.015734@2] [DVFS]aml_dvfs_do_voltage_change, no dvfs driver [ 52.018566@3] RTL871X: module init start [ 52.018577@3] RTL871X: rtl8192cu v4.0.5_11249.20140422 [ 52.018582@3] RTL871X: build time: Aug 15 2021 17:12:24 [ 52.115740@1] [DVFS]aml_dvfs_do_voltage_change, no dvfs driver [ 52.156781@2] RTL871X: rtw_ndev_init(wlan1) [ 52.158665@2] RTL871X: rtw_ndev_init(wlan2) [ 52.167744@0] usbcore: registered new interface driver rtl8192cu [ 52.167759@0] RTL871X: module init ret=0These require completely different kernel modules:
V4 -> 0bda:8178 (rtl8192cu)
V5 -> 2357:0107 (rtl8192eu)
I will try to find out why it does not load the module for the V5 (rtl8192eu).
In your CE log the trace looks very ugly after connecting the USB wifi device:
https://paste.kodi.tv/idowabezoh
That looks pretty sick.

i update LE with version 9.8.2.1 on 9.2.8.2 via tar archive.
The numbers were mixed up again: 9.2.8.1 -> 9.8.2.1 (Translator malfunction?)
However, if you could check the current image with V4, that would be good, because it also got a new driver.
If it doesn't work, I will go back to the old one.
-
I update 9.8.2.1 via *.tar* and no changes.
The version number (9.2.8.2) has changed a bit, but it's okay.

The Amlogic project branch of CE 9.2.7 "non-ng" build contains exactly the same driver, so it's a little weird.
I need more information, so you should follow exactly the following steps:
- Start the box without connecting the USB stick.
- dmesg -c
This prints the dmesg and also deletes it. From now on, only recent changes are relevant. - cat /etc/os-release | grep PRETTY_NAME
- lsmod | grep cfg80211
- Now connect the USB wifi adapter.
- dmesg -c
- lsmod | grep cfg80211
I connected the TL-WN722N v1 to my M8Q as an example, but I would expect something similar:
CodeM8Q:~ # dmesg -c ... M8Q:~ # cat /etc/os-release | grep PRETTY_NAME PRETTY_NAME="LibreELEC (dtech): 9.2.8.2" M8Q:~ # lsmod | grep cfg80211 cfg80211 206547 1 8188euThe USB device is now connected...
Code
Display MoreM8Q:~ # dmesg -c [ 886.150548@3] usb 1-1.2: new high-speed USB device number 4 using dwc_otg [ 886.273154@3] usb 1-1.2: New USB device found, idVendor=0cf3, idProduct=9271 [ 886.273247@3] usb 1-1.2: New USB device strings: Mfr=16, Product=32, SerialNumber=48 [ 886.273295@3] usb 1-1.2: Product: USB2.0 WLAN [ 886.273362@3] usb 1-1.2: Manufacturer: ATHEROS [ 886.273406@3] usb 1-1.2: SerialNumber: 12345 [ 886.391053@1] usb 1-1.2: ath9k_htc: Firmware htc_9271.fw requested [ 886.393564@1] usbcore: registered new interface driver ath9k_htc [ 886.704285@1] usb 1-1.2: ath9k_htc: Transferred FW: htc_9271.fw, size: 50980 [ 886.942404@1] ath9k_htc 1-1.2:1.0: ath9k_htc: HTC initialized with 33 credits [ 887.184809@1] ath9k_htc 1-1.2:1.0: ath9k_htc: FW Version: 1.3 [ 887.184822@1] ath: EEPROM regdomain: 0x0 [ 887.184828@1] ath: EEPROM indicates default country code should be used [ 887.184832@1] ath: doing EEPROM country->regdmn map search [ 887.184839@1] ath: country maps to regdmn code: 0x3a [ 887.184845@1] ath: Country alpha2 being used: US [ 887.184850@1] ath: Regpair used: 0x3a [ 887.189399@1] ieee80211 phy1: Atheros AR9271 Rev:1 [ 887.189473@1] cfg80211: Calling CRDA for country: US [ 887.189850@1] cfg80211: Regulatory domain changed to country: US [ 887.189864@1] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 887.189872@1] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (3000 mBi, 0 mBm) [ 887.189878@1] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (2300 mBi, 0 mBm) [ 887.189885@1] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz), (2300 mBi, 0 mBm) [ 887.189892@1] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (2300 mBi, 0 mBm) [ 887.189898@1] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (3000 mBi, 0 mBm) [ 887.189905@1] cfg80211: (57240000 KHz - 71000000 KHz @ 2160000 KHz), (4000 mBi, 0 mBm) [ 887.312071@3] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready M8Q:~ # lsmod | grep cfg80211 cfg80211 206547 4 ath,mac80211,ath9k_htc,8188eIf this is possible, you should do this under my image on your MXIII-clone as well as from the other box under CE with same USB wifi stick.
By the way, I also ordered a WN821N today, the version will unfortunately only be revealed if it is in my hands.
-
-
Are you can add driver for rtl8192eu in your builds?
My builds are already contain this driver in this package "RTL8192EU-aml".
Code: projects/MXIII-S8X2/options... # e.g. ADDITIONAL_DRIVERS="DRIVER1 DRIVER2" ADDITIONAL_DRIVERS="gpu-aml RTL8192CU-aml RTL8192DU RTL8192EU-aml RTL8812AU RTL8188EU-aml mt7601u-aml" ...Could you send a dmesg and an lsusb output from your MXIII-clone when the WN821N is connected during the whole boot process?
-
There are KI Plus boards with an S905 processor. A photo of someone else's board does not explain the difference between the two different boot ROM logs.
S905??? No!!!
It is definitely GXL, not GXBB. So the SoC is S905D (or X/W/L).
See the first post in this topic (same message was at the first time):
GXL:BL1:9ac50e:a1974b;FEAT:ADFC318C;POC:3;RCY:0;EMMC:0;READ:0;CHK:AA;SD:0;READ:0;CHK:AA;USB:8;
Second time... Your bootloader also contains this string:
Check the screenshot from PuTTY:
Quote from PuTTY windowGXL:fixed PLL lock failed
BL1:9ac50e:bb16dc;FEAT:ADFC318C:0;POC:0;RCY:0;USB:0;SPI:0;CHK:A7;
So, what is the next question?
-
Hi,
I've recently installed the version for wetek core. It seems stable. Bluetooth works fine.I've also checked netflix and amazon vod addons and they run smooth. The same for PVR.
All testing were done using a wired connection.
I'll report any issue that I'll found.Thanks for the feedback.
I also made the 4K-bugfix release (v9.2.8.1) for the WeTek Core.

-
Please remove the heat sink and attach CPU photo
But, only remove it if you can glue it back with something!
Otherwise, based on this photo, it looks the same as the box of creited:
-
I just tested the image and it doesn't work either, after the Minix logo the black screen appears and that's it. Thank you anyway.

First time you tried v9.2.8.1?
I only ask because it is based entirely on datrh's kernel, his kernel configuration and the same dtb.
I just don’t understand why it doesn’t boot on your device... (But I'm trying to solve the puzzle.)
-
Hola, dtech. Thanks for your work with the devices.
I have installed the image rom sd for my Minix x8h plus (s812)but he has not taken the pot from me. So it doesn't start.
I don't know why, I also tried the images para Amlogic universal n200 (S812, 2GB RAM, 10/100 Mbps LAN, AP6330 WiFi) But the wifi does not work in any way.
I also tried the img for OTT M8S+ with Amlogic S812 SoC (2G/8G):but the wifi doesn't work either. The same happened to me with the MXlll img.
What a shame, I was looking to update Kodi 18.6, in this I can only see h264 BRrips and I wanted to try another more current firmware.
You should first try image v9.2.8 instead of v9.2.8.1 because it was made with another kernel (kszaq-based instead of datrh-based).
Index of /3rdParty/S8X2/X8-H_Plus-S812_2G-AP6335e/ARCHIVE/
If I understand correctly, the 9.0.2 image made by datrh with Kodi v18.6 works on your box. Is this correct?
-
LE 9.2.8 image for WP1:
Amlogic Meson6 (AML8726-MX) SoC on Linux kernel v3.10.108 (LTS):
- WeTek Play (1G/4G) a.k.a. WP1:
The device image is based on the officially supported version 9.0.2.
WP1 image: Index of /WeTek_Play/
- WeTek Play (1G/4G) a.k.a. WP1:
-
As for the bridging with another router in order to provide wired connection to it.
Does this mean connecting them via ethernet? I know how it is done.
What I suggested is an AP-bridge solution, not a client bridge, so the routers need to be connected to each other via Ethernet, not the box.
The point is that the box is connected to a separate wireless network, not to the main router's wlan.
You only need max. 1 meter of cable between the routers, so I think it will fit.
People do not want wires running around their homes.
It's easier to have the cables in the wall in advance, where you need it. But for that, I had to be put some PVC-pipes into the wall, even before painting.

-
Imagine 3 excited kids (plus their friends) running around a room and something protuding out of the tvbox. I give it 1 month before they break the adapter and the usb that is plugged in

Rather, I would be more afraid the TV will be damaged, because that is a little more expensive than a TV box or wifi adapter.
It seems a bit of an excuse...

I have a suggestion to reverse the situation: put in an older router (e.g. 802.11g) in bridge mode that communicates well with the box.
Forget the WAN side, connect the network cable to one of the ports on the LAN. Turn off the DHCP server and set up the wlan interface.
Finally, connect the box to this router via WiFi. At the moment, I can't suggest a better and simpler than this solution.
I'm sure if you have a lot of USB wifi adapters, you also have a couple of old routers.

-
Hi jim_p !
chewitt is right, the wired connection is always better.
For live streams (e.g. IPTV), even a well-functioning wireless connection can sometimes cause random delays because multiple devices are connected to it at the same time, and this sometimes puts jitter into the signal. This will make the broadcast completely unenjoyable.
(For this, it is enough to have a smartphone connected to the same wireless network at the same time as the box. Not recommended.)
What Da Flex suggested is actually a client bridge, which is an adapter between the WiFi and the wired connection.
(This can still cause jitter problems with live streams because it's really just a media converter, from wireless 802.11* to wired 802.3*.)
But for offline media (e.g. play a movie from NAS) a wireless connection may be sufficient because that can be pre-buffered.
However, the integrated Realtek wireless driver are a really old piece (just like the kernel), and I don’t have a good experience with it either.
But, if you have an USB WiFi adapter, try it with your box first. Like this...
For me, this Atheros-based adapter (TP-Link WN722N) works better than the integrated Realtek.
It’s not a piece of today either, but at least it’s stable.
Regardless, I prefer a wired connection much more than any wireless solution.
-
LibreELEC v9.2.8.1 (4K-bugfix) has been released for S8X2 devices only.
Changes:- 4k-bugfix: fix 2160p resolutions support in amlogic-3.10 kernel,
- 3rdParty images: separate Minix (datrh-based) and MXIII (Demetris-based) S8X2 builds,
- 3rdParty images: fix X8-H Plus wifi issues and add support for X8 / X8-H devices.
Thanks to oceanzhang for his help in debugging and testing.
Affected devices: OTT M8S+, X8-H Plus, MXIII, MXIII-Plus/-G, Universal n200 devices and WeTek Core.
For more information and for download links, please check the first post in this topic: #1
Important notice for WeTek Core users:If anyone has tested the image for the WeTek Core, please comment because I have not received any feedback on it so far.If I do not receive any feedback, I will discontinue the support due to lack of interest. -