Bonjour,
Sur une LMDE (mint) toute neuve (pc tout neuf), j'ai un pb lors de la sortie de veille.
Le réseaux (eth) semble se connecter, mais je n'arrive à accéder à rien du tout. Network manager semble marcher, je peux me déconnecter et me reconnecter. Mais je n'accede toujours à rien. La carte semble active (les diodes clignotes). Je peux faire un ping sur mon address ip (mais pas de réponse si je ping le router). Alors il faut que je reboote (deconexion de X ne suffit pas)
voici quelques infos:
un log de wake
desktop NetworkManager[1299]: <info> sleep requested (sleeping: no enabled: yes)
Nov 9 08:08:24 desktop NetworkManager[1299]: <info> sleeping or disabling...
Nov 9 08:08:24 desktop NetworkManager[1299]: <info> (eth1): now unmanaged
Nov 9 08:08:24 desktop NetworkManager[1299]: <info> (eth1): device state change: 8 -> 1 (reason 37)
Nov 9 08:08:24 desktop NetworkManager[1299]: <info> (eth1): deactivating device (reason: 37).
Nov 9 08:08:24 desktop NetworkManager[1299]: <info> (eth1): canceled DHCP transaction, DHCP client pid 1342
Nov 9 08:08:24 desktop avahi-daemon[1366]: Withdrawing address record for 192.168.0.103 on eth1.
Nov 9 08:08:24 desktop avahi-daemon[1366]: Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.0.103.
Nov 9 08:08:24 desktop avahi-daemon[1366]: Interface eth1.IPv4 no longer relevant for mDNS.
Nov 9 08:08:24 desktop NetworkManager[1299]: <info> (eth1): cleaning up...
Nov 9 08:08:24 desktop NetworkManager[1299]: <info> (eth1): taking down device.
Nov 9 08:08:24 desktop avahi-daemon[1366]: Interface eth1.IPv6 no longer relevant for mDNS.
Nov 9 08:08:24 desktop avahi-daemon[1366]: Leaving mDNS multicast group on interface eth1.IPv6 with address fe80::a800:4ff:fe00:a04.
Nov 9 08:08:24 desktop avahi-daemon[1366]: Withdrawing address record for fe80::a800:4ff:fe00:a04 on eth1.
Nov 9 08:08:24 desktop NetworkManager[1299]: <info> (eth1): carrier now OFF (device state 1)
Nov 9 08:08:24 desktop dbus[1289]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Nov 9 08:08:24 desktop dbus[1289]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Nov 9 08:08:46 desktop acpid: client 1339[0:0] has disconnected
Nov 9 08:08:46 desktop acpid: client connected from 1339[0:0]
Nov 9 08:08:46 desktop acpid: 1 client rule loaded
Nov 9 08:08:47 desktop NetworkManager[1299]: <info> wake requested (sleeping: yes enabled: yes)
Nov 9 08:08:47 desktop NetworkManager[1299]: <info> waking up and re-enabling...
Nov 9 08:08:47 desktop NetworkManager[1299]: <info> WWAN now enabled by management service
Nov 9 08:08:47 desktop NetworkManager[1299]: <info> (eth1): now managed
Nov 9 08:08:47 desktop NetworkManager[1299]: <info> (eth1): device state change: 1 -> 2 (reason 2)
Nov 9 08:08:47 desktop NetworkManager[1299]: <info> (eth1): bringing up device.
Nov 9 08:08:47 desktop NetworkManager[1299]: <info> (eth1): preparing device.
Nov 9 08:08:47 desktop NetworkManager[1299]: <info> (eth1): deactivating device (reason: 2).
Nov 9 08:08:48 desktop NetworkManager[1299]: <info> (eth1): carrier now ON (device state 2)
Nov 9 08:08:48 desktop NetworkManager[1299]: <info> (eth1): device state change: 2 -> 3 (reason 40)
Nov 9 08:08:48 desktop NetworkManager[1299]: <info> Activation (eth1) starting connection 'Ethernet automatique'
Nov 9 08:08:48 desktop NetworkManager[1299]: <info> (eth1): device state change: 3 -> 4 (reason 0)
Nov 9 08:08:48 desktop NetworkManager[1299]: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Nov 9 08:08:48 desktop NetworkManager[1299]: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Nov 9 08:08:48 desktop NetworkManager[1299]: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Nov 9 08:08:48 desktop NetworkManager[1299]: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Nov 9 08:08:48 desktop NetworkManager[1299]: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Nov 9 08:08:48 desktop NetworkManager[1299]: <info> (eth1): device state change: 4 -> 5 (reason 0)
Nov 9 08:08:48 desktop NetworkManager[1299]: <info> Activation (eth1) Stage 2 of 5 (Device Configure) successful.
Nov 9 08:08:48 desktop NetworkManager[1299]: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) scheduled.
Nov 9 08:08:48 desktop NetworkManager[1299]: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Nov 9 08:08:48 desktop NetworkManager[1299]: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) started...
Nov 9 08:08:48 desktop NetworkManager[1299]: <info> (eth1): device state change: 5 -> 7 (reason 0)
Nov 9 08:08:48 desktop NetworkManager[1299]: <info> Activation (eth1) Beginning DHCPv4 transaction (timeout in 45 seconds)
Nov 9 08:08:48 desktop NetworkManager[1299]: <info> dhclient started with pid 3060
Nov 9 08:08:48 desktop NetworkManager[1299]: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) complete.
Nov 9 08:08:48 desktop dhclient: Internet Systems Consortium DHCP Client 4.1.1-P1
Nov 9 08:08:48 desktop dhclient: Copyright 2004-2010 Internet Systems Consortium.
Nov 9 08:08:48 desktop dhclient: All rights reserved.
Nov 9 08:08:48 desktop dhclient: For info, please visit https://www.isc.org/software/dhcp/
Nov 9 08:08:48 desktop dhclient:
Nov 9 08:08:48 desktop NetworkManager[1299]: <info> (eth1): DHCPv4 state changed nbi -> preinit
Nov 9 08:08:48 desktop dhclient: Listening on LPF/eth1/aa:00:04:00:0a:04
Nov 9 08:08:48 desktop dhclient: Sending on LPF/eth1/aa:00:04:00:0a:04
Nov 9 08:08:48 desktop dhclient: Sending on Socket/fallback
Nov 9 08:08:49 desktop dhclient: DHCPREQUEST on eth1 to 255.255.255.255 port 67
Nov 9 08:08:49 desktop dhclient: DHCPACK from 192.168.0.1
Nov 9 08:08:50 desktop NetworkManager[1299]: <info> (eth1): DHCPv4 state changed preinit -> reboot
Nov 9 08:08:50 desktop NetworkManager[1299]: <info> Activation (eth1) Stage 4 of 5 (IP4 Configure Get) scheduled...
Nov 9 08:08:50 desktop dhclient: bound to 192.168.0.103 -- renewal in 570691 seconds.
Nov 9 08:08:50 desktop NetworkManager[1299]: <info> Activation (eth1) Stage 4 of 5 (IP4 Configure Get) started...
Nov 9 08:08:50 desktop NetworkManager[1299]: <info> address 192.168.0.103
Nov 9 08:08:50 desktop NetworkManager[1299]: <info> prefix 24 (255.255.255.0)
Nov 9 08:08:50 desktop NetworkManager[1299]: <info> gateway 192.168.0.1
Nov 9 08:08:50 desktop NetworkManager[1299]: <info> nameserver '180.168.255.18'
Nov 9 08:08:50 desktop NetworkManager[1299]: <info> nameserver '192.168.0.1'
Nov 9 08:08:50 desktop NetworkManager[1299]: <info> Scheduling stage 5
Nov 9 08:08:50 desktop NetworkManager[1299]: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) scheduled...
Nov 9 08:08:50 desktop NetworkManager[1299]: <info> Done scheduling stage 5
Nov 9 08:08:50 desktop NetworkManager[1299]: <info> Activation (eth1) Stage 4 of 5 (IP4 Configure Get) complete.
Nov 9 08:08:50 desktop NetworkManager[1299]: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) started...
Nov 9 08:08:50 desktop avahi-daemon[1366]: Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.0.103.
Nov 9 08:08:50 desktop avahi-daemon[1366]: New relevant interface eth1.IPv4 for mDNS.
Nov 9 08:08:50 desktop avahi-daemon[1366]: Registering new address record for 192.168.0.103 on eth1.IPv4.
Nov 9 08:08:50 desktop avahi-daemon[1366]: Joining mDNS multicast group on interface eth1.IPv6 with address fe80::a800:4ff:fe00:a04.
Nov 9 08:08:50 desktop avahi-daemon[1366]: New relevant interface eth1.IPv6 for mDNS.
Nov 9 08:08:50 desktop avahi-daemon[1366]: Registering new address record for fe80::a800:4ff:fe00:a04 on eth1.*.
Nov 9 08:08:51 desktop NetworkManager[1299]: <info> (eth1): device state change: 7 -> 8 (reason 0)
Nov 9 08:08:51 desktop NetworkManager[1299]: <info> Policy set 'Ethernet automatique' (eth1) as default for IPv4 routing and DNS.
Nov 9 08:08:51 desktop NetworkManager[1299]: <info> Activation (eth1) successful, device activated.
Nov 9 08:08:51 desktop NetworkManager[1299]: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) complete.
Nov 9 08:08:51 desktop dbus[1289]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Nov 9 08:08:51 desktop dbus[1289]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
et des infos sur la carte et la config
```console
desktop nous # ifconfig
eth1 Link encap:Ethernet HWaddr aa:00:04:00:0a:04
inet adr:192.168.0.103 Bcast:192.168.0.255 Masque:255.255.255.0
adr inet6: fe80::a800:4ff:fe00:a04/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:45939 errors:0 dropped:0 overruns:0 frame:0
TX packets:34714 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
RX bytes:59702376 (56.9 MiB) TX bytes:4331159 (4.1 MiB)
Interruption:42 Adresse de base:0xe000
lo Link encap:Boucle locale
inet adr:127.0.0.1 Masque:255.0.0.0
adr inet6: ::1/128 Scope:Hôte
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2041 errors:0 dropped:0 overruns:0 frame:0
TX packets:2041 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:73268 (71.5 KiB) TX bytes:73268 (71.5 KiB)
driver carte : r8169
```
Si quelqu'un avait des pistes à me donner, ce serait cool…
# Sortie d'hibernation ou de sommeil difficile...
Posté par JoeltheLion (site web personnel) . Évalué à 5.
Fais toi un café!
[] <--------
# carte reseau, module et mise en veille
Posté par NeoX . Évalué à 3.
essaye en desactivant/reactivant, à la main, le module de ta carte reseau quand tu reviens de veille.
si ca marche, regarde sur le net, pour desactiver le module avant la mise en veille et le reactiver apres (quelques lignes à mettre dans un script ou deux)
[^] # Re: carte reseau, module et mise en veille
Posté par FDF (site web personnel) . Évalué à 0.
J'essaye ca quand je rentre a la maison...
Merci
[^] # Re: carte reseau, module et mise en veille
Posté par FDF (site web personnel) . Évalué à 0.
MERCI !
C'était la solution!
En fait je ne connaissais pas la commande rmmod. J'avais toujours eu des problèmes de pilote non chargé. Pas de pilote a supprimer...
[^] # Re: carte reseau, module et mise en veille
Posté par NeoX . Évalué à 2.
rmmod est un alias pour modprobe -r
Suivre le flux des commentaires
Note : les commentaires appartiennent à celles et ceux qui les ont postés. Nous n’en sommes pas responsables.