MX Linux Forum

JayM wrote: Sun Aug 09, 2020 2:10 am Exactly what brand and model of USB wifi dongle is it?

sunrat wrote: Sun Aug 09, 2020 2:15 am A search shows that device ID 0bda:f179 is rtl8188fu. Try the driver at https://github.com/corneal64/Realtek-US ... er-Drivers

Vipul88 wrote: Sun Aug 09, 2020 2:29 am

sunrat wrote: Sun Aug 09, 2020 2:15 am A search shows that device ID 0bda:f179 is rtl8188fu. Try the driver at https://github.com/corneal64/Realtek-US ... er-Drivers

i will check and let u know

JayM wrote: Mon Aug 10, 2020 12:22 am Could be a kernel issue. That 4.19.0-6 kernel is outdated and vulnerable anyway. You should install Debian 64 bit (4.19) which at this time is 4.19.0-10, from MX Package Installer, Popular Apps, Kernels category. Then run MX Boot Options and select it as the default, then click Apply and reboot. If that doesn't fix your lockups you have something else wrong with your installation that probably isn't even related to wifi drivers.

JayM wrote: Mon Aug 10, 2020 12:33 am Another thing I see: per your Quick System Info your CPU temperature was 54 degrees and the maximum temperature allowed by your CPU before it does a thermal shutdown is 67.4 degrees. However, temperatures reported by inxi aren't necessarily all that accurate. I recommend that you right-click on your panel and install the sensors plugin or change your conky to one that shows CPU temperature and monitor it. It's possible that your browsers combined with whatever websites your loading are causing your CPU temperature to climb too high and that's what's causing the problem. 54 degrees seems rather high for a desktop computer's CPU: mine only gets that hot when it's under a big load.

https://ark.intel.com/content/www/us/en ... 0-ghz.html

Huckleberry Finn wrote: Mon Aug 10, 2020 8:37 am 0bda:f179 => rtl8188fu

Code: Select all

git clone https://github.com/kelebek333/rtl8188fu

Code: Select all

sudo dkms add ./rtl8188fu ; sudo dkms build rtl8188fu/1.0 ; sudo dkms install rtl8188fu/1.0

Code: Select all

sudo cp ./rtl8188fu/firmware/rtl8188fufw.bin /lib/firmware/rtlwifi/

Code: Select all

sudo mkdir -p /etc/modprobe.d/ ; sudo touch /etc/modprobe.d/rtl8188fu.conf

Code: Select all

echo "options rtl8188fu rtw_power_mgnt=0 rtw_enusbss=0" | sudo tee /etc/modprobe.d/rtl8188fu.conf

Huckleberry Finn wrote: Tue Aug 11, 2020 8:37 am I,too think that the issue shouldn't be related to installing a driver. Also this one is proven to work (not only with MX).

"Maybe" for you have 2 additional repos.. or something else ...

If it was a clean MX install and then you installed the driver this way, I've no doubt it would work flawlessly... (Maybe you try that on a tiny partition, say 8 GB ).

Huckleberry Finn wrote: Tue Aug 11, 2020 9:49 am Yep. No matter both are same versions..

Anyway, on Grub you'll see them as "MX 19 blahblah on sdaX" and "MX .. on sdaY"

You can also label their partitions on Gparted, say, the current one as MX and the new one as TEST or so ... that will make things easier in general, to recognize which is which..

Huckleberry Finn wrote: Tue Aug 11, 2020 8:37 am I,too think that the issue shouldn't be related to installing a driver. Also this one is proven to work (not only with MX).

"Maybe" for you have 2 additional repos.. or something else ...

If it was a clean MX install and then you installed the driver this way, I've no doubt it would work flawlessly... (Maybe you try that on a tiny partition, say 8 GB ).

Huckleberry Finn wrote: Mon Aug 10, 2020 8:37 am 0bda:f179 => rtl8188fu

Code: Select all

git clone https://github.com/kelebek333/rtl8188fu

Code: Select all

sudo dkms add ./rtl8188fu ; sudo dkms build rtl8188fu/1.0 ; sudo dkms install rtl8188fu/1.0

Code: Select all

sudo cp ./rtl8188fu/firmware/rtl8188fufw.bin /lib/firmware/rtlwifi/

Code: Select all

sudo mkdir -p /etc/modprobe.d/ ; sudo touch /etc/modprobe.d/rtl8188fu.conf

Code: Select all

echo "options rtl8188fu rtw_power_mgnt=0 rtw_enusbss=0" | sudo tee /etc/modprobe.d/rtl8188fu.conf

