You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 2017-08-26 17:04:41
- consumptivas
- Member
- Registered: 2017-07-07
- Posts: 11
dwa-131 wifi key not working
Hello,
I try to get my D-Link wifi dongle working on my KDE desktop without success.
I installed "8192eu-dkms" from AUR.
When I plug the dongle, The NetworkManager detect all Wifi signals. But When I try to connect to any SSID, NetworkManager try to connect (I see the loader running...) and finally nothing hapen and no error message display
Here is journalctl outpout :
journalctl -f _TRANSPORT=kernel
-- Logs begin at Mon 2016-05-02 16:46:03 CEST. --
août 26 18:20:07 localhost.localdomain kernel: wlp0s26u1u4: send auth to e4:9e:12:0e:65:29 (try 1/3)
août 26 18:20:07 localhost.localdomain kernel: wlp0s26u1u4: send auth to e4:9e:12:0e:65:29 (try 2/3)
août 26 18:20:07 localhost.localdomain kernel: wlp0s26u1u4: send auth to e4:9e:12:0e:65:29 (try 3/3)
août 26 18:20:07 localhost.localdomain kernel: wlp0s26u1u4: authentication with e4:9e:12:0e:65:29 timed out
août 26 18:20:13 localhost.localdomain kernel: IPv6: ADDRCONF(NETDEV_UP): wlp0s26u1u4: link is not ready
août 26 18:20:13 localhost.localdomain kernel: IPv6: ADDRCONF(NETDEV_UP): wlp0s26u1u4: link is not ready
août 26 18:25:55 localhost.localdomain kernel: IPv6: ADDRCONF(NETDEV_UP): wlp0s26u1u4: link is not ready
août 26 18:31:11 localhost.localdomain kernel: IPv6: ADDRCONF(NETDEV_UP): wlp0s26u1u4: link is not ready
août 26 18:36:26 localhost.localdomain kernel: IPv6: ADDRCONF(NETDEV_UP): wlp0s26u1u4: link is not ready
août 26 18:41:42 localhost.localdomain kernel: IPv6: ADDRCONF(NETDEV_UP): wlp0s26u1u4: link is not ready
août 26 18:43:48 localhost.localdomain kernel: IPv6: ADDRCONF(NETDEV_UP): wlp0s26u1u4: link is not readyNetworkManager version
1.8.3dev+18+gf43222d41-1 (stable)wpa_supplicant version 1:2.6-8 (stable)
KDE Plasma version : 5.10.5
KDE Frameworks version : 5.37.0
QT version : 5.9.1uname -a
Linux localhost.localdomain 4.12.8-2-ARCH #1 SMP PREEMPT Fri Aug 18 14:08:02 UTC 2017 x86_64 GNU/Linuxlsusb | grep 2001:3319
Bus 001 Device 014: ID 2001:3319 D-Link Corp.I think it is Rev E1
lsmod
Module Size Used by
ppp_mppe 20480 2
ppp_async 20480 1
ppp_generic 32768 6 ppp_async,ppp_mppe
slhc 20480 1 ppp_generic
nf_conntrack_pptp 16384 0
nf_conntrack_proto_gre 16384 1 nf_conntrack_pptp
nf_conntrack 110592 2 nf_conntrack_pptp,nf_conntrack_proto_gre
libcrc32c 16384 1 nf_conntrack
crc32c_generic 16384 0
fuse 98304 3
8192eu 1077248 0
arc4 16384 6
rtl8xxxu 118784 0
mac80211 688128 1 rtl8xxxu
cfg80211 520192 2 mac80211,8192eu
rfkill 20480 5 cfg80211
input_leds 16384 0
led_class 16384 1 input_leds
joydev 20480 0
mousedev 20480 0
amdkfd 118784 1
amd_iommu_v2 20480 1 amdkfd
radeon 1462272 45
ttm 81920 1 radeon
ppdev 20480 0
evdev 24576 13
iTCO_wdt 16384 0
iTCO_vendor_support 16384 1 iTCO_wdt
mac_hid 16384 0
mei_wdt 16384 0
snd_hda_codec_realtek 73728 1
drm_kms_helper 131072 1 radeon
intel_powerclamp 16384 0
snd_hda_codec_generic 69632 1 snd_hda_codec_realtek
coretemp 16384 0
snd_hda_codec_hdmi 49152 1
kvm_intel 192512 0
snd_hda_intel 36864 6
snd_hda_codec 106496 4 snd_hda_intel,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek
kvm 520192 1 kvm_intel
drm 299008 22 radeon,ttm,drm_kms_helper
snd_hda_core 65536 5 snd_hda_intel,snd_hda_codec,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek
irqbypass 16384 1 kvm
crc32c_intel 24576 1
snd_hwdep 16384 1 snd_hda_codec
intel_cstate 16384 0
snd_pcm 86016 5 snd_hda_intel,snd_hda_codec,snd_hda_core,snd_hda_codec_hdmi
syscopyarea 16384 1 drm_kms_helper
sysfillrect 16384 1 drm_kms_helper
sysimgblt 16384 1 drm_kms_helper
psmouse 131072 0
snd_timer 28672 1 snd_pcm
fb_sys_fops 16384 1 drm_kms_helper
pcspkr 16384 0
snd 69632 19 snd_hda_intel,snd_hwdep,snd_hda_codec,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek,snd_pcm
r8169 77824 0
i2c_i801 24576 0
i7core_edac 24576 0
i2c_algo_bit 16384 1 radeon
lpc_ich 24576 0
soundcore 16384 1 snd
mii 16384 1 r8169
parport_pc 28672 0
asus_atk0110 20480 0
parport 40960 2 parport_pc,ppdev
tpm_infineon 20480 0
button 16384 0
mei_me 36864 1
mei 77824 3 mei_me,mei_wdt
acpi_cpufreq 20480 1
tpm_tis 16384 0
tpm_tis_core 20480 1 tpm_tis
tpm 49152 3 tpm_infineon,tpm_tis,tpm_tis_core
shpchp 32768 0
sch_fq_codel 20480 7
vboxnetflt 28672 0
vboxnetadp 28672 0
pci_stub 16384 1
vboxpci 24576 0
vboxdrv 385024 3 vboxnetadp,vboxnetflt,vboxpci
sg 36864 0
ip_tables 24576 0
x_tables 28672 1 ip_tables
ext4 540672 3
crc16 16384 1 ext4
jbd2 90112 1 ext4
fscrypto 24576 1 ext4
mbcache 16384 1 ext4
sr_mod 24576 0
cdrom 53248 1 sr_mod
sd_mod 49152 5
hid_generic 16384 0
uas 24576 0
usbhid 45056 0
usb_storage 65536 1 uas
hid 114688 2 hid_generic,usbhid
serio_raw 16384 0
atkbd 24576 0
libps2 16384 2 atkbd,psmouse
ahci 36864 4
libahci 28672 1 ahci
libata 208896 2 ahci,libahci
ehci_pci 16384 0
ehci_hcd 73728 1 ehci_pci
scsi_mod 155648 6 sd_mod,usb_storage,libata,uas,sr_mod,sg
usbcore 208896 7 usbhid,usb_storage,ehci_hcd,8192eu,uas,rtl8xxxu,ehci_pci
usb_common 16384 1 usbcore
i8042 24576 0
serio 20480 6 serio_raw,atkbd,psmouse,i8042Maybe linux-firmwares conflict with 8192eu ?
Maybe wpa_supplicant wrong version
I really do not understand the problem
Any help much appreciated.
Thanks in advance.
Offline
#2 2017-08-26 17:07:20
- Slithery
- Administrator
- From: Norfolk, UK
- Registered: 2013-12-01
- Posts: 5,776
Re: dwa-131 wifi key not working
May not be relevant to this issue but you really need to set your hostname, not having one can cause all sorts of random problems.
Offline
#3 2017-08-27 08:09:06
- consumptivas
- Member
- Registered: 2017-07-07
- Posts: 11
Re: dwa-131 wifi key not working
Yes, I changet it.
Last edited by consumptivas (2017-08-27 08:09:43)
Offline
#4 2017-08-27 08:59:03
- Gusar
- Member
- Registered: 2009-08-25
- Posts: 3,607
Re: dwa-131 wifi key not working
Your lsmod output shows you have both rtl8xxxu and 8192eu drivers loaded. That for sure causes a conflict. Uninstall 8192eu-dkms and reboot. When you plug in the device, make sure only rtl8xxxu is loaded. Try to connect. If it doesn't work, install 8192eu-dkms again and blacklist the rtl8xxxu driver so you won't have a conflict again. The rtl8xxxu driver is tested to work with your device though, so 8192eu-dkms shouldn't be needed.
Offline
Pages: 1