Just installed Fedora 44 and it will not connect to my WiFi

S

SuperWookie68

Member
Joined
Aug 20, 2024
Messages
100
Reaction score
23
Credits
1,494
Hey everyone. So I'm once again having trouble connecting a Linux OS to my WiFi. I’ve dabbled with Linux in the past and for some reason always ended up back on my Windows or Mac. I guess it’s because it’s just easier to use, and the PC with windows 11 has my Steam games on it. But for a multitude of reasons, I’d like to get back into using Linux as my daily driver and only use windows for playing my few steam games.

So I have a PC that has 2 separate NVMe drives. One is for windows, the other is for Linux. At one point a few years ago, I did have KDE Plasma running and working on the second drive and windows on the first drive. That was easy setting that up after watching a good video on youtube.

But the problem I’m running into now, and have ALWAYS run into when using Linux, is that it NEVER connects to my WiFi. I’ve used Pop OS!, Mint, KDE Plasma and Ubuntu. And now Fedora. And I’ve used them on my PC and my Macbook Air. And EVERY SINGLE TIME, it’s an absolute nightmare trying to get the damn Linux OS to connect to my WiFi. But after days or weeks of futzing around with it and asking questions, it usually works. Sometimes by someone that knows what they're doing. Other times by dumb luck and weeks of messing around. And yet stupid me never wrote down the solution.

So I'm back at it, just downloaded and installed Fedora 44 on the second drive. It loaded and installed fine. I then go into the Network settings and try to set it up so it will connect to the internet. It shows my network, I can see it, I can select it, and then it “tries” to connect, but it never does. It just spins and spins forever and constantly keeps asking me for my password, even though it's correct and already input. I’ve already done and checked the “normal” issues most people say I need to check. Turn off randomized MAC address. Turn off Fast Boot. Try to delete or forget the network and set it up again from scratch. I've unplugged my power cord from the PSU, turned off the switch and let the computer sit for 5-10 mins. Plug it back in and immediately boot into Fedora. I've ran certain command lines that people have suggested and yes, Fedora can see my WiFi network, it just won't connect. Nothing works.

I have a Gigabyte B550 Vision D-P Mobo and it has an Intel AX200 Wireless Communication Module on it for WiFi. It works for Windows 11. And no other wireless device in our townhouse has any problem connecting to the WiFi network, OTHER than Linux OS's.

This is what I get when I type in ifconfig in the terminal:
1.jpeg


And after someone had me type this command line in: grep -iA3 network <<< $(lspci -nnk)
It spit this out:
50:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a)
Subsystem: Intel Corporation Wi-Fi 6 AX200NGW [8086:0084]
Kernel Driver in use: iwlwifi
Kernel modules: iwlwifi

Nothing is working.

So just need some help figuring out why this always happens? And how do I fix it?

Thank you
 


The Intel AX200 is natively supported by the kernel, but it has known issues with Wi-Fi 6 handshakes and power management under Linux that cause this exact password-loop behavior. It isn't an installation error, it's a driver/router conflict.

Because the underlying networking stack (NetworkManager) is the same across Fedora, Ubuntu, and Mint, changing distros won't fix it. We need to see the exact error code.

Run this command in your terminal:

Code: 
sudo journalctl -u NetworkManager -f

While it's running, try to connect to your Wi-Fi. Once it fails, hit CTRL+C to stop the command, and copy/paste the output back here. The log lines will show the exact reason the authentication is failing.

P.S. Mac/Windows are proprietary systems with an astronomical amount of funding. Linux is a Free Open Source Software alternative powered globally by volunteers and some paid organizations; if you're transition to Linux is a rough one it's not because Linux is incapable, it's because you're unfamiliar with the systems and how to troubleshoot properly.

Additionally. Make sure you've set the proper security protocol for your connection, i.e. WPA2/WPA3; I've seen countless newbies overlook this.
 
AlphaObeisance said:
The Intel AX200 is natively supported by the kernel, but it has known issues with Wi-Fi 6 handshakes and power management under Linux that cause this exact password-loop behavior. It isn't an installation error, it's a driver/router conflict.

Because the underlying networking stack (NetworkManager) is the same across Fedora, Ubuntu, and Mint, changing distros won't fix it. We need to see the exact error code.

Run this command in your terminal:

Code: 
sudo journalctl -u NetworkManager -f

While it's running, try to connect to your Wi-Fi. Once it fails, hit CTRL+C to stop the command, and copy/paste the output back here. The log lines will show the exact reason the authentication is failing.

P.S. Mac/Windows are proprietary systems with an astronomical amount of funding. Linux is a Free Open Source Software alternative powered globally by volunteers and some paid organizations; if you're transition to Linux is a rough one it's not because Linux is incapable, it's because you're unfamiliar with the systems and how to troubleshoot properly.

