Realtek 8188eus(after getting a solution actually rtl8188fu) wifi usb not detected after driver make and install

[aldQueiroz]

"Googling around" for more references, I've just found out this:
viewtopic.php?f=108&t=56254
which leads to this:
https://askubuntu.com/questions/1062402 ... uctor-corp
And finally, this: https://github.com/kelebek333/rtl8188fu ... Well, I'm "walking in circles" !!...

[aldQueiroz]

So, the driver is loaded and the device's working.

I'd say this from the beginning: From Menu : Session and Startup => Autostart Apps: uncheck Bluetooth (Blueman) (so that it won't conflict with the wi-fi) https://docs.xfce.org/_media/xfce/xfce4 ... ostart.png

P.S. The names are similar but that one is another model with a different chip number. We also solved that several times in the forum :)

You can also:

Code: Select all

echo "blacklist rtl8xxxu" | sudo tee -a /etc/modprobe.d/rtl8xxxu.conf

Reboot.

Ok!! I'll do it, later (but I've had already unchecked Bluetooth...)

[Huckleberry Finn]

Yes but those (links) are what you already did :)

Your device began working. Just there's something else that prevents you connect to an Access Point.

This one is "so fine"

Code: Select all

pedro_lucas@bento:~
$ inxi -Nxxx
Network:   Device-1: NVIDIA MCP61 Ethernet vendor: Micro-Star MSI type: network bridge 
           driver: forcedeth v: kernel port: ee00 bus ID: 00:07.0 chip ID: 10de:03ef 
           Device-2: Realtek type: USB driver: rtl8188fu bus ID: 1-2:2 chip ID: 0bda:f179

and from now on you don't need to search what to install etc. (It's just a connection issue now but not driver .. )

P.S. If you'd turned off the internal wi-fi device: turn it on, too .

[aldQueiroz]

Yeah, the dongle is "alive", and finding all available Wi-fi nets, but still with some unknown issue impeaching connection..

Wifi_demesg & lsmod results.jpeg

P.S.: I tried to delete the "Wifi connection profile" I had settled before with SSID & password of my net and, when I tried to select it again form the list of available nets the dongle is "seeing", then I received the password request!
But again, it was unsuccessful on connecting... dmesg returned practically the same results after...

[Huckleberry Finn]

If the "circles" as if "being connected" are still there, you can try a different kernel: Say, 5.6 (I'm also on currently) from MX Package Installer (You'll see in the first tab (Popular Apps): "Kernels")

Also enter Router Settings and try these:

• Change 802.11 mode from "mixed" (or b/g/n) to b/g or g only (discard the n as some devices have problems with that)
• Change the channel from "Auto" to a fixed one, preferably Channel 1
• Change Security from WPA/WPA2 to WPA2

Reboot

[aldQueiroz]

Could yet be missing some pacakge to install?
I've found this :
https://www.linux.org/threads/cant-use-wi-fi.28047/

I'll plug th wire into the machine again and install the package firmware-realtek, and see what happens...

[aldQueiroz]

If the "circles" as if "being connected" are still there, you can try a different kernel: Say, 5.6 (I'm also on currently) from MX Package Installer (You'll see in the first tab (Popular Apps): "Kernels")

Also enter Router Settings and try these:

• Change 802.11 mode from "mixed" (or b/g/n) to b/g or g only (discard the n as some devices have problems with that)
• Change the channel from "Auto" to a fixed one, preferably Channel 1
• Change Security from WPA/WPA2 to WPA2

Reboot

HI, I've just made it as per your suggestion: I did the kernel upgrade to Debian 5.6 (more specifically, 5.6.0-2-amd64), but it didn't work...
I prefer not to mess with Router (modem) settings. It could bring other issues to connection of my other devices (and also, the Wifi troubled machine isn't meant to be used here, but rather another house, within a different Wifi network)
I decided to give a try to a Windows driver; MX Network assistant is easy to use, and installing of "ndiswrapper" was smoothly (wire connected, of course). But the App failed to apply a driver from the files within the CD which accompanies the dongle (I copied all its content to the HDD); although it supplies drives to all versions of Windows (from Xp to Win 10, both 32 and 64bit versions), the App failed on reading the *.inf files with installing instructions... I've got stuck, again..!

[Huckleberry Finn]

The last thing I can say (for sure):

• You're getting tired for nothing: Yours is not a driver issue from the minute you installed the fu driver and the device began working.
• Linux drivers are always better when available.
• Ndis was designed to work according to XP (drivers).
• You need to use either Linux drivers or Ndis. In case you'd like to turn back (that I recommend) remove Ndis via MX Network Assistant.

In case the modem is ZyXel: In my case I needed to add 0x as a prefix to the password (when typing to connect) exactly as displayed on modem settings . Say, when I typed password it wouldn't accept that but only 0xpassword. But that was only for wep encryption.

[aldQueiroz]

The last thing I can say (for sure):

• You're getting tired for nothing: Yours is not a driver issue from the minute you installed the fu driver and the device began working.
• Linux drivers are always better when available.
• Ndis was designed to work according to XP (drivers).
• You need to use either Linux drivers or Ndis. In case you'd like to turn back (that I recommend) remove Ndis via MX Network Assistant.

In case the modem is ZyXel: In my case I needed to add 0x as a prefix to the password (when typing to connect) exactly as displayed on modem settings . Say, when I typed password it wouldn't accept that but only 0xpassword. But that was only for wep encryption.

oh, I would love to get "tired for nothing' all the times I get troubles with malfunction of devices over Linux !!
I put Ndis as "blocked', but I can simply uninstall it through the same Network assistant; that's the easy part..
The dongle is identified as "LV-UW06', and the maker is "BGN' (a generic name for more one "made in China' cheap accessory...), there is no more information available on the case of the product, neither on the mini-CD which comes with it (the one for drivers installation, a thing that usually isn't necessary when using it with Windows, where this cheap pieces of c***p work out-of-the-box!)...
I can try that "0x" before the password; something has to work, eventually! Or, instead, I'll have to buy another Wifi dongle, but some based on another chipset than Realtek...

Thanks for all assistance, pal! I shall talk with you later about other "projects", like using "runit" as init system in my own machine (does it make it more fast and responsive?), and about other issues I couldn't yet solve satisfactorily (I'm struggling with " no sound through HDMI " since I started to use MX Linux -- but that's another story!!

[Huckleberry Finn]

based on another chipset than Realtek...

" Ralink ".

... using "runit" as init system in my own machine (does it make it more fast and responsive?)

No noticeable difference. Nice, though.

other issues I couldn't yet solve satisfactorily (I'm struggling with " no sound through HDMI " since I started to use MX Linux -- but that's another story!!

Yes, requires a new thread :)

P.S. Remembered one more thing: Disable "Secure Boot" in Bios (if there's such an option of course).