Posts by dtech
-
-
Hi! I also have a KII Pro mecool with Soc 905D and 3.14 kernel. What device tree have you used? and did you get tvheadend to work?
Try this one for S905D SoC-based KII Pro: gxl_p231_2g_dvb.dtb
Tvheadend needs to work because the KI Pro has the same tuner. I recommend the "dvb-latest" module package for the tuner.
-
I try this one "20210903"
Please also try 20210901. It contain datrh's original startup scripts and original platform_init script as well.Rebuild: Index of /snapshots/20210906/ -
I apologize. Please tell me, do you have any ideas for rtl8723?
Thank youUnfortunately, I have no idea at the moment.
Previously, there was a box with exactly same integrated SDIO wifi, but it was an S905 box and it eventually started with the external module.
-
Thank you so much for everything, but it no longer proves anything, that I don't have much time.
Thanks a lot for everything.
I'm sorry I couldn't really help you.
The truth is, I’m also trying to provide support for devices I’ve never had at all. And since I can't test these myself that way, and I can't debug any errors myself on them, so it's really just a remote series of experiments. And if something failed, it’s actually just a waste of time for me too. Unfortunately, I never know if actually I made a mistake or the tester messed up something. That’s when I usually come with this sentence: "Are you sure you did exactly that...?" Although I may have actually screwed up something.
Unfortunately, I start to get a little tired of these.
--
Edit:
Which snapsot image did you test? "20210901" or "20210903"? Unfortunately, this is by no means an insignificant parameter.
For snapshots, the main version number matters much less, the build date matters first.
-
-
Affected page: LibreELEC Amlogic - LibreELEC
Latest Stable Version (2020.05)
LibreELEC 9.0- Kodi 18.2
- Linux Kernel 4.19.x
Mistake #1:
Release date:
In fact, it should be 2019 instead of 2020, but May is true.
Mistake #2:
So, the Linux Kernel 4... WHAT?!
As far as I know, you only worked with 3.10 (Meson6, Meson8) and 3.14 (GXBB, GXL) on Amlogic devices, and never with 4.19.
-
i am using window 10 *.img unpack is for linex (i think)
This program is required for unpacking Amlogic firmware images: Amlogic_Flash_Tool_v6.0.0 .zip
-
There are new snapshot images for Minix-based devices: Index of /snapshots/20210906/
- Every time I try to stop, it freezes... doesnt matter what I command then, just a reboot to make it alive again;
Okay, I replaced the platform_init script with the one I modified for M8S+.
This was preceded by quite a long experimentation, but there it finally solved the freeze on the M8S+.
Although it didn’t work on n200 (MXIII-based) devices, that’s why I didn’t apply it to anything other than M8S+ because I can’t test.
I would ask you to test it please.
There´ s no sign if it is on or off - the led is dead;
Unfortunately, I cannot comment on this. I use the datrh solution. Did it work under his image?
As far as I´ ve seen, the player isn´ t as smooth as before - some image tearing during playback.
Let's see now if the new initramfs script solved this as well. If not, I would like clarification as to which videos are not playing properly.
-
And last build 9.2.8.2 (also bluetooth don't work)
I don't know why rtl8723bs doesn't work even though it's turned back on.
Neither the external nor the internal module works. I don't know why, but I'm going crazy about it!
...
Okay, maybe we have one more option, so please send the output from these commands under the old 9.2.8.1:
I need to know the vendor ID and the product ID of the integrated wireless/bluetooth SDIO module.
-
Here are some new test images: Index of /snapshots/20210901/
Momantai: LibreELEC-X8-X8H.arm-9.2.8.2.*
SerGioTenerife: LibreELEC-X8H-Plus.arm-9.2.8.2.*
blackride: LibreELEC-MXIII-Plus.arm-9.2.8.2.*
Please test them and describe your experiences. Thank you everyone.
-
-
Now the 8723bs module will have the problem.
I need some information about the integrated adapter from an older version that was still working.
lshw -C network
BTW I was using an custom image before (S802/S812-Libreelec images for 7/8/9).
Can you specify which image you are using? The topic link is a pretty broad concept.
-
-
-
-
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=0
These 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 8188eu
The 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,8188e
If 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.