Omv i586 32 aggiornata a 3.02 non collega il wifi - scambia l'interfaccia wifi per interfaccia ethernet

Buona sera a Tutti. Omv i586 32 sul mio portatile non si connette al wifi di casa malgrado la chiave di accesso sia corretta.
Quando tento di connettere il wifi da plasma mediante il pulsante connect non fa nulla e continua a ripresentare il pulsante connect
Ho provato sempre via grafica a cancellare l’interfaccia e ricrearla ma nulla di che, anzi quando vado a vedere le interfacce attive vedo che l’interfaccia wifi la vede come ethernet.
anche se la ricreo come wifi poi non riesco a collegarla e la ritrovo come ethernet.
Quando collego il cavo di rete mi collego e come vedete posso navigare ma lo posso fare solo mediante il cavo di lan.
Allego alcune liste tratte da console:
[root@new-host-4 giorgio]# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.136 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::215:60ff:feb7:32d5 prefixlen 64 scopeid 0x20
ether 00:15:60:b7:32:d5 txqueuelen 1000 (Ethernet)
RX packets 4938 bytes 3737175 (3.5 MiB)
RX errors 0 dropped 71 overruns 0 frame 0
TX packets 3210 bytes 429425 (419.3 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Local Loopback)
RX packets 185 bytes 16868 (16.4 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 185 bytes 16868 (16.4 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlp2s4: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether f2:8d:04:50:f8:20 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

[root@new-host-4 giorgio]# lspci
00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
00:1d.0 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 03)
00:1d.1 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 03)
00:1d.2 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 03)
00:1d.3 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 03)
00:1d.7 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d3)
00:1e.2 Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC’97 Audio Controller (rev 03)
00:1e.3 Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC’97 Modem Controller (rev 03)
00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) IDE Controller (rev 03)
02:04.0 Network controller: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05)
02:06.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller
02:06.2 FireWire (IEEE 1394): Texas Instruments OHCI Compliant IEEE 1394 Host Controller
02:0e.0 Ethernet controller: Broadcom Limited BCM4401-B0 100Base-TX (rev 02)

Grazie
Giorgio

Controlla di aver installato il pacchetto contenente il firmware

rpm -qa | grep ipw2200-firmware

altrimenti lo installi. Se ancora non funzione controlla che il relativo modulo del kernel sia stato correttamente caricato:

lsmod | grep -i ipw2100

In caso contrario prova a (ri)caricarlo manualmente:

modprobe -r ipw2100
modprobe ipw2100
1 Like

Purtroppo è un problema “ostico” ho verificato il firmware c’è e mi pare anche che il modulo sia caricato.
Inizialmente non lo era ma poi con modprobe l’ho caricato come descritto.

Ora vedo che lo carica sempre, ma il wireless non lo collega.
Di seguito il tracciato della console.
Volevo provare a reinstallare il firmware anche se è solo una ipotesi poco fantasiosa.

[root@new-host-4 giorgio]# rpm -qa |grep ipw2200
ipw2200-firmware-3.1-5-omv2015.0.noarch

[root@new-host-4 giorgio]# lsmod | grep -i ipw2200
ipw2200 139264 0
libipw 32768 1 ipw2200
cfg80211 516096 2 ipw2200,libipw
[root@new-host-4 giorgio]

Grazie
Ciao

