[Strong SRT2400] AP6212 WiFi Issue

Lirk · November 24, 2024 at 1:04 PM

1. Doesn't work WIFI module, as in previous LE versions (16.x to 17.x). According to MAC Address range: 44:2C:05:00:00:00 - 44:2C:05:FF:FF:FF, vendor is "AMPAK". I tried to run LE with different device trees, working without WIFI support was: gxbb_p200_1G_100M.dtb, gxbb_p200_1G_100M_RealtekWiFi.dtb, gxbb_p200_1G_wetek_hub.dtb, gxbb_p200_k1_plus.dtb. But WIFI work on LE13 with "meson-gxbb-nexbox-a95x.dtb" device tree.

2. Properly working software deinterlace on SD resolutions was from 16.x to 17.x versions, but from 18.x version it work with frame dropping.

3. From 18.x version doesn't work OK button, but it fixed with this solution manually: RE: Ok button doesn't work on H1 remote

**dtech** · November 24, 2024 at 2:08 PM

Quote from Lirk

1. Doesn't work WIFI module, as in previous LE versions (16.x to 17.x). According to MAC Address range: 44:2C:05:00:00:00 - 44:2C:05:FF:FF:FF, vendor is "AMPAK". I tried to run LE with different device trees, working without WIFI support was: gxbb_p200_1G_100M.dtb, gxbb_p200_1G_100M_RealtekWiFi.dtb, gxbb_p200_1G_wetek_hub.dtb, gxbb_p200_k1_plus.dtb. But WIFI work on LE13 with "meson-gxbb-nexbox-a95x.dtb" device tree.
2. Properly working software deinterlace on SD resolutions was from 16.x to 17.x versions, but from 18.x version it work with frame dropping.
3. From 18.x version doesn't work OK button, but it fixed with this solution manually: RE: Ok button doesn't work on H1 remote

You have written a lot of things, but there is not much meaningful information in it.

What box do you have? And specifically, what kind of WiFi chip is in your box?

If you could send me a log, both from the previous working and the currently non-working versions, I might be able to help.

Lirk · November 24, 2024 at 3:49 PM

Quote from dtech

What box do you have?

Strong SRT2400.

Quote from dtech

And specifically, what kind of WiFi chip is in your box?

I don't know, but vendor determined by MAC is "AMPAK". Is there way to determine WIFI chip without disassembling the box? So, this is working version of device tree: https://github.com/torvalds/linux…nexbox-a95x.dts from the newest version, is there the same device tree for this version?

**chewitt** · November 24, 2024 at 5:00 PM

The Nexbox A95 device-tree file in the upstream kernel defines no SDIO WiFi module, which normally means the module will not be probed and detected. It's possible the module is connected via USB instead; it's nnot unheard of but unusual in Amlogic boxes of that era. Ampak modules are normally using Broadcom chipsets, but which one? Logs from the Android/vendor kernel are needed else there are more questions than answers.

**dtech** · November 24, 2024 at 5:12 PM

Quote from Lirk

I don't know, but vendor determined by MAC is "AMPAK".

That's why it would be good to have the relevant part of a kernel log from a previous working system.

For example: dmesg | grep dhd

