Connexion ethernet impossible après nouvelle installation

[marceline]

Bonjour,

Mon problème :

Je viens d'installer Linux Mint 22.1 sur le PC de mon beau-père (avant sous windows)
Les paramètres réseaux indique que le PC est connecté sur le réseau ethernet, mais l'accès à internet reste impossible.

ce que j'ai déjà essayé (sans succès, donc) :
https://www.reddit.com/r/linuxmint/comm ... _mint_221/

Infos utiles :
Ce PC n'a a priori pas de carte wifi ni bluetooth, donc ethernet est le seul moyen de connection.
La connection ethernet marchait impec sous windows, avant l'installation.

Code : Tout sélectionner

ean@jean-System-Product-Name:~$ sudo lshw -C network
  *-network                 
       description: Ethernet interface
       produit: RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller
       fabricant: Realtek Semiconductor Co., Ltd.
       identifiant matériel: 0
       information bus: pci@0000:03:00.0
       nom logique: enp3s0
       version: 09
       numéro de série: 08:60:6e:d5:8f:35
       taille: 100Mbit/s
       capacité: 1Gbit/s
       bits: 64 bits
       horloge: 33MHz
       fonctionnalités: 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=6.8.0-51-generic duplex=full firmware=rtl8168f-1_0.0.5 06/18/12 ip=192.168.0.100 latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s
       ressources : irq:16 portE/S:e000(taille=256) mémoire:f0004000-f0004fff mémoire:f0000000-f0003fff

Code : Tout sélectionner

jean@jean-System-Product-Name:~$ sudo lshw -C network
  *-network                 
       description: Ethernet interface
       produit: RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller
       fabricant: Realtek Semiconductor Co., Ltd.
       identifiant matériel: 0
       information bus: pci@0000:03:00.0
       nom logique: enp3s0
       version: 09
       numéro de série: 08:60:6e:d5:8f:35
       taille: 100Mbit/s
       capacité: 1Gbit/s
       bits: 64 bits
       horloge: 33MHz
       fonctionnalités: 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=6.8.0-51-generic duplex=full firmware=rtl8168f-1_0.0.5 06/18/12 ip=192.168.0.100 latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s
       ressources : irq:16 portE/S:e000(taille=256) mémoire:f0004000-f0004fff mémoire:f0000000-f0003fff

Log du networkmanager :

Code : Tout sélectionner