Huckleberry Finn wrote: Wed Aug 12, 2020 3:14 am P.S. In case you decide to remove one of the MXs and let one only, you may need to start MX Boot Repair first and give the Grub's control to the one that will stay. (Or later do it on live-session if you forget doing that).

https://ibb.co/sjd3X1q => https://ibb.co/6W31fCc => https://ibb.co/NVRpYgQ

Also remember that you can take a snapshot with "MX Snapshot" when everything's fine, and have your own iso under your hand somewhere, so you won't need to do them again and again ..

Vipul88 wrote: Wed Aug 12, 2020 3:30 am after i make the snapshot in a pendrive will it load as live if i save it in a usb stick?

JayM wrote: Wed Aug 12, 2020 3:36 am

Vipul88 wrote: Wed Aug 12, 2020 3:30 am after i make the snapshot in a pendrive will it load as live if i save it in a usb stick?

Yes, if you use MX Live USB Maker to write it to the thumbdrive in full-feature mode. I always keep a spare thumbdrive set aside, and redo and reburn the snapshot about once a week. I also back up everything in my home directory including hidden files and folders to an external hard drive. Then if something happens I can reinstall my personalized MX along with the apps I've added, restore all my data, and I'm up and running again with little or no data lost or wasted time reconfiguring MX and reinstalling apps from scratch. What would ordinarily be a disaster becomes a mere annoyance.

Huckleberry Finn wrote: Fri Aug 14, 2020 7:45 am To make it clear: After you installed and saw it was working, you were (at least once) able to connect to internet but now can't .. Or never connected ? (Sometimes, tiny things cause frustrations.. When you right-click on the icon on panel, are the top 3 boxes ("enable ...") checked? If not, do that )

Huckleberry Finn wrote: Fri Aug 14, 2020 12:41 pm Though the device itself looks working:

Code: Select all

rfkill unblock all

Bluetooth conflicts with the wi-fi at 2.4 Ghz. So,

Menu => Session & Startup => Application Autostart tab: uncheck Blueman , Reboot.
https://docs.xfce.org/_media/xfce/xfce4 ... ostart.png

If not again: Enter router settings (192.168...) change 802.11 mode from b/g/n (or "mixed") to b/g or g only (discard "n" mode as some devices have problems with that).

While you're at it, select a fixed channel, preferably Channel 1 , rather than "Auto" .. Apply ...

Vipul88 wrote: Sun Aug 16, 2020 10:04 am

Huckleberry Finn wrote: Wed Aug 26, 2020 12:42 pm viewtopic.php?f=104&t=57280&start=20#p591444

$ usb-devices

T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev≠= 4 Spd=480 MxXh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0bda ProdID=f179 Rev=00.00
S: Manufacturer=Realtek
S: Product=802.11n
S: SerialNumber=00E0202FD755
C: #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=500mA
I: If#=0x0 Alt= 0 #EPs= 3 Xls=ff(vend.) Sub=ff Prot=ff Driver=rtl8188fu

Huckleberry Finn wrote: Thu Aug 27, 2020 8:56 am In fact, that was just according to the model name (nothing to lose) but the best is the QSI or at least

Code: Select all

inxi -Nxxx

or lsusb when the device is attached, so that we know the exact chip no and what's needed ...

Also, have you right-clicked on the Network icon on panel? (Check all 3 boxes: "Enable ..." )

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 
           serial: 00E0202FD755 
pedro_lucas@bento:~
$ 

Huckleberry Finn wrote: Thu Aug 27, 2020 9:27 am Thank you, too. Sadly this shows only wired (ethernet) card. What about lsusb ? (when the device is attached)

Edit: Saw you edited the post above and it's here:

Vendor=0bda ProdID=f179
Driver=rtl8188fu

So, it's exactly the same device with the correct driver. Then, there must be something else.

Oh: If you didn't:

Code: Select all

rfkill unblock all

If not again, enter Bios Settings and check if there's something "disabled" related to "network" ... (Also check if there's a tiny wireless button to switch off/on or the Fn Keys)

pedro_lucas@bento:~
$ lsusb
Bus 001 Device 002: ID 0bda:f179 Realtek Semiconductor Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 10c4:8108 Cygnal Integrated Products, Inc. 
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
pedro_lucas@bento:~
$ rfkill unblock all
pedro_lucas@bento:~
$ 

