[Buster] - Messages d'erreurs au lancement

Hello,

Je cherche à résoudre les différents messages d’erreur qui apparaissent au lancement de Buster…
Si un expert sur le sujet pouvait jeter un coup d’œil dessus, et m’indiquer quoi faire ce serait cool!
Mais je ne lâche pas l’affaire de mon coté !
Merci d’avance.

Voici le journal que j’ai récupéré au lancement :

juin 09 17:05:58 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:05:58 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:05:58 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:03:25 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:03:25 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:03:25 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:03:25 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:03:24 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:03:24 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:03:24 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:03:24 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:03:24 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:03:24 NetworkManager[517]: ((src/settings/nm-settings-connect
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:05:48 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:03:25 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:03:25 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:03:25 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:03:25 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:03:24 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:03:24 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:03:24 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:03:24 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:03:24 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:03:24 NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
juin 09 17:03:24 systemd[1]: Failed to start keep memory of all UPnP devices that announced themselves.
juin 09 17:03:24 minissdpd[876]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
juin 09 17:03:21 wpa_supplicant[507]: bgscan simple: Failed to enable signal strength monitoring
juin 09 17:03:16 NetworkManager[517]: ((src/settings/nm-settings.c:899)): assertion '<dropped>' failed
juin 09 17:03:16 systemd[1]: Failed to start Raise network interfaces.
juin 09 17:03:16 dhclient[623]: exiting.
juin 09 17:03:16 dhclient[623]: 
juin 09 17:03:16 dhclient[623]: process and the information we find helpful for debugging.
juin 09 17:03:16 dhclient[623]: before submitting a bug.  These pages explain the proper
juin 09 17:03:16 dhclient[623]: bugs on either our web page at www.isc.org or in the README file
juin 09 17:03:16 dhclient[623]: than a configuration issue please read the section on submitting
juin 09 17:03:16 dhclient[623]: If you think you have received this message due to a bug rather
juin 09 17:03:16 dhclient[623]: 
juin 09 17:03:16 dhclient[623]: Failed to get interface index: No such device
juin 09 17:03:15 bluetoothd[508]: sap-server: Operation not permitted (1)
juin 09 17:03:15 bluetoothd[508]: Sap driver initialization failed.
juin 09 17:03:15 avahi-daemon[630]: chroot.c: open() failed: No such file or directory
juin 09 17:03:09 kernel: uvcvideo: Failed to query (GET_DEF) UVC control 8 on unit 1: -32 (exp. 1).
juin 09 17:03:09 kernel: uvcvideo: Failed to query (GET_DEF) UVC control 8 on unit 1: -32 (exp. 1).
juin 09 17:03:08 kernel: uvcvideo: Failed to query (GET_INFO) UVC control 8 on unit 1: -32 (exp. 1).
juin 09 17:03:07 kernel: kvm: disabled by bios
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:06 kernel: pstore: decompression failed: -22
juin 09 17:03:06 kernel: pstore: crypto_comp_decompress failed, ret = -22!
juin 09 17:03:04 systemd[1]: network.target: Job networking-routes.service/start deleted to break ordering cycle starting with network.target
juin 09 17:03:04 kernel: do_IRQ: 3.55 No irq handler for vector
juin 09 17:03:04 kernel: do_IRQ: 2.55 No irq handler for vector
juin 09 17:03:04 kernel: do_IRQ: 1.55 No irq handler for vector

1 - Les informations de la distribution installée

Debian 10.0
4.19.0-5-amd64 #1 SMP Debian 4.19.37-3 (2019-05-15) x86_64 GNU/Linux

2 - Les informations du matériel

dmidecode -q

Résultat:

BIOS Information
	Vendor: Insyde
	Version: F.1F
	Release Date: 12/01/2015
	Address: 0xE0000
	Runtime Size: 128 kB
	ROM Size: 4096 kB
	Characteristics:
		PCI is supported
		BIOS is upgradeable
		BIOS shadowing is allowed
		Boot from CD is supported
		Selectable boot is supported
		BIOS ROM is socketed
		EDD is supported
		Japanese floppy for NEC 9800 1.2 MB is supported (int 13h)
		Japanese floppy for Toshiba 1.2 MB is supported (int 13h)
		5.25"/360 kB floppy services are supported (int 13h)
		5.25"/1.2 MB floppy services are supported (int 13h)
		3.5"/720 kB floppy services are supported (int 13h)
		3.5"/2.88 MB floppy services are supported (int 13h)
		8042 keyboard services are supported (int 9h)
		CGA/mono video services are supported (int 10h)
		ACPI is supported
		USB legacy is supported
		Targeted content distribution is supported
		UEFI is supported
	BIOS Revision: 15.31
	Firmware Revision: 99.45

System Information
	Manufacturer: Hewlett-Packard
	Product Name: HP Notebook
	Version: Type1ProductConfigId
	Serial Number: CND5267PGC
	UUID: 6d9383a4-f51a-e511-a26a-5820b167894f
	Wake-up Type: Power Switch
	SKU Number: N0L65EA#ABF
	Family: 103C_5335KV G=N L=CON B=HP

Base Board Information
	Manufacturer: Hewlett-Packard
	Product Name: 8137
	Version: 99.45
	Serial Number: PFHTKD2WV8VRQM
	Asset Tag: Base Board Asset Tag
	Features:
		Board is a hosting board
		Board is replaceable
	Location In Chassis: Base Board Chassis Location
	Type: Motherboard

Chassis Information
	Manufacturer: Hewlett-Packard
	Type: Notebook
	Lock: Not Present
	Version: Chassis Version
	Serial Number: Chassis Serial Number
	Asset Tag: Chassis Asset Tag
	Boot-up State: Safe
	Power Supply State: Safe
	Thermal State: Safe
	Security Status: None
	OEM Information: 0x0000010E
	Height: Unspecified
	Number Of Power Cords: 1
	Contained Elements: 0
	SKU Number: Not Specified

System Slot Information
	Designation: J3606
	Type: x2 PCI Express 2 x2
	Current Usage: Available
	Length: Short
	ID: 1
	Characteristics:
		3.3 V is provided
		PME signal is supported
		Hot-plug devices are supported
	Bus Address: 0000:00:02.0

System Slot Information
	Designation: J3703
	Type: x1 PCI Express x1
	Current Usage: Available
	Length: Short
	ID: 2
	Characteristics:
		3.3 V is provided
		PME signal is supported
		Hot-plug devices are supported
	Bus Address: 0000:00:04.0

System Slot Information
	Designation: J3700
	Type: x1 PCI Express x1
	Current Usage: Available
	Length: Short
	ID: 3
	Characteristics:
		3.3 V is provided
		PME signal is supported
		Hot-plug devices are supported
	Bus Address: 0000:00:05.0

System Slot Information
	Designation: J3701
	Type: x1 PCI Express x1
	Current Usage: Available
	Length: Short
	ID: 4
	Characteristics:
		3.3 V is provided
		PME signal is supported
		Hot-plug devices are supported
	Bus Address: 0000:00:06.0

System Slot Information
	Designation: J2500
	Type: x1 PCI Express x1
	Current Usage: Available
	Length: Short
	ID: 4
	Characteristics:
		3.3 V is provided
		PME signal is supported
		Hot-plug devices are supported
	Bus Address: 0000:00:07.0

System Slot Information
	Designation: J615
	Type: 32-bit PC-98/Card
	Current Usage: Available
	Length: Long
	Characteristics:
		5.0 V is provided
		3.3 V is provided
		Cardbus is supported
		Modem ring resume is supported
		PME signal is supported
		SMBus signal is supported
	Bus Address: 0000:00:14.7

OEM Strings
	String 1: $HP$
	String 2: LOC#ABA
	String 3: ABS 70/71 78 79 7A 7B
	String 4: String4 for Original Equipment Manufacturer
	String 5: HP_Mute_LED_0_A
	String 6: String6 for Original Equipment Manufacturer
	String 7: String7 for Original Equipment Manufacturer
	String 8: String8 for Original Equipment Manufacturer
	String 9: FBYTE#3Q6b7K7P7W7jaBapaqasauawbPbSbhbpbzcbce.nF;
	String 10: BUILDID#15WW2THA602#SABF#DABF;
	String 11: String11 for Original Equipment Manufacturer

BIOS Language Information
	Language Description Format: Long
	Installable Languages: 5
		en|US|iso8859-1
		fr|CA|iso8859-1
		es|ES|iso8859-1
		zh|TW|unicode
		zh|CN|unicode
	Currently Installed Language: fr|CA|iso8859-1

System Boot Information
	Status: No errors detected

Portable Battery
	Location: Primary
	Manufacturer: 13-42....
	Manufacture Date: 8/7/2018
	Serial Number: 04369 8/7/2018
	Name: HS04041
	Chemistry: Lithium Ion
	Design Capacity: 38480 mWh
	Design Voltage: 14800 mV
	SBDS Version: 1
	Maximum Error: 11%
	OEM-specific Information: 0x000C090E

Onboard Device
	Reference Designation:  
	Type: Other
	Status: Enabled
	Type Instance: 1
	Bus Address: 0000:02:00.0

Physical Memory Array
	Location: System Board Or Motherboard
	Use: System Memory
	Error Correction Type: None
	Maximum Capacity: 4 GB
	Number Of Devices: 2

Memory Device
	Total Width: Unknown
	Data Width: Unknown
	Size: No Module Installed
	Form Factor: SODIMM
	Set: None
	Locator: Bottom
	Bank Locator: CHANNEL A
	Type: Unknown
	Type Detail: Unknown
	Speed: Unknown
	Manufacturer: Empty
	Serial Number: Empty
	Asset Tag: Asset Tag: 
	Part Number: Empty
	Rank: Unknown
	Configured Memory Speed: Unknown
	Minimum Voltage: Unknown
	Maximum Voltage: Unknown
	Configured Voltage: Unknown

Memory Device
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 4096 MB
	Form Factor: SODIMM
	Set: None
	Locator: Top
	Bank Locator: CHANNEL A
	Type: DDR3
	Type Detail: Synchronous Unbuffered (Unregistered)
	Speed: 1600 MT/s
	Manufacturer: Samsung
	Serial Number: 123CD8E8
	Asset Tag: Asset Tag: 
	Part Number: M471B5173QH0-YK0  
	Rank: 1
	Configured Memory Speed: 800 MT/s
	Minimum Voltage: Unknown
	Maximum Voltage: Unknown
	Configured Voltage: Unknown

Memory Device Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x000FFFFFFFF
	Range Size: 4 GB
	Partition Row Position: 1

Memory Array Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x000FFFFFFFF
	Range Size: 4 GB
	Partition Width: 255

Processor Information
	Socket Designation: Socket FT1
	Type: Central Processor
	Family: A-Series
	Manufacturer: AMD processor
	ID: 01 0F 70 00 FF FB 8B 17
	Signature: Family 22, Model 0, Stepping 1
	Flags:
		FPU (Floating-point unit on-chip)
		VME (Virtual mode extension)
		DE (Debugging extension)
		PSE (Page size extension)
		TSC (Time stamp counter)
		MSR (Model specific registers)
		PAE (Physical address extension)
		MCE (Machine check exception)
		CX8 (CMPXCHG8 instruction supported)
		APIC (On-chip APIC hardware supported)
		SEP (Fast system call)
		MTRR (Memory type range registers)
		PGE (Page global enable)
		MCA (Machine check architecture)
		CMOV (Conditional move instruction supported)
		PAT (Page attribute table)
		PSE-36 (36-bit page size extension)
		CLFSH (CLFLUSH instruction supported)
		MMX (MMX technology supported)
		FXSR (FXSAVE and FXSTOR instructions supported)
		SSE (Streaming SIMD extensions)
		SSE2 (Streaming SIMD extensions 2)
		HTT (Multi-threading)
	Version: AMD A6-5200 APU with Radeon(TM) HD Graphics    
	Voltage: 1.3 V
	External Clock: 100 MHz
	Max Speed: 2000 MHz
	Current Speed: 2000 MHz
	Status: Populated, Enabled
	Upgrade: None
	Serial Number: NotSupport
	Asset Tag: FFFF
	Part Number: FFFF
	Core Count: 4
	Core Enabled: 4
	Thread Count: 4
	Characteristics:
		64-bit capable

Cache Information
	Socket Designation: L1 Cache
	Configuration: Enabled, Not Socketed, Level 1
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 256 kB
	Maximum Size: 256 kB
	Supported SRAM Types:
		Pipeline Burst
	Installed SRAM Type: Pipeline Burst
	Speed: 1 ns
	Error Correction Type: Multi-bit ECC
	System Type: Unified
	Associativity: 2-way Set-associative

Cache Information
	Socket Designation: L2 Cache
	Configuration: Enabled, Not Socketed, Level 2
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 2048 kB
	Maximum Size: 2048 kB
	Supported SRAM Types:
		Pipeline Burst
	Installed SRAM Type: Pipeline Burst
	Speed: 1 ns
	Error Correction Type: Multi-bit ECC
	System Type: Unified
	Associativity: 16-way Set-associative

3 - D’autres informations du matériel

dmidecode -t bios

Résultat:

# dmidecode 3.2
Getting SMBIOS data from sysfs.
SMBIOS 2.8 present.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
	Vendor: Insyde
	Version: F.1F
	Release Date: 12/01/2015
	Address: 0xE0000
	Runtime Size: 128 kB
	ROM Size: 4096 kB
	Characteristics:
		PCI is supported
		BIOS is upgradeable
		BIOS shadowing is allowed
		Boot from CD is supported
		Selectable boot is supported
		BIOS ROM is socketed
		EDD is supported
		Japanese floppy for NEC 9800 1.2 MB is supported (int 13h)
		Japanese floppy for Toshiba 1.2 MB is supported (int 13h)
		5.25"/360 kB floppy services are supported (int 13h)
		5.25"/1.2 MB floppy services are supported (int 13h)
		3.5"/720 kB floppy services are supported (int 13h)
		3.5"/2.88 MB floppy services are supported (int 13h)
		8042 keyboard services are supported (int 9h)
		CGA/mono video services are supported (int 10h)
		ACPI is supported
		USB legacy is supported
		Targeted content distribution is supported
		UEFI is supported
	BIOS Revision: 15.31
	Firmware Revision: 99.45

Handle 0x000B, DMI type 13, 22 bytes
BIOS Language Information
	Language Description Format: Long
	Installable Languages: 5
		en|US|iso8859-1
		fr|CA|iso8859-1
		es|ES|iso8859-1
		zh|TW|unicode
		zh|CN|unicode
	Currently Installed Language: fr|CA|iso8859-1

4 - Et pour finir sur le hardware

lspci

Résultat:

00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 16h Processor Root Complex
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8400 / R3 Series]
00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Kabini HDMI/DP Audio
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 16h Processor Function 0
00:02.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 16h Processor Functions 5:1
00:02.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 16h Processor Functions 5:1
00:02.5 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 16h Processor Functions 5:1
00:10.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller (rev 01)
00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode]
00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 39)
00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller (rev 39)
00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 39)
00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller (rev 39)
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 3a)
00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD] FCH Azalia Controller (rev 02)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 11)
00:14.7 SD Host controller: Advanced Micro Devices, Inc. [AMD] FCH SD Flash Controller (rev 01)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 16h Processor Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 16h Processor Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 16h Processor Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 16h Processor Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 16h Processor Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 16h Processor Function 5
02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8188EE Wireless Network Adapter (rev 01)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller (rev 07)