Networkmanager log
sept. 12 18:05:48 jean-System-Product-Name systemd[1]: Starting NetworkManager.service - Network Manager...
sept. 12 18:05:50 jean-System-Product-Name NetworkManager[772]: <info>  [1757693149.9554] NetworkManager (version 1.46.0) is starting... (boot:5196d30a-8c31-4026-a060-a759e0297da7)
sept. 12 18:05:50 jean-System-Product-Name NetworkManager[772]: <info>  [1757693150.3142] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 20-connectivity-ubuntu.>
sept. 12 18:05:50 jean-System-Product-Name NetworkManager[772]: <info>  [1757693150.5373] manager[0x55ccbfdf3760]: monitoring kernel firmware directory '/lib/firmware'.
sept. 12 18:05:50 jean-System-Product-Name NetworkManager[772]: <info>  [1757693150.5374] monitoring ifupdown state file '/run/network/ifstate'.
sept. 12 18:05:50 jean-System-Product-Name NetworkManager[772]: <info>  [1757693150.7120] hostname: hostname: using hostnamed
sept. 12 18:05:50 jean-System-Product-Name NetworkManager[772]: <info>  [1757693150.7120] hostname: static hostname changed from (none) to "jean-System-Product-Name"
sept. 12 18:05:50 jean-System-Product-Name NetworkManager[772]: <info>  [1757693150.7781] dns-mgr: init: dns=systemd-resolved rc-manager=unmanaged (auto), plugin=systemd-resolved
sept. 12 18:05:50 jean-System-Product-Name NetworkManager[772]: <info>  [1757693150.7860] manager[0x55ccbfdf3760]: rfkill: Wi-Fi hardware radio set enabled
sept. 12 18:05:50 jean-System-Product-Name NetworkManager[772]: <info>  [1757693150.7861] manager[0x55ccbfdf3760]: rfkill: WWAN hardware radio set enabled
sept. 12 18:05:50 jean-System-Product-Name NetworkManager[772]: <info>  [1757693150.8723] Loaded device plugin: NMWifiFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.46.0/libnm-device-plugin>
sept. 12 18:05:50 jean-System-Product-Name NetworkManager[772]: <info>  [1757693150.8801] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.46.0/libnm-device-plugin>
sept. 12 18:05:50 jean-System-Product-Name NetworkManager[772]: <info>  [1757693150.9653] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.46.0/libnm-device-plugi>
sept. 12 18:05:50 jean-System-Product-Name NetworkManager[772]: <info>  [1757693150.9660] Loaded device plugin: NMAtmManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.46.0/libnm-device-plugin->
sept. 12 18:05:51 jean-System-Product-Name NetworkManager[772]: <info>  [1757693151.1582] Loaded device plugin: NMTeamFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.46.0/libnm-device-plugin>
sept. 12 18:05:51 jean-System-Product-Name NetworkManager[772]: <info>  [1757693151.1590] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
sept. 12 18:05:51 jean-System-Product-Name NetworkManager[772]: <info>  [1757693151.1592] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
sept. 12 18:05:51 jean-System-Product-Name NetworkManager[772]: <info>  [1757693151.1594] manager: Networking is enabled by state file
sept. 12 18:05:51 jean-System-Product-Name NetworkManager[772]: <info>  [1757693151.2731] settings: Loaded settings plugin: ifupdown ("/usr/lib/x86_64-linux-gnu/NetworkManager/1.46.0/libnm-setti>
sept. 12 18:05:51 jean-System-Product-Name NetworkManager[772]: <info>  [1757693151.2731] settings: Loaded settings plugin: keyfile (internal)
sept. 12 18:05:51 jean-System-Product-Name NetworkManager[772]: <info>  [1757693151.2732] ifupdown: management mode: unmanaged
sept. 12 18:05:51 jean-System-Product-Name NetworkManager[772]: <info>  [1757693151.3170] ifupdown: interfaces file /etc/network/interfaces doesn't exist
sept. 12 18:05:58 jean-System-Product-Name NetworkManager[772]: <info>  [1757693158.4871] dhcp: init: Using DHCP client 'internal'
sept. 12 18:05:58 jean-System-Product-Name NetworkManager[772]: <info>  [1757693158.4875] manager: (lo): new Loopback device (/org/freedesktop/NetworkManager/Devices/1)
sept. 12 18:05:58 jean-System-Product-Name NetworkManager[772]: <info>  [1757693158.4890] device (lo): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'exte>
sept. 12 18:05:58 jean-System-Product-Name NetworkManager[772]: <info>  [1757693158.4895] device (lo): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'e>
sept. 12 18:05:58 jean-System-Product-Name NetworkManager[772]: <info>  [1757693158.4901] device (lo): Activation: starting connection 'lo' (213a112c-69da-4758-9be9-edb862f17050)
sept. 12 18:05:58 jean-System-Product-Name NetworkManager[772]: <info>  [1757693158.4910] manager: (enp3s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
sept. 12 18:05:58 jean-System-Product-Name NetworkManager[772]: <info>  [1757693158.4914] device (enp3s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
sept. 12 18:05:59 jean-System-Product-Name NetworkManager[772]: <info>  [1757693159.0432] failed to open /run/network/ifstate
sept. 12 18:05:59 jean-System-Product-Name systemd[1]: Started NetworkManager.service - Network Manager.
sept. 12 18:05:59 jean-System-Product-Name NetworkManager[772]: <info>  [1757693159.0445] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
sept. 12 18:05:59 jean-System-Product-Name NetworkManager[772]: <warn>  [1757693159.0449] dns-mgr: update-pending changed: DNS plugin did not become ready again. Assume something is wrong
sept. 12 18:05:59 jean-System-Product-Name NetworkManager[772]: <info>  [1757693159.0455] device (lo): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
sept. 12 18:05:59 jean-System-Product-Name NetworkManager[772]: <info>  [1757693159.0461] device (lo): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
sept. 12 18:05:59 jean-System-Product-Name NetworkManager[772]: <info>  [1757693159.0463] device (lo): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
sept. 12 18:05:59 jean-System-Product-Name NetworkManager[772]: <info>  [1757693159.0472] device (lo): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
sept. 12 18:05:59 jean-System-Product-Name NetworkManager[772]: <info>  [1757693159.0491] modem-manager: ModemManager available
sept. 12 18:05:59 jean-System-Product-Name NetworkManager[772]: <info>  [1757693159.2332] device (lo): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
sept. 12 18:05:59 jean-System-Product-Name NetworkManager[772]: <info>  [1757693159.2337] device (lo): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
sept. 12 18:05:59 jean-System-Product-Name NetworkManager[772]: <info>  [1757693159.2349] device (lo): Activation: successful, device activated.
sept. 12 18:06:01 jean-System-Product-Name NetworkManager[772]: <info>  [1757693161.8671] device (enp3s0): carrier: link connected
sept. 12 18:06:01 jean-System-Product-Name NetworkManager[772]: <info>  [1757693161.8677] device (enp3s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: '>
sept. 12 18:06:01 jean-System-Product-Name NetworkManager[772]: <info>  [1757693161.8688] policy: auto-activating connection 'Connexion filaire 1' (c504fe23-1d34-3817-bc6f-0c9aa01be6e0)
sept. 12 18:06:01 jean-System-Product-Name NetworkManager[772]: <info>  [1757693161.8696] device (enp3s0): Activation: starting connection 'Connexion filaire 1' (c504fe23-1d34-3817-bc6f-0c9aa01b>
sept. 12 18:06:01 jean-System-Product-Name NetworkManager[772]: <info>  [1757693161.8698] device (enp3s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
sept. 12 18:06:01 jean-System-Product-Name NetworkManager[772]: <info>  [1757693161.8705] manager: NetworkManager state is now CONNECTING
sept. 12 18:06:01 jean-System-Product-Name NetworkManager[772]: <info>  [1757693161.8709] device (enp3s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
sept. 12 18:06:01 jean-System-Product-Name NetworkManager[772]: <info>  [1757693161.8722] device (enp3s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
sept. 12 18:06:01 jean-System-Product-Name NetworkManager[772]: <info>  [1757693161.8731] dhcp4 (enp3s0): activation: beginning transaction (timeout in 45 seconds)
sept. 12 18:06:01 jean-System-Product-Name NetworkManager[772]: <info>  [1757693161.9347] dhcp4 (enp3s0): error parsing DHCP option 6 (domain_name_servers): address 0.0.0.0 is ignored
sept. 12 18:06:01 jean-System-Product-Name NetworkManager[772]: <info>  [1757693161.9348] dhcp4 (enp3s0): state changed new lease, address=192.168.0.100, acd pending
sept. 12 18:06:02 jean-System-Product-Name NetworkManager[772]: <info>  [1757693162.0539] dhcp4 (enp3s0): state changed new lease, address=192.168.0.100
sept. 12 18:06:02 jean-System-Product-Name NetworkManager[772]: <info>  [1757693162.0546] policy: set 'Connexion filaire 1' (enp3s0) as default for IPv4 routing and DNS
sept. 12 18:06:02 jean-System-Product-Name NetworkManager[772]: <info>  [1757693162.2172] device (enp3s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
sept. 12 18:06:02 jean-System-Product-Name NetworkManager[772]: <info>  [1757693162.2447] device (enp3s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')

Même si j'ai souvent installé Linux sur des vieux (et moins vieux) PC, je suis loin d'être une geek. Et j'ai assez peu de compréhension du fonctionnement du réseau. C'est la première fois que je rencontre ce problème. Tout aide est la bienvenue. Si besoin de plus d'infos, n'hésitez pas !

[marceline]

Et oui, mais je ne peux pas. Car ce n'est pas sur le terminal de mon PC, mais sur celui de mon beau-père - qui n'a pas accès à internet, donc

Edit : j'ai modifier en faisant un copier/coller

[marceline]

Code : Tout sélectionner

ping -c3 cbiot.fr

retour :

Code : Tout sélectionner

nom ou service inconnu

[marceline]

Salut Cyrille,

merci de t'intéresser à mon cas
On est d'accord c'est super space. Je n'ai modifié aucun paramètre (juste fait la manip indiqué dans le lien que j'ai donné)

Voici ce que retournent les commandes que tu m'as donné :

Code : Tout sélectionner

jean@jean-System-Product-Name:~$ lspci -nnd ::0280
jean@jean-System-Product-Name:~$ lspci -nnkd ::0280
jean@jean-System-Product-Name:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 08:60:6e:d5:8f:35 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.100/24 brd 192.168.0.255 scope global dynamic noprefixroute enp3s0
       valid_lft 3683sec preferred_lft 3683sec
    inet6 2a02:a03f:684f:ab00:1447:318d:804d:c571/64 scope global temporary dynamic 
       valid_lft 86376sec preferred_lft 71976sec
    inet6 2a02:a03f:684f:ab00:cb6d:c33e:d27f:8cdf/64 scope global dynamic mngtmpaddr noprefixroute 
       valid_lft 86376sec preferred_lft 71976sec
    inet6 fe80::7046:a262:9afd:1d3d/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

Code : Tout sélectionner

jean@jean-System-Product-Name:~$ sudo dmesg [ egrep 'error|fail|warn'
[sudo] Mot de passe de jean :         
dmesg: bad usage
Exécutez « dmesg --help » pour obtenir des renseignements complémentaires.

[marceline]

ah oui, là il y a plein d'"error" qui s'affichent

Code : Tout sélectionner

jean@jean-System-Product-Name:~$ sudo dmesg | egrep 'error|fail|warn'
[sudo] Mot de passe de jean :         
[    0.989315] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
[    0.990915] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT1._GTF due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
[    0.991137] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
[    0.991712] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT1._GTF due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
[ 1546.284753] sd 6:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 4456.990906] sd 6:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[11021.040356] sd 6:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
jean@jean-System-Product-Name:~$ ^C
jean@jean-System-Product-Name:~$ 

[tescan]

Bonjour,
bricolage du DHCP? Adresse fixe?
si non
DHCP de enp3s0 est bien sur "Automatique"? (Paramètres Réseau >Filaire >IPv4/IPv6

Retour de:

Code : Tout sélectionner

sudo dhclient -v enp3s0

[marceline]

@tescan Oui, on a fait des tentatives pour changer l'IP, sans succès.
Les paramètres sont de nouveaux par défault- en automatique partout

@cyrille Pendant l'install, le réseau fonctionnait très bien sur l'ordi et dans tous le reste de la maison.

[marceline]

Oui, je vais tenter ça la prochaine fois que j'y retourne.
(Et aussi essayer de changer le câble ethernet, on sait jamais)

Je vous dis quoi !