$ inxi
CPU: Single Core AMD Sempron LE-1250 (-UP-) speed: 2210 MHz Kernel: 5.4.0-3-amd64 x86_64 
Up: 1h 27m Mem: 1135.4/2932.3 MiB (38.7%) Storage: 232.88 GiB (6.8% used) Procs: 166 
Shell: bash 5.0.3 inxi: 3.0.36

aldQueiroz wrote: Thu Aug 27, 2020 10:59 am The command "rfkill" didn't show any effect...

Huckleberry Finn wrote: Thu Aug 27, 2020 1:04 pm 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.

• 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

Huckleberry Finn wrote: Thu Aug 27, 2020 6:34 pm 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

• 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.

Huckleberry Finn wrote: Fri Aug 28, 2020 1:03 pm 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 wrote: Fri Aug 28, 2020 1:37 pmbased on another chipset than Realtek...

aldQueiroz wrote: Fri Aug 28, 2020 1:37 pm... using "runit" as init system in my own machine (does it make it more fast and responsive?)

aldQueiroz wrote: Fri Aug 28, 2020 1:37 pmother 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!!

aldQueiroz wrote: Fri Aug 28, 2020 7:17 pm My conclusion: Realtek "sucks"! Even with the correct driver(?), Realtek chipsets do have intricacies which make them not feasible to use (with Linux).

tony37 wrote: Fri Aug 28, 2020 7:33 pm

aldQueiroz wrote: Fri Aug 28, 2020 7:17 pm My conclusion: Realtek "sucks"! Even with the correct driver(?), Realtek chipsets do have intricacies which make them not feasible to use (with Linux).

I have RTL8723DE wifi, for which I do need extra drivers on MX Linux but installing them was a piece of cake and it works fine. So it's foremost the FU variant which seems problematic...

aldQueiroz wrote: Fri Aug 28, 2020 7:17 pm Hi, I'm passing here for a last time just to report; I've got back another Wifi dongle I had lent to a friend, and made a test. It worked "out of the box" ! I'm not sure about which chipset it uses (probably Ralink), but the system immediately identified it and installed the due drivers (rt73usb, rt2x00usb, and rt2x00lib; and the system pulled ''ndiswrapper" again without my intervention (?), although it seems be using Linux drivers only...)
Well, what matters is Wifi is working now, without "shenanigans"..
My conclusion: Realtek "sucks"! Even with the correct driver(?), Realtek chipsets do have intricacies which make them not feasible to use (with Linux). Given that Wifi adapters are cheap, there's no reason to spend time trying to make a troubled one work... Better get another already proved!
I thank you , Huckleberry Finn, for all your interest and kind assistance!! Surely, We'll still chat a lot about how to make MX Linux fives all we deserve!!
Regards!

Vipul88 wrote: Tue Sep 01, 2020 10:40 pm (...)

aldQueiroz glad to know someone had the exact same problem i had before.
can you please tell which is the another wifi dongle i mean make and company, or some lsusb and other commands to understand which wifi dongle it is to for future preferences for me and other similar users. and what was preconfigured drivers installed etc.. for this specific wifi dongle.
P.s. i still cant connect my rtl8188fu and i have stopped worrying

aldQueiroz wrote: Fri Aug 28, 2020 10:15 am

Huckleberry Finn wrote: Thu Aug 27, 2020 6:34 pm 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..!

Vipul88 wrote: Tue Sep 01, 2020 10:40 pm

aldQueiroz wrote: Fri Aug 28, 2020 7:17 pm (...)

aldQueiroz glad to know someone had the exact same problem i had before.
can you please tell which is the another wifi dongle i mean make and company, or some lsusb and other commands to understand which wifi dongle it is to for future preferences for me and other similar users. and what was preconfigured drivers installed etc.. for this specific wifi dongle.
P.s. i still cant connect my rtl8188fu and i have stopped worrying

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: Ralink RT2501/RT2573 Wireless Adapter type: USB driver: rt73usb 
           bus ID: 1-1:2 chip ID: 148f:2573 serial: 12345 
pedro_lucas@bento:~
$ 

aldQueiroz wrote: Wed Sep 02, 2020 8:31 am

Vipul88 wrote: Tue Sep 01, 2020 10:40 pm

aldQueiroz wrote: Fri Aug 28, 2020 7:17 pm (...)

aldQueiroz glad to know someone had the exact same problem i had before.
can you please tell which is the another wifi dongle i mean make and company, or some lsusb and other commands to understand which wifi dongle it is to for future preferences for me and other similar users. and what was preconfigured drivers installed etc.. for this specific wifi dongle.
P.s. i still cant connect my rtl8188fu and i have stopped worrying