Et la référence de mon ordinateur Portable : PC Portable HP Notebook 15-af008nf 15.6"

1- cd /sys/fs/pstore
2- ls

retour

dmesg-efi-153087460601001.enc.z  dmesg-efi-153087460606001.enc.z  dmesg-efi-153087460611001.enc.z
dmesg-efi-153087460602001.enc.z  dmesg-efi-153087460607001.enc.z  dmesg-efi-153087460612001.enc.z
dmesg-efi-153087460603001.enc.z  dmesg-efi-153087460608001.enc.z  dmesg-efi-153087460613001.enc.z
dmesg-efi-153087460604001.enc.z  dmesg-efi-153087460609001.enc.z  dmesg-efi-153087460614001.enc.z
dmesg-efi-153087460605001.enc.z  dmesg-efi-153087460610001.enc.z

3- rm dmesg-efi*

Source : PAS MOI, recherche google trouvé sur un forum concurrent.

Cool! Ça règle ce premier message d’erreur!
Merci pour cette info!
Voici le dernier retour de la commande suivante:

sudo journalctl -p err

kernel: do_IRQ: 1.55 No irq handler for vector
kernel: do_IRQ: 2.55 No irq handler for vector
kernel: do_IRQ: 3.55 No irq handler for vector
systemd[1]: network.target: Job networking-routes.service/start deleted to break ordering cycle starting with network.target
kernel: kvm: disabled by bios
kernel: uvcvideo: Failed to query (GET_INFO) UVC control 8 on unit 1: -32 (exp. 1).
kernel: uvcvideo: Failed to query (GET_DEF) UVC control 8 on unit 1: -32 (exp. 1).
kernel: uvcvideo: Failed to query (GET_DEF) UVC control 8 on unit 1: -32 (exp. 1).
dhclient[620]: Failed to get interface index: No such device
dhclient[620]: 
dhclient[620]: If you think you have received this message due to a bug rather
dhclient[620]: than a configuration issue please read the section on submitting
dhclient[620]: bugs on either our web page at www.isc.org or in the README file
dhclient[620]: before submitting a bug.  These pages explain the proper
dhclient[620]: process and the information we find helpful for debugging.
dhclient[620]: 
dhclient[620]: exiting.
systemd[1]: Failed to start Raise network interfaces.
avahi-daemon[674]: chroot.c: open() failed: No such file or directory
bluetoothd[514]: Sap driver initialization failed.
bluetoothd[514]: sap-server: Operation not permitted (1)
NetworkManager[517]: ((src/settings/nm-settings.c:899)): assertion '<dropped>' failed
wpa_supplicant[524]: bgscan simple: Failed to enable signal strength monitoring
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed
NetworkManager[517]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed

