Reti WiFi mai individuate - Ubuntu 20.04
Reti WiFi mai individuate - Ubuntu 20.04
Accedendo alle impostazioni WiFi non risulta alcuna rete, anche se ce n'è più di una che utilizzo con altri dispositivi e Windows stesso sullo stesso dispositivo. L'interfaccia segnala chiaramente la ricerca per qualche secondo, ma non risulta nulla.
La cosa strana è che per due volte, completamente a caso per quanto ne so, le reti sono apparse (tutte) e ho potuto connettermi ad internet. All'accesso successivo le reti earano nuovamente invisibili.
- thece
- Tenace Tecnocrate
- Messaggi: 12949
- Iscrizione: lunedì 23 aprile 2007, 14:16
- Distribuzione: Debian 12 (Bookworm) - KDE
Re: Reti WiFi mai individuate - Ubuntu 20.04
apri il terminale, dai i seguenti comandi e postane gli output qui sul Forum
Codice: Seleziona tutto
sudo lshw -c network
lspci -knn | grep -A 2 -i net
nmcli device wifi list
Re: Reti WiFi mai individuate - Ubuntu 20.04
Codice: Seleziona tutto
*-network
description: Wireless interface
product: MT7630e 802.11bgn Wireless Network Adapter
vendor: MEDIATEK Corp.
physical id: 0
bus info: pci@0000:03:00.0
logical name: wlp3s0f0
version: 00
serial: 54:35:30:05:82:93
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=mt76x0e driverversion=5.8.0-43-generic firmware=1.0.07-b370 latency=0 link=no multicast=yes wireless=IEEE 802.11
resources: irq:17 memory:f7900000-f79fffff
*-network
description: Ethernet interface
product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0.2
bus info: pci@0000:04:00.2
logical name: enp4s0f2
version: 0a
serial: e0:3f:49:b8:4c:5e
capacity: 1Gbit/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=5.8.0-43-generic firmware=rtl8411-1_0.0.3 06/18/12 latency=0 link=no multicast=yes port=MII
resources: irq:19 ioport:d000(size=256) memory:f2104000-f2104fff memory:f2100000-f2103fff
03:00.0 Network controller [0280]: MEDIATEK Corp. MT7630e 802.11bgn Wireless Network Adapter [14c3:7630]
Subsystem: Foxconn International, Inc. MT7630e 802.11bgn Wireless Network Adapter [105b:e074]
Kernel driver in use: mt76x0e
Kernel modules: mt76x0e
--
04:00.2 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0a)
Subsystem: ASUSTeK Computer Inc. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1043:200f]
Kernel driver in use: r8169
Kernel modules: r8169
IN-USE BSSID SSID MODE CHAN RATE SIGNAL BARS SECURITY
- thece
- Tenace Tecnocrate
- Messaggi: 12949
- Iscrizione: lunedì 23 aprile 2007, 14:16
- Distribuzione: Debian 12 (Bookworm) - KDE
Re: Reti WiFi mai individuate - Ubuntu 20.04
Codice: Seleziona tutto
nmcli general
sudo iwlist wlp3s0f0 scan | grep -i ssid -B 5 -A 5
Re: Reti WiFi mai individuate - Ubuntu 20.04
- thece
- Tenace Tecnocrate
- Messaggi: 12949
- Iscrizione: lunedì 23 aprile 2007, 14:16
- Distribuzione: Debian 12 (Bookworm) - KDE
Re: Reti WiFi mai individuate - Ubuntu 20.04
Re: Reti WiFi mai individuate - Ubuntu 20.04
Codice: Seleziona tutto
STATE CONNECTIVITY WIFI-HW WIFI WWAN-HW WWAN
connected full enabled enabled enabled enabled
Codice: Seleziona tutto
wlp3s0f0 Interface doesn't support scanning : Device or resource busy
- thece
- Tenace Tecnocrate
- Messaggi: 12949
- Iscrizione: lunedì 23 aprile 2007, 14:16
- Distribuzione: Debian 12 (Bookworm) - KDE
Re: Reti WiFi mai individuate - Ubuntu 20.04
Codice: Seleziona tutto
ifconfig
Codice: Seleziona tutto
ip a
Se non hai già il comando installato, installalo (*) con questo
Codice: Seleziona tutto
sudo apt install net-tools
Re: Reti WiFi mai individuate - Ubuntu 20.04
Codice: Seleziona tutto
enp4s0f2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.109 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::f12f:873c:c4f6:9813 prefixlen 64 scopeid 0x20<link>
ether e0:3f:49:b8:4c:5e txqueuelen 1000 (Ethernet)
RX packets 65520 bytes 89905870 (89.9 MB)
RX errors 0 dropped 6 overruns 0 frame 0
TX packets 31385 bytes 3219146 (3.2 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 82273 bytes 5927787 (5.9 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 82273 bytes 5927787 (5.9 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlp3s0f0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 54:35:30:05:82:93 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
- thece
- Tenace Tecnocrate
- Messaggi: 12949
- Iscrizione: lunedì 23 aprile 2007, 14:16
- Distribuzione: Debian 12 (Bookworm) - KDE
Re: Reti WiFi mai individuate - Ubuntu 20.04
Proseguiamo con la ricerca guasti
Codice: Seleziona tutto
dmesg | egrep 'wlp3s0f0|mt76x0e|cfg80211|mac80211'
cat /var/log/syslog | grep -i networkmanager | tail -n 50
Re: Reti WiFi mai individuate - Ubuntu 20.04
Codice: Seleziona tutto
[ 23.103183] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 23.103540] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 23.917644] mt76x0e 0000:03:00.0: ASIC revision: 76300002
[ 24.192365] mt76x0e 0000:03:00.0: Firmware Version: 1.0.07
[ 25.062685] mt76x0e 0000:03:00.0: EEPROM ver:01 fae:05
[ 25.062762] mt76x0e 0000:03:00.0: driver does not support HW RF ctrl
[ 26.199098] mt76x0e 0000:03:00.0 wlp3s0f0: renamed from wlan0
[10248.293112] mt76x0e 0000:03:00.0: TX DMA did not stop
[10337.543311] mt76x0e 0000:03:00.0: TX DMA did not stop
[13516.117992] mt76x0e 0000:03:00.0: TX DMA did not stop
[24615.929212] mt76x0e 0000:03:00.0: TX DMA did not stop
[27188.565989] mt76x0e 0000:03:00.0: TX DMA did not stop
[27926.086826] mt76x0e 0000:03:00.0: TX DMA did not stop
[30926.355161] mt76x0e 0000:03:00.0: TX DMA did not stop
[31135.190604] mt76x0e 0000:03:00.0: TX DMA did not stop
Mar 23 14:01:19 tommy-X550CC NetworkManager[712]: <info> [1616504479.8957] manager: NetworkManager state is now CONNECTING
Mar 23 14:01:19 tommy-X550CC NetworkManager[712]: <info> [1616504479.8960] device (enp4s0f2): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Mar 23 14:01:19 tommy-X550CC NetworkManager[712]: <info> [1616504479.8967] device (enp4s0f2): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Mar 23 14:01:19 tommy-X550CC NetworkManager[712]: <info> [1616504479.8972] dhcp4 (enp4s0f2): activation: beginning transaction (timeout in 45 seconds)
Mar 23 14:01:20 tommy-X550CC NetworkManager[712]: <info> [1616504480.0380] dhcp4 (enp4s0f2): option dhcp_lease_time => '43320'
Mar 23 14:01:20 tommy-X550CC NetworkManager[712]: <info> [1616504480.0381] dhcp4 (enp4s0f2): option domain_name_servers => '192.168.1.1'
Mar 23 14:01:20 tommy-X550CC NetworkManager[712]: <info> [1616504480.0381] dhcp4 (enp4s0f2): option expiry => '1616547799'
Mar 23 14:01:20 tommy-X550CC NetworkManager[712]: <info> [1616504480.0381] dhcp4 (enp4s0f2): option host_name => 'tommy-X550CC'
Mar 23 14:01:20 tommy-X550CC NetworkManager[712]: <info> [1616504480.0382] dhcp4 (enp4s0f2): option ip_address => '192.168.1.109'
Mar 23 14:01:20 tommy-X550CC NetworkManager[712]: <info> [1616504480.0382] dhcp4 (enp4s0f2): option next_server => '192.168.1.1'
Mar 23 14:01:20 tommy-X550CC NetworkManager[712]: <info> [1616504480.0382] dhcp4 (enp4s0f2): option requested_broadcast_address => '1'
Mar 23 14:01:20 tommy-X550CC NetworkManager[712]: <info> [1616504480.0382] dhcp4 (enp4s0f2): option requested_domain_name => '1'
Mar 23 14:01:20 tommy-X550CC NetworkManager[712]: <info> [1616504480.0382] dhcp4 (enp4s0f2): option requested_domain_name_servers => '1'
Mar 23 14:01:20 tommy-X550CC NetworkManager[712]: <info> [1616504480.0383] dhcp4 (enp4s0f2): option requested_domain_search => '1'
Mar 23 14:01:20 tommy-X550CC NetworkManager[712]: <info> [1616504480.0383] dhcp4 (enp4s0f2): option requested_host_name => '1'
Mar 23 14:01:20 tommy-X550CC NetworkManager[712]: <info> [1616504480.0383] dhcp4 (enp4s0f2): option requested_interface_mtu => '1'
Mar 23 14:01:20 tommy-X550CC NetworkManager[712]: <info> [1616504480.0384] dhcp4 (enp4s0f2): option requested_ms_classless_static_routes => '1'
Mar 23 14:01:20 tommy-X550CC NetworkManager[712]: <info> [1616504480.0384] dhcp4 (enp4s0f2): option requested_nis_domain => '1'
Mar 23 14:01:20 tommy-X550CC NetworkManager[712]: <info> [1616504480.0384] dhcp4 (enp4s0f2): option requested_nis_servers => '1'
Mar 23 14:01:20 tommy-X550CC NetworkManager[712]: <info> [1616504480.0384] dhcp4 (enp4s0f2): option requested_ntp_servers => '1'
Mar 23 14:01:20 tommy-X550CC NetworkManager[712]: <info> [1616504480.0384] dhcp4 (enp4s0f2): option requested_rfc3442_classless_static_routes => '1'
Mar 23 14:01:20 tommy-X550CC NetworkManager[712]: <info> [1616504480.0385] dhcp4 (enp4s0f2): option requested_root_path => '1'
Mar 23 14:01:20 tommy-X550CC NetworkManager[712]: <info> [1616504480.0385] dhcp4 (enp4s0f2): option requested_routers => '1'
Mar 23 14:01:20 tommy-X550CC NetworkManager[712]: <info> [1616504480.0385] dhcp4 (enp4s0f2): option requested_static_routes => '1'
Mar 23 14:01:20 tommy-X550CC NetworkManager[712]: <info> [1616504480.0385] dhcp4 (enp4s0f2): option requested_subnet_mask => '1'
Mar 23 14:01:20 tommy-X550CC NetworkManager[712]: <info> [1616504480.0385] dhcp4 (enp4s0f2): option requested_time_offset => '1'
Mar 23 14:01:20 tommy-X550CC NetworkManager[712]: <info> [1616504480.0385] dhcp4 (enp4s0f2): option requested_wpad => '1'
Mar 23 14:01:20 tommy-X550CC NetworkManager[712]: <info> [1616504480.0386] dhcp4 (enp4s0f2): option routers => '192.168.1.1'
Mar 23 14:01:20 tommy-X550CC NetworkManager[712]: <info> [1616504480.0386] dhcp4 (enp4s0f2): option subnet_mask => '255.255.255.0'
Mar 23 14:01:20 tommy-X550CC NetworkManager[712]: <info> [1616504480.0386] dhcp4 (enp4s0f2): state changed unknown -> bound
Mar 23 14:01:20 tommy-X550CC NetworkManager[712]: <info> [1616504480.0426] device (enp4s0f2): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Mar 23 14:01:20 tommy-X550CC dbus-daemon[711]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.16' (uid=0 pid=712 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Mar 23 14:01:20 tommy-X550CC NetworkManager[712]: <info> [1616504480.1138] device (enp4s0f2): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Mar 23 14:01:20 tommy-X550CC NetworkManager[712]: <info> [1616504480.1145] device (enp4s0f2): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Mar 23 14:01:20 tommy-X550CC NetworkManager[712]: <info> [1616504480.1152] manager: NetworkManager state is now CONNECTED_LOCAL
Mar 23 14:01:20 tommy-X550CC NetworkManager[712]: <info> [1616504480.1171] manager: NetworkManager state is now CONNECTED_SITE
Mar 23 14:01:20 tommy-X550CC NetworkManager[712]: <info> [1616504480.1175] policy: set 'Wired connection 1' (enp4s0f2) as default for IPv4 routing and DNS
Mar 23 14:01:20 tommy-X550CC NetworkManager[712]: <info> [1616504480.1187] device (enp4s0f2): Activation: successful, device activated.
Mar 23 14:01:20 tommy-X550CC NetworkManager[712]: <info> [1616504480.5355] manager: NetworkManager state is now CONNECTED_GLOBAL
Mar 23 14:01:20 tommy-X550CC whoopsie[993]: [14:01:20] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/4
Mar 23 14:01:20 tommy-X550CC whoopsie[993]: [14:01:20] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/4
Mar 23 14:01:20 tommy-X550CC whoopsie[993]: [14:01:20] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/4
Mar 23 14:01:31 tommy-X550CC systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Mar 23 14:11:39 tommy-X550CC NetworkManager[712]: <info> [1616505099.9974] manager: NetworkManager state is now CONNECTED_SITE
Mar 23 14:11:40 tommy-X550CC dbus-daemon[711]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.16' (uid=0 pid=712 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Mar 23 14:11:40 tommy-X550CC NetworkManager[712]: <info> [1616505100.2749] manager: NetworkManager state is now CONNECTED_GLOBAL
Mar 23 14:11:40 tommy-X550CC whoopsie[993]: [14:11:40] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/4
Mar 23 14:11:40 tommy-X550CC whoopsie[993]: [14:11:40] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/4
Mar 23 14:11:40 tommy-X550CC whoopsie[993]: [14:11:40] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/4
Mar 23 14:11:51 tommy-X550CC systemd[1]: NetworkManager-dispatcher.service: Succeeded.
- thece
- Tenace Tecnocrate
- Messaggi: 12949
- Iscrizione: lunedì 23 aprile 2007, 14:16
- Distribuzione: Debian 12 (Bookworm) - KDE
Re: Reti WiFi mai individuate - Ubuntu 20.04
Codice: Seleziona tutto
nmcli connection
Re: Reti WiFi mai individuate - Ubuntu 20.04
Codice: Seleziona tutto
NAME UUID TYPE DEVICE
Wired connection 1 015322b4-933a-35b5-b287-97b630e30aad ethernet enp4s0f2
Inoltre a suo tempo salvai le reti (quando sono apparse), e mi apparivano nella lista delle reti memorizzate, finché non le ho rimosse.
- thece
- Tenace Tecnocrate
- Messaggi: 12949
- Iscrizione: lunedì 23 aprile 2007, 14:16
- Distribuzione: Debian 12 (Bookworm) - KDE
Re: Reti WiFi mai individuate - Ubuntu 20.04
[EDIT]
E' solo un test
Codice: Seleziona tutto
sudo ifconfig wlp3s0f0 down
sudo ifconfig wlp3s0f0 up
sudo iwlist wlp3s0f0 scan | grep -i ssid -B 5 -A 5
Re: Reti WiFi mai individuate - Ubuntu 20.04
- thece
- Tenace Tecnocrate
- Messaggi: 12949
- Iscrizione: lunedì 23 aprile 2007, 14:16
- Distribuzione: Debian 12 (Bookworm) - KDE
Re: Reti WiFi mai individuate - Ubuntu 20.04
Il 3° ripetilo in questa forma
Codice: Seleziona tutto
sudo iwlist wlp3s0f0 scan
Il tuo PC è in dualboot con Windows? Giusto per verificare che la scheda di rete WIFI sia funzionante. Non possiamo ancora escludere che si sia guastata.
Se si cerca in Rete "mt76x0e issues" vengono fuori un pò di risultati, ma non ho letto. mt76x0e è il driver che pilota la tua scheda di rete WIFI
Re: Reti WiFi mai individuate - Ubuntu 20.04
Il comando dà di nuovo
Codice: Seleziona tutto
wlp3s0f0 Interface doesn't support scanning : Device or resource busy
- thece
- Tenace Tecnocrate
- Messaggi: 12949
- Iscrizione: lunedì 23 aprile 2007, 14:16
- Distribuzione: Debian 12 (Bookworm) - KDE
Re: Reti WiFi mai individuate - Ubuntu 20.04
Re: Reti WiFi mai individuate - Ubuntu 20.04
Immagino che windows tenesse la scheda di rete occupata?
Grazie mille per l'aiuto
Re: Reti WiFi mai individuate - Ubuntu 20.04
Ok, potrebbe comunque trattarsi di qualche altro problema. Per ora funziona..!
Ma tieni conto che ogni volta che anche solo metto il computer in sleep mode mi chiede quale boot avviare, se windows o ubuntu. Io non ricordo le altre volte se avessi arrestato o meno Windows.
Quello che voglio dire è che probabilmente non avevo mai arrestato windows, e questo continuava a occupare la scheda.
Chi c’è in linea
Visualizzano questa sezione: 0 utenti iscritti e 5 ospiti