Sto cercando di configurare il WiFi con il nuovo modem Fastweb , vede la connessione ma mi restituisce l’errore in argomento. Ho una scheda D-link wireless N nano wireless usb adapter rilevata dal comando lsusb (sto scrivendo dal tablet ) e con ifconfigè wlp4s0u2 attiva ma senza indirizzo IP, ho provato ad assegnare anche un IP statico ma non funziona comunque. Qualche suggerimento?
Quella chiavetta supporta solo i 2.4 GHz, a vedere la scheda tecnica. (È questa? https://eu.dlink.com/it/it/products/dwa-131-wireless-n-nano-usb-adapter).
Non è che il router è impostato solo per i 5 GHz?
Ho provato sia con entrambe le bande attive 5GHz e 2.4GHz che solo con 2.4GHz, il problema è che non riesco a pingarla
Ah. Ma riesci a connetterti? Ti viene chiesta la password del wifi? E il problema è a livello di IP?
Il comando iwconfig cosa dice?
`iwconfig`
lo no wireless extensions.
enp0s31f6 no wireless extensions.
wlp4s0u2 IEEE 802.11 ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
Retry short limit:7 RTS thr=2347 B Fragment thr:off
Encryption key:off
Power Management:off
virbr1 no wireless extensions.
virbr1-nic no wireless extensions.
Con l’interfaccia di NetworkManager provo a dare “connetti” ma mi risponde
“La rete senza fili non può essere trovata”
Quindi non è a livello IP (non riesci a pingarla). Anche assegnare un IP statico è inutile, se nemmeno riesci a connetterti.
Esatto, ma è normale che mi rilevi l’accesspoint ma non riesco ad attivare la scheda wifi?
Se provi da linea di comando? (Darà lo stesso messaggio, ma è giusto per vedere cosa dice).
nmcli device wifi connect NOMEDELWIFI password password_del_wifi
nmcli device wifi connect FASTWEB-D4DCE7 password N3GFRYJN8K
Errore: attivazione connessione non riuscita: (53) Impossibile trovare la rete Wi-Fi
Vabbe’ la password potevi anche non scriverla 
A parte questo.
Bisogna vedere i log.
Apri un secondo terminale e lancia tipo
journalctl -xf -u NetworkManager
Poi riprova il comando nmcli e guarda se nei log vedi qualche riga che faccia intuire come mai non funziona.
Vediamo cosa succede all’inserimento del device usb.
Procedi così:
-
fai partire il sistema senza il modulo usb
-
apri un terminale come root e dai questo comando:
-
# tail -f /var/log/messages
(che rimane in attesa di eventi)
- inserisci il modulo usb
A questo punto nel terminale dovresti vedere una serie di righe come output.
Postale qui.
Ciao.
Sergio
@idraulico, scusa, tre cose:
-
/var/log/messagesnon esiste più, oggi i log di sistema si guardano conjournalctl - root di default è disabilitato, meglio consigliare di eseguire i comandi che richiedono privilegi usando
sudo - nel caso specifico di @trex, il problema non è che il sistema non vede la chiavetta, ma che con il nuovo router non riesce a collegarsi alla rete
@alciregi:
journalctl -xf -u NetworkManager
‘mag 24 14:28:12 localhost.localdomain NetworkManager[882]: [1590323292.5931] manager: kernel firmware directory ‘/lib/firmware’ changed
mag 24 14:28:36 localhost.localdomain NetworkManager[882]: [1590323316.5341] device (wlp4s0u2): set-hw-addr: set MAC address to 7E:08:B8:B4:B1:ED (scanning)
mag 24 14:28:36 localhost.localdomain NetworkManager[882]: [1590323316.9015] device (wlp4s0u2): supplicant interface state: inactive -> disabled’
Vabbè la password la cambio, 
Tutto qua?
Ma una domanda: il problema è nato cambiando router?
@idraulico
‘tail -f /var/log/messagessto’
May 24 14:52:51 localhost kernel: usb 3-2: new high-speed USB device number 2 using xhci_hcd
May 24 14:52:51 localhost kernel: usb 3-2: New USB device found, idVendor=2001, idProduct=3319, bcdDevice= 2.00
May 24 14:52:51 localhost kernel: usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
May 24 14:52:51 localhost kernel: usb 3-2: Product: Wireless N Nano USB Adapter
May 24 14:52:51 localhost kernel: usb 3-2: Manufacturer: Realtek
May 24 14:52:51 localhost kernel: usb 3-2: SerialNumber: 00e04c000001
May 24 14:52:51 localhost mtp-probe[3160]: checking bus 3, device 2: “/sys/devices/pci0000:00/0000:00:1c.4/0000:04:00.0/usb3/3-2”
May 24 14:52:51 localhost mtp-probe[3160]: bus: 3, device: 2 was not an MTP device
May 24 14:52:52 localhost kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database
May 24 14:52:52 localhost kernel: cfg80211: Loaded X.509 cert ‘sforshee: 00b28ddf47aef9cea7’
May 24 14:52:52 localhost kernel: usb 3-2: This Realtek USB WiFi dongle (0x2001:0x3319) is untested!
May 24 14:52:52 localhost kernel: usb 3-2: Please report results to [email protected]
May 24 14:52:56 localhost kernel: usb 3-2: Vendor: Realtek
May 24 14:52:56 localhost kernel: usb 3-2: Product: Wireless N
May 24 14:52:56 localhost kernel: usb 3-2: Serial: no USB Adap
May 24 14:52:56 localhost kernel: usb 3-2: rtl8192eu_parse_efuse: dumping efuse (0x200 bytes):
May 24 14:52:56 localhost kernel: usb 3-2: 00: 29 81 00 7c 01 40 03 00
May 24 14:52:56 localhost kernel: usb 3-2: 08: 40 74 04 50 14 00 00 00
May 24 14:52:56 localhost kernel: usb 3-2: 10: 21 21 21 21 21 21 25 25
May 24 14:52:56 localhost kernel: usb 3-2: 18: 25 25 25 ee 0f ef ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 20: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 28: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 30: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 38: ff ff 1e 1e 1e 1e 1e 1e
May 24 14:52:56 localhost kernel: usb 3-2: 40: 24 24 24 24 24 ee 0f ef
May 24 14:52:56 localhost kernel: usb 3-2: 48: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 50: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 58: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 60: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 68: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 70: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 78: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 80: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 88: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 90: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 98: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: a0: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: a8: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: b0: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: b8: 21 36 21 00 00 00 ff ff
May 24 14:52:56 localhost kernel: usb 3-2: c0: ff 01 00 10 00 00 00 ff
May 24 14:52:56 localhost kernel: usb 3-2: c8: 00 00 ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: d0: 01 20 19 33 e7 47 02 18
May 24 14:52:56 localhost kernel: usb 3-2: d8: 0f 76 06 8d cf 09 03 52
May 24 14:52:56 localhost kernel: usb 3-2: e0: 65 61 6c 74 65 6b 1d 03
May 24 14:52:56 localhost kernel: usb 3-2: e8: 57 69 72 65 6c 65 73 73
May 24 14:52:56 localhost kernel: usb 3-2: f0: 20 4e 20 4e 61 6e 6f 20
May 24 14:52:56 localhost kernel: usb 3-2: f8: 55 53 42 20 41 64 61 70
May 24 14:52:56 localhost kernel: usb 3-2: 100: 74 65 72 00 ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 108: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 110: ff ff ff ff ff ff ff 0d
May 24 14:52:56 localhost kernel: usb 3-2: 118: 03 00 05 00 30 00 00 00
May 24 14:52:56 localhost kernel: usb 3-2: 120: 00 93 ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 128: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 130: f6 a8 98 2d 03 92 98 00
May 24 14:52:56 localhost kernel: usb 3-2: 138: fc 8c 00 11 9b 44 02 0a
May 24 14:52:56 localhost kernel: usb 3-2: 140: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 148: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 150: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 158: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 160: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 168: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 170: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 178: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 180: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 188: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 190: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 198: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 1a0: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 1a8: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 1b0: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 1b8: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 1c0: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 1c8: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 1d0: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 1d8: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 1e0: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 1e8: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 1f0: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: 1f8: ff ff ff ff ff ff ff ff
May 24 14:52:56 localhost kernel: usb 3-2: RTL8192EU rev B (SMIC) 2T2R, TX queues 3, WiFi=1, BT=0, GPS=0, HI PA=0
May 24 14:52:56 localhost kernel: usb 3-2: RTL8192EU MAC: 18:0f:76:06:8d:cf
May 24 14:52:56 localhost kernel: usb 3-2: rtl8xxxu: Loading firmware rtlwifi/rtl8192eu_nic.bin
May 24 14:52:56 localhost kernel: usb 3-2: Firmware revision 19.0 (signature 0x92e1)
May 24 14:53:04 localhost kernel: usbcore: registered new interface driver rtl8xxxu
May 24 14:53:04 localhost NetworkManager[994]: [1590324784.9265] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/5)
May 24 14:53:04 localhost systemd[1]: Starting Load/Save RF Kill Switch Status…
May 24 14:53:04 localhost mtp-probe[3184]: checking bus 3, device 2: “/sys/devices/pci0000:00/0000:00:1c.4/0000:04:00.0/usb3/3-2”
May 24 14:53:04 localhost mtp-probe[3184]: bus: 3, device: 2 was not an MTP device
May 24 14:53:04 localhost systemd-udevd[3175]: Using default interface naming scheme ‘v243’.
May 24 14:53:04 localhost wireless[3189]: setting regulatory domain to IT based on timezone (Europe/Rome)
May 24 14:53:04 localhost NetworkManager[994]: [1590324784.9476] supplicant: wpa_supplicant running
May 24 14:53:04 localhost NetworkManager[994]: [1590324784.9736] rfkill0: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.4/0000:04:00.0/usb3/3-2/3-2:1.0/ieee80211/phy0/rfkill0) (driver rtl8xxxu)
May 24 14:53:04 localhost systemd-udevd[3175]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
May 24 14:53:04 localhost kernel: rtl8xxxu 3-2:1.0 wlp4s0u2: renamed from wlan0
May 24 14:53:04 localhost systemd[1]: Started Load/Save RF Kill Switch Status.
May 24 14:53:04 localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=‘unit=systemd-rfkill comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
May 24 14:53:04 localhost NetworkManager[994]: [1590324784.9973] device (wlan0): interface index 5 renamed iface from ‘wlan0’ to ‘wlp4s0u2’
May 24 14:53:05 localhost NetworkManager[994]: [1590324785.0201] device (wlp4s0u2): state change: unmanaged -> unavailable (reason ‘managed’, sys-iface-state: ‘external’)
May 24 14:53:05 localhost systemd-udevd[3159]: Using default interface naming scheme ‘v243’.
May 24 14:53:05 localhost org_kde_powerdevil[2303]: UdevQt: unhandled device action “move”
May 24 14:53:05 localhost plasmashell[2196]: UdevQt: unhandled device action “move”
May 24 14:53:05 localhost baloo_file[2209]: UdevQt: unhandled device action “move”
May 24 14:53:05 localhost dolphin[2285]: UdevQt: unhandled device action “move”
May 24 14:53:05 localhost NetworkManager[994]: [1590324785.4163] device (wlp4s0u2): set-hw-addr: set MAC address to 3E:92:17:D4:3F:56 (scanning)
May 24 14:53:05 localhost kwin_x11[2178]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 59525, resource id: 62914571, major code: 18 (ChangeProperty), minor code: 0
May 24 14:53:05 localhost wpa_supplicant[960]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface.P2PDevice dbus_property=P2PDeviceConfig getter failed
May 24 14:53:05 localhost NetworkManager[994]: [1590324785.8328] sup-iface[0x55796ab25100,wlp4s0u2]: supports 4 scan SSIDs
May 24 14:53:05 localhost NetworkManager[994]: [1590324785.8331] device (wlp4s0u2): supplicant interface state: starting -> ready
May 24 14:53:05 localhost NetworkManager[994]: [1590324785.8331] device (wlp4s0u2): state change: unavailable -> disconnected (reason ‘supplicant-available’, sys-iface-state: ‘managed’)
May 24 14:53:10 localhost systemd[1]: systemd-rfkill.service: Succeeded.
May 24 14:53:10 localhost audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=‘unit=systemd-rfkill comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
May 24 14:54:53 localhost audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=‘unit=packagekit comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
May 24 14:54:53 localhost systemd[1]: packagekit.service: Succeeded.
May 24 14:54:53 localhost systemd[1]: packagekit.service: Consumed 5.975s CPU time.
Prima con il modem Tim mi connettevo con il cavo ethernet ma adesso con Fastweb il telefono funziona con il voip e ho dovuto spostarlo ecco il motivo del wifi, con win… funziona senza problemi, mi viene il sospetto che sia un problema di driver 
Considerazione amara, se ad oggi non si riesce a far funzionare una scheda wifi usb con linux siamo messi male, con win… zero problemi 
Eh, fratello. Nessuno ci costringe a usare Linux. Io penso sempre: se con Windows uno si trova meglio, che lo usi. Comunque diceva quello: la rivoluzione non è una cena di gala.
Mettendo da parte la filosofia, il problema sono i costruttori di hardware che pensano solo a Windows. Tante volte anche chi usa il ben più blasonato Mac OS X si trova nelle stesse situazioni, se non peggio, se non sta attento alla compatibilità.
Comunque il chip è un Realtek. Il modello sembra essere RTL8192EU, rtl8xxxu se non sbaglio è il modulo che viene caricato, magari non va benissimo con quel chip lì (nei log si legge This Realtek USB WiFi dongle (0x2001:0x3319) is untested!).
Prova a cercare su internet se esiste un modulo specifico per RTL8192EU da compilare.
Per esempio qui: https://github.com/Mange/rtl8192eu-linux-driver
Guarda, qui c’è uno con lo stesso problema:
Insomma, c’è da sudare un attimo (non solo col comando sudo 
).