Aux lignes suivantes dans le journal:
Failed to start Raise network interface
See 'systemctl status networking.service' for detais.

Voici le résultat pour le statut:
sudo service networking status

● networking.service - Raise network interfaces
   Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2019-06-30 07:59:43 CEST; 1h 3min ago
     Docs: man:interfaces(5)
  Process: 520 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
 Main PID: 520 (code=exited, status=1/FAILURE)

juin 30 07:59:43 robgall dhclient[621]: than a configuration issue please read the section on submitting
juin 30 07:59:43 robgall dhclient[621]: bugs on either our web page at www.isc.org or in the README file
juin 30 07:59:43 robgall dhclient[621]: before submitting a bug.  These pages explain the proper
juin 30 07:59:43 robgall dhclient[621]: process and the information we find helpful for debugging.
juin 30 07:59:43 robgall dhclient[621]: 
juin 30 07:59:43 robgall dhclient[621]: exiting.
juin 30 07:59:43 robgall ifup[520]: ifup: failed to bring up eth0
juin 30 07:59:43 robgall systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
juin 30 07:59:43 robgall systemd[1]: networking.service: Failed with result 'exit-code'.
juin 30 07:59:43 robgall systemd[1]: Failed to start Raise network interfaces.

Une idée pour corriger ce point là?

