It works.
Wow, that's good news, the driver seems to be working. Did you manage to connect to a Wi-Fi network?
I bought here: ...
I will try to get one and see what happens. Thanks. 
Posts by dtech
-
-
Well, it seems that the required module has not been loaded. Let's try to load it manually:
Codedmesg -c > /dev/null modprobe 8723as dmesg | pasteAnd thanks for the photo.
Btw, also doesn't work Power On from remote control. Can anything be done about it?
Unfortunately, it looks like I need to dig deeper into the code, and the HD18Q image probably wouldn't be fully compatible with this 2022 box release. I feel like we can't move forward until I get a piece of this myself.
But there is a new question: Does the box really turn off under Android when the power button is pressed on the remote, or does it just go to standby?
P.s.: We just need to find out who is selling exactly the same box. If anyone knows accurate information about this, please let me know. Thanks.
-
It seems that the SDIO bus is re-initialized, but the SDIO adapter does not appear afterwards.
Next step: I would need an lsmod output.
Unfortunately, I don't have an S805 device with SDIO wifi, so if I don't manage to get such a box, I can only rely on user tests.
-
I tried to take the log from alexelec and it looks like what you said. It doesn't fit, does it?
From a completely different operating system, I won't really get information about the status of the driver I modified, so it's unfortunately useless for me. However, I/O errors related to the SD card are also present here, only in a smaller volume.
It would be worth running this in overwrite mode, before you write an image to the SD card again.
-
Now some SD card related R/W error keeps repeating itself over and over again...
The log should start like this:
Code[ 0.000000@0] Booting Linux on physical CPU 0x200 [ 0.000000@0] Linux version 3.10.108 (dtech@LibreBuilder) (gcc version 8.3.0 (GCC) ) #1 SMP PREEMPT Sat May 27 21:18:35 CEST 2023 [ 0.000000@0] CPU: ARMv7 Processor [410fc051] revision 1 (ARMv7), cr=10c5387d [ 0.000000@0] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000@0] Machine: Amlogic Meson8B, model: AMLOGIC [ 0.000000@0] physical memory start address is 0x200000 ...Unfortunately, I can't help you until the essential part is invisible. I would recommend trying a different SD card first.
-
The above command should be run relatively quickly after Kodi startup, preferably without pressing any button on the remote control.
Unfortunately, the log buffer is limited, so what you sent is only filled by pressing buttons on the remote control.
-
Installed the new snapshot version and the wifi still doesn't work.
I would be happy to get a syslog from you:
dmesg | paste
In addition, it would be good to identify whether the same PCB is also in your box.
-
If anyone has a similar box, or knows where to get a 100% identical one, please let me know.
-
Broken something when reassembling heat-sink, board won't boot, have to check if fixable in the spare time.
Can't test the image right now.
Oops, that's not good news. I hope there was no short circuit or similar.
-
I think that's behind the marketing idea: bigger is better...
I think the manufacturer simply has a bunch of empty MXQ boxes that they haven't sold before. By the way, the "5G" label on the box is also strange because the RTL8723AS only works on 2.4GHz. So it's the usual Chinese industrial scam again. I haven't been surprised by this in a while...
Meanwhile, I found an obvious error in the driver that I hadn't noticed before. I fixed this, please try this new snapshot version:
Index of /snapshots/20230515_rtl8723as_67db88d/
You should probably boot successfully with this image, but even if the wifi is working or not, I would ask for a journalctl | paste output.
-
Well, the manufacturer saved a lot of space, the PCB is quite small compared to the size of the box.
How to access the uart? there are pins on the PCB?
The unsoldered 4-pin header behind one of the Jack connectors looks similar, but I'm not sure it really is.
-
I just enabled passthrough but nothing changed. The GUI volume has always been set at 100%
If passthrough is active and the correct output and currently used encoding are enabled, it doesn't matter what volume is set under Kodi, because then the incoming bitstream is passed directly to the output without processing.
Edit: Okay, wait a second...
^ You didn't set this to 100%, did you? Because this is only the volume of the system sounds, not the master volume.
You can adjust the master volume of Kodi using the +/- buttons on the number pad.
Of course, with passthrough, this will have no effect, unless you only send basic PCM audio.
-
Thanks, it is AS and not BS. I have misunderstood vid and pid, now I've checked the chip by removing the heat sink.
Could you send some photos of the PCB?
Testing the provided image I've found that Kodi starts in safe mode ...
That doesn't look promising, it usually happens after several unsuccessful boot process. It's a shame I would have asked for some kernel log, but that way you could only extract anything meaningful from the UART.
-
Please try this snapshot image:
Index of /snapshots/20230512_rtl8723as_9b693a0/
Bluetooth probably won't work, but wifi should hopefully start with this driver.
Changes:
-
Just found that wifi is not working, the wifi chip is an RTL-8723BS, (024c:8723), tried modprobe on r8723bs but getting
modprobe: FATAL: Module r8723bs not found in directory /lib/modules/3.10.108The RTL8723BS is supported (module name: 8723bs.ko, without the "r" at the beginning), but it seems to me that the wifi chip you indicated is an RTL8723AS, which unfortunately I don't know too much about, but I'll try to look it up. I would like to ask you for a little patience.
-
Good news for users stuck on Leia (Kodi 18) is that an external developer (JimmyS83) backported the changes to this version.
This is also currently in alpha7 stage, but since the developer didn't make a zip for testing, I made it instead:
-
yes i have
Okay, it's fine then.
There is no point sending more commands to you, just use installtointernal again. The essence would be the same anyway, and it will solve your problem.
However, it is a mystery to me what caused the corruption of the filesystems on the eMMC.
-
I did reboot whitout sd and get: error in mount_storage etc... could not mount /dev/data
It looks like your /dev/data partition is also corrupted.
That's not good news. Did you have a Kodi backup?