Additionally. Make sure you've set the proper security protocol for your connection, i.e. WPA2/WPA3; I've seen countless newbies overlook this.
Click to expand...
I will do this as soon as I get home later today and post back here. Thank you

And thank you for explaining as well, I appreciate that. I'm a beginner to linux and not a computer expert, but it's nice to learn WHY things happen and most people don't ever mention those things.

And I did know that the reason WiFi and certain things don't "work" well out of the box for Linux isn't because it's bad or doesn't work. It is very frustrating, but I know Apple and Windows and other PC companies spend billions to make sure their systems and stuff works, while Linux is free and trying to fight all sorts of problems windows and apple have. It's one of many reasons I appreciate and respect the Linux community and want to be part of it. It's absolutely amazing how many people spend their free time not only creating for Linux, but also helping others. For the most part, it's a great community and again, thank you for explaining things instead of just telling me what to do. Very much appreciated.
 
My advise would be to try and avoid Linux "tutorials". I too fell down that rabbit hole when I began using Linux because it was "comfortable" and "inspiriting" if you will, to have a face on a screen walking me through the things I was trying to learn. But frankly, all I was doing at that point was memorizing the process. It wasn't until I got into Arch Linux, which required that I read the Arch Wiki linked above, that I truly began to understand the fundamentals of how things work on Linux.

Make no mistake. I still use google daily, at this point I've forgotten more than I remember. So I might encounter a niche problem, or have forgotten a particular command that warrants a quick search on Google or a prompt to AI to refresh my memory; but having read the documentation my forgetfulness generally only needs a gentle point in the right direction before I'm back to doing my own thing. You don't want to be come dependent on tutorials (or even more dangerously, AI) to resolve your issues. And I'm an avid AI user, I use it daily. But I generally understand the conversations that I'm having because I've already studied most of what is being discussed and I'm either seeking further understanding or trying to expedite the learning of certain contexts. Keep in mind I've worked pretty extensively with AI since it's come about, so I'm quite familiar with prompting properly so to make "dumb" AI respond more intelligently and reliably.

Point stands though; if you truly do want to learn (and understand) Linux; I can assure you that reading the Arch Wiki will 100% help you fundamentally as a user; and will absolutely make the Linux space feel more like a playground than a minefield. I can assure you, it's only as complicated as you make it out to be. Think of it like putting on a new pair of custom leather work boots. At first, they're going to kill your feet, you're going to cramp and chafe. But, once you break them in, you'll have boots that will last you for years, and can be rebuilt; unlike some name brand alternative that's going to fall apart and require replacement because they lack welted construction; charging you a premium for the brand rather than the quality. Linux is really no different.
 
So, I can't copy and paste it. I'm not able to get an internet connection at all. I'm writing to you on my Macbook. There's no way I know of to copy something from Linux on one drive of my desktop computer, then restart the computer and paste into Windows on another drive of the same computer. So I have to paste photos of what it shows.

The white line is highlighted to give you a delineation point. To see where the last line ends on one photo and begins on the next photo.

So I typed in the code, immediately went to Settings and tried connecting. Then after it spun and spun and spun and didn't connect and came back with the screen that says put in your password to connect, that's when I het Ctrl C.
IMG_0299.JPG

IMG_0300.JPG
 
Take this with a grain of salt, but the computer thinks your credentials are incorrect. This could be for a number of reasons. The most common I've encountered personally is the use of special characters in a password. I've found that certain specialized characters don't play nice when connecting via wifi; but I honestly cannot explain why.

I would try to delete the connection

Code: 
nmcli connection delete id "Cyborgitron2400"

then

Code: 
nmcli device wifi connect "Cyborgitron2400" password "AwesomePassword"

Or you could do

Code: 
nmcli device wifi connect "Cyborgitron2400" --ask

Which will prompt you for password instead of typing it in a single string if you prefer.

I seem to recall having once set a password that required I escape the characters when inputting the password using forward slashes \ or something ruther but don't quote me on that. Someone wiser than I will have to elaborate on what I"m talking about here, hopefully I've articulated it well enough they can decipher what I'm referencing too.
 
SuperWookie68 said:
Hey everyone. So I'm once again having trouble connecting a Linux OS to my WiFi. I’ve dabbled with Linux in the past and for some reason always ended up back on my Windows or Mac. I guess it’s because it’s just easier to use, and the PC with windows 11 has my Steam games on it. But for a multitude of reasons, I’d like to get back into using Linux as my daily driver and only use windows for playing my few steam games.

So I have a PC that has 2 separate NVMe drives. One is for windows, the other is for Linux. At one point a few years ago, I did have KDE Plasma running and working on the second drive and windows on the first drive. That was easy setting that up after watching a good video on youtube.