Salut
bizarre de voir eth0, normalement les règles de nommage ont changées
https://www.debian.org/releases/buster/amd64/release-notes/ch-information.en.html#migrate-interface-names
Que dit la commande

ip link

As tu inscrit eth0 en dur quelque part?

Non je n’ai rien inscrit en dur.
voici le retour de:

ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether 58:20:b1:67:89:4f brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
    link/ether d8:5d:e2:4d:d2:6f brd ff:ff:ff:ff:ff:ff

Salut,

Peut-être vérifier le fichier /etc/network/interfaces ainsi que le contenu de
/etc/network/interfaces.d/, histoire de voir s’il n’y aurait pas de références à eth0 ?

A+

Voici ce qu’il y a dans /etc/network/interfaces

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

…et dans /etc/network/interfaces.d/setup

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

Salut,

Sais-tu le pourquoi de ce fichier: /etc/network/interfaces.d/setup ?
À mon avis, tu devrais le virer: L’interface lo est déjà déclarée dans /etc/network/interfaces, et on y voit une interface eth0, qui ne devrait pas exister ?

A+

Dans une Debian non bricolée il n’y a rien dans ce dossier

debian:/etc/network/interfaces.d$ ls -alrt
total 8
drwxr-xr-x 2 root root 4096 mars  13  2015 .
drwxr-xr-x 7 root root 4096 avril  5  2016 ..

Qui a ajouté ce fichier /etc/network/interfaces.d/setup et pourquoi?

Je ne sais pas qui l’a ajouter et pourquoi…

OK merci. Plus de message au démarrage.