No, I now test my ralink wifi adapter and it is working after replug.
I thought that rtl driver makes my ralink adaptor working but after all I know just my wifi adapter find the networks a little bit later when I replug it and because that I thought it is not working because not showing my networks.
but as I say I test it again and wait some seconds and it shows wifi.
however my main problem( wifi adapter not working normally after reboot) is not fixed yet.
mahdi2421@mahdi2421 in ~ as 🧙 took 24s
λ bash -c "nmcli networking off; sudo systemctl stop NetworkManager; sudo ip link set wlp1s0f0u1 down; sleep 1; sudo modprobe -r rt2800usb; sleep 3; sudo modprobe rt2800usb; sleep 1; sudo ip link set wlp1s0f0u1 up; sleep 1; sudo systemctl start NetworkManager; nmcli networking on; sleep 1; nmcli r wifi off; sleep 1; nmcli r wifi on"
Cannot find device "wlp1s0f0u1"
Cannot find device "wlp1s0f0u1"
mahdi2421@mahdi2421 in ~ as 🧙 took 20s
λ bash -c "nmcli networking off; sudo systemctl stop NetworkManager; sudo ip link set wlp1s0f0u1 down; sleep 1; sudo rmmod asus_wmi; sleep 1; sudo modprobe -r rt2800usb; sleep 3; sudo modprobe rt2800usb; sleep 1; sudo ip link set wlp1s0f0u1 up; sleep 1; sudo systemctl start NetworkManager; sleep 1; nmcli networking on; sleep1; nmcli r wifi off; sleep 1; nmcli r wifi on"
Cannot find device "wlp1s0f0u1"
rmmod: ERROR: Module asus_wmi is in use by: eeepc_wmi
Cannot find device "wlp1s0f0u1"
then I ran ip a s command on terminal and it shows this
mahdi2421@mahdi2421 in ~ as 🧙 took 22s
λ ip a s
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether 0c:9d:92:12:15:15 brd ff:ff:ff:ff:ff:ff
7: wlp1s0f0u13: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether f4:3e:61:65:79:3b brd ff:ff:ff:ff:ff:ff
As you see my device name is wlp1s0f0u13 and I ran edit command for it and ran .
mahdi2421@mahdi2421 in ~ as 🧙 took 19s
λ bash -c "nmcli networking off; sudo systemctl stop NetworkManager; sudo ip link set wlp1s0f0u13 down; sleep1; sudo modprobe -r rt2800usb; sleep 3; sudo modprobe rt2800usb; sleep 1; sudo ip link set wlp1s0f0u13 up; sleep 1; sudo systemctl start NetworkManager; nmcli networking on; sleep 1; nmcli r wifi off; sleep 1; nmcli r wifi on"
mahdi2421@mahdi2421 in ~ as 🧙 took 20s
λ bash -c "nmcli networking off; sudo systemctl stop NetworkManager; sudo ip link set wlp1s0f0u13 down; sleep1; sudo rmmod asus_wmi; sleep 1; sudo modprobe -r rt2800usb; sleep 3; sudo modprobe rt2800usb; sleep 1; sudoip link set wlp1s0f0u13 up; sleep 1; sudo systemctl start NetworkManager; sleep 1; nmcli networking on; sleep 1; nmcli r wifi off; sleep 1; nmcli r wifi on"
rmmod: ERROR: Module asus_wmi is in use by: eeepc_wmi
excuse me, what do you mean from cold boot and warm reboot?
No I dont use hub and I pluged my wifi dongle direct to usb port.
About the wifi driver , how can I use ndiswrapper ?
I Install it but how can I use windows driver for linux or how can I work with it to install driver for my wifi dongle.
I think my wifi dongle problem is from kernel or driver problem that doesnt work correctly.
Don’t. Don’t do it. Don’t break my h-e-a-r-t.
(The Band, man)
It’s been too long; Linux has grown too much. Please please beg, borrow or steal something that does not require that hacky shit. We gave that up a long time ago, really.
Yes, you are correct, this isn’t really a Garuda specific issue. It is likely kernel/driver related, but considering the age of this adapter I doubt this will ever be addressed at this point.
I’m not sure why you would find this hard to understand.
Cold boot.
Once the computer is running initiate a warm boot (reboot).
Once the computer has restarted remove the wifi dongle from the USB port.
Reinsert the wifi dongle into the USB port.
This is simply a test to see if after that sequence you can then run the wifi after a reboot by simply removing/reinserting your adapter. While nowhere near a fix, once you had finished the initial cold boot/reboot, you could then restart anytime and use your wifi by simply reinserting it.
Or as @Bro mentioned, and I myself stated on your other threads, buy another adapter.
Yes ,After I ask you , then I decide to google what is cold boot and warm boot exactly and I do this :
first I shutdown my pc from garuda linux and then turn on pc with the case button .
And wifi is working in this mode as I know( as i said I didnt have problem when I cold boot).
then I restart my pc and go to garuda linux and then again I see my wifi working and it connect to it?!
because I have problem in warm boot and always it is not working as I tested.
just maybe two thing fix the problem.
1- first is the ipv6 disabling
2- and second maybe from mac address random disable
update : I just warm boot now ( for sure about that my wifi adapter problem fix in warm boot ) , and unfortunately it isnt working .
just it works after warm boot in this case I think : you do cold boot then warm boot for 2 or 3 mins after you are in desktop and it is working.
because as I say, now I warm boot after first warm boot and it is not working and I need replug.
after all thanks from your and other member and admins help.
I decide to use my other wifi dongle as it is seem to work good on linux.
excuse me if I ask much question or dont attention to someting.
Don’t. Don’t do it. Don’t break my h-e-a-r-t. 