One specific Wireless wifi won't connect under Ubuntu under 20.04 focal; others connect fine and connect fine when booted into other OS's

ajmcello · 02-24-2020, 02:42 PM

Ok. I'm running a multi-boot system. I have two wifi adapters.

Under one OS, I can connect just fine using the same hardware, mac address, etc, to a specific wifi. It is a public wifi, so it goes through an authorization screen that asks me to click yes or log in, or something of that sort. Works fine, and it is cached to the mac address so that I don't have to repeat it.

This has worked fine until recently. I could boot between OS's and not have to login again after the first initial wifi login.

Now, for some reason, only in Ubuntu, this one particular won't connect, using either wifi adapter. I tried binding a different or alternate mac address, it still won't connect. It is a public wifi.

What can I do to try and resolve this?

Of course I've rebooted, ran all updates, etc, clicked "Forget" and removed the wifi in question and re-added it several times. It just never connects using Ubuntu.

Thanks in advance

frankbell · 02-24-2020, 07:23 PM

It would likely help if you filled out the story:

What is the other OS, the one that connects, and what are the chipsets in the two wireless adapters, both the one that works and the one that has become uncooperative with Ubuntu?

ajmcello · 02-29-2020, 04:26 PM

Quote:

Originally Posted by frankbell

It would likely help if you filled out the story:

What is the other OS, the one that connects, and what are the chipsets in the two wireless adapters, both the one that works and the one that has become uncooperative with Ubuntu?

AC9560 && A6210

Other OS where it always works (Win10 Pro).

Anyway, under Ubuntu, it finally resolved itself. Most wifi's connected fine, but one, actually two, one day stopped working.

Even booted up a newly downloaded live cd and it still did not connect to the same wifi that my installed Ubuntu would not connect to.

Have no idea what changed. Works now.

frankbell · 02-29-2020, 09:24 PM

That's freaky. Glad it's working.

Sounds like what one tech I used to know would refer to as an "FM problem."

If he got to the job site and the problem had magically gone awa, and if the customer asked what happened, he'd say, "It was an FM problem," then quickly make his exit.

FM, loosely translated, stands for "freaking magic."

ajmcello · 03-01-2020, 03:56 AM

Quote:

Originally Posted by frankbell

That's freaky. Glad it's working.

Sounds like what one tech I used to know would refer to as an "FM problem."

If he got to the job site and the problem had magically gone awa, and if the customer asked what happened, he'd say, "It was an FM problem," then quickly make his exit.

FM, loosely translated, stands for "freaking magic."

Must be. Literally thought a live usb would work. Had finished watching I think episode II of this new docu called In his own words (Unabomber) before reading this. Guy left false clues that were labeled “FC.” FBI had to figure out what it meant and came up with “Fuckin Crazy.” Ha.

westernira12 · 03-07-2020, 05:02 AM

Quote:

Originally Posted by frankbell

It would likely help if you filled out the story:

What is the other OS, the one that connects, and what are the chipsets in the two wireless adapters, both the one that works and the one that has become uncooperative with Ubuntu?

Thanks for sharing!! I don’t know much about this but got something more informative on this. I even found out this site called routerlogin.one which has a lot of guides on WiFi, so maybe that might help resolve your issues as well.

Let me know if you need more assistance.

yancek · 03-07-2020, 06:33 AM

Quote:

One specific Wireless wifi won't connect under Ubuntu under 20.04

Ubuntu 20.04 is a beta (test) release so by installing and using it, you have volunteered to test the distribution. That's the purpose of having it available before the official release, to find problems and hopefully eliminate them prior to the actual release. The proper procedure when you have a problem is to contact Canonical/Ubuntu informing them of the specifics of the problems and any solution if available. This of course, so they can make changes prior to the actual release.

kareempharmacist · 08-23-2020, 02:28 PM

I had a problem once. I have a TP-Link wireless dongle that was working well. I found out that restarting from Linux to Windows or from Windows to Linux makes the wireless dongle fail to connect or disconnects after a while. The only solution is to cold reboot the computer which means shutting down the computer and powering it on again. This solved the problem without any tweaking. I guess it's a power problem in the dongle. It doesn't shut down properly between reboots.
output of the command

Code:

sudo lsusb

Code:

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter
Bus 001 Device 005: ID 04e8:6031 Samsung Electronics Co., Ltd 
Bus 001 Device 004: ID 13fd:0840 Initio Corporation INIC-1618L SATA
Bus 001 Device 003: ID 03f0:1941 HP, Inc 
Bus 001 Device 007: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

The output of the command

Code:

sudo lshw -C network

Code:

*-network                 
       description: Ethernet interface
       product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:01:00.0
       logical name: eth0
       version: 0c
       serial: 6c:4b:90:6c:cc:57
       capacity: 1Gbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=r8169 firmware=rtl8168g-2_0.0.1 02/06/13 latency=0 link=no multicast=yes port=MII
       resources: irq:16 ioport:e000(size=256) memory:f7000000-f7000fff memory:f0000000-f0003fff
  *-network
       description: Wireless interface
       physical id: 2
       bus info: usb@1:8
       logical name: wlan0
       serial: f8:d1:11:b4:2f:73
       capabilities: ethernet physical wireless
       configuration: broadcast=yes driver=rtl8192cu driverversion=5.2.15-antix.1-amd64-smp firmware=N/A ip=192.168.0.107 link=yes multicast=yes wireless=IEEE 802.11

The output of the command

Code:

inxi -N

Code:

Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 
           Device-2: Realtek RTL8188CUS 802.11n WLAN Adapter type: USB driver: rtl8192cu

I triple booting Windows 7 and Windows 10 Pro and MX Linux. All are 64 bit.

The output of the command

Code:

uname -a

Code:

Linux MX-Linux 5.2.15-antix.1-amd64-smp #1 SMP PREEMPT Sun Sep 22 17:26:24 EEST 2019 x86_64 GNU/Linux

Hope this helps.

colorpurple21859 · 08-23-2020, 02:37 PM

Quote:

I found out that restarting from Linux to Windows or from Windows to Linux makes the wireless dongle fail to connect

I had this problem on a 2012 hp laptop with the internal wireless card. If I remember correctly it had something do with the rfkill switch.