Scusate volevo allegare anche questo:
[root@new-host-4 giorgio]# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.137 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::215:60ff:feb7:32d5 prefixlen 64 scopeid 0x20
ether 00:15:60:b7:32:d5 txqueuelen 1000 (Ethernet)
RX packets 6553 bytes 2054449 (1.9 MiB)
RX errors 0 dropped 182 overruns 0 frame 0
TX packets 3229 bytes 523187 (510.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Local Loopback)
RX packets 180 bytes 16462 (16.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 180 bytes 16462 (16.0 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlp2s4: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 06:3e:2c:87:4f:36 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
Grazie
Giorgio

Network-manager è il gestore di rete predefinito e conviene non utilizzare altri programmi per la configurazione. La sua interfaccia testuale è nmcli, Puoi postare anche il risultato di:

nmcli d

Grazie Mandian
ecco l’output
[root@new-host-4 giorgio]# nmcli d
DEVICE TYPE STATE CONNECTION
eth0 ethernet connected System eth0
wlp2s4 wifi disconnected –
lo loopback unmanaged

Giorgio

Anche questo un po più esteso
[root@new-host-4 giorgio]# nmcli
eth0: connected to System eth0
“Broadcom Limited BCM4401-B0 100Base-TX (NX6110/NC6120)”
ethernet (b44), 00:15:60:B7:32:D5, hw, mtu 1500
ip4 default
inet4 192.168.1.137/24
inet4 192.168.1.135/24
inet6 fe80::215:60ff:feb7:32d5/64

wlp2s4: disconnected
“Intel PRO/Wireless 2200BG [Calexico2] (nc6120/nx8220/nw8240)”
3 connections available
wifi (ipw2200), 72:7B:F8:63:D1:7E, hw

lo: unmanaged
loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536

DNS configuration:
servers: 62.101.93.101 83.103.25.250
domains: fastwebnet.it
interface: eth0
Grazie

La tua scheda è una Intel Corporation PRO/Wireless 2200BG perciò penso di aver sbagliato il nome nel post precedente :flushed:

I comandi corretti dovrebbero essere

lsmod | grep -i ipw2200
modprobe -r ipw2200
modprobe ipw2200

Se ancora non funziona pova a cercare tra gli errori del kernel

dmesg | grep iwl

1 Like

Cosa strana ho dovuto lanciare due volta il comando
modprobe -r ipw2200
per non vederlo più in lsmod

poi l’ho ricaricato e ho provato a connettere il wifi.
Se conrollo il led del wifi vedo che durante il entativo di connessione emette due lampeggi ravvicinati ma poi non rimane fisso, come si sconnettesse immediatamente

Ho poi notato questo nel file modprobe.conf, due righe per il modulo ipw2200 una come pci è normale?
ecco il cat
[root@new-host-4 giorgio]# cat /etc/modprobe.conf
alias pci:v00008086d00004220sv0000103Csd000012F6bc02sc80i00 ipw2200
alias wlp2s4 ipw2200

L’ouput degli errori del kernel non c’e nulla purtroppo.
GRAAZIEEE

pero ho trovato qualcosa anche negli errori kernel ecco il report un po’ lunghetto ma potrebbe essere chiarificatore per chi lo sa interpretare come Voi

[root@new-host-4 giorgio]# dmesg | grep wlp2
[Sat Jun  3 17:22:58 2017] ipw2200 0000:02:04.0 wlp2s4: renamed from eth1
[Sat Jun  3 17:22:59 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 17:23:01 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 17:23:01 2017] wlp2s4: Setting MAC to 86:b0:ef:c7:66:7d
[Sat Jun  3 17:23:01 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 17:23:01 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 17:28:43 2017] wlp2s4: Setting MAC to 76:39:08:8b:3c:5d
[Sat Jun  3 17:28:43 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 17:28:43 2017] wlp2s4: Setting MAC to 76:39:08:8b:3c:5d
[Sat Jun  3 17:28:43 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 17:33:59 2017] wlp2s4: Setting MAC to 7a:91:25:4d:29:42
[Sat Jun  3 17:33:59 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 17:33:59 2017] wlp2s4: Setting MAC to 7a:91:25:4d:29:42
[Sat Jun  3 17:33:59 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 17:39:15 2017] wlp2s4: Setting MAC to f2:96:8d:45:02:a7
[Sat Jun  3 17:39:15 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 17:39:15 2017] wlp2s4: Setting MAC to f2:96:8d:45:02:a7
[Sat Jun  3 17:39:15 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 17:44:31 2017] wlp2s4: Setting MAC to aa:53:7e:1b:f7:5c
[Sat Jun  3 17:44:31 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 17:44:31 2017] wlp2s4: Setting MAC to aa:53:7e:1b:f7:5c
[Sat Jun  3 17:44:31 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 17:48:54 2017] wlp2s4: Setting MAC to 00:16:6f:61:a0:2d
[Sat Jun  3 17:48:54 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 17:48:55 2017] wlp2s4: Setting MAC to 3e:46:ac:3e:9c:47
[Sat Jun  3 17:48:55 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 17:48:55 2017] wlp2s4: Setting MAC to 3e:46:ac:3e:9c:47
[Sat Jun  3 17:48:55 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 17:48:55 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 17:53:56 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 17:53:56 2017] wlp2s4: Setting MAC to 7e:22:b7:e2:8a:e9
[Sat Jun  3 17:53:57 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 17:53:57 2017] wlp2s4: Setting MAC to 7e:22:b7:e2:8a:e9
[Sat Jun  3 17:53:57 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 17:59:12 2017] wlp2s4: Setting MAC to 26:15:50:1e:d2:ec
[Sat Jun  3 17:59:12 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 17:59:12 2017] wlp2s4: Setting MAC to 26:15:50:1e:d2:ec
[Sat Jun  3 17:59:12 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 18:04:28 2017] wlp2s4: Setting MAC to ba:1d:35:cb:9a:61
[Sat Jun  3 18:04:28 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 18:04:28 2017] wlp2s4: Setting MAC to ba:1d:35:cb:9a:61
[Sat Jun  3 18:04:28 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 18:09:44 2017] wlp2s4: Setting MAC to ee:eb:4e:f0:95:90
[Sat Jun  3 18:09:44 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 18:09:44 2017] wlp2s4: Setting MAC to ee:eb:4e:f0:95:90
[Sat Jun  3 18:09:44 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 18:15:00 2017] wlp2s4: Setting MAC to 06:3e:2c:87:4f:36
[Sat Jun  3 18:15:00 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 18:15:00 2017] wlp2s4: Setting MAC to 06:3e:2c:87:4f:36
[Sat Jun  3 18:15:00 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 18:20:16 2017] wlp2s4: Setting MAC to 26:a4:17:cf:66:56
[Sat Jun  3 18:20:16 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 18:20:16 2017] wlp2s4: Setting MAC to 26:a4:17:cf:66:56
[Sat Jun  3 18:20:16 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 18:25:32 2017] wlp2s4: Setting MAC to 96:28:c9:82:a1:f6
[Sat Jun  3 18:25:32 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 18:25:32 2017] wlp2s4: Setting MAC to 96:28:c9:82:a1:f6
[Sat Jun  3 18:25:32 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 18:30:48 2017] wlp2s4: Setting MAC to 92:d7:df:f0:cb:19
[Sat Jun  3 18:30:48 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 18:30:48 2017] wlp2s4: Setting MAC to 92:d7:df:f0:cb:19
[Sat Jun  3 18:30:48 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 18:36:04 2017] wlp2s4: Setting MAC to de:a4:8c:5a:10:23
[Sat Jun  3 18:36:04 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 18:36:04 2017] wlp2s4: Setting MAC to de:a4:8c:5a:10:23
[Sat Jun  3 18:36:04 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 18:41:20 2017] wlp2s4: Setting MAC to 6e:aa:10:d3:db:b0
[Sat Jun  3 18:41:20 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 18:41:20 2017] wlp2s4: Setting MAC to 6e:aa:10:d3:db:b0
[Sat Jun  3 18:41:20 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 18:46:36 2017] wlp2s4: Setting MAC to fa:c6:55:96:a1:51
[Sat Jun  3 18:46:36 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 18:46:36 2017] wlp2s4: Setting MAC to fa:c6:55:96:a1:51
[Sat Jun  3 18:46:36 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 18:51:52 2017] wlp2s4: Setting MAC to 72:7b:f8:63:d1:7e
[Sat Jun  3 18:51:52 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 18:51:52 2017] wlp2s4: Setting MAC to 72:7b:f8:63:d1:7e
[Sat Jun  3 18:51:52 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 18:57:08 2017] wlp2s4: Setting MAC to d2:38:1c:6c:0c:b0
[Sat Jun  3 18:57:08 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 18:57:08 2017] wlp2s4: Setting MAC to d2:38:1c:6c:0c:b0
[Sat Jun  3 18:57:08 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:02:24 2017] wlp2s4: Setting MAC to fe:86:64:c9:62:5d
[Sat Jun  3 19:02:24 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:02:24 2017] wlp2s4: Setting MAC to fe:86:64:c9:62:5d
[Sat Jun  3 19:02:24 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:07:40 2017] wlp2s4: Setting MAC to 72:c9:5f:1a:72:d5
[Sat Jun  3 19:07:40 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:07:40 2017] wlp2s4: Setting MAC to 72:c9:5f:1a:72:d5
[Sat Jun  3 19:07:40 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:12:56 2017] wlp2s4: Setting MAC to fe:ec:65:8e:8e:3e
[Sat Jun  3 19:12:56 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:12:56 2017] wlp2s4: Setting MAC to fe:ec:65:8e:8e:3e
[Sat Jun  3 19:12:56 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:18:12 2017] wlp2s4: Setting MAC to b2:a9:94:f4:81:c9
[Sat Jun  3 19:18:12 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:18:12 2017] wlp2s4: Setting MAC to b2:a9:94:f4:81:c9
[Sat Jun  3 19:18:12 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:23:28 2017] wlp2s4: Setting MAC to f6:19:5e:d7:c4:d4
[Sat Jun  3 19:23:28 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:23:28 2017] wlp2s4: Setting MAC to f6:19:5e:d7:c4:d4
[Sat Jun  3 19:23:28 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:24:38 2017] LoadPin: kernel-module old-api-pinning-ignored obj=<unknown> pid=8824 cmdline="/sbin/modprobe -q -- wlp2s4"
[Sat Jun  3 19:24:38 2017] LoadPin: kernel-module old-api-pinning-ignored obj=<unknown> pid=8825 cmdline="/sbin/modprobe -q -- wlp2s4"
[Sat Jun  3 19:24:38 2017] LoadPin: kernel-module old-api-pinning-ignored obj=<unknown> pid=8825 cmdline="/sbin/modprobe -q -- wlp2s4"
[Sat Jun  3 19:24:38 2017] LoadPin: kernel-module old-api-pinning-ignored obj=<unknown> pid=8825 cmdline="/sbin/modprobe -q -- wlp2s4"
[Sat Jun  3 19:24:38 2017] LoadPin: kernel-module old-api-pinning-ignored obj=<unknown> pid=8824 cmdline="/sbin/modprobe -q -- wlp2s4"
[Sat Jun  3 19:24:38 2017] LoadPin: kernel-module old-api-pinning-ignored obj=<unknown> pid=8824 cmdline="/sbin/modprobe -q -- wlp2s4"
[Sat Jun  3 19:24:38 2017] LoadPin: kernel-module old-api-pinning-ignored obj=<unknown> pid=8825 cmdline="/sbin/modprobe -q -- wlp2s4"
[Sat Jun  3 19:24:38 2017] LoadPin: firmware pinning-ignored obj="/lib/firmware/ipw2200-bss.fw" pid=8824 cmdline="/sbin/modprobe -q -- wlp2s4"
[Sat Jun  3 19:24:39 2017] ipw2200 0000:02:04.0 wlp2s4: renamed from eth1
[Sat Jun  3 19:24:40 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:24:40 2017] wlp2s4: Setting MAC to e6:a9:53:d1:43:f3
[Sat Jun  3 19:24:40 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:24:40 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:28:50 2017] LoadPin: kernel-module old-api-pinning-ignored obj=<unknown> pid=9010 cmdline="/sbin/modprobe -q -- wlp2s4"
[Sat Jun  3 19:28:50 2017] LoadPin: kernel-module old-api-pinning-ignored obj=<unknown> pid=9011 cmdline="/sbin/modprobe -q -- wlp2s4"
[Sat Jun  3 19:28:50 2017] LoadPin: kernel-module old-api-pinning-ignored obj=<unknown> pid=9011 cmdline="/sbin/modprobe -q -- wlp2s4"
[Sat Jun  3 19:28:50 2017] LoadPin: kernel-module old-api-pinning-ignored obj=<unknown> pid=9010 cmdline="/sbin/modprobe -q -- wlp2s4"
[Sat Jun  3 19:28:50 2017] LoadPin: kernel-module old-api-pinning-ignored obj=<unknown> pid=9011 cmdline="/sbin/modprobe -q -- wlp2s4"
[Sat Jun  3 19:28:50 2017] LoadPin: kernel-module old-api-pinning-ignored obj=<unknown> pid=9010 cmdline="/sbin/modprobe -q -- wlp2s4"
[Sat Jun  3 19:28:50 2017] LoadPin: kernel-module old-api-pinning-ignored obj=<unknown> pid=9011 cmdline="/sbin/modprobe -q -- wlp2s4"
[Sat Jun  3 19:28:50 2017] LoadPin: kernel-module old-api-pinning-ignored obj=<unknown> pid=9010 cmdline="/sbin/modprobe -q -- wlp2s4"
[Sat Jun  3 19:28:50 2017] LoadPin: firmware pinning-ignored obj="/lib/firmware/ipw2200-bss.fw" pid=9011 cmdline="/sbin/modprobe -q -- wlp2s4"
[Sat Jun  3 19:28:50 2017] ipw2200 0000:02:04.0 wlp2s4: renamed from eth1
[Sat Jun  3 19:28:51 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:28:51 2017] wlp2s4: Setting MAC to 32:0b:52:6d:64:b5
[Sat Jun  3 19:28:51 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:28:51 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:28:52 2017] LoadPin: kernel-module old-api-pinning-ignored obj=<unknown> pid=9122 cmdline="/sbin/modprobe -q -- wlp2s4"
[Sat Jun  3 19:28:52 2017] LoadPin: kernel-module old-api-pinning-ignored obj=<unknown> pid=9121 cmdline="/sbin/modprobe -q -- wlp2s4"
[Sat Jun  3 19:28:52 2017] LoadPin: kernel-module old-api-pinning-ignored obj=<unknown> pid=9121 cmdline="/sbin/modprobe -q -- wlp2s4"
[Sat Jun  3 19:28:52 2017] LoadPin: kernel-module old-api-pinning-ignored obj=<unknown> pid=9122 cmdline="/sbin/modprobe -q -- wlp2s4"
[Sat Jun  3 19:28:52 2017] LoadPin: kernel-module old-api-pinning-ignored obj=<unknown> pid=9121 cmdline="/sbin/modprobe -q -- wlp2s4"
[Sat Jun  3 19:28:52 2017] LoadPin: kernel-module old-api-pinning-ignored obj=<unknown> pid=9122 cmdline="/sbin/modprobe -q -- wlp2s4"
[Sat Jun  3 19:28:52 2017] LoadPin: kernel-module old-api-pinning-ignored obj=<unknown> pid=9122 cmdline="/sbin/modprobe -q -- wlp2s4"
[Sat Jun  3 19:28:52 2017] LoadPin: kernel-module old-api-pinning-ignored obj=<unknown> pid=9121 cmdline="/sbin/modprobe -q -- wlp2s4"
[Sat Jun  3 19:28:52 2017] LoadPin: firmware pinning-ignored obj="/lib/firmware/ipw2200-bss.fw" pid=9122 cmdline="/sbin/modprobe -q -- wlp2s4"
[Sat Jun  3 19:28:52 2017] ipw2200 0000:02:04.0 wlp2s4: renamed from eth1
[Sat Jun  3 19:28:53 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:28:53 2017] wlp2s4: Setting MAC to 96:0a:39:55:9e:a1
[Sat Jun  3 19:28:53 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:28:53 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:28:54 2017] LoadPin: kernel-module old-api-pinning-ignored obj=<unknown> pid=9223 cmdline="/sbin/modprobe -q -- wlp2s4"
[Sat Jun  3 19:28:54 2017] LoadPin: kernel-module old-api-pinning-ignored obj=<unknown> pid=9222 cmdline="/sbin/modprobe -q -- wlp2s4"
[Sat Jun  3 19:28:54 2017] LoadPin: kernel-module old-api-pinning-ignored obj=<unknown> pid=9222 cmdline="/sbin/modprobe -q -- wlp2s4"
[Sat Jun  3 19:28:54 2017] LoadPin: kernel-module old-api-pinning-ignored obj=<unknown> pid=9223 cmdline="/sbin/modprobe -q -- wlp2s4"
[Sat Jun  3 19:28:54 2017] LoadPin: kernel-module old-api-pinning-ignored obj=<unknown> pid=9222 cmdline="/sbin/modprobe -q -- wlp2s4"
[Sat Jun  3 19:28:54 2017] LoadPin: kernel-module old-api-pinning-ignored obj=<unknown> pid=9222 cmdline="/sbin/modprobe -q -- wlp2s4"
[Sat Jun  3 19:28:54 2017] LoadPin: kernel-module old-api-pinning-ignored obj=<unknown> pid=9223 cmdline="/sbin/modprobe -q -- wlp2s4"
[Sat Jun  3 19:28:54 2017] LoadPin: firmware pinning-ignored obj="/lib/firmware/ipw2200-bss.fw" pid=9222 cmdline="/sbin/modprobe -q -- wlp2s4"
[Sat Jun  3 19:28:54 2017] ipw2200 0000:02:04.0 wlp2s4: renamed from eth1
[Sat Jun  3 19:29:17 2017] ipw2200 0000:02:04.0 wlp2s4: renamed from eth1
[Sat Jun  3 19:29:17 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:29:17 2017] wlp2s4: Setting MAC to e2:7b:06:ec:f2:02
[Sat Jun  3 19:29:17 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:29:18 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:29:43 2017] wlp2s4: Setting MAC to 00:16:6f:61:a0:2d
[Sat Jun  3 19:29:43 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:29:43 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:29:44 2017] wlp2s4: Setting MAC to 8a:29:b8:2f:83:70
[Sat Jun  3 19:29:44 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:29:44 2017] wlp2s4: Setting MAC to 8a:29:b8:2f:83:70
[Sat Jun  3 19:29:44 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:30:00 2017] wlp2s4: Setting MAC to 00:16:6f:61:a0:2d
[Sat Jun  3 19:30:00 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:30:01 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:30:01 2017] wlp2s4: Setting MAC to 46:8e:dd:18:e4:b1
[Sat Jun  3 19:30:01 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:30:01 2017] wlp2s4: Setting MAC to 46:8e:dd:18:e4:b1
[Sat Jun  3 19:30:01 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:30:11 2017] wlp2s4: Setting MAC to 00:16:6f:61:a0:2d
[Sat Jun  3 19:30:11 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:30:11 2017] wlp2s4: Setting MAC to 12:77:99:fd:f2:41
[Sat Jun  3 19:30:11 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:30:11 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:30:12 2017] wlp2s4: Setting MAC to 12:77:99:fd:f2:41
[Sat Jun  3 19:30:12 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:36:07 2017] wlp2s4: Setting MAC to ee:2e:9e:6e:b7:68
[Sat Jun  3 19:36:07 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:36:07 2017] wlp2s4: Setting MAC to ee:2e:9e:6e:b7:68
[Sat Jun  3 19:36:07 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:40:02 2017] wlp2s4: Setting MAC to 00:16:6f:61:a0:2d
[Sat Jun  3 19:40:02 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:40:02 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:40:02 2017] wlp2s4: Setting MAC to 4e:83:c9:37:ec:a1
[Sat Jun  3 19:40:03 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:40:03 2017] wlp2s4: Setting MAC to 4e:83:c9:37:ec:a1
[Sat Jun  3 19:40:03 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:40:07 2017] wlp2s4: Setting MAC to 00:16:6f:61:a0:2d
[Sat Jun  3 19:40:07 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:40:08 2017] wlp2s4: Setting MAC to e2:d9:78:6b:40:f0
[Sat Jun  3 19:40:08 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:40:08 2017] wlp2s4: Setting MAC to e2:d9:78:6b:40:f0
[Sat Jun  3 19:40:08 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:40:08 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:40:54 2017] wlp2s4: Setting MAC to 00:16:6f:61:a0:2d
[Sat Jun  3 19:40:54 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:40:54 2017] wlp2s4: Setting MAC to ca:62:13:8e:9b:47
[Sat Jun  3 19:40:55 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:40:55 2017] wlp2s4: Setting MAC to ca:62:13:8e:9b:47
[Sat Jun  3 19:40:55 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:40:55 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:46:37 2017] wlp2s4: Setting MAC to 86:a5:24:a7:99:d6
[Sat Jun  3 19:46:37 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:46:37 2017] wlp2s4: Setting MAC to 86:a5:24:a7:99:d6
[Sat Jun  3 19:46:37 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:51:53 2017] wlp2s4: Setting MAC to 3e:f3:9e:ea:19:bf
[Sat Jun  3 19:51:53 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:51:53 2017] wlp2s4: Setting MAC to 3e:f3:9e:ea:19:bf
[Sat Jun  3 19:51:53 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:57:09 2017] wlp2s4: Setting MAC to 4a:9f:45:13:f7:1c
[Sat Jun  3 19:57:09 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[Sat Jun  3 19:57:09 2017] wlp2s4: Setting MAC to 4a:9f:45:13:f7:1c
[Sat Jun  3 19:57:09 2017] IPv6: ADDRCONF(NETDEV_UP): wlp2s4: link is not ready
[root@new-host-4 giorgio]# 

Grazie

Cercando in rete pare che il firmware che ti ho segnalato è ormai deprecato in favore di iwlwifi.
Prova a rimuovere e disinstallare il firmware precedente e vedere se il nuovo funziona. Il nome del pacchetto dovrebbe essere iwlwifi-agn-ucode.

il pacchetto iwlwifi-agn-ucode è gia installato in OpenMandriva, ho tolto quindi ipw2200 e ora provo a reinizializzare per vedere se il wifi si abilita. Se era già installato vuoi dire che erano in conflitto i due firmware??

Asap

Grazie

Al momento non riesco. Senza il pacchetto ipw2200 l’interfaccia wireless non si attiva e non vedo le sorgenti Wi-Fi. Ho provato con drakconf a settare una nuova interfaccia wireless ma mi ritorna ad installare il firmware ipw2200.
Mi piacerebbe provare a inizializzare con una live per vedere che cosa mi abilità e che modulo carica ma inizializzare con la live non è facile dati i numerosi tentativi precedenti andati male.
Vi farò sapere. Se hai altre info sempre ben accette.
Grazie Mandian

Non usare drakconf per configurare la rete. Per quanto ne so è un pacchetto vecchio ed in via di sostituzione (leggi: può scrivere delle configurazioni sbagliate al giorno d’oggi). Per quanto riguarda i consigli se prova i comandi di prima con il nuovo firmware. Soprattutto controlla che la scheda si visibile per Network Manager (indipendentemente dalla connessione) e controlla gli errori del kernel come sopra.

Ok. Network manager intendi il programma di Config dell’interfaccia grafica no?
Dalla barra dei comandi vedo solo l’interfaccia wired Ethernet mentre la Wi-Fi non la vedo più e quindi non posso tentare di collegarla.
Nel frattempo ho inserito il cd della ISO i586 32 lx3.00 e al secondo tentativo mi è partito.
Ho dato la passkey del mio Wi-Fi e si e collegato con il vecchio firmware. Anche con la live ho visto che tutti e due i firmware sono installati. Una cosa in più ho dovuto fare ho dato la password di Kvallet che viene chiesta ogni volta che si inserisce una chiave come appunto nel caso della chiave Wi-Fi. Invece nella omv reale io ho disabilitato kvallet xche continuava a chiedermi la password sempre e in continuazione, dato che il Wi-Fi non si collegava. Che sia li problema??
coss ne pensi??
Sempre grazie.
Giorgio.

Penso di no. Non ho mai usato KWallet e non ho problemi col wifi.

Prova a vedere quale dei moduli usa quando funziona. Lo puoi verificare con lspci -v: in genere l’utima roge per ongi dispositivo è Kernel driver in use.

Allora dovresti trovare gli errori del kernel.

1 Like

Ecco l’output del comando con la live e il wifi abiliato
02:04.0 Network controller: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05)
Subsystem: Hewlett-Packard Company nc6120/nx8220/nw8240
Flags: bus master, medium devsel, latency 64, IRQ 21
Memory at d0000000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [dc] Power Management version 2
Kernel driver in use: ipw2200
Kernel modules: ipw2200
[root@new-host-2 live]# lsmod |grep ipw
ipw2200 122880 0
libipw 32768 1 ipw2200
lib80211 16384 2 lib80211_crypt_tkip,libipw
cfg80211 397312 2 libipw,ipw2200

[root@new-host-2 live]# lsmod |grep iwlwifi
[root@new-host-2 live]#

ho visto che ho i due firmware installati ma sembra che il modulo che viene usato è ipw2200 come si vede da lsmod riportato sopra

[root@new-host-2 live]# rpm -qa |grep iwl
iwlwifi-agn-ucode-20160614-1-omv2015.0.noarch
[root@new-host-2 live]# rpm -qa |grep ipw
ipw2200-firmware-3.1-5-omv2015.0.noarch
ipw2100-firmware-1.3-7-omv2015.0.noarch
[root@new-host-2 live]#

[root@new-host-2 live]# nmcli c
NAME UUID TYPE DEVICE
FASTWEB-1-gsBjf48sgBil 1ccbbb9d-4852-4619-aed2-c567c2664808 802-11-wireless wlp2s4
System eth0 5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03 802-3-ethernet –
System wlan0 113f1f4e-535e-c25b-8849-2c6f770a6501 802-3-ethernet –
[root@new-host-2 live]# nmcli d
DEVICE TYPE STATE CONNECTION
wlp2s4 wifi connected FASTWEB-1-gsBjf48sgBil
eth1 ethernet disconnected –
lo loopback unmanaged –

Cosa ne pensi?? Vorrei vedere che aggiornamento è il file del driver ipw2200 che invece ho onstallato nella versione installata ed aggiornata dei pacchetti alla 3.02.
e poi vorrei vedere che errori mi d il kernel come dici Tu
Grazie
Ciao
Giorgio

solo per curiosità, cosa dice il comando

$ rfkill list

?

sono quindi tornato sulla versione installata di OpenMandriva i586 32 lx 3.02 senza il firmware ipw2200 e con il firmware iwlwifi del quale ho dovuto avviare il modulo con modprobe
ora ho in pancia i seguenti moduli wifi:
[root@localhost giorgio]# lsmod |grep iwl
iwlwifi 151552 0
cfg80211 516096 1 iwlwifi
Purtroppo non conosco per nulla il comando network-manager e con nmcli non riesco a fare più di tanto e non riesco ad attivare l’interfaccia wifi.
Se invece da plasma utilizzo i programmi di configurazione di una nuova connessione e vado ad aggiungere una connessione wifi mi va a richiedere la reinstallazione del firmware ipw2200 cioè il vecchio firmware…

[root@localhost giorgio]# nmcli radio wifi on
[root@localhost giorgio]#
[root@localhost giorgio]# nmcli c
NAME UUID TYPE DEVICE
System eth0 5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03 802-3-ethernet eth0

[root@localhost giorgio]# nmcli -p -f general,wifi-properties
eth0: connected to System eth0
“Broadcom Limited BCM4401-B0 100Base-TX (NX6110/NC6120)”
ethernet (b44), 00:15:60:B7:32:D5, hw, mtu 1500
ip4 default
inet4 192.168.1.137/24
inet4 192.168.1.130/24
inet6 fe80::215:60ff:feb7:32d5/64

lo: unmanaged
loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536

DNS configuration:
servers: 62.101.93.101 83.103.25.250
domains: fastwebnet.it
interface: eth0

[root@localhost giorgio]# nmcli radio wifi
enabled

più di cosi non riesco ma non è sufficiente.

ecco per Bruno che ringrazio il comando richiesto

[root@localhost giorgio]# rfkill list
0: hp-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no

ecco il kernel
LoadPin: kernel-module old-api-pinning-ignored obj= pid=3798 cmdline="/sbin/modprobe fuse"
[Sun Jun 4 14:56:06 2017] fuse init (API version 7.26)
[Sun Jun 4 15:00:27 2017] LoadPin: kernel-module old-api-pinning-ignored obj= pid=4312 cmdline=“modprobe iwlwifi”
[Sun Jun 4 15:00:27 2017] Intel® Wireless WiFi driver for Linux
[Sun Jun 4 15:00:27 2017] Copyright© 2003- 2015 Intel Corporation
[Sun Jun 4 21:24:56 2017] b44 ssb0:0 eth0: Link is up at 100 Mbps, full duplex
[Sun Jun 4 21:24:56 2017] b44 ssb0:0 eth0: Flow control is off for TX and off for RX
[Sun Jun 4 21:24:56 2017] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[Sun Jun 4 21:30:28 2017] LoadPin: kernel-module old-api-pinning-ignored obj= pid=6521 cmdline=“modprobe iwlwifi”
[Sun Jun 4 21:30:28 2017] Intel® Wireless WiFi driver for Linux
[Sun Jun 4 21:30:28 2017] Copyright© 2003- 2015 Intel Corporation
[Sun Jun 4 21:31:11 2017] lib80211_crypt: unregistered algorithm ‘NULL’

dal lato fisico il led blu del wifi non da più segni di vita da quando ho disinstallato il vecchio firmware non so. vorrei provare a reinstallare il vecchio firmware ed ad accertarmi che il nuovo non sia caricato come modulo per vedere se per caso si disturbano a vicenda. tutto per il fatto che nella live il vecchio firmware sembra andare bene.
Provo a fare queste prove e poi Vi dico

Grazie
Giorgio

È:

networkmanager-applet-1.0.10-1-omv2015.0.i586

installato? Non ho potuto ottenere wifi per lavorare in LXQt desktop senza di esso.

1 Like