Wifi not working on Linux, works on Windows

Support Network
, ,
21

I am fairly certain the device is working - providing the link is ok for documentation purpose

  • let us have It :slight_smile:
22

R you talking about KDE Connect? I saw the icon you mentioned after clicking on this 4 option came out. 1. Majnaro setting 2. Disk and Device 3. Display Config 4. KDE Connect.

23
24

The device works OOB on Manjaro Ralink RT3290 Wireless 802.11n 1T/1R PCIe

The wireless device is detected and driver loaded by kernel.

You are using Plasma and it looks like a fully synced system.

Please do no use text-speech or self-invented abbreviations - use properly formatted language.

Plasma uses Network Manager - so that is what I am referring to - NOT KDE-connect which is something entirely different.

You can open a terminal and use the console to setup the connection

nmtui
25

Screenshot_20240604_154854

26 
NetworkManager TUI ├──┐
                     │                         │ 
                     │ Please select an option │ 
                     │                         │ 
                     │ Edit a connection       │ 
                     │ Activate a connection   │ 
                     │ Set system hostname     │ 
                     │ Radio                   │ 
                     │                         │ 
                     │ Quit                    │ 
                     │                         │ 
                     │                    <OK> │

If I go for Activate a connection then I can only get a wired connection which is my LAN. I didn’t find anything else there.

27

And the Radio part?

28 
 NetworkManager TUI ├──┐
             ┌────┤ Set the radio switches status ├────┐
             │                                         │ 
             │ Wi-Fi                                   │ 
             │ Hardware: Enabled   Software: <Enabled> │ 
             │                                         │ 
             │ WWAN                                    │ 
             │ Hardware: Missing   Software: <Enabled> │ 
             │                                         │ 
             │                                  <Back>
29

It is obvious the device is identified, the necessary driver loaded and the device is not blocked by hardware or software.

Check the status of your device

ip link | grep wlo1

You should have a state of UP - if you do not have that state

sudo ip link set wlo1 up

Then run

nmcli

Select Activate connection → pick you access point → Select Activate → provide credentials → Select OK

If you cannot make it work - you will have to get someone in your local neighborhood to help you.

The following is only speculation - you will need to do some research

  • is any access point(s) found
  • radio frequencies overload
  • card capabilities unsupported by access point
  • environment interference
  • as bluetooth - wifi operates on same card - possible interference
1 Like
30 
**ip link | grep wlo1**                                 
3: wlo1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue 
state DOWN mode DORMANT group default qlen 1000
 **sudo ip link set wlo1 up**                          

 **ip link | grep wlo1**                        
3: wlo1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue 
state DOWN mode DORMANT group default qlen 1000
 **nmcli**                                              
enp1s0f0: connected to Wired connection 1
        "Realtek RTL8111/8168/8211/8411"
        ethernet (r8169), 58:20:B1:71:17:42, hw, mtu 1500
        ip4 default
        inet4 192.168.0.105/24
        route4 192.168.0.0/24 metric 100
        route4 default via 192.168.0.1 metric 100
        inet6 fe80::a43b:69f6:51d6:16c7/64
        route6 fe80::/64 metric 1024

lo: connected (externally) to lo
        "lo"
        loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
        inet4 127.0.0.1/8
        inet6 ::1/128

wlo1: disconnected
        "Ralink RT3290 1T/1R"
        wifi (rt2800pci), 4E:26:64:B5:84:DC, hw, mtu 1500

DNS configuration:
        servers: 192.168.0.1
        interface: enp1s0f0

Use "nmcli device show" to get complete information about known dev>
"nmcli connection show" to get an overview on active connection pro>

lines 1-27
31

A dormant device is in a low power state.

I suggest you revisit your power settings.

The device may internally be connected to USB bus and thus powersafe features which is powering down USB devices may cause the device to be in low power state.

Check if your system has an active tlp.service

systemctl status tlp.service

@main

You could change the mode to default - see if it brings any difference

sudo ip link set wlo1 mode default

Then

sudo ip link set wlo1 up
32 
systemctl status tlp.service            
Unit tlp.service could not be found.
33

I recall a topic on a Dell laptop which would not allow for both interfaces to be active at the same time - kind of prioritized ethernet over wifi when connected using ethernet.

At the time it seemed firmware setting would automagically activate the wifi when the lan was disconnected.

You could try disconnecting your ethernet to deduce whether that would allow the wifi wake up.

34

BIOS
BIOS1152×864 37.5 KB

I got a solution for this problem. I just update my network from BIOS and now it’s working fine for both OS. Thank you guys I loved this community <3

35

please mark your topic as solved

36

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.