MiSTer FPGA Forum

Hello.
I'm having trouble using the Edimax EW-7811UN v2 WiFi dongle After a week of reading forums and following tutorials I'm not able to make it work. No connection, no wifi icon on menu. nothing.

I was wondering if any of you know how to do make it work or is having the same issue.

When I run lsusb it is recognized as Bus 001 Device 004: ID 7392:b811 Edimax Technology Co., Ltd Edimax N150 Adapter

My wpa_supplicant.conf file seems to be fine and when I run de wifi.sh script it seems to me it does nothing at all.

Any Idea? It seems the first version of the dongle works fine but I have the version 2.

Thank you.

It should work, just with a different driver, since they changed the chip with the v2. I don't have the v2 (just the v1), but I do have a TP-Link TL-WN725N, which I believe uses the same chip as the v2 (RTL8188EU; though when it comes to Realtek Wi-Fi, "same chip" can be a somewhat squishy concept). The wifi.sh script initially showed a "Failed to bring up wlan0" message, but it still worked.

If you run

ifconfig -a

after plugging in the dongle, do you see a "wlan0" interface?

If you run

dmesg | grep 8188e

after plugging in the dongle, is there any output? If the driver is binding you should get something like this:

[   32.171117] usbcore: registered new interface driver rtl8188eu
[   32.793282] ==> rtl8188e_iol_efuse_patch

ExCyber wrote: ↑Sun Oct 13, 2024 7:44 pm

It should work, just with a different driver, since they changed the chip with the v2. I don't have the v2 (just the v1), but I do have a TP-Link TL-WN725N, which I believe uses the same chip as the v2 (RTL8188EU; though when it comes to Realtek Wi-Fi, "same chip" can be a somewhat squishy concept). The wifi.sh script initially showed a "Failed to bring up wlan0" message, but it still worked.

If you run

Code: Select all

ifconfig -a

after plugging in the dongle, do you see a "wlan0" interface?

If you run

Code: Select all

dmesg | grep 8188e

after plugging in the dongle, is there any output? If the driver is binding you should get something like this:

Code: Select all

[   32.171117] usbcore: registered new interface driver rtl8188eu
[   32.793282] ==> rtl8188e_iol_efuse_patch

Thank you for taking the time to answer.

After running:

ifconfig -a

I get:

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.2.4  netmask 255.255.255.0  broadcast 192.168.2.255
        ether d6:5b:1c:e5:e3:b0  txqueuelen 1000  (Ethernet)
        RX packets 101  bytes 13480 (13.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 72  bytes 8798 (8.5 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 39  base 0xe000  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 128  bytes 9472 (9.2 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 128  bytes 9472 (9.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

After running:

dmesg | grep 8188e

I get:

[   12.369049] 8188eu: version magic '5.13.12-MiSTer SMP mod_unload ARMv7 p2v8 ' should be '5.15.1-MiSTer SMP mod_unload ARMv7 p2v8 '

I'm not sure what to do with this info but the second output message seems promising. Any idea?

Seems like you're using a kernel module for kernel 5.15.1 on kernel 5.13.12, which is likely to break. You need the kernel to match the module. Did you fudge around with kernel modules/drivers?

Bas wrote: ↑Tue Oct 15, 2024 4:29 pm

Seems like you're using a kernel module for kernel 5.15.1 on kernel 5.13.12, which is likely to break. You need the kernel to match the module. Did you fudge around with kernel modules/drivers?

At this point I'm not sure. I followed bunch instructions and maybe I have a mess of drivers.

I just did a fresh install and now I'm getting the following messages:

wlan0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 08:be:ac:42:72:a6  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

/root# dmesg | grep 8188e
[   12.203724] usbcore: registered new interface driver rtl8188eu
[   13.225238] ==> rtl8188e_iol_efuse_patch
[   20.140238] ==> rtl8188e_iol_efuse_patch
[   26.948237] ==> rtl8188e_iol_efuse_patch
[   33.745238] ==> rtl8188e_iol_efuse_patch
[   40.557239] ==> rtl8188e_iol_efuse_patch
[   47.357238] ==> rtl8188e_iol_efuse_patch
[   54.153238] ==> rtl8188e_iol_efuse_patch
[   60.957238] ==> rtl8188e_iol_efuse_patch
[   67.756237] ==> rtl8188e_iol_efuse_patch
[   74.557239] ==> rtl8188e_iol_efuse_patch
[   81.357237] ==> rtl8188e_iol_efuse_patch
[   88.165239] ==> rtl8188e_iol_efuse_patch
[   94.962239] ==> rtl8188e_iol_efuse_patch
[  101.764238] ==> rtl8188e_iol_efuse_patch
[  108.565238] ==> rtl8188e_iol_efuse_patch
[  115.363238] ==> rtl8188e_iol_efuse_patch
[  122.158238] ==> rtl8188e_iol_efuse_patch

Still not getting wifi icon on mister menu nor connection. Any idea.
Thanks again.

OK, SOLVED!!!

Now I have connection working as expected. After your diagnostic it was obvious I had a conflict with the drivers and the kernel after trying too many things for this to work. So after a fresh reinstall the kernel and the default module match then all I did was replace the wifi.sh script on my mister from the the one on the official repo. I'm not sure why after a fresh reinstall the wifi.sh wasn't working but after replacing the script it worked. Now the script is running and is letting me config the wifi network as as expected.

Thank you very much for your help.