But the problem I’m running into now, and have ALWAYS run into when using Linux, is that it NEVER connects to my WiFi. I’ve used Pop OS!, Mint, KDE Plasma and Ubuntu. And now Fedora. And I’ve used them on my PC and my Macbook Air. And EVERY SINGLE TIME, it’s an absolute nightmare trying to get the damn Linux OS to connect to my WiFi. But after days or weeks of futzing around with it and asking questions, it usually works. Sometimes by someone that knows what they're doing. Other times by dumb luck and weeks of messing around. And yet stupid me never wrote down the solution.

So I'm back at it, just downloaded and installed Fedora 44 on the second drive. It loaded and installed fine. I then go into the Network settings and try to set it up so it will connect to the internet. It shows my network, I can see it, I can select it, and then it “tries” to connect, but it never does. It just spins and spins forever and constantly keeps asking me for my password, even though it's correct and already input. I’ve already done and checked the “normal” issues most people say I need to check. Turn off randomized MAC address. Turn off Fast Boot. Try to delete or forget the network and set it up again from scratch. I've unplugged my power cord from the PSU, turned off the switch and let the computer sit for 5-10 mins. Plug it back in and immediately boot into Fedora. I've ran certain command lines that people have suggested and yes, Fedora can see my WiFi network, it just won't connect. Nothing works.

I have a Gigabyte B550 Vision D-P Mobo and it has an Intel AX200 Wireless Communication Module on it for WiFi. It works for Windows 11. And no other wireless device in our townhouse has any problem connecting to the WiFi network, OTHER than Linux OS's.

This is what I get when I type in ifconfig in the terminal:
View attachment 31927

And after someone had me type this command line in: grep -iA3 network <<< $(lspci -nnk)
It spit this out:
50:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a)
Subsystem: Intel Corporation Wi-Fi 6 AX200NGW [8086:0084]
Kernel Driver in use: iwlwifi
Kernel modules: iwlwifi

Nothing is working.

So just need some help figuring out why this always happens? And how do I fix it?

Thank you
Click to expand...
go spend $20 on a usb wifi card that is fully linux compatible. lots of them out there. Or replace the one in your computer with a working one. It is not that difficult to replace them.
 
AlphaObeisance said:
Take this with a grain of salt, but the computer thinks your credentials are incorrect. This could be for a number of reasons. The most common I've encountered personally is the use of special characters in a password. I've found that certain specialized characters don't play nice when connecting via wifi; but I honestly cannot explain why.

I would try to delete the connection

Code: 
nmcli connection delete id "Cyborgitron2400"

then

Code: 
nmcli device wifi connect "Cyborgitron2400" password "AwesomePassword"

Or you could do

Code: 
nmcli device wifi connect "Cyborgitron2400" --ask

Which will prompt you for password instead of typing it in a single string if you prefer.

I seem to recall having once set a password that required I escape the characters when inputting the password using forward slashes \ or something ruther but don't quote me on that. Someone wiser than I will have to elaborate on what I"m talking about here, hopefully I've articulated it well enough they can decipher what I'm referencing too.
Click to expand...
Ok, I'm using my iPhone as a wifi hotspot, so now I'm typing this to you from Fedora. So I typed in that first line of command exactly as written and it spit this out:

Code: 
nmcli connection delete id "Cyborgitron2400"
Error: unknown connection 'Cyborgitron2400'.
Error: cannot delete unknown connection(s): id 'Cyborgitron2400'.

So it's saying it's an "unknown" connection?!?! How the F is that possible. It shows up in the network settings as Cyborgitron2400. It won't "forget" it from there. And then the command line won't delete it or even recognize it! Uggghhhhh
 
dos2unix said:
what is output of

nmcli dev wifi list

what is the signal strength of the ssid's you want to connect to?

what is output of

iw list
Click to expand...
So I've ran this first line of code a few days ago after someone else on another forum asked me to do it. It comes back with my network at the top, says
mode: Infra
chain: 5
rate: 405Mbit/s
signal: 100
bars: full
security: wpa1 wpa2

Then when I ran iw list right now: this is what it spit out:

