lwfinger

This problem has not been previously reported. I am not sure how many people are running this driver on 32-bit ARM. Unfortunately, I cannot read your photo at all. If...

One thing that just occurred to me: Make certain that the kernel you are running does not have either rtl8818eu or r8188eu built in. Use 'modinfo rtl8188eu' to test that....

I have learned that the "Kernel stack is corrupted" message arises when the system is built with -fstack-protector. Unfortunately, building the x86_64 version with that option does not cause a...

At this point, I have no idea what to try. When I copied the kernel source from the staging-next tree, the driver failed one of the startup routines, but did...

I have not forgotten about you. There is now a new branch 'kernel' in the repo, which contains the code found in the staging driver of the kernel with the...

I have not forgotten about this issue, but I have relatively little news. In branch v5.2.2.4 using the nl80211 driver interface, the control_ap script creates an AP that is issuing...

What do you mean they did not work? I built the driver with CONFIG_CONCURRENT_MODE enabled. It created two wireless devices, and each could connect to my AP, but not at...

Yes, that is how I enabled it for my system. Please do the command lsmod and post the results.

Please attach /var/lib/dkms/8188eu/v4.3.0.8_13968/build/make.log to this issue so that I can see what happened.

Two things come to mind: 1. ifconfig is deprecated - you should be using iw and friends, and 2. That device name is strange. I would expect something shorter. Please...