Vipul88, here are the specifications of the Wifi dongle which works out of the box:

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: Ralink RT2501/RT2573 Wireless Adapter type: USB driver: rt73usb 
           bus ID: 1-1:2 chip ID: 148f:2573 serial: 12345 
pedro_lucas@bento:~
$ 

Indeed, it is a Ralink chipset built-in USB dongle. As said before, the system immediately identified it and installed the due drivers (rt73usb, rt2x00usb, and rt2x00lib; and the system pulled ''ndiswrapper" without my intervention (by MX net assistant app), although it seems be using Linux drivers only... I believe such devices are quite cheap, easy to find. So, you'd rather get some of that, instead of spending hours, days trying to make a flawed Realtek chipset Wifi dongle work (but it's a pity when we, Linux' users, don't "prevail" over the idiosyncrasies of a lazy, "Windows driven" industry...!)
Good luck, and regards!

Vipul88 wrote: Sat Sep 19, 2020 9:38 am bought a new dongle here is the details about it,
vipul@primamx:~
1.$ inxi -Nxxx
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK P8 series driver: r8169
v: kernel port: e000 bus ID: 03:00.0 chip ID: 10ec:8168
Device-2: Ralink MT7601U Wireless Adapter type: USB driver: mt7601u bus ID: 2-1.5:4 chip ID: 148f:7601
serial: 1.0
2. lsusb
Bus 002 Device 004: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless Adapter
the wifi dongle i bought it in india for 300 rs. i.e <5$,
hope this will help to anyone viewing.
al in all realtek does not work ralink does

cherith_reddy wrote: Fri Nov 06, 2020 11:13 am i had the same problem on antix linux
it got solved here is the summary

SUMMARY

Problem: My USB WiFi adapter was not getting recognized by antiX 19.3, therefore I was not able to connect to WiFi

-> I was asked to execute this in terminal ~ inxi -Fxxxz ,for getting all information about of my system to check if the drivers are already available in antiX or if I have to update the kernel or install specific firmware.

-> I was asked to execute this in terminal ~ lsusb , for checking what chip set is present in my WiFi adapter
After executing this was one of the output
Bus 001 Device 004: ID 0bda:f179 Realtek Semiconductor Corp.
therefore It ended up being a realtek rtl8188fu.

-> Many have had problems with it and someone created a .deb installer for both the firmware and kernel driver, but I need at least kernel 4.19.XXX
Xecure checked in antiX 19.3 and the firmware is NOT included. To get it to work, I would have to install antiX on the System (if not done), update the kernel and test if the wifi USB adapter works out of the box. If it doesn’t, I can get the .deb installer from https://github.com/kelebek333/rtl8188fu

Copying and running the commands one at a time from the first gitlab link should be enough to install both the driver and firmware.

Then I can follow the other optional instructions to disable some features, as recommended. The set of instructions for disabling MAC Address Spoofing is only relevant for Network Manager (not used by default in antiX, which uses connman).

-> I did exactly as stated above
1. updated the kernel
(I needed to connect though Ethernet or using your phone (connected with USB), to install the 4.19 kernel, run Package Installer (white icon in the panel), search for kernel, and install the kernel-antix one that in the description mentions LTS (4.19.XXX).)
2. copied and ran the commands one at a time from the first git lab link.(https://github.com/kelebek333/rtl8188fu
3.then all problems solved I went to connman and I could see WiFi option now (for more clarity read the article by Xecure https://www.antixforum.com/forums/topic ... ntix-19-2/ and watch the video)


hope this migth help MX users to come to a proper solution

Vipul88 wrote: Sat Nov 07, 2020 10:25 pm i never had it connect to any wifi point, rtl8188eus showed wifi signals but could not connect to any. have tried kelebek333 drivers as well.

JayM wrote: Sun Nov 08, 2020 6:48 pm

Vipul88 wrote: Sat Nov 07, 2020 10:25 pm i never had it connect to any wifi point, rtl8188eus showed wifi signals but could not connect to any. have tried kelebek333 drivers as well.

Section 3.4.2 of the manual has detailed troubleshooting steps for solving that very problem.

JayM wrote: Sun Nov 08, 2020 6:48 pm

Vipul88 wrote: Sat Nov 07, 2020 10:25 pm i never had it connect to any wifi point, rtl8188eus showed wifi signals but could not connect to any. have tried kelebek333 drivers as well.

Section 3.4.2 of the manual has detailed troubleshooting steps for solving that very problem.