Code: 
Wiphy phy0
    wiphy index: 0
    max # scan SSIDs: 20
    max scan IEs length: 356 bytes
    max # sched scan SSIDs: 20
    max # match sets: 8
    Retry short limit: 7
    Retry long limit: 4
    Coverage class: 0 (up to 0m)
    Device supports RSN-IBSS.
    Device supports AP-side u-APSD.
    Device supports T-DLS.
    Supported Ciphers:
        * WEP40 (00-0f-ac:1)
        * WEP104 (00-0f-ac:5)
        * TKIP (00-0f-ac:2)
        * CCMP-128 (00-0f-ac:4)
        * GCMP-128 (00-0f-ac:8)
        * GCMP-256 (00-0f-ac:9)
        * CMAC (00-0f-ac:6)
        * GMAC-128 (00-0f-ac:11)
        * GMAC-256 (00-0f-ac:12)
    Available Antennas: TX 0x3 RX 0x3
    Configured Antennas: TX 0x3 RX 0x3
    Supported interface modes:
         * IBSS
         * managed
         * AP
         * AP/VLAN
         * monitor
         * P2P-client
         * P2P-GO
         * P2P-device
    Band 1:
        Capabilities: 0x19ef
            RX LDPC
            HT20/HT40
            SM Power Save disabled
            RX HT20 SGI
            RX HT40 SGI
            TX STBC
            RX STBC 1-stream
            Max AMSDU length: 7935 bytes
            DSSS/CCK HT40
        Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
        Minimum RX AMPDU time spacing: 4 usec (0x05)
        HT Max RX data rate: 300 Mbps
        HT TX/RX MCS rate indexes supported: 0-15
        HE Iftypes: managed, P2P-client
            HE MAC Capabilities (0x78019a20abc0):
                +HTC HE Supported
                Trigger Frame MAC Padding Duration: 2
                Multi-TID Aggregation Support: 7
                32-bit BA Bitmap
                OM Control
                Maximum A-MPDU Length Exponent: 3
                RX Control Frame to MultiBSS
                A-MSDU in A-MPDU
                Multi-TID Aggregation TX: 7
                UL 2x996-Tone RU
            HE PHY Capabilities: (0x023f0e09fd098c160ff001):
                HE40/2.4GHz
                Punctured Preamble RX: 15
                Device Class: 1
                LDPC Coding in Payload
                NDP with 4x HE-LTF and 3.2us GI
                STBC Tx <= 80MHz
                STBC Rx <= 80MHz
                DCM Max Constellation: 1
                DCM Max Constellation Rx: 1
                SU Beamformee
                Beamformee STS <= 80MHz: 7
                Beamformee STS > 80MHz: 7
                Sounding Dimensions <= 80MHz: 1
                Sounding Dimensions > 80MHz: 1
                Triggered SU Beamforming Feedback
                Triggered MU Beamforming Feedback
                PPE Threshold Present
                Power Boost Factor ar
                HE SU PPDU & HE PPDU 4x HE-LTF 0.8us GI
                Max NC: 2
                HE ER SU PPDU 4x HE-LTF 0.8us GI
                20MHz in 40MHz HE PPDU 2.4GHz
                20MHz in 160/80+80MHz HE PPDU
                80MHz in 160/80+80MHz HE PPDU
                RX Full BW SU Using HE MU PPDU with Compression SIGB
                RX Full BW SU Using HE MU PPDU with Non-Compression SIGB
            HE RX MCS and NSS set <= 80 MHz
                1 streams: MCS 0-11
                2 streams: MCS 0-11
                3 streams: not supported
                4 streams: not supported
                5 streams: not supported
                6 streams: not supported
                7 streams: not supported
                8 streams: not supported
            HE TX MCS and NSS set <= 80 MHz
                1 streams: MCS 0-11
                2 streams: MCS 0-11
                3 streams: not supported
                4 streams: not supported
                5 streams: not supported
                6 streams: not supported
                7 streams: not supported
                8 streams: not supported
            PPE Threshold 0x61 0x1c 0xc7 0x71 
        HE Iftypes: AP, P2P-GO
            HE MAC Capabilities (0x70011a000000):
                +HTC HE Supported
                Multi-TID Aggregation Support: 7
                OM Control
                Maximum A-MPDU Length Exponent: 3
            HE PHY Capabilities: (0x02200e090009800401c000):
                HE40/2.4GHz
                LDPC Coding in Payload
                NDP with 4x HE-LTF and 3.2us GI
                STBC Tx <= 80MHz
                STBC Rx <= 80MHz
                DCM Max Constellation: 1
                DCM Max Constellation Rx: 1
                Sounding Dimensions <= 80MHz: 1
                Sounding Dimensions > 80MHz: 1
                PPE Threshold Present
                HE SU PPDU & HE PPDU 4x HE-LTF 0.8us GI
                HE ER SU PPDU 4x HE-LTF 0.8us GI
            HE RX MCS and NSS set <= 80 MHz
                1 streams: MCS 0-11
                2 streams: MCS 0-11
                3 streams: not supported
                4 streams: not supported
                5 streams: not supported
                6 streams: not supported
                7 streams: not supported
                8 streams: not supported
            HE TX MCS and NSS set <= 80 MHz
                1 streams: MCS 0-11
                2 streams: MCS 0-11
                3 streams: not supported
                4 streams: not supported
                5 streams: not supported
                6 streams: not supported
                7 streams: not supported
                8 streams: not supported
            PPE Threshold 0x61 0x1c 0xc7 0x71 
        Bitrates (non-HT):
            * 1.0 Mbps
            * 2.0 Mbps (short preamble supported)
            * 5.5 Mbps (short preamble supported)
            * 11.0 Mbps (short preamble supported)
            * 6.0 Mbps
            * 9.0 Mbps
            * 12.0 Mbps
            * 18.0 Mbps
            * 24.0 Mbps
            * 36.0 Mbps
            * 48.0 Mbps
            * 54.0 Mbps
        Frequencies:
            * 2412.0 MHz [1] (22.0 dBm)
            * 2417.0 MHz [2] (22.0 dBm)
            * 2422.0 MHz [3] (22.0 dBm)
            * 2427.0 MHz [4] (22.0 dBm)
            * 2432.0 MHz [5] (22.0 dBm)
            * 2437.0 MHz [6] (22.0 dBm)
            * 2442.0 MHz [7] (22.0 dBm)
            * 2447.0 MHz [8] (22.0 dBm)
            * 2452.0 MHz [9] (22.0 dBm)
            * 2457.0 MHz [10] (22.0 dBm)
            * 2462.0 MHz [11] (22.0 dBm)
            * 2467.0 MHz [12] (22.0 dBm)
            * 2472.0 MHz [13] (22.0 dBm)
            * 2484.0 MHz [14] (disabled)
    Band 2:
        Capabilities: 0x19ef
            RX LDPC
            HT20/HT40
            SM Power Save disabled
            RX HT20 SGI
            RX HT40 SGI
            TX STBC
            RX STBC 1-stream
            Max AMSDU length: 7935 bytes
            DSSS/CCK HT40
        Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
        Minimum RX AMPDU time spacing: 4 usec (0x05)
        HT Max RX data rate: 300 Mbps
        HT TX/RX MCS rate indexes supported: 0-15
        VHT Capabilities (0x039071f6):
            Max MPDU length: 11454
            Supported Channel Width: 160 MHz
            RX LDPC
            short GI (80 MHz)
            short GI (160/80+80 MHz)
            TX STBC
            SU Beamformee
            MU Beamformee
        VHT RX MCS set:
            1 streams: MCS 0-9
            2 streams: MCS 0-9
            3 streams: not supported
            4 streams: not supported
            5 streams: not supported
            6 streams: not supported
            7 streams: not supported
            8 streams: not supported
        VHT RX highest supported: 0 Mbps
        VHT TX MCS set:
            1 streams: MCS 0-9
            2 streams: MCS 0-9
            3 streams: not supported
            4 streams: not supported
            5 streams: not supported
            6 streams: not supported
            7 streams: not supported
            8 streams: not supported
        VHT TX highest supported: 0 Mbps
        VHT extended NSS: supported
        HE Iftypes: managed, P2P-client
            HE MAC Capabilities (0x78018a20abc0):
                +HTC HE Supported
                Trigger Frame MAC Padding Duration: 2
                Multi-TID Aggregation Support: 7
                32-bit BA Bitmap
                OM Control
                Maximum A-MPDU Length Exponent: 1
                RX Control Frame to MultiBSS
                A-MSDU in A-MPDU
                Multi-TID Aggregation TX: 7
                UL 2x996-Tone RU
            HE PHY Capabilities: (0x0c3f0e09fd098c160ff001):
                HE40/HE80/5GHz
                HE160/5GHz
                Punctured Preamble RX: 15
                Device Class: 1
                LDPC Coding in Payload
                NDP with 4x HE-LTF and 3.2us GI
                STBC Tx <= 80MHz
                STBC Rx <= 80MHz
                DCM Max Constellation: 1
                DCM Max Constellation Rx: 1
                SU Beamformee
                Beamformee STS <= 80MHz: 7
                Beamformee STS > 80MHz: 7
                Sounding Dimensions <= 80MHz: 1
                Sounding Dimensions > 80MHz: 1
                Triggered SU Beamforming Feedback
                Triggered MU Beamforming Feedback
                PPE Threshold Present
                Power Boost Factor ar
                HE SU PPDU & HE PPDU 4x HE-LTF 0.8us GI
                Max NC: 2
                HE ER SU PPDU 4x HE-LTF 0.8us GI
                20MHz in 40MHz HE PPDU 2.4GHz
                20MHz in 160/80+80MHz HE PPDU
                80MHz in 160/80+80MHz HE PPDU
                RX Full BW SU Using HE MU PPDU with Compression SIGB
                RX Full BW SU Using HE MU PPDU with Non-Compression SIGB
            HE RX MCS and NSS set <= 80 MHz
                1 streams: MCS 0-11
                2 streams: MCS 0-11
                3 streams: not supported
                4 streams: not supported
                5 streams: not supported
                6 streams: not supported
                7 streams: not supported
                8 streams: not supported
            HE TX MCS and NSS set <= 80 MHz
                1 streams: MCS 0-11
                2 streams: MCS 0-11
                3 streams: not supported
                4 streams: not supported
                5 streams: not supported
                6 streams: not supported
                7 streams: not supported
                8 streams: not supported
            HE RX MCS and NSS set 160 MHz
                1 streams: MCS 0-11
                2 streams: MCS 0-11
                3 streams: not supported
                4 streams: not supported
                5 streams: not supported
                6 streams: not supported
                7 streams: not supported
                8 streams: not supported
            HE TX MCS and NSS set 160 MHz
                1 streams: MCS 0-11
                2 streams: MCS 0-11
                3 streams: not supported
                4 streams: not supported
                5 streams: not supported
                6 streams: not supported
                7 streams: not supported
                8 streams: not supported
            PPE Threshold 0x61 0x1c 0xc7 0x71 
        HE Iftypes: AP, P2P-GO
            HE MAC Capabilities (0x70010a000000):
                +HTC HE Supported
                Multi-TID Aggregation Support: 7
                OM Control
                Maximum A-MPDU Length Exponent: 1
            HE PHY Capabilities: (0x0c200e090009800401c000):
                HE40/HE80/5GHz
                HE160/5GHz
                LDPC Coding in Payload
                NDP with 4x HE-LTF and 3.2us GI
                STBC Tx <= 80MHz
                STBC Rx <= 80MHz
                DCM Max Constellation: 1
                DCM Max Constellation Rx: 1
                Sounding Dimensions <= 80MHz: 1
                Sounding Dimensions > 80MHz: 1
                PPE Threshold Present
                HE SU PPDU & HE PPDU 4x HE-LTF 0.8us GI
                HE ER SU PPDU 4x HE-LTF 0.8us GI
            HE RX MCS and NSS set <= 80 MHz
                1 streams: MCS 0-11
                2 streams: MCS 0-11
                3 streams: not supported
                4 streams: not supported
                5 streams: not supported
                6 streams: not supported
                7 streams: not supported
                8 streams: not supported
            HE TX MCS and NSS set <= 80 MHz
                1 streams: MCS 0-11
                2 streams: MCS 0-11
                3 streams: not supported
                4 streams: not supported
                5 streams: not supported
                6 streams: not supported
                7 streams: not supported
                8 streams: not supported
            HE RX MCS and NSS set 160 MHz
                1 streams: MCS 0-11
                2 streams: MCS 0-11
                3 streams: not supported
                4 streams: not supported
                5 streams: not supported
                6 streams: not supported
                7 streams: not supported
                8 streams: not supported
            HE TX MCS and NSS set 160 MHz
                1 streams: MCS 0-11
                2 streams: MCS 0-11
                3 streams: not supported
                4 streams: not supported
                5 streams: not supported
                6 streams: not supported
                7 streams: not supported
                8 streams: not supported
            PPE Threshold 0x61 0x1c 0xc7 0x71 
        Bitrates (non-HT):
            * 6.0 Mbps
            * 9.0 Mbps
            * 12.0 Mbps
            * 18.0 Mbps
            * 24.0 Mbps
            * 36.0 Mbps
            * 48.0 Mbps
            * 54.0 Mbps
        Frequencies:
            * 5180.0 MHz [36] (22.0 dBm)
            * 5200.0 MHz [40] (22.0 dBm)
            * 5220.0 MHz [44] (22.0 dBm)
            * 5240.0 MHz [48] (22.0 dBm)
            * 5260.0 MHz [52] (22.0 dBm) (no IR, radar detection)
            * 5280.0 MHz [56] (22.0 dBm) (no IR, radar detection)
            * 5300.0 MHz [60] (22.0 dBm) (no IR, radar detection)
            * 5320.0 MHz [64] (22.0 dBm) (no IR, radar detection)
            * 5340.0 MHz [68] (disabled)
            * 5360.0 MHz [72] (disabled)
            * 5380.0 MHz [76] (disabled)
            * 5400.0 MHz [80] (disabled)
            * 5420.0 MHz [84] (disabled)
            * 5440.0 MHz [88] (disabled)
            * 5460.0 MHz [92] (disabled)
            * 5480.0 MHz [96] (disabled)
            * 5500.0 MHz [100] (22.0 dBm) (no IR, radar detection)
            * 5520.0 MHz [104] (22.0 dBm) (no IR, radar detection)
            * 5540.0 MHz [108] (22.0 dBm) (no IR, radar detection)
            * 5560.0 MHz [112] (22.0 dBm) (no IR, radar detection)
            * 5580.0 MHz [116] (22.0 dBm) (no IR, radar detection)
            * 5600.0 MHz [120] (22.0 dBm) (no IR, radar detection)
            * 5620.0 MHz [124] (22.0 dBm) (no IR, radar detection)
            * 5640.0 MHz [128] (22.0 dBm) (no IR, radar detection)
            * 5660.0 MHz [132] (22.0 dBm) (no IR, radar detection)
            * 5680.0 MHz [136] (22.0 dBm) (no IR, radar detection)
            * 5700.0 MHz [140] (22.0 dBm) (no IR, radar detection)
            * 5720.0 MHz [144] (22.0 dBm) (no IR, radar detection)
            * 5745.0 MHz [149] (22.0 dBm)
            * 5765.0 MHz [153] (22.0 dBm)
            * 5785.0 MHz [157] (22.0 dBm)
            * 5805.0 MHz [161] (22.0 dBm)
            * 5825.0 MHz [165] (22.0 dBm)
            * 5845.0 MHz [169] (disabled)
            * 5865.0 MHz [173] (disabled)
            * 5885.0 MHz [177] (disabled)
            * 5905.0 MHz [181] (disabled)
    Supported commands:
         * new_interface
         * set_interface
         * new_key
         * start_ap
         * new_station
         * new_mpath
         * set_mesh_config
         * set_bss
         * authenticate
         * associate
         * deauthenticate
         * disassociate
         * join_ibss
         * join_mesh
         * remain_on_channel
         * set_tx_bitrate_mask
         * frame
         * frame_wait_cancel
         * set_wiphy_netns
         * set_channel
         * tdls_mgmt
         * tdls_oper
         * start_sched_scan
         * probe_client
         * set_noack_map
         * register_beacons
         * start_p2p_device
         * set_mcast_rate
         * connect
         * disconnect
         * channel_switch
         * set_qos_map
         * add_tx_ts
         * set_multicast_to_unicast
         * assoc_mlo_reconf
    WoWLAN support:
         * wake up on disconnect
         * wake up on magic packet
         * wake up on pattern match, up to 20 patterns of 16-128 bytes,
           maximum packet offset 0 bytes
         * can do GTK rekeying
         * wake up on GTK rekey failure
         * wake up on EAP identity request
         * wake up on 4-way handshake
         * wake up on rfkill release
         * wake up on network detection, up to 8 match sets
    software interface modes (can always be added):
         * AP/VLAN
         * monitor
    valid interface combinations:
         * #{ managed } <= 1, #{ P2P-client, P2P-GO } <= 1, #{ P2P-device } <= 1,
           total <= 3, #channels <= 2
         * #{ managed } <= 1, #{ AP, P2P-client, P2P-GO } <= 1, #{ P2P-device } <= 1,
           total <= 3, #channels <= 1
    HT Capability overrides:
         * MCS: ff ff ff ff ff ff ff ff ff ff
         * maximum A-MSDU length
         * supported channel width
         * short GI for 40 MHz
         * max A-MPDU length exponent
         * min MPDU start spacing
    Device supports TX status socket option.
    Device supports HT-IBSS.
    Device supports SAE with AUTHENTICATE command
    Device supports low priority scan.
    Device supports scan flush.
    Device supports per-vif TX power setting
    P2P GO supports CT window setting
    P2P GO supports opportunistic powersave setting
    Driver supports full state transitions for AP/GO clients
    Driver supports a userspace MPM
    Driver/device bandwidth changes during BSS lifetime (AP/GO mode)
    Device adds DS IE to probe requests
    Device can update TPC Report IE
    Device supports static SMPS
    Device supports dynamic SMPS
    Device supports WMM-AC admission (TSPECs)
    Device supports configuring vdev MAC-addr on create.
    Device supports randomizing MAC-addr in scans.
    Device supports randomizing MAC-addr in sched scans.
    Device supports randomizing MAC-addr in net-detect scans.
    max # scan plans: 2
    max scan plan interval: 65535
    max scan plan iterations: 254
    Supported TX frame types:
         * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
         * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
         * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
         * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
         * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
         * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
         * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
         * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
         * NAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
    Supported RX frame types:
         * IBSS: 0x40 0xb0 0xc0 0xd0
         * managed: 0x40 0xb0 0xd0
         * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
         * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
         * mesh point: 0xb0 0xc0 0xd0
         * P2P-client: 0x40 0xd0
         * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
         * P2P-device: 0x40 0xb0 0xd0
         * NAN: 0xb0 0xd0
    Supported extended features:
        * [ VHT_IBSS ]: VHT-IBSS
        * [ RRM ]: RRM
        * [ MU_MIMO_AIR_SNIFFER ]: MU-MIMO sniffer
        * [ SCAN_START_TIME ]: scan start timestamp
        * [ BSS_PARENT_TSF ]: BSS last beacon/probe TSF
        * [ BEACON_RATE_LEGACY ]: legacy beacon rate setting
        * [ FILS_STA ]: STA FILS (Fast Initial Link Setup)
        * [ FILS_MAX_CHANNEL_TIME ]: FILS max channel attribute override with dwell time
        * [ ACCEPT_BCAST_PROBE_RESP ]: accepts broadcast probe response
        * [ OCE_PROBE_REQ_HIGH_TX_RATE ]: probe request TX at high rate (at least 5.5Mbps)
        * [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
        * [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
        * [ SCAN_MIN_PREQ_CONTENT ]: use probe request with only rate IEs in scans
        * [ ENABLE_FTM_RESPONDER ]: enable FTM (Fine Time Measurement) responder
        * [ CONTROL_PORT_NO_PREAUTH ]: disable pre-auth over nl80211 control port support
        * [ PROTECTED_TWT ]: protected Target Wake Time (TWT) support
        * [ DEL_IBSS_STA ]: deletion of IBSS station support
        * [ SCAN_FREQ_KHZ ]: scan on kHz frequency support
        * [ CONTROL_PORT_OVER_NL80211_TX_STATUS ]: tx status for nl80211 control port support
        * [ PROT_RANGE_NEGO_AND_MEASURE ]: support for MFP in range measurement negotiation/procedure
        * [ POWERED_ADDR_CHANGE ]: can change MAC address while up
        * [ SPP_AMSDU_SUPPORT ]: SPP A-MSDU support
    Peer measurement (PMSR)
        Max peers: 5
        REPORT_AP_TSF
        RANDOMIZE_MAC_ADDR
        FTM (Fine time measurement or Flight time measurement)
            Preambles: LEGACY HT VHT
            Bandwidth: 20_NOHT 20 40 80 160
            ASAP
            NON_ASAP
            REQ_LCI
            REQ_CIVICLOC
            TRIGGER_BASED
            NON_TRIGGER_BASED
 
APTI said:
go spend $20 on a usb wifi card that is fully linux compatible. lots of them out there. Or replace the one in your computer with a working one. It is not that difficult to replace them.
Click to expand...
Haha, I had NO IDEA that was even a "thing". I looked this up and was blown away, haha. A small usb stick or tiny antenna that amplifies my wifi for my computer. I may just have to go to Microcenter and pick one of those up and be done with all this hassle! I still want to figure this out and get my Linux running off of my WiFi, just so I can say I won. But, I'm more than likely also going to pick one of these up. Thank you for suggesting this!
 
From what I can see, your wifi looks fine, no drivers. maybe a connection issue.
 
So since I couldn't figure this out and nobody else could either. I gave up on Fedora. I went back to the ol stand by... Mint Cinnamon. It still wouldn't work. Bought a USB WiFi adapter, it barely worked and gave me the slowest internet. So I looked into my router and even though it's not that old and downstairs has good speed, I decided to research a new router and see if that would fix the problem. One that has faster speeds and better/farther coverage and it works like a charm. I was maybe getting 13-25gbps on the old router, the new one gets 380-450 consistently. It's a TP-L:ink BE3600. So even though I don't have any WiFi 7 products yet, I'll be ready for them when they come out. My PC's mobo has WiFI 6. Anyways, no idea for sure what the problem was, but guessing it could have been the router just doesn't have the coverage distance? But no idea why it would work for the Windows on my PC, Mac and iPhone in the exact same room and area of the house, but not Linux?!
 
You must log in or register to reply here.

Similar threads

ImaginaryTango
Setting Up Multiple Wifi Connections with nmcli
Replies
7
Views
1K
dos2unix
dos2unix
Mauvve Knight
Solved Linux not able to connect to wifi network
Replies
9
Views
2K
Mauvve Knight
Mauvve Knight
A
5GHz Wi-Fi stopped working after recent updates on Fedora (Intel 7260)
Replies
2
Views
684
aliakber200x
A
H
wifi ok; ethernet ok but firefox says "Unable to connect"
Replies
4
Views
1K
Condobloke
Condobloke
G
Solved I can't connect my quest 3 to my pc via cable/wire
Replies
2
Views
605
deb_user
D


Follow Linux.org

Members online

Total: 4,871 (members: 3, guests: 4,868)

Latest posts

Top