I have Garuda Linux(KDE env) which I want to connect to the internet with USB wifi, the first problem is it doesn't connect to hidden wifi, and second is when it connects to unhidden wifi sometimes take a few minutes to connect it, and sometimes it's not connecting at all, I don't know why that happens, when I had windows 10 these problems weren't there but in Linux I have.
as text! Even if you personally think it is unnecessary.
Use forum search function first, maybe you
is listed in solutions.
It's not helpful. For help, we need more details about your hard- and software.
System: Kernel: 5.11.16-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 10.2.0 parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=dcff8c34-fec2-463c-9581-ea0f69c95476 rw [email protected] quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0 systemd.unified_cgroup_hierarchy=1 resume=UUID=0606a149-9f5b-47bc-b116-22c67112ba69 loglevel=3 Desktop: KDE Plasma 5.21.4 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 vt: 2 dm: SDDM Distro: Garuda Linux base: Arch Linux Machine: Type: Desktop System: ASUS product: N/A v: N/A serial: <filter> Mobo: ASUSTeK model: PRO H410M-C v: Rev 1.xx serial: <filter> UEFI: American Megatrends v: 0602 date: 04/15/2020 CPU: Info: 8-Core model: Intel Core i7-10700 bits: 64 type: MT MCP arch: Comet Lake family: 6 model-id: A5 (165) stepping: 5 microcode: E0 cache: L2: 16 MiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 92796 Speed: 4702 MHz min/max: 800/4800 MHz Core speeds (MHz): 1: 4702 2: 4699 3: 4701 4: 4697 5: 4696 6: 4698 7: 4693 8: 4699 9: 4698 10: 4711 11: 4708 12: 4694 13: 4699 14: 4705 15: 4711 16: 4698 Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported Type: l1tf status: Not affected Type: mds status: Not affected Type: meltdown status: Not affected Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB filling Type: srbds status: Not affected Type: tsx_async_abort status: Not affected Graphics: Device-1: Intel vendor: ASUSTeK driver: i915 v: kernel bus-ID: 00:02.0 chip-ID: 8086:9bc5 class-ID: 0300 Device-2: NVIDIA GP108 [GeForce GT 1030] vendor: ASUSTeK driver: nvidia v: 465.27 alternate: nouveau,nvidia_drm bus-ID: 01:00.0 chip-ID: 10de:1d01 class-ID: 0300 Display: x11 server: X.Org 1.20.11 compositor: kwin_x11 driver: loaded: intel,nvidia unloaded: modesetting,nouveau alternate: fbdev,nv,vesa display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") s-diag: 582mm (22.9") Monitor-1: DP1 res: 1920x1080 hz: 60 dpi: 92 size: 530x300mm (20.9x11.8") diag: 609mm (24") OpenGL: renderer: Mesa Intel UHD Graphics 630 (CML GT2) v: 4.6 Mesa 21.0.3 direct render: Yes Audio: Device-1: Intel vendor: ASUSTeK driver: snd_hda_intel v: kernel alternate: snd_sof_pci bus-ID: 00:1f.3 chip-ID: 8086:a3f0 class-ID: 0403 Sound Server-1: ALSA v: k5.11.16-zen1-1-zen running: yes Sound Server-2: JACK v: 0.125.0 running: no Sound Server-3: PulseAudio v: 14.2 running: yes Sound Server-4: PipeWire v: 0.3.26 running: yes Network: Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel port: efa0 bus-ID: 00:1f.6 chip-ID: 8086:0d55 class-ID: 0200 IF: eno1 state: down mac: <filter> Device-2: D-Link DWA-123 Wireless N 150 Adapter (rev.D1) type: USB driver: r8188eu bus-ID: 1-4:5 chip-ID: 2001:3310 class-ID: 0000 serial: <filter> IF: wlp0s20f0u4 state: up mac: <filter> IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A Drives: Local Storage: total: 1.14 TiB used: 439.71 GiB (37.8%) SMART Message: Unable to run smartctl. Root privileges required. ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO Plus 250GB size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 rotation: SSD serial: <filter> rev: 2B2QEXM7 temp: 39.9 C scheme: GPT ID-2: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD10EZEX-00WN4A0 size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> rev: 1A01 scheme: GPT Partition: ID-1: / raw-size: 78.13 GiB size: 78.13 GiB (100.00%) used: 9.37 GiB (12.0%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5 ID-2: /boot/efi raw-size: 1.95 GiB size: 1.95 GiB (99.80%) used: 572 KiB (0.0%) fs: vfat dev: /dev/nvme0n1p8 maj-min: 259:8 ID-3: /home raw-size: 9.77 GiB size: 9.77 GiB (100.00%) used: 1.56 GiB (16.0%) fs: btrfs dev: /dev/nvme0n1p7 maj-min: 259:7 ID-4: /var/log raw-size: 78.13 GiB size: 78.13 GiB (100.00%) used: 9.37 GiB (12.0%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5 ID-5: /var/tmp raw-size: 78.13 GiB size: 78.13 GiB (100.00%) used: 9.37 GiB (12.0%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5 Swap: Kernel: swappiness: 10 (default 60) cache-pressure: 75 (default 100) ID-1: swap-1 type: partition size: 7.81 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/nvme0n1p6 maj-min: 259:6 ID-2: swap-2 type: zram size: 990.1 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram0 ID-3: swap-3 type: zram size: 990.1 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram1 ID-4: swap-4 type: zram size: 990.1 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram2 ID-5: swap-5 type: zram size: 990.1 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram3 ID-6: swap-6 type: zram size: 990.1 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram4 ID-7: swap-7 type: zram size: 990.1 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram5 ID-8: swap-8 type: zram size: 990.1 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram6 ID-9: swap-9 type: zram size: 990.1 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram7 ID-10: swap-10 type: zram size: 990.1 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram8 ID-11: swap-11 type: zram size: 990.1 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram9 ID-12: swap-12 type: zram size: 990.1 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram10 ID-13: swap-13 type: zram size: 990.1 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram11 ID-14: swap-14 type: zram size: 990.1 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram12 ID-15: swap-15 type: zram size: 990.1 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram13 ID-16: swap-16 type: zram size: 990.1 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram14 ID-17: swap-17 type: zram size: 990.1 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram15 Sensors: System Temperatures: cpu: 27.8 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 394 Uptime: 31m wakeups: 0 Memory: 15.47 GiB used: 3.92 GiB (25.4%) Init: systemd v: 248 tool: systemctl Compilers: gcc: 10.2.0 clang: 11.1.0 Packages: pacman: 1300 lib: 340 Shell: Bash v: 5.1.4 running-in: konsole inxi: 3.3.04
You didn't read "Reporting bugs"
If you include terminal outputs in your post please use the proper output format in your post. Using "~" 3 times above and "~" 3 times below the text block will provide a readable, raw look.
D-Link DWA-123 Wireless N
sorry, and thanks for editing
There are three drivers available for this adapter:
8188eu-aircrack-dkms-git 8188eu-dkms-git 8188eu-dkms
Have you tested any of these drivers yet?
If so, which one(s) ?
If not, that would be the place to start.
Many Realtek adapters require installing the drivers separately as the in kernel drivers aren't well developed yet.
Be sure to reboot after any driver installation.
lsmod | sort before you install an alternate driver, and then post it again after installing any driver package (reboot first) .
I made several suggestions and requested you post further outputs when you opened your help request. It appears you have not been online since opening your request some days ago.
When suggestions are given and outputs are requested it is incumbent upon the OP to provide this information in a timely manner or your thread will be deemed abandoned.
I like to keep the networking section clear of abandoned posts that are left dangling. Otherwise, we simply get a bunch of new users tacking on "me too" to old stale posts that likely aren't even a related issue.
As such I am putting a one week countdown lock on your thread for you to respond and provide the requested outputs. A week and a half should be more than sufficient time to reply to any request for outputs for most anyone requesting assistance.
If your thread has been locked and you wish it reopened then please PM another moderator to reopen this thread. I am no longer accepting PM's from users as some users have abused this system and I no longer accept PM's from members.
If your issue has already been resolved, please revisit your thread and provide an update so that other users know how to fix a related problem in the future. Please do not open help requests only to abandon them and not provide some form of closure to your thread. Even if you simply gave up on your issue you should do the courteous thing by replying to your own help request and let others know that you no longer require assistance.
It's just the courteous thing to do, and helps keep our forum neat, tidy, and organized for users to find solutions easier.
This topic was automatically closed after 6 days. New replies are no longer allowed.