(If it's really Ampak, which is actually an SDIO wifi+bt combo adapter based on Broadcom chips.)

Lirk · November 25, 2024 at 3:15 PM

Quote from dtech

That's why it would be good to have the relevant part of a kernel log from a previous working system.
For example: dmesg | grep dhd
(If it's really Ampak, which is actually an SDIO wifi+bt combo adapter based on Broadcom chips.)

Log from this 9.2 build, without working WIFI. Can it help? I have no way to run working LE 13 build now.

dmesg | grep dhd

[ 11.049187@2] dhd_module_init: in
[ 11.049222@2] dhd_wifi_platform_load: Enter
[ 11.792953@2] dhdsdio_probe : no mutex held. set lock
[ 11.878301@2] dhd_conf_set_chiprev: chip=0xa9a6, chiprev=0
[ 11.878336@2] dhd_conf_set_conf_path_by_nv_path: config_path=/usr/lib/firmware/brcm/config.txt
[ 11.878513@2] dhd_os_open_image: /usr/lib/firmware/brcm/config.txt (399 bytes) open success
[ 11.909689@2] dhd_conf_read_nv_by_chip: nv_by_chip_count=12
[ 11.909702@2] dhd_conf_read_nv_by_chip: chip=0xa962, chiprev=0, name=nvram_ap6181.txt
[ 11.909706@2] dhd_conf_read_nv_by_chip: chip=0xa962, chiprev=1, name=nvram_ap6210.txt
[ 11.909710@2] dhd_conf_read_nv_by_chip: chip=0xa9a6, chiprev=0, name=nvram_ap6212.txt
[ 11.909714@2] dhd_conf_read_nv_by_chip: chip=0xa9a6, chiprev=1, name=nvram_ap6212a.txt
[ 11.909718@2] dhd_conf_read_nv_by_chip: chip=0x4345, chiprev=6, name=nvram_ap6255.txt
[ 11.909722@2] dhd_conf_read_nv_by_chip: chip=0x4330, chiprev=4, name=nvram_ap6330.txt
[ 11.909726@2] dhd_conf_read_nv_by_chip: chip=0x4339, chiprev=1, name=nvram_ap6335.txt
[ 11.909730@2] dhd_conf_read_nv_by_chip: chip=0x4354, chiprev=2, name=nvram_ap6356.txt
[ 11.909740@2] dhd_conf_read_nv_by_chip: chip=0x4335, chiprev=1, name=nvram_bcm4335.txt
[ 11.909753@2] dhd_conf_read_nv_by_chip: chip=0xa94c, chiprev=2, name=nvram_ap6234.txt
[ 11.909758@2] dhd_conf_read_nv_by_chip: chip=0x4359, chiprev=9, name=nvram_ap6359sa.txt
[ 11.909762@2] dhd_conf_read_nv_by_chip: chip=0x4334, chiprev=3, name=nvram_bcm4334.txt
[ 11.909821@2] dhd_conf_read_config: mimo_bw_cap = 1
[ 11.910138@2] dhd_conf_read_config: bcn_timeout = 20
[ 11.910258@2] dhd_conf_read_config: kso_enable = 0
[ 11.910576@2] dhd_conf_read_config: PM = 0
[ 11.911775@3] dhd_attach(): thread:dhd_watchdog_thread:af0 started
[ 11.911802@3] dhd_attach(): thread:dhd_dpc:af1 started
[ 11.911830@3] dhd_attach(): thread:dhd_rxf:af2 started
[ 11.911839@3] dhd_deferred_work_init: work queue initialized
[ 12.209740@2] dhd_open: WLAN driver is not initialized
[ 12.209857@2] dhd_wl_ioctl: returning as busstate=0
[ 12.210445@2] dhd_txglom_enable: enable 0
[ 12.210449@2] dhd_conf_set_txglom_params: swtxglom=0, txglom_ext=0
[ 12.210452@2] dhd_conf_set_txglom_params: txglom_bucket_size=0
[ 12.210456@2] dhd_conf_set_txglom_params: txglomsize=0, deferred_tx_len=0, bus_txglom=-1
[ 12.210460@2] dhd_conf_set_txglom_params: tx_in_rx=1, tx_max_offset=0
[ 12.210469@2] dhd_bus_devreset: WLAN OFF DONE
[ 12.211549@2] dhdsdio_probe : the lock is released.
[ 12.211738@2] dhd_module_init: Exit err=0
[ 13.216570@2] dhd_open: Enter ffffffc0238e9000
[ 16.077307@2] dhd_open : wl_android_wifi_on failed (-110)
[ 16.077359@2] dhd_stop: Enter ffffffc0238e9000
[ 16.077583@2] dhd_wl_ioctl: returning as busstate=0
[ 16.077660@2] dhd_net_bus_devreset: dhd_bus_devreset: -35
[ 16.277041@2] dhd_stop: Exit
[ 16.277333@2] dhd_open: Exit ret=-1

chip:0xa9a6. It looks like AP6236?

**dtech** · November 25, 2024 at 3:58 PM

Quote from Lirk

chip:0xa9a6. It looks like AP6236?

Nope, it is just an AP6212.

If you definitely want to send a log under my version, please send a link generated by the pastekodi command instead.

Lirk · November 25, 2024 at 4:09 PM

Quote from dtech

Nope, it is just an AP6212.
If you definitely want to send a log under my version, please send a link generated by the pastekodi command instead.

Display Spoiler

https://paste.libreelec.tv/premium-hawk.log

**dtech** · November 26, 2024 at 5:44 AM

Quote from Lirk

Display Spoiler

https://paste.libreelec.tv/premium-hawk.log

Based on the log, reinitialization of the SDIO bus fails, but I don't really understand why.

Was this a clean install? Because based on the amount of installed addons, I wouldn't guess that.

If you have upgraded from a previous system or restored a backup from an older system, I would definitely recommend performing a clean installation. Also, if the dtb you are using comes from an external source, that could also be a reason. Only use dtbs from the device_trees directory.

**chewitt** · November 26, 2024 at 9:02 AM

Quote from dtech

Was this a clean install? Because based on the amount of installed addons, I wouldn't guess that.

Due to those add-ons being installed, support ends here too.

Official:Forum rules/Banned add-ons - Official Kodi Wiki

Lirk · November 26, 2024 at 4:12 PM

Quote from dtech

Was this a clean install?

Yes.

I think that problem gone in new releases with some fixes in new kernels 5.x/6.x.

So, about software deinterlace problem... In LE 16.5/17.6 releases software deinterlace worked properly with doubling framerate. But from version 18.x deinterlace works poor with frame dropping. Hardware deinterlace works properly, but videos a little blurry with it in comparison with software deinterlace.

Just compare playback this interlaced video: https://samples.ffmpeg.org/MPEG2/interlaced/burosch1.mpg in version 17.6 and in 18.9 with disabled hardware acceleration.

**Da Flex** · November 26, 2024 at 7:49 PM

Lirk As mentioned by chewitt , no more support for you under current conditions.

If you still have questions, open a new thread, and provide a clean log.

Thread

Forum Rules

General Conduct

Be polite and respectful to forum staff and other users
Be polite and respectful towards this project and other projects
Be patient, user and staff are spread all over the world, an answer may take time

Posting

One topic per thread
Posts should be written in English (add text in your native language if needed)
Be as descriptive and detailed as possible. We are not mind readers!
Do not cross-post or double-post
Do not post or promote external URL links to products, a name description is

…

newphreak

March 15, 2016 at 1:02 AM